5 Requirements

5.1 Traffic Light Maneuver (TLM) service

5.1.1 Check the message protocol version

TP Id TP_IS_TLM_MSGF_BV_01
Summary Check that protocolVersion is set to 1 and messageID is set to 4
Reference ETSI TS 103 301 [1], clause 5.3
PICS Selection PICS_SPATEM_GENERATION AND PICS_RSU
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            containing ITS PDU header
                containing protocolVersion
                    indicating value '1'
                and containing messageID
                    indicating value '4'

 

TP Id TP_IS_TLM_MSGF_BV_02
Summary Check that the IUT can successfully process all mandatory fields of SPATEM received
Reference ETSI TS 103 301 [1], clause 5.3
PICS Selection NOT PICS_RSU AND PICS_SPATEM_RECEPTION
Expected behaviour
with
    the IUT being in the "initial state"
             and the IUT sending SPATEM
ensure that
    when
        the IUT receives a valid SPATEM
    then
        the IUT forwards the SPATEM content to upper layers
        and the IUT forwards the SPATEM content to other facilities

 

5.1.2 TLM service trigger, update, repetition and termination

TP Id TP_IS_TLM_EVGN_BV_01
Summary Check that TLM Service generates a new SPATEM on reception of a valid AppSPATEM _Start request
Reference ETSI TS 103 301 [1], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_RSU
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT has not sent any SPATEM yet
ensure that
    when
        the IUT receives an AppSPATEM_Start request from the application layer
    then
        the IUT sends a valid SPATEM

 

TP Id TP_IS_TLM_EVGN_BV_02
Summary Check that TLM Service generates SPATEM are time ordered
Reference ETSI TS 103 301 [1], clause 5.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
             and the IUT has sent a SPATEM
ensure that
    when
        several SPATEM are generated
    then
        the IUT sends SPATEM in time order

 

TP Id TP_IS_TLM_EVGN_BV_03
Summary Check that TLM Service terminates on reception of a valid AppSPATEM _Stop request
Reference ETSI TS 103 301 [1], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_RSU
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        the IUT receives an AppSPATEM _Stop request from the application layer
    then
        the IUT stops sending SPATEM

 

TP Id TP_IS_TLM_EVGN_SND_BV_01
Summary Check that TLM Service generates a new SPATEM on reception of a valid AppSPATEM_Trigger request
Reference ETSI TS 103 301 [1], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppSPATEM_Trigger request from the application layer
    then
        the IUT sends a valid SPATEM

 

5.1.3 Check presence of destination area

TP Id TP_IS_TLM_COM_BV_01
Summary Check that TLM Service provides the destination area in SPATEM
Reference ETSI TS 103 301 [1], clause 5.4.3.2
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT is configured to use GBC
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            containg spat
                containing regional
                    containing at least on region
                        indicating a regionId
                        and indication a regExtValue

 

TP Id TP_IS_TLM_COM_SND_BV_01
Summary Check that TLM Service provides the destination area in SPATEM
Reference ETSI TS 103 301 [1], clause 5.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT is configured to use GBC
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            containg spat
                containing regional
                    containing at least on region
                        indicating a regionId
                        and indication a regExtValue

 

5.1.4 Check BTP type and port number

TP Id TP_IS_TLM_COM_BV_02
Summary Check that SPATEM uses BTP_B packet
Check that the destination port for SPATEM is set to 2004
Reference ETSI TS 103 301 [1], clauses 10.2 and 5.4.3.2
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            encapsulated in a BTP-B packet
                containing a destination port value set to 2004
                and containing a destination port info value set to 0

 

TP Id TP_IS_TLM_COM_SND_BV_02
Summary Check that SPATEM uses BTP_B packet
Check that the destination port for SPATEM is set to 2004
Reference ETSI TS 103 301 [1], clauses 10.2 and 5.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            encapsulated in a BTP-B packet
                containing a destination port value set to '2004'
                and containing a destination port info value set to '0'

 

5.1.5 5 Check destination type

TP Id TP_IS_TLM_COM_BV_03
Summary Check that TLM service encapsulates SPATEM in a GBC with the HeaderType field set to the value of 4
Reference ETSI TS 103 301 [1], clause 5.4.3.2
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
         the IUT sends a valid SPATEM
            encapsulated in a GBC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '4'

 

TP Id TP_IS_TLM_COM_SND_BV_03
Summary Check that TLM service encapsulates SPATEM in a GBC with the HeaderType field set to the value of 4
Reference ETSI TS 103 301 [1], clause 5.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending SPATEM
ensure that
    when
        a SPATEM is generated
    then
        the IUT sends a valid SPATEM
            encapsulated in a GBC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '4'

 

5.1.6 TLM security parameters

5.1.6.1 Check TLM SSP version

5.1.6.2 Check TLM Service specific parameters

5.1.6.3 Check TLM ITS AID value

5.1.6.4 Check that unused SSP bits are set to 0

5.2 Road and Lane Topology (RLT) service

5.2.1 Check that RLT protocol version is set to 1

TP Id TP_IS_RLT_MSGF_RCV_BV_01
Summary Check that the IUT can successfully process all mandatory fields of MAPEM received
Reference ETSI TS 103 301 [1], clause 6.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives a valid MAPEM
    then
        the IUT forwards the MAPEM content to upper layers
        and the IUT forwards the MAPEM content to other facilities

 

TP Id TP_IS_RLT_MSGF_SND_BV_01
Summary Check that protocolVersion is set to 1 and messageID is set to 4
Reference ETSI TS 103 301 [1], clause 6.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
ensure that
    when
        a MAPEM is generated
    then
        the IUT sends a valid MAPEM
            containing ITS PDU header
                containing protocolVersion
                    indicating value '1'
                and containing messageID
                    indicating value '5'

 

5.2.2 Check the RLT message fragmenting

TP Id TP_IS_RLT_INFO_SND_BV_01
Summary Check that IVI Service generates a new MAPEM on reception of a valid AppMAPEM_Trigger request
Reference ETSI TS 103 301 [1], clause 6.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppMAPEM_Trigger request from the application layer
    then
        the IUT sends a valid MAPEM

 

TP Id TP_IS_RLT_INFO_SND_BV_02
Summary Check that RLT Service transmits new content
Reference ETSI TS 103 301 [1], clause 6.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
        containing map
            not containing LayerType
            and not containing LayerID
            and containing restrictionList
                indicating the value RL_1
ensure that
    when
        the IUT is alerted about a new restrictionList indicating the value RL_2
    then
        the IUT sends a valid MAPEM
            containing map
                not containing LayerType
                and not containing LayerID
                and containing restrictionList
                    indicating indicating the value R_2

 

TP Id TP_IS_RLT_INFO_SND_BV_03
Summary Check that RLT Service generates MAPEM are time ordered
Reference ETSI TS 103 301 [1], clause 6.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT has sent a MAPEM
ensure that
    when
        several MAPEM are generated
    then
        the IUT sends MAPEM in time order

 

TP Id TP_IS_RLT_INFO_SND_BV_04
Summary Check that RLT Service transmits fragmented MAPEM when the message size exceeds the allowed message length
Reference ETSI TS 103 301 [1], clause 6.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
ensure that
    when
        the IUT is alerted about a new content
            indicating a new value which exceeds the allowed message length
    then
        the IUT sends a first valid MAPEM
            containing map
                containing LayerType
                and containing LayerID
                    indication a value LID_1
        and the IUT sends a second valid MAPEM
            containing map
                containing LayerType
                and containing LayerID
                    indication a value LID_2 = LID_1 + 1

 

5.2.3 Check continious transmition with the SPAT messages

TP Id TP_IS_RLT_COM_SND_BV_01
Summary Check that the RLT Service transmits continuously both MAPEM and SPATEM
Reference ETSI TS 103 301 [1], clause 6.4.3.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
    and the IUT has not sent any SPATEM yet
ensure that
    when
        the IUT receives an AppSPATEM_Start request from the application layer
    then
        the IUT sends a valid SPATEM
        and the IUT sends a valid MAPEM

 

5.2.4 Check BTP type and port number

TP Id TP_IS_RLT_COM_SND_BV_02
Summary Check that MAPEM uses BTP_B packet
Check that the destination port for MAPEM is set to 2003
Reference ETSI TS 103 301 [1], clauses 10.2 and 6.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
ensure that
    when
        a MAPEM is generated
    then
        the IUT sends a valid MAPEM
            encapsulated in a BTP-B packet
                containing a destination port value set to '2003'
                and containing a destination port info value set to '0'

 

5.2.5 Check destination type

TP Id TP_IS_RLT_COM_SND_BV_03
Summary Check that TLM service encapsulates MAPEM in a GBC with the HeaderType field set to the value of 4
Reference ETSI TS 103 301 [1], clause 6.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending MAPEM
ensure that
    when
        a MAPEM is generated
    then
        the IUT sends a valid MAPEM
            encapsulated in a GBC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '4'

 

5.2.6 RLT security parameters

5.2.6.1 Check RLT SSP version

5.2.6.2 Check RLT Service specific parameters

5.2.6.3 Check RLT ITS ID value

5.2.6.4 Check that unused SSP bits are set to 0

5.3 Infrastructure to Vehicle Information (IVI) service

5.3.1 Check that IVIM protocol version is set to 1

TP Id TP_IS_IVI_MSGF_RCV_BV_01
Summary Check that the IUT can successfully process all mandatory fields of IVIM received
Reference ETSI TS 103 301 [1], clause 7.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives a valid IVIM
    then
        the IUT forwards the IVIM    content to upper layers
        and the IUT forwards the IVIM content to other facilities

 

TP Id TP_IS_IVI_MSGF_SND_BV_01
Summary Check that protocolVersion is set to 1 and messageID is set to 6
Reference ETSI TS 103 301 [1], clause 7.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending IVIM
ensure that
    when
        a IVIM is generated
    then
        the IUT sends a valid IVIM
            containing ITS PDU header
                containing protocolVersion
                    indicating value '1'
                and containing messageID
                    indicating value '6'

 

5.3.2 Check that new iviIdentificationNumber value is generated for each new request

TP Id TP_IS_IVI_EVGN_BV_01
Summary Check that IVI Service generates a new IVIM on reception of a valid AppIVIM_Trigger request
Reference ETSI TS 103 301 [1], clause 7.4.1
PICS Selection PICS_IVIM_GENERATION
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppIVIM_Trigger request from the application layer
    then
         the IUT sends a valid IVIM

 

TP Id TP_IS_IVI_EVGN_BV_02
Summary Check that a new iviIdentificationNumber value is assigned for each newly generated IVIM
Reference ETSI TS 103 301 [1], clause 7.4.1
PICS Selection PICS_IVIM_GENERATION
Expected behaviour
with
    the IUT being in the "initial state"
             and the IUT having generated several IVIM
ensure that
    when
        the IUT is requested to generate a new IVIM
    then
         the IUT sends a valid IVIM
                                     containing ivi
                                             containing mandatory
                                                     containing iviIdentificationNumber
                                                             indicating an unused value

 

5.3.3 Check that the value of iviIdentificationNumber is not used recently

TP Id TP_IS_IVI_EVGN_SND_BV_03
Summary Check that iviIdentificationNumber value is set to a next unused value each time an IVIM is detected
Reference ETSI TS 103 301 [1], clause 7.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated several IVIM
    and the IUT having generated its last DENM
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    indicating IVI_ID_1
    and no active IviID being associated with iviIdentificationNumber IVI_ID_1 + 1
ensure that
    when
        the IUT is requested to generate a new IVIM
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVI_ID_1 + 1

 

5.3.4 Check that a new generated IVIM contains an iviStatus set to 'new'

TP Id TP_IS_IVI_EVGN_SND_BV_04
Summary Check that a new generated IVIM contains an iviStatus set to 'new'
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT is requested to generate a new IVIM
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviStatus
                        indicating 'new'

 

5.3.5 Check that an updated IVIM contains an iviStatus set to 'update'

TP Id TP_IS_IVI_EVGN_SND_BV_05
Summary Check that an updated IVIM contains an iviStatus set to 'update'
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    indicating IVIM_ID_1
                containing iviStatus
                    indicating 'new'
ensure that
    when
        the IUT receives an AppIVIM_update request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviStatus
                        indicating 'update'

 

5.3.6 Check that an update  can change or add the end time to the IVIM

TP Id TP_IS_IVI_EVGN_SND_BV_06
Summary Check that an update can add the end time to the IVIM
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                not containing validTo
                and containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_update indicating a validTo value VT_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing validTo
                        indicating VT_1
                    and containing iviStatus
                        indicating 'update'

 

TP Id TP_IS_IVI_EVGN_SND_BV_07
Summary Check that an update can change the end time to the IVIM
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                containing validTo
                    indicating VT_1
                containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_update indicating a validTo value VT_2
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing validTo
                        indicating VT_2
                    containing iviStatus
                        indicating 'update'

 

5.3.7 Check that the timeStamp is set to the current time when generating a new IVM or last change of information content (if iviStatus set to update)

TP Id TP_IS_IVI_EVGN_SND_BV_08
Summary Check that the timeStamp is set to the current time when generating a new IVM
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT is requested to generate a new IVIM
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing timeStamp
                        indicating CLT
                    containing iviStatus
                        indicating 'new'

 

TP Id TP_IS_IVI_EVGN_SND_BV_09
Summary Check that the timeStamp is set to the current time when generating an update with some change of information content
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                not containing validTo
                and containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_update indicating a validTo
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing timeStamp
                        indicating CLT
                    containing iviStatus
                        indicating 'update'

 

5.3.8 Check that the iviIdentificationNumber remains unchanged IVIM is updated

TP Id TP_IS_IVI_EVGN_SND_BV_10
Summary Check that the iviIdentificationNumber remains unchanged IVIM is updated
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                containing iviStatus
                    indicating 'new'
ensure that
    when
        the IUT receives an AppIVIM_update request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVIM_ID_1
                    containing iviStatus
                        indicating 'update'

 

5.3.9 Check that IVIM are generated in respect of a pre-defined repetition interval

TP Id TP_IS_IVIM_EVUP_SND_TI_01
Summary Check that IVIMs are not generated more frequently than T_GenIvimMin
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_T_GENCAMMIN AND PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated several IVIM
ensure that
    when
        the IUT sends a IVIM
    then
        the IUT does not send any CAM before expiry of T_GenIvimMin

 

TP Id TP_IS_IVIM_EVUP_SND_TI_02
Summary Check that IVIMs are not generated less frequently than T_GenIvimMax
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
             and the IUT having generated several IVIM
ensure that
    when
        the IUT sends a IVIM
    then
        the IUT sends another IVIM before expiry of T_GenIvimMax

 

TP Id TP_IS_IVIM_EVUP_SND_TI_03
Summary
Reference ETSI TS 103 301 [1], clause 7.4.2
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                containing validTo
                    indicating VT_1
                containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_update indicating a validTo value VT_2
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing validTo
                        indicating VT_2
                    containing iviStatus
                        indicating 'update'

 

5.3.10 Check that the IVI Service activates repetition under the request from the ITS-S application

TP Id TP_IS_IVIM_EVRP_SND_TI_01
Summary Check that the IUT activates repetition under the request from the ITS-S application
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated several IVIM
ensure that
    when
        the IUT receives an AppIVIM_Activate indicating 'repetition interval' activation
    then
        the IUT does not send any CAM before expiry of T_GenIvimMin
        and the IUT sends another IVIM before expiry of T_GenIvimMax

 

5.3.11 Check that the IVI Service terminates IVM generation on validity duration expeiry or on termination request

TP Id TP_IS_IVIM_EVTR_SND_BV_01
Summary
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an IVIM
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_termination request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVIM_ID_1
                    containing iviStatus
                        indicating 'termination'

 

TP Id TP_IS_IVIM_EVTR_SND_BV_02
Summary Check that the IUT terminates IVM genration on termination request
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an IVIM
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_termination request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVIM_ID_1
                    containing iviStatus
                        indicating 'termination'

 

5.3.12 Check that the IVI Service terminates IVM generation on cancellation request

TP Id TP_IS_IVIM_EVTR_SND_BV_03
Summary Check that the IUT terminates IVM genration on cancellation request
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an IVIM
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                and containing serviceProviderId
                    indicating IVIM_SP_1
                and containing iviStatus
                    indicating 'new'
             and the IUT having generated an IVIM
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                and containing serviceProviderId
                    indicating IVIM_SP_1
                and containing timeStamp
                    indicating IVM_CLT_1
                and containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_termination request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVIM_ID_1
                    and containing timeStamp
                        indication IVM_CLT_1
                    and containing iviStatus
                        indicating 'cancellation'

 

5.3.13 Check that the IVI Service terminates IVM generation on negation request

TP Id TP_IS_IVIM_EVTR_SND_BV_04
Summary Check that the IUT terminates IVM genration on negation request
Reference ETSI TS 103 301 [1], clause 7.4.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated an event
        containing ivi
            containing mandatory
                containing iviIdentificationNumber
                    inicating IVIM_ID_1
                and containing serviceProviderId
                    indicating IVIM_SP_1
                and containing iviStatus
                    indicating 'update'
ensure that
    when
        the IUT receives an AppIVIM_termination request associated with IVIM_ID_1
    then
        the IUT sends a valid IVIM
            containing ivi
                containing mandatory
                    containing iviIdentificationNumber
                        indicating IVIM_ID_1
                    and containing serviceProviderId
                        indicating IVIM_SP_1
                    and containing iviStatus
                        indicating 'negation'

 

5.3.14 Infrastructure to Vehicle Information (IVI) service/IS_IVI_14

implicitly tested by prev

5.3.15 Infrastructure to Vehicle Information (IVI) service/IS_IVI_19

5.3.16 IVI security parameters

5.3.16.1 IVI security parameters/IS_IVI_15

5.3.16.2 IVI security parameters/IS_IVI_17

5.3.16.3 IVI security parameters/IS_IVI_16

5.3.16.4 IVI security parameters/IS_IVI_18

5.3.17 Check BTP type and port number

TP Id TP_IS_IVI_COM_SND_BV_01
Summary Check that IVIM uses BTP_B packet
Check that the destination port for IVIM is set to 2006
Reference ETSI TS 103 301 [1], clauses 10.2 and 7.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending IVIM
ensure that
    when
        a IVIM is generated
    then
        the IUT sends a valid IVIM
            encapsulated in a BTP-B packet
                containing a destination port value set to '2006'
                and containing a destination port info value set to '0'

 

5.3.18 Check destination type

TP Id TP_IS_IVI_COM_SND_BV_02
Summary Check that TLM service encapsulates IVIM in a UNC with the HeaderType field set to the value of 2
Reference ETSI TS 103 301 [1], clause 7.4.3.2
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT sending IVIM
ensure that
    when
        a IVIM is generated
    then
        the IUT sends a valid IVIM
            encapsulated in a UNC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '2'

 

5.4 Traffic Light Control (TLC) service

5.4.1 Check that SREM protocol version is set to 1

TP Id TP_IS_TLC_MSGF_BV_01
Summary Check that protocolVersion is set to 1 and messageID is set to 9 (ITS-S)
Reference ETSI TS 103 301 [1], clause 8.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT is requested to generate a new SREM
    then
        the IUT sends a valid SREM
            containing ITS PDU header
                containing protocolVersion
                    indicating value '1'
                and containing messageID
                    indicating value '9'

 

TP Id TP_IS_TLC_MSGF_BV_03
Summary Check that the IUT can successfully process all mandatory fields of SSEM received (ITS-S)
Reference ETSI TS 103 301 [1], clause 8.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having receive a valid SREM
ensure that
    when
        the IUT receives a valid SSEM
    then
         the IUT forwards the SSEM content to upper layers
                             and the IUT forwards the SSEM content to other facilities

 

5.4.2 Check that SSEM protocol version is set to 1

TP Id TP_IS_TLC_MSGF_BV_02
Summary Check that the IUT can successfully process all mandatory fields of SREM received (TLC-S)
Reference ETSI TS 103 301 [1], clause 8.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT having receive a valid SREM
    then
        the IUT forwards the SREM content to upper layers
        and the IUT generates a SSEM

 

TP Id TP_IS_TLC_MSGF_BV_04
Summary Check that protocolVersion is set to 1 and messageID is set to 10 (TLC-S)
Reference ETSI TS 103 301 [1], clause 8.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT having receive a valid SREM
    then
        the IUT sends a valid SSEM
            containing ITS PDU header
                containing protocolVersion
                    indicating value '1'
                and containing messageID
                    indicating value '10'

 

5.4.3 Check that the IUT identifies SREM with a unique request identifier

TP Id TP_IS_TLC_EVGN_BV_01
Summary Check that IVI Service generates a new SREM on reception of a valid AppSREM_Trigger request (ITS-S)
Reference ETSI TS 103 301 [1], clause 8.4.1
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppSREM_Trigger request from the application layer
    then
        the IUT sends a valid SREM

 

TP Id TP_IS_TLC_EVGN_BV_02
Summary Check that the IUT identifies SREM with a unique request identifier (ITS-S)
Reference ETSI TS 103 301 [1], clause 8.4.1
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generated several SREM
ensure that
    when
        the IUT is requested to generate a new SREM
    then
        the IUT sends a valid SREM
            containing srm
                containing requests[0]
                    containing requestID
                        indicating an unused value

 

5.4.4 Check that the IUT increments the sequenceNumber when a SREM update is generated

TP Id TP_IS_TLC_EVUP_BV_01
Summary Check that the IUT increments the sequenceNumber when a SREM update is generated
Reference ETSI TS 103 301 [1], clause 8.4.1
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
    and the IUT having generate a SREM
        containing srm
            containing sequenceNumber
                indicating SREM_SN_1
            and containing requests[0]
                containing request
                    containing requestID
                        indicating SREM_RID_1
ensure that
    when
        the IUT receives an AppSREM_update request
    then
        the IUT sends a valid SSEM
            containing ssm
                containing sequenceNumber
                    indicating SREM_SN_1+ 1
                and containing requests[0]
                    containing request
                        containing requestID
                            indicating SREM_RID_1

 

5.4.5 Check that the IUT generates a SSEM using the request identification value set in reveived SREM (TCL-S)

TP Id TP_IS_TLC_EVGN_04
Summary Check that the IUT generates a SSEM using the request identification value set in reveived SREM (TCL-S)
Reference ETSI TS 103 301 [1], clause 8.4.1
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT having receive a SREM
            containing srm
                containing sequenceNumber
                    indicating SREM_SN_1
    then
            the IUT sends a valid SSEM
                containing ssm
                    containing sequenceNumber
                        indicating SREM_SN_1

 

5.4.6 Check that the IUT generates SSEM to "overrules" previous request

5.4.7 TLC security parameters

5.4.7.1 TLC security parameters/IS_TLC_08

5.4.7.2 TLC security parameters/IS_TLC_09

5.4.7.3 TLC security parameters/IS_TLC_07

5.4.7.4 TLC security parameters/IS_TLC_10

5.4.7.5 TLC security parameters/IS_TLC_11

5.4.8 Check BTP type and port number

TP Id TP_IS_TLC_COM_BV_01
Summary Check that IVIM uses BTP_B packet
Check that the destination port for IVIM is set to 2007
Reference ETSI TS 103 301 [1], clauses 10.2 and 8.4.3.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppSREM_Trigger request from the application layer
    then
        the IUT sends a valid SREM
            encapsulated in a BTP-B packet
                containing a destination port value set to '2007'
                and containing a destination port info value set to '0'

 

TP Id TP_IS_TLC_COM_BV_02
Summary Check that IVIM uses BTP_B packet
Check that the destination port for IVIM is set to 2008
Reference ETSI TS 103 301 [1], clauses 10.2 and 8.4.3.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT having receive a valid SREM
    then
        the IUT sends a valid SSEM
            encapsulated in a BTP-B packet
                containing a destination port value set to '2008'
                and containing a destination port info value set to '0'

 

5.4.9 Check destination type

TP Id TP_IS_TLC_COM_BV_03
Summary Check that TLM service encapsulates IVIM in a GBC with the HeaderType field set to the value of 4
Reference ETSI TS 103 301 [1], clause 8.4.3.3
PICS Selection NOT PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT receives an AppSREM_Trigger request from the application layer
    then
        the IUT sends a valid SREM
            encapsulated in a GBC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '4'

 

TP Id TP_IS_TLC_COM_BV_04
Summary Check that TLM service encapsulates IVIM in a GBC with the HeaderType field set to the value of 4
Reference ETSI TS 103 301 [1], clause 8.4.3.3
PICS Selection PICS_RSU_ROLE
Expected behaviour
with
    the IUT being in the "initial state"
ensure that
    when
        the IUT having receive a valid SREM
    then
        the IUT sends a valid SSEM
            encapsulated in a GBC packet
                containing a correctly formatted Common Header
                    containing HeaderType field
                        indicating the value '4'