* @desc Check that the samBody component contains the component extensions if one of the announced services can be consumed using a different communication technology from the SAEM
* <pre>
* Pics Selection: PICS_SAEM_GENERATION
* Initial conditions:
* with {
* SAS is active
* and one of the announced services can be consumed using a technology different from the one used to disseminate the SAEM
* }
* Expected behaviour:
* ensure that {
* when {
* SAS generates SAEM
* }
* then {
* the IUT sends a valid SAEM
* containing body
* containing extensions
* containing at least one SrvAdvMsgHeaderExt
* containing value of type ExtendedChannelInfos
* containing at least one ExtendedChannelInfo
* }
* }
* </pre>
*
* @see ETSI TS 104 203-2 v2.2.1 TP/SAEM/MSGF/BV-07
* @desc Check that the SAS message processing triggers, updates or ends the SAEM dissemination according to parameters received from the management entity vie the MF interface
* triggers
* <pre>
* Pics Selection: PICS_SAEM_GENERATION
* Initial conditions:
* with {
* SAS is active
* }
* Expected behaviour:
* ensure that {
* when {
* SAS receives parameters from the management entity via the MF interface
* }
* then {
* the SA facilities layer message processing functional block triggers / updates / ends SAME dissemination
* }
* }
* </pre>
*
* @see ETSI TS 104 203-2 v2.2.1 TP/SAEM/DISS/BV-04
* @desc Check that the SAS message processing triggers, updates or ends the SAEM dissemination according to parameters received from the management entity vie the MF interface
* ends
* <pre>
* Pics Selection: PICS_SAEM_GENERATION
* Initial conditions:
* with {
* SAS is active
* }
* Expected behaviour:
* ensure that {
* when {
* SAS receives parameters from the management entity via the MF interface
* }
* then {
* the SA facilities layer message processing functional block triggers / updates / ends SAME dissemination
* }
* }
* </pre>
*
* @see ETSI TS 104 203-2 v2.2.1 TP/SAEM/DISS/BV-04