# Check that protocolVersion is set to 2 and messageID is set to 19
# Check that protocolVersion is set to 2 and messageID is set to 12
ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_01
# Check that the statdionId component of the header is set to the Station ID of the Service Announcer ITS-S
#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_04
# Check that the sam component of the SAEM is of type Sam
# Check that the changeCount component is of type SrvAdvChangeCount
#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_05_06
# 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
#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_07
# Check that the samBody component contains the serviceInfos component with at least one element
# Check that the serviceId component in the ServiceInfo contains the ITS-AID of the announced ITS-S service
#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_08_09
# Check that the SAS exchanges information directly with the security entities via the interface IF.Security when ETSI ITS security is used at the facilities layer.
# Check that the contentCount in the component changeCount identifies a change of the content of the announced SA that corresponds to a certain saID
#ItsAvm_TestCases.TC_SAEM_DISS_BV_02
# Check that the saID and contentCount in the component changeCount are identical for consecutive messages with identical content from the same ITS-S
#ItsAvm_TestCases.TC_SAEM_DISS_BV_03
# 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
#ItsAvm_TestCases.TC_SAEM_DISS_BV_04
# Check that SAEMs are signed with explicit Authorization Tickets containing the SA ITS-AID and BitmapSsp SSPs