SIST ETS 300 777-2 E1:2003

• Abstract:

  This ETS will specify a subset of ISO/IEC 13816-6 (DSM-CC) for basic multimedia applications using MHEG-5. The subset will encompass DSM-CC User-User (U-U) primitives for communication between client and server. It will include a mapping of MHEG-5 to DSM-CC. Note: DSM-CC is a session layer protocol covering establishment and management of end-to-end sessions. Basic multimedia applications include (eg, as defined by DAVIC) Television distribution, near Video on Demand, Video on Demand and Teleshopping.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.160.60 - Multimedia systems and teleconferencing equipment
• ICS: 35.180 - IT Terminal and other peripheral equipment
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 777-2 ed.1 (1998-12) - Terminal Equipment (TE); End-to-end protocols for multimedia information retrieval services; Part 2: Use of Digital Storage Media Command and Control (DSM-CC) for basic multimedia applications

SIST ETS 300 777-2 E1:2003 is the Slovenian standard identical with ETS 300 777-2 Edition 1, published by SIST. It specifies a Digital Storage Media Command and Control (DSM-CC) profile for basic multimedia applications using MHEG-5. The document is aimed at DAVIC 1.2-compliant systems that need interoperable session control, object access, and Java VM-based application interfaces.

What does SIST ETS 300 777-2 E1:2003 specify?

SIST ETS 300 777-2 E1:2003 specifies a subset of ISO/IEC 13818-6 DSM-CC for basic multimedia applications. The focus is the DSM-CC User-User (U-U) interface for communication between client and server, plus a mapping of MHEG-5 to DSM-CC.

The document is organized into a short standards-style structure: foreword, scope, normative references, definitions and abbreviations, an overview, the org.etsi.dsmccuu package, an example, and history. In practice, that means the standard first explains the interoperability model and then defines the Java package that software uses to reach DSM-CC services.

Basic multimedia applications are given as television distribution, near Video on Demand, Video on Demand, and teleshopping. That matters because the standard is aimed at service delivery and terminal behavior for these service types, not at generic multimedia coding.

What are the key requirements of SIST ETS 300 777-2 E1:2003?

SIST ETS 300 777-2 E1:2003 is mainly an interface definition for interoperable multimedia terminals. The key points are the required interchange format, the Java API set, and the object and session operations exposed in org.etsi.dsmccuu.

• Clause 1 limits the profile to basic multimedia applications and says it applies to DAVIC 1.2-compliant systems. In practice, implementers use this standard when they are building or checking compatibility with the DAVIC environment.
• Clause 4.1 says applications shall use the MHEG-5 final form interchange format to deliver multimedia information to Set Top Units (STUs), and shall use the ASN.1 notation and encoding defined by ETS 300 777-1 for MHEG-5 objects. This means terminal software must exchange objects in the prescribed MHEG-5 form, rather than inventing its own object syntax.
• Clause 4.1 also says program code shall be carried in the MHEG-5 InterchangedProgram class as Java Virtual Machine (VM) code, and Java VM classes shall be encoded according to the Class File Format section of the Java Virtual Machine specification. In practice, this is the bridge between presentation objects and executable code.
• Clause 4.2 names the core Java APIs used by DAVIC 1.2 code: java.lang, java.util, org.iso.mheg5, org.etsi.dsmccuu, and org.etsi.dvbsi. That tells developers which packages they can rely on for basic runtime, MHEG-5 control, DSM-CC access, and Service Information (SI).
• Clause 5 defines the org.etsi.dsmccuu package for DSM-CC User-to-User access. The package includes object types for names, bindings, sessions, directories, files, streams, and service gateways, so implementers can navigate services and access content through a common Java API.
• The Base and Access interfaces provide common lifecycle and locking functions. Base.close() releases an object reference when access is no longer needed, while Access.getLock() and Access.setLock() expose read and write lock attributes, which matters for shared object handling.
• The Stream class defines stream control operations such as pause, resume, getPosition, getScale, getMode, reset, jump, and play, with stream modes like OPEN, PAUSE, TRANSPORT, and END_OF_STREAM. In practice, this is how a terminal tells a video server when to start, stop, seek, or change rate.
• The File class defines read, getContent, setContent, and write, using offsets, sizes, and lock-related exceptions. That gives applications controlled access to file-like content and helps them handle size limits, offset errors, and lock conflicts.
• The Directory class supports browsing and name resolution through list, resolve, open, get, and close, with path types DEPTH and BREADTH. This is what a service browser uses to find streams, files, and directories in a service tree.
• The Session, ServiceGateway, and First classes support session setup and teardown. Session.attach() establishes a session context, ServiceGateway.detach() disconnects from a gateway and session objects, and First.root() and First.service() return object references for the current session. That is the control path for entering and leaving a DSM-CC service environment.

What terms does SIST ETS 300 777-2 E1:2003 define?

API (Application Programming Interface) - A boundary across which software uses programming-language facilities to invoke services and manipulate shared objects.

DAVIC (Digital Audio Visual Council) - The interoperability framework referenced by the standard for basic multimedia systems.

DSM-CC (Digital Storage Media Command and Control) - A session-layer protocol for establishing and managing end-to-end sessions.

MHEG-5 - The multimedia and hypermedia interchange format used for delivering objects and invoking actions in this standard.

STU (Set Top Unit) - The terminal device that receives and runs the multimedia service and Java VM code.

VM (Virtual Machine) - The Java runtime environment whose class files are used to carry executable code.

Who uses SIST ETS 300 777-2 E1:2003?

SIST ETS 300 777-2 E1:2003 is used by terminal equipment designers, middleware developers, and service providers working on DAVIC 1.2-compatible multimedia systems. It is also relevant to quality managers and buyers who need to check whether a product supports the MHEG-5 to DSM-CC mapping and the required Java packages.

In practice, the standard supports teams that implement STU software, service browsing, stream control, file access, and session attachment or detachment. It fits equipment for television distribution, near Video on Demand, Video on Demand, and teleshopping services.

What changed in SIST ETS 300 777-2 E1:2003 from the previous edition?

SIST ETS 300 777-2 E1:2003 identifies itself as identical with ETS 300 777-2 Edition 1.

Which standards are used with SIST ETS 300 777-2 E1:2003?

• DAVIC 1.2 specifications - define the application framework in which this profile is used.
• ISO/IEC 13818-6 (1996) - provides DSM-CC extensions and the core consumer client application portability interface referenced for org.etsi.dsmccuu.
• ISO/IEC 13522-5 (1997) - defines MHEG-5 base-level interactive applications and the final form interchange format used for multimedia objects.
• ISO/IEC 13522-6 (1996) - defines enhanced interactive applications and the MHEG-5 InterchangedProgram class used to carry Java VM code.
• ETS 300 777-1 - defines ASN.1 notation and encoding for MHEG-5 objects.
• ETS 300 777-3 - defines the org.iso.mheg5 Java API for accessing and manipulating MHEG-5 presentation and interaction objects.

What does the SIST ETS 300 777-2 E1:2003 document contain?

SIST ETS 300 777-2 E1:2003 is mostly an API reference for DSM-CC-based multimedia terminals. It defines class and interface signatures, constants, method parameters, and the exceptions that methods may raise.

Clause 5 contains the package org.etsi.dsmccuu with object types for names, bindings, streams, files, directories, sessions, service gateways, and session entry points. It also defines many exception classes for naming errors, authorization problems, locking conflicts, size and offset problems, and stream delivery or timing errors.

Clause 6 gives an informational usage example. The example shows how to attach to a service gateway, browse or resolve directory entries, read a file, resume a stream, close a service, and detach while optionally saving context.

SLOVENSKI STANDARD
01-december-2003
Terminalska oprema (TE) – Protokoli sistema konec-konec za multimedijske
informacijske poiskavne storitve – 2. del: Uporaba ukaznih in krmilnih funkcij pri
digitalnih pomnilnih nosilcih (DSM-CC) za osnovne multimedijske aplikacije
Terminal Equipment (TE); End-to-end protocols for multimedia information retrieval
services; Part 2: Use of Digital Storage Media Command and Control (DSM-CC) for
basic multimedia applications
Ta slovenski standard je istoveten z: ETS 300 777-2 Edition 1
ICS:
33.160.60 9HþSUHGVWDYQLPXOWLPHGLMVNL Multimedia systems and
VLVWHPLLQRSUHPD]D teleconferencing equipment
WHOHNRQIHUHQFH
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 777-2
TELECOMMUNICATION December 1998
STANDARD
Source: MTA Reference: DE/MTA-011057-2
ICS: 33.020
Key words: API, MHEG, multimedia, terminal
Terminal Equipment (TE);
End-to-end protocols for multimedia information
retrieval services;
Part 2: Use of Digital Storage Media Command and Control
(DSM-CC) for basic multimedia applications
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

Page 2
ETS 300 777-2: December 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 777-2: December 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Overview .8
4.1 The DAVIC application interchange format .8
4.2 Core set of Java APIs .8
5 Package org.etsi.dsmccuu.9
5.1 Class NameComponent.9
5.2 Class Binding.9
5.3 Exception NOT_FOUND.9
5.4 Exception CANNOT_PROCEED .10
5.5 Exception INV_NAME.10
5.6 Exception SERVICE_XFR .10
5.7 Exception dsmccuuException.11
5.8 Exception INV_OFFSET.11
5.9 Exception INV_SIZE .11
5.10 Exception READ_LOCKED .11
5.11 Exception WRITE_LOCKED .12
5.12 Exception OPEN_LIMIT.12
5.13 Exception NO_AUTH.12
5.14 Exception UNK_USER.12
5.15 Exception BAD_COMPAT_INFO.12
5.16 Exception NO_RESUME .13
5.17 Exception NO_SUSPEND .13
5.18 Exception MPEG_DELIVERY.13
5.19 Exception BAD_SCALE.13
5.20 Exception BAD_START.13
5.21 Exception BAD_STOP.14
5.22 Interface Base.14
5.23 Interface Access .14
5.24 Class Stream .15
5.25 Class File .17
5.26 Class BindingIterator.19
5.27 Class Directory.20
5.28 Class Session .21
5.29 Class ServiceGateway.22
5.30 Class First.22
6 Example .23
History.28

Page 4
ETS 300 777-2: December 1998
Blank page
Page 5
ETS 300 777-2: December 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terminal Equipment (TE)
Technical Committee and later the Multimedia Terminals and Applications (MTA) Project of the European
Telecommunications Standards Institute (ETSI).
This ETS consists of 4 parts as follows:
Part 1: "Coding of multimedia and hypermedia information for basic multimedia applications
(MHEG-5)";
Part 2: "Use of Digital Storage Media Command and Control (DSM-CC) for basic multimedia
applications";
Part 3: "Application Programmable Interface (API) for MHEG-5";
Part 4: "Videotex Enhanced Man Machine Interface (VEMMI) enhancements to support broadband
multimedia information retrieval services".
Transposition dates
Date of adoption of this ETS: 4 December 1998
Date of latest announcement of this ETS (doa): 31 March 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 1999
Date of withdrawal of any conflicting National Standard (dow): 30 September 1999

Page 6
ETS 300 777-2: December 1998
Blank page
Page 7
ETS 300 777-2: December 1998
1 Scope
This European Telecommunication Standard (ETS) specifies a profile of Digital Storage Media Command
and Control (DSM-CC) for the use in basic multimedia applications. This ETS is applicable to Digital Audio
Visual Council (DAVIC), version 1.2, compliant systems.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
references are cited at the appropriate places in the text and the publications are listed hereafter. For
dated references, subsequent amendments to or revisions of any of these publications apply to this ETS
only when incorporated in it by amendment or revision. For undated references the latest edition of the
publication referred to applies.
[1] DAVIC 1.2 specifications.
[2] ISO/IEC 13818-6 (1996): "Information technology; Generic coding of moving
pictures and associated audio information; Part 6: Extensions for DSM-CC".
[3] ISO/IEC 13522-5 (1997): "Information technology; Coding of multimedia and
hypermedia information; Part 5: Support for base-level interactive applications".
[4] ISO/IEC 13522-6 (1996): "Information technology; Coding of multimedia and
hypermedia information; Part 6: Support for enhanced interactive applications".
[5] ETS 300 777-1: "Terminal Equipment (TE); End-to-end protocols for multimedia
information retrieval services; Part 1: Coding of multimedia and hypermedia
information for basic multimedia applications (MHEG-5)".
[6] ETS 300 777-3: "Terminal Equipment (TE); End-to-end protocols for multimedia
information retrieval services; Part 3: Application Programmable Interface (API)
for MHEG-5".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the definition of the standards referenced below apply. Should any
ambiguity occur, definitions of the following standards apply, in decreasing order:
- ISO/IEC 13818-6 (1996) [2];
- DAVIC 1.2 specifications [1].
Application Programmable Interface (API): A boundary across which a software application uses
facilities of programming languages to invoke software services. These facilities may include procedures
or operations, shared data objects and resolution of identifiers.
local application: A piece of software which is part of the (telecommunication) application and is running
on the considered equipment.
Page 8
ETS 300 777-2: December 1998
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
API Application Programming Interface
ASN.1 Abstract Syntax Notation One
DAVIC Digital Audio Visual Council
DSM-CC Digital Storage Media Command and Control
MHEG Multimedia and Hypermedia information coding Experts Group
SI Service Information
STU Set Top Unit
VM Virtual Machine
4 Overview
This clause positions the API defined by this ETS in the framework of the DAVIC 1.2 specifications [1].
4.1 The DAVIC application interchange format
To deliver multimedia information to Set Top Units (STUs) in an interoperable way, applications shall use
the Multimedia and Hypermedia information coding Experts Group (MHEG-5) final form interchange
format, as defined by ISO/IEC 13522-5 [3]. The ASN.1 notation and encoding, as defined by
ETS 300 777-1 [5], shall be used to interchange MHEG-5 objects. This format defines the semantics and
the encoding of the multimedia and hypermedia objects.
To deliver program code to STUs in an interoperable way, applications shall use the MHEG-5
InterchangedProgram class to encapsulate Java (note) Virtual Machine (VM) code, according to the
semantics and encoding defined by ISO/IEC 13522-6 [4]. Java VM classes are called from MHEG-5
objects using the MHEG-5 Call and Fork elementary actions.
NOTE: Java is a trademark of Sun Microsystems, Inc.
The Java VM code interchange unit is a Java VM class. Java VM classes shall be encoded as defined by
the Class File Format section of the Java Virtual Machine specification. A Java class encapsulates data
and methods that consist of sequences of instructions. The instruction set is defined by the Java Virtual
Machine instruction set section of the Java Virtual Machine specification.
4.2 Core set of Java APIs
The following set of APIs are used by Java VM code in the DAVIC 1.2 specifications [1] to express access
to basic functions of the STU in an interoperable way:
- the java.lang package;
- the java.util package;
- the org.iso.mheg5 package;
- the org.etsi.dsmccuu package;
- the org.etsi.dvbsi package.
NOTE 1: The Java VM specification provides flexible mechanisms to call upon external
functions whose interface is defined as a Java package. The DAVIC 1.2
specification [1] only includes a minimum core set of packages required for Java VM
code to be useful in a DAVIC environment. It is anticipated that additional Java
packages will be standardized at a later stage.
NOTE 2: Especially, the java.io package, although strictly speaking not necessary to the useful
performance of the VM environment, is part of the Java foundation classes. It is
intended that the java.io package be added to the DAVIC core set of Java APIs
together with an adequate specification of its semantics in a DAVIC environment.
The java.lang package, as defined by the Java API documentation, consists of the minimal set of Java
VM classes needed to run Java VM code, supporting the following functionality: basic data types, object,
mathematic operations, security, thread management, string manipulation, exception handling.

Page 9
ETS 300 777-2: December 1998
java.util
The package, as defined by the Java API documentation, consists of Java VM classes
supporting a number of utility features common to all Java VM programs.
The org.iso.mheg5 package, as defined by ETS 300 777-3 [6], provides Java VM code with access to
and manipulation of the MHEG-5 multimedia presentation and interaction objects, i.e. access to the
dynamic attributes of MHEG-5 objects and invocation of elementary actions on MHEG-5 objects.
The org.etsi.dsmccuu package enables Java VM code to use the DSM-CC User-to-User (U-U)
interface objects for network data access. It gives access to the Core Consumer Client Application
Portability Interface as defined by ISO/IEC 13818-6 [2].
org.etsi.dvbsi
The package enables Java VM code to access information transmitted in the DAVIC
Service Information (SI) stream.
5 Package org.etsi.dsmccuu
5.1 Class NameComponent
/**
This class represents a name component composed of an id and a kind
*/
package org.davic.net.dsmcc.uu;
public class NameComponent{
public java.lang.String id;
public java.lang.String kind;
}
5.2 Class Binding
/**
This class represents a binding composed of a name and a type
*/
package org.davic.net.dsmcc.uu;
public class Binding{
/**
Possible values for the binding type
*/
public static final byte OBJECT = 0;
public static final byte NAMING_CONTEXT = 1;
public NameComponent[] name;
public int type;
}
5.3 Exception NOT_FOUND
/**
This exception is thrown when a logical path name does not exist
*/
package org.davic.net.dsmcc.uu;
public class NOT_FOUND
extends
java.lang.Exception{
/**
Possible values for the exception reason
*/
public static final byte MISSING_NODE = 0;

Page 10
ETS 300 777-2: December 1998
public static final byte NOT_A_NAMING_CONTEXT = 1;
public static final byte NOT_AN_OBJECT = 2;
public byte why;
public NameComponent[] restOfName;
}
5.4 Exception CANNOT_PROCEED
/**
This exception is thrown when a Directory does not have permission to resolve
a node in a path name
The caller may attempt to perform the resolve directly at the returned
Directory
*/
package org.davic.net.dsmcc.uu;
public class CANNOT_PROCEED
extends
java.lang.Exception{
public Directory directory;
public NameComponent[] restOfName;
}
5.5 Exception INV_NAME
/**
This exception is thrown when a path name is incorrectly formatted
*/
package org.davic.net.dsmcc.uu;
public class INV_NAME
extends
java.lang.Exception{
}
5.6 Exception SERVICE_XFR
/**
This exception is thrown when a resolve operation was unsuccessful and
provides an alternate Service Domain when the requested Service can be
resolved
*/
package org.davic.net.dsmcc.uu;
public class SERVICE_XFR
extends
java.lang.Exception{
public byte[] serviceDomain;
public NameComponent[] pathName;
public byte[] initialContext;
}
SIST ETS 300 777-2 E1:
...