DSMCC P
ROTOCOLS
AND
I
NTERFACES
As revised 2006.05.04
Bionic Buffalo Tech Note #55
Security:
Unrestricted
DSM::LifeCycle
may be inherited by any instantiable interface. It has a single operation,
create()
, which returns a persistent, interoperable object reference (IOR) for the object upon which
the operation is called.
DSM::Security
may be inherited by any instantiable interface. It has a single operation,
authenticate()
, which allows a client to provide credentials which might be necessary to gain
access to the target object.
DSM::State
may be inherited by any instantiable interface. It includes two operations:
suspend()
requests that the object return its state with respect to the client and suspend operations, and
resume()
requests that the object resume operations using the given state.
13. Encapsulation of DSMCC Protocols
The five UN protocols (configuration, session, download, channel change, and passthrough) may be
positioned above some other datagram transport protocol. Minimum requirements for the transport
protocol are:
•
error detection must be provided (as with a CRC remainder or similar mechanism)
•
messages with errors may simply be discarded, and lost message detection is not necessary
•
no control over the rate of transmission is required
•
if messages are fragmented by the transport layer during transmission, then they must be
reassembled by the transport layer
•
messages may be delivered out of sequence
The RPC (by default, GIOP) protocol used determines the necessary characteristics of the transport layer
required for the RPC protocol. Typically, this is a reliable, guaranteed transport such as TCP/IP.
Any or all DSMCC protocols may be encapsulated within MPEG2 transport streams. The specification
details the mechanisms to be used in that case. A description of such encapsulation is beyond the scope
of this Tech Note.
14. DSMCC Extensibility and Variations
All DSMCC message formats and protocols allow considerable extensibility.
The five UN protocols employ these main mechanisms:
•
the messages include private data areas, whose syntax and semantics are left to the implementor
Copyright 2006 Bionic Buffalo. All rights reserved.
File tn0055; Modified 20060505 12:45:42
http://www.tatanka.com/doc/technote/index.html
Email: query@tatanka.com
Page 18 of 20