MMEC

Mobile Metaverse Enablement Client

Services →
Introduced in Rel-8

MMEC is a client-side entity that enables immersive metaverse experiences over mobile networks by managing extended reality sessions and coordinating with the network for quality of service and edge computing.

Category
Services
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
4 specs
MMEC Description Purpose Detected Changes Specifications

Description

The Mobile Metaverse Enablement Client (MMEC) is a functional entity residing within the User Equipment (UE) or an associated application, designed to facilitate metaverse and advanced Extended Reality (XR) services over 3GPP mobile networks. Its primary role is to act as an intelligent intermediary between the immersive application and the network, translating application requirements into network service requests. The MMEC is responsible for session management, including the establishment, modification, and termination of metaverse sessions, which are characterized by demanding requirements for ultra-high bandwidth, ultra-low latency, and high reliability. It interfaces with core network functions, such as the Policy Control Function (PCF) and Session Management Function (SMF), to negotiate and secure the necessary Quality of Service (QoS) flows and network resources. This ensures that the data streams for rendering, audio, and haptic feedback are delivered with the appropriate priority and performance guarantees.

Architecturally, the MMEC interacts with both the application layer and the 3GPP protocol stack. It consumes application-level requirements, such as required frame rate, resolution, and motion-to-photon latency, and maps these to specific network parameters. It utilizes service-based interfaces, potentially leveraging capabilities like Network Exposure Functions (NEF), to communicate its needs to the network core. A key component of its operation is the ability to request edge computing resources. For metaverse applications, processing often needs to be offloaded to Multi-access Edge Computing (MEC) platforms to reduce end-to-end latency. The MMEC can initiate procedures for User Plane Function (UPF) selection and traffic steering towards the optimal application server instance at the network edge.

Furthermore, the MMEC plays a vital role in mobility and session continuity. As a user moves, the client must work with the network to ensure seamless handovers without degrading the immersive experience, potentially triggering network-controlled handovers based on application state. It also handles aspects of security and privacy, ensuring that user data and biometric information used in XR sessions are protected according to network policies. In essence, the MMEC abstracts the complexity of the underlying 3GPP network from the metaverse application, providing a standardized way to harness advanced network capabilities like network slicing, edge computing, and precise QoS management to deliver consistent and high-quality immersive experiences.

Purpose & Motivation

The MMEC was created to address the fundamental mismatch between the extreme performance requirements of the metaverse and the traditional best-effort nature of mobile data services. Prior to its conceptualization, immersive XR applications had to operate over generic data connections, struggling with latency spikes, jitter, and insufficient bandwidth, leading to poor user experiences like motion sickness and broken immersion. The rise of the metaverse, encompassing social interaction, gaming, training, and digital twins, demanded a new paradigm where the network is an active, aware participant in the service delivery.

The technology was motivated by the need for a standardized, network-aware client that could dynamically negotiate service requirements. Without such a client, each metaverse application would have to implement proprietary and non-interoperable methods to interact with different network operators, stifling ecosystem growth. The MMEC provides a common abstraction layer, enabling application developers to specify 'intent' (e.g., 'immersive AR session') rather than low-level network commands. This allows operators to optimize their resources using tools like network slicing, where a dedicated slice with guaranteed performance can be instantiated for an MMEC session. Its creation is a direct response to the industry's shift towards service-based architectures and network programmability, aiming to unlock new revenue streams from premium XR services.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 1 change

In Release 15, the MMEC function introduced enhanced support for mobile terminated services during unreachable states, leveraging the existing High Latency Communication functions for data buffering. It also integrated with the Service Gap timer mechanism to manage mobile originated signaling peaks from a large number of UEs. Furthermore, it provided specific handling for low access priority indications in mobile originated NAS signaling to allow for network protective measures.

  • EPS mobile identity and UE status in the ATTACH REQUEST message TS 24.301CR3028
Rel-18 1 change

In Release 18, the MMEC function introduced a correction to the determination of the mobile reachable timer based on the user plane, specifically aligning its start with the start of the user plane activity. This adjustment ensures more accurate reachability management for UEs in ECM-IDLE state, particularly when applying NAS-level mobility management congestion control, where the timer values may need to be modified.

  • Correction to determination of periodic timer, mobile reachable timer based on UP and start of UP TS 24.301CR3996
Rel-19 2 changes

In Release 19, the MMEC function introduced new capabilities for managing network congestion by allowing the MME to adjust the mobile reachable timer and the implicit detach timer when applying General NAS level Mobility Management Congestion Control. This adjustment provides the network with a mechanism to control the signaling load from UEs in ECM-IDLE state during congestion events. The change specifically enables the MME to modify these timers dynamically, rather than relying solely on static values derived from the UE's periodic TAU timer.

  • The adjustment of mobile reachable timer or the implicit detach timer TS 24.301CR4343
  • Correction to the mobile reachable timer TS 24.301CR4656

Explore further

Broader topics and technologies where MMEC plays a role.

Defining Specifications

3GPP specifications that define or reference MMEC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8