Sceye's stratospheric cell served unmodified handsets over SoftBank's core network

Nothing had to be installed on the phone. Sceye says the standard devices it served over Japan reached SoftBank's core network unmodified ^[3]. For a carrier that removes the two slowest parts of standing up a new access layer, device certification and a firmware campaign. What is left belongs to the core network team and to whoever holds the spectrum grant.

Work the 68 milliseconds backwards. Sceye and SoftBank report an average round-trip processing response of 68 ms onboard the platform and a latency cut of more than 40 percent against internet-based cloud processing ^[13]. Divide 68 by 0.6 and the baseline they measured against was at least about 113 ms ^[15]. The account does not say where that cloud endpoint sat or what the workload was, so the comparison is the partners' own ^[12].

Frandsen's own account is warmer than the flight profile. "Groundbreaking and historic only begin to describe our ST1 flight," said Mikkel Vestergaard Frandsen, Sceye's founder and chief executive ^[8]. He said the mission "proved not only that our technology, vehicle systems, payload, and operational infrastructure are ready for connectivity services" ^[9]. The mission was named Service Test 1, and it ended with a planned termination and descent near Moriarty on September 5 ^[1][4]. The account gives no figure for how many devices were served at once or how much spectrum the test used, and it does not say how many consecutive days the platform held station over Japan ^[12]. Sceye says its vehicles hold altitude and area of operation through consecutive day and night cycles, operating like geostationary satellites at 1,800 times closer to Earth ^[10].

"Designed to", "at full scale": that is the wording on the 500-tower coverage figure, and it is a target rather than a measurement taken from ST1 ^[6]. The follow-up question for anyone writing a resilience plan around it is how fast a second airframe reaches station. ST1 took 13 days to fly from New Mexico to Japan ^[2].

Two questions decide whether any of this belongs in a network plan next year: whether the gap being filled is coverage or capacity, and whether the need is continuous or episodic. The tested evidence sits in one of those four boxes. Sceye ran emergency calls through an alert messaging system built for large-scale disasters, and tested links to drones ^[7], which is episodic coverage over a wide area. For continuous coverage of a populated area, the deciding number is consecutive days on station per airframe, and until that is published the honest place for a HAPS in a plan is a standby contract.