A new industry alliance led by Alphabet’s Loon high-altitude balloon technology company and SoftBank’s HAPSMobile stratospheric glider subsidiary aims to work together on standards and tech related to deploying network connectivity using high-altitude delivery mechanisms.
This extends the existing partnership between HAPSMobile and Loon, which began with a strategic alliance between the two announced last April, and which recently resulted in Loon adapting the network hardware it uses on its stratospheric balloons to work with the HAPSMobile stratospheric long-winged drone. Now, they two are welcoming more members, including AeroVironment, Airbus Defence and Space, Bharti Airtel, China Telecom, Deutsche Telekom, Ericsson, Intelsat, Nokia, HAPSMobile parent SoftBank and Telefonica.
The new HAPS Alliance, as it’s being called (HAPS just stands for ‘High Altitude Platform Station’) will be working together to promote use of the technology, as well as work with regulators in the markets where they operate on enabling its use. They’ll work towards developing a set of common industry standards for network interoperability, and also figure how to essentially carve up the or stake out the stratosphere so that participating industry players can work together without stepping on each other’s toes.
This new combined group is no slouch: It includes some of the most powerful network operators in the world, as well as key network infrastructure players and aerospace companies. Which could mean big things for stratospheric networks, which have the advantages of being closer to Earth than satellite-based internet offerings, but also avoid the disadvantages of ground-based cell towers like having to deal with difficult terrain or more limited range.
Is this the first step towards a future where our connected devices rely on high-flying, autonomous cell towers for connectivity? It’s too early to say how ubiquitous this will get, but this new group of heavyweights definitely lends more credence to the idea.
from TechCrunch https://ift.tt/32eeSk5
via IFTTT
No comments:
Post a Comment