Interfaces for service requests in a balloon network
Example embodiments may relate to web interfaces for a balloon-network. For example, a computing device may display a graphical interface that that includes one or more interface features to receive a request for use of bandwidth of a balloon network. In particular, the computing device may receive, via the graphical interface, input data corresponding to a bandwidth request for a first location, where the bandwidth request includes: (i) an indication of the first location and (ii) an indication of time. Subsequently, the computing device may receive an indication corresponding to whether or not the bandwidth request is accepted, where acceptance of the bandwidth request is based at least in part on expected movement of one or more balloons from a plurality of balloons in the balloon network. As such, the computing device may display, on the graphical interface, the indication corresponding to whether or not the bandwidth request is accepted.
1. A method, comprising:
obtaining, by one or more processors of a computing device, state information associated with a set of high altitude platforms (HAPs) configured to operate in the stratosphere, the state information including link information for one or more communication links of the set of HAPs;
identifying, by the one or more processors, a particular geographic location associated with service by one or more HAPs of the set of HAPs, the particular geographic location being part of a coverage area for the set of HAPs;
identifying, by the one or more processors, variation of one or more performance measures associated with the link information, the one or more performance measures including a latency measure; and
generating for display on at least one display device, by the one or more processors based on the state information and the particular geographic location, a map interface including a performance measure visualization including information to illustrate the latency measure.
2. The method of claim 1 , wherein the map interface is configured to illustrate geographic areas associated with the particular geographic location where the latency measure falls within different latency ranges or levels.
3. The method of claim 2 , wherein the latency measure includes a one-way latency or a round-trip latency.
4. The method of claim 1 , wherein the map interface is configured to indicate one or more latency levels that are expected in one or more geographic areas associated with the particular geographic location at a future time.
5. The method of claim 4 , wherein expectation of the one or more latency levels is associated with movement of the one or more HAPs of the set of HAPs in the stratosphere.
6. The method of claim 1 , wherein the map interface is configured to indicate one or more latency levels that are occurring in one or more geographic areas associated with the particular geographic location at a current time.
7. The method of claim 1 , wherein the map interface is configured to indicate one or more historical latency levels that have occurred in one or more geographic areas associated with the particular geographic location.
8. The method of claim 1 , further comprising receiving a quality of service request from a user for the particular geographic location.
9. The method of claim 8 , wherein the quality of service request is a request for latency reduction.
10. The method of claim 1 , wherein the one or more performance measures further include information about throughput, and the performance measure visualization further includes information to illustrate the throughput.
11. The method of claim 1 , wherein the one or more performance measures further include information about jitter, and the performance measure visualization further includes information to illustrate the jitter.
12. The method of claim 1 , wherein the one or more performance measures further include information about errors, and the performance measure visualization further includes information to illustrate the errors.
13. The method of claim 1 , wherein generating the map interface including the performance measure visualization including information to illustrate the latency measure is based on a predicted state of the set of HAPs at a future time.
14. The method of claim 13 , wherein the state of the set of HAPs is predicted, at least in part, based on one or more of historical information, bandwidth service requests, event reporting, information received from one or more client devices, or fleet-planning decisions for the set of HAPs.
15. The method of claim 14 , wherein the historical information includes information for the particular geographic location during at least one of (i) different times of a particular day, (ii) different times of a particular month, or (iii) different times of year.
16. The method of claim 13 , wherein predicting the state of the set of HAPs is further based on an expected future position of one or more client devices remote from the set of HAPs.
17. The method of claim 16 , wherein predicting the state of the set of HAPs includes determining whether a selected client device of the one or more client devices will be present in at least a portion of the particular geographic location at the future point in time.
18. The method of claim 1 , wherein generating the map interface is done using a moving window of time for the performance measure visualization.
19. The method of claim 18 , wherein the moving window of time is selected according to dynamic movement of the one or more HAPs of the set of HAPS through the coverage area.
20. The method of claim 18 , wherein the moving window of time is based on speeds of the one or more HAPs relative to the ground.