ISO IEC 24792:2010 pdf – lnformation technology – Telecommunications and informationexchange between systems – Multicastsession Management Protocol(MSMP)
ISO IEC 24792:2010 pdf – lnformation technology – Telecommunications and informationexchange between systems – Multicastsession Management Protocol(MSMP).
After successful session creation, the server will announce the new session to the clients with the more specified OoS parameter values. The announcement may be done by e-mail, web posting, and so on. From this point on, those clients may register In multicast groups.
A client may register for the session, considering those QoS parameter values. After successful registration, the client belongs to the registered group.
When the session starts, the session’s registered members will start a group application to send and receive
session data. At this time, all preparations for the data transfer and group management are accomplished.
The sessions registered group member belongs to the enrolled group. After that, the GMP server sends the
MSMP server a QoS Session Join Indication message, QSJIND The MSMP server starts the 005 Reporting
Request and Response.
6.3 Q0S Management
The MSMP server aggregates the QoS parameter values such as throughput, delay, delay jitter, and loss from all participants. After aggregation of the QoS parameter values, the MSMP server arbitrates them and will send the 005 parameter values to the session creator via a 005 Setting Request message, QSREQ. The session creator will acknowledge with the final arbitrated the QoS parameter values to the MSMP server via a QoS Setting Response message. QSRES. After receiving QSRES, the MSMP server announces the final arbitrated QoS parameter values to all session participants via Q0S Setting Report message, QSREP.
The QoS reporting is performed to maintain and update the QoS parameter values. The MSMP server will send periodically a QoS Reporting Request message, QRREQ, to all participants to gather the QoS parameter values. Each participant will acknowledge with own QoS parameter values for receiving a data via a QoS Reporting Response message, ORRES. If the session participant is a session creator or a sender, the participant will reply with own Q0S parameter values for sending and receiving data via ORRES. After receving ORRES, the MSMP server arbitrates them and will send the QoS parameter values to the session creator via OSREG. The session creator will reply with the final arbitrated the QoS parameter values to the MSMP server via QSRES. After recewing OSRES. the MSMP server will update and keep the QoS parameter values and announces the values to all session participants.
Figure 3 shows an example of MSMP operations. After a session is created and announced, four session participants, A, B, C, and D register for a session in the session registration phase, The session creator and clients send a session join request to the GMP server to be ready to communicate with each other in the session enrollment phased. After thai, the session creator and the clients belong to the enrolled group. A session creator and three participants, A. B and D enter the active state by sending a session activation request message to the GMP server. In Figure 3, the participant C who is a late-joiner will send a session activation request message to the GMP server after the session activation. In the late join case, the late-joiner comes to send a 005 Value Request message, QVREO. to the MSMP server in order to get QoS parameter values of the on-going session. Now, the particIpant 0 comes to be a troublemaker w$’io reports QoS parameter values lower than the QoS parameter values of the on-going session, If a troublemaker could not maintain the QoS parameter values at a desired level in the on.going session, the troublemaker may be e’ected from the on-going session as shown in Figure 3. For some reason there may be a case that the troubIemer does not leave the session( see subsection 7.2.4).