Interactive transport path with service performance related features

Abstract

In some implementations, a method for visualizing an interactive transport path with service performance related features includes displaying, on a display device, a map viewer including a geographic area map; obtaining a transportation path of a travel of a vehicle, wherein the transportation path comprises one or more travel segments within the geographic area map; obtaining a corresponding state of an onboard service provided during each corresponding one of the one or more trip segments of the trip of the vehicle; obtaining, for each corresponding one of the one or more trip segments, a corresponding one of one or more trip segment icons, each trip segment icon having a feature representative of the corresponding state of the onboard service provided during the corresponding trip segment; and displaying the one or more travel segment icons corresponding to the one or more travel segments in the map viewer.

Description

[0001] Inventors:

[0002] Ryan Dunner Technical Field

[0003] The present disclosure relates generally to mobile communication systems, and more particularly to monitoring communication systems that provide onboard services on vehicles such as airplanes, trains, ships, cruisers, buses, and the like. Background Art

[0004] There are many Internet service providers in the market that provide commercial aviation data to customers. The aviation data may include information about the onboard communication services available on commercial aircraft. The onboard services may include various communication and entertainment services, such as access to the Internet, computer-based entertainment, etc. The commercial aviation data is described in various graphical representations including a graphical user interface (GUI).

[0005] However, most often, commercial aviation customers want to view information about the aircraft's onboard services with a high level of detail and granularity. For example, customers want the displays provided to be comprehensive, yet easy to gather. Customers also want to be able to request and receive information about the status of onboard services at any point in the aircraft's itinerary. The term "itinerary" or "transportation path" herein refers to a flight, voyage, cruise, or tour performed by a vehicle. The terms "vehicle" and "vehicle" are used interchangeably herein.

[0006] Customers also want to know when onboard services provided by an aircraft are up or down during a trip, what types of problems prevented the onboard services from being available on the aircraft, and so on.

[0007] Having this type of information readily available can be very important to commercial aviation customers, especially those responsible for ensuring that inflight services are available on a vehicle. For example, an airline operator would like to know the status of services at various points in an aircraft's journey, for example. In fact, in some cases, an operator would like to know the status of inflight services on a minute-by-minute basis so that the operator can evaluate and improve the health of inflight services provided by aircraft flying over different regions, from different airports to different destinations, at different times, in different time zones, etc.

[0008] Therefore, there is a need for improved methods and tools that allow the status of onboard services provided on a vehicle to be interactively monitored and visualized during the vehicle's journey, and more specifically, that allow the status of onboard services to be interactively monitored / visualized during various parts of the vehicle's journey. Summary of the invention

[0009] In some implementations, a method allows interactive monitoring and visualization of a graphical representation of the status of onboard services provided on a vehicle during a journey of the vehicle. More specifically, the method allows visualization of the status of onboard services provided by the vehicle during various portions and points of the journey in a GUI. In other words, the method provides an interactive GUI that allows visualization of the quality of onboard services provided during corresponding portions of the journey of the vehicle, and allows interaction with the GUI to request detailed information about the quality of onboard services provided at corresponding points of the journey of the vehicle. This information may be provided in real time or offline, and may be provided to the personnel of the vehicle as well as to ground operators of the enterprise managing the vehicle. Different ways of determining the quality of onboard services will be described later.

[0010] Assume that a vehicle, such as an airplane, takes off from an airport in Los Angeles, California, and flies to San Francisco, California. However, when the airplane reaches an altitude of 10,000 feet above the ground, the crew of the airplane notices that, for example, some of the onboard services, including in-flight connectivity (IFC), have been compromised. The presented method allows for displaying a GUI that allows the crew to identify the point in the trip at which connectivity is compromised, monitor the quality of the in-flight connectivity service throughout the trip, and interactively obtain more information about the service at any point in the trip.

[0011] The presented GUI can be displayed to the crew of the aircraft, for example, in an aircraft cockpit, and can be used to visualize the transportation path of the aircraft's journey. As the aircraft continues to fly toward its destination, the GUI can be used to provide detailed information about the services provided at any point and during any portion of the journey. The interactive GUI can also be displayed in a control station used by ground operators at airports and airlines.

[0012] The interactive GUI may be available online, ie, in real time as the aircraft continues to fly toward its destination, or offline, ie, after the trip is completed.

[0013] In some implementations, the interactive GUI depicts the interactive transportation route using a graphical representation of the route. The route may be represented using different colors, patterns, line shapes, etc. to indicate the quality of the onboard services provided during corresponding portions or points of the journey. For example, segments of the journey during which the quality of the onboard services is compromised may be color-coded using red, while segments of the journey during which the quality of the onboard services is good may be color-coded using green, and so on.

[0014] The status of the in-flight services provided during the trip may include aggregate information about the in-flight services provided during each trip segment of the trip. The aggregate information about the in-flight services provided during the corresponding trip segment may include aggregate information about: in-flight entertainment (IFE) services, in-flight connectivity (IFC) services, IFE session services, Wi-Fi connection services, Wi-Fi session services, TV services, TV session services, data session services, promotional session services, email services, and / or SMS services.

[0015] The GUI presented herein may display an icon indicating the current position of an aircraft along a corresponding transportation path. When a user hovers a pointing device such as a cursor over any portion of the transportation path, the icon indicating the current position of the aircraft may be updated and repositioned accordingly. For example, when the user moves the cursor to another location along the path, the GUI detects a corresponding hovering event, and in response thereto, the GUI repositions the icon to a new location along the path.

[0016] In addition to visualizing the current position of the aircraft along the path, the GUI may also display messages providing detailed information about the quality of the onboard service at the location along the path. Example messages will be described later.

[0017] The interactive GUI may also depict one or more flight indicator viewers that show graphical representations of corresponding types of onboard services. Each graphical representation of a service may be represented as a function of the time of the trip. Examples of flight indicator viewers may include viewers that depict IFE services, IFC services, etc.

[0018] In addition, the interactive GUI may depict a vertical bar positioned on the displayed flight metrics viewer. The bar may be represented as, for example, a vertical line positioned at a location along the path. The bar may be repositioned along the path as the user hovers over the path using a pointing device and moves the pointing device to a new location along the path. The bar allows the user to track events occurring during the trip and visualize the quality of the onboard services provided at the corresponding point in the trip.

[0019] One of the benefits of the provided interactive GUI is that the interface provides interactivity with the displayed information and allows the user to request information about the quality of the onboard services provided at any point during the journey of the vehicle. The GUI may display, for example, messages indicating disruption events, such as (e.g., the aircraft was out of coverage during the corresponding portion of the journey, and therefore, the IFC service onboard the aircraft was not available during the particular portion of the journey. The message may also indicate the cause of the service disruption event and events that may have affected the quality of the service, such as out of coverage events, tail blocking events, transport prohibition events, no aircraft data bus, etc. Disruption events will be explained later.

[0020] Assume that the GUI displays a specific flight indicator viewer that graphically represents the quality of the IFC service provided by the vehicle during the trip. If the quality of the IFC service is poor during a specific segment of the trip, the icon representing the corresponding segment of the trip depicted in the GUI can be color-coded using, for example, red.

[0021] However, if the quality of the IFC service during another segment of the journey is good, the icon representing that segment of the journey depicted in the GUI may be color-coded using, for example, green. The GUI may also display a message indicating details of the quality of the IFC service provided, for example, on the board of the aircraft during the corresponding segment of the journey. The GUI may also color-code and color-coordinate other icons and indicators of the GUI. Details will be described later.

[0022] Some of the reasons why the in-flight services on the aircraft are unavailable may be determined by policies and rules imposed by countries and their corresponding governments. For example, some government policies stipulate rules about whether aircraft flying over the territory of these countries can send and receive data wirelessly. Information about those rules can be included in the interactive GUI presented herein to allow the user to determine why the quality of the in-flight services provided on the aircraft is impaired.

[0023] Once the aircraft reaches a certain altitude, some of the aircraft's onboard services are unavailable. Information about those rules can also be displayed in the GUI to allow the user to determine why the quality of the onboard services is compromised.

[0024] In some implementations, an apparatus for visualizing an interactive transportation path with service performance-related features includes: a processor; a memory in electronic communication with the processor; and instructions stored in the memory and executable by the processor to cause the processor to perform the steps of the method described herein.

[0025] In some implementations, one or more non-transitory computer-readable storage media stores one or more instructions for visualizing an interactive transportation path with service performance-related features. The instructions of the storage media can be stored in a memory and, when executed by one or more processors, can cause the processor to perform the steps of the method described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] A further understanding of the nature and benefits of the present method may be achieved with reference to the following drawings. In the accompanying drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following a second label that distinguishes similar components after the reference label.

[0027] In the attached picture:

[0028] Figure 1 is an example of a block diagram of a network communication system according to one or more embodiments.

[0029] Figure 2 is an example of a block diagram of a ground server according to one or more embodiments.

[0030] Figure 3 is an example block diagram of an onboard system according to one or more embodiments.

[0031] Figure 4A is an example of a GUI depicting an interactive transportation path viewer having service capability related features in accordance with one or more embodiments.

[0032] Figure 4B is an example of a GUI depicting an interactive flight metrics viewer having service performance related features in accordance with one or more embodiments.

[0033] Figure 4C is an example of a GUI depicting an example of an interactive flight metrics viewer having service performance related features in accordance with one or more embodiments.

[0034] Figure 4D is an example of a GUI depicting an example interactive transportation flight path viewer and an example interactive flight metrics viewer having service performance related features in accordance with one or more embodiments.

[0035] Figure 4E is an example of a GUI depicting an example interactive transportation flight path viewer and an example interactive flight metrics viewer having service performance related features in accordance with one or more embodiments.

[0036] Figure 5A is an example process for generating and displaying an interactive transportation path viewer having service performance related features in accordance with one or more embodiments.

[0037] Figure 5B is an example process for generating and displaying an interactive transportation path viewer having service performance related features triggered by hover events in accordance with one or more embodiments.

[0038] Fig. 6A are example processes for generating and displaying one or more metrics flight viewers having service performance related features in accordance with one or more embodiments.

[0039] Figure 6B are example processes for generating and displaying one or more metrics flight viewers having service performance related features triggered by hover events in accordance with one or more embodiments.

[0040] Figure 7 is a block diagram depicting a computer system upon which some embodiments may be implemented. DETAILED DESCRIPTION

[0041] In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding of the method described herein. However, it will be apparent that the method can be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid unnecessary confusion of the method.

[0042] The detailed description is organized as follows according to the following overview:

[0043] 1.0. Overview

[0044] 1.1. Interactive transport routing with service performance-related characteristics

[0045] 1.2. Interactive flight indicator viewer with service performance related features

[0046] 2.0. Example communication system for generating interactive path viewer and flight indicator viewer

[0047] 2.1. Communication system

[0048] 2.2. Ground system

[0049] 2.3. Airborne systems

[0050] 3.0. Example interactive transport route viewer with service performance related features

[0051] 4.0. Example interactive flight metrics viewer with service performance related features

[0052] 5.0. Example of a hybrid viewer

[0053] 6.0. Flowchart

[0054] 6.1. Interactive map viewer with service performance related features

[0055] 6.2. Map Viewer Interactivity

[0056] 6.3. Interactive flight metrics viewer with service performance related features

[0057] 6.4. Flight Indicator Viewer Interactivity

[0058] 7.0. Hardware Implementation

[0059] 8.0. General Considerations.

[0060] *

[0061] 1.0. Overview

[0062] 1.1. Interactive transport routing with service performance-related characteristics

[0063] In some implementations, a method provides an interactive GUI that allows visualization, online and / or offline, of the quality of onboard services provided during a journey of a vehicle and allows interaction with the GUI to request and receive detailed information and messages about the quality of onboard services provided at respective points of the journey of the vehicle. The visualization of the onboard services may include generating and displaying a map viewer that depicts an interactive transportation path corresponding to the journey of the vehicle.

[0064] An example method for visualizing an interactive transportation route having service performance-related features may include displaying a GUI on a display device that includes a map viewer that includes a map of a geographic area. Figure 4A An example map viewer 404 is depicted in FIG.

[0065] The example method may further include obtaining a flight path of the vehicle's trip. The flight path of the vehicle's trip may be depicted in the GUI and may have a trip start location and a trip end location. Figure 4A An example trip start location 406 and an example end location are depicted in FIG.

[0066] The flight path may include one or more trip segments depicted within a map of the geographic area. Each trip segment may have a corresponding trip segment start location and a corresponding trip segment end location. Each trip segment may be displayed as a segment overlay on the map of the geographic area.

[0067] Additionally, the method may include obtaining a corresponding status of an onboard service provided during each corresponding one of the trip segments of the trip of the vehicle, and obtaining a corresponding trip segment icon for each corresponding one of the trip segments. Figure 4A Examples of trip segment icons 408 , 410 , 411 , and 412 are depicted in the GUI of .

[0068] Each trip segment icon may have a feature representing a corresponding status of the onboard service provided during the corresponding trip segment. The feature may be represented using a shape, color, pattern, shading, dashed line, broken line, or color pattern. For example, if the quality of IFC during a particular segment of the trip is poor, the trip segment icon depicted in the GUI representing the particular trip segment of the trip may be color-coded using, for example, red.

[0069] Each trip segment icon may be positioned in a map viewer of the GUI according to a corresponding trip segment start position and a corresponding trip segment end position of the corresponding trip segment.

[0070] The corresponding status of the in-flight services provided during the corresponding trip segment may include aggregated information about the in-flight services provided during the corresponding trip segment. The aggregated information about the in-flight services provided during the corresponding trip segment may include aggregated information about the following: in-flight entertainment (IFE) services, in-flight connectivity (IFC) services, IFE session services, etc.

[0071] In some implementations, the method further includes obtaining a first indication of a first hover event of a pointing device over a first trip segment icon displayed in a map viewer of the GUI. In response to obtaining the first indication of the first hover event, displaying a first message at a first location near the first trip segment icon in the map viewer. The first message may indicate a corresponding first status of an onboard service provided during a first trip segment corresponding to the first trip segment icon. Figure 4A An example first message 414 is depicted in FIG.

[0072] The method may further include obtaining a second indication of a second hovering event of the pointing device over the second trip segment icon. In response to obtaining the second indication of the second hovering event, removing the first message from the map viewer of the GUI and displaying a second message in the map viewer at a second position near the second trip segment icon. The second message may indicate, for example, a corresponding second status of an onboard service provided during a second trip segment corresponding to the second trip segment icon.

[0073] 1.2. Interactive flight indicator viewer with service performance related features

[0074] In some implementations, a method provides an interactive GUI that allows visualization of the quality of respective types of onboard services provided during a journey of a vehicle, and allows interaction with the GUI to request and receive detailed information about the quality of respective onboard services provided at respective points of the journey of the vehicle. The visualization of the onboard services may include visualization of an interactive flight indicators viewer that depicts the quality of respective onboard services provided during the journey. In addition to displaying the interactive flight indicators viewer, the method may also include displaying the interactive map viewer that has been previously described. Figure 4A An example map viewer 404 is depicted in FIG. FIG. 4B to FIG. 4C Examples of flight indicator viewers 442 to 444 are depicted in FIG. FIG. 4D to FIG. 4E An example of a flight indicators viewer 442 combined with a map viewer 404 is depicted in FIG.

[0075] An example method for visualizing an interactive transportation path and flight metrics viewer having service performance related features includes displaying a map viewer including a map of a geographic area on a display device.

[0076] The method may further include displaying in a map of the geographic area of ​​a map viewer of the GUI one or more trip segment icons corresponding to trip segments of a flight path of a trip of the vehicle and corresponding to time intervals of the trip.

[0077] The method may also include displaying a flight indicator viewer on the display device, the flight indicator viewer having one or more viewer segment icons corresponding to one or more time intervals of the trip and corresponding to one or more viewer segments of the flight indicator viewer. Examples of viewer segment icons of flight indicator viewer 442 include viewer segment icon 424, viewer segment icon 426, viewer segment icon 428, and viewer segment icon 429.

[0078] Each viewer segment icon may have a viewer feature that represents a corresponding state of an onboard service provided during a corresponding time interval in one or more time intervals of the time period of the trip. Examples of states are described later.

[0079] In some implementations, the method further includes obtaining an indication of a hovering event of the pointing device. The indication may specify that the pointing device hovered over a first trip segment icon in the trip segment icons of the map viewer or over a first viewer segment icon of the flight indicator viewer at a specific time of the trip.

[0080] In response to obtaining an indication of the hover event, a first visual marker is displayed in the map viewer overlying a first trip segment icon corresponding to a first time interval including the specific time at a specific time. An example of the first visual marker 416 is shown in FIG. Figure 4A , Figure 4D and depicted in FIG4F , and are represented as dots.

[0081] The second visual marker is displayed in the flight indicator viewer while the first visual marker is displayed in the map viewer. The second visual marker is displayed as an overlay on the first viewer segment icon corresponding to the first time interval including the specific time at the specific time. The example second visual marker 490 is displayed in FIG. 4B to FIG. 4C and are represented as vertical bars. Additional examples include Figure 4D The second visual mark 496 and Figure 4E The second visual mark 498 in FIG. 498 is shown in FIG. 498. It should be noted that FIG. 4A to FIG. 4E The scenes depicted in are independent and unrelated to each other.

[0082] Each of the first visual marker and the second visual marker may have one or more characteristics, such as shape, color, pattern, shading, etc. For example, referring to Figure 4A , the first visual marker 416 (i.e., the corresponding point) may be color-coded using the same color used to color-code the first trip segment icon 412 of the trip segment icons for the flight path depicted in the map viewer 404. The corresponding first viewer segment icon of the viewer segment icons of the flight metrics viewer may be color-coded using the same color or pattern.

[0083] In addition, the method may include displaying a first message in the map viewer in response to obtaining an indication of the hover event. The first message may be displayed as an overlay on a first trip segment icon corresponding to a first time interval that includes the specific time. In addition, the first message may indicate a corresponding first status of an onboard service provided at the specific time of the time period of the trip of the vehicle. In addition, the first message may include time information about the first time interval and the specific time. Figure 4D An example first message 476 is depicted in Figure 4E An example first message 486 is depicted in FIG.

[0084] The corresponding first status of the in-flight services provided at the specific time of the time period of the journey of the vehicle may include aggregated information about the in-flight services provided at the specific time of the journey of the vehicle. Examples of in-flight services have been described above.

[0085] A second message may be displayed in the flight indicator viewer while the first visual marker is displayed in the map viewer. The second message may be displayed overlying the first viewer segment icon corresponding to the first time interval including the specific time. The second message may indicate a corresponding second status of an onboard service of a specific type and provided at a specific time during the time period of the transport's trip. The corresponding second status of an onboard service of a specific type and provided at a specific time during the time period of the transport's trip may include aggregated information about onboard services of a specific service type provided at the specific time during the transport's trip.

[0086] In some implementations, trip segment icons depicted in the map viewer may be color-coded using colors corresponding to corresponding ranges of quality of the on-board communication service provided during one or more corresponding ones of the trip segments of the trip.

[0087] In addition, the viewer segment icons may be color-coded using colors corresponding to corresponding ranges of quality of the onboard communication service provided during corresponding ones of the trip segments of the trip. For example, one of the one or more trip segment icons depicted in the map viewer may be depicted using the same color as a corresponding viewer segment icon in the viewer segment icons of the flight metrics viewer.

[0088] In some implementations, in response to determining that the second visual indicia overlies a particular viewer segment icon depicted in the flight indicator viewer, the display device may increase the brightness of a color used to depict the particular viewer segment icon and decrease the brightness of a color used to depict the remaining viewer segment icons of the one or more viewer segment icons depicted in the flight indicator viewer.

[0089] 2.0. Example communication system for generating interactive path viewer and flight indicator viewer

[0090] Various vehicles (such as airplanes, ships, buses, etc.) may be equipped with onboard systems configured to provide onboard communication services during travel. Onboard services may be consumed by passengers of the vehicle, crew members operating the vehicle, ground operators managing a fleet of vehicles, etc. The user experience associated with consumption of onboard services may be affected by the performance of the communication server and the communication connections established between the vehicle, satellite, and ground systems.

[0091] The quality of onboard service provided by a vehicle is often measured in terms of bandwidth, availability, reliability, usability, and speed. As the quality of service provided by a vehicle improves, passenger and crew satisfaction and enjoyment also increase. However, providing high-quality onboard service often requires continuous and careful monitoring of the service, and quick and efficient resolution of service problems.

[0092] In order to effectively monitor onboard services, service-specific status and metric data is collected and visualized to allow identification of problems with the vehicle in providing the onboard service.

[0093] In some implementations, embodiments of the present disclosure provide an interactive GUI that allows visualization of the quality of onboard services provided during a journey of a vehicle online and / or offline, and allows interaction with the GUI to request and receive detailed information and messages about the quality of onboard services provided at respective points of the journey of the vehicle. The GUI may collect, display, and provide for interaction with GUI data. Some of the GUI data may include status information of onboard services provided during the journey of the vehicle.

[0094] As used herein, the terms "GUI data" and "interface data" may refer to any data in a computer system that is related to the representation of one or more GUIs or portions thereof. The GUI data may represent, for example, various graphical icons and / or other visual identifiers or features. In addition, the GUI data may include data or code that provides instructions for generating or displaying / presenting various graphical icons and other visual identifiers and features on a display device.

[0095] GUI data may also refer to any type of user interface page or portion of a page with any type of content. GUI data may refer to, for example, a page of a website, a page of a network-enabled application, or any type of code used by a user interface to generate a web page, content page, or interface. GUI data may include code conforming to any suitable or desired language, such as hypertext markup language (HTML) code, Java or JavaScript code, Android code, iOS code, other embedded device operating system code, etc.

[0096] The status information of the onboard services provided during the trip may correspond to performance indicators of the onboard services provided during the trip and may be represented in the GUI using icons, colors, shading, or other visual objects.

[0097] User input associated with icons or other objects displayed in the GUI (such as clicking, tapping, hovering, etc.) may trigger or cause the generation, provision and / or presentation of GUI data related to communication services provided on the vehicle and / or related hardware devices regarding the journey being conducted by the vehicle.

[0098] The icon may have one or more features, including, for example, visual features. Certain visual features of the icon may indicate a status level of a communication service provided onboard the vehicle. For example, if a user provides user input indicating a hover event of a user's pointing device (e.g., a mouse) over a specific trip segment icon displayed in a map viewer, a corresponding status of the onboard service provided onboard during the corresponding specific trip segment may be obtained and provided to the GUI for display in the GUI. By allowing user input and interaction associated with icons displayed in the GUI, a user may be able to access, for example, detailed information about various types of onboard services provided by the vehicle during the trip.

[0099] Vehicle data associated with communication services provided on a vehicle may include any type of communication service related information associated with the vehicle. For example, vehicle data may indicate service cases opened for the vehicle over a period of time. Vehicle data may further provide information regarding communication service hardware replacement or maintenance. Such information may provide insight into whether equipment replacement may help the performance of the communication services on the vehicle.

[0100] The trip data associated with the communication services provided during the trip may include any type of communication service related information associated with the trip. For example, the trip data may indicate passenger experience reporting events captured during the trip or passenger experience reporting availability of onboard services provided during the trip.

[0101] The status of the service type of an onboard service provided by a vehicle may be represented in a variety of ways. For example, the status may be represented by a single value (e.g., a number), by a set of indicator values ​​(e.g., a set of numbers), by a series of values, etc. A single status value for a service type may be calculated by aggregating different indicator data values ​​determined for the type of service provided by the vehicle during a trip. According to another example, the status of a network connection provided by a vehicle may be represented by a set of indicator values, each of which is calculated by aggregating measured values ​​of a connection provided during a trip performed by the vehicle over a time period.

[0102] The count and type of onboard services provided to passengers during a trip may vary and depend on the implementation. Examples of types of communication services may include network connections to the Internet and / or other networks. Examples of types of in-flight entertainment services may include streaming TV services, in-flight entertainment services (providing access to content stored on board, such as movies and shows), etc. The availability and utilization of on-board services may be collected by a computer server installed, for example, in a vehicle. A server installed in a vehicle may be referred to as an on-board server. The on-board server may send the collected indicator data to one or more ground systems, which in turn may process and aggregate the data and display the aggregated data on a display device.

[0103] 2.1. Communication system

[0104] In some implementations, the methods presented herein may be implemented as part of a communication system. The communication system may include several components, and these components may cooperate with each other to determine status information of communication services provided during a journey of a vehicle and provide the status information to an interactive GUI. These components allow the GUI to visualize, for example, the quality of onboard services provided during a journey of a vehicle, and to provide and receive detailed information about the quality of onboard services provided at corresponding points of the journey of the vehicle.

[0105] Figure 1 is an example of a block diagram of a network communication system 100 according to one or more embodiments. Figure 1, other drawings, and all descriptions and claims in this disclosure are intended to present, disclose, and claim a technical system and method in which specially programmed computers designed using a dedicated distributed computer system perform previously unavailable functions to provide practical application of computing technology to machine learning model development, validation, and deployment problems. In this manner, the present disclosure proposes a technical solution to the technical problem, and any interpretation of the present disclosure or claims covering any judicial exception to patent eligibility (such as abstract ideas, mental processes, methods of organizing human activities, or mathematical algorithms) have no support in this disclosure and are erroneous.

[0106] In some implementations, communication system 100 includes one or more communication satellites 102A-102B, one or more vehicles 104A-104B, one or more network gateways 108A-108B, one or more network performance monitoring units 110A-110B, one or more ground systems 112, one or more display devices 114, and one or more data communication networks 116. Other embodiments may include fewer or more components.

[0107] In some implementations, the communication system 100 supports bidirectional communications between vehicles 104A-104B, gateways 108A-108B, network performance units 110A-110B, communication network 116, ground system 112, and potentially other components of the system 100 (not shown) via air-to-ground connections or otherwise.

[0108] The display device 114 may be configured to display, for example, icons that visualize the status of the onboard services provided during the journey of the vehicle. For example, the display device 114 may be configured to generate a GUI for graphically presenting icons (using colors, shading, patterns, etc.) to represent the onboard services provided during the journey.

[0109] Satellites 102A-102B may be configured to provide network communication connections to communication systems implemented in vehicles 104A-104B, including target devices implemented and / or present in vehicles 104A-104B. Target devices may be mobile devices operated by crew and passengers of vehicles 104A-104B, and may include smartphones, tablet computers, iPods, laptop computers, PDAs, etc. Satellites 102A-102B may, for example, facilitate network communications to and from target devices to provide Internet access, TV programs, movies, data news feeds, etc.

[0110] Vehicles 104A-104B may be mobile machines configured to carry passengers, crew members, and cargo, and provide communications network connectivity and onboard services. Figure 1The vehicles 104A-104B are depicted as airplanes, but the vehicles 104A-104B may include any type of vehicle, including ships, trains, buses, cars, cruisers, etc. The vehicles 104A-104B may be configured to provide onboard services, such as access to the Internet, in-flight entertainment, etc.

[0111] In some implementations, vehicles 104A-104B include a location determination device, such as an inertial measurement unit (IMU) or a global positioning system (GPS). Such a device, if installed, may allow the vehicle to determine the physical location of the vehicle. Ground system 112 may utilize the location information to perform certain functions disclosed herein.

[0112] Other techniques for determining the location of a vehicle may also be used. For example, in an embodiment where the satellites 102A-102B are spot beam satellites, the vehicles 104A-104B may be able to deduce the location of the vehicle based on the spot beams used to communicate with the satellite network 116.

[0113] In some implementations, the vehicle 104A-104B may send location information of the vehicle to the ground system 112. The location information may be associated with vehicle-specific metrics collected near or at the reported location. This may allow the ground system 112 to associate specific vehicle-specific metrics with specific network service areas based on the associated location of the vehicle.

[0114] The location data of one or more of the vehicles 104A-104B may be obtained by the ground system 112 from Figure 1 The location data may be obtained from a separate entity or server not shown in the figure. Such an entity or server may receive the location data from the vehicle, or derive the location data in other ways.

[0115] The vehicles 104A-104B may include onboard computer systems and sensor systems configured to collect and monitor indicator data regarding various events that reflect the quality of the onboard services. The indicator data may include information regarding the availability and utilization of network connections and / or in-flight entertainment services available on the vehicles 104A-104B. These events may include receiving a request for an Internet connection, a data communication session, downloading a TV program from a content provider, downloading a movie from an onboard movie content server, etc.

[0116] The metrics data collected by the onboard servers of the vehicles 104A-104B may include, for example, metrics showing the availability and utilization of network connectivity and onboard services on the respective vehicles, respective trips, and / or respective portions of the trips. The metrics data may also include web browsing scores, video streaming scores, customer satisfaction scores, etc. The metrics data may include upload speed metrics, download speed metrics, wait time metrics, etc.

[0117] The collected metric data may be sent from the onboard server of the vehicle 104A-104B to the ground system 112 and / or the network performance monitoring units 110A-110B. The metric data may be sent via, for example, the network gateways 108A-108B.

[0118] The network performance monitoring units 110A-110B may be configured to collect metrics data for onboard services provided on the vehicles 104A-104B. The metrics data may be collected by the network performance monitoring units 110A-110B themselves, the satellites 102A-102B, and / or the vehicles 104A-104B. The metrics data may be processed by any of the monitoring units 110A-110B, the ground system 112, the satellites 102A-102B, and / or the vehicles 104A-104B.

[0119] Ground systems 112 may be configured to process the collected metrics data, aggregate the data, and use the data to generate, for example, map viewers and flight metrics viewers for visualizing performance indicators of onboard services provided during a trip of a vehicle. These viewers may be used by vehicle crews, operators of vehicle control centers, fleet operators, service providers, and suppliers to allow them to evaluate the quality of onboard services provided during a trip performed by one or more vehicles.

[0120] The ground system 112 may include one or more electronic hardware computers or components including control circuitry configured to perform certain functions discussed in detail below.

[0121] The network gateways 108A-108B may be computer-based systems configured to perform the functions of a communication modem. These functions may include modulating and demodulating signals transmitted between the satellites 102A-102B and the network performance monitoring units 110A-110B. These functions may also include packet queuing, packet acceleration and deceleration, network address translation (NAT), firewall-based security, periodic pinging, and other signal processing functions.

[0122] The communication network 116 may be implemented as any type of communication network or group of communication networks. The network 116 may be configured to provide support for a variety of communication protocols, including broadband protocols, wireless protocols, etc. The network 116 may support two-way communication between the gateways 108A-108B, the monitoring units 110A-110B, the ground system 112, the display device 114, and other computer systems and servers (not shown) implemented in the system 100.

[0123] 2.2. Ground system

[0124] In some embodiments, a method for visualizing the quality of airborne services provided during a journey of a vehicle and providing requested detailed information about the quality of airborne services provided at respective points of the journey of the vehicle is implemented in one or more ground systems. Performance indicators of airborne services may be visualized using a GUI configured to generate and display, for example, a map viewer and a flight indicators viewer depicting status information of communication services provided during the journey.

[0125] Figure 2 is an example of a block diagram of a ground server 200 according to one or more embodiments. The ground system 200 may be, for example Figure 1 Ground system 112 described in . Ground system 200 may be implemented in a computer server or a network of computer servers (such as a cloud-based system and / or a virtual computing node).

[0126] In some implementations, ground system 200 includes a single hardware computer contained within a single physical housing, while in other embodiments, ground system 200 is implemented in multiple computers installed in multiple physical housings, some of which are located within the single physical housing and other computers are geographically distributed away from each other. The functionality described with respect to ground system 200 may be distributed among the various computers in a manner different from that shown or described herein. Figure 1 Between components of system 100.

[0127] In some implementations, ground system 200 is configured to collect, monitor, aggregate, and otherwise process indicator data indicating the performance of onboard services of one or more service types provided in a vehicle. Ground system 200 can be configured to use the collected and processed information to generate, for example, a map viewer and a flight indicator viewer for visualizing performance indicators of onboard services provided during a trip.

[0128] Ground system 200 may be configured to obtain, for example, a vehicle identifier of a vehicle for which airborne services are to be collected and monitored and status information for a trip carried by the vehicle. Ground system 200 may also receive a request to obtain status information for airborne services provided during a particular portion or point of a trip.

[0129] The ground system 200 may obtain the vehicle identifier using various techniques. For example, the ground system 200 may request the vehicle identifier from the vehicle control center of the fleet and store the identifier in a storage device of the ground system 200.

[0130] The ground system 200 may use the vehicle identifier as a search keyword in, for example, a query issued by the ground system to request index data about onboard services provided on the corresponding vehicle. For example, the ground system 200 may use the vehicle identifier as a search keyword in a query issued by the ground system to request index data about onboard services provided on the corresponding vehicle. Figure 1 ) to request indicator data about onboard services provided by vehicle 104A during a specific time period at a specific point in the journey.

[0131] In other implementations, the indicator data regarding the onboard services provided on the vehicle is automatically provided by an onboard system implemented in the vehicle itself, or obtained from a ground network performance monitoring unit, or obtained in combination with an onboard system implemented in the vehicle and a ground network performance monitoring unit.

[0132] In some implementations, ground system 200 includes one or more service monitors 202, one or more data aggregators 204, one or more performance indicator generators 206, and one or more data storage units 208. System 200 may also include one or more processors 210, one or more storage units 212, one or more display devices 214, and one or more network interface cards 216. The components of ground system 200 may communicate with each other directly or indirectly via a communication bus 220. Other embodiments may include fewer or more components.

[0133] Display device 214 may be configured to display a visualization of the status of onboard services provided during a journey of a vehicle. The visualized status of onboard services may be represented using, for example, a journey segment icon, a flight indicator segment icon, etc. Examples of icons have been described above.

[0134] The display device 214 may be configured to generate a GUI for displaying the viewer in a concise and communicable form. The viewer may use icons with different colors, shades, patterns, etc. to indicate the status of the onboard services provided during the trip.

[0135] The display 214 may be implemented as an electronic display such as a CRT display, an LCD display, a touch screen, a mobile device screen, or the like.

[0136] The service monitor 202 may be configured to collect metrics data about onboard services of various service types provided in a vehicle, such as Figure 1 . These events may include receiving a request for an Internet connection, a data communication session, downloading a TV program from a content provider, downloading a movie from an onboard movie content server, etc. These events may also include receiving an indication that an Internet connection is available or unavailable in the vehicle at a given time, successfully or unsuccessfully opening or closing a data communication session, successfully or unsuccessfully downloading a movie to a target device operated by the vehicle, etc. Metric data regarding events may be collected when a passenger boards a vehicle, when the vehicle is traveling, when the vehicle arrives at its destination, and / or when a passenger exits a vehicle.

[0137] In some implementations, the data aggregator 204 generates an average, maximum, minimum, mean, and / or median of two or more communication service performance indicators for a communication service provided on a vehicle during at least one trip of the vehicle. The data aggregator 204 may determine the negative variance between the communication service performance indicators of the vehicle being monitored as it travels along its travel route. The negative variance itself may be aggregated to produce a summary indicator that represents the difference in performance of the communication service of the monitored vehicle compared to certain performance targets. This may provide a threshold / indicator for evaluating communication service performance. In some implementations, the aggregation of negative variances may be divided by the duration of a given trip to the current point to provide an average negative variance experienced during the trip.

[0138] The data aggregator 204 may be configured to process, classify, and aggregate the collected and monitored indicator data. The processed data may be classified and / or aggregated based on service type, vehicle identifier, fleet identifier, airline identifier, airport identifier, etc. The type of processing performed on the data may depend on various factors. For example, if the data is related to a trip that has been completed by the vehicle, the data may be aggregated based on the type of data, the type of service represented by the data, the source providing the data, etc. However, if the data is related to an ongoing trip, the processing may include selecting the most recently received data from the collected data that reflects the current latest onboard service availability and utilization.

[0139] The indicator generator 206 may be configured to use the classified and aggregated information to determine a performance indicator for determining the status of services provided to passengers while onboard a vehicle. The performance indicator may indicate, for example, the performance of onboard services of one or more service types provided on a respective vehicle, a respective trip, and / or a respective portion of a trip.

[0140] The indicator generator 206 may also be configured to encode the classified and aggregated data into corresponding status indicators to reflect the performance provided in the vehicle. In some implementations, the indicator generator 206 determines the status of the onboard services of one or more service types provided on the selected vehicle. The status of the service type may be determined based on the indicator data collected for the service type provided on the selected vehicle and may include information about the service characteristics of the service provided to the passenger.

[0141] The status of a particular service type may, for example, correspond to a value (or range of values) of a service metric determined for a particular onboard service. The status may be associated with one or more icons to be displayed, for example, in a map viewer, a flight metric viewer, a message, or the like. For example, some of the features in a message may be represented numerically using, for example, a single number or a set of metric values. A single number status for a particular onboard service may be calculated as an aggregation of service metric data collected for the particular onboard service during a particular time period. A set of metric values ​​for a particular onboard service may include values ​​determined for the particular onboard service during a trip.

[0142] Other characteristics may be graphically represented using, for example, graphical elements such as icons having specific colors, patterns, etc. A graphical characteristic of a specific onboard service may correspond to a value or a range of values ​​determined based on a corresponding service indicator of the specific onboard service, and may be depicted using a specific icon having a specific color or pattern that graphically represents the corresponding value or corresponding range of values ​​for the corresponding onboard service.

[0143] In some implementations, the status may be determined by the indicator generator 206 itself. Alternatively, the status may be provided by the satellites 102A-102B, the vehicles 104A-104B, the network gateways 108A-108B, and / or the performance monitoring units 110A-110B, such as Figure 1 as shown in .

[0144] The service indicators may be stored in data storage device 208. Alternatively or additionally, the information and indicators may be transmitted to a computer server (such as other ground systems 200 and / or computer servers installed in ground system 200). The status and indicators may be used to generate a GUI such as that presented herein.

[0145] Processor 210 may be configured to provide an execution environment for performing various system-based functions and for performing the methods described herein. Processor 210 may be configured to provide, for example, support for executing an operating system and system functions implemented in ground system 200 .

[0146] The memory unit 212 may include a random access memory (RAM) unit and a read only memory (ROM) unit. The memory 212 may be used to store operating system instructions and computer readable instructions and computer executable instructions for implementing the methods described herein.

[0147] The network interface card 216 may be configured to facilitate communication between the ground system 200 and a vehicle, a satellite, a network monitoring station, a vehicle control center, a vehicle operator center, a supplier center, etc. The interface may be implemented in hardware, software, and / or a combination thereof, and may be implemented to support various communication protocols, including wireless communication protocols, broadband communication protocols, etc. The network interface 216 may also be used to provide a connection to an input device (not shown) configured in the ground system 200. The input device may include a keyboard, a smart phone, a touch screen, an audio device, etc., and may be used to provide input, a request for service performance information of an onboard service, etc.

[0148] In some implementations, the ground system 200 includes a network server ( Figure 2 ). The network server may be a single server, or may represent a distributed network of servers across geographic regions. The network server may store instructions for generating and displaying a network-based user interface. The network-based user interface may allow a user to provide user input for configuring one or more thresholds or other performance target data discussed herein. In addition, the network-based user interface may provide GUI data representing the values ​​of indicators collected by the systems / components described herein. The network server may be further configured to generate and / or provide GUI data to one or more remote monitoring systems or local monitoring systems for generating displays and / or presentations for users. The network server may receive indications of user inputs related to the GUI. The generation of GUI data may be triggered by a user input indication, as described in detail later.

[0149] In some implementations, the network server may send a message to one or more vehicles 104A-104B ( Figure 1 ) and provided by data aggregator 204 ( Figure 2 The aggregated metric may indicate, for example, the number of seconds required to load web page data provided by a web server at a vehicle 104A-104B.

[0150] Web pages and / or website content may be copied to and / or provided at a network server. In this manner, the communication service performance indicator may represent the communication service performance of the ground system 200 ( Figure 2) with the performance of the communication network of the monitored vehicle and may not be affected by performance issues that may affect the transmission of content from the origin server (e.g., the server that created the website).

[0151] 2.3. Airborne systems

[0152] In some implementations, a method for visualizing the quality of onboard services provided during a journey of the vehicle and providing requested detailed information about the quality of onboard services provided at respective points of the journey of the vehicle is implemented and installed in the vehicle itself.

[0153] In some implementations, an onboard server installed in a vehicle is used to collect service indicator data for service types of onboard services provided on the vehicle, and to send the collected indicator data from the onboard server to a ground server, which in turn uses the received indicator data to determine the status of each service type to generate, for example, a map viewer and a flight indicator viewer.

[0154] Figure 3 is an example block diagram of an onboard system according to one or more embodiments. Figure 3 The example depicted in FIG. 1 shows the vehicle 300 as an airplane; however, in other embodiments, the vehicle 300 may correspond to a helicopter, a cruise ship, a bus, a train, a ship, etc. To provide a simple example, assume that Figure 3 The vehicle 300 depicted in FIG. Figure 1 Any of the vehicles 104A-104B shown in .

[0155] In some implementations, the vehicle 300 includes an onboard system 350. The onboard system 350 can be configured to collect onboard service metrics data for the type of service provided on the vehicle 300. The onboard system 350 can also be configured to send the collected metrics data to a ground system, such as Figure 2 The ground system 200 shown in FIG. The collected indicator data can be associated with the unique identifier of the vehicle 300 by the airborne system 350 and / or the ground network performance monitoring unit of the airborne system. The unique identifier of the vehicle is also referred to herein as a vehicle identifier or vehicle ID.

[0156] If the vehicle 300 corresponds to an airplane, the identifier may include an airplane tail identifier (ID), a nose ID, an airplane serial number, etc. The identifier may be configured or hard-coded in a computer system implemented in the vehicle 300. Additional information associated with the vehicle may include a trip number (such as a flight number), a trip segment number (such as a route number), a crew identifier of a crew member of the vehicle 300, an equipment identifier (such as a serial number of an antenna or a network device), an origin terminal identifier, a destination terminal identifier, a scheduled departure time, a scheduled arrival time, etc.

[0157] In some implementations, the vehicle 300 includes various hardware components, software components, and / or combinations thereof. For example, the vehicle 300 may include one or more antennas 304, one or more transceivers 306, one or more modems 308, a communication and onboard service management system 312, one or more wireless access points (“WAPs”) 314, and one or more onboard media client applications implemented in one or more personal target devices 316 and / or one or more passenger seat back media systems 318. The vehicle 300 is also equipped with a power supply unit 330 and a positioning system 332.

[0158] Antenna 304, transceiver 306, and modem 308 may be collectively referred to as two-way communication system 302. System 302 may be configured to facilitate communication with a satellite such as Figure 1 Two-way communication with satellites 102A-102B) shown in FIG.

[0159] The communication system 302 may be configured to support two-way data communication between a communication network (such as the Internet) and the target device 316, the seat back media system 318, the positioning system 332, etc. For example, the system 302 may be configured to provide uplink data received from the target device 316 and / or the seat back system 318 to the modem 308 to allow the generation of modulated uplink data in the form of a transmit intermediate frequency (IF) signal. The system 302 may also support receiving forward downlink signals from a satellite (or other system, such as an air-to-ground system) and transmitting return uplink signals back to a satellite (or other system, such as an air-to-ground system) to support two-way communication.

[0160] Antenna 304 may be configured to communicate between vehicle 300 and a satellite or other system ( Figure 3 Signals may be transmitted between antenna 304 and a satellite (not shown). Signals may be transmitted via one or more communication links (not shown). Antenna 304 may be mounted on an elevation and azimuth gimbal that points antenna 304 toward the satellite and allows active tracking of the satellite.

[0161] like Figure 3As shown in , the modem 308 may be implemented as a separate component or may be integrated with the network performance monitoring system 321 of the communication and airborne service management system 312. The modem 308 may be configured to generate modulated uplink data based on uplink data received from the communication and airborne service management system 312. The modulated IF signal may be passed to the transceiver 306.

[0162] The transceiver 306 may be configured to convert the modulated uplink data and then amplify the modulated uplink data to generate a return uplink signal and transmit the amplified signal to one or more satellites via the antenna system 304. The transceiver 306 may also be configured to receive a forward downlink signal from a satellite via the antenna system 304. The transceiver 306 may, for example, amplify and downconvert the forward downlink signal and generate modulated downlink data (such as a receive IF signal), which is then demodulated by the modem 308. The demodulated downlink data may then be provided from the modem 308 to the communication and onboard service management system 312 for routing to the target device 316 and / or the seat back system 318.

[0163] The target device 316 may include a smartphone, laptop, tablet computer, iPod, PDA, netbook, etc. that has been brought aboard the vehicle 300 by passengers and crew members. The target device 316 and / or the seat back system 318 may communicate with the communication and onboard service management system 312 via a wired and / or wireless communication link (not shown). The communication link may be part of a local area network (LAN) or a wireless local area network (WLAN) supported by a WAP 314. The WAP 314 may be installed in various locations in the vehicle 300 and may be configured to provide traffic switching and routing functions.

[0164] Positioning system 332 may include global positioning system (GPS) circuitry configured to determine the current location or position of vehicle 300. Positioning system 332 may receive positioning information from sensors installed throughout vehicle 300. Position information may include readings of altitude, longitude, latitude, elapsed distance from the originating terminal, etc. In some implementations, each position reading is associated with a corresponding time value corresponding to the time when vehicle 300 was at a particular location and the particular location value was recorded.

[0165] 3.0. Example interactive transport route viewer with service performance related features

[0166] In the context of the present method, an itinerary is an itinerary of an aircraft, for which an interactive transportation path viewer having service capability related features is generated and displayed using a GUI. The viewer may be automatically generated when a user requests information about onboard service capabilities provided during the itinerary while the itinerary is ongoing or completed. The viewer may also be generated offline after the itinerary has concluded.

[0167] In some implementations, once a user launches and executes a software application configured to generate an interactive transportation route viewer, a system implementing the present method may generate a GUI to display an interactive map viewer showing a graphical representation of the transportation route. The trip segments may be represented using corresponding icons representing the quality of onboard services provided during the corresponding portions or points of the trip.

[0168] Figure 4A is an example of a GUI depicting an interactive transportation path viewer 400 having service performance related features according to one or more embodiments. The depicted example shows a map viewer 404 including a map of a geographic area. Figure 4A In the example of , only the left border 402 of the geographic map is shown; other borders of the geographic map are omitted. In fact, several other details of the map that are not important to the present method (such as airport names, road names, etc.) have been omitted in the examples shown in the included figures.

[0169] Reference again Figure 4A , the map viewer 404 shows the flight path of the vehicle's trip. For purposes of illustrating a simple example only, assume that the vehicle departs from Phoenix, Arizona, and is traveling to Los Angeles, California. In this example, the flight path of the trip begins at the trip start point 418 (which corresponds to the Phoenix airport) and ends at the trip end point 406 (which corresponds to the Los Angeles airport).

[0170] The flight path may include one or more trip segments displayed in the map viewer 404. The trip segments may be represented in the map viewer 404 using corresponding trip segment icons 408, 410, 411, and 412. Each of the trip segment icons 408, 410, 411, and 412 is placed according to a corresponding trip segment start position and a corresponding trip segment end position of the corresponding trip segment. A location icon 416 is used to indicate a current location or a selected location along the path.

[0171] Each trip segment icon may have a feature representing a corresponding status of the onboard services provided during the corresponding trip segment. The corresponding status of the onboard services provided during the corresponding trip segment may include aggregated information about the onboard services provided during the corresponding trip segment. Examples of aggregated information are described above.

[0172] The status of an onboard service can be determined by e.g. Figure 2 The ground system 200 described in the embodiment provides a ground system corresponding to Figure 1 Alternatively, although in rare cases, the information may be provided by an onboard system such as Figure 3 The onboard system 350 described in is provided.

[0173] The ground system may be configured to collect, monitor, aggregate, and otherwise process metrics data indicative of onboard services of one or more service types provided in a vehicle. The ground system may be configured to use the collected and processed information to determine, for example, the visual appearance of trip segment icons 408, 410, 411, and 412 to visualize the quality of the onboard services provided during the corresponding trip segment of the trip.

[0174] Reference again Figure 2 , a ground system 200 including a service monitor 202, a data aggregator 204, a performance indicator generator 206, and a data storage unit 208 may use the service monitor 202 to collect indicator data about airborne services of various service types provided in a vehicle. The service monitor 202 may receive, for example, a request for an Internet connection, a data communication session, a download of a TV program from a content provider, a download of a movie from an onboard movie content server, etc. The data aggregator 204 may be configured to generate an average, maximum, minimum, mean, and / or median value of two or more communication service performance indicators of communication services provided on the vehicle for a trip performed by the vehicle. The data aggregator 204 may also measure, classify, and aggregate the collected and monitored indicator data. The processed data may be classified and / or aggregated based on service type, vehicle identifier, fleet identifier, airline identifier, airport identifier, etc. The indicator generator 206 may use the classified and aggregated information to determine performance indicators for determining the status of the services provided to passengers when onboard the vehicle. The performance indicators may be used to determine characteristics of, for example, trip segment icons 408 , 410 , 411 , and 412 .

[0175] In some implementations, features representing the corresponding status of the onboard service provided during the corresponding trip segment are represented in the trip segment icon using color, shape, pattern, shading, dotted line, dashed line, colored pattern, etc. Different colors, shapes, etc. are used to distinguish various levels of quality of the onboard service provided during the corresponding trip segment.

[0176] exist Figure 4AIn the example shown in , different line types are used to represent the trip segment icons 408, 410, 411, and 412. More specifically, the trip segment icon 408 is represented by a short dashed line, the trip segment icon 410 is represented by a medium dashed line, the trip segment 411 is represented by a solid line, the trip segment icon 412 is represented by a long dashed line, and so on. It should be noted that FIG. 4A to FIG. 4E The scenes depicted in are independent and unrelated to each other.

[0177] Map viewer 404 provides interactive capabilities that allow the user to request and obtain additional information about the quality of onboard services provided at specific points along the itinerary. Figure 4A In the map viewer 404 of FIG. 4 , a user hovers a pointing device (such as a mouse) over a trip segment icon 412 at a point 416. Hovering the pointing device over the point 416 may cause the GUI to generate a corresponding hover event. In response to obtaining an indication of the hover event, the GUI may collect the content of the message 414 and display the message 414 at a location near the point 416 in the map viewer 404.

[0178] Message 414 may include various types of information. Figure 4A In the example shown in , message 414 indicates the corresponding status of the onboard services provided during the trip segment corresponding to trip segment icon 412 at point 416. As the vehicle continues its journey, this information may be very helpful to the crew of the aircraft and the operators working at the ground operation station at the airport.

[0179] Icon 416 may have an associated location, an associated time, and one or more associated features. One or more of the associated features of icon 416 may include shape, color, etc. Figure 4A In the example described in , icon 416 is depicted as a large black dot.

[0180] If the user moves the pointing device to a different point ( Figure 4A ), the GUI may obtain an indication of another hover event of the pointing device, and then the GUI may collect the content of another message and display the message ( Figure 4A 404) to indicate the corresponding status of the onboard services provided at the new point of the journey. When a new message is displayed, the previous message is removed from the map viewer 404 if necessary.

[0181] In other implementations, the map viewer 404 may be used with Figure 4A The map viewer shown in the is arranged differently and can be used with Figure 4A The information is depicted in different forms as shown.

[0182] 4.0. Example interactive flight metrics viewer with service performance related features

[0183] Figure 4B is an example of a GUI depicting an interactive flight metrics viewer with service performance related features in accordance with one or more embodiments. The depicted example shows an event timeline viewer 442 and an IFC session count viewer 444.

[0184] In addition, the depicted example shows a vertical marker (ie, bar) 490. The vertical marker 490 indicates the point in time when the user requested detailed information about the onboard services provided by the vehicle. The vertical marker 490 is depicted as overlaying the event timeline viewer 442 and the IFC session count viewer 444.

[0185] The user can reposition the vertical marker by hovering the user's pointing device (e.g., mouse) over different locations along any viewer 442 / 444. Once the user repositions the vertical marker to a different location, the corresponding status information of the onboard services provided at the corresponding time point is displayed to the user and visualized.

[0186] The example event timeline viewer 442 shows a plurality of viewer segment icons 424, 426, 428, and 429. The viewer segment icons correspond to the travel segments of the transportation path of the travel of the vehicle. In addition, the viewer segment icons correspond to the time intervals of the travel.

[0187] Each viewer segment icon has one or more viewer features representing a corresponding state of an onboard service provided during a corresponding time interval along the trip timeline 433. The viewer segment icons are depicted according to a vehicle altitude range 443. The altitude range 443 is displayed on the left side of the viewer.

[0188] The event timeline viewer 442 also includes a legend that provides that the viewer 442 depicts the status of an IFC disconnected using a cross-hash pattern 430 , depicts the status of an IFC compromised using black 432 , and depicts the status of an IFC connected using white 436 .

[0189] In event timeline viewer 442, according to timeline 433, viewer segment icon 424 corresponds to a trip segment that starts at approximately 13:50 and ends at 14:45. Viewer segment icon 424 shows that during this time period, the IFC service was connected until approximately 14:28, then the IFC service was disconnected for a few minutes, and then the service was impaired, but restored at approximately 4:34. Viewer segment icon 426 corresponds to a trip segment that starts at approximately 14:45 and ends at 14:47. Viewer segment icon 426 shows that during this time period, the IFC service was connected. Viewer segment icon 428 corresponds to a trip segment that starts at approximately 14:47 and ends at 16:40. Viewer segment icon 428 shows that during this time period, the IFC service was connected. Viewer segment icon 429 corresponds to a trip segment that starts at approximately 16:40 and ends at 18:40. Viewer segment icon 429 shows that during this time period, the IFC service was connected.

[0190] The example IFC session count viewer 444 shows a plurality of viewer segment icons organized into a group 450 (corresponding to a first service), a group 452 (corresponding to a second service), a group 454 (corresponding to a third service), and a group 456 (corresponding to a fourth service). Each group corresponds to a different type of onboard service provided during a journey of a vehicle. Each group represents the status of a corresponding onboard service from approximately 13:50 to 18:40 according to a timeline 435. The shape of the corresponding group representation represents the corresponding status of the onboard service provided during a corresponding time interval along the timeline 435 of the journey. The viewer segment icons are depicted according to the session count 445 depicted on the left side of the viewer.

[0191] The example IFC session count viewer 444 also includes a legend that provides that the state of the first service 450 is represented using a solid line, the state of the second service 452 is represented using a long dashed line, the state of the third service 454 is represented using a dotted line, and the state of the fourth service 456 is represented using a short dashed line.

[0192] Figure 4C is an example of a GUI depicting an example of an interactive flight metrics viewer with service performance related features in accordance with one or more embodiments. The depicted example shows an event timeline viewer 442, an IFC session count viewer 444, and an average data rate viewer 446. Figure 4B Details regarding viewers 442 to 444 are described in . Figure 4C and Figure 4B The difference between Figure 4C Also shown is an average data rate viewer 446, and Figure 4B Not shown.

[0193] The depicted example also shows a vertical marker (ie, bar) 490. The vertical marker 490 indicates a point in time when a user requests detailed information about an onboard service provided by a vehicle. The vertical marker 490 is depicted as overlying viewers 442, 444, and 446. Figure 4C As shown in , onboard service at the location indicated by vertical marker 490 appears to be compromised.

[0194] The user can reposition the vertical marker by hovering the user's pointing device (e.g., mouse) over different locations along any viewer 442 / 444 / 446. Once the user repositions the vertical marker to a different location, the corresponding status information of the onboard services provided at the corresponding time point is displayed and visualized in the GUI.

[0195] The example average data rate viewer 446 shows a plurality of viewer segment icons organized into group 461 (corresponding to download rates) and group 462 (corresponding to upload rates). Group 461 represents the download rates of the onboard services provided during the journey of the vehicle, while group 462 represents the upload rates of the onboard services provided during the journey of the vehicle. According to the timeline 437, each group represents the status of the corresponding onboard service from approximately 13:50 to 18:40. The shape of the corresponding group represents the corresponding status of the onboard service provided during the corresponding time interval along the timeline 437 of the journey. According to the download rate 446 and the upload rate ( Figure 4C ) to depict the viewer segment icon.

[0196] The example average data rate viewer 446 also includes a legend that provides that the status of the download rate 461 is represented using a solid line, while the status of the upload rate 462 is represented using a long dashed line.

[0197] 5.0. Example of a hybrid viewer

[0198] Figure 4D is an example of a GUI depicting an example interactive transportation flight path viewer and an example interactive flight metrics viewer with service performance related features according to one or more embodiments. In the depicted example, the GUI shows a map viewer 404 and an event timeline viewer 442. Both viewers 404 and 442 have been described above. It should be noted that Figure 4D The scene depicted in Figure 4A The scene depicted in .

[0199] However, it should be noted that Figure 4DThe example depicted in FIG. 4 involves a journey that begins at a starting point 418 located on a mainland and ends at a destination airport 406 located on an island. Much of the journey between the starting point 418 and the destination airport 418 is over a body of water. When an aircraft flies over a body of water, the onboard communication services provided by the aircraft are often impaired. In fact, in Figure 4D In the example shown in and as further described, IFC onboard services appear to be impaired when the aircraft is flying over water.

[0200] The depicted example also shows a vertical marker (ie, a vertical bar) 496. The vertical marker 496 indicates a point in time along the timeline 432 at which the user requested detailed information about an onboard service provided by the vehicle. The vertical marker 496 is depicted as being overlaid on the viewer 442.

[0201] The user may reposition the vertical marker by hovering the user's pointing device (e.g., mouse) over a different location within the viewer 442. Once the user repositions the vertical marker to a different location, the corresponding status information of the onboard services provided at the corresponding point in time is displayed and visualized in the viewer 442.

[0202] like Figure 4C , the IFC onboard service at the location indicated by the vertical marker 496 appears to be impaired. In fact, the event timeline viewer 442 indicates that the IFC onboard service was impaired for a period of time. Therefore, the GUI may display one or more messages that will provide additional information about the impaired service. For example, these messages may explain why the service was impaired during a particular trip segment. For example, these messages may explain that the service was impaired because the vehicle was in an out of service area, or because the rear of the vehicle blocked the signal for communicating with the IFC onboard service to or from the vehicle, or because a transmit inhibit event for transmitting the service occurred during a particular portion of the trip, etc.

[0203] Example messages include message 474 and message 476. Message 474 is displayed in map viewer 404 and indicates that being out of coverage of the IFC airborne service began at 10:07 and lasted until at least 14:16. It also indicates that the IFC service began to become available at approximately 14:20. Message 476 is displayed in event timeline viewer 442 and indicates almost the same information as message 474.

[0204] In other examples and implementations, the message may include different information and may be presented using different formats.

[0205] Figure 4Eis an example of a GUI depicting an example interactive transportation flight path viewer and an example interactive flight metrics viewer with service performance related features according to one or more embodiments. In the depicted example, the GUI shows a map viewer 404 and an event timeline viewer 442. Both viewers 404 and 442 have been described above. It should be noted that Figure 4E The scene depicted in Figure 4A The scene depicted in .

[0206] It should be noted that Figure 4E The example depicted in FIG. 4 involves a trip that begins at airport 418 and ends at destination airport 406. The two airports are located on the same continent. However, suppose that the flight from airport 418 to destination airport 406 requires flying over a desert. In fact, Figure 4E In the example shown in , a large portion of the trip from airport 418 to destination airport 418 is over the desert. When an aircraft flies over the desert, onboard communication services on the aircraft are often compromised. Figure 4E In the example shown in and as further depicted, IFC onboard services appear to be compromised while the aircraft is flying over the desert.

[0207] The depicted example also shows a vertical marker (ie, vertical bar) 498. The vertical marker 498 indicates a point in time along the timeline 432 at which the user requested detailed information about an onboard service provided by the vehicle. The vertical marker 498 is depicted as overlaying the viewer 442.

[0208] The user may reposition the vertical marker by hovering the user's pointing device (e.g., mouse) over a different location within the viewer 442. Once the user repositions the vertical marker to a different location, corresponding status information of the onboard services provided at the corresponding point in time is displayed and visualized.

[0209] like Figure 4E , the IFC onboard service at the location indicated by the vertical marker 498 appears to be impaired. In fact, because the event timeline viewer 442 indicates that the IFC onboard service was impaired for a period of time according to the timeline 432, the GUI may display one or more messages that will provide additional information about the impaired service. For example, these messages may explain why the service was impaired during a particular trip segment. The service may be impaired because the vehicle is in an out-of-service area, or because the rear of the vehicle blocks the signal used to communicate with the IFC onboard service to or from the vehicle, or because a transmit inhibit event occurred during a particular portion of the trip, etc.

[0210] Example messages include message 484 and message 486. Message 484 is displayed in map viewer 404 and indicates that the IFC service was disconnected due to tail blocking from 18:46 to approximately 18:58. It also indicates that the IFC service at the requested time 18:48:73 was blocked because the aircraft tail blocked the incoming and outgoing IFC signals. Message 486 is displayed in event timeline viewer 442 and indicates almost the same information as message 484.

[0211] In other examples and implementations, the message may include different information and may be presented using different formats.

[0212] 6.0. Flowchart

[0213] With respect to the various methods and processes disclosed herein, although certain orders of operations or steps are shown and / or described, it should be understood that the various steps and operations shown and described may be performed in any suitable or desired temporal order. In addition, any of the operations or steps shown and / or described may be omitted from any given method or process, and the methods and processes shown / described may include additional operations or steps that are not explicitly shown or described.

[0214] 6.1. Interactive map viewer with service performance related features

[0215] Figure 5A is an example process for generating and displaying an interactive transportation route viewer with service performance related features according to one or more embodiments. The steps of processes 502 to 510 may be performed by control circuitry of a device for monitoring network communication services onboard a vehicle, and / or at least in part by a ground communication service monitoring server (such as the one described above). Figure 1 Ground system 112 or Figure 2 The ground system 200) is used.

[0216] In some implementations, the device that performs some or all of steps 502 to 510 may be part of a ground server configured to monitor network communication services for a plurality of vehicles.

[0217] In some implementations, the example process may include, for example, Figure 2 Steps 504 to 508 performed by the service monitor 202 of the ground system 220 shown in FIG. Figure 2 20. In some other implementations, steps 502 to 510 may be performed by the display device 214 of the ground system 220 shown in FIG. Figure 2 Other components of the ground system 200 shown in FIG. Figure 3 Some components of the onboard system 350 shown in FIG.

[0218] In step 502, the service monitor causes the display device to display a map viewer including a map of the geographic area. Figure 4A and FIG. 4D to FIG. 4E An example of a map viewer is described in .

[0219] In step 504, the service monitor obtains a flight path of a trip of the vehicle, wherein the flight path includes one or more trip segments within a map of the geographic area, each trip segment having a corresponding trip segment start position and a corresponding trip segment end position along the flight path. Figure 4A Examples of paths are described in .

[0220] In step 506, the service monitor obtains a corresponding status of an onboard service provided during each corresponding trip segment of one or more trip segments of the trip of the vehicle. The status of the onboard service provided during the trip may correspond to a performance indicator determined for the onboard service provided during the trip.

[0221] In step 508 , the service monitor obtains, for each corresponding trip segment of the one or more trip segments, a corresponding trip segment icon of the one or more trip segments, each trip segment icon having a feature representing a corresponding status of an onboard service provided during the corresponding trip segment.

[0222] In step 510, the service monitor causes the display device to display one or more trip segment icons corresponding to the one or more trip segments in the map viewer. Each of the one or more trip segment icons may be placed according to a corresponding trip segment start position and a corresponding trip segment end position of the corresponding trip segment. Figure 4A Examples of trip segment icons are described in .

[0223] 6.2. Map Viewer Interactivity

[0224] Figure 5B is an example process for generating and displaying an interactive transportation path viewer with service performance related features triggered by a hover event according to one or more embodiments. In some implementations, the device performing steps 522 to 534 may be part of a ground server configured to monitor network communication services for multiple vehicles. In the following example, it is assumed that these steps are performed by Figure 2 The service monitor 202 shown in FIG.

[0225] In some implementations, the example process may include, for example, Figure 2 Steps 522 to 524, 528 to 530, and 534 performed by the service monitor 202 of the ground system 220 shown in FIG. Figure 226 and 532 are performed by the display device 214 of the ground system 220 shown in FIG. In some other implementations, steps 522 to 534 may be performed by Figure 2 Other components of the ground system 200 shown in FIG. Figure 3 Some components of the onboard system 350 shown in FIG.

[0226] In step 522, the service monitor determines whether a first indication of a first hovering event of a pointing device over a first trip segment icon of the one or more trip segment icons is obtained. FIG. 4A to FIG. 4B An example of a hover event is described in .

[0227] If in step 524 the service monitor determines that a first indication of a first hover event of the pointing device over a first trip segment icon of the one or more trip segment icons has been obtained, the service monitor proceeds to step 526. Otherwise, the service monitor performs a test in step 522.

[0228] In step 526, the service monitor causes the display device to display a first message at a first position near the first trip segment icon in the map viewer, the first message indicating a corresponding first status of an onboard service provided during the first trip segment corresponding to the first trip segment icon. Figure 4A and FIG. 4D to FIG. 4E Examples of messages are described in .

[0229] In step 528 , the service monitor determines whether a second indication of a second hover event of the pointing device over a second trip segment icon of the one or more trip segment icons has been obtained.

[0230] If in step 530 the service monitor determines that a second indication of a second hover event of the pointing device over a second trip segment icon of the one or more trip segment icons has been obtained, the service monitor proceeds to step 532. Otherwise, the service monitor performs a test in step 528.

[0231] In step 532, the service monitor causes the display device to display a second message at a second position near the second trip segment icon in the map viewer, the second message indicating a corresponding second status of the onboard service provided during the second trip segment corresponding to the second trip segment icon. Figure 4A and FIG. 4D to FIG. 4E Examples of messages are described in .

[0232] The process of testing additional events may continue. For example, if in step 534, the service monitor obtains additional indications of hovering events of the pointing device over other trip segment icons, the service monitor causes the display device to display a corresponding message indicating the corresponding status of the onboard service provided during the corresponding trip segment.

[0233] 6.3. Interactive flight metrics viewer with service performance related features

[0234] Fig. 6A is an example process for generating and displaying one or more indicator flight viewers having service performance related features according to one or more embodiments. The steps of process 602 to 614 may be performed by the control circuit system of the device for monitoring network communication services onboard the vehicle, and / or at least in part by a ground communication service monitoring server (such as described in detail above). Figure 1 Ground system 112 or Figure 2 The ground system 200) is used.

[0235] In some implementations, the device that performs some or all of steps 602 to 614 may be part of a ground server configured to monitor network communication services for multiple vehicles. In the following examples, it is assumed that these steps are performed by Figure 2 The service monitor 202 shown in FIG.

[0236] In some implementations, the example process may include, for example, Figure 2 Steps 608 to 610 performed by the service monitor 202 of the ground system 220 shown in FIG. Figure 2 602 to 606 and 612 to 614 are performed by the display device 214 of the ground system 220 shown in FIG. In some other implementations, steps 602 to 614 may be performed by Figure 2 Other components of the ground system 200 shown in FIG. Figure 3 Some components of the onboard system 350 shown in FIG.

[0237] In step 602, the service monitor causes the display device to display a map viewer including a map of the geographic area. FIG. 4D to FIG. 4E An example of a map viewer is described in .

[0238] In step 604, the service monitor causes the display device to display one or more trip segment icons corresponding to one or more trip segments of the flight path of the trip of the vehicle and corresponding to one or more time intervals of the time period of the trip in the map viewer's geographic area map. FIG. 4D to FIG. 4E Examples of paths are described in .

[0239] In step 606, the service monitor causes the display device to display a flight indicator viewer having one or more viewer segment icons corresponding to one or more time intervals of the time period and corresponding to one or more viewer segments of the flight indicator viewer. In the flight indicator viewer, each viewer segment icon has a viewer feature that represents a corresponding status of an onboard service provided during a corresponding time interval in the one or more time intervals of the time period of the trip. FIG. 4D to FIG. 4E Examples of viewer segment icons are described in .

[0240] In step 608, the service monitor determines whether an indication of a hover event of the pointing device over a first trip segment icon of the one or more trip segment icons of the map viewer or a first viewer segment icon of the one or more viewer segment icons of the flight indicators viewer is obtained at a particular time within the time period. FIG. 4D to FIG. 4E An example of a hover event is described in .

[0241] If, in step 610, the service monitor determines that an indication of a hover event of the pointing device over a first trip segment icon of the one or more trip segment icons of the map viewer or a first viewer segment icon of the one or more viewer segment icons of the flight indicators viewer has been obtained at a particular time within the time period, the service monitor proceeds to step 612. Otherwise, the service monitor continues testing at step 608.

[0242] In step 612, the service monitor causes the display device to display a first visual marker in the map viewer, the first visual marker overlying a first trip segment icon corresponding to a first time interval including the specific time at the specific time. FIG. 4D to FIG. 4E An example of a first mark visualized as a large black dot is described in .

[0243] In step 614, the service monitor causes the display device to display a second visual marker in the map viewer while displaying the first visual marker in the flight indicator viewer, the second visual marker overlying the first viewer segment icon corresponding to the first time interval including the specific time at the specific time. FIG. 4D to FIG. 4E An example of a second visual indicia visualized as a vertical bar is described in .

[0244] 6.4. Flight Indicator Viewer Interactivity

[0245] Figure 6B are example processes for generating and displaying one or more metrics flight viewers having service performance related features triggered by hover events in accordance with one or more embodiments.

[0246] In some implementations, the device performing steps 622 to 630 may be part of a ground server configured to monitor network communication services for multiple vehicles. In the following example, it is assumed that these steps are performed by Figure 2 The service monitor 202 shown in FIG.

[0247] In step 622, the service monitor determines whether a hovering event of the pointing device over a first trip segment icon among the one or more trip segment icons of the map viewer or a first viewer segment icon among the one or more viewer segment icons of the flight indicator viewer is obtained at a specific time within the time period. FIG. 4D to FIG. 4E An example of a hover event is described in .

[0248] If, in step 624, the service monitor determines that a hover event of the pointing device over a first trip segment icon of the one or more trip segment icons of the map viewer or a first viewer segment icon of the one or more viewer segment icons of the flight indicators viewer has been obtained at a particular time within the time period, the service monitor proceeds to step 626. Otherwise, the service monitor performs a test in step 622.

[0249] In step 626, the service monitor causes the display device to display a first message in the map viewer, the first message overlaying the first trip segment icon corresponding to the first time interval including the specific time and indicating a corresponding first status of the onboard service provided at the specific time of the time period of the trip of the vehicle. FIG. 4D to FIG. 4E Examples of messages are described in .

[0250] In step 628, the service monitor causes the display device to display a first visual indicia in the map viewer while displaying a second message in the flight indicators viewer that overlays the first viewer segment icon corresponding to the first time interval that includes the specific time and indicates a corresponding second status of a specific type of onboard service and is provided at the specific time of the time period of the vehicle's trip. FIG. 4D to FIG. 4E Examples of messages are described in .

[0251] The process of testing additional events may continue. For example, if in step 630, the service monitor obtains additional indications of hover events of the pointing device over other trip segment icons, the service monitor causes the display device to display a corresponding message in the map viewer indicating the corresponding status of the onboard service provided during the corresponding trip segment while displaying the first visual marker in the map viewer.

[0252] 7.0. Hardware Implementation

[0253] According to some implementations of the present method, the techniques described herein are implemented by at least one computer system. These techniques may be implemented in whole or in part using at least one server computer or a combination of other computer systems coupled using a network such as a packet data network. The computer system may be hardwired to perform these techniques, or may include digital electronics, such as at least one application specific integrated circuit (ASIC) or field programmable gate array (FPGA) that is permanently programmed to perform these techniques, or may include at least one general purpose hardware processor that is programmed to perform these techniques according to program instructions in firmware, memory, other storage devices, or combinations thereof. Such computer systems may also combine custom hardwired logic, ASICs, or FPGAs with custom programming to accomplish the described techniques.

[0254] The computer system may be a server computer, a workstation, a personal computer, a portable computer system, a handheld device, a mobile computing device, a wearable device, a body-mounted or implantable device, a smartphone, a smart appliance, a networked device, an autonomous or semi-autonomous device (such as a robot) or an unmanned ground or aerial vehicle, any other electronic device incorporating hardwired or program logic to implement the described techniques, one or more virtual computing machines or instances in a data center, or a network of server computers or personal computers.

[0255] Figure 7 is a block diagram illustrating an example computer system in which some implementations may be implemented. Figure 7 In the example of FIG. 7 , computer system 700 and instructions for implementing the disclosed techniques in hardware, software, or a combination of hardware and software are schematically represented as, for example, boxes and circles, with the same level of detail that ordinary technicians in the field of the present disclosure typically use to convey computer architectures and computer system implementations.

[0256] Computer system 700 includes an input / output (I / O) subsystem 702, which may include a bus or other communication mechanism for transferring information or instructions between components of computer system 700 via electronic signal paths. I / O subsystem 702 may include an I / O controller, a memory controller, and at least one I / O port. Electronic signal paths are schematically represented in the figures as, for example, lines, unidirectional arrows, or bidirectional arrows.

[0257] At least one hardware processor 704 is coupled to the I / O subsystem 702 for processing information and instructions. The hardware processor 704 may include, for example, a general purpose microprocessor or microcontroller or a dedicated microprocessor such as an embedded system or a graphics processing unit (GPU) or a digital signal processor or an ARM processor. The processor 704 may include an integrated arithmetic logic unit (ALU) or may be coupled to a separate ALU.

[0258] The computer system 700 includes one or more units of memory 706, such as main memory, coupled to the I / O subsystem 702 for electronically digitally storing data and instructions to be executed by the processor 704. The memory 706 may include volatile memory, such as various forms of random access memory (RAM) or other dynamic storage devices. The memory 706 may also be used to store temporary variables or other intermediate information during the execution of instructions by the processor 704. When stored in a non-transitory computer-readable storage medium accessible to the processor 704, such instructions may cause the computer system 700 to become a special-purpose machine that is customized to perform the operations specified in the instructions.

[0259] Computer system 700 further includes non-volatile memory, such as read-only memory (ROM) 708, or other static storage, coupled to I / O subsystem 702 for storing information and instructions for processor 704. ROM 708 may include various forms of programmable ROM (PROM), such as erasable PROM (EPROM) or electrically erasable PROM (EEPROM). Units of permanent storage 710 may include various forms of non-volatile RAM (NVRAM), such as flash memory or solid-state storage devices, magnetic disks or optical disks, such as CD-ROM or DVD-ROM, and may be coupled to I / O subsystem 702 for storing information and instructions. Storage 710 is an example of a non-transitory computer-readable medium that may be used to store instructions and data that, when executed by processor 704, cause execution of a computer-implemented method to perform the techniques herein.

[0260] The instructions in the memory 706, ROM 708 or storage device 710 may include one or more groups of instructions organized as modules, methods, objects, functions, routines or calls. The instructions may be organized as one or more computer programs, operating system services or applications including mobile applications. The instructions may include an operating system or system software; one or more libraries to support multimedia, programming or other functions; data protocol instructions or stacks to implement TCP / IP, HTTP or other communication protocols; file processing instructions to interpret and present files encoded using HTML, XML, JPEG, MPEG or PNG; user interface instructions to present or interpret commands for a GUI (GUI), command line interface or text user interface; application software such as an office suite, an Internet access application, a design and manufacturing application, a graphics application, an audio application, a software engineering application, an educational application, a game or a variety of applications. The instructions may implement a network server, a network application server or a network client. The instructions may be organized into a presentation layer, an application layer and a data storage layer, such as a relational database system using structured query language (SQL) or NoSQL, an object storage device, a graph database, a flat file system or other data storage device.

[0261] The computer system 700 may be coupled to at least one output device 712 via the I / O subsystem 702. In some implementations, the output device 712 is a digital computer display. Examples of displays that may be used in some implementations include a touch screen display or a light emitting diode (LED) display or a liquid crystal display (LCD) or an electronic paper display. As an alternative to or in addition to a display device, the computer system 700 may include other types of output devices 712. Examples of other output devices 712 include a printer, a receipt printer, a plotter, a projector, a sound card or video card, a speaker, a buzzer or piezoelectric device or other auditory device, a light or LED or LCD indicator, a tactile device, an actuator, or a servo mechanism.

[0262] At least one input device 714 is coupled to I / O subsystem 702 for communicating signals, data, command selections, or gestures to processor 704. Examples of input device 714 include a touch screen, a microphone, still and video digital cameras, alphanumeric and other keys, a keypad, a keyboard, a graphics tablet, an image scanner, a joystick, a clock, a switch, a button, a dial, a slider, or various types of sensors such as force sensors, motion sensors, thermal sensors, accelerometers, gyroscopes, and inertial measurement unit (IMU) sensors or various types of transceivers such as wireless transceivers such as cellular or Wi-Fi, radio frequency (RF) or infrared (IR) transceivers, and global positioning system (GPS) transceivers.

[0263] Another type of input device is a control device 716, which can perform cursor control or other automatic control functions, such as navigating in a GUI on a display screen as an alternative to or in addition to the input function. The control device 716 can be a touch pad, a mouse, a trackball, or cursor direction keys for transmitting direction information and command selections to the processor 704 and for controlling cursor movement on the display 712. The input device can have at least two degrees of freedom on two axes (a first axis (e.g., x) and a second axis (e.g., y)), which allows the device to specify a position in a plane. Another type of input device is a wired, wireless, or optical control device, such as a joystick, a stick, a console, a steering wheel, a pedal, a gear shift mechanism, or other type of control device. The input device 714 may include a combination of multiple different input devices, such as a camera and a depth sensor.

[0264] In some implementations, the computer system 700 may include an Internet of Things (IoT) device in which one or more of the output device 712, the input device 714, and the control device 716 are omitted. In some implementations, the input device 714 may include one or more cameras, motion detectors, thermometers, microphones, earthquake detectors, other sensors or detectors, measuring devices, or encoders, and the output device 712 may include a dedicated display such as a single-line LED or LCD display, one or more indicators, display panels, meters, valves, solenoids, actuators, or servo mechanisms.

[0265] When the computer system 700 is a mobile computing device, the input device 714 may include a global positioning system (GPS) receiver coupled to a GPS module capable of triangulating a plurality of GPS satellites to determine and generate a geographic location or location data, such as latitude and longitude values ​​for the geophysical location of the computer system 700. The output device 712 may include hardware, software, firmware, and interfaces for generating a location report packet, notification, pulse or heartbeat signal directed to the host computer 724 or server 730, or other cyclic data transport specifying the location of the computer system 700, either alone or in combination with other application-specific data.

[0266] The computer system 700 may implement the techniques described herein using custom hardwired logic, at least one ASIC or FPGA, firmware or program instructions or logic that, when loaded and used or executed in conjunction with a computer system, cause the computer system or programmed computer system to operate as a special purpose machine. According to some implementations, the computer system 700 performs the techniques described herein in response to the processor 704 executing at least one sequence of at least one instruction contained in the main memory 706. Such instructions may be read into the main memory 706 from another storage medium (such as a storage device) 710. Execution of the sequence of instructions contained in the main memory 706 causes the processor 704 to perform the process steps described herein. In some implementations, hardwired circuitry may be used in place of or in combination with software instructions.

[0267] The term "storage media" as used herein refers to any non-transitory media that stores data or instructions that cause a machine to operate in a particular manner. Such storage media may include non-volatile media or volatile media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 710. Volatile media include dynamic memory, such as memory 706. Common forms of storage media include, for example, hard disks, solid-state drives, flash drives, magnetic data storage media, any optical or physical data storage media, memory chips, etc.

[0268] Storage media are distinct from, but may be used in conjunction with, transmission media. Transmission media participate in the transmission of information between storage media. For example, transmission media include coaxial cables, copper wire, and optical fiber, including wires that comprise the bus of I / O subsystem 702. Transmission media may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

[0269] Various forms of media may be involved in carrying at least one sequence of at least one instruction to the processor 704 for execution. For example, the instructions may initially be carried by a disk or solid-state drive of a remote computer. The remote computer may load the instructions into its dynamic memory and send the instructions using a modem over a communication link such as an optical fiber or coaxial cable or a telephone line. A modem or router local to the computer system 700 may receive data on the communication link and convert the data for reading by the computer system 700. For example, a receiver such as a radio frequency antenna or an infrared detector may receive data carried in a wireless or optical signal, and appropriate circuitry may provide the data to the I / O subsystem 702, such as placing the data on a bus. The I / O subsystem 702 carries the data to the memory 706, from which the processor 704 retrieves and executes the instructions. The instructions received by the memory 706 may optionally be stored on the storage device 710 before or after being executed by the processor 704.

[0270] The computer system 700 also includes a communication interface 718 coupled to the bus 702. The communication interface 718 provides a two-way data communication coupled to a network link 720, which is directly or indirectly connected to at least one communication network, such as a network 722 or a public or private cloud on the Internet. For example, the communication interface 718 can be an Ethernet network interface, an integrated services digital network (ISDN) card, a cable modem, a satellite modem, or a modem to provide a data communication connection to a corresponding type of communication line (e.g., an Ethernet cable or any kind of metal cable or fiber optic line or telephone line). The network 722 broadly represents a local area network (LAN), a wide area network (WAN), a campus network, the Internet, or any combination thereof. The communication interface 718 may include a LAN card to provide a data communication connection to a compatible LAN, or a cellular radiotelephone interface for wired transmission or reception according to a cellular radiotelephone wireless network standard, or a satellite radio interface for wired transmission or reception of digital data according to a satellite wireless network standard. In any such implementation, the communication interface 718 sends and receives electrical, electromagnetic, or optical signals through a signal path that carries digital data streams representing various types of information.

[0271] The communication interface 718 may be based on interconnection technology used in distributed computing systems, supercomputer systems, and high-performance computing systems. For example, the communication interface 718 may be based on OMNI-PATH, INFINIBAND, ARIES, NVLINK, TOFU, or Ethernet.

[0272] Network link 720 typically provides electrical, electromagnetic, or optical data communication to other data devices directly or through at least one network using, for example, satellite, cellular, Wi-Fi, or Bluetooth technology. For example, network link 720 may provide a connection to host computer 724 via network 722.

[0273] Additionally, network link 720 may provide connectivity through network 722 or to other computing devices via interconnected devices or computers operated by Internet Service Provider (ISP) 726. ISP 726 provides data communication services through the global packet data communication network represented as Internet 728.

[0274] The server computer 730 may be coupled to the Internet 728. The server 730 broadly represents any computer, data center, virtual machine, or virtual computing instance with or without a hypervisor, or a computer executing a containerized program system such as DOCKER or Kubernetes. The server 730 may represent an electronic digital service implemented using more than one computer or instance, and access and use the electronic digital service by sending a network service request, a uniform resource locator (URL) string with parameters in the HTTP payload, an API call, an application service call, or other service call. The computer system 700 and the server 730 may form an element of a distributed computing system, which includes other computers, processing clusters, server farms, or other computer organizations that collaborate to perform tasks or execute applications or services. The server 730 may include one or more groups of instructions organized as modules, methods, objects, functions, routines, or calls. The instructions may be organized as one or more computer programs, operating system services, or applications including mobile applications. The instructions may include an operating system or system software; one or more libraries to support multimedia, programming or other functions; data protocol instructions or stacks to implement TCP / IP, HTTP or other communication protocols; file format processing instructions to interpret or present files encoded using HTML, XML, JPEG, MPEG or PNG; user interface instructions to present or interpret commands for a GUI command line interface or a text user interface; application software such as an office suite, an Internet access application, a design and manufacturing application, a graphics application, an audio application, a software engineering application, an educational application, a game or a variety of applications. The server 730 may include a network application server that hosts a presentation layer, an application layer, and a data storage layer, such as a relational database system using structured query language (SQL) or NoSQL, an object storage device, a graph database, a flat file system, or other data storage device.

[0275] Computer system 700 may send messages and receive data and instructions, including program code, through the network, network link 720, and communication interface 718. In the example of the Internet, server 730 may send requested code for an application program through Internet 728, ISP 726, local network 722, and communication interface 718. The received code may be executed by processor 704 as it is received, or stored in storage device 710 or other non-volatile storage for later execution.

[0276] The execution of the instructions described in this section may implement a process in the form of an instance of a computer program being executed, and includes the program code and its current activity. Depending on the operating system (OS), a process may consist of multiple threads of execution that execute instructions concurrently. In this case, a computer program is a passive collection of instructions, and a process may be the actual execution of these instructions. Several processes may be associated with the same program; for example, opening several instances of the same program generally means that more than one process is being executed. Multitasking may be implemented to allow multiple processes to share the processor 704. Although each processor 704 or core of a processor executes a single task at a time, the computer system 700 may be programmed to implement multitasking to allow each processor to switch between the tasks being executed without having to wait for each task to complete. In some implementations, switching may be performed when a task performs an input / output operation, when a task indicates that it can be switched, or when a hardware interrupt occurs. By quickly performing context switching to provide the appearance of multiple processes executing in parallel at the same time, time sharing may be implemented to allow fast response of interactive user applications. In some implementations, for security and reliability, the operating system may prevent direct communication between independent processes, thereby providing a strictly mediated and controlled inter-process communication function.

[0277] 8.0. General Considerations

[0278] Although some of the various figures may show multiple logical stages in a particular order, stages that are not dependent on order may be reordered, and other stages may be combined or decomposed. Although some reordering or other groupings may be specifically mentioned, other reorderings or other groupings will be apparent to one of ordinary skill in the art, and thus the orderings and groupings given herein are not an exhaustive list of alternatives. In addition, it should be appreciated that the stages may be implemented in hardware, firmware, software, or any combination thereof.

[0279] The foregoing description has been described with respect to specific embodiments for purposes of explanation. However, the above illustrative embodiments are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. In view of the above teachings, many modifications and variations are possible. The embodiments are selected in order to best explain the principles underlying the claims and their practical application, thereby enabling others skilled in the art to best utilize the embodiments with various modifications that are suitable for the intended use.

[0280] In the foregoing specification, embodiments of the method have been described with reference to numerous specific details that may vary from implementation to implementation. Accordingly, the specification and drawings are to be regarded as illustrative rather than restrictive. The sole and exclusive indicator of the scope of the method, and what the applicant intends as an indicator of the scope of the method, is the literal and equivalent range of the set of claims issuing from this application, in the specific form in which such claims issue, including any subsequent amendment.

[0281] Any definitions herein for terms contained in the claims shall govern the meaning of those terms as used in the claims. No limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of the claim in any way. The specification and drawings are to be regarded as illustrative rather than restrictive.

[0282] As used herein, the terms "include" and "comprise" (and variations of these terms, such as "including, includes", "comprising, comprises", etc.) are intended to be inclusive and are not intended to exclude further features, components, integers or steps.

[0283] References to "embodiments" herein indicate that the described or illustrated embodiments may include certain features, structures, or characteristics, but not every embodiment necessarily includes the certain features, structures, or characteristics. Such phrases do not necessarily refer to the same embodiment. In addition, when a certain feature, structure, or characteristic is described or illustrated in conjunction with an embodiment, whether or not explicitly stated, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments.

[0284] Various features of the present disclosure have been described using process steps. The function / processing of a given process step may be performed in different ways and by different systems or system modules. In addition, a given process step may be divided into multiple steps and / or multiple steps may be combined into a single step. In addition, the order of the steps may be changed without departing from the scope of the present disclosure.

[0285] It should be understood that the embodiments disclosed and defined in this specification extend to alternative combinations of the corresponding features and components mentioned or evident from the text or drawings. These different combinations constitute various alternative aspects of the embodiments.

[0286] The attached claims and their equivalents are intended to cover such forms or modifications that fall within the scope and spirit of protection. For example, the various components shown in the figures can be implemented as software and / or firmware on a processor, ASIC / FPGA or dedicated hardware. In addition, the features and attributes of the specific embodiments disclosed above can be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure. Although the present disclosure provides certain preferred embodiments and applications, other embodiments that are obvious to those of ordinary skill in the art (including embodiments that do not provide all the features and advantages set forth herein) are also within the scope of the present disclosure. Therefore, the scope of the present disclosure is intended to be defined only by reference to the attached claims.

[0287] The methods and processes described herein may be implemented in software code modules executed by one or more general and / or special computers, and may be partially or fully automated. The term "module" may refer to logic contained in hardware and / or firmware, or a collection of software instructions that may have entry and exit points, written in a programming language such as C or C++. Software modules may be compiled and linked into executable programs, installed in dynamic link libraries, or may be written in interpretive programming languages ​​such as BASIC, Perl, or Python. It should be understood that software modules may be called from other modules or themselves, and / or may be called in response to detected events or interrupts. Software instructions may be embedded in firmware, such as an erasable programmable read-only memory (EPROM). "Module" may further refer to one or more devices, components, systems, or subsystems that may conceptually implement related functions. It should be further understood that hardware modules may be composed of connected logic units (such as gates and triggers) and / or may be composed of programmable units (such as programmable gate arrays, application-specific integrated circuits, and / or processors). The modules described herein are preferably implemented as software modules, but may also be represented by hardware and / or firmware. Additionally, while in some implementations a module may be compiled separately, in other embodiments a module may represent a subset of instructions of a separately compiled program and may not have interfaces available to other logical program units.

[0288] ________________________________________________

Claims

1. A method for visualizing an interactive transportation route having service performance related features, the method include: displaying (502) a map viewer including a map of a geographic area on a display device; obtaining (504) a transportation path for a trip of a vehicle, wherein the transportation path includes one or more trip segments within the map of the geographic area, each trip segment having a corresponding trip segment start location and a corresponding trip segment end location along the transportation path; obtaining (506) a corresponding status of an onboard service provided during each corresponding trip segment of the one or more trip segments of the trip of the vehicle; for each corresponding one of the one or more trip segments, obtaining (508) a corresponding one of the one or more trip segment icons, each trip segment icon having a feature representing the corresponding status of the onboard service provided during the corresponding trip segment; and The one or more trip segment icons corresponding to the one or more trip segments are displayed ( 510 ) in the map viewer, wherein each of the one or more trip segment icons is positioned according to the corresponding trip segment start position and the corresponding trip segment end position of the corresponding trip segment. 2 . The method of claim 1 , wherein the corresponding status of the onboard service provided during the corresponding trip segment in the one or more trip segments comprises aggregated information about the onboard service provided during the corresponding trip segment.

3. The method of claim 2 , wherein the aggregate information about the inflight services provided during the corresponding trip segment comprises aggregate information about one or more of: an in-flight entertainment (IFE) service, an in-flight connectivity (IFC) service, an IFE session service, a Wi-Fi connection service, a Wi-Fi session service, a TV service, a TV session service, a data session service, a promotional session service, an email service, or a text message service. 4 . The method of claim 1 , wherein the feature is represented using one or more of: a shape, a color, a pattern, a shading, a dashed line, a broken line, or a color pattern.

5. The method according to claim 1, further comprising: include: obtaining ( 522 ) a first indication of a first hover event of a pointing device over a first trip segment icon of the one or more trip segment icons; In response to obtaining the first indication of the first hover event: displaying ( 526 ) a first message in the map viewer at a first location adjacent to the first trip segment icon, the first message indicating a corresponding first status of an onboard service provided during a first trip segment corresponding to the first trip segment icon; as well as obtaining (528) a second indication of a second hover event of the pointing device over a second trip segment icon of the one or more trip segment icons; In response to obtaining the second indication of the second hover event: removing the first message from the map viewer, and A second message is displayed (532) in the map viewer at a second location adjacent to the second trip segment icon, the second message indicating a corresponding second status of an onboard service provided during a second trip segment corresponding to the second trip segment icon. 6 . The method of claim 1 , wherein each of the one or more trip segments is displayed as a segment overlay on top of the map of the geographic area.

7. The method according to claim 1, wherein the transportation path of the trip of the vehicle has a trip start location and a trip end location; the method further include: determining a trip start location icon corresponding to the trip start location of the trip and displaying the trip start location icon as a starting overlay on a map of the geographic area in the map viewer at the trip start location along the transportation path; as well as An end-of-trip location icon is determined that corresponds to the end-of-trip location of the trip and is displayed in the map viewer as an end overlay on a map of the geographic area at the end-of-trip location along the transportation path.

8. A device for visualizing an interactive transport path with service performance related features, the device include: processor, a memory in electronic communication with the processor; as well as Instructions stored in the memory and executable by the processor to cause the processor to perform the following operations: displaying (502) a map viewer including a map of a geographic area on a display device; obtaining (504) a transportation path for a trip of a vehicle, wherein the transportation path includes one or more trip segments within the map of the geographic area, each trip segment having a corresponding trip segment start location and a corresponding trip segment end location along the transportation path; obtaining (506) a corresponding status of an onboard service provided during each corresponding trip segment of the one or more trip segments of the trip of the vehicle; for each corresponding one of the one or more trip segments, obtaining (508) a corresponding one of the one or more trip segment icons, each trip segment icon having a feature representing the corresponding status of the onboard service provided during the corresponding trip segment; and The one or more trip segment icons corresponding to the one or more trip segments are displayed ( 510 ) in the map viewer, wherein each of the one or more trip segment icons is positioned according to the corresponding trip segment start position and the corresponding trip segment end position of the corresponding trip segment. 9 . The apparatus of claim 8 , wherein the corresponding status of the onboard service provided during the corresponding trip segment of the one or more trip segments comprises aggregated information about the onboard service provided during the corresponding trip segment.

10. The apparatus of claim 9, wherein the aggregate information about the inflight services provided during the corresponding trip segment comprises aggregate information about one or more of: an in-flight entertainment (IFE) service, an in-flight connectivity (IFC) service, an IFE session service, a Wi-Fi connection service, a Wi-Fi session service, a TV service, a TV session service, a data session service, a promotional session service, an email service, or a text message service.

11. The apparatus of claim 8, wherein the feature is represented using one or more of: a shape, a color, a pattern, a shading, a dashed line, a broken line, or a colored pattern.

12. The apparatus of claim 8 storing additional instructions for: obtaining (522) a first indication of a first hover event of a pointing device over a first trip segment icon of the one or more trip segment icons; In response to obtaining the first indication of the first hover event: displaying (526) a first message in the map viewer at a first location adjacent to the first trip segment icon, the first message indicating a corresponding first status of an onboard service provided during a first trip segment corresponding to the first trip segment icon ； as well as obtaining (528) a second indication of a second hover event of the pointing device over a second trip segment icon of the one or more trip segment icons; In response to obtaining the second indication of the second hover event: removing the first message from the map viewer, and A second message is displayed (532) in the map viewer at a second location adjacent to the second trip segment icon, the second message indicating a corresponding second status of an onboard service provided during a second trip segment corresponding to the second trip segment icon.

13. The apparatus of claim 8, wherein each of the one or more trip segments is displayed as a segment overlay on top of the map of the geographic area.

14. The apparatus of claim 8, wherein the transport path of the trip of the vehicle has a trip start location and a trip end location; wherein the device stores additional instructions for: determining a trip start location icon corresponding to the trip start location of the trip, and displaying the trip start location icon as a starting overlay on a map of the geographic area in the map viewer at the trip start location along the transportation path; An end-of-trip location icon is determined that corresponds to the end-of-trip location of the trip and is displayed in the map viewer as an end overlay on a map of the geographic area at the end-of-trip location along the transportation path.

15. One or more non-transitory computer-readable storage media storing computer code for visualizing an interactive transportation path having service performance related features, the computer code comprising instructions that, when executed by a processor, cause the processor to: displaying (502) a map viewer including a map of a geographic area on a display device; obtaining (504) a transportation path for a trip of a vehicle, wherein the transportation path includes one or more trip segments within the map of the geographic area, each trip segment having a corresponding trip segment start location and a corresponding trip segment end location along the transportation path; obtaining (506) a corresponding status of an onboard service provided during each corresponding trip segment of the one or more trip segments of the trip of the vehicle; for each corresponding one of the one or more trip segments, obtaining (508) a corresponding one of the one or more trip segment icons, each trip segment icon having a feature representing the corresponding status of the onboard service provided during the corresponding trip segment; and The one or more trip segment icons corresponding to the one or more trip segments are displayed ( 510 ) in the map viewer, wherein each of the one or more trip segment icons is positioned according to the corresponding trip segment start position and the corresponding trip segment end position of the corresponding trip segment.

16. The one or more non-transitory computer-readable storage media of claim 15, wherein the corresponding status of the onboard services provided during the corresponding trip segment in the one or more trip segments comprises aggregated information about the onboard services provided during the corresponding trip segment.

17. One or more non-transitory computer-readable storage media according to claim 16, wherein the aggregate information about the inflight services provided during the corresponding trip segment includes aggregate information about one or more of the following: in-flight entertainment (IFE) service, in-flight connectivity (IFC) service, IFE session service, Wi-Fi connection service, Wi-Fi session service, TV service, TV session service, data session service, promotional session service, email service or SMS service.

18. The one or more non-transitory computer-readable storage media of claim 15, wherein the feature is represented using one or more of: a shape, a color, a pattern, a shading, a dashed line, a broken line, or a colored pattern.

19. The one or more non-transitory computer-readable storage media of claim 15 storing additional instructions for: obtaining (522) a first indication of a first hover event of a pointing device over a first trip segment icon of the one or more trip segment icons; In response to obtaining the first indication of the first hover event: displaying (526) a first message in the map viewer at a first location adjacent to the first trip segment icon, the first message indicating a corresponding first status of an onboard service provided during a first trip segment corresponding to the first trip segment icon ； as well as obtaining (528) a second indication of a second hover event of the pointing device over a second trip segment icon of the one or more trip segment icons; In response to obtaining the second indication of the second hover event: removing the first message from the map viewer, and A second message is displayed (532) in the map viewer at a second location adjacent to the second trip segment icon, the second message indicating a corresponding second status of an onboard service provided during a second trip segment corresponding to the second trip segment icon.

20. The one or more non-transitory computer-readable storage media of claim 15, wherein each of the one or more trip segments is displayed as a segment overlay on top of the map of the geographic area.

21. The one or more non-transitory computer-readable storage media of claim 15, wherein the transportation path of the trip of the vehicle has a trip start location and a trip end location; wherein the one or more non-transitory computer-readable storage media store additional instructions for: determining a trip start location icon corresponding to the trip start location of the trip, and displaying the trip start location icon as a starting overlay on a map of the geographic area in the map viewer at the trip start location along the transportation path; An end-of-trip location icon is determined that corresponds to the end-of-trip location of the trip and is displayed in the map viewer as an end overlay on a map of the geographic area at the end-of-trip location along the transportation path.

22. The method according to claim 5, further comprising: include: determining whether an outage event occurred during at least the first trip segment of the trip based on a quality of an onboard communication service delivered by the vehicle during the first trip segment corresponding to the first trip segment icon; as well as In response to determining that the interruption event occurred during at least the first trip segment of the trip: determining a time interval during which the interruption event occurs; as well as Information about the interruption event and the time interval of the interruption event is included in the first message.

23. The method of claim 22, wherein the event comprises one of: out of coverage, jammed, transmission inhibited, and no aircraft data bus.

24. The apparatus of claim 12 storing additional instructions for: determining whether an outage event occurred during at least the first trip segment of the trip based on a quality of an onboard communication service delivered by the vehicle during the first trip segment corresponding to the first trip segment icon; In response to determining that the interruption event occurred during at least the first trip segment of the trip: determining a time interval during which the interruption event occurs; as well as Information about the interruption event and the time interval of the interruption event is included in the first message.

25. The apparatus of claim 24, wherein the event comprises one of: out of coverage, jammed, transmission inhibited, and no aircraft data bus.

26. The one or more non-transitory computer-readable storage media of claim 19 storing additional instructions for: determining whether an outage event occurred during at least the first trip segment of the trip based on a quality of an onboard communication service delivered by the vehicle during the first trip segment corresponding to the first trip segment icon; In response to determining that the interruption event occurred during at least the first trip segment of the trip: determining a time interval during which the interruption event occurs; as well as Information about the interruption event and the time interval of the interruption event is included in the first message.

27. The one or more non-transitory computer-readable storage media of claim 26, wherein the interruption event comprises one of: out of coverage, blocking, transmission inhibit, and no aircraft data bus.

Images