next up previous contents
Next: Summary Up: Distributed Virtual Reality Previous: Application Model

The Distributed Virtual Reality Multicast Protocol, DVRMP

DVRMP runs on top of RTP[#!rtp!#] and UDP. All DVRMP messages are multicast. As in Parnes' proposal, we use RTP data packets as is, for data. If reliability is needed, the RTP PT field is used to indicate SRM, otherwise it simply conveys normal data.


 
Table 8.1: RTP Header
\begin{table}\begin{tex2html_preform}\begin{verbatim}0 1 2 3
0 1 2 3 4 5 6 7 8 ...
...-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\end{verbatim}\end{tex2html_preform}
\end{table}

The SSRC is the source VR application. the CSRC can be used for input from specific devices.

We use RTCP as is for session quality reports, and respect the PARNES protocol for reliability:


 
Table 8.2: RTP and SRM
\begin{table}\begin{tex2html_preform}\begin{verbatim}SRM RTCP Packet:0 1 2 3
...
...=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+\end{verbatim}\end{tex2html_preform}
\end{table}

More than one multicast group is used. Session messages are used within one multicast group to advertise the existence of participants and objects. Objects have owners. At any one time, the owner is the source of the session messages about an object.

Messages can be marked as reliable or not reliable, however, this is not binding on recipients. Recipients can operate the repair algorithm on reliable object messages in the normal way. Other messages are deemed ephemeral, and can be lost (or discarded) at will8.5.


next up previous contents
Next: Summary Up: Distributed Virtual Reality Previous: Application Model
Jon CROWCROFT
1998-12-03