Network Requirements for the Metaverse

I’ve often joked that I don’t play computer games because I’m holding out for a holodeck. While that may sound ridiculously far-future, we’re on the verge of seeing web-based virtual reality that will be a major step towards a holodeck. There is already some awesome virtual reality software and games where a person can get immersed in another world using a headset. But it will be a big leap to move virtual reality online where people from anywhere can join in a game together like is done in the movie Ready Player One. If you haven’t seen it, it’s a movie from 2018 about a believable future worldwide gaming phenomenon.

Meta (formerly Facebook) is investing heavily in creating a platform that can host game designers and others to launch virtual reality apps. When Meta first announced that it was going to tackle the metaverse, people assumed the company was off designing games, but the company is instead tackling the technology that will enable the use of online virtual reality.

Meta says there are some key requirements that will be needed to support the metaverse.

  • Fast symmetrical broadband speeds. And they aren’t just talking about one gigabit bandwidth – faster speeds will be needed to transmit the huge amounts of data needed to create real-time virtual reality worlds.
  • Low latency, under 10 milliseconds. Well-designed last-mile fiber networks have speeds in this range today. But Meta isn’t talking only about the last mile network, but the middle mile network used to connect users to the cloud. The company says that middle-mile carriers will need to step up their game. Some networks are already this fast, but many are not.
  • We’re going to need higher resolution video – 4K is not good enough resolution to convey the pixels needed to create immersive worlds. And that means big data files.
  • With big data files, we’re going to need the next generation of video compression that can compress huge data files in real-time and that can be decompressed without adding delay to the signal.
  • To make everything work together in real-time will require cooperation in the network between entities. Some traffic optimization is done today by network operators while content providers do their own optimization – it’s going to take a coordinated real-time integrated process of network optimization that includes all parties to the metaverse.
  • Metaverse software must be able to adapt to the user. While designed for a high-bandwidth, low latency fiber customer, the metaverse system must be able to adapt to the local network conditions. We do this in a minor way today when Netflix dummies down the video signal to match a user’s bandwidth.
  • What Meta didn’t way is that we’ll need ISPs willing to deliver the fast 2-way traffic needed to make the metaverse work in homes.

This may all sound out of reach, but Meta already has early prototypes of the concepts working in the lab. We’re seeing last-mile fiber builders now using XGS-PON that can deliver 10-gigabit symmetrical broadband. We’re seeing new middle-mile routes with 300-gigabit pipes reaching out to smaller and smaller cities.

The metaverse and web-based virtual reality will only become possible when there are enough people in the world connected to a fast fiber connection. We’re certainly on that path in the U.S. with plans for various ISPs to build fiber to pass nearly 50 million more homes in just the next few years. Meta envisions a platform where it supplies the muscles and tens of thousands of develops independently create metaverse worlds. That’s not quite a holodeck – but I might just give it a try.

One thought on “Network Requirements for the Metaverse

  1. Great post as always. What you don’t include here is the in-home network requirements. This is a distinctly different network than the one serving the home. The user experience, and therefore the perception of the network and application experience, is dependent on ubiquitous symmetrical distribution of capacity throughout the home as well as low latency.

Leave a Reply