Implementing MGSF SAEM TPs

LibItsSaem_Pics.PICS_IS_IUT_SECURED := true

LibItsSaem_Pixits.PX_NEW_SERVICE_ID            := 100

LibItsSaem_Pixits.PX_NEW_SERVICE_CHANNEL_INDEX := 30

[LOGGING]

# In this section you can specify the name of the log file and the classes of events

# you want to log into the file or display on console (standard error).

# 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 channel Index component in the ServiceInfo contains a pointer to an entry in the channelInfos component or in the ExtendedChannelInfos extension if there are entries

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_10

# Check that the channelIndex component in the ServiceInfo is set to 0 if the channelInfos component and the ExtendedChannelInfos extension are absent

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_11

# Check that the extension SrvOpP-ProtocolStack is present in the ServiceInfo component

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_12

# Check that the extension IPv6Address is present if the extension SrvOpP-ProtocolStack indicates "IPv6"

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_13

# Check that the extension ProviderMACaddress is present when the Service Provider is implemented in a different ITS-S than the Advertiser and forwarding at data link layer is used

# Check that the subcomponents systemSerrvice and serviceProviderPort are not used

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_14_15

# Check that the channelInfos component and / or the ExtendedChannelInfos extension are present if the ITS-S service can be consumed on a channel that is different from the channel on which the SAEM is transmitted

#ItsAvm_TestCases.TC_MVM_MSD_FMT_BV_16

# 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.

#ItsAvm_TestCases.TC_SAEM_IFSE_BV_01

Subproject commit 35313de9f9c23e2f0b15670e5205ff3918548868

Subproject commit f310658efb4be0b8c502be7939f8ee838afdd8fe