Table of Contents
1Scope
2Normativereferences
3Definitions
4Abbreviations
5Overview
5.1Userapplication
5.2ApplicationProtocolEntity
5.3ApplicationResourceManager
5.4ApplicationServiceElement
6GenericApplicationTemplate
6.1Initialization
6.2Enrollment
6.2.1Registrationsession
6.2.2Standardbasesession
6.2.3Non-standardbasesession
6.2.4Publicsession
6.2.5Privatesession
6.3Formingregistrykeys
6.4Capabilitynegotiation
6.5Leavingasession
7ReviewofMCSresourcesandGCCservices
7.1Channels
7.1.1Staticchannel
7.1.2Dynamicchannel
7.1.3UserIDchannel
7.1.4AssignedChannel
7.1.5Privatechannel
7.1.6PotentialproblemswiththeuseofMCS
channels
7.1.7Summary
7.2Datatransfer
7.3Tokens
7.3.1Statictokens
7.3.2Dynamictokens
7.4Applicationroster
7.5Applicationregistry
7.6Conductorship
7.7Remoteinvoking
8Userapplicationguidelines
8.1Identificationofuserapplications
8.2Useofcollapsingandnon-collapsingcapabilities
8.3Sessioncontext
8.4Selectingasessiontoparticipatein
8.5Controllingtheuseofasession
8.6Addingnewparticipantstoasession
8.7Extension,modificationandreuseofapplication
protocols Abstract
Provides guidance for application developers and application protocol developers on the correct and effective use of the T.120 infrastructure. It provides a generic model for an application that communicates using T.120 services and defines a Generic Application Template specifying the use of T.122 (MCS) and T.124 (GCC) services that are commonly required by application protocols making use of T.120 services.
