Going to the Metaverse? Tune up Your Network and Edge Infrastructure
summary
Metaverse workloads force latency under 10 ms ( ≈600 miles max), with VR at 7–15 ms and tactile at 1 ms; VR needs ~250 Mbps, holograms demand terabits/sec. Open projects expose service APIs—Kamara’s quality‑on‑demand and edge‑resource location APIs—and Akrino provides edge blueprints that place rendering and hardware acceleration near users. Demos include Telefonica Microsoft and Apple for remote surgery and Deutsche Telecom Orange and Mitsuko for holographic calls showing API-driven reservations and Edge placement actually reducing jitter and improving perceived quality.
AI-written summary · about
chapters (10)
- 0:00Metaverse network challenges
- 1:12Metaverse use cases
- 3:19Network latency and edge computing
- 7:39Decentralized infrastructure model
- 9:29App-network integration via APIs
- 12:48Kamara project APIs
- 15:39Remote maintenance and XR
- 18:09Cranio edge blueprints
- 20:19Open source for metaverse
- 21:00Key takeaways
related talks
17mPath to Metaverse-ready Networks
14mThinking Point: The Metaverse and the evolving connectivity requirements
22mHow 5G and Edge Compute Will Enable Pervasive AR Experiences
13mCloud XR Experience on 5G with Mobile Edge Networks
58mNew solutions leveraging Verizon’s 5G network
19mPowering Immersive Technologies
19mKeynote: Network of Tomorrow - 5G and Edge
44mHow 5G Edge is being used to solve customer problems