Incongruity between requirements [V2G2-546], [V2G2-714] and [V2G2-716]

Problem

According to [V2G2-714], [V2G2-716] and table 110, the SECC must start the communication setup timer as soon as the data link is established and stop it when the timeout is reached or a SessionSetupReq is received. The timeout value for the communication setup is set to 18 seconds.

But, according to [V2G2-536] and to Table 109, the SECC must set the sequence timer and wait for the supportedAppProtocolReq. The timeout value for the wait of the supportedAppProtocolReq message is set to 60 secs.

As the timeout for the Communication Setup is tighter (18 secs), there is no way that the Sequence timer for the supportedAppProtocolReq can ever be triggered.

What shall be the procedure given these requirements?

Requirements

[V2G2-714]

The SECC shall set the timeout V2G_SECC_CommunicationSetup_Performance_Time to the value as defined in Table 110, reset the V2G_SECC_CommunicationSetup_Timer and start monitoring the V2G_SECC_CommunicationSetup_Timer when a successful Data-Link establishment is indicated (D-LINK_READY.indication(DLINKSTATUS=Link established).

[V2G2-716] The SECC shall stop waiting for SessionSetupReq and stop monitoring the V2G_SECC_CommunicationSetup_Timer when V2G_SECC_CommunicationSetup_Timer is equal or larger than V2G_SECC_CommunicationSetup_Performance_Time and no SessionSetupRes message was sent. It shall then apply [V2G2-034].

[V2G2-536] The SECC shall enter a wait state for supportedAppProtocolReq, set the timeout V2G_SECC_Sequence_Timeout to the value MessageType as defined in Table 109, reset the V2G_SECC_Sequence_Timer and start monitoring the V2G_SECC_Sequence_Timer.