Document Title: Acceptance Test Specification of Communication Via Bus

Acceptance Test Specification of Communication via
bus
AUTOSAR TC Release 1.2.0
Document Title Acceptance Test Specification

of Communication via bus
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 666
Document Classification Auxiliary
Document Status Final

Part of AUTOSAR Standard Acceptance Tests for Classic Platform
Part of Standard Release 1.2.0
Document Change History

Date Release Changed by Change Description
2016-12-15 1.2.0 AUTOSAR  Checked and adapted to Classic Platform
Release Release 4.2.2
Management  Added RS_BRF_01649 for Large Data
Com
 ATS_COMINDEP_00226 modified
2015-10-31 1.1.0 AUTOSAR  Checked and adapted to Classic Platform
Release Release 4.2.1 (ATS_COMINDEP_00205,
Management ATS_COMINDEP_00260,
ATS_COMINDEP_00261 modified)
 Formalization of the point of control and
observation for actions and expected
results
 Added 29 new test cases
2014-07-30 1.0.0 AUTOSAR  Initial release
Release
Management
1 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

- AUTOSAR Confidential -
bus
Disclaimer
This specification and the material contained in it, as released by AUTOSAR, is for
the purpose of information only. AUTOSAR and the companies that have contributed
to it shall not be liable for any use of the specification.
The material contained in this specification is protected by copyright and other types
of Intellectual Property Rights. The commercial exploitation of the material contained
in this specification requires a license to such Intellectual Property Rights.
This specification may be utilized or reproduced without any modification, in any form
or by any means, for informational purposes only. For any other purpose, no part of
the specification may be utilized or reproduced, in any form or by any means, without
permission in writing from the publisher.
The AUTOSAR specifications have been developed for automotive applications only.
They have neither been developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.
Advice for users
AUTOSAR specifications may contain exemplary items (exemplary reference

models, "use cases", and/or references to exemplary technical solutions, devices,
processes or software).
Any such exemplary items are contained in the specifications for illustration purposes
only, and they themselves are not part of the AUTOSAR Standard. Neither their
presence in such specifications, nor any later documentation of AUTOSAR
conformance of products actually implementing such exemplary items, imply that
intellectual property rights covering such exemplary items are licensed under the
same rules as applicable to the AUTOSAR Standard

bus
Table of Contents
1 Acronyms and abbreviations .............................................................................. 8

2 Scope ................................................................................................................. 9
3 RS_BRF_01600 - Timeout Handling ................................................................ 10
3.1 General Test Objective and Approach........................................................ 10
3.1.1 Test System........................................................................................... 10
3.1.2 Test Configuration ................................................................................. 13
3.1.3 Test Case Design .................................................................................. 15
3.2 Re-usable Test Steps ................................................................................. 15
3.3 Test Cases ................................................................................................. 15
3.3.1 [ATS_COMINDEP_00100] Managing Rx signal deadline timeout with
notification ............................................................................................. 15
3.3.2 [ATS_COMINDEP_00101] Managing Rx signal group deadline
timeout with action REPLACE ............................................................... 18
3.3.3 [ATS_COMINDEP_00102] Managing Tx Ipdu deadline timeout............ 19
3.3.4 [ATS_COMINDEP_00104] Disabling/Enabling Rx Deadline
monitoring .............................................................................................. 20
3.3.5 [ATS_COMINDEP_00105] Managing Rx Ipdu deadline timeout
without notification ................................................................................. 22
3.3.6 [ATS_COMINDEP_00107] Managing Rx signal group deadline
timeout with action NONE...................................................................... 24
3.3.7 [ATS_COMINDEP_00738] Signal With ComRxDataTimeoutAction
Set To NONE And Reception Deadline Monitoring Expires .................. 25
4 RS_BRF_01616 - Initial Values........................................................................ 27
4.1.1 Test System........................................................................................... 28
4.1.3 Test Case Design .................................................................................. 33
4.3 Test Cases ................................................................................................. 34
4.3.1 [ATS_COMINDEP_00075] Providing UINT8 initial value if Rx signal
was never received ................................................................................ 34
deadline timeout occurs ......................................................................... 35
4.3.7 [ATS_COMINDEP_00083] Providing SINT8 initial value if Rx signal

bus
4.3.13 [ATS_COMINDEP_00090] Providing BOOLEAN initial value if Rx
signal was never received ..................................................................... 46
4.3.14 [ATS_COMINDEP_00091] Providing BOOLEAN initial value if Rx
signal deadline timeout occurs .............................................................. 46
4.3.15 [ATS_COMINDEP_00092] Providing FLOAT32 initial value if Rx
4.3.17 [ATS_COMINDEP_00094] Providing UINT8_N initial value if Rx
4.3.18 [ATS_COMINDEP_00095] Providing UINT8_N initial value if Rx
4.3.21 [ATS_COMINDEP_00098] Providing initial value for Tx gatewayed
signal if Rx signal was never received ................................................... 54
4.3.22 [ATS_COMINDEP_00099] Providing initial value for Tx gatewayed
signal if Rx signal deadline timeout occurs ............................................ 55
4.3.23 [ATS_COMINDEP_00721] Packing Of IPdu Data ................................. 56
4.3.24 [ATS_COMINDEP_00722] Unpacking Of IPdu Data ............................. 57
5 RS_BRF_01632 - Data Consistency ................................................................ 59
5.1.1 Test System........................................................................................... 59
5.1.3 Test Case Design .................................................................................. 63
5.3 Test Cases ................................................................................................. 63
5.3.1 [ATS_COMINDEP_00050] Invalidating a Tx signal group when
invalidated by the SWC ......................................................................... 63
5.3.2 [ATS_COMINDEP_00051] Notifying the SWC when a signal or a
signal group is received with invalid data .............................................. 65
5.3.3 [ATS_COMINDEP_00072] Invalidating a Tx signal when invalidated
by the SWC ........................................................................................... 66
5.3.4 [ATS_COMINDEP_00074] Replacing by the init value when a signal
group is received invalid ........................................................................ 67
6 RS_BRF_01649- LdCom data transfer (Bus independent) .............................. 69
bus
6.1.1 Test System........................................................................................... 69
6.1.3 Test Case Design .................................................................................. 72
6.3 Test Cases ................................................................................................. 73
6.3.1 [ATS_COMINDEP_01470] LdCom Transmission using <Bus>IF API
and Notification for PDU Transfer .......................................................... 73
6.3.2 [ATS_COMINDEP_01471] LdCom Reception using <Bus>IF API ........ 74
6.3.3 [ATS_COMINDEP_01472] LdCom Transmission using <Bus>TP API
and Notification for PDU Transfer .......................................................... 75
6.3.4 [ATS_COMINDEP_01473] LdCom Reception using <Bus>TP API....... 76
6.3.5 [ATS_COMINDEP_01476] Behavior of LdCom Transmit Request
from Application when there is a request in Progress for the same
PDU ....................................................................................................... 77
6.3.6 [ATS_COMINDEP_01478] Behavior of LdCom Receive Request from
Application when there is a request in Progress for the same PDU ...... 79
6.3.7 [ATS_COMINDEP_01047] Behavior of LdCom Transmit Request
from Application when Transmit Confirmation was invoked for the
ongoing Transmission request for the same PDU ................................. 80
7 RS_BRF_01592 - Data Transfer (Bus independent) ........................................ 83
7.1.1 Test System........................................................................................... 83
7.1.3 Test Case Design .................................................................................. 94
7.3 Test Cases ................................................................................................. 94
7.3.1 [ATS_COMINDEP_00200] Group Control - Time Based frame
(PERIODIC) ........................................................................................... 94
7.3.2 [ATS_COMINDEP_00205] Group Control - User Request frame
(DIRECT) + MDT ................................................................................... 97
7.3.3 [ATS_COMINDEP_00259] User Request frame (DIRECT) + MDT ....... 99
7.3.4 [ATS_COMINDEP_00260] User Request frame (DIRECT) + several
triggers................................................................................................. 100
7.3.5 [ATS_COMINDEP_00212] Tx notification ........................................... 101
7.3.6 [ATS_COMINDEP_00220] Tx Mode Switch (TMS) -
PERIODIC/PERIODIC ......................................................................... 103
7.3.7 [ATS_COMINDEP_00221] Tx Mode Switch (TMS) - MIXED/DIRECT 106
7.3.8 [ATS_COMINDEP_00261] DIRECT + TRIGGERED ON CHANGE
WITHOUT REPETITIONS ................................................................... 108
PERIODIC/MIXED + MDT ................................................................... 110
DIRECT/PERIODIC ............................................................................. 112
7.3.11 [ATS_COMINDEP_00225] Manual Tx Mode Switch (TMS)
PERODIC/PERIODIC .......................................................................... 114
7.3.12 [ATS_COMINDEP_00223] Manual Tx Send (Trigger IPdu Send) +
MDT ..................................................................................................... 116
bus
7.3.13 [ATS_COMINDEP_00226] Ipdu and Trigger Transmit Callouts .......... 118
7.3.14 [ATS_COMINDEP_00723] Transmission Of An I-PDU having
DIRECT Tx Mode Consisting of Signal And Signal Group with
Triggered On Change Transfer Property ............................................. 120
7.3.15 [ATS_COMINDEP_00724] Transmission Of An I-PDU having MIXED
Tx Mode Consisting of Signal And Signal Group With Triggered On
Change Transfer Property ................................................................... 121
7.3.16 [ATS_COMINDEP_00725] Transmission Of An I-PDU having
DIRECT Tx Mode Consisting of Signal And Signal Group with
TRIGGERED WITHOUT REPETITION Transfer Property .................. 123
7.3.17 [ATS_COMINDEP_00726] Transmission Of An I-PDU Having MIXED
Tx Mode Consisting of Signal And Signal Group with TRIGGERED
WITHOUT REPETITION Transfer Property......................................... 124
7.3.18 [ATS_COMINDEP_00727] Transmission Of An I-PDU having MIXED
Tx Mode Consisting of Signal And Signal Group with TRIGGERED
ON CHANGE WITHOUT REPETITION Transfer Property .................. 125
7.3.19 [ATS_COMINDEP_00728] Triggered Transmission Of An I-Pdu With
MIXED Mode And Minimum Delay Timer Configured .......................... 127
7.3.20 [ATS_COMINDEP_00729] Transmit I-PDU Callout With Tx Mode
PERIODIC ........................................................................................... 128
MIXED ................................................................................................. 129
7.3.22 [ATS_COMINDEP_00731] Verify The Update Bits In An IPDU With
TX MODE DIRECT when Com_Sendsignal / Com_SendSignalGroup
is invoked............................................................................................. 130
TX MODE PERIODIC when Com_Sendsignal /
Com_SendSignalGroup is invoked ...................................................... 131
MIXED TX MODE when Com_Sendsignal / Com_SendSignalGroup
is invoked............................................................................................. 132
7.3.25 [ATS_COMINDEP_00734] Signal Routing When Source And
Destination Signals/signal group have Update Bit And Update Bit Of
The Received Signal Is Not Set ........................................................... 134
7.3.26 [ATS_COMINDEP_00735] Signal Routing When Source Signals Has
Update Bit And Destination Signals has no Update Bit And Update Bit
Of The Received Signal Is Not Set ...................................................... 135
Update Bit And Destination Signals has no Update Bit With Update
Bit Of The Received Signal Is Set ....................................................... 136
7.3.28 [ATS_COMINDEP_00737] The Filter Mechanism Of
“MASKED_NEW_DIFFERS_MASKED_OLD” On Reception Of An I-
Pdu ...................................................................................................... 137
8 RS_BRF_01648 - Large Data Type ............................................................... 139
8.1 General Test Objective and Approach...................................................... 139
8.1.1 Test System......................................................................................... 139
8.1.2 Test Configuration ............................................................................... 140
8.1.3 Test Case Design ................................................................................ 143
8.2 Re-usable Test Steps ............................................................................... 143
bus
8.3 Test Cases ............................................................................................... 143
8.3.1 [ATS_COMINDEP_00233] DIRECT TP transmission ......................... 143
8.3.2 [ATS_COMINDEP_00234] PERIODIC TP transmission ..................... 145
8.3.3 [ATS_COMINDEP_00235] MIXED TP transmission ........................... 146
8.3.4 [ATS_COMINDEP_00236] Dynamic send message ........................... 148
8.3.5 [ATS_COMINDEP_00238] Stop Ipdu group even if TP transmission
is not complete .................................................................................... 149
8.3.6 [ATS_COMINDEP_00275] Stop Ipdu group even if TP Reception is
not complete ........................................................................................ 151
8.3.7 [ATS_COMINDEP_00739] Unsuccessful Transmission Of An I-PDU
Consisting Of A Dynamic Signal With Periodic Mode And Having
ComTransferProperty As TRIGGERED ............................................... 153
Consisting Of A Dynamic Signal Having ComTransferProperty As
PENDING ............................................................................................ 154
8.3.9 [ATS_COMINDEP_00741] Reception Of Dynamic Length I-PDU ....... 155
8.3.10 [ATS_COMINDEP_00742] Reception Of A Large I-PDU Via The TP
Interface............................................................................................... 155
8.3.11 [ATS_COMINDEP_00743] Data Sequence control when Received I-
PDU counter is greater than expected I-PDU counter + threshold ...... 156
9 Miscellaneous features .................................................................................. 158
9.1 General Test Objective and Approach...................................................... 158
9.1.1 Test System......................................................................................... 158
9.1.2 Test Configuration ............................................................................... 159
9.2 Re-usable Test Steps ............................................................................... 159
9.3 Test Cases ............................................................................................... 159
9.3.1 [ATS_COMINDEP_00744] Check The Functionality Of
PduR_EnableRouting And PduR_DisableRouting............................... 159
9.3.2 [ATS_COMINDEP_00745] Interface PDU Transmission During
Singlecast When Source PDU Belongs To Com And Destination PDU
Belongs To CanIf ................................................................................. 160
9.3.3 [ATS_COMINDEP_00746] Interface PDU Transmission During
Multicast When Source PDU Is From Com Module And Destination
PDU Belongs To Lower Layer (CanIf, LinIf, FRIF)............................... 161
9.3.4 [ATS_COMINDEP_00747] Frame Gateway From CanIf To LinIf,
CanIf And FrIf ...................................................................................... 162
9.3.5 [ATS_COMINDEP_00748] Tp PDU Transmission During Singlecast
When Source PDU Belongs To Com and Destination PDU Belongs
To CanTp............................................................................................. 163
9.3.6 [ATS_COMINDEP_00749] Frame Gateway From CanTp To LINTP,
CanTp and FrTp .................................................................................. 164

bus
1 Acronyms and abbreviations
Abbreviation / Description:
Acronym:
AT Acceptance Test
CAN Controller Area Network
ECU Electronic Control Unit
LT Lower Tester
NM Network Management
PCO Point of Control and Observation
PDU Protocol Data Unit
RfC Request for Change
Rx Reception
SUT System Under Test
SWC Software Component
TCP Test Coordination Procedures
Tx Transmission
UT Upper Tester
LdCom Large Data COM

bus
2 Scope
The following test cases are used to verify the correct behavior of all the
communication features which are independent from the bus (i.e. bus can be CAN,
LIN, FlexRay or Ethernet).
Each test case documents for which releases of the AUTOSAR software
specification it can be used:
 When test cases are known to be applicable for a release, this is mentioned in
the “AUTOSAR Releases” field of the test case specifications.
You can find a summary of the applicability of all test cases to the software
specification releases in the “AUTOSAR_TR_ATSReleaseApplicability”
document.
 When test cases are known to require adaptations (in their configuration
requirements or test sequences), this is mentioned in the “Needed Adaptation
to other Releases” field of the test case specifications.

bus
3 RS_BRF_01600 - Timeout Handling

3.1 General Test Objective and Approach
This Test Specification intends to cover the Timeout Handling feature of the Com as
described in the AUTOSAR Feature [RS_BRF_01600].
The tests use a test bench environment and Embedded Software Components that
use the feature.
This test case document has been established to cover the following features:
This specification gives the description of required tests environments (test bench,
uses case, arxml files) and detailed tests cases for executing tests.
3.1.1 Test System

3.1.1.1 Overview on Architecture
In order to cover the required features / sub-features coverage, the environment has
been separated in several uses case.
3.1.1.1.1 Use case 01.01: Deadline Monitoring
For this use case, the aim is to test the Timeout Handling feature.
The test system architecture consists of Test Bench that executes only test
sequencer and gives actions request through Test coordination Procedures to
embedded SWC.

bus
The test architecture depends on the bus chosen for the test:
- CAN Bus:
Test System SUT
SWC
Lower (Upper
TCP (Test Coordination Procedures)
Tester Test)
PCO
Runtime Environment (RTE)
Test Bench Com ComM or BswM
PduR
Basic Software (BSW)
CanIf
Can
PCO Microcontroller
CAN Bus
- FlexRay Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
FrIf
Fr
PCO Microcontroller
FlexRay Bus

bus
- LIN Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
LinIf LinSM
Lin
PCO Microcontroller
LIN Bus
3.1.1.2 Specific Requirements

Not Applicable.
3.1.1.3 Test Coordination Requirements

Not Applicable.

bus
3.1.2 Test Configuration
This section describes sets of requirements on configuration. These sets are later
referenced by test cases. No configuration files are provided. They need to be
developed when the test suite is implemented.
3.1.2.1 Required ECU Extract of System Description Files
A Mode-Switch Interface IF_AT_SwC_ActionsBswM must be created. The SWC

Upper Tester is the owner of this state machine and BswM read the state through
BswMMode Port. BswM shall launch actions according to following table (check 3.3
Test Cases for details):
ModeDeclaration BswM Actions

OnEntry:
IPDU_ACTIVATED
-Start IpduGroup
OnEntry:
IPDU_DEACTIVATED
-Stop IpduGroup
OnEntry:
IPDU_OFF_ON -Stop IpduGroup
-Re-start IpduGroup
OnEntry:
TXMODE_TRUE
-SwitchIPduMode to TRUE
OnEntry:
TXMODE_FALSE
-SwitchIPduMode to FALSE
OnEntry:
TRIG_IPDU_SEND
-TriggerIpduSend
OnEntry:
LIN_START_SCHEDULE
-Start LIN Schedule Table
OnEntry:
IPDU_ACTIVATED_LIN_ST
-Start IpduGroup
ART_SCHEDULE

bus
Unless a different configuration is specified in test case, Sender/Receiver Ports used

for communication Non queued Data Element and Explicit Data access for
associated runnables.
The communication database is depicted below:
IPduGroup IPdu SignalGroup Signal Tx ECU Rx ECU

AT_100_Ipdu_ AT_100_Sg1 AT_100_Sg1 TestBench SUT
1 AT_100_Sg2 AT_100_Sg2 TestBench SUT
AT_100_IpduGroup
AT_100_Ipdu_ AT_100_Sg3 AT_100_Sg3 TestBench SUT
2 AT_100_Sg4 AT_100_Sg4 TestBench SUT
AT_101_Ipdu_ AT_101_GrSg1
AT_101_IpduGroup AT_101_SgGr1 TestBench SUT
2 AT_101_GrSg2
AT_102_TxIpd
AT_102_IpduGroup AT_102_TxSg1 AT_102_TxSg1 SUT TestBench
u_1
AT_104_Ipdu_
AT_104_IpduGroup AT_104_Sg1 AT_104_Sg1 TestBench SUT
1
AT_105_Ipdu_
AT_105_IpduGroup AT_105_Sg2 AT_105_Sg2 TestBench SUT
3
AT_107_Ipdu_ AT_107_GrSg1
AT_107_IpduGroup AT_107_SgGr2 TestBench SUT
4 AT_107_GrSg2
Some of the test cases requires specific signal transfer properties and unique IPDU
structure to fulfil the test requirements. These are listed here.
AT_738 Signal Properties:

SWCTemplate::Co SWCTempla
Fibex::Fib mmunication::Rec te::Commun
exCore::C eiverComSpec.aliv ication:Rece
Com
oreComm eTimeout and iverComSpe
First
unication:: SystemTemplate::F Com Timeout Notification c::Nonqueu
Timeou
ISignalTo ibex::FibexCore::C edReceiver
t (ms)
PduMappi oreCommunication ComSpec.h
ng ::SignalPort.timeou andleTimeo
t utType
Sn_83 150 500 App_Rte_Com_CbkRxTOut_Sn_81 NONE
Sn_84 50 500 App_Rte_Com_CbkRxTOut_Sn_82 NONE
Sg84 150 500 App_Rte_Com_CbkRxTOut_Sg80 NONE
AT_738_IPDU_Structure:
B7
B6
B5 Sn_83
B4 Sg84_2
B3
B2 Sn_84
B1 Sg84_1
B0
D7 D6 D5 D4 D3 D2 D1 D0
bus
3.1.2.2 Required ECU Configuration Description Files

No specific configuration requirements for ECU Configuration files as they can be
derived from EcuExtract.
3.1.2.3 Required Software Component Description Files

No specific configuration requirements for Software Components.
3.1.2.4 Mandatory vs. Customizable Parts

Mandatory parameters are listed in Tests Cases (see 3.3 Test Cases).
Customizable parameters are (these values are test case independent):

 ComSignalType (ISignal.networkRepresentationProps.swBaseType),
ComSignalLength (baseTypeSize) and ComBitSize (ISignal.length) => must
be consistent to associated dataElement
 ComSignalInitValue (ISignal.initValue)
 PduLength (Pdu.length)
 ComBitPosition (ISignalToIPduMapping.startPosition) and
ComUpdateBitPosition (ISignalToIPduMapping.updateIndicationBitPosition)
values => the location of these elements in the pdu
 frames identifiers
3.1.3 Test Case Design

Not Applicable.
3.2 Re-usable Test Steps

Not Applicable.
3.3 Test Cases
3.3.1 [ATS_COMINDEP_00100] Managing Rx signal deadline timeout with

notification
Test Objective Managing Rx signal deadline timeout with notification
ID ATS_COMINDEP_00100 AUTOSAR 3.2.1|3.2.2|4.0.3|4.1.1|4.2.1|4.2.2
Releases
Affected Com State reviewed
Modules
Trace to ATR: ATR_ATR_00030
Requirement ATR: ATR_ATR_00112
on Acceptance
Test Document
Trace to SWS COM: SWS_Com_00291
Item COM: SWS_Com_00292
COM: SWS_Com_00500
COM: SWS_Com_00772
Requirements / Configuration use case : UC01.01

bus
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): AT_100_Ipdu_1, AT_100_Ipdu_2
Parameters - ComIPduDirection(CommConnectorPort.communicationDirection) = RECEIVE
ComSignal(ISignalToPduMapping): AT_100_Ipdu_1->AT_100_Sg1
- ComUpdateBitPosition(updateIndicationBitPosition)
- ComTimeout(ReceiverComSpec.aliveTimeout) = 600ms
- ComUpdateBitPosition(updateIndicationBitPosition)
- ComTimeout(ReceiverComSpec.aliveTimeout) = 300ms
- No ComUpdateBitPosition(updateIndicationBitPosition)
- ComTimeout(ReceiverComSpec.aliveTimeout) = 1s
- No ComUpdateBitPosition(updateIndicationBitPosition)
- ComTimeout(ReceiverComSpec.aliveTimeout) = 4s
For all ComSignal/ComSignalGroup (ISignalToPduMapping):

- ComTimeoutNotification(no upstream template parameter) is configured
- ComRxDataTimeoutAction (NonqueuedReceiverComSpec.handleTimeoutType) =
NONE
Summary The SUT is started. The Rx IPdu 1, IPdu 2 are sent periodically on the bus, with the
update-bit of the Signal 1 and Signal 2 set to 1. Two use case must be tested:
- use case with IPdu 1 (Ignoring IPDU base timeout handling if all signals are
configured with update-bit):
1- After a while, the update-bit of the Signal 1 is set to 0
2- After Signal 1 Timeout, the update-bit of the Signal 2 is set to 0
- use case with IPdu 2 (Smallest configured timeout for signals without update bits):
1- After a while, stop sending IPdu 2
2- Check Signal 3 and Signal 4 Deadline timeout
Awaiting result for first use case with IPdu 1 (Ignoring IPDU base timeout handling if
all signals are configured with update-bit):
 Deadline timeout occurs independently (with configured timeout value) for

the Signal 1 and Signal 2. The SUT must notify Deadline timeout to the
SWC.
 The value of the Signal 1 and Signal 2 must be the same as the last valid
received value.
Awaiting result for first use case with IPdu 2 (Smallest configured timeout for signals
without update bits):
 Deadline timeout occurs is the same for the Signal 3 and Signal 4 (Smallest
configured timeout). The SUT must notify Deadline timeout to the SWC.
 The value of the Signal 3 and Signal 4 must be the same as the last valid
received value.
Needed None
Adaptation to
other Releases
Pre-conditions The SUT is started.
The frames containing Rx AT_100_Ipdu_1, AT_100_Ipdu_2 are sent periodically
Signals values different from Init value

bus
Main Test Execution
Test Steps Pass Criteria
Step 1 [LT]
Set update-bit of AT_100_Sg1, AT_100_Sg2
with value 1
Step 2 [SWC] [SWC]
Check the update-bit of AT_100_Sg1 AND Return Value of Rte_IsUpdated for
AT_100_Sg2 (call to Rte_IsUpdated) Signal_1 is TRUE
Return Value of Rte_IsUpdated for
Signal_2 is TRUE
Step 3 [LT]
Set update-bit of the AT_100_Sg1 with value
0
Step 4 [SWC] [SWC]
Check the update-bit of Signal_1 (call to Return Value of Rte_IsUpdated for
Rte_IsUpdated) Signal_1 is FALSE
Step 5 [SWC] [SWC]
Waiting for 500ms The SUT must NOT notify the SWC
(<deadline_timeout=600ms - (Return Value of Rte_Read for
safety_margin=100ms>) AT_100_Sg1 is different from
RTE_E_MAX_AGE_EXCEEDED)
Step 6 [SWC] [SWC]
|Waiting for 200ms The SUT must notify the SWC
(<deadline_timeout=600ms + (Return Value of Rte_Read for
safety_margin=100ms> - 500ms) AT_100_Sg1 is
Step 7 [SWC] [SWC]
Get AT_100_Sg1 Value (Rte_Read) AT_100_Sg1 Value is the same as
the last valid received value
Step 8 [LT]
Set update-bit of the AT_100_Sg2 with value
0
Step 9 [SWC] [SWC]
Check the updatebit of AT_100_Sg2 (call to Return value of Rte_IsUpdated for
Rte_IsUpdated()) AT_100_Sg2 is FALSE
Step 10 [SWC] [SWC]
Wait for 200ms (<deadlinetimeout=300ms - The SUT must NOT notify the SWC
safetymarging=100ms>) (Return Value of Rte_Read for
AT_100_Sg2 is different from
Step 11 [SWC] [SWC]
Wait for 200ms ((deadlinetimeout + The SUT must notify the SWC
safetymargin) - 200ms) (Return value of Rte_Read for
AT_100_Sg2 is
Step 12 [LT]
Stop sending periodically the AT_100_Ipdu2
Step 13 [SWC] [SWC]
Wait for 900ms (min(deadlinetimeout The SUT must NOT notify the SWC:
GrSg3/GrSg4) - safetymargin) - Return Value of Rte_Read for
RTE_E_MAX_AGE_EXCEEDED
- Return Value of Rte_Read for
Step 14 [CP] [SWC]
bus
Wait for 200ms The SUT must notify the SWC:
AT_100_Sg3 is
AT_100_Sg4 is
Post- None
conditions
3.3.2 [ATS_COMINDEP_00101] Managing Rx signal group deadline timeout

with action REPLACE
Test Objective Managing Rx signal group deadline timeout with action REPLACE
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00772
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu):
ComSignalGroup(ISignalToPduMapping):
- ComUpdateBitPosition(updateIndicationBitPosition) is configured
- ComTimeout(ReceiverComSpec.aliveTimeout) is configured
REPLACE
Summary The SUT is started. The Rx IPdu 2 is sent periodically on the bus, with the update-
bit of the Signal Group 1 set to 1. After a while, the update-bit of the Signal Group 1
is set to 0.
Hint: To perform this test, the COM Bsw should be configured with
ComTimeOutNotification on SignalGroup level (not exist at ICC1 level).
Needed None
Adaptation to
other Releases
The frame containing Rx IPdu 2 is sent periodically
Signal value different from Init value
Main Test Execution

bus
Step 1 [LT]
Set update-bit of the SignalGroup_1 with
value 1
Step 2 [SWC] [SWC]
Check the update-bit of SignalGroup_1 (call Return Value of Rte_IsUpdated for
to Rte_IsUpdated) SignalGroup_1 is TRUE
Step 3 [LT]
Set update-bit of SignalGroup_1 with value 0
Step 4 [SWC] [SWC]
to Rte_IsUpdated) SignalGroup_1 is FALSE
Step 5 [CP]
Waiting for <deadline_timeout>
Step 6 [SWC] [SWC]
Get signalGroup_1 Value (Rte_Read()) Return Value of Rte_Read should be
equal to
SignalGroup_1 Value is set to
InitValue
Post- None
conditions
3.3.3 [ATS_COMINDEP_00102] Managing Tx Ipdu deadline timeout

Test Objective Managing Tx Ipdu deadline timeout
Releases
Modules
Requirement
on Acceptance
Test Document
COM: SWS_Com_00481
Reference
to Test In order to block sending of Tx IPdu 1, one of these means can be used:
Environment - If applied on CAN bus, the bus is overloaded by CAN frame (so that the Tx IPdu 1
cannot be sent by the SUT) or LowerTester stop its CAN Controller (Hint: In this
case, [BUSOFF detection Timer > Tx_deadline_timeout] and no rule in BswM shall
stop associated IpduGroup if BUSOFF is detected).
- If applied on FlexRay/LIN bus, Tester must be intrusive to block the notification

(lock interrupt, No TxConfirmation configured in FrIf/LinIf
Parameters - ComIPduDirection(CommConnectorPort.communicationDirection) = SEND
- ComTxModeTrue
(IPduTiming.TransmissionModeDeclaration.transmissionModeTrueTiming)
-- ComTxModeMode (TransmissionModeTiming) = PERIODIC (CyclicTiming)
ComSignal(ISignalToPduMapping):
bus
- DataSendCompletedEvent mapped on signal transmission (ComNotification is
configured)
Summary The SUT is started. The Tx IPdu 1 is sent periodically on the bus. After a while, the
sending of Tx IPdu 1 is blocked.
Expected result: The SUT must notify the SWC that the deadline timeout occurs for
the Tx IPdu 1.
Needed None
Adaptation to
other Releases
The frame containing Tx IPdu 1 is sent periodically.
Main Test Execution
Step 1 [LT]
Send application frames to the SUT
Step 2 [LT] [LT]
Check Tx IPdu_1 is received on the bus The Tx IPdu_1 is sent periodically by
SUT on the bus
Step 3 [LT]
Make correct transmission impossible
(e.g. stop acknowledging can frames,
overload, destroy frames, ...)
avoiding bus off handling by CanSM
Step 4 [SWC]
Update value of TxIPdu_1 -> TxSignal_1
(Rte_Write)
Step 5 [CP] [SWC]
Wait for <deadlinetimeout - safetymargin> Return Value of Rte_Feedback is
NOT RTE_E_TIMEOUT (The SUT
has NOT notified the SWC)
DataSendCompletedEvent NOT
called
Step 6 [SWC] [SWC]
Waiting for 2 x <safetymargin> Return Value of Rte_Feedback is
RTE_E_TIMEOUT (The SUT has
notified the SWC)
called
Post- None
conditions
3.3.4 [ATS_COMINDEP_00104] Disabling/Enabling Rx Deadline monitoring

Test Objective Disabling/Enabling Rx Deadline monitoring
Releases
Modules
bus
on Acceptance
Test Document
COM: SWS_Com_00486
COM: SWS_Com_00772
Reference
to Test
Environment
NONE
Summary The SUT is started. The Rx Deadline monitoring is disabled.
Use Case 1, Rx Deadline monitoring disabled:

The Rx IPdu 1 is sent periodically on the bus, with the update-bit of the Signal 1 set
to 1. After a while, the update-bit of the Signal 1 is set to 0.
Awaiting result :
 The SUT must NOT notify the SWC that the deadline timeout occurs for the
Signal 1.
Use Case 2, Rx Deadline monitoring enabled:
The SWC enables the Rx Deadline monitoring. The Rx IPdu 1 is sent periodically
on the bus, with the update-bit of the Signal 1 set to 1. After a while, the update-bit
of the Signal 1 is set to 0.
Awaiting result :
 The SUT must notify the SWC that the deadline timeout occurs for the
Signal 1.
Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC]
Disable Rx Deadline Monitoring (request
DeadlineMonitoringControl action to BswM)

bus
Step 2 [LT] [LT]
Send Rx IPdu_1 on the bus The Rx IPdu_1 is sent periodically on
the bus
Step 3 [LT]
Set update-bit of Signal_1 with value 1
Step 4 [SWC] [SWC]
Rte_IsUpdated) Signal_1 is TRUE
Step 5 [LT]
Step 6 [SWC] [SWC]
Step 7 [CP] [SWC]
Waiting for <deadline_timeout> The SUT must not notify the SWC
(Return Value of Rte_Read is
different from
Step 8 [SWC]
Enable Rx Deadline Monitoring (request
DeadlineMonitoringControl action to BswM)
Step 9 [LT]
Step 10 [SWC] [SWC]
Rte_IsUpdated) Signal_1 is TRUE
Step 11 [LT]
Step 12 [SWC] [SWC]
Step 13 [SWC] [SWC]
Waiting for <deadline_timeout> The SUT must notify the SWC
Post- None
conditions
3.3.5 [ATS_COMINDEP_00105] Managing Rx Ipdu deadline timeout without

notification
Test Objective Managing Rx Ipdu deadline timeout without notification
Releases
Modules
Requirement
on Acceptance
Test Document
COM: SWS_Com_00470
bus
COM: SWS_Com_00772
Reference
to Test
Environment
- ComUpdateBitPosition(updateIndicationBitPosition) is NOT configured
- ComTimeoutNotification(no upstream template parameter) is not present
REPLACE
If applied on Flexray bus:

- FlexRay Rx Frame in Dynamic slot
If applied on CAN/LIN bus:

- Normal Rx Frame
Summary The SUT is started. The Rx IPdu 3 is sent periodically on the bus. After a while, the
Rx IPdu 3 is stopped to be sent.
Awaiting result :
 The SUT must NOT notify the SWC that the deadline timeout occurs for Rx
IPdu 3.
 The value of the Signal 2 must be replaced by its Init value.
Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send periodically Rx IPdu_3 on the bus with The Rx IPdu_3 is sent periodically on
Signal_2 Value equal Value_1 the bus with Value_1
Step 2 [SWC] [SWC]
Read value of Signal_2 (Rte_Read) Signal_2 value is Value_1
Step 3 [LT] [LT]
Stop sending Rx IPdu_3 on the bus The Rx IPdu_3 is not sent on bus
Step 4 [CP]
Step 5 [SWC] [SWC]
Read value of Signal_2 (Rte_Read) The SUT must NOT notify the SWC
(Return Value of Rte_Read is NOT
Signal_2 Value is the Init Value
Post- None
conditions

bus
3.3.6 [ATS_COMINDEP_00107] Managing Rx signal group deadline timeout
with action NONE
Test Objective Managing Rx signal group deadline timeout with action NONE
Releases
Modules
Requirement
on Acceptance
Test Document
COM: SWS_Com_00772
Reference
to Test
Environment
ComSignalGroup(ISignalToPduMapping):
NONE
Summary The SUT is started. The Rx IPdu 4 is sent periodically on the bus, with the update-
bit of the Signal Group 2 set to 1. After a while, the update-bit of the Signal Group 2
is set to 0.
Awaiting result :
 The SUT must notify the SWC that the deadline timeout occurs for the
Signal Group 2.
 The value of the Signal Group 2 must be the same as the last valid received
value.
Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send Rx IPdu_4 on the bus with The Rx IPdu_4 should be sent
SignalGroup_2 value different from init value periodically on the bus
Step 2 [LT]
Set update-bit of SignalGroup_2 with value 1
Step 3 [SWC] [SWC]
to Rte_IsUpdated) SignalGroup_2 is TRUE
Step 4 [LT]

bus
Set update-bit of the SignalGroup_2 with
value 0
Step 5 [SWC] [SWC]
to Rte_IsUpdated) SignalGroup_2 is FALSE
Step 6 [CP]
Step 7 [SWC] [SWC]
Get signalGroup_2 Value (Rte_Read) The SUT must notify the SWC
SignalGroup_2 Value is the same as
the last valid received value
Post- None
conditions
3.3.7 [ATS_COMINDEP_00738] Signal With ComRxDataTimeoutAction Set To

NONE And Reception Deadline Monitoring Expires
Test Objective Signal With ComRxDataTimeoutAction Set To NONE And Reception Deadline
Monitoring Expires
ID ATS_COMINDEP_00738 AUTOSAR 4.0.3|4.2.1|4.2.2
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Requirements / none
Reference
to Test
Environment
Configuration For signal properties, please refer to "AT_738 Signal Properties:" in chapter 3.1.2.1
Parameters
For IPDU Rx_IPDU_DMTO_None Structure, please refer to
"AT_738_IPDU_Structure" in chapter 3.1.2.1
Summary The required functionality can be achieved by configuring the
ComRxDataTimeoutAction to NONE and using the configured timeout notification
for reception deadline monitoring.
Needed
Adaptation to
other Releases
Pre-conditions DUT shall be in Full communication state
Main Test Execution
Step 1 [LT] [SWC]
Transmit Rx_IPDU_DMTO_None frame Com Notification for the
packed with signals having valid values corresponding signals are called out
Step 2 [CP] [SWC]
Wait until the deadline monitoring timeout Com timeout notification functions for
bus
expires (e.g. 500) all signals are invoked.
Post- None
conditions

bus
4 RS_BRF_01616 - Initial Values

This Test Specification intends to cover the Initial Values feature of the Com as
use the feature.

bus
4.1.1 Test System
4.1.1.1.1 Use case 02.01: Initial Values
For this use case, the aim is to test the Initial Values features.
embedded SWC.
- CAN Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
CanIf
Can
PCO Microcontroller
CAN Bus
- FlexRay Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
FrIf
Fr
PCO Microcontroller
FlexRay Bus
- LIN Bus:
bus
Test System SUT

SWC
Lower (Upper
Tester Test)
PCO
PduR
LinIf LinSM
Lin
PCO Microcontroller
LIN Bus

Not Applicable.

Not Applicable.

bus


OnEntry:
IPDU_ACTIVATED
-Start IpduGroup
OnEntry:
IPDU_DEACTIVATED
-Stop IpduGroup
OnEntry:
-Re-start IpduGroup
OnEntry:
TXMODE_TRUE
OnEntry:
TXMODE_FALSE
OnEntry:
TRIG_IPDU_SEND
-TriggerIpduSend
OnEntry:
LIN_START_SCHEDULE
OnEntry:
-Start IpduGroup
ART_SCHEDULE

bus


AT_BRF01616_ AT_BRF01616_S
TestBench SUT
Sg1_1 g1_1
TestBench SUT
AT_BRF01616 Sg1_2 g1_1
_IpduRx1 AT_BRF01616_ AT_BRF01616_S
TestBench SUT
Sg1_3 g1_1
TestBench SUT
Sg1_4 g1_1
TestBench SUT
Sg2_1 g2_1
AT_BRF01616 AT_BRF01616_ AT_BRF01616_S
TestBench SUT
AT_BRF01616_Ipd _IpduRx2 Sg2_2 g2_2
uGroup AT_BRF01616_ AT_BRF01616_S
TestBench SUT
Sg2_3 g2_3
TestBench SUT
AT_BRF01616 Sg3_1 g3_1
_IpduRx3 AT_BRF01616_ AT_BRF01616_S
TestBench SUT
Sg3_2 g3_2
TestBench SUT
_IpduRx4 Sg4_1 g4_1
TestBench SUT
_IpduRx5 Sg5_1 g5_1
SUT TestBench
_IpduTx1 Sg6_1 g6_1
AT_721 Signal Transfer Properties:

Fibex::FibexCore::CoreCo Fibex::FibexCore::CoreCommuni
mmunication::ISignalToP cation::ISignalToIPduMapping.tra Com Notification
duMapping nsferProperty
Sn_01 PENDING Rte_ComCbkTAck_Sn_01
Sn_05 TRIGGERED Rte_ComCbkTAck_Sn_05
Sg1 PENDING Rte_ComCbkTAck_Sg1
Sg5 TRIGGERED Rte_ComCbkTAck_Sg5

bus
AT_721_PDU structure:
B7 Sn_01 Sg2_2
B6 Sg3_3 Sn_04
B5 Sg5_4 Sg4_2
B4 Sg3_2 Sg3_1
B3 Sn_05 Sg4_1 Sg1_3
B2 Sg2_1 Sn_03
B1 Sg5_2 Sg5_3 Sn_02
B0 Sg5_1 Sg1_2 Sg1_1
D7 D6 D5 D4 D3 D2 D1 D0
AT_722: ComNotification
Fibex::FibexCore::CoreCommunication::ISignalToPduMapping Com Notification
Sn_06 Rte_ComCbk_Sn_06
Sg6 Rte_ComCbk_Sg6
Sg7 Rte_ComCbk_Sg7
Sg8 Rte_ComCbk_Sg8
Sg9 Rte_ComCbk_Sg9
Sg10 Rte_ComCbk_Sg10
AT_722_IPDU_Structure
B7 Sg8_2 Sg9_4
B6 Sg7_3 Sn_10
B5 Sn_09
B4 Sg9_1 Sg7_2 Sg9_3
B3 Sn_08 Sg6_3 Sg10_2
B2 Sg10_1 Sn_07
B1 Sg9_2 Sg8_1 Sn_06
B0 Sg7_1 Sg6_2 Sg6_1
D7 D6 D5 D4 D3 D2 D1 D0


bus



Not Applicable.

bus
Not Applicable.
4.3 Test Cases
4.3.1 [ATS_COMINDEP_00075] Providing UINT8 initial value if Rx signal was

never received
Test Objective Providing UINT8 initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment
ComSignal or ComGroupSignal(ISignalToPduMapping):
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = UINT8
- ComSignalInitValue (ISignal.initValue) is configured (different from 0)
Summary The SUT is started. The Rx IPdu 1 is never sent to the SUT. One SWC gets the
value of the Signal 1.1.
Awaiting result : The Initial value is provided to the SWC.

Needed None
Adaptation to
other Releases
No frame is sent to the SUT
Main Test Execution
Step 1 [LT]
No Frame is sent to the SUT
Step 2 [LT] [LT]
Check Rx IPdu_1 The Rx IPdu_1 is never sent to the
SUT
Step 3 [SWC] [SWC]
Check value of the Signal_1_1 (Rte_Read()) UINT8 initial value provided
Post- None
conditions

bus
deadline timeout occurs
Test Objective Providing UINT8 initial value if Rx signal deadline timeout occurs
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
ComSignal or ComSignalGroup(ISignalToPduMapping):
REPLACE
Summary The SUT is started. The Rx IPdu 1 is sent periodically to the SUT. After a while, the
Rx IPdu 1 is stopped to be sent to the SUT. One SWC gets the value of the Signal
1.1.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send Rx IPdu_1 with Signal_1_1 Value_1 The Rx IPdu_1 is sent periodically to
(different from Signal_1_1 InitValue) the SUT
Step 2 [SWC] [SWC]
Check value of Signal_1_1 (Rte_Read()) Signal_1_1 Value is different from
InitValue (value from BUS is received)
Step 3 [LT] [LT]
Stop sending Rx IPdu_1 The Rx IPdu_1 is stopped to be sent
to the SUT
Step 4 [CP]
Wait for <deadline_timeout>
Step 5 [SWC] [SWC]
Post- None
conditions

bus

never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Post- None
conditions


bus
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
1.2.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Post- None
conditions

Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
1.3.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
4.3.7 [ATS_COMINDEP_00083] Providing SINT8 initial value if Rx signal was
never received
Test Objective Providing SINT8 initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = SINT8

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Check value of the Signal_1_4 (Rte_Read()) SINT8 initial value provided
Post- None
conditions

Test Objective Providing SINT8 initial value if Rx signal deadline timeout occurs
Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
1.4.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Post- None
conditions

Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
2.1.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Post- None
conditions

Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
2.2.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
4.3.13 [ATS_COMINDEP_00090] Providing BOOLEAN initial value if Rx signal
was never received
Test Objective Providing BOOLEAN initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = BOOLEAN

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]

Check value of the Signal_2_3 BOOLEAN initial value provided
Post- None
conditions
4.3.14 [ATS_COMINDEP_00091] Providing BOOLEAN initial value if Rx signal

Test Objective Providing BOOLEAN initial value if Rx signal deadline timeout occurs
Releases
bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = BOOLEAN
2.3.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 6 [SWC] [SWC]
Check value of the Signal_2_3 BOOLEAN initial value provided
Post- None
conditions

bus
4.3.15 [ATS_COMINDEP_00092] Providing FLOAT32 initial value if Rx signal
was never received
Test Objective Providing FLOAT32 initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = FLOAT32

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Check value of the Signal_3_1 (Rte_Read()) FLOAT32 initial value provided
Post- None
conditions

Test Objective Providing FLOAT32 initial value if Rx signal deadline timeout occurs
Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
3.1.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Check value of the Signal_3_1 (Rte_Read()) FLOAT initial value provided
Post- None
conditions

bus
4.3.17 [ATS_COMINDEP_00094] Providing UINT8_N initial value if Rx signal was
never received
Test Objective Providing UINT8_N initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = UINT8_N

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Check value of the Signal_3_2 (Rte_Read()) UINT8_N initial value provided
Post- None
conditions
4.3.18 [ATS_COMINDEP_00095] Providing UINT8_N initial value if Rx signal

Test Objective Providing UINT8_N initial value if Rx signal deadline timeout occurs
Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
- ComSignalType(ISignal.networkRepresentationProps.swBaseType) = UINT8_N
3.2.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Check value of the Signal_3_2 (Rte_Read()) Signal_3_2 Value is different from
Step 3 [LT] [LT]
Stop sending Rx IPdu_3 to the SUT The Rx IPdu_3 is stopped to be sent
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Check value of the Signal_3_2 (Rte_Read()) UINT8_N initial value provided
Post- None
conditions

bus
was never received
Test Objective Providing FLOAT64 initial value if Rx signal was never received
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00604
Reference
to Test
Environment

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT]
Step 2 [LT] [LT]
SUT
Step 3 [SWC] [SWC]
Post- None
conditions

Test Objective Providing FLOAT64 initial value if Rx signal deadline timeout occurs
Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
REPLACE
4.1.

Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Step 2 [SWC] [SWC]
Step 3 [LT] [LT]
to the SUT
Step 4 [CP]
Step 5 [SWC] [SWC]
Post- None
conditions

bus
4.3.21 [ATS_COMINDEP_00098] Providing initial value for Tx gatewayed signal
if Rx signal was never received
Test Objective Providing initial value for Tx gatewayed signal if Rx signal was never received
Releases
Modules
Requirement
on Acceptance
Test Document
COM: SWS_Com_00604
COM: SWS_Com_00701
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): IPdu_5
ComSignal or ComGroupSignal(ISignalToPduMapping): Signal_5_1

- ComSignalInitValue (ISignal.initValue) is configured (RxInitValue != 0)
ComIpdu(SignalIPdu): TxIPdu_1
- ComIPduDirection(CommConnectorPort.communicationDirection) = SEND
- ComTxIPduUnusedAreasDefault (unusedBitPattern) is configured
- ComTxModeTrue

- ComSignalInitValue (ISignal.initValue) is configured (TxInitValue != 0)
ComGwMapping (Gateway): Signal_5_1->Signal_6_1

- ComGwSource (Gateway.ISignalMapping)
-- ComGwSignal (ComSignal or ComSignalGroup or ComGroupSignal) => Rx
Signal_5_1
- ComGwDestination (Gateway.ISignalMapping)
-- ComGwSignal (ComSignal or ComSignalGroup or ComGroupSignal) => Tx
Signal_6_1
Summary The SUT is started. The Rx IPdu 5 is never sent to the SUT. The Tx IPdu 1 is sent
periodically by the SUT.
Awaiting result : The initial value (TxInitValue) must be sent in the Tx IPdu 1
Needed None
Adaptation to
other Releases
The Tx IPdu 1 is sent periodically by SUT
Main Test Execution
Step 1 [LT]
bus
Step 2 [LT] [LT]
SUT
Step 3 [CP]
Wait for 2 seconds
Step 4 [LT] [LT]
Check Signal_6_1 value of Tx IPdu_1 Signal_6_1 Initial value should be
sent by the SUT
Post- None
conditions
4.3.22 [ATS_COMINDEP_00099] Providing initial value for Tx gatewayed signal

if Rx signal deadline timeout occurs
Test Objective Providing initial value for Tx gatewayed signal if Rx signal deadline timeout occurs
Releases
Modules
Requirement
on Acceptance
Test Document
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): IPdu_5

- ComSignalInitValue (ISignal.initValue) is configured (RxInitValue != 0)
ComIpdu(SignalIPdu): TxIPdu_1
- ComTxModeTrue

- ComSignalInitValue (ISignal.initValue) is configured (TxInitValue != 0)
ComGwMapping (Gateway): Signal_5_1->Signal_6_1

- ComGwSource (Gateway.ISignalMapping)
-- ComGwSignal (ComSignal or ComSignalGroup or ComGroupSignal) => Rx
Signal_5_1
- ComGwDestination (Gateway.ISignalMapping)
-- ComGwSignal (ComSignal or ComSignalGroup or ComGroupSignal) => Tx
Signal_6_1
Summary The SUT is started. The Rx IPdu 5 is sent periodically to the SUT. The Tx IPdu 1 is
sent periodically by the SUT, which contains the same value as the one sent in the

bus
Rx IPdu 5.
After a while, the Rx IPdu 5 is stopped to be sent to the SUT.
Awaiting result : The initial value (RxInitValue) must be sent in the Tx IPdu 1
Needed None
Adaptation to
other Releases
The Rx IPdu 5 is sent periodically to the SUT
The Tx IPdu 1 is sent periodically by SUT
Main Test Execution
Step 1 [LT] [LT]
Step 2 [LT] [LT]
Check Tx IPdu_1 period The Tx IPdu_1 is sent periodically by
the SUT
Step 3 [LT] [LT]
Check Signal_6_1 value of Tx IPdu_1 Signal_6_1 Value is different from
InitValue
Tx Signal_6_1 = Rx Signal_5_1
Value_1
Step 4 [LT]
Stop sending Rx IPdu_5 to SUT.
Step 5 [LT] [LT]
Check Rx IPdu_5 The Rx IPdu_5 is stopped to be sent
to the SUT
Step 6 [CP]
Step 7 [LT] [LT]
Check Signal_6_1 value of Tx IPdu_1 Signal_6_1 Initial value should be
sent by the SUT
Post- None
conditions
4.3.23 [ATS_COMINDEP_00721] Packing Of IPdu Data

Test Packing Of IPdu Data
Objective
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
bus
Requirements none
/ Reference
to Test
Environment
Configuration Signals and their transfer properties: Please refer to "AT_721 Signal Transfer
Parameters Properties" in chapter 4.1.2.1
Tx IPDU STRUCTURE: Please refer to "AT_721_PDU structure" in chapter 4.1.2.1
Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = DIRECT
Fibex::FibexCore::CoreCommunication.EventControlledTiming.numberOfRepetitions=
2
Fibex::FibexCore::CoreCommunication::EventControlledTiming.repetitionPeriod =
300 ms
Summary The transmission of assigned I-PDU shall be verified using Com transmission
confirmation of the respective signals and signal groups along with data observed on
the trace log.
Needed
Adaptation to
other
Releases
Pre- DUT shall be in full communication
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write for Signal_01 Signal_02 E_OK shall be returned for the
Signal_Group_1 and with valid data requests
Step 2 - [LT]
Frame shall be observed on the bus by
the DUT twice for every Com
Transmission Mode Repetition Period
Step 3 - [SWC]
Com transmission confirmation for the
configured signals and signal groups
shall be invoked
Step 4 [SWC] [SWC]
Call Rte_Write for Signal_03 Signal_Group_4 E_OK shall be returned for the request
and Signal_Group_5 with valid data
Step 5 - [LT]
Step 6 - [SWC]
shall be invoked
Post- None
conditions
4.3.24 [ATS_COMINDEP_00722] Unpacking Of IPdu Data

Test Objective Unpacking Of IPdu Data
Releases
bus
Modules
Trace to
Requirement
on Acceptance
Test Document
Requirements / none
Reference
to Test
Environment
Configuration For signals and their Notification, please refer to "AT_722: ComNotification" in
Parameters chapter 4.1.2.1
For RX PDU Structure, please refer to "AT_722_IPDU_Structure" in chapter 4.1.2.1
Summary The unpacking of I-PDU data shall be verified using Com receive acknowledgement
of the respective signals and signal groups.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [SWC]
Tester to send the frame with 0x69 0x55 Com notification for the signals and
0x0D 0x85 0x40 0x54 0xAA0x0A value signal groups shall be invoked
Step 2 [SWC] [SWC]
Call Rte_read for Signal_Group_6, E_OK shall be returned for all the
Signal_Group_7, Signal_Group_8, requests along with the transmitted
Signal_06, Signal_07, Signal_08, Signal_09, data
Signal_10, Signal_Group_9 and
Signal_Group_10
Post- None
conditions

bus
5 RS_BRF_01632 - Data Consistency

This Test Specification intends to cover the Data Consistency feature of the Com as
use the feature.
5.1.1 Test System

5.1.1.1.1 Use case 03.01: Data consistency on Rx way and Tx way
For this use case, the aim is to test the Data Consistency features.
embedded SWC.

bus
- CAN Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
CanIf
Can
PCO Microcontroller
CAN Bus
- FlexRay Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
FrIf
Fr
PCO Microcontroller
FlexRay Bus

bus
- LIN Bus:
Test System SUT
SWC
Lower (Upper
Tester Test)
PCO
PduR
LinIf LinSM
Lin
PCO Microcontroller
LIN Bus

Not Applicable.

Not Applicable.


bus


OnEntry:
IPDU_ACTIVATED
-Start IpduGroup
OnEntry:
IPDU_DEACTIVATED
-Stop IpduGroup
OnEntry:
-Re-start IpduGroup
OnEntry:
TXMODE_TRUE
OnEntry:
TXMODE_FALSE
OnEntry:
TRIG_IPDU_SEND
-TriggerIpduSend
OnEntry:
LIN_START_SCHEDULE
OnEntry:
-Start IpduGroup
ART_SCHEDULE


bus

AT_50_GrSg1
AT_50_IpduGroup AT_50_Ipdu1 AT_50_SgGr1 SUT TestBench
AT_50_GrSg2
AT_51_Ipdu1 AT_51_Sg1 AT_51_Sg1 TestBench SUT
AT_51_IpduGroup AT_51_GrSg1
AT_51_Ipdu2 AT_51_SgGr1 TestBench SUT
AT_51_GrSg2
AT_72_IpduGroup AT_72_Ipdu AT_72_Sg1 AT_72_Sg1 SUT TestBench
AT_74_GrSg1
AT_74_IpduGroup AT_74_Ipdu AT_74_SgGr1 TestBench SUT
AT_74_GrSg2





Not Applicable.

Not Applicable.
5.3 Test Cases
5.3.1 [ATS_COMINDEP_00050] Invalidating a Tx signal group when invalidated

by the SWC
Test Objective Invalidating a Tx signal group when invalidated by the SWC
Releases

bus
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): TxIPdu_1
- ComTxModeTrue
ComSignalGroup(ISignalToPduMapping): SgGr1
- ComGroupSignal(ISignalToPduMapping): GrSg1
-- ComSignalDataInvalidValue (SwDataDefProps.invalidValue) is configured
Summary The SUT is started. A SignalGroup is sent periodically by the SUT. The SWC
invalidates The SignalGroup.
Awaiting result : The SUT must invalidate each GroupSignal of the SignalGroup.
Needed None
Adaptation to
other Releases
The Tx IPdu 1 is sent periodically on the bus
Main Test Execution
Step 1 [SWC] [LT]
Update Tx IPdu_1 SgGr1 (Rte_Write()) with The Tx IPdu_1 is sent periodically on
value different from Invalid_Value the bus
SgGr1 is updated
Group signal GrSg1 value is different
from GrSg1_Invalid_Value
Group signal GrSg2 value is different
from GrSg2_Invalid_Value
Step 2 [SWC] [LT]
Invalidate the SignalGroup SgGr1 SgGr1 is updated
(Rte_Invalidate()) Group signal GrSg1 value is
GrSg1_Invalid_Value
Group signal GrSg2 value is
GrSg2_Invalid_Value
(The SUT has invalidated each
GroupSignal of the SignalGroup)
Post- None
conditions

bus
5.3.2 [ATS_COMINDEP_00051] Notifying the SWC when a signal or a signal
group is received with invalid data
Test Objective Notifying the SWC when a signal or a signal group is received with invalid data
Releases
Modules
Requirement
on Acceptance
Test Document
COM: SWS_Com_00717
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): RxIPdu_1
ComSignal(ISignalToPduMapping): Sg1
- ComSignalDataInvalidValue (SwDataDefProps.invalidValue) is configured
- ComInvalidNotification (no upstream template parameter) is configured
- ComDataInvalidAction (PortInterface.InvalidationPolicy) = NOTIFY
ComIpdu(SignalIPdu): RxIPdu_2
- ComIPduDirection(CommConnectorPort.communicationDirection) = RECEIVE
- ComDataInvalidAction (PortInterface.InvalidationPolicy) = NOTIFY
- ComGroupSignal(ISignalToPduMapping): GrSg1/GrSg2
-- ComInvalidNotification (no upstream template parameter) is configured
Summary This test case validates notification to SWC when receiving a signal in a frame with
InvalidValue, and when receiving a groupsignal with invalid value inside a
signalgroup.
Needed None
Adaptation to
other Releases
Pre-conditions The SUT is started
Main Test Execution
Step 1 [LT] [LT]
Send periodically Rx IPdu_1 with Sg1 The Rx IPdu_1 is sent periodically to
Value_1 (different from Sg1 InitValue) the SUT
Step 2 [SWC] [SWC]
Check value of Sg1 (Rte_Read()) Return value of Rte_Read is
RTE_E_OK
Sg1 Value is different from InitValue
(value from BUS is received)
Step 3 [LT]
Send periodically Rx IPdu_1 with Sg1
INVALID value
Step 4 [SWC] [SWC]
bus
Check value of Sg1 (Rte_Read()) Return value of Rte_Read is
RTE_E_INVALID
Sg1 Value is the last valid value
Step 5 [LT] [LT]
Send periodically Rx IPdu_2 with: The Rx IPdu_2 is sent periodically to
GrSg1 value = GrSg1_Value1 the SUT
GrSg2 value = GrSg2_Value1 (different from
SgGr1 InitValue)
Step 6 [SWC] [SWC]
Check value of SgGr1 (Rte_Read()) Return value of Rte_Read is
RTE_E_OK
GrSg1_Value1
GrSg2_Value1
Step 7 [LT]
Send periodically Rx IPdu_2 with:
GrSg1 value = GrSg1_InvalidValue
GrSg2 value = GrSg2_Value1
(only 1 GroupSignal INVALID)
Step 8 [SWC] [SWC]
RTE_E_INVALID
GrSg1_Value1
GrSg2_Value1
Post- None
conditions
5.3.3 [ATS_COMINDEP_00072] Invalidating a Tx signal when invalidated by the

SWC
Test Objective Invalidating a Tx signal when invalidated by the SWC
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): TxIPdu_1
- ComTxModeTrue
bus
- ComSignalDataInvalidValue (SwDataDefProps.invalidValue) is configured
Summary The SUT is started. A signal is sent periodically by the SUT. The SWC invalidates
this signal.
Awaiting result : The SUT must invalidate the signal.

Needed None
Adaptation to
other Releases
The Tx IPdu 1 is sent periodically on the bus
Main Test Execution
Step 1 [SWC] [LT]
Update Tx IPdu_1 Sg1 (Rte_Write()) with The Tx IPdu_1 is sent periodically on
value different from Invalid_Value the bus
Sg1 is updated
Signal Sg1 value is different from
Sg1_Invalid_Value
Step 2 [SWC] [LT]
Invalidate the Signal Sg1 (Rte_Invalidate()) Sg1 is updated
Signal Sg1 value is
Sg1_Invalid_Value
(The SUT has invalidated the signal)
Post- None
conditions
5.3.4 [ATS_COMINDEP_00074] Replacing by the init value when a signal group

is received invalid
Test Objective Replacing by the init value when a signal group is received invalid
Releases
Affected State reviewed
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): RxIPdu_1
- ComDataInvalidAction (PortInterface.InvalidationPolicy) = REPLACE
bus
-- ComInvalidNotification (no upstream template parameter) is configured
Summary The SUT is started. The Rx IPdu 1 is sent periodically to the SUT. Inside this
Frame, there is one signal group.
One group signal inside this signal group is set INVALID.
Awaiting result : The SUT shall replace the values of all group signals by their init
values.
Needed None
Adaptation to
other Releases
Pre-conditions The SUT is started
The Rx IPdu 1 is sent periodically to the SUT
Main Test Execution
Step 1 [LT] [LT]
Send periodically Rx IPdu_1 with: The Rx IPdu_1 is sent periodically to
GrSg1 value = GrSg1_Value1 the SUT
(different from SgGr1 InitValue)
Step 2 [SWC] [SWC]
RTE_E_OK
GrSg1_Value1
GrSg2_Value1
Step 3 [LT]
Send periodically Rx IPdu_1 with:
GrSg1 value = GrSg1_InvalidValue
(only 1 GroupSignal INVALID)
Step 4 [SWC] [SWC]
RTE_E_OK
GrSg1_Value_Init
GrSg2_Value_Init
(The SUT has replaced the values of
whole Group signals by their init
values)
Post- None
conditions

bus
6 RS_BRF_01649- LdCom data transfer (Bus independent)

This Test Specification intends to cover communication features of array type
signals, using LdCom as Interaction Layer, independent of underlying bus as
described in AUTOSAR Feature [RS_BRF_01649].
The tests use a Test Bench environment and Embedded Software Components that
uses the feature.
Figure 1: Mindmap of features covered and not covered in the test cases
This specification gives the description of required test environment (Test Bench,
Use cases, arxml files) and detailed test case for executing tests.
6.1.1 Test System

In order to cover the required features/sub-features, the environment has been
separated into several Use cases.

bus
Figure 2: Test System architecture
The Test System architecture consists of Test Bench that executes only test
sequences and gives action request through test coordination procedures to
embedded SWC.
6.1.1.1.1 Use case 06.01: Data Transfer of Array Signal of Size lesser than or
equal to<BUS> Capability
For this use case, the aim is to test data transfer features of LdCom, for array signal
of length lesser than or equal to underlying bus capability.
6.1.1.1.2 Use case 06.02: Data Transfer of Array Signal of size more than
<BUS> Capability
For this use case, the aim is to test data transfer features of LdCom, for array signal
of length greater than underlying bus capability.

Not Applicable.

Not Applicable.

referenced by test cases. No configuration files are provided, they need to be

bus
Figure 3: Required SWC description
From Software Component point of view, for each test case, the communication
interfaces are defined as follows:
Port name Data Data element Mapping Type

element
type
<TestCaseName>_<signalname> UINT8_N <signalname> <signalname> signal
Table 1: SWC Interface used
Therefore ports and signals names change according to Test Case number, but the
building rule is the same.
For API calls Rte_Write(), Rte_Send(), Rte_Read(),Rte_Receive(), Rte_Feedback()

refer AUTOSAR_SWS_RTE.pdf.
For API calls Rte_LdComCbkTpRxIndication, Rte_LdComCbkTxConfirmation,

Rte_LdComRxIndication, Rte_LdComCbkTpTxConfirmation refer to Specification of
Module Efficient COM for Large Data.
6.1.2.1.1 Use Case 06.01: Data Transfer of Array Signal of Size lesser than or
equal to<BUS> Capability
bus
IPdu Signal TxECU RxECU

AT_1470_IPdu AT_1470_Sg1 SUT TestBench
AT_1471_IPdu AT_1471_Sg1 TestBench SUT
Table 2: Communication Database
6.1.2.1.2 Use case 06.02: Data Transfer of Array Signal of size more than
<BUS> Capability
IPdu Signal TxECU RxECU

Table 3: Communication Database

No specific configuration requirements for ECU Configuration files, as they can be


Mandatory parameters are:
 ISignalToIPduMapping.startPosition => 0
 ISignalToIPduMapping.packingByteOrder =>Opaque
 ISignalToIPduMapping.transferProperty =>triggered/
triggeredWithoutRepetition
See 6.3 Test Cases for further details.

 FlexRay, CAN frames identifiers

Not Applicable.

Not Applicable.

bus
6.3 Test Cases
6.3.1 [ATS_COMINDEP_01470] LdCom Transmission using <Bus>IF API and
Notification for PDU Transfer
Test Objective LdCom Transmission using <Bus>IF API and Notification for PDU Transfer
ID ATS_COMINDEP_01470 AUTOSAR 4.2.1|4.2.2
Releases
Affected LdCom, PduR, BusIf, BusDrv State reviewed
Modules
on Acceptance
Test Document
Trace to SWS LargeDataCOM: SWS_LDCOM_00046
Item
Requirements / Use Case UC06.01
Reference
to Test
Environment
Configuration LdComIPdu(SignalIPdu): AT_1470_IPdu(normal I-PDU)
Parameters -LdComApiType = LDCOM_IF
-LdComIPduDirection(CommConnectorPort.communicationDirection) =
LDCOM_SEND
-LdComTxConfirmation = Rte_LdComCbkTxConfirmation_Sg1
LdComSignal(ISignalToPduMapping): Sg1
-SignalLength(baseTypeSize) < Size of <BUS> capability
-SystemSignal.networkRepresentationProps.swBaseType = UINT8_N
-DataSendCompletedEvent mapped on TxConfirmation
PduRRoutingPath:
-Routing path for LdComIPdu with PduRSrcBswModuleRef = BswMod_LdCom
-PduRDestPdu with PduRDestBswModuleRef = BswMod_<Bus>If
Summary - To check that application layer can initiate a LdCom transmission via IF-API. As
this is indirect testing for transmission confirmation, notification is given to software
component of Upper Tester about transmission of signal.
Needed n/a
Adaptation to
other Releases
Pre-conditions Com stack is initialized
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write() for Port AT_1470_Sg1 with Rte_Write() shall return RTE_E_OK.
Signal value AT_1470_Sg1_Value_1.
Step 2 [LT] [LT]
Monitor and validate the frame on bus. Frame shall be observed on bus with
data transmitted by SUT.
Step 3 - [SWC]
Rte_LdComCbkTxConfirmation API
for the signal is invoked for the signal.
DataSendCompleted Event
bus
is activated for the same.
Post- Not Applicable
conditions
6.3.2 [ATS_COMINDEP_01471] LdCom Reception using <Bus>IF API

Test Objective LdCom Reception using <Bus>IF API
Releases
Affected LdCom, PduR, BusIf, BusDrv State reviewed
Modules
on Acceptance
Test Document
Item
Reference
to Test
Environment
Parameters -LdComApiType = LDCOM_IF
LDCOM_RECEIVE
-LdComRxIndication = Rte_LdComCbkRxIndication_Sg1
LdComSignal(ISignalToPduMapping): Sg1
-SignalLength(baseTypeSize) < Size of <BUS> capability
-DataReceivedEvent mapped on RxIndication
PduRRoutingPath:
-Routing path for LdComIpdu with PduRSrcBswModuleRef = BswMod_<Bus>If
-PduRDestPdu with PduRDestBswModuleRef = BswMod_LdCom
Summary -To check application can receive LdCom data via IF-API.
Needed n/a
Adaptation to
other Releases
Pre-conditions Com stack is initialized.
Main Test Execution
Step 1 [LT] [SWC]
Send the signal AT_1471_Sg1 with Rte_LdComRxIndication API is

AT_1471_Sg1_Value_1. invoked for the signal and
DataReceivedEvent is activated for
the same.
Step 2 [SWC] [SWC]
Call Rte_Read() for Signal AT_1471_Sg1. Rte_Read() shall return RTE_E_OK.
AT_1471_Sg1_value is
bus
AT_1471_Sg1_Value_1.
conditions
6.3.3 [ATS_COMINDEP_01472] LdCom Transmission using <Bus>TP API and

Notification for PDU Transfer
Test Objective LdCom Transmission using <Bus>TP API and Notification for PDU Transfer
Releases
Affected LdCom, PduR, BusTp, BusIf, State reviewed
Modules BusDrv
on Acceptance
Test Document
Item LargeDataCOM: SWS_LDCOM_00013
Reference
to Test
Environment
Configuration LdComIPdu(SignalIPdu): AT_1472_IPdu(large I-PDU)
Parameters -LdComApiType = LDCOM_TP
LDCOM_SEND
-LdComTxCopyTxData = Rte_LdComCbkCopyTxData_Sg1
-LdComTxConfirmation = Rte_LdComCbkTpTxConfirmation_Sg1
-SignalLength(baseTypeSize) > Size of <BUS> capability
-DataSendCompletedEvent mapped on signal transmission
PduRRoutingPath:
-Routing path for LdComIpdu with PduRSrcBswModuleRef = BswMod_LdCom
-PduRDestPdu with PduRDestBswModuleRef = BswMod_<Bus>TP
Summary -To check LdCom transmission through TP for a signal of length greater than or
equal to maximum transmission unit of underlying bus. As this is indirect testing for
transmission confirmation, notification is given to software component of Upper
Tester about transmission of the signal.
Needed n/a
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write() for port AT_1472_Sg1 with Rte_Write() shall return RTE_E_OK.
value AT_1472_Sg1_Value_1.
Step 2 [LT] [LT]

bus
Monitor the bus for First Frame and validate First Frame shall be observed with
the same. data transmitted by SUT. Send Flow
Control frame with Flow Status
ClearToSend.
Step 3 [SWC] [LT]
Consecutive frames are sent by SWC until all Consecutive Frames shall
the data has been transmitted on reception be observed with data transmitted by
of Flow Control frame. SUT.
Step 4 - [LT]
Rte_LdComCbkTpTxConfirmation API
is invoked for the signal.
DataSendCompleted event is
activated for the same.
conditions
6.3.4 [ATS_COMINDEP_01473] LdCom Reception using <Bus>TP API

Test Objective LdCom Reception using <Bus>TP API
Releases
Affected LdCom, PduR, BusTp, BusIf, State reviewed
Modules BusDrv
on Acceptance
Test Document
Item LargeDataCOM: SWS_LDCOM_00016
LargeDataCOM: SWS_LDCOM_00017
Reference
to Test
Environment
LDCOM_RECEIVE
-LdComRxIndication = Rte_LdComCbkTpRxIndication_Sg1
-LdComRxStartOfReception = Rte_LdComCbkStartOfReception_Sg1
-LdComRxCopyRxData = Rte_LdComCbkCopyRxData_Sg1
PduRRoutingPath:
-Routing path for LdComIpdu with PduRSrcBswModuleRef = BswMod_<Bus>Tp
-PduRDestPdu with PduRDestBswModuleRef = BswMod_LdCom
Summary - To check LdCom reception through TP for signal length greater than transmission
unit of underlying bus.

bus
Needed n/a
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [SWC]
Send the signal AT_1473_Sg1 First Frame shall be received with

with AT_1473_Sg1_Value_1. FF_DL value greater than single
frame length. Flow Control with Flow
Status ClearToSend is sent.
Step 2 [LT] [SWC]
Consecutive frames are sent by LT until all DataReceivedEvent is activated on

the data has been transmitted on reception successful reception of all
of Flow Control frame. Consecutive Frames.
Step 3 [SWC] [SWC]
Call Rte_Read() for AT_1473_Sg1. Return value of Rte_Read() is

RTE_E_OK.
AT_1473_Sg1_Value_1.
conditions
6.3.5 [ATS_COMINDEP_01476] Behavior of LdCom Transmit Request from

Application when there is a request in Progress for the same PDU
Test Objective Behavior of LdCom Transmit Request from Application when there is a request in
Progress for the same PDU
Releases
Affected RTE, LdCom State reviewed
Modules
on
Acceptance
Test
Document
Trace to SWS RTE: SWS_Rte_01379
Item
Requirements Use Case UC06.02
/ Reference
to Test
Environment
bus
LDCOM_SEND
Summary - To transmit large signal data from software component of Upper Tester to Lower
Tester. The second frame is introduced deliberately when already initiated
transmission is in progress.
Needed n/a
Adaptation to
other
Releases
Main Test Execution
Step 1 [SWC] [SWC]
Trigger Rte_Write() for AT_1476_Sg1 Rte_Write() shall return RTE_E_OK.

signal with AT_1476_Sg1_Value1(This will
initiate LdCom transmission).
Step 2 [LT] [LT]
Monitor the bus for First Frame and First frame shall be observed on bus
validate the same. with data transmitted by SUT.
Step 3 [LT] [SWC]
Send Flow Control frame with Flow Status Flow Control frame is received.
ClearToSend.
Step 4 [SWC] [SWC]
Trigger Rte_Write() for AT_1476_Sg1 Rte_Write() shall

signal with AT_1476_Sg1_Value2 before return RTE_E_COM_BUSY as the TP
the transmission initiated in Step1 is buffer is locked due to the ongoing
completed. transmission.
Step 5 [SWC] [LT]
Consecutive frames are sent by SWC until Consecutive frames shall be observed
all the data has been transmitted for data on bus with data
transmission initiated in Step1 AT_1476_Sg1_Value1 transmitted by
SUT.
Step 6 - [SWC]
Rte_LdComCbkTpTxConfirmation API is
invoked for the signal and
DataSendCompletedEvent is activated
for the same.
Post- NONE
conditions

bus
6.3.6 [ATS_COMINDEP_01478] Behavior of LdCom Receive Request from
Application when there is a request in Progress for the same PDU
Test Objective Behavior of LdCom Receive Request from Application when there is a request in
Progress for the same PDU
Releases
Modules
on Acceptance
Test Document
Item RTE: SWS_Rte_01387
Reference
to Test
Environment
LDCOM_RECEIVE
-LdComRxIndication = Rte_LdComCbkTpRxIndication_Sg1
-LdComRxStartOfReception = Rte_LdComCbkStartOfReception_Sg1
-LdComRxCopyRxData = Rte_LdComCbkCopyRxData_Sg1
Summary - To check LdCom behavior for a PDU reception when already initiated reception for
the same PDU is in progress.
Needed n/a
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [SWC]
Send the Signal AT_1478_Sg1 with Flow Control with Flow Status
AT_1478_Sg1_Value_1. ClearToSend is sent from SUT on
reception of First Frame.
Step 2 [LT] [SWC]
Send the Signal AT_1478_Sg1 with Rte_LdComCbkTpRxIndication API

AT_1478_Sg1_Value_2. shall be invoked with E_NOT_OK
for signal AT_1478_Sg1 triggered in
Step1.
Step 3 - [SWC]
Reception is started for second

instance of AT_1478_Sg1 triggered in
Step2. Send Flow control frame with
Flow Status ClearToSend.
bus
Step 4 [LT] [SWC]
Consecutive frames are sent by LT until all DataReceivedEvent is activated on

the data has been transmitted on reception successful reception of all
of Flow Control frame. Consecutive Frames.
Step 5 [SWC] [SWC]
Call Rte_Read() for AT_1478_Sg1. Rte_Read() returns RTE_E_OK.
AT_1478_Sg1_Value_2
Post- NONE
conditions
6.3.7 [ATS_COMINDEP_01047] Behavior of LdCom Transmit Request from

Application when Transmit Confirmation was invoked for the ongoing
Transmission request for the same PDU
Test Objective Behavior of LdCom Transmit Request from Application when Transmit Confirmation
was invoked for the ongoing Transmission request for the same PDU
Releases
Modules
on Acceptance
Test Document
Item
Reference
to Test
Environment
LDCOM_SEND
Summary To check the unlocking of signal buffer by RTE when the Transmit Confirmation has
been invoked for the PDU. A Second frame is transmitted from Application after
Transmit confirmation was received for the ongoing tramsmission for same PDU.
Needed
Adaptation to
other Releases
Main Test Execution
bus
Step 1 [SWC] [SWC]
Trigger Rte_Write() for AT_1047_Sg1 signal Rte_Write() shall return RTE_E_OK

with AT_1047_Sg1_Value1 (This will initiate
LdCom transmission)
Step 2 [LT] [LT]
Monitor the bus for First Frame and validate First frame shall be observed on bus
the same. with data transmitted by SUT.
Step 3 [LT] [SWC]
ClearToSend.
Step 4 [SWC] [LT]
Consecutive frames are sent by SWC until all Consecutive frames shall be
the data has been transmitted. observed on bus with data
AT_1047_Sg1_Value1 transmitted by
SUT.
Step 5 - [SWC]
Rte_LdComCbkTpTxConfirmation
API is invoked for the signal.
DataSendCompletedEvent is
activated.
Step 6 [SWC] [LT]
Trigger Rte_Write() for AT_1047_Sg1 signal Rte_Write() shall return RTE_E_OK.

with AT_1047_Sg1_Value2.
Step 7 [LT] [LT]
Monitor the bus for first frame and validate First frame shall be observed on bus
the same. with data transmitted by SUT.
Step 8 [LT] [SWC]
ClearToSend.
Step 9 [SWC] [LT]
Consecutive frames are sent by SWC until all Consecutive frames shall be
the data has been transmitted. observed with data
AT_1047_Sg1_Value2 transmitted by
SUT.
Step 10 - [SWC]
Rte_LdComCbkTpTxConfirmation
API is invoke for the signal and
DataSendCompletedEvent is
activated for the same.
Post- NONE
conditions

bus

bus
7 RS_BRF_01592 - Data Transfer (Bus independent)

This Test Specification intends to cover the Data Transfer feature of the Com as
use the feature.
7.1.1 Test System

7.1.1.1.1 Use case 04.01: General features
For this use case, the aim is to test the general Com module data transfer features
independently of the Bus.

bus
Test System SUT

SWC
Lower
(Upper
Tester TCP(Test Coordination Procedures)
Test)
PCO
PduR
CanIf FrIf LinIf LinSM
Can Fr Lin
PCO Microcontroller
CAN or FlexRay or LIN Bus
embedded SWC.
The Bus used (CAN or FlexRay or Lin) is independent for this use case.

Not Applicable.

Not Applicable.


bus


OnEntry:
IPDU_ACTIVATED
-Start IpduGroup
OnEntry:
IPDU_DEACTIVATED
-Stop IpduGroup
OnEntry:
-Re-start IpduGroup
OnEntry:
TXMODE_TRUE
OnEntry:
TXMODE_FALSE
OnEntry:
TRIG_IPDU_SEND
-TriggerIpduSend
OnEntry:
LIN_START_SCHEDULE
OnEntry:
-Start IpduGroup
ART_SCHEDULE
For the Software Component point of view, for each test case, the communication
interfaces are defined as follow:

bus
Port name Data Dataelement Mapping Type
element
type
<TestCaseName>_<signalname> Uint8 <signalname> <Signalname> Signal
<TestCaseName>_<signalgroupname> Struct Groupsignal Groupsignal1->
{ <signal1name>
Uint8: Groupsignal2->
groupsignal1; <signal2name>
… <PortName>->
Uint8: <signalgroupname>
groupsignalx;
}


bus
7.1.2.1.1 Use Case 04.01: General features

AT_200_Sg1 AT_200_Sg1
AT_200_Sg2 AT_200_Sg2
AT_200_IpduGroup AT_200_Ipdu SUT TestBench
AT_200_GrSg1
AT_200_SgGr1
AT_200_GrSg2
AT_212_Sg1 AT_212_Sg1
AT_212_GrSg1
AT_212_IpduGroup AT_212_Ipdu AT_212_SgGr1 AT_212_GrSg2 SUT TestBench
AT_212_GrSg3
AT_212_Sg2 AT_212_Sg2
AT_220_Sg1 AT_220_Sg1
AT_220_Sg2 AT_220_Sg2
AT_220_GrSg1
AT_220_SgGr1
AT_220_GrSg2
AT_221_Sg1 AT_221_Sg1
AT_221_Sg2 AT_221_Sg2
AT_261_Sg1 AT_261_Sg1
AT_261_GrSg1
AT_261_SgGr1
AT_261_IpduGroup AT_261_Ipdu AT_261_GrSg2 SUT TestBench
AT_261_GrSg3
AT_261_SgGr2
AT_261_GrSg4
AT_222_GrSg1
AT_222_IpduGroup At_222_Ipdu AT_222_SgGr1 SUT TestBench
AT_222_GrSg2
AT_224_Sg1 AT_224_Sg1
AT_224_SgGr1
AT_224_GrSg2
AT_226_Ipdu1 AT_226_Sg1 AT_226_Sg1 SUT TestBench
AT_226_IpduGroup
AT_226_Ipdu2 AT_226_Sg2 AT_226_Sg2 SUT TestBench

Fibex::FibexCore::Co
Fibex::FibexCore::CoreCommunication::I
reCommunication::IS Com Notification
SignalToIPduMapping.transferProperty
ignalToPduMapping
Sn_12 TRIGGERED_ON_CHANGE Rte_ComCbkTAck_Sn_12
Sg12 TRIGGERED_ON_CHANGE Rte_ComCbkTAck_Sg12

bus
B7
B6 Sn_11
B5 Sn_12
B4
B3 Sg12_3 Sg12_2 Sg12_1
B2
B1 Sg11_4 Sg11_3 Sg11_2 Sg11_1
B0 Sn_13
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::Core
Fibex::FibexCore::CoreCommunication::I
Communication::ISign Com Notification
SignalToIPduMapping.transferProperty
alToPduMapping
Sn_14 TRIGGERED_ON_CHANGE Rte_ComCbkTAck_Sn_14
Sg13 TRIGGERED_ON_CHANGE Rte_ComCbkTAck_Sg13
B7
B6 Sn_14
B5 Sn_15
B4
B3 Sg14_3 Sg14_2 Sg14_1
B2
B1 Sg13_4 Sg13_3 Sg13_2 Sg13_1
B0 Sn_16
D7 D6 D5 D4 D3 D2 D1 D0
AT_725 Signal Properties

Fibex::FibexCore::CoreC Fibex::FibexCore::CoreCommunicatio
ommunication::ISignalTo n::ISignalToIPduMapping.transferPro Com Notification
PduMapping perty
Sn_17 TRIGGERED_WITHOUT_REPETITION Rte_ComCbkTAck_Sn_17
Sg16 TRIGGERED_WITHOUT_REPETITION Rte_ComCbkTAck_Sg16
bus
B7 Sn_19
B6
B5 Sn_18
B4
B3 Sg16_5 Sg16_4 Sg16_3 Sg16_2 Sg16_1
B2
B1 Sg15_4 Sg15_3 Sg15_2 Sg15_1
B0 Sn_17
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCo Fibex::FibexCore::CoreCommunicatio
mmunication::ISignalToP n::ISignalToIPduMapping.transferPro Com Notification
duMapping perty
Sn_67 TRIGGERED_WITHOUT_REPETITION Rte_ComCbkTAck_Sn_67
Sg17 TRIGGERED_WITHOUT_REPETITION Rte_ComCbkTAck_Sg17
B7 Sn_67
B6
B5 Sn_66
B4
B3 Sg17_5 Sg17_4 Sg17_3 Sg17_2 Sg17_1
B2
B1 Sg18_4 Sg18_3 Sg18_2 Sg18_1
B0 Sn_65
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::Core Fibex::FibexCore::CoreCommunicati
Communication::ISigna on::ISignalToIPduMapping.transferPr Com Notification
lToPduMapping operty
TRIGGERED_ON_CHANGE_WITHOU
Sn_90 Rte_ComCbkTAck_Sn_90
T_REPETITION
TRIGGERED_ON_CHANGE_WITHOU
Sg91 Rte_ComCbkTAck_Sg91
T_REPETITION
bus
B7 Sn_90
B6
B5 Sn_91
B4 Sg91_5 Sg91_4 Sg91_3 Sg91_2 Sg91_1
B3 Sg92_5 Sg92_4 Sg92_3 Sg92_2 Sg92_1
B2
B1 Sg93_4 Sg93_3 Sg93_2 Sg93_1
B0
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreComm
Fibex::FibexCore::CoreCommuni
unication::ISignalToIPduMapp Com Notification
cation::ISignalToPduMapping
ing.transferProperty

Sg96 TRIGGERED Rte_ComCbkTAck_Sg96
B7
B6 Sn_95
B5 Sn_96
B4
B3 Sg96_3 Sg96_2 Sg96_1
B2
B1 Sg97_4 Sg97_3 Sg97_2 Sg97_1
B0 Sn_97
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCommunication::ISignalT Fibex::FibexCore::CoreCommunication::ISi
oPduMapping gnalToIPduMapping.transferProperty
Sn_74 TRIGGERED
Sn_75 PENDING
Sn_76 PENDING
Sg74 PENDING
Sg75 PENDING
B7
B6 Sn_74
bus
B5 Sn_75
B4
B3 Sg74_3 Sg74_2 Sg74_1
B2
B1 Sg75_4 Sg75_3 Sg75_2 Sg75_1
B0 Sn_76
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCommunication::ISignalT Fibex::FibexCore::CoreCommunication::IS
oPduMapping ignalToIPduMapping.transferProperty
Sn_80 TRIGGERED
Sn_78 PENDING
Sn_77 PENDING
Sg77 PENDING
Sg78 PENDING
B7
B6 Sn_80
B5 Sn_78
B4
B3 Sg78_3 Sg78_2 Sg78_1
B2
B1 Sg77_4 Sg77_3 Sg77_2 Sg77_1
B0 Sn_77
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCom Fibex::FibexCore::CoreCommunicat
munication::ISignalToPduM ion::ISignalToIPduMapping.transfer Com Notification
apping Property
sn_44 TRIGGERED Rte_ComCbkTAck_Sn_44
B7 USg43 USn44 USn43
B6
B5 Sn_44
B4
B3
B2 Sn_43
B1 Sg43_1 Sg43_2
B0
bus
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCo Fibex::FibexCore::CoreCommunicati
mmunication::ISignalToPd on::ISignalToIPduMapping.transferPr Com Notification
uMapping operty
sn_45 PENDING Rte_ComCbkTAck_Sn_45
B6
B5 Sn_46
B4
B3
B2 Sn_45
B1 Sg45_1 Sg45_2
B0
D7 D6 D5 D4 D3 D2 D1 D0

Fibex::FibexCore::CoreCom Fibex::FibexCore::CoreCommunicat
munication::ISignalToPduMa ion::ISignalToIPduMapping.transfer Com Notification
pping Property
sn_47 PENDING Rte_ComCbkTAck_Sn_47
B6
B5 Sn_48
B4
B3
B2 Sn_47
B1 Sg47_1 Sg47_2
B0
D7 D6 D5 D4 D3 D2 D1 D0
AT_734_Rx_IPDU_SR STRUCTURE
B6
B5 Sn_60
B4
bus
B3
B2 Sn_49
B1 Sg49_1 Sg49_2
B0
D7 D6 D5 D4 D3 D2 D1 D0
AT_734_Tx_IPDU_SR STRUCTURE
B6
B5 Sn_60
B4 Sn_66
B3
B2 Sn_49
B1 Sg49_1 Sg49_2
B0
D7 D6 D5 D4 D3 D2 D1 D0
B6
B5 Sn_42
B4
B3
B2
B1 Sg41_1 Sg41_2
B0 Sn_41
D7 D6 D5 D4 D3 D2 D1 D0
AT_735_Tx_IPDU_SR STRUCTURE:
:B7
B6
B5 Sn_42
B4 Sn_70
B3
B2
B1 Sg41_1 Sg41_2
B0 Sn_41
D7 D6 D5 D4 D3 D2 D1 D0
B6
B5 Sn_62
B4
B3
B2 Sn_61
B1 Sg61_1 Sg61_2
B0
D7 D6 D5 D4 D3 D2 D1 D0

bus
AT_736_Tx_IPDU_SR STRUCTURE:
B7
B6
B5 Sn_62
B4
B3
B2 Sn_61
B1 Sg61_1 Sg61_2
B0
D7 D6 D5 D4 D3 D2 D1 D0




 CAN, LIN and FlexRay frames identifiers

Not Applicable.

Not Applicable.
7.3 Test Cases
7.3.1 [ATS_COMINDEP_00200] Group Control - Time Based frame (PERIODIC)

Test Group Control - Time Based frame (PERIODIC)
Objective
bus
Releases
Modules
on
Acceptance
Test
Document
Trace to COM: SWS_Com_00217
SWS Item COM: SWS_Com_00222
COM: SWS_Com_00228
COM: SWS_Com_00334
COM: SWS_Com_00444
COM: SWS_Com_00677
COM: SWS_Com_00740
COM: SWS_Com_00787
Requirement Use Case UC04.01
s/
Reference
to Test
Environment
Configuratio Please refer to the basic communication Database present in sub-chapter "Test
n Configuration" of this test suite. In addition to that:
Parameters
ComIpdu(SignalIPdu): AT_200_Ipdu
- ComTxModeTrue
--- ComTxModeTimeOffset(timeOffset) > ComTxModeTimePeriod(timePeriod)
ComSignal(ISignalToPduMapping): AT_200_Sg1/AT_200_Sg2
- ComUpdateBitPosition (updateIndicationBitPosition) is configured
- ComSignalInitValue (ISignal.initValue) = Sg1_Value_init/Sg2_Value_init
ComSignalGroup(ISignalToPduMapping): AT_200_SgGr1
- ComGroupSignal(ISignalToPduMapping): AT_200_GrSg1/AT_200_GrSg2
-- ComSignalInitValue (ISignal.initValue) = GrSg1_Value_init/GrSg2_Value_init
Summary Aim:
- No signal and no group signal filter, so only One TxMode (ComTxModeTrue)
[SWS_Com_00677]
1) Check that update signal and group signal values on stopped ipdu (ipdu never
started) has no effect
2) Check that starting an ipdu group on first time, initilializes signal values, respects
Offset and Period times, fulfills unused byte of the Ipdu
[SWS_Com_00740][SWS_Com_00787][SWS_Com_00222][SWS_Com_00217]
3) Check that stopping an ipdu group, stop send of time based frames
4) Check that signal and group signal values are updated even if the ipdu is
stopped [SWS_Com_00334]
5) Check that starting an ipdu group (with initialize = FALSE), uses last signal values
and doesn't restart Offset time [SWS_Com_00787][SWS_Com_00228]
Needed None
Adaptation
to other
Releases
bus
Pre- Com stack is initialized, but ipdu groups are not running
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Send signal AT_200_Sg1 (call Rte_Write() for Sender Rte_Write shall return
Port AT_200_Sg1) with value AT_200_Sg1_Value_1 "RTE_E_COM_STOPPED"
AT_200_SgGr1.AT_200_GrSg1=AT_200_GrSg1_Val
ue_1
AT_200_SgGr1.AT_200_GrSg2=AT_200_GrSg2_Val
ue_1
Send signal group AT_200_SgGr1 (call Rte_Write()
for Sender Port AT_200_GrSg1)
(Rte will send group signal AT_200_GrSg1 with value
AT_200_GrSg1_Value_1, send group signal
AT_200_GrSg2 with value AT_200_GrSg2_Value_1,
send signal group AT_200_SgGr1)
Step 2 - [LT]
AT_200_Ipdu is not sent out.
Step 3 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest First AT_200_Ipdu is sent out
port) to IPDU_ACTIVATED (start Ipdu group after Offset time value.
AT_200_IpduGroup with INITIALIZE = FALSE) Other AT_200_Ipdu occurences
are sent out every Period time
value.
AT_200_Sg1 value shall be
AT_200_Sg1_Value_Init
AT_200_GrSg1 value shall be
AT_200_GrSg1_Value_1
AT_200_Sg1, AT_200_Sg2
UpdateBits are cleared (0) for all
AT_200_Ipdu occurrences
Update bit of “AT_200_SgGr1”
set(1) for the first Transmission
and cleared (0) for subsequent
transmissions
Unused areas in
AT_200_Ipdu are filled with
configured UnusedBitPattern
Step 4 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest AT_200_Ipdu is not sent out
port) to IPDU_DEACTIVATED (stop Ipdu group
AT_200_IpduGroup)
Step 5 [SWC] [SWC]
Send signal AT_200_Sg2 (call Rte_Write() for Sender Rte_Write shall return
Port AT_200_Sg2) with value AT_200_Sg2_Value_1 "RTE_E_COM_STOPPED"
AT_200_SgGr1.AT_200_GrSg1 =
AT_200_GrSg1_Value_Init
Send signal group AT_200_GrSg1 (call Rte_Write()
for Sender Port AT_200_GrSg1)
( Rte will send group signal AT_200_GrSg2 with value
bus
AT_200_GrSg2_Value_1, send signal group
AT_200_SgGr1 )
Step 6 - [LT]
AT_200_Ipdu is not sent out.
Step 7 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest First AT_200_Ipdu is sent out
port) to IPDU_ACTIVATED (start Ipdu group after at last Period time value
AT_200_IpduGroup with INITIALIZE = FALSE) (not offset time).
Other AT_200_Ipdu occurences
are sent out every Period time
value
AT_200_Sg2_Value_1
AT_200_Sg1, AT_200_Sg2,
AT_200_SgGr1 UpdateBits are
cleared (0) for all AT_200_Ipdu
occurences
Unused areas in
AT_200_Ipdu are filled with
configured UnusedBitPattern
conditions
7.3.2 [ATS_COMINDEP_00205] Group Control - User Request frame (DIRECT)

+ MDT
Test Objective Group Control - User Request frame (DIRECT) + MDT
Releases
Modules
on Acceptance
Test Document
COM: SWS_Com_00787
COM: SWS_Com_00812
Reference
to Test
Environment
Configuration Please refer to the basic communication Database present in sub-chapter "Test
Parameters Configuration" of this test suite. In addition to that:
bus
- ComMinimumDelayTime (IPduTiming.minimumDelay) = y ms
- ComTxModeTrue
-- ComTxModeMode (TransmissionModeTiming) = DIRECT
(EventControlledTiming)
--- ComTxModeRepetitionPeriod(RepetitionPeriod) = x ms
--- ComTxModeNumberOfRepetitions(numberOfRepetitions) = 3
==> Constraint: y << x
ComSignal(ISignalToPduMapping): AT_205_Sg1
- ComTransferProperty (transferProperty) = TRIGGERED
- ComUpdateBitPosition (updateIndicationBitPosition) is not configured
configured)
Summary Aim:
- Check that ipdu group stops the Minimum Delay Time (MDT) [SWS_Com_00787]
- Check that a send triggered signal (related to DIRECT Ipdu) respects the
Repetition Period [SWS_Com_00812][SWS_Com_00330][SWS_Com_00305]
=> See Attached file (AT-205 overview) for more details

Needed For Release < 4.2.1 :
Adaptation to For steps 2, 4 and 6, AT_205_Ipdu is transmitted on the bus 3 times.
other Releases
Pre-conditions Com stack is initialized, but ipdu groups are not running
Main Test Execution
Step 1 [SWC]
Request ModeSwitch (call to
BswMModeRequest port) to
IPDU_ACTIVATED (start Ipdu group
AT_205_IpduGroup)
Step 2 [SWC] [LT]
Send triggered signal AT_205_Sg1 (call to AT_205_Ipdu is sent out 4 times
Rte_Write() API for Port AT_205_Sig1) First sent is done on trigger
with AT_205_Sg1_Value_1 Others sent are done
every RepetitionPeriod
AT_205_Sg1_Value_1 for the 3
AT_205_Ipdu items
Step 3 [CP]
Wait DataSendCompletedEvent occurrence
on SWC Sender side.
Step 4 [SWC] [LT]
When DataSendCompletedEvent occurs, AT_205_Ipdu is sent out 4 times
send triggered signal AT_205_Sg1 (call to First sent is done after
Rte_Write() API for Port AT_205_Sig1) MinimumDelayTime
with AT_205_Sg1_Value_2 Others sent are done
AT_205_Ipdu items
Step 5 [CP]
Wait DataSendCompletedEvent occurrence
on SWC Sender side.
Step 6 [SWC]
When DataSendCompletedEvent occurs,
bus
BswMModeRequest Port) to IPDU_OFF_ON
(Actions: stop Ipdu group
AT_205_IpduGroup; start Ipdu group
AT_205_IpduGroup)
Step 7 [SWC] [LT]
Immediately Send triggered signal AT_205_Ipdu is sent out 4 times
AT_205_Sg1 (call to Rte_Write() API for Port First sent is done on trigger (no MDT
AT_205_Sig1) with AT_205_Sg2_Value_3 applied, reset by IpduGroup start)
Others sent are done
AT_205_Ipdu items
conditions
7.3.3 [ATS_COMINDEP_00259] User Request frame (DIRECT) + MDT

Test Objective User Request frame (DIRECT) + MDT
Releases
Modules
on Acceptance
Test Document
Reference
to Test
Environment
- ComMinimumDelayTime (IPduTiming.minimumDelay) = y ms
- ComTxModeTrue
configured)
Summary Aim:
- Check that a send triggered signal (related to DIRECT Ipdu) respects the MDT
[SWS_Com_00812][SWS_Com_00698]
Needed None
bus
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC]
AT_259_IpduGroup)
Step 2 [SWC] [LT]
Send triggered signal AT_259_Sg1 (call to AT_259_Ipdu sent out shall occur
Rte_Write() API for Port AT_259_Sg1) with only one time
AT_259_Sg1_Value_1 AT_259_Sg1 value shall be
AT_259_Sg1_Value_1
Step 3 [CP] -
Wait DataSendCompletedEvent occurence
on SWC Sender side.
Step 4 [SWC] [LT]
When DataSendCompletedEvent occurs, AT_259_Ipdu sent out shall occur
send triggered signal AT_259_Sg1 (call to after MinimumDelayTime
Rte_Write() API for Port AT_259_Sg1) with AT_259_Sg1 value shall be
AT_259_Sg1_Value_2 AT_259_Sg1_Value_2
conditions
7.3.4 [ATS_COMINDEP_00260] User Request frame (DIRECT) + several

triggers
Test Objective User Request frame (DIRECT) + several triggers
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
- ComTxModeTrue
bus
configured)
Summary Aim:
- Check that multiple send triggered signal (related to DIRECT Ipdu) does not cause
triggers accumulation
Needed For Release < 4.2.1 :

Adaptation to For step 4: The frame would have been transmitted 7 times in total and it would
other Releases have been received with AT_260_Sg1_Value_3 for the last 4 times
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to Start frame monitoring
AT_260_IpduGroup)
Step 2 [SWC]
Send triggered signal AT_260_Sg1 (call
Rte_Write() API for Port AT_260_Sig1) with
AT_260_Sg1_Value_1
Step 3 [SWC]
1,3 * repetitions period after, send triggered
signal AT_260_Sg1(call Rte_Write() API for
Port AT_260_Sig1) with
AT_260_Sg1_Value_2
Step 4 [SWC] [LT]
1,3 * repetitions period after, send triggered Stop frame monitoring, analyse
signal AT_260_Sg1 (call Rte_Write() API for frames received during monitoring:
Port AT_260_Sig1) with - AT_260_Ipdu sent out shall occur 8
AT_260_Sg1_Value_3 times
- Each occurrence shall be done
- AT_260_Sg1 value shall be
AT_260_Sg1_Value_1 in sent out (1)
and (2)
AT_260_Sg1_Value_2 in sent out (3)
AT_260_Sg1_Value_3 in sent out (4),
(5), (6), (7) & (8)
conditions
7.3.5 [ATS_COMINDEP_00212] Tx notification

Test Objective Tx notification

bus
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
- ComTxModeTrue
- No ComTxModeFalse (transmissionModeFalseTiming)
- ComTransferProperty (transferProperty) = PENDING
for Sg1/SgGr1/Sg2:
- ComUpdateBitPosition (updateIndicationBitPosition) is not configured
- DataSendCompletedEvent mapped on signal transmissio
Summary Aim:
- Test PENDING signal and signal group
- Test Signal and Signal Group Tx notifications
- Tests Signal and Signal Group Error notification on ipdu group control stop
[SWS_Com_00479]
Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC]
AT_212_IpduGroup)
Step 2 [SWC] [LT]
Send pending signal AT_212_Sg1 (call AT_212_Ipdu shall not be sent out
Rte_Write() on Port AT_212_Sig1) with
AT_212_Sg1_Value_1
bus
Step 3 [SWC] [LT]
AT_212_SgGr1.AT_212_GrSg1 = AT_212_Ipdu shall not be sent out
AT_212_GrSg3_Value_1\
Send pending signal group AT_212_SgGr1
call (Rte_Write() for Port AT_212_SgGr1)
Step 4 [SWC] [LT]
Send triggered signal AT_212_Sg2 (call AT_212_Ipdu shall be sent 1 time
Rte_Write() for Port AT_212_Sg2) with AT_212_Sg1 value shall
AT_212_Sg2_Value_1 be AT_212_Sg1_Value_1
AT_212_Sg2 value shall
be AT_212_Sg2_Value_1
AT_212_GrSg1 value shall
be AT_212_GrSg1_Value_1
DataSendCompletedEvent (Tx
notification functions callback)
associated to signal AT_212_Sg1,
signal group AT_212_SgGr1 and
signal AT_212_Sg2 shall be called
Step 5 [SWC]
Send triggered signal AT_212_Sg2 (call
Rte_Write() API for Port AT_212_Sg2) and
stop Ipdu group AT_212_IpduGroup (call to
BswMModeRequest to IPU_DEACTIVATED)
before Tx Irq Confirmation.
Step 6 [CP]
WAIT 200ms
Step 7 [SWC] [SWC]
Call Rte_feedback() API for AT_212_Sg2 Rte_feedback() should return
RTE_E_COM_STOPPED
conditions
7.3.6 [ATS_COMINDEP_00220] Tx Mode Switch (TMS) - PERIODIC/PERIODIC

Test Tx Mode Switch (TMS) - PERIODIC/PERIODIC
Objective
ID ATS_COMINDEP_00220 AUTOSAR 3.2.1|3.2.2|4.0.3|4.1.1|4.2.1|4.2
Releases .2
Modules
Requirement
on
Acceptance
Test
Document
Trace to COM: SWS_COM_00799
bus
COM: SWS_Com_00231
COM: SWS_Com_00326
COM: SWS_Com_00495
COM: SWS_Com_00676
s/
Reference
to Test
Environment
Parameters
- ComTxModeTrue
-- PERIODIC (TransmissionModeTiming.CyclicTiming)
--- timeOffset = 0
--- timePeriod > 0
- ComTxModeFalse(transmissionModeFalseTiming)
-- PERIODIC (TransmissionModeTiming.CyclicTiming)
--- timeOffset and timePeriod values are different from ModeTrue
- No ComFilter
- ComFilter(DataFilter)
-- dataFilterType = ONE_EVERY_N
-- period/offset configured => TMC = FALSE
- ComSignalInitValue
-- No ComFilter
-- ComFilter(DataFilter)
--- dataFilterType = MASK
Summary Aim:
- Check that updating Signal and Group Signal that have no filter does not impact the
TMS [SWS_Com_00676][SWS_Com_00236]
- Check that updating Signal and Group Signal that have filter impacts the TMS
[SWS_Com_00676][SWS_Com_00236]
- Check that if one of TMCs is True, TxModeTrue is used [SWS_Com00032]
- Check that if all TMCs are False, TxModeFalse is used [SWS_Com00799]
- Test MASKED_NEW_EQUALS_X filter
- Test ONE_EVERY_N filter [SWS_Com_00231]
- Test that a TMS does an immediate sent (respecting TimeOffset) [SWS_Com_00495]
Needed None
Adaptation
to other
Releases
conditions
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest port) 1st AT_220_Ipdu sent out shall
bus
to IPDU_ACTIVATED (start Ipdu group be done after TxModeTrue
AT_220_IpduGroup) Period
Others AT_220_Ipdu sent out
shall be done every
TxModeTrue Period
AT_220_Sg1 value is
AT_220_Sg2 value is
AT_220_GrSg1 value is
Step 2 [SWC] [LT]
Send signal AT_220_Sg1 (call to Rte_Write() for Port Tx mode is not changed
AT_220_Sg1) with value AT_220_Sg1_Value_1 (TxModeTrue Period is
AT_220_SgGr1.AT_220_GrSg1=AT_220_GrSg1_Value respected)
_1 AT_220_Sg1 value is
AT_220_SgGr1.AT_220_GrSg2=AT_220_GrSg2_Value AT_220_Sg1_Value_1
_Init AT_220_Sg2 value is
Call Rte_Write() for Port AT_220_SgGr1 AT_220_Sg2_Value_Init
Step 3 [SWC] [LT]
AT_220_SgGr1.AT_220_GrSg1=AT_220_GrSg1_Value 1st AT_220_Ipdu sent out shall
_1 be done after TxModeFalse
AT_220_SgGr1.AT_220_GrSg2=AT_220_GrSg2_Value Offset
_1 (This value changes the signal TMC to FALSE) Others AT_220_Ipdu sent out
Call Rte_Write() for Port AT_220_SgGr1 shall be done every
TxModeFalse Period
AT_220_Sg1 value is
AT_220_Sg1_Value_1
AT_220_Sg2 value is
Step 4 [SWC] [LT]
Do several Send signal AT_220_Sg2 (call to 1st AT_220_Ipdu sent out
Rte_Write() for Port AT_220_Sg2) with value immediatly
AT_220_Sg2_Value_1 (The last sent change the group Others AT_220_Ipdu sent out
signal TMC to TRUE) shall be done every
Send signal group AT_220_SgGr1 (call to Rte_Write() TxModeTrue Period
for Port AT_220_SgGr1) AT_220_Sg1 value is
AT_220_Sg1_Value_1
AT_220_Sg2 value is
AT_220_Sg2_Value_1
Step 5 [SWC] [LT]
AT_220_SgGr1.AT_220_GrSg2=AT_220_GrSg2_Value Tx mode is not changed
_2 (This value changes the signal TMC to TRUE) (TxModeTrue Period is
Call Rte_Write() for Port AT_220_SgGr1 respected)
AT_220_Sg1 value is
bus
AT_220_Sg1_Value_1
AT_220_Sg2 value is
AT_220_Sg2_Value_1
conditions
7.3.7 [ATS_COMINDEP_00221] Tx Mode Switch (TMS) - MIXED/DIRECT

Test Objective Tx Mode Switch (TMS) - MIXED/DIRECT
Releases
Modules
Requirement
on Acceptance
Test Document
Item
Reference
to Test
Environment
- ComTxModeTrue
-- DIRECT (EventControlledTiming)
--- NumberOfRepetitions = 2
--- RepetitionPeriod = x
-- MIXED (EventControlledTiming and CyclicTiming)
--- RepetitionPeriod = y
--- timeOffset != timePeriod (timePeriod >3 * y)
- No ComFilter
configured)
-- dataFilterType = MASKED_NEW_DIFFERS_X
-- period/offset configured =
Summary Aim:

bus
- Check that Time Offset for MIXED ipdu is started on TMS change
[SWS_Com_00495]
- Check that the direct (event) frame in the MIXED ipdu does not perturb the
periodic frames
- Test MASKED_NEW_DIFFERS_X filter
- Test that updating a pending signal does not generate a DIRECT sent but can
generate a TMS switch
Needed None
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to Tx Mode True is used (AT_221_Ipdu
BswMModeRequest port) to is not sent out)
IPDU_ACTIVATED (start Ipdu group Start AT_221_Ipdu frame monitoring
AT_221_IpduGroup)
Step 2 [SWC]
Send signal AT_221_Sg1 (call Rte_Write()
for Port AT_221_Sg1)
with AT_221_Sg1_Value_1
Step 3 [CP] [LT]
Wait <x + SafetyMargin> (x = Stop frame monitoring, analyse
RepetitionPeriod of AT_221_Ipdu) frames received during monitoring:
- AT_221_Ipdu is sent out 2 times
- First send is immediate after
previous step action Rte_Write()
- Second send is done after <x>
RepetitionPeriod (ModeTrue)
- AT_221_Sg1 value
is AT_221_Sg1_Value_1
- AT_221_Sg2 value
is AT_221_Sg2_Value_1_Init
Step 4 - [SWC]
AT_221_Sg1 notification
(DataSendCompletedEvent) is called
only one time
Step 5 [SWC] [LT]
Send signal AT_220_Sg2 (Call Rte_Write() AT_221_Ipdu is not sent out
for Port AT_221_Sg2)with value Start AT_221_Ipdu frame monitoring
AT_220_Sg2_Value_1 (This value does not
change the signal TMC to FALSE)
Step 6 [SWC]
Send signal AT_220_Sg2 (call Rte_Write()
for Port AT_221_Sg2) with value
AT_220_Sg2_Value_2 (This value changes
the signal TMC to FALSE)
Step 7 [CP] [LT]
Wait <10 * timePeriod> Stop frame monitoring, analyse
frames received during monitoring:

bus
- AT_221_Ipdu periodic sent is started
after previous step action Rte_Write()
- Fisrt sent is done after TimeOffset
(ModeFalse)
- Others sent are done each
TimePeriod (ModeFalse)
- AT_221_Sg1 value is
AT_221_Sg1_Value_1
AT_221_Sg2_Value_2
Step 8 - [SWC]
(DataSendCompletedEvent) is called
on each ipdu sent out
Step 9 [SWC]
When DataSendCompletedEvent occurs
(AT_221_Sg1 notification), send signal
AT_221_Sg1 (call Rte_Write() for Port
AT_221_Sg1) with AT_221_Sg1_Value_2
Step 10 [CP] [LT]
Wait <10 * timePeriod> Stop frame monitoring, analyse
frames received during monitoring:
- 3 AT_221_Ipdu are sent
immediately after previous step action
Rte_Write() (each sent is done every
RepetitionPeriod - Mode False)
AT_221_Sg1_Value_2
AT_221_Sg2_Value_2
- AT_221_Ipdu Periodic sent out is
not disturbed
Step 11 - [SWC]
(DataSendCompletedEvent) is done
only one time for the Direct sent and
at each time for periodic sent
conditions
7.3.8 [ATS_COMINDEP_00261] DIRECT + TRIGGERED ON CHANGE WITHOUT

REPETITIONS
Test DIRECT + TRIGGERED ON CHANGE WITHOUT REPETITIONS
Objective
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
bus
s/
Reference
to Test
Environment
Parameters
- ComTxModeTrue
-- DIRECT (TransmissionModeTiming.EventControlledTiming)
--- RepetitionPeriod
- ComTransferProperty (transferProperty) =
TRIGGERED_ON_CHANGE_WITHOUT_REPETITION
- No ComFilter
- ComSignalInitValue(ISignal.initValue)
- ComTransferProperty (transferProperty) =
TRIGGERED_ON_CHANGE_WITHOUT_REPETITION
-- No ComFilter
-- ComSignalInitValue(ISignal.initValue)
Summary Aim:
- Test TRIGGERED_ON_CHANGE_WITHOUT_REPETITION signal

[SWS_Com_00768]
- Test TRIGGERED_ON_CHANGE_WITHOUT_REPETITION signal group
[SWS_Com_00770]
Needed For Release < 4.2.1:
Adaptation For step 2, the IPDU is transmitted on the bus 5 times.
to other
Releases
conditions
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest port) AT_261_Ipdu is not sent out
to IPDU_ACTIVATED (start Ipdu group
AT_261_IpduGroup)
Step 2 [SWC] [LT]
AT_261_SgGr2.AT_261_GrSg3=AT_261_GrSg3_Value AT_261 is sent out 6 times
_Init 1st send is immediate
AT_261_SgGr2.AT_261_GrSg4=AT_261_GrSg4_Value Time between each send
_Init is Repetition Period
Call Rte_Write() for Port AT_261_SgGr2 AT_261_Sg1 value is
(Rte will send group signal AT_261_GrSg3 AT_261_Sg1_Value_Init

bus
with AT_261_GrSg3_Value_Init, then send group signal AT_261_GrSg1 value is
AT_261_GrSg4 with AT_261_GrSg4_Value_Init, and AT_261_GrSg1_Value_Init
finally send signal group AT_261_SgGr2) AT_261_GrSg2 value is
Step 3 [SWC] [LT]
Send signal AT_261_Sg1 (call Rte_Write() API for Port AT_261 is not sent out
AT_261_Sg1) with the initial value
Step 4 [SWC] [LT]
Send signal AT_261_Sg1 (call Rte_Write() API for Port AT_261 is sent out only 1 time
AT_261_Sg1) with a new value AT_261_Sg1_Value_1 (this sent is immediate)
AT_261_Sg1 value is
AT_261_Sg1_Value_1
Step 5 [SWC] [LT]
AT_261_SgGr1.AT_261_GrSg1=AT_261_GrSg1_Value AT_261 is not sent out
_Init
AT_261_SgGr1.AT_261_GrSg2=AT_261_GrSg2_Value
_Init
call Rte_Write() for Port AT_261_SgGr1
(Rte will send group signal AT_261_GrSg1
with AT_261_GrSg1_Value_Init, then send group signal
AT_261_GrSg2 with AT_261_GrSg2_Value_Init and
finally send signal group AT_261_SgGr1)
Step 6 [SWC] [LT]
AT_261_SgGr1.AT_261_GrSg1=AT_261_GrSg1_Value AT_261 is sent out only 1 time
_Init (this sent is immediate)
AT_261_SgGr1.AT_261_GrSg2=AT_261_GrSg2_Value AT_261_Sg1 value is
_1 AT_261_Sg1_Value_1
call Rte_Write() for Port AT_261_SgGr1 AT_261_GrSg1 value is
(Rte will send group signal AT_261_GrSg1 AT_261_GrSg1_Value_Init
with AT_261_GrSg1_Value_Init, then send group signal AT_261_GrSg2 value is
AT_261_GrSg2 with AT_261_GrSg2_Value_1 and AT_261_GrSg2_Value_1
finally send signal group AT_261_SgGr1) AT_261_GrSg3 value is
conditions
7.3.9 [ATS_COMINDEP_00222] Tx Mode Switch (TMS) - PERIODIC/MIXED +

MDT
Test Tx Mode Switch (TMS) - PERIODIC/MIXED + MDT
Objective
bus
ID ATS_COMINDEP_00222 AUTOSAR 3.2.1|3.2.2|4.0.3|4.1.1|4.2.1|4.2
Releases .2
Modules
Requirement
on
Acceptance
Test
Document
s / Reference
to Test
Environment
Parameters
- ComTxModeTrue
-- MIXED (EventControlledTiming and CyclicTiming)
--- timeOffset = 0
--- timePeriod > 0
-- PERIODIC (CyclicTiming)
--- timeOffset > timePeriod
- minimumDelay < timePeriod(TxModeTrue)
- No updateIndicationBitPosition
configured)
-- No ComFilter
--- dataFilterType = NEW_IS_OUTSIDE
-- ComSignalInit
Summary Aim:
- Check that Minimum Delay Time (MDT) is checked on TMS change
[SWS_Com_00582]
- Check that Minimum Delay Time (MDT) is started on pdur transmission request
[SWS_Com_00698]
- Test NEW_IS_OUTSIDE filter
Needed None
Adaptation
to other
Releases
conditions
Main Test Execution

bus
Step 1 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest port) Start AT_222_Ipdu frame
to IPDU_ACTIVATED (start Ipdu group monitoring
AT_222_IpduGroup)
Step 2 [CP] [LT]
Wait <10 * timePeriod(TxModeFalse)> Stop frame monitoring, analyse
frames received during
monitoring:
- First sent out (after previous
step action) is done after
TxModeFalse Offset
- AT_222_Ipdu is sent out
periodically (each TxMode
False Period)
- AT_222_GrSg1 value
is AT_222_GrSg1_Value_Init
- AT_222_GrSg2 value
Step 3 - [SWC]
Signal group AT_222_SgGr1
notification
(DataSendCompletedEvent) is
called at each sent out
Step 4 [SWC] [LT]
When DataSendCompletedEvent occurs AT_222_Ipdu Direct sent out is
(AT_222_SgGr1 notification): not done immediately. It shall
AT_222_SgGr1.AT_222_GrSg1=AT_222_GrSg2_value be done after MDT
_Init One or more Periodic sent out
AT_222_SgGr1.AT_222_GrSg2=AT_222_GrSg2_value of AT_222_Ipdu is postponed
_1 (this value changes the group signal TMC to TRUE) to respect the MDT
Call Rte_Write() for Port AT_222_SgGr1 AT_222_GrSg1 value is
conditions
7.3.10 [ATS_COMINDEP_00224] Tx Mode Switch (TMS) - DIRECT/PERIODIC

Test Tx Mode Switch (TMS) - DIRECT/PERIODIC
Objective
Releases
Modules
Requiremen
t on
Acceptance
Test
Document
COM: SWS_Com_00603
bus
COM: SWS_Com_00604
Requiremen Use Case UC04.01
ts /
Reference
to Test
Environmen
t
Parameters
- ComTxModeTrue
--- timeOffset = 0
--- timePeriod > 0
-- DIRECT (EventControlledTiming)
- ComSignalInitValue(ISignal.initValue) => TMC = TRUE
-- dataFilterType = MASKED_NEW_DIFFERS_MASKED_OLD
-- ComSignalInitValue(ISignal.initValue) => TMC = FALSE
--- dataFilterType = MASKED_NEW_DIFFERS_MAS
Summary Aim:
- Test MASKED_NEW_DIFFERS_MASKED_OLD filter
[SWS_Com_00604][SWS_Com_00603][SWS_Com_00302][SWS_Com_00303]
Needed None
Adaptation
to other
Releases
conditions
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest port) AT_224_Ipdu is sent out after
to IPDU_ACTIVATED (start Ipdu group Period and after each Period
AT_224_IpduGroup) (TxMode True)
AT_224_Sg1 value
is AT_224_Sg1_Value_Init
AT_224_GrSg1 value
AT_224_GrSg2 value
Step 2 [SWC] [LT]
Send signal AT_224_Sg1 (call Rte_Write() API for Port AT_224_Ipdu is sent out every
AT_224_Sg1) with AT_224_Sg1_Value_1 (this value Period (TxMode True)
bus
does not change the signal TMC: TRUE) AT_224_Sg1 value
AT_224_GrSg1 value
AT_224_GrSg2 value
Step 3 [SWC] [LT]
Send signal AT_224_Sg1 (call Rte_Write() API for Port AT_224_Ipdu is sent out
AT_224_Sg1) with AT_224_Sg1_Value_2 (this value immediately and only 1 time
changes the signal TMC: FALSE) (TxMode False)
AT_224_Sg1 value
AT_224_GrSg1 value
AT_224_GrSg2 value
Step 4 [SWC] [LT]
AT_224_SgGr1.AT_224_GrSg1=AT_224_GrSg1_Valu AT_224_Ipdu is sent out
e_1 (this value changes the group signal TMC: TRUE) immediately and after each
AT_224_SgGr1.AT_224_GrSg2=AT_224_GrSg2_Valu Period (TxMode True)
e_Init AT_224_Sg1 value
call Rte_Write() for Port AT_224_SgGr1 is AT_224_Sg1_Value_2
AT_224_GrSg1 value
is AT_224_GrSg1_Value_1
AT_224_GrSg2 value
Step 5 [SWC] [LT]

AT_224_SgGr1.AT_224_GrSg1=AT_224_GrSg1_Valu AT_224_Ipdu is sent out every
e_2 (this value does not change the signal TMC: each Period (TxMode True)
TRUE) AT_224_Sg1 value
AT_224_SgGr1.AT_224_GrSg2=AT_224_GrSg2_Valu is AT_224_Sg1_Value_2
e_Init AT_224_GrSg1 value
call Rte_Write() for Port AT_224_SgGr1 is AT_224_GrSg1_Value_2
AT_224_GrSg2 value

conditions
7.3.11 [ATS_COMINDEP_00225] Manual Tx Mode Switch (TMS)

PERODIC/PERIODIC
Test Objective Manual Tx Mode Switch (TMS) PERODIC/PERIODIC
Releases
Modules
Requirement
on Acceptance
Test Document
bus
COM: SWS_Com_00229
COM: SWS_Com_00495
COM: SWS_Com_00602
COM: SWS_Com_00784
Reference
to Test
Environment
- ComTxModeTrue
--- timeOffset != timePeriod
--- timeOffset != timePeriod (different value from ModeTrue)
- ComSignalInitValue(ISignal.initValue) => TMC = FALSE
-- dataFilterType = NEW_IS_WITHIN
Summary Aim:
- Check that Ipdu group determines the correct Transmission Mode
[SWS_Com_00228][SWS_Com_00223] => TxModeFalse
- Check that SwitchIpduTxMode (FALSE) does not change the Tx mode
[SWS_Com_00784] => TxModeFalse
- Check that SwitchIpduTxMode (TRUE) changes the
mode [SWS_Com_00784][SWS_Com_00495] => TxModeTrue
- Check that a send signal changes the Tx Mode => TxModeFalse and even if TMC
is false signal is not filter out [SWS_Com_00602]
- Check that upate a signal (change TMC) and restart the IpduGroup determines the
new Transmission Mode [SWS_Com_00223][SWS_Com_00229] => TxModeTrue
- Test NEW_IS_WITHIN filter
Needed
Adaptation to In BswM R3.2.x, SwitchIPduMode action is
other Releases Configuration: [yes] not available. UserCallout action must be
used in this case.
Test Steps: [n/a]
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to AT_225_Ipdu is sent out after
BswMModeRequest port) to OffsetFalse and after each
IPDU_ACTIVATED (start Ipdu group PeriodFalse
AT_225_IpduGroup) AT_225_Sg1 value is

bus
Step 2 [SWC] [LT]
Request ModeSwitch (call to AT_225_Ipdu is sent out every
BswMModeRequest port) to PeriodFalse
TXMODE_FALSE (SwitchIpduTxMode to AT_225_Sg1 value is
FALSE) AT_225_Sg1_Value_Init
Step 3 [SWC] [LT]
BswMModeRequest port) to OffsetTrue and after each PeriodTrue
TXMODE_TRUE (SwitchIpduTxMode to AT_225_Sg1 value is
TRUE) AT_225_Sg1_Value_Init
Step 4 [SWC] [LT]
Update signal AT_225_Sg1 (Call Rte_Write AT_225_Ipdu is sent out after
for Port AT_225_Sg1) to OffsetFalse and after each
AT_225_Sg1_Value_1 (TMC keeps to PeriodFalse
FALSE) AT_225_Sg1 value is
AT_225_Sg1_Value_1
Step 5 [SWC] [LT]
Request ModeSwitch (call to AT_225_Ipdu Ipdu is not send out
IPDU_DEACTIVATED (stop Ipdu group
AT_225_IpduGroup)
Step 6 [SWC] [LT]
Update signal AT_225_Sg1 (Call Rte_Write() AT_225_Ipdu is not send out
for Port AT_225_Sg1) to
AT_225_Sg1_Value_2 (TMC keeps to
TRUE)
Step 7 [SWC] [LT]
BswMModeRequest port) to OffsetTrue and after each PeriodTrue
IPDU_ACTIVATED (start Ipdu group AT_225_Sg1 value is
AT_225_IpduGroup) (Initialize = FALSE) AT_225_Sg1_Value_2

conditions
7.3.12 [ATS_COMINDEP_00223] Manual Tx Send (Trigger IPdu Send) + MDT

Test Objective Manual Tx Send (Trigger IPdu Send) + MDT
Releases
Modules
on Acceptance
Test Document
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): AT_223_Ipdu
bus
- No ComTxModeFalse(transmissionModeFalseTiming)
- ComTxModeTrue
--- ComTxModeRepetitionPeriod(RepetitionPeriod) = y ms
- ComMinimumDelayTime (IPduTiming.minimumDelay) = x ms
=> constraint: x < y
configured)
Summary Aim:
- Check that Trigger Ipdu Send takes into account the MDT
- Check that Trigger Ipdu Send does not take into account the number of repetitions
Needed
Adaptation to In BswM R3.2.x, TriggerIpduSend action is
other Releases Configuration: [yes] not available. UserCallout action must be
used in this case.
Test Steps: [n/a]
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call Rte_Switch AT_223_Ipdu is not sent out
associated to BswMMode port) to
AT_223_IpduGroup)
Step 2 [SWC] [LT]
Send triggered signal AT_223_Sg1 (call The AT_223_Ipdu is sent two times
Rte_Write() API for Port AT_223_Sg1) with (number of repetitions and repetition
AT_223_Sg1_Value_1 period are respected)
AT_223_Sg1 value is
AT_223_Sg1_Value_1
Step 3 [SWC] [LT]
Wait DataSendCompletedEvent during DataSendCompletedEvent occurs
<TransmissionAckTimeout> before <TransmissionAckTimeout>
Step 4 [SWC] [SWC]
In Runnable activated by Return Value of Rte_Feedback is
DataSendCompletedEvent, Get RTE_E_TRANSMIT_ACK
Transmission Feedback of signal
AT_223_Sg1 (call Rte_Feedback)
Step 5 [SWC] [LT]
In Runnable activated by AT_223_Ipdu is sent out only 1 time
DataSendCompletedEvent, Request after MDT elapsed (MDT is respected,
ModeSwitch (call Rte_Switch associated to number of repetitions is ignored)
BswMMode port) to TRIG_IPDU_SEND AT_223_Sg1 value is
(action call TriggerIpduSend for AT_223_Sg1_Value_1
Ipdu_AT_223)
Step 6 [SWC] [SWC]

bus
Get Transmission Feedback of signal Return Value of Rte_Feedback is
AT_223_Sg1 (call Rte_Feedback) until RTE_E_TRANSMIT_ACK before
Return Value is RTE_E_TRANSMIT_ACK <TransmissionAckTimeout>
DataSendCompletedEvent was called
2 times (once after Rte_Write, once
after TriggerIpduSend)
conditions
7.3.13 [ATS_COMINDEP_00226] Ipdu and Trigger Transmit Callouts

Test Objective Ipdu and Trigger Transmit Callouts
Releases
Modules
Requirement
on
Acceptance
Test
Document
Requirements Use Case UC04.01
/ Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): AT_226_Ipdu1
- No ComTxModeFalse
- ComTxModeTrue
- ComIPduCallout is configured
ComIpdu(SignalIPdu): AT_226_Ipdu2
- No ComTxModeFalse
- ComTxModeTrue
-- NONE (no timing assigned)
- ComIPduTriggerTransmitCallout is configured
Hint: For Ipdu2 Trigger Transmit mechanism is needed. Therefore LIN, FlexRay or
CanNM Pdu should be used for Ipdu2.
Summary Aim:
1) Ipdu Callout [SWS_Com_00346][SWS_Com_00492]
bus
- Check that if return value of the callout is False, ipdu is not sent out
- Check that if return value of the callout is True, ipdu is sent out (and Ipdu value can
be modified by the callout)
- Check that trigger IpduSend call also the callout
2) Trigger Transmit Callout [SWS_Com_00346]
- Check that the return value of the Trigger Transmit Callout has no effect (Ipdu is
sent out even if the return value is false)
- Check if Trigger Transmit Callout modifies ipdu value, new value is taken into
account
Needed
Adaptation to
other
Releases
Pre- Com stack is initialized, but ipdu groups are running
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Update signal AT_226_Sg1 (call Rte_Write() AT_226_Ipdu1_Callout is called
API for Port AT_226_Sg1) with
AT_226_Sg1_Value_1
Step 2 [SWC] [LT]
In AT_226_Ipdu1_Callout, set return value to AT_226_IPdu1 is not sent out
FALSE
Step 3 [SWC] [SWC]
Update signal AT_226_Sg1 (call Rte_Write() AT_226_Ipdu1_Callout is called
API for Port AT_226_Sg1) with
AT_226_Sg1_Value_1
Step 4 [SWC] [LT]
In AT_226_Ipdu1_Callout, modify ipdu data AT_226_IPdu1 is sent out one time
(set AT_226_Sg1 value to AT_226_Sg1 value is
AT_226_Sg1_Value_2) AT_226_Sg1_Value_2
Set AT_226_Ipdu1_Callout return value to
TRUE
Step 5 [SWC] [SWC]
Call trigger ipdu send for AT_226_Ipdu1 by AT_226_Ipdu1_Callout is called
Requesting ModeSwitch (call Rte_Switch
associated to BswMMode port) to
TRIG_IPDU_SEND (action call
TriggerIpduSend for Ipdu_AT_226)
Step 6 [SWC] [LT]
In AT_226_Ipdu1_Callout, set return value to AT_226_IPdu1 is sent out one time
TRUE AT_226_Sg1 value is
AT_226_Sg1_Value_2
Step 7 [SWC] [LT]
Wait call of AT_226_IPdu2 is sent out one time
AT_226_Ipdu2_TriggerTransmitCallout AT_226_Sg2 value is
Set AT_226_Sg2_Value_Init
AT_226_Ipdu2_TriggerTransmitCallout return
value to FALSE
Step 8 [SWC] [LT]
Wait call of AT_226_IPdu2 is sent out one time
AT_226_Ipdu2_TriggerTransmitCallout AT_226_Sg2 value is
In AT_226_Ipdu2_TriggerTransmitCallout, AT_226_Sg2_Value_1
modify ipdu data (set AT_226_Sg2 value to
AT_226_Sg2_Value_1 different from init)
bus
Set
AT_226_Ipdu2_TriggerTransmitCallout return
value to TRUE
Step 9
[SWC]
Call Com_IpduGroupControl using [SWC]
generic BswM Request from The
Application SWC to stop the I-PDU ComIPduTriggerTransmitCallout
groups shall not be called
conditions
7.3.14 [ATS_COMINDEP_00723] Transmission Of An I-PDU having DIRECT Tx

Mode Consisting of Signal And Signal Group with Triggered On Change
Transfer Property
Test Transmission Of An I-PDU having DIRECT Tx Mode Consisting of Signal And Signal
Objective Group with Triggered On Change Transfer Property
Releases
Affected Com State proposed
Modules
Trace to
Requirement
on
Acceptance
Test
Document
COM: SWS_Com_00743
Requirements none
/ Reference
to Test
Environment
Configuration For signal properties, please refer to "AT_723 Signal Properties:" in chapter 6.1.2.1.1
Parameters For IPDU Structure, please refer to "AT_723_IPDU_Structure" in chapter 6.1.2.1.1
3
300 ms
confirmation of the respective I-PDU and data observed on the bus log.
Needed
Adaptation to
other
Releases
Pre- DUT shall be in Full communication state
conditions
Main Test Execution
bus
Step 1 [SWC] [SWC]
Trigger Rte_Write for Signal_13 and E_OK shall be returned for the request
Signal_12 with valid data
Step 2 - [LT]
Step 3 - [SWC]
configured signals should be invoked
Step 4 [SWC] [SWC]
Trigger Rte_Write for Signal_12 with same E_OK shall be returned for the request
data as before
Step 5 - [LT]
Corresponding frame is not transmitted
by the DUT
Step 6 [SWC] [SWC]
Trigger Rte_Write for Signal_11 E_OK shall be returned for the request
Signal_Group_11 and Signal_Group_12 with
valid data
Step 7 - [LT]
the DUT thrice for every Com
Step 8 - [SWC]
Step 9 [SWC] [SWC]
Trigger Rte_Write for Signal_Group_12 with E_OK shall be returned for the request
same data as before
Step 10 - [LT]
by the DUT
Post- None
conditions
7.3.15 [ATS_COMINDEP_00724] Transmission Of An I-PDU having MIXED Tx

Mode Consisting of Signal And Signal Group With Triggered On Change
Transfer Property
Test Transmission Of An I-PDU having MIXED Tx Mode Consisting of Signal And Signal
Objective Group With Triggered On Change Transfer Property
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document

bus
Requirements none
/ Reference
to Test
Environment
Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = MIXED
2
100 ms
Fibex::FibexCore::CoreCommunication::CyclicTiming.timePeriod = 500ms
Summary The transmission of assigned I-Pdu shall be verified using COM transmission
confirmation of the respective I-Pdu and data observed on the trace log.
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Step 2 - [LT]
Transmission Mode RepetitionPeriod
Step 3 - [SWC]
Step 4 [SWC] [SWC]
data as before
Step 5 - [LT]
by the DUT
Step 6 [SWC] [SWC]
Trigger Rte_Write for SignalGroup_14 and E_OK shall be returned for the request
SignalGroup_13 with valid data
Step 7 - [LT]
the DUT twice in a period of Com
and periodically for every Cycle time
Step 8 - [SWC]
Step 9 [SWC] [SWC]
Trigger Rte_Write for SignalGroup_13 with E_OK shall be returned for the request
same data as before
Step 10 - [LT]
bus
Immediate transmission of frame is not
observed and only regular periodic
instances of the frame are observed
Post- None
conditions
7.3.16 [ATS_COMINDEP_00725] Transmission Of An I-PDU having DIRECT Tx

Mode Consisting of Signal And Signal Group with TRIGGERED WITHOUT
REPETITION Transfer Property
Test Transmission Of An I-PDU having DIRECT Tx Mode Consisting of Signal And Signal
Objective Group with TRIGGERED WITHOUT REPETITION Transfer Property
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Requirements none
/ Reference
to Test
Environment
3
100 ms
confirmation of the respective I-PDU and data observed on the trace log.
Needed
Adaptation to
other
Releases
Pre- DUT shall be in Full communication mode
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Step 2 - [LT]
Frame shall be transmitted once by the
DUT
Step 3 - [SWC]
bus
Step 4 [SWC] [SWC]
valid data
Step 5 - [LT]
Frame shall be transmitted once by the
DUT
Step 6 - [SWC]
Post- None
conditions
7.3.17 [ATS_COMINDEP_00726] Transmission Of An I-PDU Having MIXED Tx

Mode Consisting of Signal And Signal Group with TRIGGERED WITHOUT
REPETITION Transfer Property
Test Transmission Of An I-PDU Having MIXED Tx Mode Consisting of Signal And Signal
Objective Group with TRIGGERED WITHOUT REPETITION Transfer Property
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Requirements none
/ Reference
to Test
Environment
3
100 ms
Fibex::FibexCore::CoreCommunication::CyclicTiming.timePeriod = 200 ms
Needed
Adaptation to
other
Releases

bus
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Step 2 - [LT]
Frame shall be observed once on the
bus immediately and periodically on
the bus by the DUT for every Com
Transmission Mode Time Period time
Step 3 - [SWC]
Step 4 [SWC] [SWC]
valid data
Step 5 - [LT]
Frame shall be observed once on the
bus immediately and periodically on
the bus by the DUT for every Com
Transmission Mode Time Period time
Step 6 - [SWC]
Post- None
conditions
7.3.18 [ATS_COMINDEP_00727] Transmission Of An I-PDU having MIXED Tx

Mode Consisting of Signal And Signal Group with TRIGGERED ON
CHANGE WITHOUT REPETITION Transfer Property
Test Transmission Of An I-PDU having MIXED Tx Mode Consisting of Signal And Signal
Objective Group with TRIGGERED ON CHANGE WITHOUT REPETITION Transfer Property
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Requirements none
/ Reference
to Test
Environment
bus
3
100 ms
Summary The transmission of assigned I-Pdu shall be verified using Com transmission
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Step 2 - [LT]
Frame shall be observed on the bus
immediately and periodically for every
Com Transmission Mode Time
Periodtime
Step 3 - [SWC]
Step 4 [SWC] [SWC]
data as before
Step 5 - [LT]
by the DUT
Step 6 [SWC] [SWC]
Trigger Rte_Write for Signal_Group_93 E_OK shall be returned for the request
valid data
Step 7 - [LT]
Frame shall be observed on the bus
immediately and periodically for every
Com Transmission Mode Time
Periodtime
Step 8 - [SWC]
Step 9 [SWC] [SWC]
Trigger Rte_Write for Signal_Group_91 with E_OK shall be returned for the request
same data as before
Step 10 - [LT]
Immediate transmission of frame is not
observed and only regular periodic
instances of the frame are observed
Post- None
conditions

bus
7.3.19 [ATS_COMINDEP_00728] Triggered Transmission Of An I-Pdu With

MIXED Mode And Minimum Delay Timer Configured
Test Triggered Transmission Of An I-Pdu With MIXED Mode And Minimum Delay Timer
Objective Configured
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Item
Requirements none
/ Reference
to Test
Environment
CoreCommunication::IPduTiming.minimumDelay = 300 ms
250 ms
2
Summary By using the Com_MinimumDelayTime we shall observe whether the immediate
transmission of the assigned I-Pdu is occurring or not.
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write for Signal_95 Signal_97 and E_OK shall be returned for the request
SignalGroup_96 with valid data
Step 2 - [LT]
Frames should be observed with the
value on bus by the DUT twice in a
period of 250ms and periodically for
every Com Transmission Mode
Repetition Period
Step 3 - [SWC]
should be invoked accordingly
bus
Step 4 [SWC] [SWC]
Call Rte_Write for SignalGroup_97 with valid E_OK shall be returned for the request
data before expiry of Minimum Delay Timer
Step 5 - [LT]
Corresponding Frame should not be
observed immediately on bus by the
DUT
Step 6 [SWC] [SWC]
Call Rte_Write for SignalGroup_97 with valid E_OK shall be returned for the request
data after expiry of Minimum Delay Timer
Step 7 - [LT]
Frames should be observed with the
value on bus by the DUT after Com
Minimum Delay Time twice in a period
of Com Transmission Mode Repetition
Period and periodically for every Com
Transmission Mode Time Period
Step 8 - [LT]
should be invoked accordingly
Post- None
conditions

PERIODIC
Test Objective Transmit I-PDU Callout With Tx Mode PERIODIC
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
Configuration For signal properties, please refer to "AT_729 Signal Properties:" in chapter
Parameters 6.1.2.1.1
For IPDU Structure, please refer to "AT_729_IPDU_Structure" in chapter 6.1.2.1.1
Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = PERIODIC
Fibex::FibexCore::CoreTopology::CommConnectorPort.communicationDirection =
SEND
ComIPduCallout = App_Com_Tx_IPdu_Request_Sn_74
Summary The invocation of I-Pdu callout shall be verified by configuring Com transmission I-
Pdu callout.
Needed
bus
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write for Signal_75 Signal_76 E_OK shall be returned for the
SignalGroup_74 and SignalGroup_75 with request
valid data
Step 2 [SWC] [SWC]
Call Rte_Write for Signal_74 with valid data E_OK shall be returned for the
request
Step 3 - [SWC]
Com transmission I-Pdu callout with
Data should be invoked periodically
for every Com Transmission Mode
Time Period
Post- None
conditions
7.3.21 [ATS_COMINDEP_00730] Transmit I-PDU Callout With Tx Mode MIXED

Test Objective Transmit I-PDU Callout With Tx Mode MIXED
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
Fibex::FibexCore::CoreCommunication.EventControlledTiming.numberOfRepetitions
=1
Fibex::FibexCore::CoreTopology::CommConnectorPort.communicationDirection =
SEND
ComIPduCallout = App_Com_Tx_IPdu_Request_Sn_80
Summary The invocation of I-Pdu callout shall be verified by configuring Com transmission I-
Pdu callout.
Needed
Adaptation to
other Releases

bus
Main Test Execution
Step 1 [SWC] [SWC]
Trigger Rte_Write for Signal_77 Signal_78 E_OK shall be returned for the
SignalGroup_77 and SignalGroup_78 with request
valid data
Step 2 [SWC] [SWC]
Trigger Rte_Write for Signal_80 with valid E_OK shall be returned for the
data request
Step 3 - [SWC]
Com transmission I-Pdu callout with
Data shall be invoked immediately
and periodically for every 500 ms
Post- None
conditions
7.3.22 [ATS_COMINDEP_00731] Verify The Update Bits In An IPDU With TX

MODE DIRECT when Com_Sendsignal / Com_SendSignalGroup is
invoked
Test Objective Verify The Update Bits In An IPDU With TX MODE DIRECT when Com_Sendsignal
/ Com_SendSignalGroup is invoked
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Requirements / none
Reference
to Test
Environment
Summary The update bit should be set in data observed on the trace log.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [SWC] [SWC]
Trigger Explicit Rte_Write for E_OK shall be returned for the
SignalGroup_43 Signal_43 and Signal_44 request
bus
with valid data
Step 2 - [LT]
Frame shall be transmitted on the bus
by the DUT and check if the updated
bits are updated for each signal
Step 3 - [SWC]
should be invoked
Step 4 [SWC] [SWC]
Trigger Explicit Rte_Write for Signal_44 with E_OK shall be returned for the
valid data request
Step 5 - [LT]
Frame shall be transmitted on the bus
by the DUT and check that the
updated bit is updated only for
Signal_44 and not for other two.
Step 6 - [SWC]
configured Signal_44 should be
invoked
Post- None
conditions
7.3.23 [ATS_COMINDEP_00732] Verify The Update Bits In An IPDU With TX

MODE PERIODIC when Com_Sendsignal / Com_SendSignalGroup is
invoked
Test Objective Verify The Update Bits In An IPDU With TX MODE PERIODIC when
Com_Sendsignal / Com_SendSignalGroup is invoked
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Requirements / none
Reference
to Test
Environment
Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = PERIODIC
Needed
Adaptation to

bus
other Releases
Main Test Execution
Step 1 [SWC] [SWC]
Trigger Explicit Rte_Write for Signal_45 E_OK shall be returned for the
Signal_46 and SignalGroup_45 with valid requests
data
Step 2 - [LT]
Frames shall be transmitted by the
DUT and check if the updated bits are
updated for each signal on the first
periodic transmission and no update
bits are set for the subsequent
transmissions
Step 3 - [SWC]
should be invoked
Step 4 [SWC] [SWC]
Trigger Explicit Rte_Write for Signal_45 and E_OK shall be returned for the
SignalGroup_45 with valid data requests
Step 5 - [LT]
Frames shall be transmitted on the
bus by the DUT and check that
updated bits are updated only for
Signal_45 and SignalGroup_45 but
not for Signal_46 on the first periodic
transmission
Step 6 - [SWC]
should be invoked
Post- None
conditions
7.3.24 [ATS_COMINDEP_00733] Verify The Update Bits In An IPDU With MIXED

TX MODE when Com_Sendsignal / Com_SendSignalGroup is invoked
Test Verify The Update Bits In An IPDU With MIXED TX MODE when Com_Sendsignal /
Objective Com_SendSignalGroup is invoked
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document

bus
Requirements none
/ Reference
to Test
Environment
2
100 ms
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Trigger Explicit Rte_Write for Signal_47 E_OK shall be returned for the request
SignalGroup_47 and Signal_48 with valid data
Step 2 - [LT]
updated for each signal on the
immediate transmission and no update
bits are set for the subsequent periodic
transmissions
Step 3 - [SWC]
should be invoked
Step 4 [SWC] [SWC]
Trigger Explicit Rte_Write for Signal_48 with a E_OK shall be returned for the request
different valid data
Step 5 - [LT]
updated for only Signal_48 on the
immediate transmission and no update
bits are set for the subsequent periodic
transmissions
Step 6 - [SWC]
should be invoked
Post- None
conditions

bus
7.3.25 [ATS_COMINDEP_00734] Signal Routing When Source And Destination
Signals/signal group have Update Bit And Update Bit Of The Received
Signal Is Not Set
Test Objective Signal Routing When Source And Destination Signals/signal group have Update Bit
And Update Bit Of The Received Signal Is Not Set
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
Configuration Rx_IPDU_SR STRUCTURE:
Parameters For IPDU Structure, please refer to "AT_734_Rx_IPDU_SR STRUCTURE" in
chapter 6.1.2.1.1
Tx_IPDU_SR STRUCTURE
For IPDU Structure, please refer to "AT_734_Tx_IPDU_SR STRUCTURE" in
chapter 6.1.2.1.1
Fibex::FibexCore::CoreCommunication::ISignalToIPduMapping.transferProperty =
TRIGGERED(For all the signals and signal groups configured)
Summary The routing of signal shall be verified observing data on the trace log.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send the frame Rx_IPDU_SR from Tester to Frame Tx_IPDU_SR is not
the DUT without setting any of the update transmitted by the DUT
bits configured
Step 2 [SWC] [SWC]
Trigger Rte_Write for Signal_66 with a valid E_OK shall be returned for the
data request
Step 3 - [LT]
Frame TX_IPDU_SR is transmitted
with just the updated value for
Signal_66 and no other signal has
updated values
Step 4 [LT] [LT]
Send the frame Rx_IPDU_SR from Tester to DUT transmits Frame TX_IPDU_SR
the DUT with all the signals with a different with the updated values and their
values and update bits set corresponding update bits se (except
Signal_66)t
Post- None
conditions
bus

Update Bit And Destination Signals has no Update Bit And Update Bit Of
The Received Signal Is Not Set
Test Objective Signal Routing When Source Signals Has Update Bit And Destination Signals has
no Update Bit And Update Bit Of The Received Signal Is Not Set
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
chapter 6.1.2.1.1
chapter 6.1.2.1.1
Summary The routing of signal shall be verified observing data on the trace log.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send the frame Rx_IPDU_SR from Tester to Frame Tx_IPDU_SR is not
the DUT without setting any of the update transmitted by the DUT
bits configured
Step 2 [SWC] [SWC]
Trigger Rte_Write for Signal_70 with a valid E_OK shall be returned for the
data request
Step 3 - [LT]
Frame TX_IPDU_SR is transmitted
with updated value for just Signal_70
and the routed signals without any
change in value.
Post- None
conditions

bus

Update Bit And Destination Signals has no Update Bit With Update Bit Of
The Received Signal Is Set
Test Objective Signal Routing When Source Signals Has Update Bit And Destination Signals has
no Update Bit With Update Bit Of The Received Signal Is Set
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
chapter 6.1.2.1.1
chapter 6.1.2.1.1
Summary The routing of signal shall be verified by data observed on the trace log.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [LT]
Send the frame Rx_IPDU_SR from Tester to Frame TX_IPDU_SR is not
the DUT without setting any of the update transmitted
bits configured
Step 2 [LT] [LT]
Send the frame Rx_IPDU_SR from Tester to Frame TX_IPDU_SR is transmitted
the DUT with all updated signals and their with all updated values
corresponding update bits set
Post- None
conditions

bus
7.3.28 [ATS_COMINDEP_00737] The Filter Mechanism Of
“MASKED_NEW_DIFFERS_MASKED_OLD” On Reception Of An I-Pdu
Test Objective The Filter Mechanism Of “MASKED_NEW_DIFFERS_MASKED_OLD” On
Reception Of An I-Pdu
Releases
Modules
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
Configuration ISignalIPdu RX_IPDU_FIL with:
Parameters Fibex::FibexCore::CoreCommunication::ISignalToPduMapping = Sn_51
Com Notification = Rte_ComCbk_Sn_51
Com Filter Algorithm = MASKED_NEW_DIFFERS_MASKED_OLD
ComFilterMask = 0xFF
SWComponentTemplate::Communcation::ComSpec.initValue or
SystemTemplate::Fibex::FibexCore::CoreCommuncation::ISignal.initValue.= 0x05
Summary The I-PDU is configured with a signal having filter mechanism of

“MASKED_NEW_DIFFERS_MASKED_OLD”. If the masked value has changed
then the filter should pass any signal or signal group.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [SWC]
Transmit the frame RX_IPDU_FIL with the Com notification for the configured
value different than the initial value (e.g. signal should be invoked
0x80)
Step 2 [SWC] [SWC]
Call Rte_Read for a Signal_51 Signal value should be the same as
transmitted one
Step 3 [LT] [SWC]
Transmit the frame RX_IPDU_FIL with the No notification is called
value same values as previous one (e.g.
0x80)
Step 4 [SWC] [SWC]
Rte_Read for a Signal_51 Data was the same as the last
received one
Step 5 [LT] [SWC]
Transmit the frame RX_IPDU_FIL with the Com notification for the configured
value different than the initial value (e.g. signal should be invoked
0x88)
Step 6 [SWC] [SWC]
Rte_Read for a Signal_51 Signal value should be newly
bus
transmitted value
Post- None
conditions

bus
8 RS_BRF_01648 - Large Data Type

This Test Specification intends to cover the communication transfer of data sizes
larger than the maximum transmission unit of the underlying bus as described in the
AUTOSAR Feature [RS_BRF_01648].
use the feature.
8.1.1 Test System

For this use case, the aim is to test general large data type transfer features

bus
Test System SUT

SWC
Lower
(Upper
Test)
PCO
PduR
CanTp FrTp LinTp LinSM
CanIf LinIf LinIf
Can Fr Lin
PCO Microcontroller
embedded SWC.

Not Applicable.

Not Applicable.


bus


OnEntry:
IPDU_ACTIVATED
-Start IpduGroup
OnEntry:
IPDU_DEACTIVATED
-Stop IpduGroup
OnEntry:
-Re-start IpduGroup
OnEntry:
TXMODE_TRUE
OnEntry:
TXMODE_FALSE
OnEntry:
TRIG_IPDU_SEND
-TriggerIpduSend
OnEntry:
LIN_START_SCHEDULE
OnEntry:
-Start IpduGroup
ART_SCHEDULE
For the Software Component point of view, for each test case, the communication
interfaces are defined as follow:

bus
Port name Data Dataelement Mapping Type
element
type
<TestCaseName>_<signalname> Uint8 <signalname> <Signalname> Signal
<TestCaseName>_<signalgroupname> Struct Groupsignal Groupsignal1->
{ <signal1name>
Uint8: Groupsignal2->
groupsignal1; <signal2name>
… <PortName>->
Uint8: <signalgroupname>
groupsignalx;
}

for communication queued Data Element (RTE restriction concerning Large Data
Type) and Explicit Data access for associated runnables.
8.1.2.1.1 Use Case 05.01: General features

AT_233_Sg1 AT_233_Sg1
AT_233_SgGr1
AT_233_GrSg2
AT_236_Sg1
AT_236_Sg1
(Not dynamic)
AT_236_Sg2
AT_236_Sg2
(dynamic)
AT_275_IpduGroup AT_275_Ipdu AT_275_Sg1 AT_275_Sg1 TestBench SUT



bus

 CAN, LIN and FlexRay frames identifiers

Not Applicable.

Not Applicable.
8.3 Test Cases

8.3.1 [ATS_COMINDEP_00233] DIRECT TP transmission
Test DIRECT TP transmission
Objective
ID ATS_COMINDEP_00233 AUTOSAR 4.0.3|4.1.1|4.2.1|4.2.2
Releases
Affected Com, PduR, BusTp, BusIf, BusDrv State reviewed
Modules
Requirement
on
Acceptance
Test
Document
Trace to COM: ECUC_Com_00761
SWS Item
s / Reference
to Test
Environment
Configuratio ComIpdu(SignalIPdu): AT_233_Ipdu1 (large I-PDU)
n - ComIPduType = TP(TpConfig.TpConnection)
- ComTxModeTrue
- ComSignalLength(baseTypeSize) > Size of <BUS> capability

bus
- Signal is queued
configured)
- Signal is queued
configured)
-- ComSignalInitValue
Summary Aim:
- Check that on User Request (triggered event) a TP transmission is executed by Com
module
- Check that TP transmission can be done only if ipdu group is started
- Test Tx notification
Sequence:
1) Action: Do a send Send signal
- Result: TP transmission is not done
2) Start ipdu group
3) Action: Send a triggered signal
- Result: TP transmission is done
- Result: Group Signal values are initial value
- Result: Signal value is changed
- Result: Signal and SignalGroup Tx notifications are called when the last segmented
frame is sent out
4) Action: Send a triggered signal group (after updating group signal)
- Result: Group Signal values are changed
- Result: Signal value is not changed
- Result: Signal and SignalGroup Tx notifications are called when the last segmented
frame is sent out
Needed
Adaptation Configuration: [n/a] Large data types and TP for regular COM is
to other not possible in R3.x.
Releases Test Steps: [n/a]
This test case shall be removed
conditions
Main Test Execution
Step 1 [SWC] [LT]
Call Rte_Send() for Port AT_233_Sg1 TP transmission is not done
(Rte will perform a send signal AT_233_Sg1)
Step 2 [SWC] [LT]
Request ModeSwitch (call to BswMModeRequest port) TP transmission is not done
to IPDU_ACTIVATED (start Ipdu group
AT_233_IpduGroup)
Step 3 [SWC] [LT]
Call Rte_Send() for Port AT_233_Sg1 with TP transmission is done
AT_233_Sg1_Value_1 AT_233_Sg1 value

bus
(Rte will send signal AT_233_Sg1 with is AT_233_Sg1_Value_1
AT_233_Sg1_Value_1) AT_233_GrSg1 value
AT_233_GrSg2 value
Step 4 - [SWC]
AT_233_Sg1 and
AT_233_SgGr1 notifications
(DataSendCompletedEvent)
are called when the last
segmented frame is sent out
Step 5 [SWC] [LT]
AT_233_SgGr1.AT_233_GrSg1=AT_233_GrSg1_Valu TP transmission is done
e_1 AT_233_Sg1 value
AT_233_SgGr1.AT_233_GrSg2=AT_233_GrSg2_Valu is AT_233_Sg1_Value_1
e_1 AT_233_GrSg1 value
call Rte_Send() for Port AT_233_SgGr1 is AT_233_GrSg1_Value_1
(Rte will send group signal AT_233_GrSg1 with AT_233_GrSg2 value
AT_233_GrSg1_Value_1, the, send group signal is AT_233_GrSg2_Value_1
AT_233_GrSg2 with AT_233_GrSg1_Value_2 and
finally send signal group AT_233_SgGr1)
Step 6 - [SWC]
AT_233_Sg1 and
AT_233_SgGr1 notifications
(DataSendCompletedEvent)
are called when the last
segmented frame is sent out
conditions
8.3.2 [ATS_COMINDEP_00234] PERIODIC TP transmission

Test Objective PERIODIC TP transmission
Releases
Affected Com, PduR, BusTp, BusIf, State reviewed
Modules BusDrv
Requirement
on Acceptance
Test Document
Trace to SWS COM: ECUC_Com_00761
Item
Reference
to Test
Environment
Configuration ComIpdu(SignalIPdu): AT_234_Ipdu1 (large I-PDU)
Parameters - ComIPduType = TP(TpConfig.TpConnection)
- ComTxModeTrue

bus
- Signal is queued
configured)
Summary Aim:
- Check that a periodic TP transmission is executed by Com module
Sequence:
1) Start ipdu group
- Result: first TP transmission is done after OffsetTime
- Result: other TP transmissions are started every PeriodTime
- Signal value is the initial value
2) Action: Update a pending signal
- Result: Periodic sent are not disturbed
- Result: Signal value is changed
Needed
Adaptation to Configuration: [n/a] Large data types and TP for regular COM is
other Releases not possible in R3.x.
Test Steps: [n/a]
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to First TP transmission is done after
BswMModeRequest port) to OffsetTime, other TP transmissions
IPDU_ACTIVATED (start Ipdu group are started every PeriodTime
AT_234_IpduGroup) AT_234_Sg1 value
is AT_234_Sg1_Value_Init
Step 2 [SWC] [LT]
Call Rte_Send() for AT_234_Sg1 with Periodic sent are not disturbed
AT_234_Sg1_Value_1 AT_234_Sg1 value is now
(Update a pending signal AT_234_Sg1 AT_234_Sg1_Value_1
with AT_234_Sg1_Value_1)
conditions
8.3.3 [ATS_COMINDEP_00235] MIXED TP transmission

Test Objective MIXED TP transmission
Releases
Modules BusDrv
Requirement
bus
on Acceptance
Test Document
Trace to SWS COM: ECUC_Com_00761
Item
Reference
to Test
Environment
Parameters - ComIPduType = TP(TpConfig.TpConnection)
- ComTxModeTrue
-- MIXED(EventControlledTiming and CyclicTiming)
- Signal is queued
configured)
Summary Aim:
- Check that a periodic TP transmission is executed by Com module
- Check that on User Request (triggered event) a TP transmission is executed by
Com module
Sequence:
1) Start ipdu group
- Result: TP transmission is done periodically
- Result: one event TP transmission is inserted between two periodic TP
transmissions
Needed
Adaptation to Configuration: [n/a] Large data types and TP for regular COM is
other Releases Test Steps: [n/a] not possible in R3.x.
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to TP transmission is done periodically
BswMModeRequest port) to AT_235_Sg1 value
IPDU_ACTIVATED (start Ipdu group is AT_235_Sg1_Value_Init
AT_235_IpduGroup)
Step 2 [SWC] [LT]
Call Rte_Send() for Port AT_235_Sg1 with One event TP transmission is inserted
AT_235_Sg1_Value_1 ( Rte will send a between two periodic TP
triggered signal AT_235_Sg1 with transmissions
AT_235_Sg1_Value_1 ) AT_235_Sg1 value is now
AT_235_Sg1_Value_1
conditions
bus
8.3.4 [ATS_COMINDEP_00236] Dynamic send message

Test Dynamic send message
Objective
Releases
Affected Com, PduR, BusTp, BusIf, BusDrv State reviewed
Modules
Requirement
on
Acceptance
Test
Document
s / Reference
to Test
Environment
Configuratio ComIpdu(SignalIPdu): AT_236_Ipdu1 (large I-PDU)
n Parameters - ComIPduType = TP(TpConfig.TpConnection)
-
ComTxModeTrue(IPduTiming.TransmissionModeDeclaration.transmissionModeTrueTi
ming)
-- DIRECT(EventControlledTiming)
- ComSignalType(networkRepresentationProps.swBaseType) != UINT8_DYN
- ComBitSize(ISignal.length) = 8 bits
- ComSignalType(swBaseType + SystemSignal.dynamicLength) = UINT8_DYN(No
BaseTypeEncoding/BaseTypeSize=maxBaseTypeSize + dynamicLength=true)
- ComSignalLength(baseTypeSize) = 254 bytes
for Sg1/Sg2:
- Signal is queued
configured)
Summary Aim:
- Check that dynamic send is taken into account for the TP transmission
Sequence:
1) Start ipdu group
2) Action: update pending signal (Sg1)
3) Action: Send a triggered dynamic signal (Sg2) (ipdu length lower than a SF)
- Result: TP IPDU length is adjusted (only Single frame is sent)
- Result: Sg1 and Sg2 values are different from initial values
bus
4) Action: Send a triggered dynamic signal (Sg2) (ipdu length greater than a SF)
- Result: TP IPDU length is adjusted (complete TP exchange is done, FF, CF and FC
(except for Lin))
- Result: Sg1 and Sg2 values are different from initial values
Needed
Adaptation Configuration: [n/a] Transmission of dynamic messages is not
to other Test Steps: [n/a] possible in R3.x.
Releases This test case shall be removed
conditions
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to No frame sent out
AT_236_IpduGroup)
Step 2 [SWC] [LT]
Call Rte_Send() for Port AT_236_Sg1 with No frame sent out
AT_236_Sg1_Value_1
(Rte will send the pending signal
(AT_236_Sg1) with AT_236_Sg1_Value_1)
Step 3 [SWC] [LT]
Call Rte_Send(<data>, <length = 5>) for Port Only 1 Single frame (FlexRay = STF
AT_236_Sg2 with value Start Frame) is sent.
AT_236_Sg2_Value_1(Rte will send a AT_236_Sg1 (1 byte) value is
triggered dynamic signal (AT_236_Sg2) (length AT_236_Sg1_Value_1 (Static Length)
is 5) with AT_236_Sg2_Value_1) AT_236_Sg2 (5 bytes) value is
AT_236_Sg2_Value_1 (Dynamic
Length)
Data bytes Length (SF_DL / STF_ML)
is 6 bytes
Step 4 [SWC] [LT]
Call Rte_Send(<data>, <length = 254>) for TP transmission is started: First frame
Port AT_236_Sg2 with AT_236_Sg2_Value_2 (FlexRay = STF Start Frame) is sent.
( Rte will send a triggered dynamic signal Data bytes Length (FF_DL / STF_ML)
(AT_236_Sg2 ) (length is 254) with is 255 bytes
AT_236_Sg2_Value_2) complete TP exchanges are done
(CF...)
AT_236_Sg1 (1 byte) value is
AT_236_Sg1_Value_1 (Static Length)
AT_236_Sg2 (254 bytes) value is
AT_236_Sg2_Value_2 (Dynamic
Length)
conditions
8.3.5 [ATS_COMINDEP_00238] Stop Ipdu group even if TP transmission is not

complete
Test Objective Stop Ipdu group even if TP transmission is not complete

bus
Releases
Modules BusDrv
Requirement
on Acceptance
Test Document
Reference
to Test
Environment
Parameters - length is very large (many Consecutive Frame are needed - more than 2 -
depending on <BUS> capability)
- ComIPduType = TP(TpConfig.TpConnection)
- ComTxModeTrue
-- DIRECT(EventControlledTiming)
- Signal is queued
configured)
- ComErrorNotification is configured
Summary Aim:
- Check that stop an ipdu group cancel the ongoing TP transmission
Sequence:
1) Start ipdu group
- Result: TP transmission is started
3) Action: Stop ipdu group before all consecutives frames are sent out
- Result: TP transmission is stopped
- Result: SIgnal error notification is called
Needed
Adaptation to Configuration: [n/a] Transmission of dynamic messages is not
other Releases possible in R3.x.
Test Steps: [n/a]
Main Test Execution
Step 1 [SWC] [LT]
Request ModeSwitch (call to TP transmission is not done
AT_238_IpduGroup)

bus
Step 2 [SWC] [LT]
Call Rte_Send() for Port AT_238_Sg1 with TP transmission is started (First
AT_238_Sg1_Value (send a triggered signal Frame is sent out)
AT_238_Sg1 with AT_238_Sg1_Value)
Step 3 - [SWC]
Return Value of Rte_Feedback for
AT_238_Sg1 is RTE_E_NO_DATA
Step 4 [SWC]
AT_238_IpduGroup (and BUS shall not send
the Flow Control frame))
Step 5 [CP] [SWC]
Wait 200ms Return Value of Rte_Feedback for
AT_238_Sg1 is
RTE_E_COM_STOPPED (Signal
error notification was called by SUT)
AT_238_Sg1
called
Step 6 [LT] [LT]
Send the Flow Control frame (except for LIN No consecutives frames are sent out
bus where Flow Control is not needed)
conditions
8.3.6 [ATS_COMINDEP_00275] Stop Ipdu group even if TP Reception is not

complete
Test Objective Stop Ipdu group even if TP Reception is not complete
Releases
Modules BusDrv
Trace to
Requirement
on Acceptance
Test Document
Item
Requirements / Use Case UC1
Reference
to Test
Environment
Parameters - length is very large (many Consecutive Frame are needed - more than 2 -
depending on <BUS> capability)
- ComIPduType = TP(TpConfig.TpConnection)
- ComIPduDirection(CommConnectorPort.communicationDirection) = RECEIVE
- Signal is queued
- DataReceivedEvent mapped on signal reception (ComNotification is configured)
bus
Summary Aim:
- Check that stop an ipdu group cancel the ongoing TP reception
Sequence:
1) Start ipdu group
2) Action: Lower Tester Send FF of TP frame
- Result: TP reception is started
3) Action: Stop ipdu group before all consecutives frames are sent out
- Result: TP reception is stopped
- Result: partly received Data is not provided to SWC
Needed
Adaptation to Configuration: [n/a] Transmission of dynamic messages is not
other Releases possible in R3.x.
Test Steps: [n/a]
Main Test Execution
Step 1 [SWC]
AT_275_IpduGroup)
Step 2 [LT] [LT]
Send AT_275_Sg1 with TP transmission is started (First
AT_275_Sg1_Value1 (First Frame of TP Frame is sent out)
Frame is sent)
Step 3 [LT] [LT]
Wait Flow Control frame from SUT (except Flow Control frame is received
for LIN bus where Flow Control is not
needed)
Step 4 [SWC]
AT_275_IpduGroup)
Step 5 [LT]
Consecutive Frame shall not be sent
Step 6 [LT] [LT]

Send the Consecutive Frame No Flow Control frame is received
(except for LIN bus where Flow
Control is not needed)
Step 7 [SWC] [SWC]
Read value of AT_275_Sg1 (Rte_Receive()) Return Value of Rte_Receive is
RTE_E_NO_DATA
DataReceivedEvent never called
conditions

bus
Consisting Of A Dynamic Signal With Periodic Mode And Having
ComTransferProperty As TRIGGERED
Test Unsuccessful Transmission Of An I-PDU Consisting Of A Dynamic Signal With Periodic
Objective Mode And Having ComTransferProperty As TRIGGERED
Releases
Modules
Trace to
Requireme
nt on
Acceptanc
e Test
Document
SWS Item
Requireme none
nts /
Reference
to Test
Environme
nt
Configurat Signal:Signal_101
ion Fibex::FibexCore::CoreCommunication::ISignalToIPduMapping.transferProperty =
Parameter TRIGGERED
s Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = PERIODIC
Fibex::FibexCore::CoreCommunication::CyclicTiming.timePeriod = 300
CoreCommunication::IPduTiming.minimumDelay = 200
SystemTemplate::Fibex::FibexCore::CoreCommuncation::ISignal.initValue = 0
SystemTemplate::Fibex::FibexCore::CoreCommunication::SystemSignal.networkReprese
ntationProps.swBaseType = UINT8_DYN
Datatype::DataTypes::OpaqueType.numberOfBits = 8
Summary The unsuccessful transmission of the assigned I-PDU shall be verified configuring the
mode to PERIODIC and the signal has Triggered transfer property.
Needed
Adaptatio
n to other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write for Signal_101 with valid array of E_OK shall be returned for the request
data and its length
Step 2 - [LT]
Respective IPDU is not transmitted by
DUT.
Post- None
conditions

bus
Consisting Of A Dynamic Signal Having ComTransferProperty As
PENDING
Test Unsuccessful Transmission Of An I-PDU Consisting Of A Dynamic Signal Having
Objective ComTransferProperty As PENDING
Releases
Modules
Trace to
Requireme
nt on
Acceptanc
e Test
Document
SWS Item
Requireme none
nts /
Reference
to Test
Environme
nt
Configurat Signal :Signal_108
ion Fibex::FibexCore::CoreCommunication::ISignalToIPduMapping.transferProperty =
Parameter PENDING
s Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = DIRECT
SystemTemplate::Fibex::FibexCore::CoreCommuncation::ISignal.initValue = 0
Datatype::DataTypes::OpaqueType.numberOfBits = 8
Summary The unsuccessful transmission of the assigned I-PDU shall be verified by configuring the
transfer property as PENDING along with other required parameters.
Needed
Adaptatio
n to other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Call Rte_Write for Signal_108 with valid array of E_OK shall be returned for the request
data and length
Step 2 - [LT]
Respective frame shall be not be
transmitted immediately.
Post- None
conditions

bus
8.3.9 [ATS_COMINDEP_00741] Reception Of Dynamic Length I-PDU
Test Reception Of Dynamic Length I-PDU
Objective
Releases
Modules
Trace to
Requireme
nt on
Acceptanc
e Test
Document
SWS Item
Requireme none
nts /
Reference
to Test
Environme
nt
Configurat Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = DIRECT
ion Fibex::FibexCore::CoreTopology::CommConnectorPort.communicationDirection =
Parameter RECEIVE
s ComNotification = Rte_ComCbk_Sig_052
Summary The AUTOSAR COM module shall calculate the length of the contained dynamic length
signal and Com I-Pdu callout shall notify the SWC.
Needed
Adaptatio
n to other
Releases
conditions
Main Test Execution
Step 1 [LT] [COM]Com notification for the configured
Transmit the frame from TESTER with the signal shall be invoked
dynamic length signal and its size
Step 2 [SWC] [SWC]
Call inter Rte_read for Signal_052 E_OK shall be returned for the request
with the transmitted value
Post- None
conditions
8.3.10 [ATS_COMINDEP_00742] Reception Of A Large I-PDU Via The TP

Interface
Test Reception Of A Large I-PDU Via The TP Interface
Objective

bus
Releases
Modules
Trace to
Requirem
ent on
Acceptanc
e Test
Document
SWS Item
Requirem none
ents /
Reference
to Test
Environm
ent
Configurat Fibex::FibexCore::CoreCommunication::TransmissionModeTiming = DIRECT
ion Fibex::FibexCore::CoreTopology::CommConnectorPort.communicationDirection =
Parameter RECEIVE
s TransportProtocols::CanTpConnection = TP
ComNotification = Rte_ComCbkTAck_Sig_053
ntationProps.swBaseType= UINT8
Summary The I-PDU reception will be verified by using reception confirmation
Needed
Adaptatio
n to other
Releases
conditions
Main Test Execution
Step 1 [LT] [SWC]
Transmit the frame from TESTER with valid Com notification for the configured signal
value for the large IPDu shall be invoked
Step 2 [SWC] [SWC]
Call inter Rte_read for a Signal_053 Rte return E_OK and data shall be
updated
Post- None
conditions
8.3.11 [ATS_COMINDEP_00743] Data Sequence control when Received I-PDU

counter is greater than expected I-PDU counter + threshold
Test Objective Data Sequence control when Received I-PDU counter is greater than expected I-
PDU counter + threshold
Releases
Modules
Trace to
Requirement
bus
on Acceptance
Test Document
Item
Requirements / none
Reference
to Test
Environment
Configuration Fibex::FibexCore::CoreCommunication::SignalIPduCounter.pduCounterThreshold =
Parameters 1
Fibex::FibexCore::CoreCommunication::SignalIPduCounter.pduCounterSize = 4 bits
Fibex::FibexCore::CoreCommunication::SignalIPduCounter.pduCounterStartPosition
=2
ComI-PDUCounterErrorNotification = App_Rte_Com_CbkCounterErr_55
ComNotification = Rte_ComCbkTAck_Sig_055
SystemTemplate::Fibex::FibexCore::CoreCommuncation::ISignal.initValue = 0x22
Summary The mismatch of the expected and received I-PDU counter is achieved by using the
configured error notification for a signal.
Needed
Adaptation to
other Releases
Main Test Execution
Step 1 [LT] [SWC]
Transmit the Frames with counter value Com notification for the configured
updated counters and signal values signal shall be invoked
incremented every time
Step 2 [SWC] [SWC]
Call Rte_Read for the configured Signal Correct value of the signal shall be
received
Step 3 [LT] [SWC]
Transmit the frame with wrong IPDU counter Com I-Pdu Counter Error Notification
for the configured signal with
Expected Counter Value and
Received Counter Value shall be
invoked
Step 4 [SWC] [SWC]
Call Rte_Read for the configured Signal Rte shall provide the previously
received value
Post- None
conditions

bus
9 Miscellaneous features
This test suite provides additional test cases for miscellaneous features of the Bus
Independent features, when they do not require a complete test suite on their own.
9.1.1 Test System

For this use case, the aim is to test general large data type transfer features
Test System SUT

SWC
Lower
(Upper
Test)
PCO
PduR
CanTp FrTp LinTp LinSM
CanIf LinIf LinIf
Can Fr Lin
PCO Microcontroller
embedded SWC.

None

Not Applicable.
bus

The configuration required to implement and execute the test cases is described in
the “Configuration Parameters” field of each test case.

Not Applicable.
9.3 Test Cases
9.3.1 [ATS_COMINDEP_00744] Check The Functionality Of

PduR_EnableRouting And PduR_DisableRouting
Test Check The Functionality Of PduR_EnableRouting And PduR_DisableRouting
Objective
Releases
Affected PDUR State reviewed
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Trace to SWS PDURouter: SWS_PduR_00615
Item PDURouter: SWS_PduR_00617
Requirement none
s / Reference
to Test
Environment
Configuratio BswPduRouterAction = BSWM_PDUR_E-BLE
n Parameters BswPduRouterAction = BSWM_PDUR_DISABLE
BswMUserCallout = App_PduR_User_RENBL(callout for enabling the PduR uting)
App_PduR_User_RDSBL(callout for disabling the PduR routing)PduRUpperModule =
TRUE(Com)
PduRLowerModule = TRUE(CanIf)
PduRDestPduDataProvision = PDUR_DIRECT(CanIf)
Frame Configuration:
Fibex::FibexCore::CoreCommunication::Timing.EventControlledTiming.numberOfRepe
ats = Ex: 2 (user configurable)
Fibex::FibexCore::CoreCommunication::EventControlledTiming.repetitionPeriod = Ex:
100 ms (user configurable)
Summary The functionality of PduR_EnableRouting and PduR_DisableRouting shall be achieved
by using the BswM module’s functionality BswMPduRouterControl action where a
configured user callout shall be invoked in ComM current state notification which will in
turn switch the BswM mode.
Needed
Adaptation to
other
Releases
Pre- DUT shall be in Full Communication
bus
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Invoke Rte_Write for sending the data. Rte_Write shall return RTE_E_OK.
Step 2 - [LT]
The respective frame is not transmitted
on the bus.
Step 3 [SWC] [SWC]
SendBswM_RequestMode for changing BswM Callout function
mode to disable the routing. App_PduR_User_RDSBL shall be
invoked indicating the call of
PduR_DisableRouting
Step 4 [SWC] [SWC]
Invoke Rte_Write for sending the data. Rte_Write shall return RTE_E_OK.
Step 5 [SWC] [SWC]
SendBswM_RequestMode for changing BswM Callout function
mode to enable the routing. App_PduR_User_RENBL shall be
invoked indicating the call of
PduR_EnableRouting
Step 6 [SWC] [LT]
Invoke Rte_Write for sending the data. Tester shall observe for expected
frames on bus.
Post- None
conditions
9.3.2 [ATS_COMINDEP_00745] Interface PDU Transmission During Singlecast

When Source PDU Belongs To Com And Destination PDU Belongs To
CanIf
Test Interface PDU Transmission During Singlecast When Source PDU Belongs To Com
Objective And Destination PDU Belongs To CanIf
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
PDURouter: SWS_PduR_00626
Requirement none
s / Reference
to Test
Environment
Configuratio PduRUpperModule = TRUE(Com)
n Parameters PduRLowerModule = TRUE(CanIf)
PduRTxConfirmation = TRUE
PduRDestPduDataProvision = PDUR_DIRECT
bus
ComNotification = App_Com_CbkTxAck_TC_002(callback function to be called on
Sender side)
Signal = Signal_TC2Tx
Summary The required functionality shall be tested indirectly through Rte confirmation for the
configured signal and the data observed on the trace log.
Needed
Adaptation to
other
Releases
Pre- DUT should be in full communication
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Invoke Rte_Write for sending the data with Rte_Write shall return RTE_E_OK.
Signal_TC2Tx.
Step 2 - [LT]
Tester shall observe for expected
frames on bus.
Step 3 - [SWC]
Com notification
App_Com_CbkTxAck_TC_002 shall be
invoked
Post- None
conditions
9.3.3 [ATS_COMINDEP_00746] Interface PDU Transmission During Multicast

When Source PDU Is From Com Module And Destination PDU Belongs
To Lower Layer (CanIf, LinIf, FRIF)
Test Interface PDU Transmission During Multicast When Source PDU Is From Com Module
Objective And Destination PDU Belongs To Lower Layer (CanIf, LinIf, FRIF)
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Requirement none

bus
s / Reference
to Test
Environment
n Parameters PduRLowerModule = TRUE(CanIf LinIf FrIf)
PduRTriggerTransmit = TRUE
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(LinIf)
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(FrIf)
Summary The required functionality shall be achieved by invoking Rte_Write and observing the
data on the trace log. It’s an indirect testing.
Needed
Adaptation to
other
Releases
conditions Lin and FlexRay schedule table shall be started
Main Test Execution
Step 1 [SWC] [SWC]
Invoke Rte_Write for sending the data with Rte_Write shall return RTE_E_OK.
Signal_TC3Tx.
Step 2 - [LT]
Tester shall observe for expected CAN
LIN & FlexRay frames on bus.
Post- None
conditions
9.3.4 [ATS_COMINDEP_00747] Frame Gateway From CanIf To LinIf, CanIf And

FrIf
Test Frame Gateway From CanIf To LinIf, CanIf And FrIf
Objective
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
Item

bus
Requirement none
s / Reference
to Test
Environment
n Parameters PduRLowerModule = TRUE(CanIf LinIf Frif)
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(LinIf)
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(FrIf)
Summary The required functionality shall be achieved by sending the data from tester and the
frame is replicated in other buses. This can be confirmed by observing it on the trace
log for the corresponding gateway frames.
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [LT] [SWC]
Transmit the source CAN frame from the tester Com notification for the corresponding
signal shall be invoked
Step 2 - [LT]
Tester shall observe for expected
frames in CANLIN and FlexRay buses.
Post- None
conditions
9.3.5 [ATS_COMINDEP_00748] Tp PDU Transmission During Singlecast When

Source PDU Belongs To Com and Destination PDU Belongs To CanTp
Test Tp PDU Transmission During Singlecast When Source PDU Belongs To Com and
Objective Destination PDU Belongs To CanTp
Releases
Modules
Trace to
Requirement
on
Acceptance
Test
Document
bus
Requirement none
s / Reference
to Test
Environment
n Parameters PduRLowerModule = TRUE(CanTp)
PduRDestPduDataProvision = PDUR_DIRECT(CanTp)
ComNotification = App_Com_CbkTxAck_TC_009(Com transmission confirmation)
Summary The required functionality shall be tested indirectly through Rte confirmation for the
configured signal and the data observed on the trace log.
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [SWC] [SWC]
Invoke Rte_Write for Signal_TC9Tx with data. Rte_Write shall return RTE_E_OK.
Step 2 - [LT]
Corresponding frame is transmitted on
the bus.
Step 3 - [SWC]
Com transmission confirmation
App_Com_CbkTxAck_TC_009 shall be
invoked.
Post- None
conditions
9.3.6 [ATS_COMINDEP_00749] Frame Gateway From CanTp To LINTP, CanTp

and FrTp
Test Frame Gateway From CanTp To LINTP, CanTp and FrTp
Objective
Releases
Modules
Trace to
Requirement

bus
on
Acceptance
Test
Document
Item
Requirement none
s / Reference
to Test
Environment
n Parameters PduRLowerModule = TRUE(CanTp FrTp LinTp)
PduRDestPduDataProvision = PDUR_DIRECT(CanTp)
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(FrTp)
PduRDestPduDataProvision = PDUR_TRIGGERTRANSMIT(LinTp)
ComNotification = App_Com_CbkRxAck_TC_013
Summary The required functionality shall be achieved by sending the data from tester and finally
observing it on the trace log for the corresponding gateway signal.
Needed
Adaptation to
other
Releases
conditions
Main Test Execution
Step 1 [LT] [SWC]
Transmit the configured TP frame to the DUT. Com notification
App_Com_CbkRxAck_TC_013 for the
configured signal shall be invoked after
the complete reception of the frame
Step 2 - [LT]
Same frame shall be observed also on
the other buses also.
Post- None
conditions


Document Title: Acceptance Test Specification of Communication Via Bus

Uploaded by

Copyright:

Available Formats

Document Title: Acceptance Test Specification of Communication Via Bus

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Document Title: Acceptance Test Specification of Communication Via Bus

Uploaded by

Copyright:

Available Formats

Acceptance Test Specification of Communication via

Document Title Acceptance Test Specification

Document Status Final

Document Change History

1 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

Advice for users

AUTOSAR specifications may contain exemplary items (exemplary reference

2 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

1 Acronyms and abbreviations .............................................................................. 8

3 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

7 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

1 Acronyms and abbreviations

8 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

9 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3 RS_BRF_01600 - Timeout Handling

3.1.1 Test System

3.1.1.1.1 Use case 01.01: Deadline Monitoring

10 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

11 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.1.1.2 Specific Requirements

3.1.1.3 Test Coordination Requirements

12 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.1.2.1 Required ECU Extract of System Description Files

A Mode-Switch Interface IF_AT_SwC_ActionsBswM must be created. The SWC

ModeDeclaration BswM Actions

13 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

Unless a different configuration is specified in test case, Sender/Receiver Ports used

The communication database is depicted below:

IPduGroup IPdu SignalGroup Signal Tx ECU Rx ECU

AT_738 Signal Properties:

Sn_83 150 500 App_Rte_Com_CbkRxTOut_Sn_81 NONE

Sn_84 50 500 App_Rte_Com_CbkRxTOut_Sn_82 NONE

Sg84 150 500 App_Rte_Com_CbkRxTOut_Sg80 NONE

3.1.2.2 Required ECU Configuration Description Files

3.1.2.3 Required Software Component Description Files

3.1.2.4 Mandatory vs. Customizable Parts

Customizable parameters are (these values are test case independent):

3.1.3 Test Case Design

3.2 Re-usable Test Steps

3.3 Test Cases

3.3.1 [ATS_COMINDEP_00100] Managing Rx signal deadline timeout with

15 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

For all ComSignal/ComSignalGroup (ISignalToPduMapping):

 Deadline timeout occurs independently (with configured timeout value) for

16 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.3.2 [ATS_COMINDEP_00101] Managing Rx signal group deadline timeout

18 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.3.3 [ATS_COMINDEP_00102] Managing Tx Ipdu deadline timeout

- If applied on FlexRay/LIN bus, Tester must be intrusive to block the notification

3.3.4 [ATS_COMINDEP_00104] Disabling/Enabling Rx Deadline monitoring

Use Case 1, Rx Deadline monitoring disabled:

Use Case 2, Rx Deadline monitoring enabled:

21 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.3.5 [ATS_COMINDEP_00105] Managing Rx Ipdu deadline timeout without

If applied on Flexray bus:

If applied on CAN/LIN bus:

23 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

24 of 165 Document ID 666: AUTOSAR_ATS_CommunicationViaBus

3.3.7 [ATS_COMINDEP_00738] Signal With ComRxDataTimeoutAction Set To