Кіріспе
Цифрлық сақтау ортасының басқару және бақылау жүйесі (Digital storage media command and control - DSM CC) MPEG 1 және MPEG 2 ағындарымен байланысты басқару арналарын жасауға арналған құралдар жиынтығы болып табылады. Ол MPEG 2 стандартының 6-бөлігінде (DSM CC кеңейтімдері) сипатталған және негізгі желі арқылы байланысқан клиент/сервер моделін қолданады (MPEG 2 мультиплексі арқылы немесе қажет болған жағдайда жеке түрде). DSM CC бейне қабылдауды басқаруға мүмкіндік береді, мысалы, бейнекассеталық магнитофондарда (VCR) кездесетін мүмкіндіктерді (ойнатуды жылдамдату, кері ойнату, тоқтату және т.б.) қамтамасыз етеді. Ол сондай-ақ пакеттік деректерді тасымалдау сияқты көптеген басқа мақсаттарда да қолданылуы мүмкін. Бұл жүйе бірқатар маңызды стандарттармен анықталады, ең бастысы – MPEG 2 ISO/IEC 13818 6 (MPEG 2 стандартының 6-бөлігі). DSM CC жаңа буын пакеттік желілермен бірлесіп жұмыс істей алады, RSVP, RTSP, RTP және SCP сияқты интернет-протоколдарымен үйлесімді. DSM CC көбінесе бейне таратумен (спутник немесе эфир арқылы) және интерактивті контентпен байланысты болғанымен, аудио серверлер мен клиенттер арасында да қолданылады. Архитектура жүйенің үш негізгі бөлігін сипаттайды: клиент, сервер және сессия ресурстарын басқарушы (SRM). Сервер клиентке контент пен басқа да қызметтерді ұсынады, ал екеуі де SRM-нің «клиенттері» болып табылады. SRM желі ресурстарын (мысалы, арналар, өткізу қабілеті және желілік мекенжайлар) бөліп, басқарады. Серверлік және клиенттік компоненттерді бір платформада біріктіру арқылы контентқа қол жеткізу және тарату жүйелерін құруға болады. Бұл сипаттамалар көптеген іске асыру опцияларын қамтиды. Мысалы, MPEG 2 бейнесі әртүрлі тәсілдермен кодталуы мүмкін, ал DSM CC жүйесі белгілі бір мүмкіндіктер мен интерфейстерді қосу немесе алып тастау үшін құрастырылуы мүмкін. Әдетте, сыртқы сипаттама белгілі бір опциялардың профилін анықтайды, бұл ортақ профильдерді пайдалана отырып құрылған жүйелердің өзара үйлесімді жұмыс істеуіне мүмкіндік береді. DSM CC бес түрлі протоколды анықтайды немесе кеңейтеді:
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Пайдаланушы-Пайдаланушы (User-User) Клиентке сервердегі объектілерге қашықтан қол жеткізуге мүмкіндік береді. User-User сипаттамасы белгілі бір серверлік объектілер кластарын анықтаудан асып, клиентке тән кластарды және жүйенің басқа бөліктерімен өзара әрекеттесуді анықтайды. Бөлінген объектілер моделі CORBA негізінде құрылған. Объектілерге интернеттер ORB протоколы (IIOP) арқылы қол жеткізіледі, кейбір қосымша кеңейтулермен. Екі кіші жиынтық анықталған: «негізгі» және «кеңейтілген». Модельде кейбір клиенттер серверге контент жүктеуі мүмкін.
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Пайдаланушы-Желі (User-Network) Бұл протоколдың екі бөлімі бар: Сессия және Ресурс. Бұл протокол клиент пен SRM және сервер мен SRM арасында қолданылады. U N сессия протоколы желімен сессияларды орнату үшін қолданылады, ал U N ресурс протоколы бөлінетін және босатылатын ресурстармен байланысты.
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
MPEG тасымалдау профильдері (MPEG transport profiles) Бұл сипаттама стандартты MPEG тасымалдау протоколына (ISO/IEC 13818 1 бойынша) оқиғалар, синхрондау, жүктеу және басқа да ақпаратты MPEG тасымалдау ағынында таратуға мүмкіндік беретін профильдерді ұсынады.
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Жүктеу (Download) Бұл протоколдың бірнеше нұсқалары серверден клиентке контентті тасымалдауға мүмкіндік береді, MPEG тасымалдау ағынының ішінде немесе жеке (жоғары жылдамдықты) арна арқылы. Ағымды басқарумен жүктеу (Flow controlled download) жүктеу операцияларын келіссөз жүргізу және клиенттік басқаруға мүмкіндік береді. Жүктеудің бір түрі – сервердегі автономды «деректер каруселі», ол ақпаратты қайта-қайта жүктейді; жүктеу каруселінің клиенты ақпаратты бастамай күтеді. Деректер каруселіне қосымша «объект каруселі» болып табылады, ол жүктелген ақпаратты User-User API-мен анықталған объектілермен үйлесімді объектілер ретінде ұсынады. (Жүктеу немесе IIOP протоколын таңдау объектінің IOR-ге енгізілген, сондықтан қол жеткізу әдісі клиенттік қолданба үшін көрінбейді.)
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Коммутацияланған цифрлық хабар тарату арнасын өзгерту протоколы (SDB/CCP) Клиентке хабар тарату ортасында арнаны қашықтан өзгертуге мүмкіндік береді. Клиентті үздіксіз беру сессиясына (CFS) немесе басқа хабар таратуға қосу үшін қолданылады. Кейде «көру үшін төлеу» жүйелерінде қолданылады. Іске асыруға әрқашан осы протоколдардың барлығы қажет емес. Нақты қолданыстағы жүйелердің көпшілігі кіші жиынтықты пайдаланады.
Digital storage media command and control
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Digital storage media command and control (DSM CC) is a toolkit for developing control channels associated with MPEG 1 and MPEG 2 streams. It is defined in part 6 of the MPEG 2 standard (Extensions for DSM CC) and uses a client/server model connected via an underlying network (carried via the MPEG 2 multiplex or independently if needed). DSM CC may be used for controlling the video reception, providing features normally found on Video Cassette Recorders (VCR) (fast forward, rewind, pause, etc.). It may also be used for a wide variety of other purposes including packet data transport. It is defined by a series of weighty standards, principally MPEG 2 ISO/IEC 13818 6 (part 6 of the MPEG 2 standard). DSM CC may work in conjunction with next generation packet networks, working alongside such internet protocols as RSVP, RTSP, RTP and SCP. Although DSM CC is usually associated with video delivery (via satellite or terrestrially) and with interactive content, it is also used among audio servers and clients. The architecture describes three main parts of the system: the client, the server, and the session resource manager (SRM). The server provides content and other services to the client, and both are "clients" of the SRM. The SRM allocates and manages network resources (such as channels, bandwidth, and network addresses.) By combining server and client components together onto the same platforms, peer to peer content access and delivery systems can be constructed. These specifications include numerous implementation options. For example, MPEG 2 video can be encoded in different ways, and a DSM CC system can be constructed to include or exclude certain features and interfaces. Normally, an outside specification will define a profile of specific options, allowing systems built using common profiles to interoperate. DSM CC defines or extends five distinct protocols:
User User Allows remote access by the client to objects on the server. The User User specification goes beyond the definition of specific server object classes to define classes local to the client, as well as some of the interaction with other parts of the system. The distributed object model is based on CORBA. Objects are accessed using the internet inter ORB protocol (IIOP), with some optional extensions. Two subsets, "core" and "extended", are defined. In the model, some clients may also load content onto the server. User Network There are two parts to this protocol: Session and Resource. This protocol is used between the client and SRM, and between the server and SRM. The U N Session protocol is used to establish sessions with the network, associated with resources which are allocated and released using the U N Resource protocol. MPEG transport profiles The specification provides profiles to the standard MPEG transport protocol (defined by ISO/IEC 13818 1) to allow transmission of event, synchronization, download, and other information in the MPEG transport stream. Download Several variations of this protocol allow transfer of content from server to client, either within the MPEG transport stream or on a separate (presumably high speed) channel. Flow controlled download allows the download operations to be negotiated and controlled by the client. A variation of download is an autonomous "data carousel" on the server which repeatedly downloads information; the download carousel client waits for the information without initiating the transfer. An extension to the data carousel is the "object carousel", which presents downloaded information as objects compatible with the objects defined by the User User API. (The choice of download or IIOP protocols is embedded in the object's IOR, so the means of access is transparent to the client application.) Switched Digital Broadcast Channel Change Protocol (SDB/CCP) Enables a client to remotely switch from channel to channel in a broadcast environment. Used to attach a client to a continuous feed session (CFS) or other broadcast feed. Sometimes used in pay per view. An implementation does not always need all of these protocols. Almost all implementations in the real world use a subset.
Ұзарту
Delivery Multimedia Integration Framework (DMIF) MPEG 2 DSM CC стандартын (ISO/IEC 13818 6:1998) интерактивті, эфирлік және сөйлесу мультимедиасын бір спецификацияға біріктіру үшін кеңейтеді, бұл десте, үстел және мобильді құрылымдарға қолданылады. DSM CC жұмысы ISO/IEC 14496 6 (MPEG 4 6-бөлігі) аясында DSM CC мультимедиалық интеграция шеңбері (DMIF) арқылы одан әрі дамытылды.
Delivery Multimedia Integration Framework (DMIF) expands upon the MPEG 2 DSM CC standard (ISO/IEC 13818 6:1998) to enable the convergence of interactive, broadcast and conversational multimedia into one specification which will be applicable to set tops, desktops and mobile stations. The DSM CC work was extended as part of the ISO/IEC 14496 6 (MPEG 4 Part 6), with the DSM CC Multimedia Integration Framework (DMIF).