- What the tools are: reference tools for conversational avatars using MPEG ARF (ISO/IEC 23090-39) in a real-time call: a Unity call application, reference ARF content and a sample OpenXR tracker.
- What this covers: the call application (rt-avatar-call) as the AR-MTSI avatar client, judged against ETSI TS 26.264 V19.4.1 (Conversational Avatar Communication). Judged on the
mainbranch of each repository on 2026-10-22. - Not covered: the AR AS, the AR media function and the Base Avatar Repository have no code in any of the repositories, so their requirements are shown as not implemented. Cases that rest on ISO/IEC 23090-39, the MPEG_node_avatar extension of ISO/IEC 23090-14 and the IETF avatar RTP payload draft, which were not available, are not shown.
- Source of this page: every requirement is split into the cases its clause defines; each case was read against the code by one reader and then independently by a second, with a third reading where they disagreed.
For what ARF and the call procedures define, see the Technology page and the Standards. For how to run the tools, see the Tutorials and the Developer Exchange.
What the Reference Tools implement
- Call application (rt-avatar-call): a WebRTC call, signalled through SWAP, that carries audio and avatar animation. The animation units travel on a data channel with the
3gpp-ar-animationsub-protocol, ordered and reliable. The receiving side applies them to the avatar; the avatar is loaded from a local file by a third-party ARF package. A webcam producer based on MediaPipe face landmarks generates the animation, and it is built only when that option is enabled. - AR metadata: the
3gpp-ar-metadatadata channel is created, but the application sends no AR metadata over it, so metadata and rendering negotiation are not implemented. - Negotiation and signalling: there is no IMS avatar call, no scene description, no
MPEG_node_avataruse, no Base Avatar Repository access and no avatar negotiation; the client writes no avatar SDP attributes, and the compatibility check between the avatar and the animation producers is local only. - Network roles: the AR AS, the media function and the Base Avatar Repository (with its Mbar_Management API) are not implemented in any repository.
- Reference content and tracker: rt-avatar-content holds ARF content and rt-avatar-unity-tracker holds the sample tracker; neither implements a specification requirement by itself.
Implementation status
Open a feature, then a requirement, to see each case and why. Filter by component and release.
- Conversational Avatars with MPEG ARF.
- AR-MTSI client (AR-MTSI client (avatar call in the user equipment: animation, ARF avatar loading, data channel)): rt-avatar-call.
- AR AS (AR AS (IMS application server for avatar calls; none exists)): .
- MF (MF (media function for network animation and rendering; none exists)): .
- BAR (BAR (Base Avatar Repository and Mbar_Management service; none exists)): .
- Source: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group; cases that rest on documents not obtained are not shown, 2026-10-22.
- Not shown: 3 further cases (it could not be settled by reading the code; the sentence states no behaviour a component could meet).
✓ Implemented≠ Differs from the specification– Absent? Specification inconsistent: its text and its OpenAPI or tables disagreei Noted: observed, not a verdict against a clauseScene placement via MPEG-I Scene Description6 of 70 implemented · 64 absent
The ARF data model1 of 70 implemented · 1 differs · 68 absent
Interfaces and interoperability4 of 189 implemented · 185 absent
End-to-end procedure7 of 82 implemented · 1 differs · 74 absent
General0 of 18 implemented · 18 absent
The full audit, with the code behind each verdict, is available to 5G-MAG members through Developer Tools.
Related
- XR Media & 3D Scenes: the scene framework that ARF is designed to work with