dministration function (Client component), in charge of handling the exchange of service management information with the DCD Server. The Content Reception and Storage Management function, in charge of handling the content reception from the server. The Client Application Interaction Function that provides the necessary functions to make possible the interaction between DCD Enabler supported services and registered DCD Enabled Client Applications. DCD Server implements the application level network functionality for the DCD application. It is composed of two logical functions: The Subscription and Administration function is in charge of handling the exchange of service man- agement information between the DCD Server and DCD Client, and between the DCD Server and the Content Provider, such as when the Content Provider handles subscriptions. The Distribution and Adaptation function distributes DCD Content and DCD Content notifications to the DCD Client. The two non-DCD players shown in Figure 9.32 are Content Providers and DCD-Enabled Client Appli- cation. DCD-Enabled Client Applications are mobile-terminal-based applications, which can consume con- tent delivered via the DCD Enabler, for example, presenting the content to users, or using it for any arbitrary purpose. DCD-Enabled Client Applications interact with the DCD Enabler either via DCD- CADE or DCD-CAR. The DCD-CADE is the interface for data exchange (for e.g., for requesting content and receiving delivered content). The DCD-CAR is the interface for registration with the DCD Enabler. DCD Content Providers interact with the DCD Enabler for utilizing one of the following functions: The DCD Content Provider may directly serve requests for content, for example, as any normal web server. In this case, the DCD Server appears as a normal web client. The DCD Content Provider may provide channel metadata which defines the characteristics of the channels it provides, and optionally support one or more content publication / delivery method. 15 The name Atom applies to 