
DCN Next Generation Open Interface Release 2.4 Microphone Management
en | 84
Bosch Communications Systems | 2007 February | SRS_MMINF | Du020903
2. MICROPHONE MANAGEMENT FOR A REMOTE INTERFACE
2.1 Introduction
The Microphone Management Remote Interface is part of the DCNNG software, which allows
for another controlling entity outside the CCU, not being the DCNNG Control PC, to use the
Microphone Management application.
2.2 Remote Microphone Management Control
Microphone Management is the application that allows for controlling the microphones in the
conference hall. Typical control issues are e.g.: turning a Microphone On, adding a delegate
to the RTS list, changing the Operation Mode etc.
Controlling microphones with a remote interface is by means of calling a defined set of
Remote Functions and acting upon a defined set of Update Notifications. The general
concept of Remote Functions and Update Notifications is described in [SRS_INF]. [SRS_INF]
also describes the protocol and hardware conditions concerning the remote interface.
Together with this remote interface, there are up to three locations in a full-connected CCU
where MM can be influenced. These locations are:
• The remote interface or the remote controller (customer build client or DCNNG Control
PC) uses the TCP/IP interface. The remote controller makes Remote Function calls for
microphone management.
• The actual units that handle their microphone keys.
To get a full operational system both the DCNNG control PC and the remote controller must
register themselves to the CCU, so they will receive update messages from the CCU.
Remote functions coming from either the DCNNG control PC or the remote controller initiates
in the CCU an update of the internal lists. During the update, notifications are generated and
sent to both the DCNNG control PC and the remote controller. In this way both remote
controllers get the update information about the actions performed on either the DCNNG
control PC or the remote controller.
During the processing of remote functions on the CCU, the update messages are created and
transmitted. This implies that the response information of a remote function can be received
after the reception of an update notification. The remote controller must wait for the response
of the remote function. After reception of the response appropriate action should be taken
upon the error code returned. The notifications received during the wait for the response may
be processed directly.
Requests coming from a unit are processed and the lists updated. During the update,
notifications are generated and sent to all registered PC’s. In the system mentioned above,
both the DCNNG control PC and the remote controller will receive the same update
notifications.
This document gives the set of Remote Functions and the set of Update Notifications
concerning Microphone Management. The relation between Remote Function, sent by the
remote controller, and Update Notifications is given in the description of each separate
Remote Function. The relation between unit events and Update Notifications is given in
section 4.1.2. At last, there is a relation between remote functions sent by the DCNNG control
PC and update notifications. Since both remote controller and DCNNG control PC receive all
update notifications, the set of update notifications therefore also contains those that are the
result of a remote function from the DCNNG control PC.
2.3 Microphone List and Mode Management
Handling the microphones in the system is basically a way of managing the various
microphone lists identified inside the CCU and choosing the appropriate operation mode. The
Komentarze do niniejszej Instrukcji