9 OA Automotive Ethernet ECU TestSpecification v1 PDF
9 OA Automotive Ethernet ECU TestSpecification v1 PDF
9 OA Automotive Ethernet ECU TestSpecification v1 PDF
Version 1.0
Status Released
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 2
OPEN Alliance
Disclaimer
The OPEN Specifications (including any part thereof) are intended to be used as an information source
to enable to manufacture and test products which comply with the OPEN Specifications.
All OPEN Specifications are provided on “as is” basis and all warranties, either explicit or implied, are
excluded unless mandatory under law. Accordingly, the OPEN Alliance Members who have contributed
to the OPEN Specifications make no representations or warranties with regard to the OPEN
Specifications or the information (including any software) contained therein, including any warranties of
merchantability, fitness for purpose, or absence of third party rights and make no representations as to
the accuracy or completeness of the OPEN Specifications or any information contained therein.
The OPEN Alliance Members who have contributed to the OPEN Specifications will not be liable for any
losses, costs, expenses or damages arising in any way out of use or reliance upon any OPEN Specification
or any information therein. Nothing in this document operates to limit or exclude any liability for fraud
or any other liability which is not permitted to be excluded or limited by operation of law.
The material contained in OPEN Specifications is protected by copyright and may be subject to other
types of Intellectual Property Rights. OPEN Specifications (or any part thereof) shall be distributed only
among those bound by the confidentiality defined for the OPEN Specification and as announced in the
OPEN Specification documents.
The distribution of OPEN Specifications shall not operate as an assignment or license to any recipient of
any OPEN Specification of any patents, registered designs, unregistered designs, trademarks, trade
names or other rights as may subsist in or be contained in or reproduced in any OPEN Specification. The
commercial exploitation of the material in this document may require such a license, and any and all
liability arising out of use without such a license is excluded.
OPEN Specification documents may be reproduced in electronic or paper form or utilized in order to
achieve the Scope only. Reproduction or utilization for any other purposes as well as any modification of
the Specification document, in any form or by any means, electronic or mechanical, including
photocopying and microfilm, is explicitly excluded.
Without prejudice to the foregoing, the OPEN Alliance Specifications have been developed for
automotive applications only. They have neither been developed, nor tested for non-automotive
applications.
OPEN Alliance reserves the right to withdraw, modify, or replace any OPEN Specification at any time,
without notice.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 3
OPEN Alliance
Contents
1 Introduction .......................................................................................................................................... 7
1.1 Overview ....................................................................................................................................... 7
1.2 Feedback ....................................................................................................................................... 7
1.3 References .................................................................................................................................... 8
1.4 Definition of Test Scopes .............................................................................................................. 8
1.4.1 Test Scope Automotive Ethernet .......................................................................................... 8
1.4.2 Test Scope TCP/IP Protocol Family ....................................................................................... 8
1.4.3 Test Scope Automotive Protocols ......................................................................................... 8
2 Test Scope Layer 1 of Automotive Ethernet ......................................................................................... 9
2.1 Interoperability Tests .................................................................................................................... 9
2.1.1 General .................................................................................................................................. 9
2.1.2 Link-up time .......................................................................................................................... 9
2.1.3 Signal Quality ...................................................................................................................... 14
2.1.4 Cable Diagnose .................................................................................................................... 19
2.2 PMA ............................................................................................................................................. 23
2.2.1 General ................................................................................................................................ 23
2.2.2 Transmitter Electrical Specifications ................................................................................... 23
2.2.3 Receiver Electrical Specifications ........................................................................................ 33
3 Test Scope Layer 2 of Automotive Ethernet ....................................................................................... 35
3.1 Overview & Requirements for ECU Automotive Ethernet Switch Testing Test Scope ............... 35
3.2 VLAN Testing ............................................................................................................................... 35
3.3 QoS Testing ................................................................................................................................. 41
3.4 General Switch Testing ............................................................................................................... 52
3.5 Ingress Filtering ........................................................................................................................... 59
3.6 Diagnostics .................................................................................................................................. 62
4 Test Scope TCP/IP Protocol Family ..................................................................................................... 65
4.1 Address Resolution Protocol (ARP) ............................................................................................. 65
4.1.1 General ................................................................................................................................ 65
4.1.2 Parameters used in the tests .............................................................................................. 66
4.1.3 Terminology used in Test Procedure .................................................................................. 67
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 4
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 5
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 6
OPEN Alliance
1 Introduction
1.1 Overview
This ECU and Network Test Specification is designed to determine if a product conforms to specifications
defined in OPEN Specifications or related requirements. This specification is a collection of all test cases
which are recommend to be considered for automotive use and should be referred by car
manufacturers within their quality control processes.
Sucessful execution and passing all relevant tests gives a Device Under Test (DUT) a mimimum approval
that the device’s basic implementiations are done correctly.
This Test specification document is grouped in several chapters oriented on the scopes: “Automotive
Ethernet”, “TCP/IP Protocol Family” and “Automotive Protocols” which are described in chapter 1.3.
Tests are organized and identified with distinct IDs that relate to their scopes, and a unique
enumeration. For every scope introduction chapters explain common requirements on the Device under
Test, the Test Setup and parameters used by the following tests.
1.2 Feedback
Any feedback for correcting, improving or adding new content is welcome. We encourage to bring
forward this feedback in the regular meetings of the OPEN Alliance TC8. In case you are not an OPEN
Alliance member you can relay questions or feedback through the following contacts:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 7
OPEN Alliance
1.3 References
[1] C&S Group, BroadR-Reach Interoperability Test Suite - Interoperability Test Suite Specification v2.0,
OpenAlliance, 2014.
[2] OPEN Alliance BroadR-Reach® (OABR) Physical Layer Transceiver Specification For Automotive
Applications V3.2, June 24th, 2014.
[3] C. Donahue and D. Estes, BroadR-Reach Physical Media Attachment Test Suite v2.0, OpenAlliance,
2014.
[4] B. Körber, Definitions for Communication Channel, 2.0 ed., OPEN Alliance, 2014.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 8
OPEN Alliance
2.1.1 General
The following test specifications are adapted from [1] to fit the general requirements of an ECU.
3 test cycles:
Synopsis Shall ensure that the link is established within a given time without a high time
variation.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 9
OPEN Alliance
6. Calculate as follows:
𝑛
1
𝑡̅ = ∑ 𝑡𝑢𝑝 (𝑖)
𝑛
𝑖=1
𝑛
1
𝜎𝑡 = √ ∑(𝑡𝑢𝑝 (𝑖) − 𝑡̅)2
𝑛−1
𝑖=1
Pass criteria 𝜎𝑡 ≤ 50 ms
Notes This test has to be performed for each port of the ECU, if it has a switch inside.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 10
OPEN Alliance
Synopsis Shall ensure that the link is established within a given time without a high time
variation.
Test system
tstart Power
supply
tstop
Power
supply
DUT
(ECU) Golden Device
PHY mC
Low
Con Con CMC Pass Tx
Filter
Rx
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 11
OPEN Alliance
6. Calculate as follows:
𝑛
1
𝑡̅ = ∑ 𝑡𝑢𝑝 (𝑖)
𝑛
𝑖=1
𝑛
1
𝜎𝑡 = √ ∑(𝑡𝑢𝑝 (𝑖) − 𝑡̅)2
𝑛−1
𝑖=1
Pass criteria 𝜎𝑡 ≤ 50 ms
Notes This test has to be performed for each port of the ECU, if it has a switch inside.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 12
OPEN Alliance
Synopsis Shall ensure that the link is established within a given time without a high time
variation.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. Wake up message is necessary. The Test System provides special awake conditions
for the DUT such as a wakeup line or network management CAN messages.
4. The manufacturer has to provide the value Isleep.
5. The manufacturer has to provide the mean wake up time of the DUT: 𝑡𝑟𝑒𝑎𝑑𝑦2
Test setup The DUT must be connected to the golden device with opposite master/slave
configuration. The polarity of the communication channel must be correct. The power
supplies are controlled by the test system.
tstop
Power Power
supply supply
DUT
(ECU) Golden Device
PHY mC
Low
Con Con CMC Pass Tx
Filter
Rx
Test 1. DUT shall be in sleep mode and Golden Device shall be active and ready to build up
procedure link.
Repeat Step 2 to Step 5 n=100times:
7. Calculate as follows:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 13
OPEN Alliance
𝑛
1
𝑡̅ = ∑ 𝑡𝑢𝑝 (𝑖)
𝑛
𝑖=1
𝑛
1
𝜎𝑡 = √ ∑(𝑡𝑢𝑝 (𝑖) − 𝑡̅)2
𝑛−1
𝑖=1
Pass criteria 𝜎𝑡 ≤ 50 ms
Notes This test has to be performed for each port of the ECU, if it has a switch inside.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 14
OPEN Alliance
Synopsis Shall ensure that the ECU’s indicated signal quality decreases for a channel with
decreasing channel quality and that there is coherence between the SQI indicated
values on the ECU and the Golden device.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. The Test system allows varying and determining the quality of the communication
channel that connects the DUT and Golden Device.
4. DUT and Golden Device must be able to monitor the signal quality indicated by the
PHY. The DUT’s information of the signal quality can be provided by an applicative
Ethernet message, an UDS communication or another communication channel like
CAN.
Test setup
Power Test system
supply
Rend=¯ Rstart=¥
Golden Device
Rn PHY mC
Low
Con Con CMC Pass Tx
BR+
Filter
Rx
BR-
DUT
(ECU) QDUT QGD
Test 1. Remove any artificial channel degradation, to ensure that the highest possible
procedure signal quality is reached on both the DUT and Golden Device.
2. Read DUT’s parameter SQI and Link Status.
3. Read Golden Device parameter SQI and Link Status.
4. Read the resistor value
5. Save the acquired information.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 15
OPEN Alliance
… … … … … …
n … … … … Rend
Pass criteria Each test iteration shall be classified as passed, if all of the following condition(s) are
fulfilled.
Both devices show a decrement on the SQI value, allowing a maximal deviation of
n%, where n% is the minimal step of the device with less resolution involved in the
test set up.
DUT lost its link after indicating a SQI value of <= 40%
Link was not lost at a SQI value of > 40%
Notes This test has to be performed for each port of the ECU, if it has a switch inside.
Notice that the DUT and the Golden Device could present different SQI scales. This fact
should be included in the test report.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 16
OPEN Alliance
Synopsis Shall ensure that the ECU’s indicated signal quality increases for a channel with
increasing channel quality and that there is coherence between the SQI indicated
values on the ECU and the Golden device.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. The Test system allows varying and determining the quality of the communication
channel that connects the DUT and Golden Device.
4. DUT and Golden Device must be able to monitor the signal quality indicated by the
PHY. The DUT’s information of the signal quality can be provided by an applicative
Ethernet message, an UDS communication or another communication channel like
CAN.
Test setup
Power Test system
supply
Rend Rstart=¥
Golden Device
Rn PHY mC
Low
Con Con CMC Pass Tx
BR+
Filter
Rx
BR-
DUT
(ECU) QDUT QGD
Test 1. Start with the lowest possible quality of the communication channel with the
procedure identified resistor value Rend of the test 0.
2. Measurement of the signal quality of the DUT and Golden Device.
Degradation Step # SQI_DUT SQI_GD LinkStatus_DUT LinkStatus_GD R_channel
… … … … … …
n … … … … Rend
3. Decrease artificial channel degradation on channel with a maximal step of 5 Ω
4. Repeat steps 2 and 3 until the channel quality reach 100%.
Pass criteria Each test iteration shall be classified as passed, if all of the following condition(s) are
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 17
OPEN Alliance
fulfilled.
Both devices show an increment on the SQI value, allowing a maximal deviation of
n%, where n% is the minimal step of the device with less resolution involved in the
test set up.
Link was not lost at a SQI value of > 40%
Notes This test has to be performed for each port of the ECU, if it has a switch inside.
Notice that the DUT and the Golden Device could present different SQI scales. This fact
should be included in the test report.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 18
OPEN Alliance
Synopsis Shall ensure that the ECU’s cable diagnostic reliably detects a ground connection of one
or both of the bus lines.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. DUT must be able to detect any cable errors. This means the DUT have to trigger
the cable diagnostic features by itself and store it e.g. as DTC (Diagnostic Trouble
Code). The result of DUT’s cable diagnostic can be provided by an applicative
Ethernet message, an UDS communication or another communication channel like
CAN.
Test setup
Power Test system
supply
Golden Device
PHY mC
Low
BR+
Con Con CMC Pass Tx
BR- Filter
Rx
1 2
QC QC QC QC
GND GND QC
DUT 1 2 1 2
(ECU) t t t t
Test 1. All DTCs or any other detected errors of the cable diagnostics of the DUT have to be
procedure deleted.
2. After the wait time t the test system requests all identified cable errors QC by the
DUT.
3. The test system creates a cable error for a defined time terror.
4. After the wait time t the test system requests all identified cable errors QC by the
DUT.
5. Repeat step 1 to 4 for all error combinations (alternately BR+ and/or BR- connect to
GND).
Pass criteria Each test iteration shall be classified as passed, if the DUT reports all expected cable
errors.
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 19
OPEN Alliance
Synopsis Shall ensure that the ECU’s cable diagnostic reliably detects an open of one or both of
the bus lines. The test shall be performed for both a near end open at the connector of
the DUT, and for a far end open at the connector of the Golden Device.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. DUT must be able to detect any cable errors. This means the DUT have to trigger
the cable diagnostic features by itself and store it e.g. as DTC (Diagnostic Trouble
Code). The result of DUT’s cable diagnostic can be provided by an applicative
Ethernet message, an UDS communication or another communication channel like
CAN.
Test setup Near Open
Power Test system
supply
Test
1
system
Golden Device
PHY mC
Low
Con Con CMC Pass Tx
BR+
Filter
Rx
BR- 2
QC QC QC
DUT 1 2 QC
(ECU) t t t
Far Open
QC QC QC
DUT 1 2 QC
(ECU) t t t
Test The following steps shall be applied to test near and far end open cable diagnostics
procedure
1. All DTCs or any other detected errors of the cable diagnostics of the DUT have to be
deleted.
2. After the wait time t the test system requests all identified cable errors QC by the
DUT.
3. The test system creates a cable error for a defined time terror.
4. After the wait time t the test system requests all identified cable errors QC by the
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 20
OPEN Alliance
DUT.
5. Repeat step 1 to 4 for all error combinations (alternately BR+ and/or BR- are open).
Pass criteria Each test iteration shall be classified as passed, if the DUT reports all expected cable
errors.
Notes The results shall be reported for each BroadR-Reach port available in the ECU.
Synopsis Shall ensure that the DUT’s cable diagnostic reliably detects a short of the bus lines. The
test shall be performed for both a near end short at the connector of the DUT, and for a
far end short at the connector of the Golden Device.
Prerequisites 1. The DUT and the Golden Device are connected to a stable power supply.
2. The DUT must be operated in normal mode which means the DUT build up the link
and sends any Ethernet messages.
3. DUT must be able to detect any cable errors. This means the DUT have to trigger
the cable diagnostic features by itself and store it e.g. as DTC (Diagnostic Trouble
Code). The result of DUT’s cable diagnostic can be provided by an applicative
Ethernet message, an UDS communication or another communication channel like
CAN.
Test setup Near Short
Golden Device
Test system PHY mC
Low
BR+
Con Con CMC Pass Tx
BR- Filter
Rx
1
DUT QC QC QC
1
(ECU)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 21
OPEN Alliance
Far Short
Golden Device
PHY mC
Low
BR+
Con Con CMC Pass Tx
BR- Filter
Rx
1
DUT QC QC QC
1
(ECU)
Test The following steps shall be applied to test near and far end short cable diagnostics
procedure
1. All DTCs or any other detected errors of the cable diagnostics of the DUT have to be
deleted.
2. After the wait time t the test system requests all identified cable errors QC by the
DUT.
3. The test system creates a cable error for a defined time terror.
4. After the wait time t the test system requests all identified cable errors QC by the
DUT.
5. Repeat step 1 to 4 for all error combinations (alternately BR+ connected to BR- at
connector of DUT/Golden Device).
Pass criteria Each test iteration shall be classified as passed, if the DUT reports a short between the
bus lines.
Notes The results shall be reported for each BroadR-Reach port available in the ECU.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 22
OPEN Alliance
2.2 PMA
2.2.1 General
This chapter shall be used for evaluation of the Physical Layer of a 100BASE-T1 (OA BR) interface on ECU
level.
Except otherwise stated the measurements shall be conducted by room temperature (RT=23°C±5°C).
Referenced specification
The tests shall be carried out based on the definitions of the related test specifications [2], [3] and [4].
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 23
OPEN Alliance
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 24
OPEN Alliance
(based on [3])
Synopsis Shall ensure that the DUT has a stable clock.
Prerequisites For an ECU which is configured as slave in the Network, the ECU shall be switched to
MASTER-mode in this test.
Pass criteria The transmit clock shall be 66 2/3 MHz ±100 ppm for all temperatures.
Test This test shall be conducted at all corner temperatures of the ECU
iterations (e.g. -40°C/RT/105°C).
Notes As the Test is realized on three corner temperatures use test cable that not influence
the result .
The signal frequency generated from the Test Mode 2 is 33 1/3 MHz
According to this criteria the result could be measured on the clock delivered by the
PHY in test mode 2 and reported as in Mbits that is the double of the measured value.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 25
OPEN Alliance
(based on the Chapter 5.4.4 Transmitter Power Spectral Density (PSD)of [2])
Synopsis Shall ensure that the DUT respects Table 5.4 of [2]:Power Spectral Density Min & Max
Mask Definition. The PSD should be between the upper and the lower values specified
in the table.
Test 1. The DUT in Test Mode 5 and sends Test Pattern continually.
procedure 2. Use a test fixture terminated with 100 Ohm.
3. Spectrum Analyzer or Oscilloscope captures the transmitted test pattern.
4. Spectrum Analyzer or Oscilloscope computes the PSD.
5. Report the Value of the PSD as a Screenshot or a diagram/plot with a resolution
that shows that no MASK Violation has been detected.
Pass criteria Each test iteration shall be classified as passed, if the Value of the PSD is according to
chapter 5.4.4 Transmitter Power Spectral Density (PSD) of [2], table 5-4.
Test The averaging function of the scope shall be set at least to 50 time.
iterations
Notes In case of using a spectrum analyzer a balun with differential input must be used.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 26
OPEN Alliance
Measurement
reference plane Test fixture
Line
ECU impedance
50Ω
RF
OA BR connector
(SMA)
VBAT Terminal
GND power
supply
Connection ECU
GND pin to ground
ECU connector plane of test
fixture
cable side
To achieve a high degree of reliability of measurement results the use of a specific test
fixture for the connection to the ECU connector MDI pins is required. A test fixture
according to the test setup and in line with definitions of [4] shall be used. The ground
pin(s) of the ECU shall be direct connected to the ground plane of the test fixture. If
possible the original harness connector shall be used. It shall be a fixed part of the test
fixture. The calibration reference plane is defined at the beginning of the harness
cennector on the test fixture.
The test and measurement settings are defined by [4] chapter 4.1 to 4.3.
Test 1. The DUT is in test mode 4 and sends Test Pattern continually [see note].
procedure 2. Use a test fixture as described in the test setup.
3. Connect the MDI via the test fixtureto the Network Analyzer.
4. Measure the Value Return Loss (Sdd11)
5. Analyze the waveform.
6. Report the result with a resolution that shows: no limit Violation was detected.
Pass criteria Each test iteration shall be classified as passed, if the value of the MDI Return Loss is
according to chapter Chapter 7.1.3 Return Loss..
Test No
iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 27
OPEN Alliance
Notes Instead of the TestMode, the OA BR transceiver can be configured for active mode and
shall be set to mode “TX off” or “Scrambler off” (no output signal generated by
transceiver) if available.
MDI Return Loss shall be measured in the frequency range of 1 MHz to 200 MHz.
(based on [4])
Synopsis The tests shall be carried out based on the definitions of the related test specifications
[4].
Shall ensure that the DUT front end respects the appropriate symmetry requirements.
2.Use Link Partner or an interface to commute the DUT in Test Mode (via BroadR-Reach
or Standard Ethernet or CAN)
4. DUT shall be set to mode “TX off” or “Scrambler off” (no output signal generated by
transceiver). It is also possible to test with completely unpowered ECU. In this case it
shall be agreed by OEM.
RF
OA BR connector
(SMA)
VBAT Terminal
GND power
supply
Connection ECU
GND pin to ground
ECU connector plane of test
fixture
cable side
To achieve a high degree of reliability of measurement results the use of a specific test
fixture for the connection to the ECU connector MDI pins is required. A test fixture
according to Fehler! Verweisquelle konnte nicht gefunden werden. test setup and in
line with definitions of [4] shall be used. The ground pin(s) of the ECU shall be direct
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 28
OPEN Alliance
connected to the ground plane of the test fixture. If possible the original harness
connector shall be used. It shall be a fixed part of the test fixture. The calibration
reference plane is defined at the beginning of the harness connector on the test fixture.
Additionally the used test fixture shall fulfill the limit for fixture self-conversion
according to the diagram of the test setup while the test fixture is not connected to the
ECU (terminal left open).
The test and measurement settings are defined by [4] chapter 4.1 to 4.3.
0
[dB] f [MHz] TCL [dB]
Comment:
-10 1 - 70
ECU terminal of test jig is left open for evaluation! 20 - 70
200 - 50
-20
-30
-40
-50
-60
-70
-80
1 10 100 1000
[MHz]
Pass criteria For evaluation of MDI mode conversion measurements in the frequency range of 1 MHz
to 1 GHz are required. The following limit shall be fulfilled.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 29
OPEN Alliance
0
[dB] f [MHz] TCL [dB]
-10 1 - 60
22 - 60
100 - 47
-20 200 - 37
-30
-40
-50
-60
-70
-80
1 10 100 1000
[MHz]
Test No
iterations
Notes
(based on)
Synopsis Shall ensure that the DUT front end is not emitting common mode signal.
VBAT Terminal
GND power
supply
Connection ECU
GND pin to ground
plane of test
ECU connector fixture
cable side
To achieve a high degree of reliability of measurement results the use of a specific test
fixture for the connection to the ECU connector MDI pins is required. A test fixture
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 30
OPEN Alliance
according to the test setup and in line with definitions of [4] shall be used. The ground
pin(s) of the ECU shall be direct connected to the ground plane of the test fixture. If
possible the original harness connector shall be used. It shall be a fixed part of the test
fixture. The calibration reference plane is defined at the beginning of the harness
connector on the test fixture.
Additionally to these definitions the used test fixture shall fulfill the limit for fixture self-
conversion according to the diagram of test setup 0 while the test fixture is not
connected to the ECU (terminal left open). The 50 Ohm resistors on the test fixture shall
be realized by RF resistor types with an accuracy of in minimum 0.1%.
The ECU shall be in an active powered state. The OA BR transceiver is configured for test
mode 5 [2]. The RF connector of the test fixture shall be connected to a RF analyzer
according to [4]. The settings for the RF analyzer are given in the table as follows.
Detector Peak
The test and measurement settings are defined by [4] chapter 4.1 to 4.3.
Test 1. The DUT in Test Mode 5 and sends Test Pattern continually.
procedure 2. Use a test fixture as described in the test setup
3. Spectrum Analyzer, Measurement Receiver or Oscilloscope captures the
transmitted common mode emission spectrum
4. Report the value of the common mode emission with a resolution that shows that
no mask violation has been detected.
Pass criteria For evaluation of MDI mode conversion measurements in the frequency range of 1 MHz
to 200 MHz are required. The following limit shall be fulfilled. (Limit t.b.d.)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 31
OPEN Alliance
80
[dBµV] f [MHz] CME [dBµV]
70 1 24
70 24
60
50
40
30
20
10
0
-10
1 10 100
[MHz]
Test No
iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 32
OPEN Alliance
Synopsys Shall ensure that the DUT’s respect the Bit Error Rate Test specified. The BER should be
less than 10-10 at typical symbol transmission rate: 66+2/3 MHz
Test 1. Test Center sends to DUT Packets with size 64 bytes continually with 100% load.
procedure 2. Test Center analyzes the Packet Loss
3. Report the Values of the PER.
Repeat Steps 1 to 3 with Packet size 1518 bytes.
Pass criteria Each test shall be classified as passed, if the Value of the BER is lower than 10-10
Test No
iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 33
OPEN Alliance
Test 1. Set symbol transmission rate at test Center to minimum: 66+2/3 MHz - 100ppm
procedure 2. Test Center sends to DUT Packets with size 64 bytes continually with 100% load.
3. Test Center analyzes the Packet Loss
4. Report the Values of the PER.
5. Repeat Steps 2 to 4 with Packet size 1518 bytes.
6. Set symbol transmission rate at test Center to maximum: 66+2/3 MHz + 100ppm
7. Test Center sends to DUT Packets with size 64 bytes continually with 100% load.
8. Test Center analyzes the Packet Loss
9. Report the Values of the PER.
10. Repeat Steps 7 to 9 with Packet size 1518 bytes.
Pass criteria Each test shall be classified as passed, if the Value of the BER is lower than 10-10
Test No
iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 34
OPEN Alliance
3.1 Overview & Requirements for ECU Automotive Ethernet Switch Testing
Test Scope
The tests in this scope validate the behavior of the “Automotive Ethernet Switch“ within the ECU. The
“Automotive Ethernet Switch“ is an entity that includes the switch silicon hardware and any additional
hardware, firmware, and software needed to meets the requirements for a “MAC bridge“ set forth in
the IEEE 802.1 standards.
Any reference to “DUT“ in this test scope refers to the logical “Automotive Ethernet Switch“ including
any software or configuration done in an MCU or CPU. The “test device“ shall include both externally
connected hardware/software as well as software running on any MCU / CPU on the ECU that is
connected to the “Automotive Ethernet Switch“ via an Automotive Ethernet Port.
The tests in this test scope are designed to test that the “Automotive Ethernet Switch“ entity is
configured & operating correctly as per the ECU configuration, but assume that the functionality of the
switch silicon, PHYs, or other components has been verified elsewhere.
The test cases are grouped by functional areas. Only those functional areas and test cases that are
applicable to a given ECU need to be tested. The configuration of each ECU (including the switch
configuration) should be used to determine which test cases are applicable.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 35
OPEN Alliance
Synopsys The test shall ensure that the switch is able to forward the traffic for unidentified MACs
in presence of line rate traffic, and drop the traffic received from un-configured VLANs.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and ready
to receive/forward Ethernet frames.
The DUT shall be capable of responding to Echo-Request message with Echo-Reply
message on some or all of its ports.
Test setup All available (external) ports of the DUT are connected to the test system.
Test Input 1. Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
2. Valid VLANs are read from the ECU Configuration File, if available.
Test 1. Create the test topology as shown in the Setup.
Procedure 2. On each test port, iterate through each VLAN, source MAC, and destination MAC,
and transmit Echo Request packets for each combination.
3. Verify that for each valid combination of destination MAC and VLAN, an Echo Reply
is received on the test device port that sent the Echo-Request packet.
4. Verify that for each invalid VLAN or each invalid MAC/VLAN combination, the Echo-
Request packet is dropped on the receiving ECU Switch Port.
5. Verify that for each combination of invalid destination MAC and valid VLAN, the
Echo-Request is forwarded to each test device port belonging to that VLAN except
the source port of Echo-Request.
Pass criteria The DUT traffic counters match the expected test device traffic counters for each
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 36
OPEN Alliance
Test The test shall be repeated for each combination of ingress and egress ports for all the
iterations combinations of:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 37
OPEN Alliance
Synopsys The test shall ensure that the switch is able to successfully forward the broadcast traffic
from all configured VLANs in presence of line rate traffic, and drop the traffic received
from un-configured VLANs.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and ready
to receive/forward Ethernet frames.
The DUT shall be capable of handling ARP request on some or all of its ports.
Test setup All available (external) ports of the DUT are connected to the test system.
Test Input Source MAC Addresses are configured in either of these ways:
Parameters read from the ECU Configuration file, if configured/available
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 38
OPEN Alliance
Procedure 2. On each test port, iterate through each VLAN, source MAC, source IP and
destination IP, and transmit ARP Request packets for each combination.
3. Verify that for each valid combination of destination IP and VLAN, an ARP Reply is
received on the test device port that sent the ARP Request packet.
4. Verify that for each invalid VLAN, the ARP Request packet is dropped on the
receiving ECU Switch Port.
5. Verify that for each combination of invalid destination IP and valid VLAN, the ARP
Request is forwarded to each test device port belonging to that VLAN except the
source port of ARP Request.
Pass criteria The DUT traffic counters match the expected test device traffic counters for each
combination of VLAN, Source MAC, Source IP and Destination IP.
Test The test shall be repeated for each combination of ingress and egress ports for all the
iterations combinations of:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 39
OPEN Alliance
Synopsys The test shall ensure that the switch is able to forward multicast packets based on the
DUT configuration.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and ready
to receive/forward Ethernet frames.
The DUT shall be capable of forwarding multicast message on all the ports
belonging to a specific VLAN.
Test setup All available (external) ports of the DUT are connected to the test system.
Test Input Source MAC Addresses are configured in either of these ways:
Parameters o read from the ECU Configuration file, if configured/available
o MAC Addresses identified for testing purpose
Source IP Addresses are configured in either of these ways:
o read from the ECU Configuration file, if configured/available
o IP Addresses identified for testing purpose
Destination Multicast IP Addresses
o read from the ECU Configuration file, if configured/available
o Multicast IP Addresses identified for testing purpose
Destination MAC Address is the multicast MAC derived from the multicast
Destination IP
4094 VLANs (excluding reserved VLAN IDs 0 and 4095) per port and VLAN
untagged
Frame size – varies with each test cycle
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 40
OPEN Alliance
Test Repeat steps 4 through 7 for each frame size and bandwidth that needs to be
iterations tested.
Notes Test derived from switch requirement VLAN01 and VLAN02: The switch shall support
VLAN handling according to IEEE 802.1Q. The switch shall support at least x different
VLAN-IDs which can be chosen freely from the entire range of all available 4095 VLAN-
IDs.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 41
OPEN Alliance
Synopsys The test shall ensure that the switch is able to forward VLAN Priority tagged packets and
meet the latency and jitter limits.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and
ready to receive/forward Ethernet frames.
The DUT shall be capable of forwarding VLAN and Priority tagged messages on
all the ports.
Each test device port shall be able to generate and monitor VLAN and Priority
tagged traffic streams for the entire valid range of VLAN (0-4094) and Priority
(0-7).
Note: VLAN 0 is a special case. The packet is tagged with VLAN ID 0 so that the
packet can be priority tagged. Usually the switch receiving these packets will
strip the VLAN header and forward the packets based on VLAN priority.
The test device shall make these statistics available for each valid/allowed
combination of VLAN and VLAN Priority:
o Frames/Bytes transmit/receive rate and traffic loss
o Min/Max/Avg latency and jitter of the frames
Test setup All available (external) ports of the DUT are connected to the test system. The topology
shown here is using three ports, but the test can be run with two ports or more than
three ports as well.
Test Input Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 42
OPEN Alliance
Valid VLANs and VLAN Priorities are read from the ECU Configuration File, if
available.
Test 1. Create the test topology as shown in the Setup.
Procedure 2. On each test device port (source port), iterate through each valid/allowed
source MAC, VLAN and VLAN Priority combination. For each such combination,
send traffic towards each valid/allowed destination MAC on other test device
ports (destination ports) that are connected to the ECU external ports.
3. Send, Capture and monitor the traffic on all the test device ports participating in
the test.
Pass criteria 1. Verify that for each valid combination of VLAN and VLAN Priority "Packets
Received = Packets Expected“ and there is no traffic loss for all the
valid/allowed VLANs and VLAN Priorities.
2. Verify that for each VLAN Priority the packets are received within the expected
latency and jitter defined for that priority i.e. high priority traffic incurs less
latency and jitter compared to low priority traffic.
Test Repeat steps 1 through 3 for different frame sizes and bandwidth including line
iterations rate to validate operation under different expected conditions.
Notes Test derived from switch requirement QOS-01 and QOS-02: The switch shall support
priority based quality of service according to IEEE 802.1Q. The switch shall support at
least x different level of priority.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 43
OPEN Alliance
Synopsys The test shall ensure that the switch is able to forward VLAN and Priority tagged packets
using strict priority algorithm.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and
ready to receive/forward Ethernet frames.
The DUT shall be capable of forwarding VLAN and Priority tagged message on all
the ports using Strict Priority Algorithm.
The test device shall consist of two traffic generator ports and one traffic
monitor port.
The traffic generator port shall be capable of generating VLAN and Priority
tagged traffic streams for the entire valid range of VLAN (0-4094) and Priority
(0-7).
Note: VLAN 0 is a special case. The packet is tagged with VLAN ID 0 so that the
packet can be priority tagged. Usually the switch receiving these packets will
strip the VLAN header and forward the packets based on VLAN priority.
The test device shall make these statistics available for each valid/allowed
combination of VLAN and VLAN Priority:
o Frames/Bytes transmit/receive rate and traffic loss
Test setup All available (external) ports of the DUT are connected to the test system. The topology
shown here is using three ports, but the test can be run with two ports or more than
three ports as well.
Test Input Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 44
OPEN Alliance
Valid VLANs and VLAN Priorities are read from the ECU Configuration File, if
available.
Test 1. Create the test topology as shown in the Setup.
Procedure 2. Iterate through all the valid VLAN IDs and configure test device Port P1 to send
100% of the line rate traffic towards test device Port P3. The VLAN priority shall
not be the lowest allowed/configured VLAN Priority for the VLAN ID chosen.
Note: The VLAN Priority may not follow numerical order in terms of priority on
many switches. For example, VLAN Priority 2 and 3 are higher in priority
compared to other VLAN Priorities on AVB enabled switches.
3. Iterate through all the valid VLAN IDs and configure test device Port P2 to send
100% of the line rate traffic towards test device Port P3. The VLAN priority shall
be lesser than the VLAN Priority configured on Port 1 for the corresponding
VLAN ID.
4. Send traffic from test device traffic generator ports (P1 and P2) at the same
time.
5. Capture and monitor the traffic on test device traffic receiver port (P3).
6. Repeat the steps above for all the allowed/valid VLAN IDs and VLAN Priorities
such that the VLAN priority configured in step#2 is always greater than the
VLAN priority configured in step#3.
Pass criteria 1. Verify that only the traffic sent from test device Port P1 is received on test
device Port P3 i.e. only the higher priority traffic is received and the traffic sent–
from test device Port P2 is not received on test device Port P3.
2. Verify that there is no loss for the traffic sent from test device Port P1 i.e. high
priority traffic does not incur any loss.
Test Repeat for each external DUT port that supports Strict Priority Algorithm.
iterations
Notes Test derived from switch requirement QOS-04: The switch shall support strict
priority scheduling for each egress port.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 45
OPEN Alliance
Synopsys The test shall ensure that the switch is able to forward VLAN and Priority tagged packets
using Weighted Round Robin algorithm.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and
ready to receive/forward Ethernet frames.
The DUT shall be capable of forwarding VLAN and Priority tagged message on all
the ports using Weighted Round Robin Algorithm.
The test device consists of two traffic generator ports and one traffic monitor
port.
The traffic generator port shall be capable of generating VLAN and Priority
tagged traffic streams for the entire valid range of VLAN (1-4094) and Priority
(0-7).
The test device shall make these statistics available for each valid/allowed
combination of VLAN and VLAN Priority:
o Frames/Bytes transmit/receive rate and traffic loss
Test setup All available (external) ports of the DUT are connected to the test system. The topology
shown here is using three ports, but the test can be run with two ports or more than
three ports as well.
Test Input Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
Valid VLANs and VLAN Priorities are read from the ECU Configuration File, if
available.
Test 1. Create the test topology as shown in the Setup.
2. Configure Sender Port P1 to send 33% of the line rate traffic towards Receiver
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 46
OPEN Alliance
Procedure Port P3. The traffic priority can be any allowed/configured VLAN Priority on the
DUT.
3. Configure Sender Port P2 to send 66% of the line rate traffic towards Receiver
Port P3. The traffic priority can be any allowed/configured VLAN Priority on the
DUT and shall be greater than the priority configured in step#2.
4. Send traffic from sender ports at the same time.
5. Capture and monitor the traffic on the receiver port.
6. Repeat steps 2 through 5 for all valid/allowed VLAN IDs (VLAN ID >= 1 and VLAN
ID <= 4094).
Pass criteria 1. Verify that the traffic sent from test device Port P1 and the traffic sent from test
device port P2 is received on test device Port P3 in the proportion governed by
the ratios of the weights assigned to the priority i.e. if priority 2 is assigned
weight 2 and priority 3 is assigned weight 4, then the
TrafficWithPriorityP3/TrafficWithPriorityP2 =
WeightForPriority3/WeightForPriority2 = 4/2.
2. Verify that there is no loss of traffic for the valid/allowed VLAN priorities.
Test Repeat for each external ECU port that supports Weighted Round Robin
iterations Algorithm.
Notes Test derived from switch requirement QOS-05: The switch shall support at least one
variant of Weighted Round Robin or Weighted Fair Queuing scheduling for each egress
port.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 47
OPEN Alliance
Synopsys The test shall ensure that the switch is able to overwrite the VLAN Priority with a
different VLAN Priority. If the packet is not VLAN-tagged, an 802.1Q VLAN Header with
default VLAN-ID and VLAN Priority will be added to the Ethernet Header.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and
ready to receive/forward Ethernet frames.
The DUT shall be capable of forwarding VLAN and Priority tagged message on all
the ports.
The test device consisting of at least one traffic generator port and at least one
traffic monitor port.
The traffic generator port shall be capable of generating VLAN and Priority
tagged traffic streams for the entire valid range of VLAN (1-4094) and Priority
(0-7).
The test device shall make these statistics available for each valid/allowed
combination of VLAN and VLAN Priority:
o Frames/Bytes transmit/receive rate and traffic loss
The traffic monitor shall be able to compare the received VLAN Priority with the
transmitted VLAN Priority.
Test setup All available (external) ports of the DUT are connected to the test system.
Test Input Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
Valid VLANs and VLAN Priorities are read from the ECU Configuration File, if
available.
Test 1. Create the test topology as shown in the setup.
Procedure 2. Configure test device port P1 to send multiple traffic streams for all the VLAN
priorities that are valid/allowed on the switch.
3. Configure test device port P2 to receive the traffic on another port.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 48
OPEN Alliance
Test Repeat the procedure for each external DUT Port that is enabled for Priority
iterations Overwrite.
Notes Test derived from switch requirement QOS-07 and QOS-09: It shall be possible to
change/overwrite the priority based on the incoming priority at the ingress port. This
includes untagged frames (=Default priority).)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 49
OPEN Alliance
Synopsys The test shall ensure that the switch is able to overwrite the VLAN Priority with a
different VLAN Priority based on the ingress port. If the packet is not VLAN-tagged, an
802.1Q VLAN Header with default VLAN-ID and VLAN Priority will be added to the
Ethernet Header.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and
ready to receive/forward Ethernet frames.
The DUT shall be capable of forwarding VLAN and Priority tagged message on all
the ports.
The test device shall consist of two traffic generator ports and one traffic
monitor port.
The traffic generator port shall be capable of generating VLAN and Priority
tagged traffic streams for the entire valid range of VLAN (1-4094) and Priority
(0-7).
The test device shall make these statistics available for each valid/allowed
combination of VLAN and VLAN Priority:
o Frames/Bytes transmit/receive rate and traffic loss
The traffic monitor shall be able to compare the received VLAN Priority with the
transmitted VLAN Priority.
Test setup All available (external) ports of the DUT are connected to the test system. The topology
shown here is using three ports, but the test can be run with more than three ports as
well.
Test Input Switch port Valid Source/Destination MAC Addresses are configured in either of
Parameters these ways:
a. read from the ECU Configuration file, if configured/available
b. MAC Addresses identified for testing purpose
Valid VLANs and VLAN Priorities are read from the ECU Configuration File, if
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 50
OPEN Alliance
available.
Test 1. Create the test topology as shown in the setup.
Procedure 2. For each test device sender port, iterate through all the VLAN priorities that are
valid/allowed on the switch, and configure at least one traffic stream for each
combination.
3. Send traffic from the test device sender ports.
4. Capture and monitor traffic on the receiver port and verify that the traffic
priority is remapped as per the priority re-mapping table.
5. Repeat above steps for all valid/allowed VLAN IDs (VLAN ID >= 1 and VLAN ID <=
4094).
Pass criteria 1. Verify that for each VLAN Priority Remapping "Packets Received = Packets
Expected“.
2. Verify that for each VLAN Priority the received packets are valid.
3. Verify that other fields in Ethernet and VLAN Headers are not modified.
Test Repeat the procedure for each external DUT Port that is enabled for Priority
iterations Overwrite.
Notes Test derived from switch requirement QOS-08: It shall be possible to change/overwrite
the priority based on the ingress port. This includes untagged frames (=Default priority).
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 51
OPEN Alliance
(Test derived from switch requirement GEN01: The switch shall use a non-blocking architecture.)
Synopsys The test shall ensure that the switch uses a non-blocking architecture, i.e. the switch is
capable of processing and forwarding all incoming data under full communication load
(i.e. full-duplex communication on all ports simultaneously).
Prerequisite The DUT shall be operated in normal mode, i.e. the switch is configured and ready to
s receive/forward Ethernet frames.
Test setup All available (external) ports of the DUT are connected to the test system.
Pass criteria Verify that all frames transmitted by the test system are forwarded correctly and that no
frame is dropped by the switch during the runtime of test.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 52
OPEN Alliance
Test The test shall be repeated for each combination of ingress and egress ports.
iterations
𝑛𝑢𝑚𝐹𝑟𝑎𝑚𝑒𝑠𝑚𝑎𝑥𝑃𝑎𝑦𝑙𝑜𝑎𝑑 = 8127
(Derived from requirement: GEN 02: The switch shall operate as store and forward switch.)
Synopsys The test shall ensure that the switch operates as a store and forward switch, i.e. the
switch shall store an incoming frame and wait until its complete reception and
syntactical verification (CRC check) before forwarding the frame.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and ready to
receive/forward Ethernet frames.
Test setup All available (external) ports of the DUT are connected to the test system.
The test system transmits a frame with a combination of the following characteristics:
Frame has
Valid CRC
Invalid CRC (last CRC bit flipped)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 53
OPEN Alliance
The 6 characteristics result in 8 combinations that are tested in separate test instances:
Pass criteria Test instances (1) – (4): Verify that tDelay has a positive value, i.e. the transmission of the
forwarded frame does not begin before the incoming frame was completely received by
the switch. Verify that all frames are forwarded correctly and that no frame is dropped
by the switch.
Test instances (3) – (4): Verify that the frame forwarded or dropped according to the
switch configuration regarding the handling of frames with unknown destination MAC
addresses.
Test instances (5) – (8): Verify that a frame with invalid CRC is dropped by the switch
and that no part of the frame is forwarded to any port.
Test The test shall be repeated for each combination of ingress and egress switch ports.
iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 54
OPEN Alliance
(Derived from requirement: GEN 08: The switch may support jumbo frames. If supported it should be
possible to turn this off.)
Synopsys The test shall ensure that the switch forwards jumbo frames (i.e. frames with a payload
larger than 1500 byte) correctly if jumbo frames are supported and the feature is
enabled. If jumbo frames are not supported or the feature is disabled the switch shall
drop jumbo frames.
Prerequisites The DUT shall be operated in normal mode, i.e. the switch is configured and ready to
receive/forward Ethernet frames.
Only one of the test instances (a) or (b) is executed, depending on the capabilities and
the configuration of the switch.
(a) The switch supports jumbo frames and the feature is enabled
(b) The switch does not support frames or the feature is disabled
For test instance (a) the manufacturer has to provide the maximum supported frame
size maxSupportedFrameSize.
Test setup All available (external) ports of the DUT are connected to the test system.
Test The test system transmits multiple consecutive frames with alternating payload length
procedure in pairs of one frame with a maximum regular payload length of 1500 byte (according to
IEEE 802.3) and one jumbo frame with increasing payload length.
The first jumbo frame is transmitted with a payload length of 1501 byte.
The n-th jumbo frame is transmitted with a payload length of 1500 + n byte.
The last jumbo frame is transmitted with a payload length of 65535 byte.
Pass criteria Verify that all frames with a payload length smaller or equal to
maxSupportedPayloadSize are forwarded correctly by the switch.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 55
OPEN Alliance
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 56
OPEN Alliance
(Derived from requirement: GEN 10: The switch shall support Mirroring for each port. This includes
mirroring frames from multiple ports to multiple ports.)
Synopsys The test shall ensure the capability of the switch to mirror all frames received or
transmitted at one or more selected switch ports to one or more particular switch
ports configured as mirroring ports.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. At least one pair of ports is configured for port mirroring.
Test setup All available (external) switch ports of the DUT are connected to the test system.
Test Let M be the set of switch port pairs Pi = (PortSi, PortMi), which are configured to
procedure mirror all incoming and outgoing frames on the source port PortSi to the mirror port
PortMi.
Let N be the set of non-mirrored switch ports, i.e. ports that are not configured as
source port within M, including all ports not included in M at all.
The test system continuously transmits unicast and broadcast frames with minimum
(42 bytes) and maximum regular (1500 bytes) payload length on all connected ports
of the DUT.
The test shall run until at least 100 frames were mirrored for each pair of ports in M.
Pass criteria Verify that all frames on all ports are forwarded correctly according to VLAN-ID and
MAC address.
Verify for all port pairs Pi in M that all incoming and outgoing frames of the source
port PortSi are additionally mirrored to and transmitted on the corresponding mirror
port PortMi.
Notes The number and ratio of broadcast frames shall be below the broadcast storm
protection threshold, if broadcast storm protection is enabled.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 57
OPEN Alliance
(Derived from requirement: GEN 11: The switch shall support disabling/enabling each single port on
MAC Layer without affecting the link state of the physical layer.)
Synopsys The test shall ensure the capability of the switch to enable and disable single switch
ports on MAC layer without affecting the link state of the physical layer.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. At least one switch port is configured to be disabled.
Test setup All available (external) switch ports of the DUT are connected to the test system.
The test system continuously transmits unicast and broadcast frames with minimum
(42 bytes) and maximum regular (1500 bytes) payload length on all connected ports
of the DUT.
The test shall run until at least 100 frames were dropped at each disabled port.
Pass criteria Verify that all frames received on disabled ports (Pdisabled) are not forwarded to any
other port.
Notes The number and ratio of broadcast frames shall be below the broadcast storm
protection threshold, if broadcast storm protection is enabled.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 58
OPEN Alliance
(Derived from requirement: FILT02: The switch shall support a configurable bandwith limitation
(policing) for each ingress port based on priority or based on VLAN-ID.)
Synopsys The test shall ensure the capability of the switch to limit the bandwidth for ingress ports
individually based on priority or based on VLAN-ID.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. The ingress filtering of the DUT is configured to limit the bandwidth depending on
priority or VLAN-ID.
Test setup All available (external) switch ports of the DUT are connected to the test system.
On port B the test system transmits frames with combinations of the following
characteristics:
The test system shall begin with frame category (1) and transmit at least 100 frames of
the same category before switching to the next frame category.
Pass criteria Verify that all frames with higher priority are forwarded correctly and that frames with
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 59
OPEN Alliance
Test The test shall be repeated for all pairs of (external) switch ports (port A and port B) of
iterations the DUT.
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 60
OPEN Alliance
(Derived from requirement: FILT04: The switch shall allow configuring that all incoming frames of a
switch port are forwarded to configured switch port (e.g. host controller).)
Synopsys The test shall ensure the capability of the switch to forward all incoming frames of a
selected switch port to another switch port.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. The ingress filtering of the DUT is configured to forward all frames of a particular
port to another port.
Test setup All available (external) switch ports of the DUT are connected to the test system.
Test Let F be the set of port pairs Pi = (PortSi, PortTi), which are configured to forward all
procedure incoming frames on the source port PortSi to the target port PortTi.
Let N be the set of non-forwarded ports, i.e. ports that are not configured as source
port within F, including all ports not included in F at all.
The test system continuously transmits unicast and broadcast frames with minimum (42
bytes) and maximum regular (1500 bytes) payload length on all connected ports of the
DUT.
The test shall run until at least 100 frames were forwarded between each pair of ports
in F.
Pass criteria Verify that for each port pair Pi all frames received on the source port PortSi are
forwarded exclusively to target port PortTi.
Verify that all frames received on a port of set N are forwarded according to VLAN-ID
and MAC address independently from the forwarding configuration in F.
Test
iterations
Notes The number and ratio of broadcast frames shall be below the broadcast storm
protection threshold, if broadcast storm protection is enabled.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 61
OPEN Alliance
3.6 Diagnostics
(Derived from requirement: DIAG01: The switch shall provide at least the following counter individually
for each port: number of received frames, number of received bytes, number of dropped frames after
reception, number of sent frames, number of unsuccessful sent frames, number of sent bytes, maximum
fill level of the queues since clearing the counter)
Synopsys The test shall ensure the capability of the switch to provide diagnostic status
information (counters) regarding processed frames.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. The maximum supported data size maxFrameDataSize for Ethernet frames has to
be provided by the DUT manufacturer. If jumbo frames are not supported, then
maxFrameDataSize = 1500.
3. The frame counters of all switch ports are cleared.
Test setup All available (external) switch ports of the DUT are connected to the test system.
Test The test system transmits valid and invalid Ethernet frames with different
procedure characteristics to stimulate the incrementation of the diagnostic frame counters:
Pass criteria Verify that all diagnostic frame counters correctly display the number of processed
frames and bytes.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 62
OPEN Alliance
(Derived from requirement: DIAG02: The switch shall provide at least the following counter or status
information individually for each port with integrated PHYs: current signal quality indicator, worst signal
quality indicator since clearing this value, number of CRC errors on reception, number of connection
losses (change of the link state))
Synopsys The test shall ensure the capability of the switch with integrated PHYs to provide
diagnostic quality indicators and counters individually for each port.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. The diagnostic indicators and counters of all switch ports are cleared.
Test setup The same test setup as for the signal quality tests (3.1.3) shall be used in order to
modify the signal quality of a switch port.
Test The test system transmits tagged unicast frames with minimum (42 byte) payload
procedure length, with valid and invalid CRCs and varying signal quality to stimulate the
incrementation of the diagnostic counters and the signal quality indicators:
Beginning with a signal quality of 100% (i.e. channel degradation = 0%) the test system
increases the channel degradation on the tested port by 1% every second, up to a
channel degradations of 70%.
After the signal quality has reached 30% the test system decreases the channel
degradation by 1% every second, until the signal quality reaches 100%.
Pass criteria Verify that all the diagnostic signal quality indicators display the correct signal quality
values and that the diagnostic counters display the correct numbers of CRC errors and
connection losses.
Test The test shall be repeated for all (external) ports of the switch with integrated PHYs.
iterations
Notes It is sufficient to decrease the signal quality below 40% in order to prevent a stable link
connection (cf. Signal Quality test cases, chapter 3.1.3)
NOTE: The connection loss counter should be tested explicitly by changing link state.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 63
OPEN Alliance
(Derived from requirement: DIAG04: The switch shall support cable diagnostics for each port with
integrated PHYs. This includes the following electrical error: broken cable of at least one wire, electrical
short between at least 2 signal cables)
Synopsys The test shall ensure the capability of the switch with integrated PHYs to provide cable
diagnostics information.
Prerequisites 1. The DUT is configured and ready to send and receive Ethernet frames.
2. The cable diagnostics information of all ports are cleared.
Test setup The same test setup as for the cable diagnostics tests (3.1.4) shall be used in order to
simulate faults on the physical layer.
(1) The test system simulates a broken cable with one wire (BR+).
(2) The test system simulates a broken cable with one wire (BR-).
(3) The test system simulates a broken cable with both wires.
(4) The test system simulates a short between the both wires.
Pass criteria Verify that broken wires and shorts between signal lines are detected and that the
diagnostics information is displayed correctly by the DUT.
Test The test shall be repeated for all (external) ports of the switch.
iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 64
OPEN Alliance
4.1.1 General
Referenced specification
The scope of this chapter is to specify test cases for Address Resolution Protocol from the following
standards:
RFC826
Simulated topologies
<TIface-0> <DIface-0>
ECU
Tester configuration required for the tests in the following sections pertaining to ARP tests:
Correct DUT MAC Address for DUT interface connected to TESTER interface
All test cases that use IP interface need to do ARP Packet exchange. This ARP packet exchange is
performed after the DUT interface is configured with IP Address. Using this packet exchange
TESTER automatically learns the MAC address of DUT. The learned MAC address is then used in
the test cases to send packets to DUT.
All the test cases in this suite require DUT to be configured with only one IP interface
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 65
OPEN Alliance
Coverage
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 66
OPEN Alliance
The second unused MAC address that the TESTER can use
for emulating specific topologies needed in test. This is
<MAC-ADDR2> auto generated as consecutive to <MAC-ADDR1>
The third unused MAC address that the TESTER can use for
emulating specific topologies needed in test. This is auto
<MAC-ADDR3> generated as consecutive to <MAC-ADDR2>
<DIFACE_O_MAC_ADDR> This is the MAC address of <DIface-0> of DUT
This indicates an arbitrary MAC address. This value is equal
<ARBIT_MAC_ADDR> to 12:34:56:78:90:00
This indicates an unknown/wrong value of hardware type
<ARP_HARDWARE_TYPE_UNKNOWN> Resolution Packet
This indicates an unknown/wrong length of hardware
<UNKNOWN_HW_ADDR_LEN> address
<ARP_PROTOCOL_UNKNOWN> This indicates an unknown/wrong value of protocol type
This indicates an unknown/wrong length of protocol
<UNKNOWN_PROTCOL_ADDR_LEN> address
This value depicts the time variance associated to any
<ARP-TOLERANCE-TIME> wait-event
The length in bytes of the Ethernet MAC Address, has the
<ETHERNET_ADDR_LEN> value 6
Name Description
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 67
OPEN Alliance
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
Synopsys the caller (hardware driver) which then transmits the packet. (Note: Here DUT is configured
to add a static entry <HOST-1-IP, MAC-ADDR1> in its ARP cache. TESTER then causes DUT to
send an ICMP Echo Request and expects that DUT will NOT send any ARP Request.)
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to add a static entry in its ARP Cache with
- IP Address of <HOST-1-IP>
- Ethernet Source Address of <MAC-ADDR1>
Test 3. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
Procedure <DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
4. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
5. DUT: Does not send ARP Request
6. CLEANUP: Configure DUT to delete static entry in its ARP Cache with
- IP Address of <HOST-1-IP>
- Ethernet Source Address of <MAC-ADDR1>
Pass Criteria 5. DUT: Does not send ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 68
OPEN Alliance
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
Synopsys the caller (hardware driver) which then transmits the packet. (Note: Here DUT is configured
to add a static entry <HOST-1-IP, MAC-ADDR1> in its ARP cache. TESTER then causes DUT to
send an ICMP Echo Request and expects that DUT will send an ICMP Echo Request.)
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to add a static entry in its ARP Cache with
- IP Address of <HOST-1-IP>
- Ethernet Source Address of <MAC-ADDR1>
3. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
Test <DIface-0> with
Procedure - Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
4. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
5. DUT: Sends ICMP Echo Request
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
6. CLEANUP: Configure DUT to delete static entry in its ARP Cache with
- IP Address of <HOST-1-IP>
- Ethernet Source Address of <MAC-ADDR1>
5. DUT: Sends ICMP Echo Request
Pass Criteria - Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 69
OPEN Alliance
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
the caller (hardware driver) which then transmits the packet.
Synopsys (Note: The objective of the test case is to validate the ARP Learning mechanism on ARP
requests. .Here TESTER sends an ARP Request to DUT so that an entry <HOST-1-IP, MAC-
ADDR1> gets added in DUT's ARP cache. TESTER then causes DUT to send an ICMP Echo
Request and expects that DUT will NOT send any ARP Request.)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Source IP Address set to <HOST-1-IP>
- Destination IP Address set to <DIface-0-IP>
Test Procedure - Ethernet Source Address set to <MAC-ADDR1>
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
6. DUT: Does not send ARP Request
Pass Criteria 6. DUT: Does not send ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 70
OPEN Alliance
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
the caller (hardware driver) which then transmits the packet. (Note: Here TESTER sends an
Synopsys
ARP Request to DUT so that an entry <HOST-1-IP, MAC-ADDR1> gets added in DUT's ARP
cache. TESTER then causes DUT to send an ICMP Echo Request and expects that DUT will
send an ICMP Echo Request.)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Source IP Address set to <HOST-1-IP>
- Destination IP Address set to <DIface-0-IP>
- Ethernet Source Address set to <MAC-ADDR1>
Test
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
Procedure arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
6. DUT: Sends ICMP Echo Request
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
6. DUT: Sends ICMP Echo Request
Pass Criteria - Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 71
OPEN Alliance
ARP_05: ARP entry learned on gratuitous ARP response (no ARP request)
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
the caller (hardware driver) which then transmits the packet. (Note: Here TESTER sends an
Synopsys
ARP Response to DUT so that an entry <HOST-1-IP, MAC-ADDR1> gets added in DUT's ARP
cache. TESTER then causes DUT to send an ICMP Echo Request and expects that DUT will
NOT send any ARP Request.)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Source IP Address set to <HOST-1-IP>
- Destination IP Address set to <DIface-0-IP>
Test - Ethernet Source Address set to <MAC-ADDR1>
Procedure - Ethernet Destination Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
ARP cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
6. DUT: Does not send ARP Request
Pass Criteria 6. DUT: Does not send ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 72
OPEN Alliance
ARP_06: ARP entry learned on gratuitous ARP response (ARP entry used)
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it finds the pair, it gives the corresponding 48.bit Ethernet address back to
the caller (hardware driver) which then transmits the packet. (Note: Here TESTER sends an
Synopsys
ARP Response to DUT so that an entry <HOST-1-IP, MAC-ADDR1> gets added in DUT's arp
cache. TESTER then causes DUT to send an ICMP Echo Request and expects that DUT will
send an ICMP Echo Request.)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Source IP Address set to <HOST-1-IP>
- Destination IP Address set to <DIface-0-IP>
- Ethernet Source Address set to <MAC-ADDR1>
Test
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
Procedure arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
6. DUT: Sends ICMP Echo Request
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
6. DUT: Sends ICMP Echo Request
Pass Criteria - Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 73
OPEN Alliance
The Address Resolution module tries to find the <protocol type, target protocol address>
pair in a table. If it does not, it probably informs the caller that it is throwing the packet
Synopsys
away (on the assumption the packet will be retransmitted by a higher network layer), and
generates an Ethernet packet with a type field of ether_type$ADDRESS_RESOLUTION.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
Test
<DIface-0> with
Procedure - Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- for Packet with Ethernet Type set to <Address-Resolution>
4. DUT: Sends ARP Request
Pass Criteria 4. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 74
OPEN Alliance
Synopsys The Address Resolution module sets the ar$hrd field to ares_hrd$Ethernet.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Hardware Type is set to ARP_HARDWARE_ETHERNET
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Hardware Type is set to ARP_HARDWARE_ETHERNET
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 75
OPEN Alliance
The Address Resolution module sets the ar$pro to the protocol type that is being
Synopsys
resolved.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Protocol Type is set to ARP_PROTOCOL_IP
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Protocol Type is set to ARP_PROTOCOL_IP
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 76
OPEN Alliance
The Address Resolution module sets the ar$hln to 6 (the number of bytes in a 48.bit
Synopsys
Ethernet address)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Hardware Address Length is set to <ETHERNET_ADDR_LEN>
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Hardware Address Length is set to <ETHERNET_ADDR_LEN>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 77
OPEN Alliance
The Address Resolution module sets the ar$pln to the length of an address in that
Synopsys
protocol
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Protocol Address Length is set to IP_ADDR_LEN
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Protocol Address Length is set to IP_ADDR_LEN
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 78
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Operation code is set to OPERATION_REQUEST
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Operation code is set to OPERATION_REQUEST
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 79
OPEN Alliance
The Address Resolution module sets the ar$sha with the 48.bit ethernet address of
Synopsys
itself.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- ARP Sender Hardware Address is set to <DIFACE-0-MAC-ADDR>
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- ARP Sender Hardware Address is set to <DIFACE-0-MAC-ADDR>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 80
OPEN Alliance
Synopsys The Address Resolution module sets the ar$spa with the protocol address of itself
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Source IP Address is set to <DIface-0-IP>
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Source IP Address is set to <DIface-0-IP>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 81
OPEN Alliance
The Address Resolution module sets the ar$tpa with the protocol address of the
Synopsys
machine that is trying to be accessed
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: Verify that received ARP Request contains:
- Destination IP Address is set to <HOST-1-IP>
4. DUT: Sends ARP Request
Pass Criteria 5. TESTER: Verify that received ARP Request contains:
- Destination IP Address is set to <HOST-1-IP>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation"
Reference
(MUST)
Notes
The Address Resolution module does not set ar$tha to anything in particular, because it is
this value that it is trying to determine. (Note: In this test TESTER sends an ARP Request
Synopsys
with ARP Target Hardware Address set to all zeroes, and, expects that DUT will send an ARP
Response after receiving the ARP Request)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 82
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
The Address Resolution module does not set ar$tha to anything in particular, because it is
this value that it is trying to determine. (Note: In this test TESTER sends an ARP Request
Synopsys
with ARP Target Hardware Address set to Ethernet Broadcast Address, and, expects that
DUT will send an ARP Response after receiving the ARP Request)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 83
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
The Address Resolution module does not set ar$tha to anything in particular, because it is
this value that it is trying to determine. (Note: In this test TESTER sends an ARP Request
Synopsys
with ARP Target Hardware Address set to an arbitrary value, and, expects that DUT will
send an ARP Response after receiving the ARP Request)
Test Input
Check section general Input Parameters
Parameters
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
ARP_19: ARP request reception (ARP Target Hardware Address = Address of DUT)
The Address Resolution module does not set ar$tha to anything in particular, because it is
Synopsys this value that it is trying to determine. (Note: In this test TESTER sends an ARP Request
with ARP Target Hardware Address set to DUT MAC Address, Ethernet Destination Address
set to Ethernet Broadcast Address, and, expects that DUT will send an ARP Response after
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 84
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Generation" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys ?Do I have the hardware type in ar$hrd? (Note:In this test TESTER is configuring DUT to
clear its ARP Cache entries. TESTER then sends an ARP Request with hardware type field set
to Ethernet. All the other fields in the ARP Request Packet are set to their correct values. It
then expects that DUT should send an ARP Response.)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 85
OPEN Alliance
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Hardware Type set to ARP_HARDWARE_ETHERNET
- Ethernet Source Address set to <MAC-ADDR1>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Response
Pass Criteria 4. DUT: Sends ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys ?Do I have the hardware type in ar$hrd? (Note:Here TESTER is sending correct values for all
the fields in the ARP Request packet except hardware type field and also TESTER is
configuring DUT to clear its ARP Cache entries.The hardware type field is set to an unknown
hardware type value, and TESTER expects that DUT will not send any ARP Response)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
Test
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Procedure containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Hardware Type set to ARP_HARDWARE_TYPE_UNKNOWN
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 86
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
?Do I have the hardware type in ar$hrd? (Note:In this test TESTER is configuring DUT to
Synopsys
clear its ARP Cache entries.TESTER then sends an ARP Response with hardware type field
set to an unknown hardware type value. All the other fields in the ARP Response Packet are
set to their correct values. TESTER then causes DUT to send an ICMP Echo Request and
expects that DUT will send an ARP Request)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
Test - Target IP Address set to <DIface-0-IP>
Procedure - Hardware Type set to ARP_HARDWARE_TYPE_UNKNOWN
- ARP Sender Hardware Address set to <MAC-ADDR1>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 87
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys [optionally check the hardware length ar$hln] (Note:In this test TESTER is configuring DUT
to clear its ARP Cache entries. TESTER then sends an ARP Request with hardware address
length field set to Ethernet Address Length. All the other fields in the ARP Request Packet
are set to their correct values. It then expects that DUT should send an ARP Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Hardware Address Length set to <ETHERNET_ADDR_LEN>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Response
Pass Criteria 4. DUT: Sends ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 88
OPEN Alliance
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
[optionally check the hardware length ar$hln] (Note:In this test TESTER is configuring DUT
Synopsys
to clear its ARP Cache entries. TESTER then sends an ARP Request with hardware address
length field set to unknown hardware address length. All the other fields in the ARP Request
Packet are set to their correct values. It then expects that DUT should NOT send an ARP
Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Hardware Address Length set to UNKNOWN_HW_ADDR_LEN
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Does not send ARP Response
Pass Criteria 4. DUT: Does not send ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Notes
Synopsys When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 89
OPEN Alliance
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Hardware Address Length set to UNKNOWN_HW_ADDR_LEN
Test - ARP Sender Hardware Address set to <MAC-ADDR1>
Procedure - ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
6. DUT: Sends ARP Request
Pass Criteria 6. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 90
OPEN Alliance
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys ?Do I speak the protocol in ar$pro? (Note:In this test TESTER is configuring DUT to clear its
ARP Cache entries. TESTER then sends an ARP Request with protocol type field set to type
IP. All the other fields in the ARP Request Packet are set to their correct values. It then
expects that DUT should send an ARP Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Protocol Type set to ARP_PROTOCOL_IP
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Response
Pass Criteria 4. DUT: Sends ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys following:Negative conditionals indicate an end of processing and a discarding of the packet
?Do I speak the protocol in ar$pro? (Note:In this test TESTER is configuring DUT to clear its
ARP Cache entries. TESTER then sends an ARP Request with protocol type field set to an
unknown protocol type value. All the other fields in the ARP Request Packet are set to their
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 91
OPEN Alliance
correct values. It then expects that DUT should NOT send an ARP Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Protocol Type set to ARP_PROTOCOL_UNKNOWN
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Does not send ARP Response
Pass Criteria 4. DUT: Does not send ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
?Do I speak the protocol in ar$pro? (Note:In this test TESTER is configuring DUT to clear its
Synopsys
ARP Cache entries.TESTER then sends an ARP Response with protocol type field set to
Unknown Protocol value. All the other fields in the ARP Response Packet are set to their
correct values. TESTER then causes DUT to send an ICMP Echo Request and expects that
DUT will send an ARP Request)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 92
OPEN Alliance
Parameters <ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Protocol Type set to ARP_PROTOCOL_UNKNOWN
Test - ARP Sender Hardware Address set to <MAC-ADDR1>
Procedure - ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
6. DUT: Sends ARP Request
Pass Criteria 6. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys [optionally check the protocol length ar$pln] (Note:In this test TESTER is configuring DUT to
clear its ARP Cache entries. TESTER then sends an ARP Request with protocol length field
set to IP Address Length. All the other fields in the ARP Request Packet are set to their
correct values. It then expects that DUT should send an ARP Response.)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 93
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- Protocol Address Length set to IP_ADDR_LEN
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Response
Pass Criteria 4. DUT: Sends ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
[optionally check the protocol length ar$pln] (Note:In this test TESTER is configuring DUT to
Synopsys
clear its ARP Cache entries. TESTER then sends an ARP Request with protocol address length
field set to an unknown protocol address length. All the other fields in the ARP Request
Packet are set to their correct values. It then expects that DUT should NOT send an ARP
Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
Test of <DIface-0>
Procedure - containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 94
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
[optionally check the protocol length ar$pln] (Note:In this test TESTER is configuring DUT to
Synopsys
clear its ARP Cache entries. TESTER then sends an ARP Response with protocol length field
set to an unknown protocol address length. All the other fields in the ARP Response Packet
are set to their correct values. TESTER then causes DUT to send an ICMP Echo Request and
expects that DUT will send an ARP Request)
<MAC-ADDR1>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
Test
- Sender IP Address set to <HOST-1-IP>
Procedure - Target IP Address set to <DIface-0-IP>
- Protocol Address Length set to UNKNOWN_PROTOCOL_ADDR_LEN
- ARP Sender Hardware Address set to <MAC-ADDR1>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 95
OPEN Alliance
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
6. DUT: Sends ARP Request
Pass Criteria 6. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MAY)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following. Negative conditionals indicate an end of processing and a discarding of the
packet. Merge_flag := false If the pair <protocol type, sender protocol address is already in
Synopsys my translation table, update the ARP sender hardware address field of the entry with the
new information in the packet and set Merge_flag to true. (Note: Here TESTER sends an
ARP Request to DUT so that an entry gets added to the dut arp cache. TESTER then sends
another ARP Request with a different Ethernet source address to DUT to check if the
existing entry gets updated.)
<MAC-ADDR1>
Test Input <MAC-ADDR2>
Parameters <ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
Test
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Procedure containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 96
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following. Negative conditionals indicate an end of processing and a discarding of the
packet. Merge_flag := false If the pair <protocol type, sender protocol address is already in
Synopsys my translation table, update the ARP sender hardware address field of the entry with the
new information in the packet and set Merge_flag to true. (Note: Here TESTER sends an
ARP Response to DUT so that an entry gets added to the dut arp cache. TESTER then sends
another ARP Response with a different Ethernet source address to DUT to check if the
existing entry gets updated.)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 97
OPEN Alliance
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
Test - Sender IP Address set to <HOST-1-IP>
Procedure - Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR2>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
4. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
5. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
6. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR2>
7. DUT: Sends ICMP Echo Request
Pass Criteria 7. DUT: Sends ICMP Echo Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following. Negative conditionals indicate an end of processing and a discarding of the
Synopsys packet. Merge_flag := false If the pair <protocol type, sender protocol address is already in
my translation table, update the ARP sender hardware address field of the entry with the
new information in the packet and set Merge_flag to true. (Note: Here TESTER sends an
ARP Request to DUT so that an entry gets added to the dut arp cache. TESTER then sends an
ARP Response with a different Ethernet source address to DUT to check if the existing entry
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 98
OPEN Alliance
gets updated.)
<MAC-ADDR1>
Test Input <MAC-ADDR2>
Parameters <ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
3. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
Test
- Target IP Address set to <DIface-0-IP>
Procedure - ARP Sender Hardware Address set to <MAC-ADDR2>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
4. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
5. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
6. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR2>
7. DUT: Sends ICMP Echo Request
Pass Criteria 7. DUT: Sends ICMP Echo Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 99
OPEN Alliance
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following. Negative conditionals indicate an end of processing and a discarding of the
packet. Merge_flag := false If the pair <protocol type, sender protocol address is already in
Synopsys my translation table, update the ARP sender hardware address field of the entry with the
new information in the packet and set Merge_flag to true. (Note: Here TESTER sends an
ARP Response to DUT so that an entry gets added to the dut arp cache. TESTER then sends
an ARP Request with a different Ethernet source address to DUT to check if the existing
entry gets updated.)
<MAC-ADDR1>
Test Input <MAC-ADDR2>
Parameters <ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
Test
- Sender IP Address set to <HOST-1-IP>
Procedure - Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR2>
4. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
5. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
6. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR2>
7. DUT: Sends ICMP Echo Request
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 100
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys ?Am I the target protocol address? (Note: In this test TESTER is configuring DUT to clear its
ARP Cache entries. TESTER then sends an ARP Request with target protocol address field set
to <DIface-0-IP>. All the other fields in the ARP Request Packet are set to their correct
values. It then expects that DUT should send an ARP Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
Test 2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Procedure containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Response
Pass Criteria 4. DUT: Sends ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 101
OPEN Alliance
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following:Negative conditionals indicate an end of processing and a discarding of the packet
Synopsys ?Am I the target protocol address? (Note: In this test TESTER is configuring DUT to clear its
ARP Cache entries. TESTER then sends an ARP Request with target protocol address field set
to an IP First unused address value. All the other fields in the ARP Request Packet are set to
their correct values. It then expects that DUT should NOT send an ARP Response.)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
Test
containing:
Procedure - Sender IP Address set to <HOST-1-IP>
- Target IP Address set to
<IP-FIRST-UNUSED-ADDR-INTERFACE-1>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Does not send ARP Response
Pass Criteria 4. DUT: Does not send ARP Response
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys following:Negative conditionals indicate an end of processing and a discarding of the packet
?Am I the target protocol address? (Note: In this test TESTER is configuring DUT to clear its
ARP Cache entries. TESTER then sends an ARP Response with target protocol address field
set to IP First unused address value. All the other fields in the ARP Response Packet are set
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 102
OPEN Alliance
to their correct values. TESTER then causes DUT to send an ICMP Echo Request and expects
that DUT will send an ARP Request)
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
- Source IP Address set to <HOST-1-IP>
- Destination IP Address set to
<IP-FIRST-UNUSED-ADDR-INTERFACE-1>
Test - Ethernet Source Address set to <MAC-ADDR1>
Procedure - Ethernet Destination Address set to ETHERNET_BROADCAST_ADDR
3. TESTER: <HOST-1> Waits up to (1) second(s) for the ARP cache of DUT
to get refreshed
4. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
5. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
6. DUT: Sends ARP Request
Pass Criteria 6. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys following. Negative conditionals indicate an end of processing and a discarding of the
packet. If Merge_flag is false, add the triplet <protocol type, sender protocol address,
sender hardware address> to the translation table. (Note: In this test TESTER sends an ARP
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 103
OPEN Alliance
Request with <sender protocol address, sender hardware address> fields set to <HOST-1-IP,
MAC-ADDR2>. TESTER then causes DUT to send an ICMP Echo Request and expects that
DUT will send an ICMP Echo Request with Ethernet Destination Address set to <MAC-
ADDR2>)
<MAC-ADDR2>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
Test
- Sender IP Address set to <HOST-1-IP>
Procedure - Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR2>
6. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
7. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
8. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR2>
9. DUT: Sends ICMP Echo Request
4. DUT: Sends ARP Request
Pass Criteria
9. DUT: Sends ICMP Echo Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 104
OPEN Alliance
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following. Negative conditionals indicate an end of processing and a discarding of the
packet. If Merge_flag is false, add the triplet <protocol type, sender protocol address,
Synopsys sender hardware address> to the translation table. (Note:In this test TESTER sends an ARP
Response with <sender protocol address, sender hardware address> fields set to <HOST-1-
IP, MAC-ADDR3>. TESTER then causes DUT to send an ICMP Echo Request and expects that
DUT will send an ICMP Echo Request with Ethernet Destination Address set to <MAC-
ADDR3>)
<MAC-ADDR3>
Test Input
<ARP-TOLERANCE-TIME>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
4. DUT: Sends ARP Request
5. TESTER: <HOST-1> Sends ARP Response to DUT through <DIface-0>
containing:
Test - Sender IP Address set to <HOST-1-IP>
Procedure - Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR3>
- ARP Target Hardware Address set to ETHERNET_BROADCAST_ADDR
6. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
arp cache of DUT to get refreshed
7. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
8. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR3>
9. DUT: Sends ICMP Echo Request
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 105
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following: ?Is the opcode ares_op$REQUEST? Yes:Set the ar$op field to ares_op$REPLY
Synopsys
(Note: In this test TESTER sends an ARP Request. All other fields in the ARP Request
message are set correctly. TESTER then expects that DUT will send an ARP Packet with
Operation code field set to Response)
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 106
OPEN Alliance
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
following: Negative conditionals indicate an end of processing and a discarding of the
Synopsys
packet. ?Is the opcode ares_op$REQUEST? (Note:In this test TESTER sends an ARP Packet
with opcode field set to response value, and expects that DUT will not send any ARP
Response)
Test Input
Check section general Input Parameters
Parameters
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys
following: ?Is the opcode ares_op$REQUEST? Swap hardware field, putting the local
hardware address in the sender field.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 107
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys
following: ?Is the opcode ares_op$REQUEST? Swap protocol field, putting the local
protocol address in the sender field.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 108
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
When an address resolution packet is received, the receiving Ethernet module gives the
packet to the Address Resolution module which goes through an algorithm similar to the
Synopsys
following: ?Is the opcode ares_op$REQUEST? Yes: Send the packet to the (new) ARP target
hardware address on the same hardware on which the request was received.
<MAC-ADDR1>
Test Input
<MAC-ADDR2>
Parameters
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
3. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
Test
4. DUT: Sends ARP Response
Procedure 5. TESTER: Verify that received ARP Response contains:
- ARP Target Hardware Address is set to <MAC-ADDR1>
6. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR2>
7. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
8. DUT: Sends ARP Response
9. TESTER: Verify that received ARP Response contains:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 109
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception" (MUST)
Notes
Synopsys For the 10Mbit Ethernet <ar$hrd> takes on the value <1>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception"
Reference
(MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 110
OPEN Alliance
Synopsys For the 10Mbit Ethernet <ar$hln> takes on the value <6>
RFC 826 "An Ethernet Address Resolution Protocol", section "Packet Reception"
Reference
(MUST)
Notes
If no packets are received from a host for a suitable length of time, the address
Synopsys
resolution entry is forgotten.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 111
OPEN Alliance
<DYNAMIC-ARP-CACHE-TIMEOUT+ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to set a timeout of
<DYNAMIC-ARP-CACHE-TIMEOUT> seconds
for the dynamic entries in the ARP Cache of <DIface-0>
3. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
4. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
ARP cache of DUT to get refreshed
5. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
Test Procedure
- Destination IP Address set to <HOST-1-IP>
6. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Target IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
7. DUT: Sends ICMP Echo Request
8. TESTER: <HOST-1> Waits up to
(<DYNAMIC-ARP-CACHE-TIMEOUT+ARP-TOLERANCE-TIME>) second(s) for the arp
cache of DUT to get refreshed
9. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
10. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
11. DUT: Sends ARP Request
12. CLEANUP: Configure DUT to clear a timeout of
<DYNAMIC-ARP-CACHE-TIMEOUT> seconds
for the dynamic entries in the ARP Cache of <DIface-0>
7. DUT: Sends ICMP Echo Request
Pass Criteria
11. DUT: Sends ARP Request
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Related issue" (SHOULD)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 112
OPEN Alliance
It may be desirable to have table aging and/or timeouts. (Note: In this test case TESTER
Synopsys
expects that DUT should delete a given Dynamic ARP Cache Entry even if it is being used.)
<MAC-ADDR1>
Test Input <DYNAMIC-ARP-CACHE-TIMEOUT>
Parameters <ARP-TOLERANCE-TIME>
Check section general Input Parameters
1. DUT CONFIGURE: Configure DUT to clear the dynamic entries in the ARP Cache
of <DIface-0>
- containing IP Address <HOST-1-IP>
2. DUT CONFIGURE: Configure DUT to set a timeout of
<DYNAMIC-ARP-CACHE-TIMEOUT> seconds
for the dynamic entries in the ARP Cache of <DIface-0>
3. TESTER: <HOST-1> Sends ARP Request to DUT through <DIface-0>
containing:
- Sender IP Address set to <HOST-1-IP>
- Target IP Address set to <DIface-0-IP>
- ARP Sender Hardware Address set to <MAC-ADDR1>
4. TESTER: <HOST-1> Waits up to (<ARP-TOLERANCE-TIME>) second(s) for the
ARP cache of DUT to get refreshed
5. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
Test Procedure - Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
6. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
7. DUT: Sends ICMP Echo Request
8. TESTER: <HOST-1> Waits up to (<DYNAMIC-ARP-CACHE-TIMEOUT>/2>)
second(s) for the ARP cache of DUT to get refreshed
9. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Source IP Address set to <DIface-0-IP>
- Destination IP Address set to <HOST-1-IP>
10. TESTER: <HOST-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Destination IP Address set to <HOST-1-IP>
- Ethernet Destination Address set to <MAC-ADDR1>
11. DUT: Sends ICMP Echo Request
12. TESTER: <HOST-1> Waits up to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 113
OPEN Alliance
Reference RFC 826 "An Ethernet Address Resolution Protocol", section "Related issue" (MAY)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 114
OPEN Alliance
4.2.1 General
The scope of this chapter is to specify test cases for the Internet Control Message Protocol Version 4
(ICMPv4) from the following standards:
<TIface-0> <DIface-0>
ECU
4.2.1.4 Coverage
Specification Document Section Number Test Category Test Number(s)
RFC 792: Internet Error Handling ICMPv4_ERROR_1 to
Control Message ICMPv4_ERROR_3
Protocol
RFC 1122: Requirements 3.2.2 Error Handling ICMPv4_ERROR_4,
for Internet Hosts ICMPv4_ERROR_5
RFC 792: Internet 4.2.3.2 ICMP Types ICMPv4_TYPE_1 to
Control Message ICMPv4_TYPE_12,
Protocol ICMPv4_TYPE_16 to
ICMPv4_TYPE_18,
ICMPv4_TYPE_21,
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 115
OPEN Alliance
ICMPv4_TYPE_22
This is the maximum time interval for which TESTER waits for an ICMP Reply
<ListenTime> packet. This defaults to 3 seconds unless DUT configuration specifies
otherwise.
This is the maximum time interval for which TESTER waits for a packet for
cases when a certain event has to be manually triggered on the DUT either
<TriggerTime>
by some protocol timer or using some external mechanism. This defaults to
30 seconds unless DUT configuration specifies otherwise.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 116
OPEN Alliance
NOTE: As a general test pattern it can be assumed that all events will be guarded by a timer, e.g.
receiving or non-receiving of message. Due to the difference nature of guarding, different default values
can be assumed:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 117
OPEN Alliance
The ICMP messages typically report errors in the processing of datagrams. To avoid the
infinite regress of messages about messages etc., no ICMP messages are sent about ICMP
Synopsis messages. (Note: This tests that no ICMP message is sent when an erroneous ICMP
messages is received, thus avoiding an infinite loop. This test is ran when
<DUTSupportsIPOptions> is TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 118
OPEN Alliance
Also ICMP messages are only sent about errors in handling fragment zero of fragmented
datagrams. (Note: This tests that ICMP error message is sent on receiving the fragment
Synopsis
having Fragment Offset field set to zero. This test is ran when <DUTSupportsIPOptions> is
TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 119
OPEN Alliance
Also ICMP messages are only sent about errors in handling fragment zero of fragmented
datagrams. (Note: This tests that ICMP error message is not sent on receiving non zero
Synopsis
fragment i.e Fragment Offset field set to non-zero value. This test is ran when
<DUTSupportsIPOptions> is TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Test Procedure
2. TESTER: Send an IP packet to <DIface-0>, containing:
- Source Address field set to address of host-1
- Destination Address field set to address of DUT
- Fragment Offset field set to data size sent in first
IP packet in unit of 8-octets
- Flags first, containing:
- MF bit set to zero
- IP Options, containing:
- One Internet Timestamp option, containing:
- length field set to 10
- pointer field set to 9
- one timestamp value
- last half of the constructed ICMP packet
3. TESTER: Listen (for up to <ListenTime> seconds) on <DIface-0>
4. DUT: Do not send ICMP Parameter Problem messages
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 120
OPEN Alliance
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 121
OPEN Alliance
An ICMP error message MUST NOT be sent as the result of receiving a datagram destined
Synopsis
to an IP broadcast. (Note: This test is ran when <DUTSupportsIPOptions> is TRUE)
Reference RFC 1122 s3.2.2 p39 Internet Control Message Protocol -- ICMP (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 122
OPEN Alliance
Reference RFC 1122 s3.2.2 p38 Internet Control Message Protocol -- ICMP (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 123
OPEN Alliance
If, in the destination host, the IP module cannot deliver the datagram because the
Synopsis indicated protocol module or process port is not active, the destination host may send a
destination unreachable message to the source host.
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 124
OPEN Alliance
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 125
OPEN Alliance
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 126
OPEN Alliance
Synopsis If fragment zero is not available then no time exceeded need be sent at all.
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 127
OPEN Alliance
If the gateway or host processing a datagram finds a problem with the header parameters
Synopsis such that it cannot complete processing the datagram it must discard the datagram. (Note:
This test is ran when <DUTSupportsIPOptions> is TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 128
OPEN Alliance
If the gateway or host processing a datagram finds a problem with the header parameters
such that it cannot complete processing the datagram it may notify the source host via the
Synopsis
parameter problem message. (Note: This test is ran when <DUTSupportsIPOptions> is
TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 129
OPEN Alliance
Unused filed in Parameter Problem Message is set to zero and it contains the exactly same
Synopsis Internet Header and 64 bits of Original Datagram. (Note: This test is ran when
<DUTSupportsIPOptions> is TRUE)
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 130
OPEN Alliance
Synopsis The data received in the echo message must be returned in the echo reply message.
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 131
OPEN Alliance
The identifier and sequence number may be used by the echo sender to aid in
Synopsis
matching the replies with the echo requests.
<idfr>
Test Input
<seqno>
Parameters
Check section “Parameters used in the tests”
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 132
OPEN Alliance
The checksum is the 16-bit one's complement of the one's complement sum of the ICMP
message starting with the ICMP Type. For computing the checksum, the checksum field
Synopsis should be zero. If the total length is odd, the received data is padded with one octet of
zeros for computing the checksum. (Note: This tests that a node does not send ICMP Echo
Reply if ICMP Checksum is incorrect).
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 133
OPEN Alliance
The data received (a timestamp) in the message is returned in the reply together with
Synopsis
an additional timestamp.
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 134
OPEN Alliance
The identifier and sequence number may be used by the echo sender to aid in
Synopsis
matching the replies with the requests.
<idfr>
Test Input
<seqno>
Parameters
Check section “Parameters used in the tests”
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 135
OPEN Alliance
ICMPv4_TYPE_16: Ensure that the DUT does not accept an ICMPv4 Information
Request and does not generate a ICMPv4 Information Reply
Ensure that
when a DUT receives an ICMPv4 Packet
containing a Type
indicating a value of 15 (Information Request)
and containing a Code
indicating a value of 0
and containing a valid Checksum
Synopsis
and containing an Identifier
indicating a value of ID1
and containing a Sequence Number
indicating a value of SEQ1
then the DUT discards the message and does not send an ICMPv4 Packet
containing a Type
indicating a value of 16 (Information Reply)
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 136
OPEN Alliance
ICMPv4_TYPE_17: Ensure that the DUT accepts an ICMPv4 Timestamp and generates
a valid ICMPv4 Timestamp Reply
Ensure that
when a DUT receives an ICMPv4 Packet
containing a Type
indicating a value of 13 (Timestamp Request)
and containing a Code
indicating a value of 0
and containing a valid Checksum
and containing an Identifier
indicating a value of ID1
and containing a Sequence Number
Synopsis indicating a value of SEQ1
then the DUT sends an ICMPv4 Packet
containing a Type
indicating a value of 14 (Timestamp Reply)
and containing a Code
indicating a value of 0
and containing a valid Checksum
and containing an Identifier
indicating a value of ID1
and containing a Sequence Number
indicating a value of SEQ1
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 137
OPEN Alliance
Test Iterations
Notes OPTIONAL
Ensure that
when a DUT receives an IPv4 Packet
containing an IPv4 Header
containing a Protocol
indicating a value of <unsupportedProtocol>
Synopsis
then the DUT sends an ICMPv4 Packet
containing a Type
indicating a value of 3 (Destination Unreachable)
and containing a Code
indicating a value of 2 (Protocol unreachable)
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 138
OPEN Alliance
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 139
OPEN Alliance
ICMPv4_TYPE_21: Ensure that the DUT does not generate an ICMPv4 Time Exceeded
message when reassembly fails due to the absence of the first fragment
Ensure that
when a DUT receives an IPv4 Packets
containing an IPv4 Header
containing Flags
containing DF flag
indicating a value of 0
Synopsis containing MF flag
indicating a value of 1
and containing Offset
indicating a value not equal to 0
then the DUT does not send an ICMPv4 Packet
containing a Type
indicating a value of 11
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 Packet with DF=1 (Don’t Fragment) and MF=1 (More
Test Procedure
Fragments) and an Offset not equal to 0
2. DUT: Does not send an ICMPv4 Time Exceeded message
The DUT does not send an ICMPv4 Packet
Pass Criteria containing a Type
indicating a value of 11
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 140
OPEN Alliance
A host must respond to all ICMP Echo Requests sent to it, by sending an ICMP Echo
Synopsis
Reply back to the sender of ICMP Echo Request.
Test Input
Check section “Parameters used in the tests”
Parameters
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 141
OPEN Alliance
4.3.1 General
The scope of this chapter is to specify test cases for the Internet Protocol Version 4 (IPv4) from the
following standards:
Though the focus of conformance testing has been limited to the above mentioned specification
documents we have relied heavily upon the following document as specification for transmission of IP
Datagrams over Ethernet Options:
RFC 894 - A Standard for the Transmission of IP Datagrams over Ethernet Networks
<TIface-0> <DIface-0>
ECU
HOST-1
TOPOLOGY-1
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 142
OPEN Alliance
<TIface-0> <DIface-0>
ECU
<TIface-1> <DIface-1>
HOST-1
TOPOLOGY-2
4.3.1.4 Coverage
Specification Document Section Test Category Test Number(s)
Number
RFC 791 3.1 IPv4 Header IPv4_HEADER_01 to
IPv4_HEADER_05,
IPv4_HEADER_08,
IPv4_HEADER_09
RFC 791 3.1 IPv4 Checksum IPv4_CHECKSUM_01,
IPv4_CHECKSUM_02,
IPv4_CHECKSUM_04,
IPv4_CHECKSUM_05
RFC 791 3.1 IPv4 Time to Live IPv4_TTL_01 , IPv4_TTL_03
to IPv4_TTL_05
RFC 791 3.1 IPv4 Version Number IPv4_VERSION_01,
IPv4_VERSION_03,
IPv4_VERSION_04
RFC 791 3.2 IPv4 Addressing IPv4_ADDRESSING_01 to
IPv4_ADDRESSING_03
RFC 791 2.3 IPv4 Fragments IPv4_FRAGMENTS_1 to
IPv4_FRAGMENTS_5
RFC 791 3.2 IPv4 Options IPv4_OPTIONS_1 to
IPv4_OPTIONS_14
RFC 791 3.2 IPv4 Reassembly IPv4_REASSEMBLY_01 to
IPv4_REASSEMBLY_11
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 143
OPEN Alliance
<LowTTLValue> Time To Live value in a Fragmented packet. This value is less than the
initial timer setting which is 15 seconds
<non-reserve-value>
A value which is not zero.
<limitedBroadcastAddress> The limited broadcast address addresses every host on the connected
physical network. {-1, -1} -> 255.255.255.255
<loopBackAddress>
The internal host loopback address, e.g. 127.0.0.1
<MTU>
The Maximum Transmission Unit size.
NOTE: As a general test pattern it can be assumed that all events will be guarded by a timer, e.g.
receiving or non-receiving of message. Due to the difference nature of guarding, different default values
can be assumed:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 144
OPEN Alliance
IPv4_HEADER_01: Ensure that the DUT generates an IPv4 Packet with a Total Length
greater than or equal to 20.
Ensure that
when the DUT is requested to generate an IPv4 packet,
then the DUT generates an IPv4 Packet
Synopsis
containing an IPv4 Header
containing a Total Length
indicating a value greater than or equal to 20.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 145
OPEN Alliance
IPv4_HEADER_02: Ensure that the DUT discards an IPv4 Packet with an invalid
Header Length
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Header Length
indicating a value less than 20,
then the DUT discards the IPv4 Packet silently.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an ICMPv4 Echo Request with a header length indicating a value less
Test Procedure
than 20
2. DUT: Does not send an ICMPv4 Echo Reply
Pass Criteria The DUT discards the IPv4 Packet silently.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 146
OPEN Alliance
IPv4_HEADER_03: Ensure that the DUT generates an IPv4 Packet with the Source
Address being one of its IPv4 Addresses
Ensure that
when the DUT is requested to generate an IPv4 packet,
then the DUT sends an IPv4 Packet
Synopsis
containing an IPv4 Header
containing a Source Address
indicating one of its defined IPv4 addresses.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Reference Derived from RFC791 section 3.1, 3.2, RFC1122 section 3.2.1.3
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 147
OPEN Alliance
IPv4_HEADER_04: Ensure that the DUT discards an IPv4 Packet with an incorrect
Destination Address
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis containing a Destination Address
indicating a value different from the DUT’s IPv4 address and is not a Broadcast or
Multicast address,
then the DUT discards the IPv4 Packet silently.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an ICMPv4 Echo Request with destination address different than the
Test Procedure DUT’s IPv4 address
2. DUT: Does not send an ICMPv4 Echo Reply
Test Iterations
Reference Derived from RFC791 section 3.1, 3.2, RFC1122 section 3.2.1.3
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 148
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.1 p13 Internet Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 149
OPEN Alliance
Internet Header Length is the length of the internet header in 32 bit words, and thus
Synopsis points to the beginning of the data. Note that the minimum value for a correct header is 5.
(Note: Tests that DUT discards a packet with total length smaller than implied by IHL value)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p11 Internet Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 150
OPEN Alliance
Total Length is the length of the datagram, measured in octets, including internet header
Synopsis and data. (Note: Tests that DUT discards a packet with total length bigger than the actual
transmitted data)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p13 Internet Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 151
OPEN Alliance
IPv4_CHECKSUM_01: Ensure that the DUT generates an IPv4 Packet with a valid
Header Checksum
Ensure that
when the DUT generates an IPv4 packet
then the DUT sends an IPv4 Packet
Synopsis
containing an IPv4 Header
containing a Header Checksum
indicating a valid checksum.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 152
OPEN Alliance
IPv4_CHECKSUM_02: Ensure that the DUT discards an IPv4 Packet with an invalid
Header Checksum
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Header Checksum
indicating an invalid <invalidChecksum>,
then the DUT discards the IPv4 Packet silently.
Prerequisites None
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 153
OPEN Alliance
The checksum field is the 16 bit one's complement of the one's complement sum of all 16
bit words in the header. For purposes of computing the checksum, the value of the
Synopsis
checksum field is zero. (Note: Here we are verifying that DUT uses same checksum
calculation method as we are expecting)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p14 Internet Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 154
OPEN Alliance
The checksum field is the 16 bit one's complement of the one's complement sum of all 16
bit words in the header. For purposes of computing the checksum, the value of the
checksum field is zero. (Note: Here we send an Echo Request with checksum calculated
Synopsis
according to rfc. DUT receives this Echo Request, verifies the Echo Request and then sends
Echo Reply. We then verify that DUT uses the checksum calculation method according to
rfc)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p14 Internet Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 155
OPEN Alliance
IPv4_TTL_01: Ensure that the DUT generates an IPv4 Packet with TTL value greater
than 0
Ensure that
when the DUT generates an IPv4 packet
then the DUT sends an IPv4 packet
Synopsis
containing an IPv4 Header
containing a TTL
indicating a value greater than 0.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Reference Derived from RFC791 section 3.1 and 3.2, RFC1122 section 3.2.1.7
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 156
OPEN Alliance
IPv4_TTL_03: Ensure that the DUT decrements the TTL of a forwarded IPv4 Packet by
at least 1
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
containing a TTL
Synopsis indicating a value TTL1
then the DUT forwards and sends an IPv4 packet
containing an IPv4 Header
containing a TTL
indicating a value less than TTL1.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with a TTL value TTL1 which is greater than 2
Test Procedure
2. DUT: Sends an IPv4 packet with a TTL value less than TTL1
Test Iterations
Reference Derived from RFC791 section 3.1 and 3.2, RFC1122 section 3.2.1.7
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 157
OPEN Alliance
IPv4_TTL_04: Ensure that the DUT discards an IPv4 packet with a TTL of 0 if the IPv4
packet has to be forwarded
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a TTL
indicating a value 0
then the DUT does not forwards and discards the IPv4.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an ICMPv4 Echo Request with a TTL value of 0 which has to be
Test Procedure forwarded
2. DUT: Does not forward the ICMPv4 Echo Request
Pass Criteria The DUT does not forwards and discards the IPv4.
Test Iterations
Reference Derived from RFC791 section 3.1 and 3.2, RFC1122 section 3.2.1.7
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 158
OPEN Alliance
A host MUST NOT discard a datagram just because it was received with TTL less than
Synopsis
2.
Test Input
Check section general Input Parameters
Parameters
1. CASE: <ttl> = 0
Test Iterations
2. CASE: <ttl> = 1
Notes Derived from RFC 1122 s3.2.1.7 p34 Time-to-Live: RFC-791 Section 3.2 (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 159
OPEN Alliance
IPv4_VERSION_01: Ensure that the DUT accepts an IPv4 Packet with a valid Version 4
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Version
indicating a value of 4,
then the DUT accepts the IPv4 Packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 160
OPEN Alliance
IPv4_VERSION_03: Ensure that the DUT generates a IPv4 Packet with a valid Version
4
Ensure that
when the DUT generates an IPv4 packet
then the DUT sends an IPv4 Packet
Synopsis
containing an IPv4 Header
containing a Version
indicating a value of 4.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 161
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 791 s3.1 p11 Internet Header Format (Version), RFC 1122 s3.2.1.1 p29
Notes
Version Number: RFC-791 Section 3.1 (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 162
OPEN Alliance
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Destination Address
indicating a value of Limited Broadcast,
then the DUT accepts the IPv4 Packet.
Prerequisites None
Pass Criteria The DUT accepts the IPv4 Packet and answers correctly with an ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 163
OPEN Alliance
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Destination Address
indicating a value of Directed Broadcast,
then the DUT discards the IPv4 Packet silently.
Prerequisites None
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 164
OPEN Alliance
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis
containing a Destination Address
indicating a value of Loop Back,
then the DUT discards the IPv4 packet silently.
Prerequisites None
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 165
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 166
OPEN Alliance
fragments.
Test Iterations
Derived from RFC 791 s2.3 p9 Function Description (Fragmentation), RFC 791 s3.2 p29
Notes
Discussion (Identification), RFC 1122 s3.3.2 p56 Reassembly (MUST)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 167
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s2.3 p9 Function Description (Fragmentation) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 168
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 169
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s2.3 p9 Function Description (Fragmentation) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 170
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 171
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s2.3 p9 Function Description (Fragmentation) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 172
OPEN Alliance
The fragmentation strategy is designed so than an unfragmented datagram has all zero
Synopsis
fragmentation information (MF = 0, fragment offset = 0).
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 173
OPEN Alliance
Ensure that
Synopsis when the DUT receives a series of IPv4 Fragments of a large IPv4 packet
then the DUT reassembles and accepts the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send several IPv4 packets as continuation of the ICMPv4 Echo Request with
MF = 1 (More Fragments) and Offset incremented each time by the payload size of the
Test Procedure
previous packet, and the ID being the same as the first fragment
3. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset incremented by
the payload size of the previous packet, and the ID being the same as the first fragment
4. DUT: Sends an ICMPv4 Echo Reply
The DUT reassembles and accepts the IPv4 packet and answers correctly with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 174
OPEN Alliance
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send an IPv4 packet with), MF = 0 (Last Fragment) and Offset incremented by
Test Procedure
the payload size of the previous packet, and the ID being different from the first
fragment
3. DUT: Does not send an ICMPv4 Echo Reply
The DUT does not reassemble and accept the IPv4 packet and does not answer with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 175
OPEN Alliance
Ensure that
when the DUT receives a series of IPv4 Fragments of a large IPv4 packet
containing an IPv4 Header
Synopsis
containing a Protocol
indicating different values
then the DUT does not reassemble and accept the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset incremented by
Test Procedure
the payload size of the previous packet, and the Protocol being different from the first
fragment
3. DUT: Does not send an ICMPv4 Echo Reply
The DUT does not reassemble and accept the IPv4 packet and does not answer with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 176
OPEN Alliance
Ensure that
Synopsis when the DUT receives a series of unordered IPv4 Fragments of a large IPv4 packet
then the DUT reassembles and accept the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset correctly
incremented, but belonging to the third fragment, and the ID being the same as the first
fragment
Test Procedure 3. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset correctly
incremented, but belonging to the second fragment, and the ID being the same as the
first fragment
4. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset correctly
incremented, and the ID being the same as the first fragment
5. DUT: Sends an ICMPv4 Echo Reply
The DUT reassembles and accept the IPv4 packet and answers correctly with an ICMPv4
Pass Criteria
Echo Request.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 177
OPEN Alliance
Ensure that
when the DUT receives a series of IPv4 Fragments of a large IPv4 packet including a
Synopsis duplicated fragment
then the DUT discards the duplicated fragment, reassembles and accepts the IPv4
packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset correctly
incremented, and the ID being the same as the first fragment
3. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset indicating the
Test Procedure
same value as in test step 2, and the ID being the same as the first fragment
4. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset correctly
incremented, and the ID being the same as the first fragment
5. DUT: Sends an ICMPv4 Echo Reply, not including any data from the fragment sent in
test step 3
The DUT discards the duplicated fragment, reassembles and accepts the IPv4 packet and
Pass Criteria answers correctly with an ICMPv4 Echo Reply not including any data from the
duplicated fragment.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 178
OPEN Alliance
Ensure that
when the DUT receives a series of IPv4 Fragments of a large IPv4 packet
containing an IPv4 Header
Synopsis
containing an Offset
indicating a value different than 0 but with correct increment
then the DUT does not reassemble and accept the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset not equal to 0,
containing an ICMPv4 Echo Request where the Total length is less than the MTU
Test Procedure 2. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset correctly
incremented, and the ID being the same as the first fragment
3. DUT: Does not send an ICMPv4 Echo Reply
The DUT does not reassemble and accept the IPv4 packet and does not answer with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 179
OPEN Alliance
Ensure that
when the DUT receives a series of IPv4 Fragments of a large IPv4 packet including the
Synopsis
first and the last fragment but missing some in between
then the DUT does not reassemble and accept the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
2. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset correctly
incremented, and the ID being the same as the first fragment
Test Procedure
3. TESTER: Send an IPv4 packet with MF = 0 (Last Fragment) and Offset is incremented
as if one more fragment would have been sent, and the ID being the same as the first
fragment
4. DUT: Does not send an ICMPv4 Echo Reply
The DUT does not reassemble and accept the IPv4 packet and does not answer with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 180
OPEN Alliance
Ensure that
when the DUT receives a series of IPv4 Fragments of a large IPv4 packet but no last
Synopsis
fragment
then the DUT does not reassemble and accept the IPv4 packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset = 0, containing
an ICMPv4 Echo Request where the Total length is less than the <MTU>
Test Procedure 2. TESTER: Send an IPv4 packet with MF = 1 (More Fragments) and Offset correctly
incremented, and the ID being the same as the first fragment
3. DUT: Does not send an ICMPv4 Echo Reply
The DUT does not reassemble and accept the IPv4 packet and does not answer with an
Pass Criteria
ICMPv4 Echo Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 181
OPEN Alliance
Ensure that
when the DUT receives an IPv4 packet
containing an IPv4 Header
Synopsis containing Flags
and containing a MF flag
indicating that there are more fragments coming: MF = 1,
then the DUT discards the IPv4 Packet silently.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
The DUT discards the IPv4 Packet silently and does not answer with an ICMPv4 Echo
Pass Criteria
Reply.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 182
OPEN Alliance
Synopsis The current recommendation for the initial timer setting is 15 seconds.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 183
OPEN Alliance
multiple of 8-octets
8. TESTER: Wait for (<ipIniReassembleTimeout> + <ParamToleranceTime>) seconds
9. TESTER: Send an IP packet to <DIface-0>, containing:
- Source Address field set to address of host-1
- Destination Address field set to address of DUT
- Fragment Offset field set to data size sent in first IP
packet in unit of 8-octets
- Flags field, containing:
- MF bit set to zero
- TTL field set to 15
- last half of the constructed ICMP packet
10. TESTER: Listen (for upto <ListenTime> seconds) on <DIface-0>
11. DUT: Do not send ICMP Echo Reply
12. TESTER: Wait for <ipIniReassembleTimeout> seconds
13. NOTE: TESTER has to wait for <ipIniReassembleTimeout> seconds
so that timeout occurs for fragment-2 stored in DUT's reassembly
buffer. If this does not happen then it may lead to a scenario
where fragment-2 stored in the DUT's reassembly buffer
may be mistaken for a fragment-1 of another test case.
So a timeout needs to occur for fragment-2.
5. DUT: Send ICMP Echo Reply
6. TESTER: Verify that Identifier, Sequence Number and Data of ICMP
Pass Criteria Echo Reply are same as those of ICMP Echo Request sent in two
fragments.
11. DUT: Do not send ICMP Echo Reply
Test Iterations
Derived from RFC 791 s3.2 p27 Discussion (An Example Reassembly Procedure)
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 184
OPEN Alliance
IPv4_REASSEMBLY_11: ICMPv4 Echo Reply (check fragment with Large TTL value)
The initial setting of the timer is a lower bound on the reassembly waiting time. This is
because the waiting time will be increased if the Time to Live in the arriving fragment is
Synopsis
greater than the current timer value. (Note: Here we are assuming that initial timer setting
is 15 seconds)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 185
OPEN Alliance
fragments.
Test Iterations
Notes Derived from RFC 791 s3.2 p27 Discussion (An Example Reassembly Procedure) (MUST)
IPv4_REASSEMBLY_12: ICMPv4 Echo Reply (check fragment with Low TTL value)
The initial setting of the timer is a lower bound on the reassembly waiting time. The
Synopsis
waiting time will not be decreased if it is less the Time to Live in the arriving fragment.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 186
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.2 p27 Discussion (An Example Reassembly Procedure) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 187
OPEN Alliance
In the case that two or more fragments contain the same data either identically or
Synopsis through a partial overlap, this procedure will use the more recently arrived copy in the
data buffer and datagram delivered.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 188
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.2 p29 Discussion (An Example Reassembly Procedure) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 189
OPEN Alliance
End of Option List option indicates the end of the option list. (Note: Here we are
Synopsis
verifying that DUT does not crash on receiving multiple End of Options)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 791 s3.1 p16 Internet Header Format (End of Option List), RFC 791 s3.2
Notes
p31 Options (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 190
OPEN Alliance
No Operation - This option may be used between options, for example, to alignthe
Synopsis beginning of a subsequent option on a 32 bit boundary. (Note: Here we are verifying that
DUT does not crash on receiving multiple No Operation Options)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p17 Internet Header Format (No Operation) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 191
OPEN Alliance
No Operation - This option may be used between options, for example, to alignthe
Synopsis beginning of a subsequent option on a 32 bit boundary. (Note: Here we are verifying that
DUT does not crash on receiving multiple No Operation and End of Options)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p17 Internet Header Format (No Operation) (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 192
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.1 p18 Internet Header Format (Security) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 193
OPEN Alliance
The Overflow (oflw) [4 bits] is the number of IP modules that cannot register
Synopsis
timestamps due to lack of space.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p22 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 194
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.1 p22 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 195
OPEN Alliance
Synopsis 1 -- each timestamp is preceded with internet address of the registering entity.
Test Iterations
Notes Derived from RFC 791 s3.1 p22 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 196
OPEN Alliance
IPv4_OPTIONS_08: ICMPv4 Echo Reply (relation between timestamp & its own
address)
3 -- the internet address fields are prespecified. An IP module only registers its
Synopsis
timestamp if it matches its own address with the next specified internet address.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p22 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 197
OPEN Alliance
IPv4_OPTIONS_09: ICMPv4 Echo Reply (relation between timestamp & its own
address, negative)
3 -- the internet address fields are prespecified. An IP module only registers its
Synopsis
timestamp if it matches its own address with the next specified internet address.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p22 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 198
OPEN Alliance
If there is some room but not enough room for a full timestamp to be inserted the
Synopsis
original datagram is considered to be in error and is discarded.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p23 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 199
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p23 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 200
OPEN Alliance
If there is some room but not enough room for a full timestamp to be inserted, an ICMP
Synopsis
parameter problem message may be sent to the source host.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p23 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 201
OPEN Alliance
If the overflow count itself overflows, an ICMP parameter problem message may be
Synopsis
sent to the source host.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 791 s3.1 p23 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 202
OPEN Alliance
Test Iterations
Notes Derived from RFC 791 s3.1 p23 Internet Header Format (Internet Timestamp) (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 203
OPEN Alliance
4.4.1 General
The scope of this chapter is to specify test cases for the Dynamic IPv4 address Autoconfiguraron
Protocol (IPv4 Autoconfig) based on the following standards:
<TIface-0> <DIface-0>
ECU
DUT
TOPOLOGY-1
This suite expects to be running against any IP enabled network interface which supports acquisitiong of
IP address through the following methods :
IPv4 Link Local Autoconfiguration
DHCP
The following information are obtained from the unused IP network configurations on the TESTER:
IP Address of all the emulated servers
IP Address Pool to be offered by these emulated DHCP Servers
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 204
OPEN Alliance
4.4.4 Coverage
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 205
OPEN Alliance
event will decide whether the DUT has correctly accepted the
packet or not.
Tolerance time associated with an event. When waiting or
listening then this number will be added with the actual wait-
<PARAM_TOLERANCE_TIME> time or listen-time.
This is the maximum time interval for which TESTER waits for a
packet for cases when a certain event has been triggered on the
DUT either by some protocol timer or using some external
<PARAM_LISTEN_TIME> mechanism (script).
<DIface-0> This denotes 1st DUT interface.
This value is equal to the value provided for "IEEE First Unused
<MAC-ADDR1> MAC Address"
This is another value for MAC address which is auto-generated
<MAC-ADDR2> from "IEEE First Unused MAC Address"
<DIFACE_O_MAC_ADDR> This is the MAC address of 1st DUT interface.
<LINK-LOCAL-NET-ADDR> This denotes the Link local network ID i.e. 169.254.0.0
CONSTANT Description
This indicates the value of PROBE_MIN constant specified in
RFC 3927 pg 26, in milliseconds i.e. the value is 1000
PROBE_MIN_IN_MILLISEC milliseconds.
This indicates the value of PROBE_MAX constant specified in
RFC 3927 pg 26, in milliseconds i.e. the value is 2000
PROBE_MAX_IN_MILLISEC milliseconds.
This indicates the value of ANNOUNCE_WAIT constant specified
ANNOUNCE_WAIT in RFC 3927 pg 26, i.e. the value is 2 seconds.
This indicates the value of ANNOUNCE_INTERVAL constant
ANNOUNCE_INTERVAL specified in RFC 3927 pg 26, i.e. the value is 2 seconds.
This indicates the value of ANNOUNCE_INTERVAL constant
specified in RFC 3927 pg 26, in milliseconds i.e. the value is 2000
ANNOUNCE_INTERVAL_IN_MILLISEC milliseconds.
This indicates the value of PROBE_MIN constant specified in RFC
PROBE_MIN_MILLISEC 3927 pg 26, in milliseconds i.e. the value is 1000.
This indicates the value of PROBE_MIN constant specified in RFC
PROBE_MIN_MILLISEC 3927 pg 26, in milliseconds i.e. the value is 1000.
This indicates the value of RATE_LIMIT_INTERVAL constant
RATE_LIMIT_INTERVAL specified in RFC 3927 pg 26, i.e. the value is 60 seconds.
This indicates the value of DEFEND_INTERVAL constant
DEFEND_INTERVAL specified in RFC 3927 pg 26, i.e. the value is 10 seconds.
This indicates the Ethernet Broadcast Address. This value is
ETHERNET_BROADCAST_ADDRESS equal to FF:FF:FF:FF:FF:FF
BROADCAST-IP Broadcast IP address of the network
NULL-MAC-ADDRESS This indicates a MAC address with value 00:00:00:00:00:00
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 206
OPEN Alliance
4.4.6 Tests
4.4.6.1 Introduction
When an operable routable address is available on an interface, the host SHOULD NOT
Synopsys
also assign an IPv4 Link-Local address on that interface.
<ROUTABLE_IP_ADDR_1>
Test Input
<ROUTABLE_IP_ADDR_2>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 207
OPEN Alliance
Test Iterations
If a host finds that an interface that was previously configured with an IPv4 Link-Local
address now has an operable routable address available, the host MUST use the routable
Synopsys
address when initiating new communications, and MUST cease advertising the availability of
the IPv4 Link-Local address.
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <AIFACE-0-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 208
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 209
OPEN Alliance
Test
Iterations
The host SHOULD continue to use the IPv4 Link-Local address for communications already
underway, and MAY continue to accept new communications addressed to the IPv4 Link-
Local address. (Note: In this test case TESTER checks that at that time when DUT is assigning
Synopsys
a routable address on its interface it will continue to use its linklocal address for any
undergoing communications, until the routable address assignment, through DHCP for
example, is complete.)
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <AIFACE-0-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 210
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 211
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 212
OPEN Alliance
Test
Iterations
The host SHOULD continue to use the IPv4 Link-Local address for communications already
underway, and MAY continue to accept new communications addressed to the IPv4 Link-
Local address. (Note: In this test case TESTER checks that at that time when DUT is assigning
Synopsys a routable address on its interface it will continue to use its linklocal address for any
undergoing communications, till the routable address assignment, and also it will accept
new communications addresses to the link local address until the routable address
assignment is complete.)
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <AIFACE-0-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 213
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 214
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 215
OPEN Alliance
Test
Iterations
If a host finds that an interface no longer has an operable routable address available, the
host MAY identify a usable IPv4 Link-Local address and assign that address to the
Synopsys
interface.Ways in which an operable routable address might cease to be available on an
interface include: *Removal of the address from the interface through manual configuration
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 216
OPEN Alliance
Test
Iterations
If a host finds that an interface no longer has an operable routable address available, the
host MAY identify a usable IPv4 Link-Local address and assign that address to the
Synopsys
interface.Ways in which an operable routable address might cease to be available on an
interface include: *Expiration of the lease on the address assigned through DHCP
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <AIFACE-0-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 217
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 218
OPEN Alliance
<DIface-0> containing:
- Source IP Address set to <AIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
19. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <AIFACE-0-IP-LINKLOCAL-ADDR>
20. DUT: Sends ARP Request Message
21. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
7. DUT: Sends DHCPREQUEST Message
Pass Criteria 11. DUT: Sends ARP Probe or ARP Response
14. DUT: Sends ARP Request Message
20. DUT: Sends ARP Request Message
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 219
OPEN Alliance
The first 256 and last 256 addresses in the 169.254/16 prefix are reserved for future use
Synopsys
and MUST NOT be selected by a host using this dynamic configuration mechanism.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 220
OPEN Alliance
Hosts that are equipped with persistent storage MAY, for each interface, record the IPv4
Synopsys address they have selected. On booting, hosts with a previously recorded address SHOULD
use that address as their first candidate when probing.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 221
OPEN Alliance
A host probes to see if an address is already in use by broadcasting an ARP Request for
Synopsys
the desired address. (Note: this is an ARP Probe Request)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 222
OPEN Alliance
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 223
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 224
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 225
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 226
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 227
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 228
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 229
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 230
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 231
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 232
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 233
OPEN Alliance
If during this period, from the beginning of the probing process until ANNOUNCE_WAIT
seconds after the last probe packet is sent, the host receives any ARP packet (Request *or*
Reply) on the interface where the probe is being performed where the packet's 'sender IP
address' is the address being probed for, then the host MUST treat this address as being in
Synopsys
use by some other host, and MUST select a new pseudo-random address and repeat the
process. (Note : Here TESTER is sending a conflicting ARP Response packet with sender IP
address equal to the link-local probed address and verifies that DUT sends another ARP
Probe with a different link-local probe address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 234
OPEN Alliance
Test Iterations
In addition, if during this period the host receives any ARP Probe where the packet's 'target
IP address' is the address being probed for, and the packet's 'sender hardware address' is
Synopsys
not the hardware address of the interface the host is attempting to configure, then the host
MUST similarly treat this as an address conflict and select a new address as above.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 235
OPEN Alliance
Test Iterations
If the number of conflicts exceeds MAX_CONFLICTS then the host MUST limit the rate at
which it probes for new addresses to no more than one new address per
Synopsys RATE_LIMIT_INTERVAL. (Note : Here TESTER checks that if number of conflicts reach
MAX_CONFLICTS(10) then the host should not send any ARP request within
RATE_LIMIT_INTERVAL seconds after the 10th conflict)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 236
OPEN Alliance
<LINK-LOCAL-NET-ADDR>
10. DUT: Sends ARP Request Message
11. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
12. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
13. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
14. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
15. DUT: Sends ARP Request Message
16. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
17. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
18. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
19. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
20. DUT: Sends ARP Request Message
21. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
22. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
23. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
24. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
25. DUT: Sends ARP Request Message
26. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
27. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
28. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 237
OPEN Alliance
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
29. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
30. DUT: Sends ARP Request Message
31. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
32. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
33. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
34. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
35. DUT: Sends ARP Request Message
36. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
37. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
38. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
39. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
40. DUT: Sends ARP Request Message
41. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
42. TESTER: <SERVER-1> retrieves the value of Destination Protocol
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
43. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
44. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
45. DUT: Sends ARP Request Message
46. TESTER: Verify that received ARP Request Message contains:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 238
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 239
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 240
OPEN Alliance
If the number of conflicts exceeds MAX_CONFLICTS then the host MUST limit the rate at
which it probes for new addresses to no more than one new address per
Synopsys RATE_LIMIT_INTERVAL. (Note : Here TESTER checks that if number of conflicts reach
MAX_CONFLICTS(10) then the host should send only 1 ARP request after the
RATE_LIMIT_INTERVAL seconds get over, within the next RATE_LIMIT_INTERVAL seconds)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 241
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 242
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 243
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 244
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 245
OPEN Alliance
If, by ANNOUNCE_WAIT seconds after the transmission of the last ARP Probe no
Synopsys conflicting ARP Reply or ARP Probe has been received, then the host has successfully
claimed the desired IPv4 Link-Local address.
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input
<MAC-ADDR1>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 246
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 247
OPEN Alliance
An ARP announcement is identical to the ARP Probe described above, except that now the
sender and target IP addresses are both set to the host's newly selected IPv4 address. In
this document, the term 'ARP Announcement' is used to refer to an ARP Request packet,
broadcast on the local link, identical to the ARP Probe described above, except that both
Synopsys the sender and target IP address fields contain the IP address being announced. (Note: Here
TESTER checks that after receiving 3 ARP Probes from DUT interface, TESTER receives an
ARP Announcement(Request) packet with Destination MAC address set to Ethernet
Broadcast Address.A tolerance time of -0.05 seconds is used at the step where TESTER is
waiting up to ANNOUNCE_WAIT seconds)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 248
OPEN Alliance
Test Iterations
An ARP announcement is identical to the ARP Probe described above, except that now the
sender and target IP addresses are both set to the host's newly selected IPv4 address. In
this document, the term 'ARP Announcement' is used to refer to an ARP Request packet,
broadcast on the local link, identical to the ARP Probe described above, except that both
Synopsys the sender and target IP address fields contain the IP address being announced. (Note: Here
TESTER checks that after receiving 3 ARP Probes from DUT interface, TESTER receives an
ARP Announcement(Request) packet with Source IP address = Target IP address =
Announced IP address. A tolerance time of -0.05 seconds is used at the step where TESTER
is waiting up to ANNOUNCE_WAIT seconds)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 249
OPEN Alliance
Announcement Message
9. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
10. DUT: Sends ARP Request Message
11. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Sender IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
12. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends 3 ARP Request Messages
10. DUT: Sends ARP Request Message
Pass Criteria
11. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Sender IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
Test Iterations
An ARP announcement is identical to the ARP Probe described above, except that now the
sender and target IP addresses are both set to the host's newly selected IPv4 address. In
this document, the term 'ARP Announcement' is used to refer to an ARP Request packet,
broadcast on the local link, identical to the ARP Probe described above, except that both
Synopsys the sender and target IP address fields contain the IP address being announced. (Note: Here
TESTER checks that after receiving 3 ARP Probes from DUT interface, TESTER receives an
ARP Announcement(Request) packet with Sender Hardware address set to DUT interface
MAC Address. A tolerance time of -0.05 seconds is used at the step where TESTER is waiting
up to ANNOUNCE_WAIT seconds)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 250
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 251
OPEN Alliance
An ARP announcement is identical to the ARP Probe described above, except that now the
sender and target IP addresses are both set to the host's newly selected IPv4 address. In
this document, the term 'ARP Announcement' is used to refer to an ARP Request packet,
broadcast on the local link, identical to the ARP Probe described above, except that both
Synopsys the sender and target IP address fields contain the IP address being announced. (Note: Here
TESTER checks that after receiving 3 ARP Probes from DUT interface, TESTER receives an
ARP Announcement(Request) packet with Target Hardware address set to all zeroes. A
tolerance time of -0.05 seconds is used at the step where TESTER is waiting up to
ANNOUNCE_WAIT seconds)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 252
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 253
OPEN Alliance
Having probed to determine a unique address to use, the host MUST then announce its
claimed address by broadcasting ANNOUNCE_NUM ARP announcements, spaced
Synopsys
ANNOUNCE_INTERVAL seconds apart. (Note : A tolerance time of -0.05 seconds is used at
the step where TESTER is waiting up to ANNOUNCE_WAIT seconds)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 254
OPEN Alliance
Having probed to determine a unique address to use, the host MUST then announce its
claimed address by broadcasting ANNOUNCE_NUM ARP announcements, spaced
ANNOUNCE_INTERVAL seconds apart. (Note : Here TESTER is verifying that the time gap
Synopsys
between the two announce messages is <ANNOUNCE_INTERVAL_IN_MILLISEC>. Tolerance
is 50 milliseconds. A tolerance time of -0.05 seconds is used at the step where TESTER is
waiting up to ANNOUNCE_WAIT seconds).
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 255
OPEN Alliance
Test Iterations
The purpose of these ARP announcements is to make sure that other hosts on the link do
Synopsys not have stale ARP cache entries left over from some other host that may previously have
been using the same address.
<AIFACE-0-IP-LINKLOCAL-ADDR>
<PARAM_PROCESS_TIME>
Test Input
<MAC-ADDR1>
Parameters
<MAC-ADDR2>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 256
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 257
OPEN Alliance
23. TESTER: Verify that received ICMP Echo Reply Message contains:
- Ethernet Destination Hardware Address is set to <MAC-ADDR2>
24. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends ARP Request Message
12. DUT: Sends ARP Request Message
16. DUT: Sends ICMP Echo Reply Message
Pass Criteria 17. TESTER: Verify that received ICMP Echo Reply Message contains:
- Ethernet Destination Hardware Address is set to <MAC-ADDR1>
22. DUT: Sends ICMP Echo Reply Message
23. TESTER: Verify that received ICMP Echo Reply Message contains:
- Ethernet Destination Hardware Address is set to <MAC-ADDR2>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 258
OPEN Alliance
Upon receiving a conflicting ARP packet, a host MAY elect to immediately configure a new
IPv4 Link-Local address. (Note: In this test case, TESTER is sending a conflicting ARP Request
Synopsys
message with source IP Address and target IP Address both set to probed link-local address
sent by the DUT and checks whether DUT sends a probe with a different link local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 259
OPEN Alliance
Test Iterations
If a host currently has active TCP connections or other reasons to prefer to keep the same
IPv4 address, and it has not seen any other conflicting ARP packets within the last
DEFEND_INTERVAL seconds, then it MAY elect to attempt to defend its address by recording
the time that the conflicting ARP packet was received, and then broadcasting one single ARP
Synopsys announcement, giving its own IP and hardware addresses as the sender addresses of the
ARP (Note : Here TESTER sends a conflicting ARP request message with both source and
target IP address set to the probed link local address and checks that the ARP
announcement that DUT has send to defend its address has both the Source IP Address and
Target IP address set to DUT's LinkLocal IP Address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 260
OPEN Alliance
Test Iterations
If a host currently has active TCP connections or other reasons to prefer to keep the same
IPv4 address, and it has not seen any other conflicting ARP packets within the last
DEFEND_INTERVAL seconds, then it MAY elect to attempt to defend its address by recording
the time that the conflicting ARP packet was received, and then broadcasting one single ARP
Synopsys announcement, giving its own IP and hardware addresses as the sender addresses of the
ARP (Note : Here TESTER sends a conflicting ARP Request message with both source and
target IP Address set to the advertised link local address and checks that the ARP
announcement that DUT has send to defend its address has the Sender Hardware Address
set to DUT interface MAC Address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 261
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 262
OPEN Alliance
If a host currently has active TCP connections or other reasons to prefer to keep the same
IPv4 address, and it has not seen any other conflicting ARP packets within the last
DEFEND_INTERVAL seconds, then it MAY elect to attempt to defend its address by recording
the time that the conflicting ARP packet was received, and then broadcasting one single ARP
Synopsys announcement, giving its own IP and hardware addresses as the sender addresses of the
ARP (Note : Here TESTER sends a conflicting ARP Response message with both source and
target IP address set to the advertised link local address and checks that the ARP
announcement that DUT has send to defend its address has both the Source IP Address and
Target IP address set to DUT's LinkLocal IP Address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 263
OPEN Alliance
Test Iterations
If a host currently has active TCP connections or other reasons to prefer to keep the same
IPv4 address, and it has not seen any other conflicting ARP packets within the last
DEFEND_INTERVAL seconds, then it MAY elect to attempt to defend its address by recording
the time that the conflicting ARP packet was received, and then broadcasting one single ARP
Synopsys announcement, giving its own IP and hardware addresses as the sender addresses of the
ARP (Note : Here TESTER sends a conflicting ARP Response packet with both source and
target IP Address set to the advertised link local address and checks that the ARP
announcement that DUT has send to defend its address has the Sender Hardware Address
set to DUT interface MAC Address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 264
OPEN Alliance
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
8. TESTER: Wait till <ANNOUNCE_WAIT+ANNOUNCE_INTERVAL> for DUT to
assign the link-local address to <DIface-0>
9. TESTER: <SERVER-1> Sends ARP Response Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
10. TESTER: Wait till <DEFEND_INTERVAL-PARAM_TOLERANCE_TIME> for DUT to
process the conflicting packet and defend it link-local address at
<DIface-0>
11. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
12. DUT: Sends ARP Request Message
13. TESTER: Verify that received ARP Request Message contains:
- Source Hardware Address is set to <DIFACE-0-MAC-ADDR>
14. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends 3 ARP Request Messages
Pass Criteria 12. DUT: Sends ARP Request Message
13. TESTER: Verify that received ARP Request Message contains:
- Source Hardware Address is set to <DIFACE-0-MAC-ADDR>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 265
OPEN Alliance
If this is not the first conflicting ARP packet the host has seen, and the time recorded for the
previous conflicting ARP packet is recent, within DEFEND_INTERVAL seconds, then the host
MUST immediately cease using this address and configure a new IPv4 Link-Local address.
Synopsys
(Note:In this test case, TESTER sends 2 conflicting ARP Request mesages with both source
and target IP address set to the advertised link local address, within DEFEND_INTERVAL
seconds, and check if DUT probes with a new advertised link local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 266
OPEN Alliance
Test Iterations
If this is not the first conflicting ARP packet the host has seen, and the time recorded for the
previous conflicting ARP packet is recent, within DEFEND_INTERVAL seconds, then the host
MUST immediately cease using this address and configure a new IPv4 Link-Local address.
Synopsys
(Note:In this test case, TESTER sends 2 conflicting ARP Response messages with both source
and target IP address set to the advertised link local address, within DEFEND_INTERVAL
seconds and check if DUT probes with a new advertised link local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 267
OPEN Alliance
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
10. TESTER: Wait till <DEFEND_INTERVAL/2> before sending the next
conflicting packet to <DIface-0>
11. TESTER: <SERVER-1> Sends ARP Response Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
12. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
13. DUT: Sends ARP Request Message
14. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
15. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends 3 ARP Request Messages
Pass Criteria 13. DUT: Sends ARP Request Message
14. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 268
OPEN Alliance
If this is not the first conflicting ARP packet the host has seen, and the time recorded for the
previous conflicting ARP packet is recent, within DEFEND_INTERVAL seconds, then the host
MUST immediately cease using this address and configure a new IPv4 Link-Local address.
Synopsys
(Note:In this test case, TESTER first sends 1 conflicting ARP Request mesages and then sends
1 conflicting ARP Response message, within DEFEND_INTERVAL seconds, and check if DUT
probes with a new advertised link local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 269
OPEN Alliance
Test Iterations
If this is not the first conflicting ARP packet the host has seen, and the time recorded for the
previous conflicting ARP packet is recent, within DEFEND_INTERVAL seconds, then the host
MUST immediately cease using this address and configure a new IPv4 Link-Local address.
Synopsys
(Note:In this test case, TESTER first sends 1 conflicting ARP Response message and then
sends 1 conflicting ARP request message, within DEFEND_INTERVAL seconds and check if
DUT probes with a new advertised link local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 270
OPEN Alliance
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
10. TESTER: Wait till <DEFEND_INTERVAL/2> before sending the next
conflicting packet to <DIface-0>
11. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
12. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Expected Network Address of Target IP Address set to
<LINK-LOCAL-NET-ADDR>
13. DUT: Sends ARP Request Message
14. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
15. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends 3 ARP Request Messages
Pass Criteria 13. DUT: Sends ARP Request Message
14. TESTER: Verify that received ARP Request Message contains:
- Target IP Address is not set to <DIFACE-0-IP-LINKLOCAL-ADDR>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 271
OPEN Alliance
Upon receiving a conflicting ARP packet, a host MAY elect to immediately configure a new
IPv4 Link-Local address. (Note: In this test case, TESTER is sending a conflicting ARP
Synopsys Response message with source IP Address and target IP Address both set to probed link-
local address sent by the DUT and checks whether DUT sends a probe with a different link
local address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 272
OPEN Alliance
Test Iterations
All ARP packets (*replies* as well as requests ) that contain a Link- Local 'sender IP address'
MUST be sent using link-layer broadcast instead of link-layer unicast. (Note:Here TESTER
Synopsys
checks that DUT sends ARP Probe Response with Ethernet destination address set to
broadcast address)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 273
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 274
OPEN Alliance
All ARP packets (*replies* as well as requests) that contain a Link- Local 'sender IP address'
MUST be sent using link-layer broadcast instead of link-layer unicast. (Note:Here TESTER
Synopsys
checks that DUT sends ARP Requests with Ethernet destination address set to broadcast
address)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 275
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 276
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 277
OPEN Alliance
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 278
OPEN Alliance
Address field of ARP Request Message received from <DIface-0> and stores
it in <DIFACE-0-IP-LINKLOCAL-ADDR>
8. TESTER: Wait till <(PROBE_MAX*2)+ANNOUNCE_WAIT+ANNOUNCE_INTERVAL>
for DUT to assign the link-local address to <DIface-0>
9. DUT CONFIGURE: Configure DUT to add a static route with
- Destination Prefix set to <AIFACE-0-IP-LINKLOCAL-ADDR>
- Netmask set to HOST_MASK
- Outgoing interface set to DUT_IFACE_0
- Gateway address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
10. DUT CONFIGURE: Configure DUT to send an ICMP Echo Request Message from
<DIface-0> with
- Destination IP Address set to <AIFACE-0-IP-LINKLOCAL-ADDR>
11. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
12. DUT: Sends ICMP Echo Request Message
13. TESTER: Verify that received ICMP Echo Request Message contains:
- Source IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address is set to
<AIFACE-0-IP-LINKLOCAL-ADDR>
14. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends ARP Request Message
12. DUT: Sends ICMP Echo Request Message
Pass Criteria 13. TESTER: Verify that received ICMP Echo Request Message contains:
- Source IP Address is set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address is set to
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 279
OPEN Alliance
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input
<MAC-ADDR1>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 280
OPEN Alliance
Test
Iterations
If for any reason the host chooses to send the packet with an IPv4 Link-Local source address
(e.g., no routable address is available on the selected interface), then it MUST ARP for the
destination address and then send its packet, with an IPv4 Link-Local source address and a
Synopsys
routable destination IPv4 address, directly to its destination on the same physical link. (Note
: Here TESTER checks that DUT sends an ICMP echo request with source IP address as its
own linklocal IP Address)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 281
OPEN Alliance
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 282
OPEN Alliance
If for any reason the host chooses to send the packet with an IPv4 Link-Local source address
(e.g., no routable address is available on the selected interface), then it MUST ARP for the
destination address and then send its packet, with an IPv4 Link-Local source address and a
Synopsys
routable destination IPv4 address, directly to its destination on the same physical link. (Note
: Here TESTER checks that DUT sends an ICMP echo request with destination IP address as
the routable address its trying to ping)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 283
OPEN Alliance
Test
Iterations
If for any reason the host chooses to send the packet with an IPv4 Link-Local source address
(e.g., no routable address is available on the selected interface), then it MUST ARP for the
destination address and then send its packet, with an IPv4 Link-Local source address and a
Synopsys
routable destination IPv4 address, directly to its destination on the same physical link. (Note
: Here TESTER checks that DUT sends an ICMP echo request with ethernet destination
address set to TESTER interface mac address))
<ROUTABLE_IP_ADDR_1>
Test Input
<MAC-ADDR1>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 284
OPEN Alliance
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 285
OPEN Alliance
If the destination address is a unicast address outside the 169.254/16 prefix, then the host
SHOULD use an appropriate routable IPv4 source address, if it can. (Note : Here TESTER
Synopsys
checks that DUT sends an ICMP echo request with source IP address set to routable
address)
<ROUTABLE_IP_ADDR_1>
Test Input
<ROUTABLE_IP_ADDR_2>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 286
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 287
OPEN Alliance
The host MUST NOT send a packet with an IPv4 Link-Local destination address to any router
for forwarding. (Note : Here TESTER sends a ping with destination IP address set to an
Synopsys
arbitrary link-local address and checks that DUT should not send the ping to a router after
consulting the static route entry in its routing table)
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <ARBITRARY-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 288
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 289
OPEN Alliance
A sensible default for applications which are sending from an IPv4 Link-Local address is to
Synopsys
explicitly set the IPv4 TTL to 1.
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input
<MAC-ADDR1>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 290
OPEN Alliance
Test Iterations
An IPv4 packet whose source and/or destination address is in the 169.254/16 prefix MUST
NOT be sent to any router for forwarding. (Note : Here TESTER sends a ping with destination
Synopsys
IP address set to DUT interface link-local address and checks that DUT should not send a ping
reply after consulting the static route entry in its routing table)
<ROUTABLE_IP_ADDR_1>
Test Input
<ARBITRARY-IP-LINKLOCAL-ADDR>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 291
OPEN Alliance
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 292
OPEN Alliance
A router may of course answer ARP Requests for one or more IPv4 Link-Local address(es)
that it has legitimately claimed for its own use according to the claim-and-defend protocol
Synopsys
described in this document. (Note : Here TESTER checks that the router/host must answer to
the ARP request for the Link-local address it is using)
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input
<MAC-ADDR1>
Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 293
OPEN Alliance
Test
Iterations
A router or other host MUST NOT indiscriminately answer all ARP Requests for addresses in
the 169.254/16 prefix. A router may of course answer ARP Requests for one or more IPv4
Link-Local address(es) that it has legitimately claimed for its own use according to the claim-
Synopsys
and-defend protocol described in this document. (Note : Here TESTER checks that the
router/host will not answer to the ARP request for an arbitrary link-local address which it is
not using)
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input <ARBITRARY-IP-LINKLOCAL-ADDR>
Parameters <MAC-ADDR1>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 294
OPEN Alliance
Test
Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 295
OPEN Alliance
When a host acquires a routable address, it does not need to retain its Link-Local address
Synopsys for the purpose of communicating with other devices on the link that are themselves using
only Link-Local addresses:
<ROUTABLE_IP_ADDR_1>
Test Input <ROUTABLE_IP_ADDR_2>
Parameters <AIFACE-0-IP-LINKLOCAL-ADDR>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 296
OPEN Alliance
containing:
- Source IP Address set to <ROUTABLE_IP_ADDR_1>
- 'yiaddr' field set to <ROUTABLE_IP_ADDR_2>
- Message Option containing:
- Type field set to DHCP_IP_ADDRESS_LEASE_TIME
- Length field set to 4
- Value set to <PARAM_LISTEN_TIME*3>
17. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
18. DUT: Sends DHCPREQUEST Message
19. TESTER: <SERVER-1> Sends DHCPACK Message to DUT through <DIface-0>
containing:
- Source IP Address set to <ROUTABLE_IP_ADDR_1>
- 'yiaddr' field set to <ROUTABLE_IP_ADDR_2>
- Message Option containing:
- Type field set to DHCP_IP_ADDRESS_LEASE_TIME
- Length field set to 4
- Value set to <PARAM_LISTEN_TIME*3>
20. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <ROUTABLE_IP_ADDR_1>
- Destination IP Address set to <ROUTABLE_IP_ADDR_2>
21. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0> for ARP response
message
22. DUT: Sends ARP Response
- Destination IP Address set to <ROUTABLE_IP_ADDR_1>
23. TESTER: <SERVER-1> Sends ARP Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <AIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Target Hardware Address set to <NULL-MAC-ADDRESS>
- Ethernet Destination Hardware Address set to
ETHERNET_BROADCAST_ADDR
24. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Source IP Address set to <DIFACE-0-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <AIFACE-0-IP-LINKLOCAL-ADDR>
25. DUT: Does not send ARP Response Message
26. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
6. DUT: Sends ARP Probe Request Message
11. DUT: Sends ARP Response Message
Pass Criteria 15. DUT: Sends DHCPDISCOVER Message
18. DUT: Sends DHCPREQUEST Message
22. DUT: Sends ARP Response
25. DUT: Does not send ARP Response Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 297
OPEN Alliance
Test Iterations
It is not necessary for that host to have a Link-Local source address in order to send to a
Synopsys
Link-Local destination address
<ROUTABLE_IP_ADDR_1>
<ROUTABLE_IP_ADDR_2>
Test Input
<ARBITRARY-IP-LINKLOCAL-ADDR>
Parameters
<MAC-ADDR1>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 298
OPEN Alliance
<DIface-0> containing:
- Source IP Address set to <ROUTABLE_IP_ADDR_1>
- Destination IP Address set to <ROUTABLE_IP_ADDR_2>
10. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0> for ARP
response message
11. DUT: Sends ARP Response
- Destination IP Address set to <ROUTABLE_IP_ADDR_1>
12. DUT CONFIGURE: Configure DUT to add a static route with
- Destination Prefix set to <ARBITRARY-IP-LINKLOCAL-ADDR>
- Netmask set to HOST_MASK
- Outgoing interface set to DUT_IFACE_0
- Gateway address set to <ROUTABLE_IP_ADDR_2>
13. TESTER: <SERVER-1> Sends ICMP Echo Request Message to DUT through
<DIface-0> containing:
- Source IP Address set to <ARBITRARY-IP-LINKLOCAL-ADDR>
- Destination IP Address set to <ROUTABLE_IP_ADDR_2>
- Ethernet Destination Hardware Address set to
<DIFACE-0-MAC-ADDR>
- Ethernet Source Hardware Address set to <MAC-ADDR1>
14. TESTER: <SERVER-1> Listens (up to <ParamListenTime>) on <DIface-0>
- Source IP Address set to <ROUTABLE_IP_ADDR_2>
- Destination IP Address set to <ARBITRARY-IP-LINKLOCAL-ADDR>
15. DUT: Sends ICMP Echo Reply Message
16. CLEANUP: Configure DUT to delete a static route on <DIface-0> with
- Destination Prefix set to <ARBITRARY-IP-LINKLOCAL-ADDR>
- Netmask set to HOST_MASK
- Outgoing interface set to DUT_IFACE_0
- Gateway address set to <ROUTABLE_IP_ADDR_2>
17. CLEANUP: Externally cause DUT to shutdown <DIface-0>
4. DUT: Sends DHCPDISCOVER Message
7. DUT: Sends DHCPREQUEST Message
Pass Criteria
11. DUT: Sends ARP Response
15. DUT: Sends ICMP Echo Reply Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 299
OPEN Alliance
Synopsys Hosts SHOULD NOT send periodic gratuitous ARPs (Note: for Link-Local Addresses).
<AIFACE-0-IP-LINKLOCAL-ADDR>
Test Input Parameters
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 300
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 301
OPEN Alliance
4.5.1 General
The scope of this chapter is to specify test cases for the User Datagram Protocol (UDP) from the
following standards:
<TIface-0> <DIface-0>
ECU
Control channel for the
stub
HOST-1 DUT
TOPOLOGY-1
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 302
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 303
OPEN Alliance
4.5.5 Tests
Ensure that
when the DUT is requested to generate a UDP packet,
then the DUT generates a UDP Packet
containing a well-formed Header
Synopsis containing a Source Port field
containing a Total Length
containing a Destination Port
containing a Length field
containing a Checksum field
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 304
OPEN Alliance
Notes
Ensure that
when the DUT receives a UDP packet
containing a well-formed Header
containing a Source Port field
containing a Destination Port
Synopsis indicating a value equal to the DUT’s UDP port
containing a Length field
indicating a valid value equal to the size of the sent datagram
containing a Checksum field
indicating a value equal to the <calculatedUDPChecksum> by the DUT
then the DUT accepts the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet containing a well-formed UDP Header
2. DUT: Sends <Indication> containing the same content of the UDP packet received.
Pass Criteria The DUT accepts the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 305
OPEN Alliance
UDP_PortHandling_01: To verify that the DUT accepts the datagram in case UDP
Header has a non-zero source port.
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Source Port Field
indicating a value different from zero
then the DUT accepts the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with a non-zero Source Port field.
2. DUT: Sends <Indication> containing the same content of the UDP packet received.
Pass Criteria The DUT accepts the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 306
OPEN Alliance
UDP_PortHandling_02: To verify that the DUT accepts the datagram in case UDP
Header has a source port with a value equal to zero.
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Source Port Field
indicating a value equal to zero
then the DUT accepts the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with a Source Port field equal to zero.
2. DUT: Sends <Indication> containing the same content of the UDP packet received.
Pass Criteria The DUT accepts the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 307
OPEN Alliance
UDP_PortHandling_03: To verify that the DUT accepts the datagram in case UDP
Header has a specific source port value.
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Source Field
indicating an acceptable specific value
then the DUT accepts the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with a specific Source Port field value.
2. DUT: Sends <Indication> containing the same content of the UDP packet received.
Pass Criteria The DUT accepts the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 308
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Source Field
indicating a value different from the <rangeOfAcceptablePorts>
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with a valid Source Port field.
2. DUT: Discards the UDP packet.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 309
OPEN Alliance
Ensure that
Synopsis when the DUT receives a truncated UDP packet
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 310
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value less than 8
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length greater than or equal to 8.
2. DUT: Discards the UDP packet and sends no <Indication>.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 311
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value greater than or equal to 8
then the DUT accepts the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length greater than or equal to 8.
2. DUT: Sends <Indication> containing the same content of the UDP packet received.
Pass Criteria The DUT accepts the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 312
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value equal to 0
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length equal to zero.
2. DUT: Discards UDP packet and sends no <Indication>.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 313
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value greater than the size of the packet
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length greater than the packet size.
2. DUT: Discards the UDP packet and sends no <Indication>.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 314
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value less than the size of the packet
then the DUT discards the UDP packet.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length field less than the size of the packet.
2. DUT: Discards the UDP packet and sends no <Indication>.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 315
OPEN Alliance
Ensure that
when the DUT receives a UDP packet
containing a UDP Header
Synopsis
containing a Length field
indicating a value equal to the maximum size
then the DUT discards the UDP packet and sends no <Indication>.
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a UDP packet with Length field set to maximum size.
2. DUT: discards the UDP packet.
Pass Criteria The DUT discards the UDP packet.
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 316
OPEN Alliance
UDP_Padding_01: To verify that IUT generates UDP datagram with odd size of
payload and adds padding at the end.
Ensure that
when the DUT is requested to generate a UDP packet with an odd <udpUserDataSize>
Synopsis then the DUT generates a UDP packet
containing Data
indicating value of the received odd payload size plus padding bytes
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 317
OPEN Alliance
UDP_Padding_02: To verify that IUT generates UDP datagram with even size of
payload and no padding at the end.
Ensure that
when the DUT is requested to generate a UDP packet with an even payload size
Synopsis then the DUT generates a UDP packet
containing Data
indicating value of the received even <udpUserDataSize> with no padding bytes
Prerequisites None
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 318
OPEN Alliance
Source Port is an optional field, when meaningful, it indicates the port of the sending
process, and may be assumed to be the port to which a reply should be addressed in the
Synopsys
absence of any other information. A user interface should allow the creation of new receive
ports [Note: In this test, we verify that application can specify source port]
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Externally cause DUT to send a UDP Message with source port
set to <unusedUDPDstPort1> through <DIface-0>
Test
2. TESTER: <HOST-1> Listens (up to<ParamListenTime>) on <DIface-0>
Procedure 3. DUT: Sends Message
4. TESTER: Verify that received UDP Message contains:
- Source UDP Port field is set to <unusedUDPDstPort1>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received UDP Message contains:
- Source UDP Port field is set to <unusedUDPDstPort1>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 319
OPEN Alliance
Source Port is an optional field, when meaningful, it indicates the port of the sending
process, and may be assumed to be the port to which a reply should be addressed in the
Synopsys
absence of any other information. [Note: In this test, we verify that DUT will respond
back(if required) to source port of received message]
<unusedUDPSrcPort>
Test Input
<UDPDefaultData>
Parameters
Check section general Input Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 320
OPEN Alliance
Source Port is an optional field, when meaningful, it indicates the port of the sending
process, and may be assumed to be the port to which a reply should be addressed in the
Synopsys absence of any other information. If not used, a value of zero is inserted. [Note: In this test,
we verify that using the value 0 for UDP Source Port is valid and DUT accepts such a
Message]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 321
OPEN Alliance
Destination Port has a meaning within the context of a particular internet destination
Synopsys address. [Note: In this test, we verify that DUT can send UDP message at same destination
port to more than one differrent IP addresses.]
<testerUDPPort>
Test Input <Host-1-IP>
Parameters <Host-2-IP>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 322
OPEN Alliance
UDP_FIELDS_05: Fields - Same Port with Different IP Address (receive and send)
Destination Port has a meaning within the context of a particular internet destination
Synopsys address. [Note: In this test, we verify that DUT can receive send UDP message at same
destination port to more than one differrent IP addresses.]
<UDPDefaultData>
<UDPData>
Test Input
<Host-1-IP>
Parameters
<Host-2-IP>
Check section general Input Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 323
OPEN Alliance
Test Iterations
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: In this test, we configure DUT to send <udpUserDataSize> size of data so that the
length in Header is (<udpUserDataSize > + 8(UDP Header Size)) bytes]
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 324
OPEN Alliance
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: In this test, we configure DUT to send 0 (zero) size of data so that the length in
Header is 8(UDP Header Size)) bytes]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 325
OPEN Alliance
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: Check that the DUT discards the received datagram in case the total length of the
datagram is less than 8 bytes]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 326
OPEN Alliance
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: Check that the DUT discards the received datagram in case the total length of the
datagram is zero (‘0’)]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 327
OPEN Alliance
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: Check that the DUT discards the received datagram in case the length value in the
header is greater than the actual length of the datagram]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 328
OPEN Alliance
Length is the length in octets of this user datagram including this header and the data.
Synopsys [Note: Check that the DUT accepts the received datagram in case the length value in the
header is set to the maximum value]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 329
OPEN Alliance
Checksum is the 16-bit one's complement of the one's complement sum of a pseudo header
of information from the IP header, the UDP header, and the data, padded with zero octets
Synopsys at the end (if necessary) to make a multiple of two octets. [Note: In this test, we verify that
DUT calculates UDP checksum correctly. While calculating UDP checksum the padded byte
is needed to be considered.]
<udpUserDataSize>
Test Input
<calculatedUDPChecksum>
Parameters
Check section general Input Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 330
OPEN Alliance
Checksum is the 16-bit one's complement of the one's complement sum of a pseudo header
of information from the IP header, the UDP header, and the data, padded with zero octets
Synopsys at the end (if necessary) to make a multiple of two octets. [Note: In this test, we verify that
DUT calculates UDP checksum correctly. While calculating UDP checksum the padded byte
is not required.]
1. TESTER: Externally cause DUT to send UDP Message with 100 of data
through <DIface-0>
Test
2. TESTER: <HOST-1> Listens (up to<ParamListenTime>) on <DIface-0>
Procedure 3. DUT: Sends Message
4. TESTER: Verify that received UDP Message contains:
- UDP Header Checksum field is set to <calculatedUDPChecksum>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received UDP Message contains:
- UDP Header Checksum field is set to <calculatedUDPChecksum>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 331
OPEN Alliance
If a UDP datagram is received with a checksum that is non-zero and invalid, UDP MUST
Synopsys silently discard the datagram. [Note: In this test, we verify that DUT will not accept UDP
message with incorrect checksum]
<incorrectUDPChecksum>
Test Input
<UDPDefaultData>
Parameters
Check section general Input Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.4 Page 78 'UDP Checksums' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 332
OPEN Alliance
An all zero transmitted checksum value means that the transmitter generated no checksum
(for debugging or for higher level protocols that don't care). An application MAY optionally
Synopsys be able to control whether a UDP checksum will be generated, but it MUST default to
checksumming on. [Note: In this test, we verify that DUT accepts UDP datagram with zero
checksum]
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 333
OPEN Alliance
An all zero transmitted checksum value means that the transmitter generated no checksum
(for debugging or for higher level protocols that don't care). An application MAY optionally
Synopsys be able to control whether a UDP checksum will be generated, but it MUST default to
checksumming on. [Note: In this test, we verify that application on DUT can generate UDP
datagram with no-checksum]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 334
OPEN Alliance
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.4 Page 78 'UDP Checksums' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 335
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that user
interface allows creation of new receive ports. This test is only ran when
<DUTSupportsDynamicInterface> is TRUE]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 336
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that receive
operations on the receive ports return the data octets correctly. This test is only ran when
<DUTSupportsDynamicInterface> is TRUE]
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 337
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that receive
operations on the receive ports return the source port correctly. This test is only ran when
<DUTSupportsDynamicInterface> is TRUE]
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 338
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that receive
operations on the receive ports return the source address correctly. This test is only ran
when <DUTSupportsDynamicInterface> is TRUE]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 339
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that an
operation that allows a datagram to be sent, specifies the source port to be sent. This test is
only ran when <DUTSupportsDynamicInterface> is TRUE]
1. TESTER: Externally cause DUT to send a UDP Message with source port
set to <unusedUDPSrcPort> through <DIface-0>
Test
2. TESTER: <HOST-1> Listens (up to<ParamListenTime>) on <DIface-0>
Procedure 3. DUT: Sends Message
4. TESTER: Verify that received UDP Message contains:
- Source UDP Port field is set to <unusedUDPSrcPort>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received UDP Message contains:
- Source UDP Port field is set to <unusedUDPSrcPort>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 340
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that an
operation that allows a datagram to be sent, specifies the destination port to be sent. This
test is only ran when <DUTSupportsDynamicInterface> is TRUE]
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 341
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that an
operation that allows a datagram to be sent, specifies the source address to be sent. This
test is only ran when <DUTSupportsDynamicInterface> is TRUE]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 342
OPEN Alliance
A user interface should allow the creation of new receive ports, receive operations on the
receive ports that return the data octets and an indication of source port and source
address, and an operation that allows a datagram to be sent, specifying the data, source
Synopsys
and destination ports and addresses to be sent. [Note: In this test, we verify that an
operation that allows a datagram to be sent, specifies the destination address to be sent.
This test is only ran when <DUTSupportsDynamicInterface> is TRUE]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 343
OPEN Alliance
4.5.5.7 IP Interface
One possible UDP/IP interface would return the whole internet datagram including all of
the internet header in response to a receive operation. Such an interface would also allow
the UDP to pass a full internet datagram complete with header to the IP to send. The IP
Synopsys
would verify certain fields for consistency and compute the internet header checksum.
[Note: In this test we verify that application is notified about TTL value of received UDP
message]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 344
OPEN Alliance
4.5.5.8 Introduction
UDP is used by applications that do not require the level of service of TCP or that wish to
use communications services (e.g., multicast or broadcast delivery) not available from TCP.
Synopsys
[Note: In this test we verify that DUT will accept UDP message with broadcast destination
Address.]
Test Iterations
Notes Derived from RFC 1122 Section 4.1.1 Page 77 'Introduction' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 345
OPEN Alliance
UDP is used by applications that do not require the level of service of TCP or that wish to
use communications services (e.g., multicast or broadcast delivery) not available from TCP.
Synopsys
[Note: In this test we verify that DUT will accept UDP message with multicast destination
Address.]
Test Iterations
Notes Derived from RFC 1122 Section 4.1.1 Page 77 'Introduction' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 346
OPEN Alliance
If a datagram arrives addressed to a UDP port for which there is no pending LISTEN call,
Synopsys
UDP SHOULD send an ICMP Port Unreachable message.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.1 Page 77 'Ports' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 347
OPEN Alliance
4.5.5.9 IP Option
UDP MUST pass any IP option that it receives from the IP layer transparently to the
Synopsys
application layer. [Note: In this test, we verify 'Time Stamp' IP Option ]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.2 Page 77 'IP Option' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 348
OPEN Alliance
An application MUST be able to specify IP options to be sent in its UDP datagrams, and
Synopsys UDP MUST pass these options to the IP layer. [Note: In this test, we verify 'Time Stamp' IP
Option ]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.2 Page 77 'IP Option' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 349
OPEN Alliance
An application program MUST be able to specify the IP source address to be used for
sending a UDP datagram or to leave it unspecified (in which case the networking software
Synopsys
will choose an appropriate source address). [Note: In this test, we verify that the
networking software has chosen an an appropriate source address.]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.5 Page 79 'UDP Multihoming' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 350
OPEN Alliance
A request/response application that uses UDP should use a source address for the
Synopsys
response that is the same as the specific destination address of the request.
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.5 Page 79 'UDP Multihoming' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 351
OPEN Alliance
A UDP datagram received with an invalid IP source address (e.g., a broadcast or multicast
Synopsys address) must be discarded by UDP or by the IP layer (see Section 3.2.1.3). [Note: In this
test, we verify UDP Message with multicast address as source address. ]
<UDPDefaultData>
Test Input
<allSystemMCastAddr>
Parameters
Check section general Input Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.6 Page 79 'Invalid Addresses' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 352
OPEN Alliance
A UDP datagram received with an invalid IP source address (e.g., a broadcast or multicast
Synopsys address) must be discarded by UDP or by the IP layer (see Section 3.2.1.3). [Note: In this
test, we verify UDP Message with broadcast address as source address. ]
<UDPDefaultData>
Test Input
<AIface-0-BcastIP>
Parameters
Check section general Input Parameters
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.6 Page 79 'Invalid Addresses' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 353
OPEN Alliance
An application-layer program MUST be able to set the TTL and TOS values as well as IP
options for sending a UDP datagram, and these values must be passed transparently to the
Synopsys
IP layer. [Note: In this test, we verify that UDP-application on DUT can specify TTL value for
IP header.]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 Section 4.1.4 Page 79 'UDP/APPLICATION LAYER INTERFACE'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 354
OPEN Alliance
An application-layer program MUST be able to set the TTL and TOS values as well as IP
options for sending a UDP datagram, and these values must be passed transparently to the
Synopsys
IP layer. [Note: In this test, we verify that UDP-application on DUT can specify TOS value for
IP header.]
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 Section 4.1.4 Page 79 'UDP/APPLICATION LAYER INTERFACE'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 355
OPEN Alliance
UDP MUST pass to the application layer all ICMP error messages that it receives from
Synopsys
the IP layer.
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.3 Page 78 'ICMP Messages' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 356
OPEN Alliance
4.6.1 General
The scope of this chapter is to specify test cases for Dynamic Host configuration Protocol Version 4
(DHCPv4) from the following standards:
Though the focus of conformance testing has been limited to the above mentioned specification
document we have relied heavily upon the following document as specification for DHCP Message
Options:
RFC 2132 - DHCP Options and BOOTP Vendor Extensions
The number of DUT interfaces required by the topologies described below are as follows:
In each test, TESTER simulates a portion of exactly one of the 6 topologies shown below. Each node
shown in a topology is represented with a unique identifier. The test methods follow the same
representation of these nodes.
TOPOLOGY-1
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 357
OPEN Alliance
N0 N0
<TIface-0> <DIface-0>
ECU
<CLIENT-1>
TOPOLOGY-1
TOPOLOGY-2
<TIface-0>
<TIface-0>
N0
N0
<DIface-0>
<CLIENT-1>
ECU
<DIface-1>
N1
<TIface-1>
N1
N1
<CLIENT-2>
TOPOLOGY-2
TOPOLOGY-3
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 358
OPEN Alliance
These two clients are connected to the same DUT interface <DIface-0> through an emulated
broadcast device (e.g., HUB. See above)
<TIface-0>
<TIface-0>
N0
N0
<CLIENT-1>
HUB <DIface-0> ECU
<TIface-0>
N0
N1
<CLIENT-2>
TOPOLOGY-3
TOPOLOGY-4
These three clients are connected to the same DUT interface <DIface-0> through an emulated
broadcast device (e.g., HUB. See above)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 359
OPEN Alliance
<CLIENT-1> N0
<TIface-0>
<CLIENT-3>
<TIface-0> N0
TOPOLOGY-4
TOPOLOGY-5
<RELAY-AGENT-1> <DIface-0>
N0
N0 ECU
N1
<CLIENT-1> N1
<TIface-0> TOPOLOGY-5
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 360
OPEN Alliance
The tests specified in this document expects to be running against a DHCP Server implementation.
Most of the tests can be run against a single interface, only a few tests require that the machine TESTER
is running on be connected to 2 interfaces that are connected to the DUT.
Though in all the tests TESTER will be emulating one or more DHCP Client(s), IP TESTER Address will be
used in special cases where TESTER needs to emulate a client with static IP Address and when DHCP
Relay Agent is emulated to be running between the emulated client(s) and the DHCP Server running on
the DUT.
4.6.4 Coverage
Section No. Test Category Test Number(s)
Introduction, Design Goals DHCPv4_SERVER_SUMMARY_01 to
1, 1.6, 2, 2.2 and Protocol Summary DHCPv4_SERVER_SUMMARY_09
DHCPv4_SERVER_PROTOCOL_01 to
3 The Client-Server Protocol DHCPv4_SERVER_PROTOCOL_04
Client-server interaction -
allocating a network DHCPv4_SERVER_ALLOCATING_01 to
3.1 address DHCPv4_SERVER_ALLOCATING_05
Client-server interaction -
reusing a previously DHCPv4_SERVER_REUSING_01 to
3.2 allocated network address DHCPv4_SERVER_REUSING_04
DHCPv4_SERVER_PARAMETERS_01 to
3.3, 3.4, 3.5 Client parameters in DHCP DHCPv4_SERVER_PARAMETERS_07
Constructing and sending DHCPv4_SERVER_CONSTRUCTING_MESSAGES_01
4.1 DHCP messages to DHCPv4_SERVER_CONSTRUCTING_MESSAGES_18
DHCP server administrative DHCPv4_SERVER_ADMINISTRATIVE_01 to
4.2 controls DHCPv4_SERVER_ADMINISTRATIVE_02
DHCPv4_SERVER_DISCOVER_01 to
4.3.1 DHCPDISCOVER message DHCPv4_SERVER_DISCOVER_13
DHCPv4_SERVER_REQUEST_01 to
4.3.2 DHCPREQUEST message DHCPv4_SERVER_REQUEST_04
4.3.3 DHCPDECLINE message DHCPv4_SERVER_DECLINE_01
DHCPv4_SERVER_RELEASE_01,
4.3.4 DHCPRELEASE message DHCPv4_SERVER_RELEASE_02
DHCPv4_SERVER_INFORM_01 to
4.3.5 DHCPINFORM message DHCPv4_SERVER_INFORM_03
TOTAL 74
(Negative) 8
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 361
OPEN Alliance
<DHCP-MAGIC-COOKIE> The first 4 octets of DHCP Options which represent the value 99,
130, 83 and 99 respectively. [Ref: RFC2131 Section 3 Page 13 ]
The all 1 Layer 2 broadcast address to which if any packet is
sent, all the nodes within the physical LAN ( and logical LAN is
<LINK-LAYER-BROADCAST-ADDRESS>
policy permits) will receive the packet. [Ref: RFC2131 Section
4.4.3 Page 39 ]
Value of DHCP IP Address Lease Time in seconds which will be
configured on the DUT so that the DHCP Server running on the
DUT offers to TESTER (DHCP Client) that particular value and not
default values (which can be in the order of days). It is advised
<ParamLeaseTime> that a too small value (less than 10 seconds) can create some
critical timeout related issues possibly leading to undesirable
test results since other timers like T1 (Renewal Time) and T2
(Rebinding Time) are based on this entries. [Default : 15 seconds
]
The amount of tolerance to be provided so that we do not miss
DUT packets. Increasing the value of this entry too much will
<ParamToleranceTime> mean adding too much tolerance to DUT behaviour which can
mean more tests passing but actually with not sufficient
conformance with the specification. [Default : 1 second ]
The amount of time TESTER will usually wait for the DUT to
process some PDU sent by TESTER before continuing with the
test. The purpose of this entry also is to provide some amount of
<ParamProcessTime>
latency consideration for the DUT so that the DUT gets ample
time to process some PDU and take action in accordance to that.
[Default : 2 seconds ]
When we listen for a packet from the DUT either as response to
a packet we have senht or when the specification does not
<ParamListenTime>
define any specific time to listen for, this entry is used. [Default:
10 seconds ]
<TAIface-n-IP-ADDRESS> IP Address of the 'n'th TESTER interface connected to DUT
<DIface-n-IP-ADDRESS> IP Address of the 'n'th DUT interface connected to TESTER
<CLIENTn-IP-ADDRESS> IP Address acquired by the 'n'th emulated client using DHCP
Renewal Time (T1) of the 'n'th emulated Client which has
obtained lease for 'x' seconds from DUT. If the DUT sent a
<CLIENTn-RENEWAL-TIME>
particular value in Renewal Time Value Option then that value is
used oherwise it is calculated as (0.5 * 'x') seconds.
Rebinding Time (T2) of the 'n'th emulated Client which has
obtained lease for 'x' seconds from DUT. If the DUT sent a
<CLIENTn-REBINDING-TIME>
particular value in Rebinding Time Value Option then that value
is used oherwise it is calculated as (0.875 * 'x') seconds.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 362
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 363
OPEN Alliance
4.6.6 Tests
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 364
OPEN Alliance
4.6.6.1 Summary
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
Test Procedure
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
Pass Criteria 6. DUT: Sends DHCPOFFER Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 365
OPEN Alliance
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains all of the
following:
- 'yiaddr' field is greater than or equal to
<DUT-SERVER-0-IP-POOL-START>
- 'yiaddr' field is less than or equal to
<DUT-SERVER-0-IP-POOL-END>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains all of the
following:
Pass Criteria - 'yiaddr' field is greater than or equal to
<DUT-SERVER-0-IP-POOL-START>
- 'yiaddr' field is less than or equal to
<DUT-SERVER-0-IP-POOL-END>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 366
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 367
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
Test Procedure for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
7. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is less than or equal to extractedYiaddr
7. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- 'yiaddr' field is less than or equal to extractedYiaddr
Test Iterations
Notes Derived from RFC 2131 Section 1.6 Page 7 'Design Goals' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 368
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. DUT CONFIGURE: Restart the DHCP Server running on DUT
causing it to listen on 1 interface(s)
7. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
8. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
8. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- 'yiaddr' field is set to extractedYiaddr
Test Iterations
Notes Derived from RFC 2131 Section 1.6 Page 7 'Design Goals' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 369
OPEN Alliance
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
5. TESTER: Extracts the content of Source IP Address field to
<extractedSrcIP>
6. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field set to 54 (Server Identifier Option)
- Length field set to 4
- Value set to extractedSrcIP
6. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
Pass Criteria - Type field set to 54 (Server Identifier Option)
- Length field set to 4
- Value set to extractedSrcIP
Test Iterations
Notes Derived from RFC 2131 Section 2 Page 10 'Protocol Summary' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 370
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
Test Procedure 2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
5. TESTER: Verify that received DHCPOFFER Message contains:
- Bits 2 to 16 of 'flags' field is set to 0
5. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Bits 2 to 16 of 'flags' field is set to 0
Test Iterations
Notes Derived from RFC 2131 Section 2 Page 11 'Protocol Summary' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 371
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
Test Procedure for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- 'flags' field set to 0x7FFF(*INVALID*)
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
Pass Criteria 6. DUT: Sends DHCPOFFER Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 372
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as (<DUT-SERVER-0-IP-POOL-START>+1)
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
7. TESTER: DHCP Client <CLIENT-1> sends DHCPRELEASE Message to DUT
Test Procedure through <DIface-0>
8. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPRELEASE Message
9. TESTER: DHCP Client <CLIENT-2> transit state machine to BOUND state
10. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
11. TESTER: DHCP Client <CLIENT-2> sends DHCPRELEASE Message to DUT
through <DIface-0>
12. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPRELEASE Message
13. TESTER:DHCP Client <CLIENT-3> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
14. TESTER:DHCP Client <CLIENT-3> Listens (upto <ParamListenTime>) on
<DIface-0>
15. DUT: Sends DHCPOFFER Message
16. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
Pass Criteria 15. DUT: Sends DHCPOFFER Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 373
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 2.2 Page 12 'Dynamic allocation of network addresses'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 374
OPEN Alliance
The first four octets of the 'options' field of the DHCP message contain the (decimal)
Synopsys values 99, 130, 83 and 99, respectively (this is the same magic cookie as is defined in RFC
1497)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- First four octets of DHCP Options is set to
<DHCP-MAGIC-COOKIE>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- First four octets of DHCP Options is set to
<DHCP-MAGIC-COOKIE>
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 375
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
Test Procedure
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
5. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field set to 53 (Message Type Option)
5. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria - Message Option containing:
- Type field set to 53 (Message Type Option)
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 376
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
Test Procedure 2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing:
- Type field set to 53 (Message Type Option)
5. TESTER: Verify that received DHCPACK Message contains:
Pass Criteria - Message Option containing:
- Type field set to 53 (Message Type Option)
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 377
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
Test Procedure 5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. TESTER: Verify that received DHCPNAK Message contains:
- Message Option containing:
- Type field set to 53 (Message Type Option)
8. DUT: Sends DHCPNAK Message
9. TESTER: Verify that received DHCPNAK Message contains:
Pass Criteria
- Message Option containing:
- Type field set to 53 (Message Type Option)
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 378
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure Client Ping Checking for DHCP Server
running on DUT to FALSE
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
5. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
7. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Does not send ICMP Echo Message
Pass Criteria 8. DUT: Does not send ICMP Echo Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 379
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0>
8. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPACK Message
6. DUT: Sends DHCPOFFER Message
Pass Criteria
9. DUT: Sends DHCPACK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 380
OPEN Alliance
Any configuration parameters in the DHCPACK message SHOULD NOT conflict with those
Synopsys
in the earlier DHCPOFFER message to which the client is responding
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
Test Procedure through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Extracts the content of All the DHCP Message options to
<extractedOptions>
8. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0>
9. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Sends DHCPACK Message
11. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing extractedOptions
6. DUT: Sends DHCPOFFER Message
10. DUT: Sends DHCPACK Message
Pass Criteria
11. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing extractedOptions
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 381
OPEN Alliance
If the selected server is unable to satisfy the DHCPREQUEST message (e.g., the requested
Synopsys network address has been allocated), the server SHOULD respond with a DHCPNAK
message
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
Pass Criteria 8. DUT: Sends DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 382
OPEN Alliance
The server selected in the DHCPREQUEST message commits the binding for the client to
persistent storage and responds with a DHCPACK message containing the configuration
parameters for the requesting client... The server SHOULD mark an address offered to a
client in a DHCPOFFER message as available if the server receives no DHCPREQUEST
Synopsys
message from that client (Note: In this test the two emulated clients are to be provided the
only IP address configured in the DUT IP Pool after the Server Reboot causes all non
persistent information about the client from which the server did not receicve
DHCPREQUEST Message to get flushed)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-START>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Procedure listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. DUT CONFIGURE: Restart the DHCP Server running on DUT
causing it to listen on 1 interface(s)
7. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
8. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
8. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- 'yiaddr' field is set to extractedYiaddr
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 383
OPEN Alliance
Synopsys Servers SHOULD NOT check that the client's network address is already in use
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: Wait till (<CLIENT1-RENEWAL-TIME>/2) so that any client
Test Procedure
verification ICMP requests from server get flushed
7. TESTER: DHCP Client <CLIENT-1> transit state machine to INIT-REBOOT
state
8. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Length field set to 4
- Value set to extractedYiaddr
9. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Does not send ICMP Echo Message
11. (Note: Server will not send ICMP Echo Message because
DUT has prior knowledge of the client's configuration)
Pass Criteria 10. DUT: Does not send ICMP Echo Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 384
OPEN Alliance
If the client's request is invalid (e.g., the client has moved to a new subnet), servers
Synopsys
SHOULD respond with a DHCPNAK message to the client
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 385
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 386
OPEN Alliance
The server MUST broadcast the DHCPNAK message to the 0xffffffff broadcast address
Synopsys because the client may not have a correct network address or subnet mask, and the client
may not be answering ARP requests
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
Test Procedure
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. TESTER: Verify that received DHCPNAK Message contains:
- Destination IP Address field is set to 0xffffffff
8. DUT: Sends DHCPNAK Message
Pass Criteria 9. TESTER: Verify that received DHCPNAK Message contains:
- Destination IP Address field is set to 0xffffffff
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 387
OPEN Alliance
Otherwise, the server MUST send the DHCPNAK message to the IP address of the
Synopsys
BOOTP relay agent, as recorded in 'giaddr'
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 388
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 389
OPEN Alliance
4.6.6.5 Parameters
A client acquires a lease for a network address for a fixed period of time (which may be
infinite). Throughout the protocol, times are to be represented in units of seconds. The
Synopsys time value of 0xffffffff is reserved to represent \"infinity\" (Note: In this test we simply
check the syntactic usage of lease time DHCP option value since actual verification of
'infinity' is beyond our scope)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of 0xffffffff on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
Test
through <DIface-0> containing :
Procedure - Message Option containing:
- Type field set to 51 (IP Address Lease Time Option)
- Length field set to 4
- Value set to 0xffffffff
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field set to 51 (IP Address Lease Time Option)
- Length field set to 4
- Value set to 0xffffffff
6. DUT: Sends DHCPOFFER Message
Pass Criteria 7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 390
OPEN Alliance
Test Iterations
Servers receiving a DHCPINFORM message construct a DHCPACK message with any local
Synopsys
configuration parameters appropriate for the client
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP 3 (Router Option) with value
<DIface-0-IP-ADDRESS>
Test Procedure
for interface <DIface-0>
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
5. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
- Message Option containing:
- Type field set to 55 (Parameter Request List Option)
- Length field set to 1
- Value set to 3 (Router Option)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 391
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 392
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to 0
6. DUT: Sends DHCPACK Message
Pass Criteria 7. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to 0
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 393
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
Test Procedure - Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing:
- Type field is not set to 51 (IP Address Lease Time Option)
- Message Option containing:
- Type field is not set to 58 (Renewal (T1) Time Value
Option)
- Message Option containing:
- Type field is not set to 59 (Rebinding (T2) Time Value
Option)
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
Pass Criteria - Message Option containing:
- Type field is not set to 51 (IP Address Lease Time Option)
- Message Option containing:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 394
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 395
OPEN Alliance
The servers SHOULD unicast the DHCPACK reply to the address given in the 'ciaddr'
Synopsys
field of the DHCPINFORM message
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to <AIface-0-IP-ADDRESS>
6. DUT: Sends DHCPACK Message
Pass Criteria 7. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to <AIface-0-IP-ADDRESS>
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 396
OPEN Alliance
The server SHOULD check the network address in a DHCPINFORM message for
Synopsys consistency, but MUST NOT check for an existing lease (Note: This test verifies that the
DUT checks that the source IP address of DHCPINFORM message is consistent)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to
<IP-UNUSED-ADDRESS>(*INVALID*)
- 'ciaddr' field set to <DUT-SERVER-0-IP-POOL-START>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Does not send DHCPACK Message
Pass Criteria 6. DUT: Does not send DHCPACK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 397
OPEN Alliance
The server SHOULD check the network address in a DHCPINFORM message for consistency,
but MUST NOT check for an existing lease (Note: This test verifies that the DUT does not
Synopsys
check if the source IP address of DHCPINFORM message is in existing lease database of the
DUT)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-2> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to extractedYiaddr
- 'ciaddr' field set to extractedYiaddr
7. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPACK Message
Pass Criteria 8. DUT: Sends DHCPACK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 398
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure 4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
7. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to extractedYiaddr
8. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPNAK Message
Pass Criteria 9. DUT: Sends DHCPNAK Message
Test Iterations
Notes Derived from RFC 2131 Section 3.5 Page 22 'Client parameters in DHCP' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 399
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
Test Procedure
6. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
7. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to extractedYiaddr(*INVALID*)
8. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPNAK Message
10. TESTER: Verify that received DHCPNAK Message contains:
- Message Option containing:
- Type field set to 56 (Message Option)
9. DUT: Sends DHCPNAK Message
10. TESTER: Verify that received DHCPNAK Message contains:
Pass Criteria
- Message Option containing:
- Type field set to 56 (Message Option)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 400
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- 255 (End Option) at position Last
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Message Option containing:
- 255 (End Option) at position Last
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP
Notes
messages' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 401
OPEN Alliance
A server with multiple network addresses MUST be prepared to to accept any of its
Synopsys
network addresses as identifying that server in a DHCP message
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-1>
as follows :
- Start of pool as <DUT-SERVER-1-IP-POOL-START>
- End of pool as <DUT-SERVER-1-IP-POOL-END>
- Subnet as <DUT-SERVER-1-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-1-IP-POOL-SUBNETMASK>
4. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-1>
Test Procedure
5. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 2 interface(s)
6. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
7. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
8. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 54 (Server Identifier Option)
- Length field set to 4
- Value set to <DIface-0-IP-ADDRESS>
9. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Sends DHCPACK Message
11. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-1> containing :
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 402
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 403
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
Test Procedure
5. TESTER: Extracts the content of Value field of 54 (Server
Identifier Option) to <serverId>
6. TESTER: Extracts the content of Source Harware Address field to
<serverHwAddr>
7. TESTER:DHCP Client <CLIENT-1> Sends ARP Request Message to DUT
through <DIface-0> containing :
- ARP Target IP Address field set to serverId
8. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends ARP Response Message
10. TESTER: Verify that received ARP Response Message contains:
- ARP Sender MAC Address field is set to serverHwAddr
9. DUT: Sends ARP Response Message
Pass Criteria 10. TESTER: Verify that received ARP Response Message contains:
- ARP Sender MAC Address field is set to serverHwAddr
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 404
OPEN Alliance
If the 'giaddr' field in a DHCP message from a client is non-zero, the server sends any
Synopsys return messages to the 'DHCP server' port on the BOOTP relay agent whose address
appears in 'giaddr' (Note: This test verifies the UDP destination port)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 405
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 406
OPEN Alliance
If the 'giaddr' field in a DHCP message from a client is non-zero, the server sends any
Synopsys return messages to the 'DHCP server' port on the BOOTP relay agent whose address
appears in 'giaddr' (Note: This test verifies the IP Destination address)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 407
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
If the 'giaddr' field is zero and the 'ciaddr' field is nonzero, then the server unicasts
Synopsys DHCPOFFER and DHCPACK messages to the address in 'ciaddr' (Note: This test verifies that
DHCPACK is unicast to 'ciaddr' field of DHCPREQUEST Message)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <clientIPAddr>
6. TESTER: Wait till <CLIENT1-RENEWAL-TIME> for T1 timer to expire for
<CLIENT-1>
7. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- 'ciaddr' field set to clientIPAddr
8. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPACK Message
10. TESTER: Verify that received DHCPACK Message contains:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 408
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
If 'giaddr' is zero and 'ciaddr' is zero, and the broadcast bit is set, then the server
Synopsys
broadcasts DHCPOFFER and DHCPACK messages to 0xffffffff
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- 'flags' field set to DHCP_FLAGS_BROADCAST
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Destination IP Address field is set to 0xffffffff
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 409
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 410
OPEN Alliance
If the broadcast bit is not set and 'giaddr' is zero and 'ciaddr' is zero, then the server
Synopsys unicasts DHCPOFFER and DHCPACK messages to the client's hardware address and
'yiaddr' address
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to SELECTING
state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: Verify that received DHCPOFFER Message contains:
- Destination IP Address field is set to extractedYiaddr
7. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
8. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to extractedYiaddr
6. TESTER: Verify that received DHCPOFFER Message contains:
- Destination IP Address field is set to extractedYiaddr
Pass Criteria
8. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to extractedYiaddr
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 411
OPEN Alliance
In all cases, when 'giaddr' is zero, the server broadcasts any DHCPNAK messages to
Synopsys
0xffffffff
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
Test Procedure
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. TESTER: Verify that received DHCPNAK Message contains:
- Destination IP Address field is set to 0xffffffff
8. DUT: Sends DHCPNAK Message
Pass Criteria 9. TESTER: Verify that received DHCPNAK Message contains:
- Destination IP Address field is set to 0xffffffff
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP
Notes
messages' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 412
OPEN Alliance
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
Synopsys overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: This test
checks option overload for 'file' field)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
Test Procedure 6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
Pass Criteria 8. DUT: Sends DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 413
OPEN Alliance
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
Synopsys overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: This test
checks option overload for 'sname' field)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
Test Procedure state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'sname' field is used to hold options
- DHCP Message Option in 'sname' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'sname' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 414
OPEN Alliance
<DIface-0>
8. DUT: Sends DHCPNAK Message
Pass Criteria 8. DUT: Sends DHCPNAK Message
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
Synopsys overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: This test
does not send Overload Option but send Options in 'file' field of DHCP Message)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 415
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 416
OPEN Alliance
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
Synopsys overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: This test
does not send Overload Option but send Options in 'sname' field of DHCP Message)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
Test Procedure - Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'sname' field is used to hold options
- DHCP Message Option in 'sname' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'sname' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 417
OPEN Alliance
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
10. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
11. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
12. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
13. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
14. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- DHCP Message Option in 'sname' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'sname' field containing:
- Type field set to 255 (End Option)
15. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
16. DUT: Does not send DHCPNAK Message
8. DUT: Sends DHCPNAK Message
Pass Criteria
16. DUT: Does not send DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 418
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated by the 'options overload'
Synopsys
option) MUST begin with the first octet of the field
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
Test Procedure - Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 419
OPEN Alliance
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
10. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
11. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
12. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
13. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
14. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 0 (Pad Option)(*INVALID*)
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
15. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
16. DUT: Does not send DHCPNAK Message
8. DUT: Sends DHCPNAK Message
Pass Criteria
16. DUT: Does not send DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 420
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated ...) MUST be
Synopsys
terminated by an 'end' option
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
Test Procedure - Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 421
OPEN Alliance
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
10. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
11. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
12. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
13. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
14. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
15. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
16. DUT: Does not send DHCPNAK Message
8. DUT: Sends DHCPNAK Message
Pass Criteria
16. DUT: Does not send DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 422
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated ... and MUST be
Synopsys
followed by 'pad' options to fill the remainder of the field
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
Test Procedure - Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Sends DHCPNAK Message
9. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 423
OPEN Alliance
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
10. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
11. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
12. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
13. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
14. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Additional PAD Options to make packet length set to 576
- Message Option containing:
- Type field set to 52 (Overload Option)
- Length field set to 1
- Value set to the 'file' field is used to hold options
- DHCP Message Option in 'file' field containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)
- DHCP Message Option in 'file' field containing:
- Type field set to 0 (Pad Option)(*INVALID*)
- DHCP Message Option in 'file' field containing:
- Type field set to 255 (End Option)(*INVALID*)
15. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
16. DUT: Does not send DHCPNAK Message
8. DUT: Sends DHCPNAK Message
Pass Criteria
16. DUT: Does not send DHCPNAK Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 424
OPEN Alliance
A server or relay agent sending or relaying a DHCP message directly to a DHCP client (i.e.,
not to a relay agent specified in the 'giaddr' field) SHOULD examine the BROADCAST bit in
the 'flags' field. If this bit is set to 1, the DHCP message SHOULD be sent as an IP broadcast
Synopsys
using an IP broadcast address (preferably 0xffffffff) as the IP destination address and the
link-layer broadcast address as the link-layer destination address (Note: This test is to verify
the destination link local address of the received DHCP Messages from the DUT)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
Test - 'flags' field set to DHCP_FLAGS_BROADCAST
Procedure 5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Destination Harware Address field is set to
<LINK-LAYER-BROADCAST-ADDR>
8. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- 'flags' field set to DHCP_FLAGS_BROADCAST
9. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Sends DHCPACK Message
11. TESTER: Verify that received DHCPACK Message contains:
- Destination Harware Address field is set to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 425
OPEN Alliance
<LINK-LAYER-BROADCAST-ADDR>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Destination Harware Address field is set to
<LINK-LAYER-BROADCAST-ADDR>
Pass Criteria
10. DUT: Sends DHCPACK Message
11. TESTER: Verify that received DHCPACK Message contains:
- Destination Harware Address field is set to
<LINK-LAYER-BROADCAST-ADDR>
Test Iterations
Derived from RFC 2131 Section 4.1 Page 25 'Constructing and sending DHCP messages'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 426
OPEN Alliance
If the BROADCAST bit is cleared to 0, the message SHOULD be sent as an IP unicast to the
Synopsys IP address specified in the 'yiaddr' field and the link-layer address specified in the 'chaddr'
field
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- 'flags' field set to 0
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
8. TESTER: Extracts the content of 'chaddr' field to <extractedChaddr>
9. TESTER: Verify that received DHCPOFFER Message contains:
- Destination Harware Address field is set to extractedChaddr
- Destination IP Address field is set to extractedYiaddr
6. DUT: Sends DHCPOFFER Message
9. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Destination Harware Address field is set to extractedChaddr
- Destination IP Address field is set to extractedYiaddr
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 427
OPEN Alliance
Derived from RFC 2131 Section 4.1 Page 25 'Constructing and sending DHCP messages'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 428
OPEN Alliance
DHCP servers are not required to respond to every DHCPDISCOVER and DHCPREQUEST
message they receive. For example, a network administrator, to retain stringent control
Synopsys
over the clients attached to the network, may choose to configure DHCP servers to respond
only to clients that have been previously registered through some external mechanism
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DUT to allow only the client
with MAC Address <CLIENT1-MAC-ADDR> through <DIface-0>
Test
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Procedure listening on 1 interface(s)
5. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
6. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
7. DUT: Sends DHCPOFFER Message
8. TESTER:DHCP Client <CLIENT-2> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
9. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Does not send DHCPOFFER Message
7. DUT: Sends DHCPOFFER Message
Pass Criteria
10. DUT: Does not send DHCPOFFER Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 429
OPEN Alliance
Notes Derived from RFC 2131 Section 4.2 Page 25 'DHCP server administrative controls' (MAY)
If the client does not provide a 'client identifier' option, the server MUST use the
Synopsys
contents of the 'chaddr' field to identify the client
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
6. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
7. TESTER: DHCP Client <CLIENT-2> transit state machine to SELECTING
state
8. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is not set to extractedYiaddr
8. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- 'yiaddr' field is not set to extractedYiaddr
Derived from RFC 2131 Section 4.2 Page 26 'DHCP server administrative controls'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 430
OPEN Alliance
If an address is available, the new address SHOULD be chosen as follows: o The client's
Synopsys
current address as recorded in the client's current binding,
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: Wait till <CLIENT1-RENEWAL-TIME> for T1 timer to expire for
<CLIENT-1>
7. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0>
8. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPACK Message
10. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to extractedYiaddr
9. DUT: Sends DHCPACK Message
Pass Criteria 10. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to extractedYiaddr
Notes Derived from RFC 2131 Section 4.3.1 Page 27 'DHCPDISCOVER message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 431
OPEN Alliance
o The client's previous address as recorded in the client's (now expired or released)
Synopsys binding, if that address is in the server's pool of available addresses and not already
allocated,
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
Test Procedure
6. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
7. TESTER: DHCP Client <CLIENT-1> sends DHCPRELEASE Message to DUT
through <DIface-0>
8. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPRELEASE Message
9. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
10. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
11. DUT: Sends DHCPOFFER Message
12. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
11. DUT: Sends DHCPOFFER Message
Pass Criteria 12. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 432
OPEN Alliance
Notes Derived from RFC 2131 Section 4.3.1 Page 27 'DHCPDISCOVER message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 433
OPEN Alliance
o The address requested in the 'Requested IP Address' option, if that address is valid
Synopsys
and not already allocated,
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Length field set to 4
- Value set to (<DUT-SERVER-0-IP-POOL-START>+1)
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to (<DUT-SERVER-0-IP-POOL-START>+1)
6. DUT: Sends DHCPOFFER Message
Pass Criteria 7. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to (<DUT-SERVER-0-IP-POOL-START>+1)
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 27 'DHCPDISCOVER message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 434
OPEN Alliance
o A new address allocated from the server's pool of available addresses; the address is
Synopsys
selected based on the subnet from which the message was received (if 'giaddr' is 0)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Subnet Address of 'yiaddr' field is set to
<DIface-0-SUBNET>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Subnet Address of 'yiaddr' field is set to
<DIface-0-SUBNET>
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 27 'DHCPDISCOVER message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 435
OPEN Alliance
o A new address allocated from the server's pool of available ... or on the address of the
Synopsys
relay agent that forwarded the message ('giaddr' when not 0)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 436
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 27 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 437
OPEN Alliance
The server must also choose an expiration time for the lease, as follows: o IF the client has
not requested a specific lease in the DHCPDISCOVER message and the client already has an
Synopsys
assigned network address, the server returns the lease expiration time previously assigned
to that address
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure 4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 51 (IP Address Lease Time Option) to
<extractedLeaseTime>
6. TESTER: Wait till <CLIENT1-RENEWAL-TIME> for T1 timer to expire for
<CLIENT-1>
7. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0>
8. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
9. DUT: Sends DHCPACK Message
10. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing extractedLeaseTime
9. DUT: Sends DHCPACK Message
Pass Criteria 10. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing extractedLeaseTime
Notes Derived from RFC 2131 Section 4.3.1 Page 28 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 438
OPEN Alliance
The server must also choose an expiration time for the lease, as follows: o IF the client has
Synopsys not requested a specific lease in the DHCPDISCOVER message and the client does not have
an assigned network address, the server assigns a locally configured default lease time.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field is not set to 51 (IP Address Lease Time Option)
- Length field is not set to 4
- Value is not set to 0
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
Pass Criteria
- Type field is not set to 51 (IP Address Lease Time Option)
- Length field is not set to 4
- Value is not set to 0
Notes Derived from RFC 2131 Section 4.3.1 Page 28 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 439
OPEN Alliance
The server MUST return to the client: o Parameters requested by the client, according to
the following rules: -- IF the server has been explicitly configured with a default value for
Synopsys
the parameter, the server MUST include that value in an appropriate option in the 'option'
field.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Vendor class identifier with value
\"CONFORMANCE-DUT\"
for interface <DIface-0>
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
5. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 55 (Parameter Request List Option)
- Length field set to 1
- Value set to Vendor class identifier
6. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
7. DUT: Sends DHCPOFFER Message
8. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field set to Vendor class identifier
7. DUT: Sends DHCPOFFER Message
8. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Message Option containing:
- Type field set to Vendor class identifier
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 440
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 29 'DHCPDISCOVER message' (MUST)
The server MUST return to the client: o Parameters requested by the client, according to
the following rules: -- IF the server has been explicitly configured ... ELSE -- IF the server
Synopsys recognizes the parameter as ... ELSE -- The server MUST NOT return a value for that
parameter, (Note: In this test we verify the last ELSE statement by requesting 150 as a
vendor specific option)
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
Procedure through <DIface-0> containing :
- Message Option containing:
- Type field set to 55 (Parameter Request List Option)
- Length field set to 1
- Value set to 150
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field is not set to 150
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 441
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 29 'DHCPDISCOVER message' (MUST)
The server MUST supply as many of the requested parameters as possible and MUST
Synopsys
omit any parameters it cannot provide.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Vendor class identifier with value
Test Procedure \"CONFORMANCE-DUT\"
for interface <DIface-0>
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
5. TESTER: DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 55 (Parameter Request List Option)
- Length field set to 2
- Value set to 150 (Unsupported)
- Value set to 60 (Vendor Class Identifier)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 442
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 30 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 443
OPEN Alliance
Synopsys The server MUST include each requested parameter only once
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure 4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 55 (Parameter Request List Option)
- Length field set to 3
- Value set to 57 (Maximum DHCP Size Option)
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- All the DHCP Message options occurring exactly once
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Message Option containing:
- All the DHCP Message options occurring exactly once
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 30 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 444
OPEN Alliance
The server MAY choose to return the 'vendor class identifier' used to determine the
Synopsys parameters in the DHCPOFFER message to assist the client in selecting which DHCPOFFER
to accept
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Vendor class identifier with value
\"CONFORMANCE-DUT\"
Test Procedure
for interface <DIface-0>
4. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
5. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
6. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
7. DUT: Sends DHCPOFFER Message
8. TESTER: Verify that received DHCPOFFER Message contains:
- Message Option containing:
- Type field set to Vendor class identifier
7. DUT: Sends DHCPOFFER Message
8. TESTER: Verify that received DHCPOFFER Message contains:
Pass Criteria
- Message Option containing:
- Type field set to Vendor class identifier
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 30 'DHCPDISCOVER message' (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 445
OPEN Alliance
The server inserts the 'xid' field from the DHCPDISCOVER message into the 'xid' field of
Synopsys
the DHCPOFFER message and sends the DHCPOFFER message to the requesting client.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
Test Procedure 3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0> containing :
- 'xid' field set to 1000
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPOFFER Message
7. TESTER: Verify that received DHCPOFFER Message contains:
- 'xid' field is set to 1000
6. DUT: Sends DHCPOFFER Message
Pass Criteria 7. TESTER: Verify that received DHCPOFFER Message contains:
- 'xid' field is set to 1000
Test Iterations
Notes Derived from RFC 2131 Section 4.3.1 Page 30 'DHCPDISCOVER message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 446
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 447
OPEN Alliance
<DIface-0>
10. DUT: Sends DHCPNAK Message
Pass Criteria 10. DUT: Sends DHCPNAK Message
Test Iterations
Notes Derived from RFC 2131 Section 4.3.2 Page 31 'DHCPREQUEST message' (SHOULD)
If 'giaddr' is 0x0 in the DHCPREQUEST message, the client is on the same subnet as the
Synopsys server. The server MUST broadcast the DHCPNAK message to the 0xffffffff broadcast
address
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: DHCP Client <CLIENT-2> transit state machine to INIT-REBOOT
state
6. TESTER:DHCP Client <CLIENT-2> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- Message Option containing:
- Type field set to 50 (Requested IP Address Option)
- Value set to <CLIENT1-IP-ADDRESS>
7. TESTER:DHCP Client <CLIENT-2> Listens (upto <ParamListenTime>) on
<DIface-0>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 448
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.2 Page 32 'DHCPREQUEST message' (MUST)
If 'giaddr' is set in the DHCPREQUEST message, the client is on a different subnet. The
Synopsys server MUST set the broadcast bit in the DHCPNAK, so that the relay agent will broadcast
the DHCPNAK to the client
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 449
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.2 Page 32 'DHCPREQUEST message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 450
OPEN Alliance
o DHCPREQUEST generated during REBINDING state: The DHCP server SHOULD check
Synopsys
'ciaddr' for correctness before replying to the DHCPREQUEST
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Wait till (<CLIENT1-REBINDING-TIME>+<ParamToleranceTime>)
for Rebinding Time (T2) of <CLIENT-1> to expire
6. TESTER:DHCP Client <CLIENT-1> Sends DHCPREQUEST Message to DUT
through <DIface-0> containing :
- 'ciaddr' field set to 0
7. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
8. DUT: Does not send DHCPACK Message
Pass Criteria 8. DUT: Does not send DHCPACK Message
Test Iterations
Notes Derived from RFC 2131 Section 4.3.2 Page 32 'DHCPREQUEST message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 451
OPEN Alliance
If the server receives a DHCPDECLINE message,... The server MUST mark the network
Synopsys
address as not available
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
Test Procedure
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: DHCP Client <CLIENT-1> sends DHCPDECLINE Message to DUT
through <DIface-0>
7. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPDECLINE message
8. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
9. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
10. DUT: Sends DHCPOFFER Message
11. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is not set to extractedYiaddr
10. DUT: Sends DHCPOFFER Message
Pass Criteria 11. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is not set to extractedYiaddr
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 452
OPEN Alliance
Notes Derived from RFC 2131 Section 4.3.3 Page 33 'DHCPDECLINE message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 453
OPEN Alliance
Upon receipt of a DHCPRELEASE message, the server marks the network address as
Synopsys
not allocated.
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as (<DUT-SERVER-0-IP-POOL-START>+1)
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
Test Procedure 6. TESTER: DHCP Client <CLIENT-2> transit state machine to BOUND state
7. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
8. TESTER: DHCP Client <CLIENT-1> sends DHCPRELEASE Message to DUT
through <DIface-0>
9. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPRELEASE Message
10. TESTER:DHCP Client <CLIENT-3> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
11. TESTER:DHCP Client <CLIENT-3> Listens (upto <ParamListenTime>) on
<DIface-0>
12. DUT: Sends DHCPOFFER Message
13. TESTER: Verify that received DHCPOFFER Message contains:
- 'yiaddr' field is set to extractedYiaddr
Pass Criteria 12. DUT: Sends DHCPOFFER Message
13. TESTER: Verify that received DHCPOFFER Message contains:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 454
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.4 Page 33 'DHCPRELEASE message' (MUST)
Upon receipt of a DHCPRELEASE message, ... The server SHOULD retain a record of the
Synopsys client's initialization parameters for possible reuse in response to subsequent requests
from the client
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
listening on 1 interface(s)
Test Procedure 4. TESTER: DHCP Client <CLIENT-1> transit state machine to BOUND state
5. TESTER: Extracts the content of 'yiaddr' field to <extractedYiaddr>
6. TESTER: Wait till <ParamProcessTime> for DUT to complete the
activation of DHCP session
7. TESTER: DHCP Client <CLIENT-1> sends DHCPRELEASE Message to DUT
through <DIface-0>
8. TESTER: Wait till <ParamProcessTime> for DUT to process the
DHCPRELEASE Message
9. TESTER:DHCP Client <CLIENT-1> Sends DHCPDISCOVER Message to DUT
through <DIface-0>
10. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 455
OPEN Alliance
Test Iterations
Notes Derived from RFC 2131 Section 4.3.4 Page 33 'DHCPRELEASE message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 456
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to <AIface-0-IP-ADDRESS>
6. DUT: Sends DHCPACK Message
Pass Criteria 7. TESTER: Verify that received DHCPACK Message contains:
- Destination IP Address field is set to <AIface-0-IP-ADDRESS>
Test Iterations
Notes Derived from RFC 2131 Section 4.3.5 Page 33 'DHCPINFORM message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 457
OPEN Alliance
The server responds to a DHCPINFORM message by sending a DHCPACK ... The server
Synopsys
MUST NOT send a lease expiration time to the client
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- Message Option containing:
- Type field is not set to 51 (IP Address Lease Time Option)
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
Pass Criteria
- Message Option containing:
- Type field is not set to 51 (IP Address Lease Time Option)
Test Iterations
Notes Derived from RFC 2131 Section 4.3.5 Page 33 'DHCPINFORM message' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 458
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Configure IP Address pool on the DUT for interface <DIface-0>
as follows :
- Start of pool as <DUT-SERVER-0-IP-POOL-START>
- End of pool as <DUT-SERVER-0-IP-POOL-END>
- Subnet as <DUT-SERVER-0-IP-POOL-SUBNET>
- Subnet Mask as <DUT-SERVER-0-IP-POOL-SUBNETMASK>
2. DUT CONFIGURE: Configure Lease Time of <ParamLeaseTime> on DUT
for interface <DIface-0>
3. DUT CONFIGURE: Configure DHCP Server on the DUT to start
Test Procedure
listening on 1 interface(s)
4. TESTER:DHCP Client <CLIENT-1> Sends DHCPINFORM Message to DUT
through <DIface-0> containing :
- Source IP Address field set to <AIface-0-IP-ADDRESS>
- 'ciaddr' field set to <AIface-0-IP-ADDRESS>
5. TESTER:DHCP Client <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
6. DUT: Sends DHCPACK Message
7. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to 0
6. DUT: Sends DHCPACK Message
Pass Criteria 7. TESTER: Verify that received DHCPACK Message contains:
- 'yiaddr' field is set to 0
Test Iterations
Notes Derived from RFC 2131 Section 4.3.5 Page 33 'DHCPINFORM message' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 459
OPEN Alliance
4.7.1 General
The scope of this chapter is to specify test cases for the Dynamic Host configuration Protocol Version 4
(DHCPv4) from the following standards:
Though the focus of conformance testing has been limited to the above mentioned specification
document we have relied heavily upon the following document as specification for DHCP Message
Options:
RFC 2132 - DHCP Options and BOOTP Vendor Extensions
The number of DUT interfaces required by the topologies described below are as follows:
In each test, TESTER simulates a portion of exactly one of the 4 topologies shown below. Each node
shown in a topology is represented with a unique identifier. The test methods follow the same
representation of these nodes.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 460
OPEN Alliance
TOPOLOGY-1
N0 N0
<TIface-0> <DIface-0>
ECU
<SERVER-1> DUT
TOPOLOGY-1
TOPOLOGY-2
N0 N0
<TIface-0> <DIface-0>
ECU
<TIface-1> <DIface-1>
N1 N1
<SERVER-1> DUT
TOPOLOGY-2
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 461
OPEN Alliance
TOPOLOGY-3
These two servers are connected to the same DUT interface <DIface-0> through an emulated
broadcast device (e.g., HUB. See below)
<TIface-0>
<TIface-0>
N0
N0
<SERVER-1>
HUB <DIface-0> ECU
<TIface-0>
N0
N1
<SERVER-2>
TOPOLOGY-3
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 462
OPEN Alliance
TOPOLOGY-4
<TIface-0>
<TIface-0>
N0
N0
<SERVER-1>
HUB <DIface-0> ECU
<TIface-0>
N0
N1
<STATIC-CLIENT-1>
TOPOLOGY-4
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 463
OPEN Alliance
This suite expects to be running against any IP enabled network interface which supports acquisitiong of
IP address using DHCP. Most of the tests can be run against a single interface, only a few tests require
that the TESTER be connected to 2 interfaces that are connected to the DUT.
The highest number of DUT interfaces required in the DHCP Client Test Suite is 2 (two).
The following information are obtained from the unused IP network configurations:
IP Address of all the emulated servers
IP Address Pool to be offered by these emulated DHCP Servers
4.7.4 Coverage
Section
No. Test Category Test Number(s)
Design Goals and Protocol DHCPv4_CLIENT_SUMMARY_01 to
1.6, 2 Summary The Client-Server Protocol DHCPv4_CLIENT_SUMMARY_04
DHCPv4_CLIENT_PROTOCOL_01 to
3 The Client-Server Protocol DHCPv4_CLIENT_PROTOCOL_06
Client-server interaction - allocating DHCPv4_CLIENT_ALLOCATING_01 to
3.1 a network address DHCPv4_CLIENT_ALLOCATING_14
Client-server interaction - reusing a DHCPv4_CLIENT_REUSING_01 to
3.2 previously allocated network address DHCPv4_CLIENT_REUSING_08
DHCPv4_CLIENT_PARAMETERS_01 to
3.4, 3.5 Client parameters in DHCP DHCPv4_CLIENT_PARAMETERS_06
3.6, DHCPv4_CLIENT_USAGE_01 to
3.7, 4.4.4 DHCP Usage DHCPv4_CLIENT_USAGE_03
Constructing and sending DHCP DHCPv4_CLIENT_CONSTRUCTING_MESSAGES_01 to
4.1 messages DHCPv4_CLIENT_CONSTRUCTING_MESSAGES_14
DHCPv4_CLIENT_REQUEST_01 to
4.3.2 DHCPREQUEST message DHCPv4_CLIENT_REQUEST_12
Initialization and allocation of DHCPv4_CLIENT_INITIALIZATION_ALLOCATION_01
4.4.1 network address to DHCPv4_CLIENT_INITIALIZATION_ALLOCATION_10
Initialization with an externally DHCPv4_CLIENT_INITIALIZATION_EXTERNAL_01 to
4.4.3 assigned network address DHCPv4_CLIENT_INITIALIZATION_EXTERNAL_03
DHCPv4_CLIENT_REACQUISITION_01 to
4.4.5 Reacquisition and expiration DHCPv4_CLIENT_REACQUISITION_10
TOTAL 90
(Negative) 10
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 464
OPEN Alliance
Parameters/Constants Description
Value of DHCP IP Address Lease Time in seconds which will be offered
to the DUT (DHCP Client) unless overridden by specific value in a
particular test. It is advised that a too small value (less than 10 seconds)
<ParamLeaseTime>
can create some critical timeout related issues possibly leading to
undesirable test results since other timers like T1 (Renewal Time) and
T2 (Rebinding Time) are based on this entries. [Default : 15 seconds ]
The amount of tolerance to be provided so that we do not miss DUT
packets. Increasing the value of this entry too much will mean adding
<ParamToleranceTime> too much tolerance to DUT behaviour which can mean more tests
passing but actually with not sufficient conformance with the
specification.[Default : 1 second ]
The amount of time TESTER will usually wait for the DUT to process
some PDU sent by TESTER before continuing with the test. The purpose
<ParamProcessTime> of this entry also is to provide some amount of latency consideration
for the DUT so that the DUT gets ample time to process some PDU and
take action in accordance to that. [Default : 2 seconds ]
When we listen for a packet from the DUT either as response to a
packet we have senht or when the specification does not define any
specific time to listen for, this entry is used. It is also very important
<ParamListenTime> that it should have a large value since we start listening for a packet
and in the background some automated script may be fired to trigger
some event of the DUT which should cause the DUT to send our
desirable packet. [Default: 10 seconds ]
The number of seconds taken by the DUT to re-send a DHCPDISCOVER
after TESTER acting as a DHCP-Server did not send a DHCPOFFER
corresponding to the first DHCPDISCOVER sent by the DUT. This
parameter is used to calculate the next retransmission interval by the
TESTER and is different in case of different DUTs. "The delay between
<ParamFirstRetransmissionInterv retransmissions SHOULD be chosen to allow sufficient time for replies
al> from the server to be delivered based on the characteristics of the
internetwork between the client and the server. For example, in a
10Mb/sec Ethernet internetwork, the delay before the first
retransmission SHOULD be 4 seconds randomized by the value of a
uniform random number chosen from the range -1 to +1." -RFC
2131,Sec 4.1, Pg 24. [Default: 4 seconds ]
<DHCP-MAGIC-COOKIE> The first 4 octets of DHCP Options which represent the value 99, 130,
83 and 99 respectively.[Ref: RFC2131 Section 3 Page 13 ]
The all 1 IP broadcast address to which if any IP packet is sent, all the
<IP-BROADCAST-ADDRESS> nodes within the physical LAN ( and logical LAN is policy permits) will
receive the packet. [Ref: RFC2131 Section 4.4.3 Page 39 ]
<SERVERn-IP-ADDRESS> IP Address of the emulated 'n'th DHCP Server. (n = 1, 2)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 465
OPEN Alliance
'M'th IP Address in the pool of IP Address that the 'n'th server has to
SERVERn-IP-POOL-L-M> offer to clients requesting IP address through associated 'L'th interface
connection between DUT and TESTER.
IP Subnet Mask for all the pools of IP Addresses (as above) associated
<SERVERn-IP-POOL-NETMASK>
globally with the 'n'th emualated DHCP Server.
A MAC Address (Layer 2 address) which is not of any of the interfaces
<MAC-UNUSED-ADDRESS>
of TESTER nor DUT.
<IP-UNUSED-ADDRESS> IP Address which is of a different subnet than all the emulated servers
and all other objects within the simulated topologies.
<IP-UNUSED-NET-MASK> IP Subnet Mask of the above IP Unused Address which is basically the
IP Netmask provided for the configuration entry 'IP Unused Net Mask'
In some tests which require the DUT to retransmit its DHCPREQUEST
Message in Renewing state must have sufficiently high lease time so
<HIGH-LEASE-TIME> that the calculated value of T1 is such that half-way through T2 from T1
is greater than 60 seconds. [Value : 350 seconds ] [Ref: RFC2131
Section 4.4.5 Page 41]
In some tests which require the DUT to retransmit its DHCPREQUEST
Message in Rebinding state must have sufficiently high lease time so
<VERY-HIGH-LEASE-TIME> that the calculated value of T2 is such that half-way through Lease Time
from T2 is greater than 60 seconds. [Value : 1000 seconds ] [Ref:
RFC2131 Section 4.4.5 Page 41]
The 'n'th remote DHCP Client (DUT) which is served by emulated DHCP
Server if identified as <REMOTE-CLIENTn>, then the lease time for
<REMOTE-CLIENTn-LEASE-TIME>
which the client is expected to use the offered IP Address is identified
by this entry.
The 'n'th remote DHCP Client (DUT) which is served by emulated DHCP
Server if identified as <REMOTE-CLIENTn>, then the renewal time after
<REMOTE-CLIENTn-T1> which client is expected to attempt automated renewal of IP address
(as per RFC2131 Section 4.4 Page 35) is identified by this entry.
[Expected value : 0.5 * Offered Lease Time]
The 'n'th remote DHCP Client (DUT) which is served by emulated DHCP
Server if identified as <REMOTE-CLIENTn>, then the rebinding time
after which client is expected to attempt broadcasting of
<REMOTE-CLIENTn-T2>
DHCPREQUEST message after failing to get response in Renewing state
(as per RFC2131 Section 4.4 Page 35) is identified by this entry.
[Expected value : 0.875 * Offered Lease Time]
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 466
OPEN Alliance
4.7.6 Tests
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 467
OPEN Alliance
5.7.6.1 Summary
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 468
OPEN Alliance
DHCPv4_CLIENT_SUMMARY_02: Discard DHCP Offsers whose xid is not the one of the
latest DHCPDISCOVER sent
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 469
OPEN Alliance
Test Iterations
A DHCP client must be prepared to receive DHCP messages with an 'options' field of at
Synopsys least length 312 octets. This requirement implies that a DHCP client must be prepared to
receive a message of up to 576 octets
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 2 Page 10 'Protocol Summary' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 470
OPEN Alliance
The remaining bits of the flags field are reserved for future use. They MUST be set to
Synopsys
zero by clients and ignored by servers and relay agents
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 2 Page 11 'Protocol Summary' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 471
OPEN Alliance
The first four octets of the 'options' field of the DHCP message contain the (decimal)
Synopsys values 99, 130, 83 and 99, respectively (this is the same magic cookie as is defined in RFC
1497)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 472
OPEN Alliance
One particular option - the \"DHCP message type\" option - must be included in every
Synopsys DHCP message (Note: This test verifies the above statement for DHCPDISCOVER
Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 473
OPEN Alliance
One particular option - the \"DHCP message type\" option - must be included in every
Synopsys
DHCP message (Note: This test verifies the above statement for DHCPREQUEST Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 474
OPEN Alliance
One particular option - the \"DHCP message type\" option - must be included in every
Synopsys
DHCP message (Note: This test verifies the above statement for DHCPRELEASE Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 475
OPEN Alliance
One particular option - the \"DHCP message type\" option - must be included in every
Synopsys
DHCP message (Note: This test verifies the above statement for DHCPDECLINE Message)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 476
OPEN Alliance
One particular option - the \"DHCP message type\" option - must be included in every
Synopsys
DHCP message (Note: This test verifies the above statement for DHCPINFORM Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3 Page 13 'The Client-Server Protocol' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 477
OPEN Alliance
Synopsys The client broadcasts a DHCPDISCOVER message on its local physical subnet
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 478
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 479
OPEN Alliance
The client broadcasts a DHCPREQUEST message that MUST include the 'server identifier'
Synopsys
option to indicate which server it has selected
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 480
OPEN Alliance
the DHCPREQUEST message MUST use the same value in the DHCP message header's
Synopsys
'secs' field ... as the original DHCPDISCOVER message
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 481
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 482
OPEN Alliance
The client times out and retransmits the DHCPDISCOVER message if the client receives
Synopsys
no DHCPOFFER messages
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 483
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 484
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 485
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 486
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 487
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 488
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 489
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 490
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 491
OPEN Alliance
The client identifies the lease to be released with its 'client identifier', or 'chaddr' and
Synopsys
network address in the DHCPRELEASE message
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 492
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 493
OPEN Alliance
If the client receives neither a DHCPACK or a DHCPNAK message after employing the
Synopsys retransmission algorithm, the client reverts to INIT state and restarts the initialization
process
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 494
OPEN Alliance
If a client remembers and wishes to reuse a previously allocated network address, a client
Synopsys
may choose to omit some of the steps described in the previous section
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 495
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.2 Page 17-18 (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 496
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 497
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 498
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 499
OPEN Alliance
Synopsys the client may respond to ICMP Echo Request messages at this point
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 500
OPEN Alliance
If the client receives a DHCPNAK message, it cannot reuse its remembered network
Synopsys address. It must instead request a new address by restarting the configuration process, this
time using the (non-abbreviated) procedure described in section 3.1
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 501
OPEN Alliance
If a client has obtained a network address through some other means (e.g., manual
Synopsys configuration), it may use a DHCPINFORM request message to obtain other local
configuration parameters
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 502
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.5 Page 21 'Client parameters in DHCP' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 503
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Notes Derived from RFC 2131 Section 3.5 Page 21 'Client parameters in DHCP' (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 504
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.5 Page 21 'Client parameters in DHCP' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 505
OPEN Alliance
The client SHOULD include the 'maximum DHCP message size' option to let the server
Synopsys
know how large the server may make its DHCP messages
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.5 Page 21 'Client parameters in DHCP' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 506
OPEN Alliance
In addition, the client may suggest values for the network address and lease time in the
Synopsys DHCPDISCOVER message. The client may ... include the 'IP address lease time' option to
suggest the lease time it would like
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.5 Page 21 'Client parameters in DHCP' (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 507
OPEN Alliance
A client with multiple network interfaces must use DHCP through each interface
Synopsys independently to obtain configuration information parameters for those separate
interfaces
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 508
OPEN Alliance
A client SHOULD use DHCP to reacquire or verify its IP address and network parameters
Synopsys
whenever the local network parameters may have changed; e.g., at system boot time
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 3.7 Page 22 'When clients should use DHCP' (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 509
OPEN Alliance
If the client receives no response to DHCP messages sent to the IP address of a known
Synopsys DHCP server, the DHCP client reverts to using the IP broadcast address (Note: In this test
we check this feature for DHCPINFORM Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2131 Section 4.4.4 Page 40 'Use of broadcast and unicast' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 510
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.1 Page 22-23 'Constructing and sending DHCP
Notes
messages' (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 511
OPEN Alliance
DHCP clients MUST use the IP address provided in the 'server identifier' option for any
Synopsys
unicast requests to the DHCP server
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 512
OPEN Alliance
DHCP messages broadcast by a client prior to that client obtaining its IP address must have
Synopsys the source address field in the IP header set to 0 (Note: This test verifies source IP address
field of DHCPDISCOVER Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 513
OPEN Alliance
DHCP messages broadcast by a client prior to that client obtaining its IP address must have
Synopsys the source address field in the IP header set to 0 (Note: This test verifies source IP address
field of DHCPREQUEST Message)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 514
OPEN Alliance
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: Here we
Synopsys
verify that DUT correctly parses 'sname' field when Option Overload is present and set to
'sname contains options')
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 515
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 516
OPEN Alliance
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: Here we
Synopsys
verify that DUT correctly parses 'file' field when Option Overload is present and set to 'file
contains options')
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 517
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 23 'Constructing and sending DHCP messages'
Notes
(MUST)
If the options in a DHCP message extend into the 'sname' and 'file' fields, the 'option
overload' option MUST appear in the 'options' field, with value 1, 2 or 3 (Note: Here we
Synopsys
verify that DUT correctly does not parse 'file' field as Options when Option Overload is not
present)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 518
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 519
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 520
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated by the 'options overload'
option) MUST begin with the first octet of the field (Note: In this test we verify that the
Synopsys
DUT correctly does not imbibe the Option present in 'sname' field when 1st octet is not the
start of the option)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 521
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 522
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 523
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated ... MUST be terminated by
Synopsys an 'end' option (Note: In this test we verify that the DUT correctly does not imbibe the
Option present in 'sname' field in absence of 'end' option)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 524
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 525
OPEN Alliance
<DIface-0>
23. DUT: Does not send ICMP Echo Message
4. DUT: Sends DHCPDISCOVER Message
7. DUT: Sends DHCPREQUEST Message
11. DUT: Sends ICMP Echo Message
Pass Criteria
16. DUT: Sends DHCPDISCOVER Message
19. DUT: Sends DHCPREQUEST Message
23. DUT: Does not send ICMP Echo Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 526
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated ... MUST be terminated by
Synopsys an 'end' option (Note: In this test we verify that the DUT correctly does not imbibe the
Option present in 'file' field in absence of 'end' option)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 527
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 528
OPEN Alliance
<DIface-0>
23. DUT: Does not send ICMP Echo Message
4. DUT: Sends DHCPDISCOVER Message
7. DUT: Sends DHCPREQUEST Message
11. DUT: Sends ICMP Echo Message
Pass Criteria
16. DUT: Sends DHCPDISCOVER Message
19. DUT: Sends DHCPREQUEST Message
23. DUT: Does not send ICMP Echo Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 529
OPEN Alliance
The options in the 'sname' and 'file' fields (if in use as indicated ...) and MUST be followed
Synopsys by 'pad' options to fill the remainder of the field (Note: This test is done using the 'sname'
field only)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 530
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 531
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 532
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.1 Page 24 'Constructing and sending DHCP messages'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 533
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 534
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.1 Page 24 'Constructing and sending DHCP messages'
Notes
(SHOULD)
For example, a client may choose a different, random initial 'xid' each time the client
Synopsys
is rebooted,
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 2131 Section 4.1 Page 24 'Constructing and sending DHCP
Notes messages'
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 535
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 536
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 537
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 538
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 539
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 540
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 541
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 542
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 543
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 544
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 545
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 546
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 547
OPEN Alliance
The client SHOULD wait a random time between one and ten seconds to desynchronize
Synopsys
the use of DHCP at startup
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 548
OPEN Alliance
DHCPDISCOVER Message
is greater than or equal to
(1 - <ParamToleranceTime>) second
11. TESTER: Verify that the time interval between
sending of last DHCPNAK Message and reception of last
DHCPDISCOVER Message
is less than or equal to
(10 + <ParamToleranceTime>) second
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 549
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 550
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 551
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 552
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 553
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 554
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 555
OPEN Alliance
15. TESTER:DHCP Server <SERVER-1> Sends ICMP Echo Message to DUT through
<DIface-0> containing :
- Destination Harware Address field set to
<DIface-0-MAC-ADDRESS>
- Destination IP Address field set to <SERVER1-IP-POOL-0-0>
16. TESTER:DHCP Server <SERVER-1> Listens (upto <ParamListenTime>) on
<DIface-0>
17. DUT: Does not send ICMP Echo Reply Message
4. DUT: Sends DHCPDISCOVER Message
7. DUT: Sends DHCPREQUEST Message
Pass Criteria
13. DUT: Sends ICMP Echo Reply Message
17. DUT: Does not send ICMP Echo Reply Message
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 556
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 557
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 558
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 559
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 560
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 561
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 562
OPEN Alliance
At time T1 the client moves to RENEWING state and sends (via unicast) a DHCPREQUEST
Synopsys
message to the server to extend its lease
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 40 'Reacquisition and expiration'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 563
OPEN Alliance
If no DHCPACK arrives before time T2, the client moves to REBINDING state and sends
Synopsys
(via broadcast) a DHCPREQUEST message to extend its lease
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 564
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 565
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 566
OPEN Alliance
In both RENEWING and REBINDING states, if the client receives no response to its
DHCPREQUEST message, the client SHOULD wait one-half of the remaining time until T2 (in
Synopsys
RENEWING state) and one-half of the remaining lease time (in REBINDING state), down to a
minimum of 60 seconds, before retransmitting the DHCPREQUEST message.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 567
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(SHOULD)
In both RENEWING and REBINDING states, if the client receives no response to its
DHCPREQUEST message, the client SHOULD wait one-half of the remaining time until T2 (in
Synopsys
RENEWING state) and one-half of the remaining lease time (in REBINDING state), down to a
minimum of 60 seconds, before retransmitting the DHCPREQUEST message.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 568
OPEN Alliance
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 569
OPEN Alliance
If the lease expires before the client receives a DHCPACK, the client moves to INIT state,
MUST immediately stop any other network processing and requests network initialization
Synopsys
parameters as if the client were uninitialized (Note: In this test we verify that the DUT stops
network processing after lease time expires)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 570
OPEN Alliance
If the lease expires before the client receives a DHCPACK, the client moves to INIT state,
MUST immediately stop any other network processing and requests network initialization
Synopsys
parameters as if the client were uninitialized (Note: In this test we verify that the DUT
requests network initialization parameters after lease time expires)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 571
OPEN Alliance
If the client then receives a DHCPACK allocating that client its previous network address,
Synopsys
the client SHOULD continue network processing
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 2131 Section 4.4.5 Page 41 'Reacquisition and expiration'
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 572
OPEN Alliance
If the client is given a new network address, it MUST NOT continue using the previous
Synopsys
network address
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 573
OPEN Alliance
4.8.1 General
The scope of this chapter is to specify test cases for the Transmisison Control Protocol (TCP) from the
following standards:
RFC 793 - "Transmission Control Protocol" of DARPA, Internet Program, Protocol Specification
RFC 1122 - Requirement for Internet Hosts -- Communication Layers
RFC 2460 - Internet Protocol, Version 6 (IPv6) Specification
<TIface-0> <DIface-0>
ECU
Control channel for the
stub
HOST-1 DUT
TOPOLOGY-1
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 574
OPEN Alliance
<openTCPSocket(typeOfSocket)>: prompts the IUT to open a TCP socket depending on the type:
- Passive: opens a socket with a receiving call.
- Active: opens a socket with a sending call.
<Confirmation>: a message sent by the IUT as a response to procedure call from the Tester through the
Upper Tester channel. This message confirms, in case of the operation success, by sending a Boolean
back with some additional information depending on the type of operation required from the IUT.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 575
OPEN Alliance
4.8.6 Tests
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 576
OPEN Alliance
Test Iterations
Synopsys TCP MUST send an ACK in response to a FIN received in ESTABLISHED state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 577
OPEN Alliance
TCP, in CLOSED state, MUST send a RST segment with zero SEQ number in response to
Synopsys
an incoming segment not containing RST and ACK flags
Test Input
Check section general Input Parameters
Parameters
Pass Criteria 2. DUT: Send a RST control message with zero SEQ number
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 578
OPEN Alliance
TCP, in CLOSED state, MUST send a RST in response to an incoming segment containing
Synopsys
ACK and not containing RST and SEQ number is taken from SEG.ACK
Test Input
Check section general Input Parameters
Parameters
2. DUT: Send a RST segment with SEQ number same as the ACK
Pass Criteria
number of the incoming segment
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 579
OPEN Alliance
Synopsys TCP, in CLOSED state, MUST send a SYN on an active OPEN call
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 580
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 581
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 582
OPEN Alliance
TCP MUST move on to CLOSED state after receiving an ACK of the sent FIN in LAST-
Synopsys
ACK state
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 583
OPEN Alliance
Synopsys TCP MUST send an ACK after receiving a FIN in FINWAIT-1 or FINWAIT-2 state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 584
OPEN Alliance
TCP MUST move on to CLOSED state from TIME-WAIT state after a timeout of 2*MSL,
Synopsys
where TIME-WAIT is reached through FINWAIT-2 state
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 585
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 586
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 587
OPEN Alliance
TCP MUST NOT move on to CLOSED state from TIME-WAIT state before 2*MSL time
Synopsis
expires, where TIME-WAIT state is reached through CLOSING state
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 588
OPEN Alliance
TCP MAY send an ACK after receiving a data segment in FINWAIT-1 or FINWAIT-2
Synopsys
state
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 589
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 590
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 591
OPEN Alliance
Receiver TCP MUST check the checksum in any incoming segment, and MUST
Synopsys
acknowledge in case of no error
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.7 p86 TCP Checksum "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 592
OPEN Alliance
Receiver TCP MUST check the checksum in any incoming segment, and MUST NOT
Synopsys
acknowledge in case of an error
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.7 p86 TCP Checksum "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 593
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.7 p86 TCP Checksum "RFC-793 Section 3.1 p16 Header"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 594
OPEN Alliance
An ISN generator MUST be employed for selecting a 32 bit ISN that increments roughly
Synopsys
every 4 microseconds
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.9 p87 ISN Selection "RFC-793 s3.3 p27 Sequence
Notes Numbers"
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 595
OPEN Alliance
Synopsys TCP MUST return to LISTEN state, on receiving an acceptable RST, in SYN-RCVD state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 596
OPEN Alliance
Synopsys TCP MUST NOT change state, on receiving an unacceptable RST, in SYN-RCVD state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 597
OPEN Alliance
Synopsys TCP MUST send a RST after receiving an unacceptable ACK in SYN-RCVD state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 598
OPEN Alliance
TCP, in ESTABLISHED state, MUST return ACK with proper SEQ and ACK numbers after recv
a seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in
a synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptable acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 599
OPEN Alliance
TCP, in LISTEN state MUST send a RST after receiving a segment that is carrying an
Synopsys
unacceptable ACK and remain in the same state
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 600
OPEN Alliance
TCP, in ESTABLISHED state, MUST send an ACK indicating the correct SEQ number it
Synopsys
expects, after receiving a SYN with a SEQ number that is OTW
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 601
OPEN Alliance
TCP, in LISTEN state, MUST send a RST after receiving a spurious SYN,ACK that
Synopsys
potentially corresponds to an old SYN
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 602
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send a RST control message with SEQ number same as the ACK
Pass Criteria
number of the incoming segment
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 603
OPEN Alliance
TCP, in FINWAIT-1 state, MUST return an ACK with proper SEQ and ACK numbers after recv
a seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in
a synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptable acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 604
OPEN Alliance
TCP, in FINWAIT-2 state, MUST return an ACK with proper SEQ and ACK numbers after recv
a seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in
a synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptible acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 605
OPEN Alliance
TCP, in CLOSING state, MUST return an ACK with proper SEQ and ACK numbers after recv a
seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in a
synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptible acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 606
OPEN Alliance
TCP, in LAST-ACK state, MUST return an ACK with proper SEQ and ACK numbers after recv a
seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in a
synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptible acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 607
OPEN Alliance
TCP, in TIME-WAIT state, MUST return an ACK with proper SEQ and ACK numbers after recv
a seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in
a synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptible acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 608
OPEN Alliance
TCP, in CLOSE-WAIT state, MUST return ACK with proper SEQ and ACK numbers after recv a
seg with OTW SEQ or unacc ACK number, and remain in same state If the connection is in a
synchronized state, any unacceptable segment (out of window sequence number or
Synopsys unacceptible acknowledgment number) must elicit only an empty acknowledgment
segment containing the current send-sequence number and an acknowledgment indicating
the next sequence number expected to be received, and the connection remains in the
same state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 609
OPEN Alliance
4.8.6.4 Processing TCP OPEN Calls Received from the Application Layer
For an active OPEN call with unspecified foreign socket, TCP MUST return error:
Synopsys
foreign socket unspecified
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 610
OPEN Alliance
TCP MUST refuse a passive OPEN call on a <wnp> indicating \"error: connection illegal
Synopsys
for this process\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 611
OPEN Alliance
If an OPEN call arrives on state SYN-SENT, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 612
OPEN Alliance
If an OPEN call arrives on state SYN-RCVD, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 613
OPEN Alliance
If an OPEN call arrives on state ESTABLISHED, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 614
OPEN Alliance
If an OPEN call arrives on state FINWAIT-1, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 615
OPEN Alliance
If an OPEN call arrives on state FINWAIT-2, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 616
OPEN Alliance
If an OPEN call arrives on state CLOSE-WAIT, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 617
OPEN Alliance
If an OPEN call arrives on state CLOSING, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 618
OPEN Alliance
If an OPEN call arrives on state LAST-ACK, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 619
OPEN Alliance
If an OPEN call arrives on state TIME-WAIT, TCP MUST return \"error: connection
Synopsys
already exists\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 620
OPEN Alliance
4.8.6.5 Processing TCP SEND Calls Received from the Application Layer
If a SEND call arrives on CLOSED state, and user has got proper access to such conn, TCP
Synopsys
MUST return \"error: connection does not exist\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 621
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 622
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 623
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 624
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 625
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 626
OPEN Alliance
Test Iterations
Synopsys If a SEND call arrives on SYN-RCVD state, TCP MAY queue the request
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 627
OPEN Alliance
If SEND call arrives on state TIME-WAIT, TCP MUST return \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 628
OPEN Alliance
4.8.6.6 Processing TCP RECEIVE Calls Received from the Application Layer
If RECEIVE call arrives on state CLOSING, TCP MUST return \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 629
OPEN Alliance
If RECEIVE call arrives on CLOSED state, and the user has got access to such conn, TCP
Synopsys
MUST return \"error: connection does not exist\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 630
OPEN Alliance
If RECEIVE call arrives on SYN-SENT state, TCP MUST queue the request for processing
Synopsys
after entering ESTABLISHED state
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 631
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 632
OPEN Alliance
If RECEIVE call arrives on CLOSE-WAIT state and there is data awaiting delivery, TCP
Synopsys
MUST return the data to the application
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 633
OPEN Alliance
If RECEIVE call arrives on CLOSE-WAIT state and there is no data awaiting delivery, TCP
Synopsys
MUST respond \"error: connection closing\" to the application
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 634
OPEN Alliance
If RECEIVE call arrives on state LAST-ACK, TCP MUST return \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 635
OPEN Alliance
If RECEIVE call arrives on state TIME-WAIT, TCP MUST return \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 636
OPEN Alliance
For CLOSE call on CLOSED state, if the user has got access to such a connection, TCP
Synopsys
MUST return \"error: connection does not exist\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 637
OPEN Alliance
For CLOSE call on state CLOSING, TCP MUST return with \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 638
OPEN Alliance
Synopsys For CLOSE call on state FINWAIT-1, TCP SHOULD return \"error: connection closing\"
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 639
OPEN Alliance
For CLOSE call on state TIME-WAIT, TCP MUST return with \"error: connection
Synopsys
closing\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 640
OPEN Alliance
Synopsys For CLOSE call on state FINWAIT-2, TCP SHOULD return \"error: connection closing\"
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 641
OPEN Alliance
4.8.6.8 Processing TCP ABORT Calls Received from the Application Layer
For ABORT call on CLOSED state, if user has got access to such connection, TCP MUST
Synopsys
return with \"error: connection does not exist\"
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 642
OPEN Alliance
Synopsys For ABORT call in ESTABLISHED state TCP MUST enter CLOSED state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 643
OPEN Alliance
For ABORT call on CLOSING, LAST-ACK or TIME-WAIT state, TCP MUST respond with
Synopsys
\"ok\" and enter CLOSED state
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 644
OPEN Alliance
Synopsys TCP MUST ignore an incoming segment with RST flag in LISTEN state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 645
OPEN Alliance
TCP in LISTEN state, TCP MUST send RST in response to incoming segment with ACK and
Synopsys
remain in the same state, SEQ number of RST is taken from SEG.ACK
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 646
OPEN Alliance
TCP in SYN-SENT state MUST ignore a segment carrying an unacceptable ACK and
Synopsys
RST
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 647
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 648
OPEN Alliance
TCP, in SYN-SENT state MUST move on to CLOSED state after receiving a segment with
Synopsys
ACK and RST and acceptable ACK number
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 649
OPEN Alliance
TCP, in SYN-SENT state MUST drop the packet and remain in the same state after
Synopsys
receiving a segment with neither SYN nor RST flag set
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 650
OPEN Alliance
TCP, in SYN-RCVD state, MUST send ACK with next expected SEQ num on receiving any
Synopsys
segment (without RST) with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in SYN-RCVD state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 651
OPEN Alliance
TCP, in ESTABLISHED state, MUST send an ACK with next expected SEQ number after
Synopsys
recv any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in ESTABLISHED state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 652
OPEN Alliance
TCP, in FINWAIT-1 state, MUST send ACK with next expected SEQ number after receiving
Synopsys
any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in FINWAIT-1 state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 653
OPEN Alliance
TCP, in FINWAIT-2 state, MUST send ACK with next expected SEQ number after receiving
Synopsys
any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in FINWAIT-2 state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 654
OPEN Alliance
TCP, in CLOSE-WAIT state, MUST send an ACK with next expected SEQ number after recv
Synopsys
any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in CLOSE-WAIT state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 655
OPEN Alliance
TCP, in CLOSING state, MUST send an ACK with next expected SEQ number after
Synopsys
receiving any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in CLOSING state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 656
OPEN Alliance
TCP, in LAST-ACK state, MUST send an ACK with next expected SEQ number after
Synopsys
receiving any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify that the DUT remains in LAST-ACK state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 657
OPEN Alliance
TCP, in TIME-WAIT state, MUST send an ACK with next expected SEQ number after recv
Synopsys
any segment with OTW SEQ number and remain in the same state
Test Input
Check section general Input Parameters
Parameters
3. DUT: Send an ACK with ACK number indicating the correct expected
Pass Criteria next SEQ number
4. TESTER: Verify DUT remains in TIME-WAIT state for other cases
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 658
OPEN Alliance
TCP_FLAGS_INVALID_15: [!closed & !syn-sent & !listen] RST(otw SEQ) -> ignore
TCP, in any state other than CLOSED, SYN-SENT and LISTEN states, MUST ignore a RST
Synopsys
segment with OTW SEQ number
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 659
OPEN Alliance
TCP, in SYN-RCVD state, reached through active OPEN, MUST inform \"connection
Synopsys
refused\" to application on recv a RST
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 660
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Pass Criteria 3. TESTER: Verify that the DUT moves on to CLOSED state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 661
OPEN Alliance
Synopsys TCP, in CLOSING, LAST-ACK state, MUST return to CLOSED state on receiving a RST
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 662
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 663
OPEN Alliance
TCP, in SYN-RCVD state, MUST send a reset and go to CLOSED state, on recv a seg with
Synopsys
SYN in window
Test Input
Check section general Input Parameters
Parameters
Pass Criteria 3. TESTER: Verify that the DUT moves on to CLOSED state
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 664
OPEN Alliance
TCP, in TIME-WAIT state, MUST acknowledge a retransmitted FIN and restart the
Synopsys
2*MSL time-out
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 665
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 666
OPEN Alliance
Synopsys TCP, in CLOSED, LISTEN or SYN-SENT state, MUST not process a FIN
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 667
OPEN Alliance
TCP, in CLOSE-WAIT, CLOSING or LAST-ACK state, MUST not change state after
Synopsys
receiving a FIN
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 668
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 669
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 670
OPEN Alliance
TCP, if starts as an active connection and reaches SYN-RCVD state MUST go to CLOSED
Synopsys
state on RESET
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.13 p88 Closing a connection "RFC-793 Section 3.5"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 671
OPEN Alliance
TCP, in ESTABLISHED state MUST inform the application in case of aborting from
Synopsys
remote site
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.13 p87 Closing a connection "RFC-793 Section 3.5"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 672
OPEN Alliance
Test Iterations
Derived from RFC 1122 s4.2.2.12 p87 RST Segment "RFC-793 Section 3.4"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 673
OPEN Alliance
TCP MAY implement a half-duplex TCP close sequence, so that an application after
Synopsys
closing cannot continue to read data from the connection
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.13 p88 Closing a connection "RFC-793 Section 3.5"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 674
OPEN Alliance
Synopsys TCP MAY accept a new SYN from the remote TCP in TIME-WAIT state
Derived from RFC 1122 s4.2.2.13 p88 Closing a connection "RFC-793 Section 3.5"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 675
OPEN Alliance
Local user initiates the close, a FIN segment can be constructed and placed on the
Synopsys
outgoing segment queue
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 676
OPEN Alliance
TCP_CLOSING_07: [established] CLOSE -> FIN [finwait-1] RECEIVE + DATA -> ACK
[finwait-1]
Local user initiates the close, TCP enters the FIN-WAIT-1 state. RECEIVEs are allowed
Synopsys
in this state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 677
OPEN Alliance
Synopsys TCP enters the FIN-WAIT-2 state. RECEIVEs are allowed in this state.
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 678
OPEN Alliance
If an unsolicited FIN arrives from the network TCP enters the CLOSE_WAIT state. TCP
Synopsys
can send any remaining data.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 679
OPEN Alliance
TCP, FINWAIT-1 state MUST inform the application in case of aborting from remote
Synopsys
site
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.13 p87 Closing a connection "RFC-793 Section 3.5"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 680
OPEN Alliance
TCP, FINWAIT-2 state MUST inform the application in case of aborting from remote
Synopsys
site
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.13 p87 Closing a connection "RFC-793 Section 3.5"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 681
OPEN Alliance
TCP, in CLOSE-WAIT state MUST inform the application in case of aborting from
Synopsys
remote site
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.13 p87 Closing a connection "RFC-793 Section 3.5"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 682
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 683
OPEN Alliance
TCP MUST be prepared to handle an illegal option length for MSS, in a SYN segment,
Synopsys
without crashing
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 684
OPEN Alliance
TCP MUST be able to receive No Operation and End of Options List options in SYN
Synopsys
segment
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 685
OPEN Alliance
Synopsys TCP MUST ignore without error any TCP option it does not implement
Test Iterations
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 686
OPEN Alliance
TCP MUST be prepared to handle an illegal option length for MSS, in a SYN segment; a
Synopsys
suggested procedure is to reset the connection
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 687
OPEN Alliance
TCP MUST be prepared to handle an illegal option length for MSS, in a SYN-ACK
Synopsys
segment, without crashing
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 688
OPEN Alliance
TCP MUST be able to receive MSS option in SYN segment and calculate the effective
Synopsys
send segment size appropriately
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section
3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 689
OPEN Alliance
TCP MUST assume a default send MSS of 536 if MSS option is not received at
Synopsys
connection setup
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section
3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 690
OPEN Alliance
SendMSS is the MSS value received from the remote host, or the default 536 if no MSS
Synopsys
option is received.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section
3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 691
OPEN Alliance
TCP MUST be able to receive MSS option in SYN,ACK segment and calculate the effective
Synopsys
send segment size appropriately
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 692
OPEN Alliance
If an MSS option is not received at connection setup, TCP MUST assume a default send MSS
Synopsys
of 536
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 693
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793
Section 3.1"
Notes
Control Protocol (TCP)
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 694
OPEN Alliance
TCP SHOULD send MSS option in every SYN segment when its receive MSS differs
Synopsys
from the default 536
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Receive MSS of the DUT is different from the default
Test Procedure 2. TESTER: Cause the application on the DUT-side to issue an active
OPEN call
3. DUT: Send a SYN with an MSS different from the default 536
Pass Criteria 3. DUT: Send a SYN with an MSS different from the default 536
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section
3.1"
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 695
OPEN Alliance
TCP MAY send MSS option in every SYN segment even when its receive MSS value is
Synopsys
same as the default 536
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.6 p85 Maximum Segment Size Option "RFC-793 Section
3.1"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 696
OPEN Alliance
TCP_MSS_OPTIONS_14: Handle an illegal option length for MSS in a SYN ACK segment
TCP MUST be prepared to handle an illegal option length for MSS, in a SYN,ACK
Synopsys
segment; a suggested procedure is to reset the connection
Test Input
Check section general Input Parameters
Parameters
Derived from RFC 1122 s4.2.2.5 p85 TCP Options "RFC-793 Section 3.1"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 697
OPEN Alliance
Test Iterations
Derived from RFC 1122 s4.2.3.2 p96 When to Send an ACK Segment
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 698
OPEN Alliance
Synopsys TCP SHOULD implement a delayed ACK, but the delay MUST be less than 0.5 sec
Test Iterations
Derived from RFC 1122 s4.2.3.2 p96 When to Send an ACK Segment
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 699
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.20 p93 Event Processing "RFC-793 Section 3.9"
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 700
OPEN Alliance
TCP MAY send an ACK segment acknowledging RCV.NXT for valid out-of-order data
Synopsys
segments
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.21 p94 Acknowledging Queued Segments "RFC-
Notes
793"Section 3.9 (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 701
OPEN Alliance
In a stream of full-sized segments there SHOULD be an ACK for at least every second
Synopsys
segment
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.3.2 p96 When to Send an ACK Segment
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 702
OPEN Alliance
Test Iterations
Derived from RFC 1122 s4.2.3.2 p96 When to Send an ACK Segment
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 703
OPEN Alliance
Synopsys TCP SHOULD implement a delayed ACK, but the delay MUST be less than 0.5 sec
Test Iterations
Derived from RFC 1122 s4.2.3.2 p96 When to Send an ACK Segment
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 704
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.20 p93 Event Processing "RFC-793 Section 3.9"
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 705
OPEN Alliance
TCP MAY send an ACK segment acknowledging RCV.NXT for valid out-of-order data
Synopsys
segments
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.21 p94 Acknowledging Queued Segments "RFC-
Notes
793"Section 3.9 (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 706
OPEN Alliance
TCP MUST include an SWS avoidance algorithm in the receiver (Note: read some data
Synopsys
of size less than MSS)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.3 p97 When to Send a Window Update (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 707
OPEN Alliance
TCP MUST include an SWS avoidance algorithm in the receiver (Note:read some data of
size greater or equal to MSS. TESTER follow the third step in a sequence. TESTER cause
Synopsys
DUT to receive multiple of 360 byte data until DUT read data of size greater or equal to
MSS.)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.3 p97 When to Send a Window Update (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 708
OPEN Alliance
If a retransmitted packet differs from the original packet in the window value, then the
Synopsys
same IP identification field MUST NOT be used
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.15 p90 Retransmission Timeout "RFC-793 Section 3.7
page 41"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 709
OPEN Alliance
If a retransmitted packet differs from the original packet in the acknowledgement field,
Synopsys
the same IP identification field MUST NOT be used
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.15 p90 Retransmission Timeout "RFC-793 Section 3.7
page 41"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 710
OPEN Alliance
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p95 Retransmission Timeout Calculation (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 711
OPEN Alliance
TCP MUST include \"exponential backoff\" (check that it increases) for successive RTO
Synopsys
values for sending data segments
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p95 Retransmission Timeout Calculation (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 712
OPEN Alliance
TCP MUST include \"exponential backoff\" (check that it increases) for successive RTO
Synopsys
values for sending SYN segments
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p95 Retransmission Timeout Calculation (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 713
OPEN Alliance
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p96 Retransmission Timeout Calculation (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 714
OPEN Alliance
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p96 Retransmission Timeout Calculation (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 715
OPEN Alliance
Synopsys TCP SHOULD use an upper bound of 2*MSL of RTO for data segments
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p96 Retransmission Timeout Calculation (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 716
OPEN Alliance
Synopsys TCP SHOULD use an upper bound of 2*MSL of RTO for SYN segment
Test Iterations
Notes Derived from RFC 1122 s4.2.3.1 p96 Retransmission Timeout Calculation (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 717
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.15 p90 Retransmission Timeout "RFC-793 Section 3.7
page 41"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 718
OPEN Alliance
Synopsys A TCP MAY keep its offered receive window closed indefinitely
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.17 p92 Probing Zero Windows "RFC-793 Section 3.7,
page 42"
Notes
(MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 719
OPEN Alliance
Test Iterations
Derived from RFC 1122 s4.2.2.3 p83 Window Size "RFC-793 Section 3.1"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 720
OPEN Alliance
A sending TCP MUST be robust against window shrinking, which may cause the
Synopsys
\"useable window\" to become negative
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.16 p91 Managing the Window "RFC-793 Section 3.7 page
41"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 721
OPEN Alliance
Even if the receive window is closed indefinitely, the sending TCP MUST allow the
Synopsys
connection to stay open as long as probes are acknowledged
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.17 p92 Probing Zero Windows "RFC-793 Section 3.7, page
42"
Notes
Control Protocol (TCP)
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 722
OPEN Alliance
TCP SHOULD send the first zero window probe when the receiver window size remains
Synopsys
zero for the retransmission timeout period
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.17 p92 Probing Zero Windows "RFC-793 Section 3.7 page
42"
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 723
OPEN Alliance
TCP SHOULD increase exponentially the interval between successive zero window
Synopsys
probes
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Derived from RFC 1122 s4.2.2.17 p92 Probing Zero Windows "RFC-793 Section 3.7
page 42"
Notes
(SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 724
OPEN Alliance
Synopsys The TTL value used to send TCP segments MUST be configurable
Test Iterations
Derived from RFC 1122 s4.2.2.19 p93 Time to Live "RFC-793 Section 3.9, page 52"
Notes
(MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 725
OPEN Alliance
TCP SHOULD implement the Nagle Algorithm, i.e., buffer all the user data, regardless of
Synopsys
PSH, until the outstanding data has been acknowledged
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.4 p98 When to Send Data (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 726
OPEN Alliance
TCP SHOULD implement the Nagle Algorithm, i.e., it buffers all user data, regardless of
Synopsys
PSH bit, until the TCP can send a full-sized segment
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.4 p98 When to Send Data (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 727
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.3.4 p98 When to Send Data (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 728
OPEN Alliance
If PUSH flags are not implemented, then the sending TCP MUST NOT buffer data
Synopsys
indefinitely
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.2.2 p83 Use of Push "RFC-793 Section 2.8" (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 729
OPEN Alliance
TCP MAY aggregate data requested by an application for sending until accumulated
Synopsys
data exceeds effective send MSS
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.2.2 p82 Use of Push "RFC-793 Section 2.8" (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 730
OPEN Alliance
In the time of transmitting, TCP MUST keep the urgent pointer pointing to the sequence
Synopsys
number of the LAST octet in a sequence of urgent data
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.2.4 p84 Urgent Pointer "RFC-793 Section 3.1" (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 731
OPEN Alliance
Synopsys TCP MUST support a sequence of urgent data of any length for transmission
Test Iterations
Notes Derived from RFC 1122 s4.2.2.4 p84 Urgent Pointer "RFC-793 Section 3.1" (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 732
OPEN Alliance
The urgent pointer points to the sequence number of the octet following the urgent
Synopsys
data.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 733
OPEN Alliance
The data following the urgent pointer (non-urgent data) MUST NOT be delivered to the
Synopsys
user in the same buffer with preceding urgent data
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 734
OPEN Alliance
TCP MUST support a sequence of urgent data of any length for transmission (Note : This
Synopsys
test supports Urgent Pointer Mechanism of RFC 793)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1122 s4.2.2.4 p84 Urgent Pointer "RFC-793 Section 3.1" (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 735
OPEN Alliance
IW, the initial value of cwnd, MUST be less than or equal to 2*SMSS bytes and MUST
Synopsys
NOT be more than 2 segments.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2581 s 3.1 p 4 Slow Start and Congestion Avoidance (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 736
OPEN Alliance
During slow start, a TCP increments cwnd by at most SMSS bytes for each ACK received
Synopsys
that acknowledges new data.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2581 s 3.1 p 4 Slow Start and Congestion Avoidance (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 737
OPEN Alliance
The TCP output routine never sends more than the minimum of cwnd and the
Synopsys
receiver's advertised window.
(Note: cwnd is less than the receiver's advertised window)
Prerequisites Check section prerequisites
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 738
OPEN Alliance
The TCP output routine never sends more than the minimum of cwnd and the
Synopsys
receiver's advertised window.
(Note: receiver's advertised window is less than the cwnd)
Prerequisites Check section prerequisites
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 739
OPEN Alliance
Synopsys When congestion occurs, one-half of the current window size is saved in ssthresh.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 740
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 741
OPEN Alliance
When congestion occurs, one-half of the current window size, but at least 2 segments
Synopsys
is saved in ssthresh.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 742
OPEN Alliance
Upon a timeout cwnd MUST be set to no more than the loss window, LW, which equals
Synopsys
1 full-sized segment (regardless of the value of IW).
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2581 s 3.1 p 5 Slow Start and Congestion Avoidance (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 743
OPEN Alliance
Synopsys Slow start continues until TCP is halfway to where it was when congestion occurred
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 744
OPEN Alliance
Test Iterations
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 745
OPEN Alliance
SMALL_MAX_SEG_SIZE)/(2*SMALL_MAX_SEG_SIZE)}*2 =
(2*SMALL_MAX_SEG_SIZE)+SMALL_MAX_SEG_SIZE (bytes)= 3 segments
18. DUT: Send 3 segments
2. DUT: Set cwnd to <cwnd-ini> segment and ssthresh to 65535 bytes
4. DUT: Send only <cwnd-ini> segments
6. DUT: Set cwnd to 2*<cwnd-ini>, send 2*<cwnd-ini> segments and
wait for their ACK
9. DUT: Set cwnd to 4 segment. Send 4 segments and wait for
their ACK
11. DUT: Set ssthresh = (cwnd/2)=2 and cwnd to <LW>
12. DUT: Send only <cwnd> segment
Pass Criteria
15. DUT: Set cwnd to 2 (2*SMALL_MAX_SEG_SIZE in bytes) send 2
segments and wait for their ACK
17. DUT: Start congestion avoidance. Calculate cwnd (in bytes) as
cwnd + { (segsize * segsize) / cwnd) } * no_of_ACK_received
i.e. (2*SMALL_MAX_SEG_SIZE) + {(SMALL_MAX_SEG_SIZE*
SMALL_MAX_SEG_SIZE)/(2*SMALL_MAX_SEG_SIZE)}*2 =
(2*SMALL_MAX_SEG_SIZE)+SMALL_MAX_SEG_SIZE (bytes)= 3 segments
18. DUT: Send 3 segments
Test Iterations
Notes Derived from RFC 2581 s 3.1 p 4 Slow Start and Congestion Avoidance (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 746
OPEN Alliance
The increase in cwnd should be at most one segment each round-trip time (regardless
Synopsys
how many ACKs are received in that RTT)
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 747
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 748
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 749
OPEN Alliance
Test Iterations
Notes Derived from RFC 2581 s3.2 p6 Fast Retransmit/Fast Recovery (MUST)
When next ACK arrives that acknowledges new data, set cwnd to ssthresh (the value set
Synopsys
in step 1). This is termed `deflating' the window.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 750
OPEN Alliance
Test Iterations
Notes Derived from RFC 2581 s3.2 p7 Fast Retransmit/Fast Recovery (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 751
OPEN Alliance
Host receiving Datagram Too Big message MUST reduce its estimate of MTU for relevant
Synopsys
path, based on value of Next-Hop MTU field in the message
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 752
OPEN Alliance
10. TESTER: Check data length does not exceed (SMALL_PATH_MTU - 40) if:
- DF bit in the IP header is set (IPv4)
OR if:
- Fragmentation Header is present in the IP header (IPv6)
Test Iterations
After receiving Datagram Too Big message, host may reduce the size of datagrams it is
Synopsys
sending along the path or cease setting DF bit.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 753
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 754
OPEN Alliance
Attempt to detect increase MUST NOT be done less than 5 minutes after a Datagram
Synopsys
Too Big message has been received for the given destination
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 755
OPEN Alliance
Attempt to detect increase MUST NOT be done less than 1 minute after a previous,
Synopsys
successful attempted increase.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 756
OPEN Alliance
Test Iterations
Hosts MUST be able to deal with Datagram Too Big messages that do not include the
Synopsys
next-hop MTU
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 757
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 758
OPEN Alliance
Synopsys Host MUST never reduce its estimate of the Path MTU below 68 octets.
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 759
OPEN Alliance
Host MUST not increase its estimate of the Path MTU in response to the contents of a
Synopsys
Datagram Too Big message.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 760
OPEN Alliance
Test Iterations
Host must not send datagrams larger than 40 octets plus the Maximum Segment Size
Synopsys
(MSS) sent by its peer.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s3.1 p5 TCP MSS Option (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 761
OPEN Alliance
Host receiving a Datagram Too Big message from an unmodified router assumes that the
Synopsys
PMTU is minimum of its currently-assumed PMTU and 576
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s5 p7 Host processing of old-style messages (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 762
OPEN Alliance
Host receiving a Datagram Too Big message from an unmodified router stops setting
Synopsys
the DF bit in datagrams sent on that path.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s5 p7 Host processing of old-style messages (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 763
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 764
OPEN Alliance
14. DUT: Increase its PMTU estimate and continue sending data of
size same as the size of last data packet sent
15. TESTER: Check the sequence number of last two packet received are
not same
Test Iterations
Notes Derived from RFC 1191 s6.3 p12 Purging stale PMTU information (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 765
OPEN Alliance
On receiving Datagram Too Big message treat it as dropped segment, and wait till
Synopsys
retransmission timer expires and retransmit segment
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s6.4 p13 TCP layer actions (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 766
OPEN Alliance
The Datagram size used in the retransmission should, of course, be no larger than the
Synopsys
new PMTU.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 767
OPEN Alliance
Test Iterations
Notes Derived from RFC 1191 s6.4 p13 TCP layer actions (MUST)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s6.4 p14 TCP layer actions (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 768
OPEN Alliance
Retransmission caused by a Datagram Too Big message should not change the
Synopsys
congestion window. It should, however, trigger the slow-start mechanism
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 1191 s6.4 p14 TCP layer actions (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 769
OPEN Alliance
Maximum window size should be set to greatest multiple of segment size (PMTU - 40)
Synopsys
that is less than or equal to sender's buffer space size.
Test Input
Check section general Input Parameters
Parameters
Notes Derived from RFC 1191 s6.4 p14 TCP layer actions (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 770
OPEN Alliance
Synopsys PMTU Discovery does not affect the value sent in the TCP MSS option
Test Iterations
Notes Derived from RFC 1191 s6.4 p14 TCP layer actions (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 771
OPEN Alliance
There is no negotiation for use of MD5 option in a connection, it's purely a matter of
Synopsys
site policy whether or not connections use the option
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a SYN packet with TCP MD5 Signature Option
2. DUT: Send a SYN-ACK packet with proper TCP MD5 Signature Option
Pass Criteria 2. DUT: Send a SYN-ACK packet with proper TCP MD5 Signature Option
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 772
OPEN Alliance
There is no negotiation for use of MD5 option in a connection, it's purely a matter of
Synopsys
site policy whether or not connections use the option
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 773
OPEN Alliance
Upon receiving a signed segment, the receiver must validate it by calculating its own
Synopsys
digest from the same data using its own key
Test Input
Check section general Input Parameters
Parameters
Test Procedure 1. TESTER: Send a SYN packet with invalid TCP MD5 digest
2. DUT: Do not send any response
Pass Criteria 2. DUT: Do not send any response
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 774
OPEN Alliance
Upon receiving a signed segment, the receiver must validate it by calculating its own
Synopsys
digest from the same data using its own key
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 775
OPEN Alliance
A failing comparison must result in the segment being dropped and must not produce
Synopsys
any response back to the sender.
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Send a SYN packet with incorrect TCP MD5 Signature Option
Test Procedure 2. DUT: Detect the incorrect value of the digest and drop the segment
3. TESTER: Do not receive any response from DUT
4. TESTER: Check DUT goes to CLOSED state.
2. DUT: Detect the incorrect value of the digest and drop the segment
Pass Criteria
4. TESTER: Check DUT goes to CLOSED state.
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 776
OPEN Alliance
Absence of the option in the SYN,ACK segment must not cause the sender to disable
Synopsys
its sending of signatures.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 777
OPEN Alliance
Synopsys SYN,ACK sent during connection negotiation not signed, will be ignored
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 778
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 779
OPEN Alliance
Synopsys Total size of the header plus option must be less than or equal to 60 bytes
Test Iterations
Notes Derived from RFC 2385 s4.3 p4 TCP Header Size (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 780
OPEN Alliance
Size of the MD5 option must be factored into the MSS offered to the other side during
Synopsys
connection negotiation.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 2385 s4.3 p4 TCP Header Size (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 781
OPEN Alliance
In TCP header padding is used to ensure that the TCP header ends and data begins on a 32
bit boundary. The padding is composed of zeros. (Note: This test verifies that the DUT
Synopsys
forms TCP packet ending at 32 bit boundary when it includes TCP MD5 Signature Option as
specified in RFC2385)
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 793 s3.1 p19 Header Format (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 782
OPEN Alliance
4.8.6.25 TCP-CUBIC
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 783
OPEN Alliance
19. DUT: Enters into Convex region and set cwnd to (cwnd + (c *
Pow((elapsedTime - k) + rtt, 3) + w_max - count)/cwnd)
and send cwnd number of segments
20. TESTER: Send ACK for the received segments and repeat until cwnd
is Max (W_max, 2 * cwnd)
21. DUT: Send Max (W_max, 2 * cwnd) segments
2. DUT: Set cwnd to <cwnd-ini> segment and ssthresh to 65535 bytes
4. DUT: Send only <cwnd-ini> segments
6. DUT: Set cwnd to 2*<cwnd-ini> and send 2*<cwnd-ini> segments
10. DUT: On receivng the 3 duplicate ACKs,
set ssthresh to one-half the current cwnd.
Retransmit the segment indicated by the last received ACK
and set cwnd to ssthresh plus 3 (in segments)
12. DUT: On receiving Full ACK, enters into congestion avoidance
Pass Criteria and Send only one segment
14. DUT: Set cwnd to (W_tcp(t) = W_max*(1-beta) + 3*beta/(2-beta)*
t/RTT) and send cwnd number of segments
17. DUT: Send segments according to concave profile till
cwnd is not greater than W_max
19. DUT: Enters into Convex region and set cwnd to (cwnd + (c *
Pow((elapsedTime - k) + rtt, 3) + w_max - count)/cwnd)
and send cwnd number of segments
21. DUT: Send Max (W_max, 2 * cwnd) segments
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 784
OPEN Alliance
rheeTest Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 785
OPEN Alliance
Test Iterations
The cubic function is set to have its plateau at W_max so the concave growth continues
Synopsys
until the window size becomes W_max.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 786
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 787
OPEN Alliance
TCP_CUBIC_04: Cubic function turns into a convex profile and the convex window
growth begins
After that, the cubic function turns into a convex profile and the convex window
Synopsys
growth begins.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 788
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 789
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 790
OPEN Alliance
Test Iterations
If cwnd is less than W_tcp(t), then the protocol is in the TCP friendly region and cwnd is
Synopsys
set to W_tcp(t) at each reception of ACK.
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 791
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 792
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 813 s5 p11 Improved Acknowledgement Algorithms (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 793
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 794
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 795
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 796
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 797
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 798
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 799
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 896 Section "The solution to the small-packet problem" (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 800
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Notes Derived from RFC 896 Section "The solution to the small-packet problem" (SHOULD)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 801
OPEN Alliance
Ensure that
when DUIT is requested to open a TCP passive socket
and receive multiple Tcp Segments from 3 different ports
containing SYN flag
Synopsys indicating a value of 1
then DUT opens a TCP passive socket
and sends a TCP Segment to each sending port
containing SYN and ACK flags
indicating a value of 1.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 802
OPEN Alliance
Then
DUT opens a TCP passive sockets
and DUT sends multiple TCP segments to the sending port
containing SYN and ACK Flags
indicating a value of 1
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 803
OPEN Alliance
Then
Synopsys DUT opens multiple TCP active sockets'
and DUT sends multiple Tcp Segments from the open active sockets
containing SYN flag
indicating a value of 1
and DUT receives SYN ACK as a resonpse to its SYN
and DUT sends multiple TCP segments from the open active sockets
containing ACK flag
indicating a value of 1.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 804
OPEN Alliance
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 805
OPEN Alliance
Ensure that
when
DUT is requested to open a TCP active socket
Synopsys
and receives a SYN, ACK packet as answer to its SYN
then
DUT moves to state 'ESTABLISHED'
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 806
OPEN Alliance
Ensure that
when
DUT receives a FIN packet
Synopsys
then
DUT sends an ACK packet
and DUT moves to 'CLOSE WAIT' state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 807
OPEN Alliance
Ensure that
when
DUT receives a FIN packet
Synopsys then
DUT sends an ACK packet
and DUT sends a 'FIN s in response to user's 'Close' request
and DUT moves to 'CLOSED' state.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 808
OPEN Alliance
Ensure that
when
DUT is in ‘FINWAIT-1’ state
Synopsys
and DUT receives an 'ACK segment'
then
DUT moves to 'FINWAIT-2' state
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 809
OPEN Alliance
Ensure that
when
DUT receives a FIN packet
Synopsys
then
DUT sends an ACK packet
and DUT moves to 'TIME WAIT' state-
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 810
OPEN Alliance
Ensure that
when
DUT sends a FIN packet
and DUT receives a data packet and ACK packet
Synopsys and DUT receives a FIN packet
then
DUT sends an 'ACK segment' for the data segment received
and DUT sends an 'ACK segment' for the FIN segment received
indicating DUT state 'TIME WAIT'
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 811
OPEN Alliance
Ensure that
when
DUT sends a FIN packet and starts Timer
and DUT receives TCP packet
containing the Sequence Number
Synopsys
indicating a value of the last ACK sent after the Timer timed out
then
DUT sends a RST packet
containing a Sequence Number
indicating a value of the sequence number of the data packet received
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 812
OPEN Alliance
Ensure that
when
DUT receives an ACK of X with no payload
Synopsys
then
DUT sends an ACK packet
indicating DUT 'still-alive'
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 813
OPEN Alliance
4.8.6.28 Header
TCP_HEADER_01: To verify that DUT generates a TCP packet containing valid header
field values
Ensure that
when
DUT generates a 'TCP packet'
Synopsys
then
DUT sends a 'TCP packet'
containing a well-formed 'TCP header'
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 814
OPEN Alliance
TCP_HEADER_02: To verify that DUT accepts the TCP packet containing valid header
field values
Ensure that
when
Synopsys DUT receives a valid 'TCP packet'
then
DUT sends and ACK
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 815
OPEN Alliance
TCP_HEADER_03: To verify that a DUT accepts the packet in case TCP header
contains valid source port
Ensure that
when
DUT receives a TCP packet
containing a Source port
Synopsys indicating <PORT1>
containing a Sequence Number
indicating <SEQ1>
then
DUT sends an ACK
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 816
OPEN Alliance
TCP_HEADER_04: To verify that a DUT discards the packet in case TCP header
contains invalid source port
Ensure that
when
DUT receives a TCP packet
containing a Source Port
indicating a value different from PORT1
Synopsys
containing a sequence number
indicating SEQ1
then
DUT discards the TCP packet
and optionally DUT sends a RST packet
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 817
OPEN Alliance
TCP_HEADER_05: To verify that a DUT accepts the packet in case TCP header
Reserved field having a zero value
Ensure that
when
DUT receives a TCP packet
Synopsys containing a Reserved field
indicating a zero value
then
DUT accepts the TCP packet
Test Iterations
Notes RFC 793, chapter 3.1, RFC 4413, chapter 4.2.3., Reserved
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 818
OPEN Alliance
TCP_HEADER_06: To verify that a DUT accepts the packet in case TCP header
Reserved field having non-zero value.
Ensure that
when
DUT receives a 'TCP packet '
containing 'Reserved field '
Synopsys
indicating a non-zero value
then
DUT ignores the 'Reserved' field
and DUT accepts the 'TCP packet'
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 819
OPEN Alliance
TCP_HEADER_07: To verify that DUT discards TCP packets in case TCP header data
offset field having an invalid non zero value
Ensure that
when
DUT receives a TCP packet
Synopsys containing Data Offset
indicating a value less than 5 and non-zero
then
DUT discards TCP packet
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 820
OPEN Alliance
TCP_HEADER_08: To verify that DUT discards TCP packets in case TCP header data
offset field having value greater than the actual value
Ensure that
when
DUT receives a TCP packet
Synopsys containing Data Offset
indicating a value greater than the actual value
then
DUT discards TCP packet
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 821
OPEN Alliance
TCP_HEADER_09: To verify that DUT discards the TCP packet in case TCP header
checksum value is zero
Ensure that
when
DUT receives a TCP packet
Synopsys containing a Checksum
indicating a value of 0
then
DUT discards the TCP packet and sends no ACK back
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 822
OPEN Alliance
TCP_HEADER_10: To verify that DUT discards TCP packets in case header zero option
length
Ensure that
when
DUT receives a TCP packet
containing a Header Option
Synopsys indicating a value of 'NOP'
and containing 'EOP'
indicating length := 0
then
DUT discards the TCP packet and sends no ACK back
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 823
OPEN Alliance
TCP_HEADER_11: To verify that DUT discards TCP packets with SYN flag set and a
Multicast IP Destination Address
Ensure that
when
DUT receives a TCP packet'
containing SYN = 1
Synopsys
and containing IP Destination Address
indicating a value of <multicastAddress>
then
Discards the TCP packet and sends no ACK back.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 824
OPEN Alliance
Ensure that
when
DUT receives a SYN packet
containing 'Sequence Number'
Synopsys indicating <ISN>
then
DUT sends an ACK
containing an Acknowledgment Number
indicating <ISN>+1
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 825
OPEN Alliance
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 826
OPEN Alliance
TCP_SEQUENCE_03: To verify that DUT accepts the TCP packet in case initial
sequence number has zero value
Ensure that
when
DUT receives a SYN packet
Synopsys containing Sequence Number
indicating a zero value
then
DUT accepts the TCP packet
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 827
OPEN Alliance
TCP_SEQUENCE_04: To verify that DUT accepts the TCP packet in case initial
sequence number has maximum value
Ensure that
when
DUT receives a TCP packet
containing Sequence Number
indicating <SeqMaxVal> value
Synopsys
then
DUT accepts the TCP packet
and DUT sends an SYN,ACK packet
containing Acknowledgment Number
indicating 0
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 828
OPEN Alliance
TCP_SEQUENCE_05: To verify that DUT accepts the TCP packets in case sequence
numbers received are in the right order
Ensure that
when
DUT receives a severalTCP packets
Synopsys containing SEQ
indicating values incremented correctly.
then
DUT sends an ACK for every received TCP Segments
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 829
OPEN Alliance
TCP_SEQUENCE_06: To verify that DUT forces retry in case the TCP packets come in a
disordered sequence.
Ensure that
when
DUT receives TCP packets
containing Sequence Numbers in a desoredered sequence.
Synopsys
then
DUT sends TCP packets
containing ACK
indicating the expected TCP packet.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 830
OPEN Alliance
4.8.6.30 Acknowledgment
Ensure that
when
DUT is requested to send an ACK and Data
then
Synopsys
DUT sends a TCP packet
containing ACK flag
indicating a value of 1
and the Data
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 831
OPEN Alliance
Ensure that
when
DUT receives a TCP packet
containing ACK flag
indicating a value of 1
Synopsys
and a payload
then
Sends an ACK
containing Ack Number
indicating the expected value
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 832
OPEN Alliance
Ensure that
when
DUT has no data left to send
and DUT receives a TCP packet
Synopsys
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 833
OPEN Alliance
Ensure that
when
DUT receives an ACK
containing Length
Synopsys
indicating a value of 0 (an empty ACK, no piggybagging)
then
DUT does not send an RST
and DUT ends connection with the expected ACK number
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 834
OPEN Alliance
TCP_CONTROL_FLAGS_01: To verify that DUT generates TCP data packet with PSH
flag not set
Ensure that
when
DUT is requested to generate a TCP packet
Synopsys then
DUT generates a TCP packet
containing a PSH flag
indicating a value of 0
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 835
OPEN Alliance
TCP_CONTROL_FLAGS_02: To verify that DUT receives TCP data packet in case PSH
flag is not set
Ensure that
when
DUT receives a TCP packet
containing PSH flag
Synopsys indicating a value of 0
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 836
OPEN Alliance
TCP_CONTROL_FLAGS_03: To verify that DUT receives TCP data packet in case PSH
flag set
Ensure that
when
DUT receives a TCP packet
containing PSH flag
Synopsys indicating PSH control bit set to 1
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 837
OPEN Alliance
TCP_CONTROL_FLAGS_04: To verify that DUT receives TCP data packet in case URG
flag is not set
Ensure that
when
DUT receives a TCP packet
containing URG flag
Synopsys indicating a value of 0
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 838
OPEN Alliance
TCP_CONTROL_FLAGS_05: To verify that DUT receives TCP data packet in case URG
flag is set
Ensure that
when
DUT receives a TCP packet
containing URG flag
Synopsys indicating a value of 1
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 839
OPEN Alliance
TCP_CONTROL_FLAGS_06: To verify that DUT generates TCP data packet with URG
flag set to one
Ensure that
when
DUT is requested to generate a TCP packet
containing URG flag
Synopsys indicating a value of 1
then
DUT generates aTCP packet
containing URG flag
indicating a value of 1
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 840
OPEN Alliance
TCP_CONTROL_FLAGS_07: To verify that DUT accepts TCP data packet with both PSH
and URG Flags set to 1
Ensure that
when
DUT receives a 'TCP packet'
containing 'URG flag' and 'PSH flag'
Synopsys indicating a value of 1 buffer
then
DUT sends an ACK
containing an Ack Number
indicating the expected value.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 841
OPEN Alliance
Ensure that
when
DUT receives a SYN packet
containing RST flag
indicating a value of 1
and containg a Sequence Number
indicating a value of a late duplicated SYN
Synopsys and DUT receives a SYN packet
containing a Sequence Number
indicating <SEQ>
then
DUT sends a SYN,ACK
containing an Ack Number
indicating a value of <SEQ> + 1
and DUT moves from state ‘LISTEN’ to ‘SYN-RECEIVED’
Test Input
Check section general Input Parameters
Parameters
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 842
OPEN Alliance
TCP_CONTROL_FLAGS_09: To verify that DUT discards a TCP packet with RST flag set
when in LISTEN state
Ensure that
when
DUT is in state ‘LISTEN’
Synopsys
and DUT receives a SYN,RST packet
then
DUT discards the TCP packet and sends no SYN,ACK back
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 843
OPEN Alliance
TCP_CONTROL_FLAGS_10: To verify that DUT rejects a TCP packet with ACK flag set
when in LISTEN state
Ensure that
when
DUT is in state ‘LISTEN’
and DUT receives a SYN,ACK packet
Synopsys
then
DUT sends a RST packet
containg a Sequence Number
indicating the value of the Sequence Number in the received SYN,ACK.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 844
OPEN Alliance
Ensure that
when
DUT is in ‘ESTABLISHED’ state
and DUT receives RST
and receives an ACK
containing a Sequence Number
Synopsys
indicating a value of <SEQ>
then
DUT sends RST
containing a Sequence Number
indicating a value of <SEQ>
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 845
OPEN Alliance
TCP_CONTROL_FLAGS_12: To verify that DUT generates a packet with PSH flag set to
1
Ensure that
when
DUT is requested to send a TCP packet
containing a PSH flag
Synopsys indicating a value of 1
then
DUT sends a TCP packet
containing a PSH flag
indicating a value of 1.
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 846
OPEN Alliance
TCP_WINDOW_SIZE_01: To verify that DUT accepts ACK packet in case window size is
zero
Ensure that
when
DUT receives an ACK
containing a Sequence Number
indicating a value of <SEQ>
containing Length
Synopsys indicating a valule of 1
containing Window size
indicating a value of 0
then
DUT sends an ACK
containing an Ack Number
indicating a value of <SEQ> + 1
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 847
OPEN Alliance
TCP_WINDOW_SIZE_02: To verify that DUT accepts the packet having URG bit set and
with zero sized window
Ensure that
when
DUT receives TCP packet
containing URG flag
indicating a value of 1
containing a Sequence Number
indicating a value of <SEQ>
Synopsys containing Length
indicating a valule of 1
containing Window size
indicating a value of 0
then
DUT sends an ACK
containing an Ack Number
indicating a value of <SEQ> + 1
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 848
OPEN Alliance
Ensure that
when
DUT is requested to generate aTCP packet
Synopsys then
DUT sends a TCP packet
containing a Checksum
indicating the <calculatedChecksum>
Test Input
Check section general Input Parameters
Parameters
Test Iterations
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 849
OPEN Alliance
5.1.1 General
The scope of this chapter is to specify test cases for Scalable service-Oriented MiddlewarE over IP
Protocol from the following standards:
Specification of Service Discovery V1.2.0 R4.1 Rev 3
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3
<TIface-0> <DIface-0>
ECU
HOST- DUT
TOPOLOGY-1 TOPOLOGY-1
Tester configuration required for the tests in the following sections pertaining to SOME/IP tests:
5.1.1.4 Coverage
Specification Document Section Test Category Test Number(s)
Number
Specification of Service
SOMEIPSRV_FORMAT_01 to
Discovery V1.2.0 R4.1 Rev 7.3 Message format
SOMEIPSRV_FORMAT_27
3
Specification of Service
SOMEIPSRV_OPTIONS_01 to
Discovery V1.2.0 R4.1 Rev 7.3.9 Options Array
SOMEIPSRV_OPTIONS_15
3
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 850
OPEN Alliance
Specification of Service
StopSubscribeEventgroup
Discovery V1.2.0 R4.1 Rev 7.4.6.2 SOMEIPSRV_SD_BEHAVIOR_06
entry
3
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 851
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 852
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 853
OPEN Alliance
This is a Service Interface version value that is not implemented in DUT and not
listed in xml specification as well.
Server Unknown
Interface Version Default: 0xFF
Setting
This is a Service ID value that is not implemented in DUT and not listed in xml
specification as well.
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 854
OPEN Alliance
Name Description
TESTER Entity which is responsible for validating the Device
under Test (DUT)
DUT Device under Test
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 855
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 856
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 857
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 858
OPEN Alliance
SOMEIPSRV_FORMAT_01: Client ID
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 859
OPEN Alliance
SOMEIPSRV_FORMAT_02: Session ID
After initialization of the Service Discovery Module, the Session ID for
Synopsys
messages sent by the local ECU shall be 0x0001.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Listens (upto (<SERVICE-ID-1-INITIAL-WAIT-
TIME> +
<CLIENT1-LISTEN-TIME>) second) on <DIface-0>
Test Procedure 3. DUT: Sends SOME/IP Notification Message
4. TESTER: Verify that received SOME/IP Notification Message
contains:
- Session ID is set to 0x0001
5. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
Pass Criteria 4. TESTER: Verify that received SOME/IP Notification Message contains:
- Session ID is set to 0x0001
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3
Reference
[SWS_SD_00034] Page 23 'Message format' (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 860
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 861
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 862
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 863
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 864
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 865
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 866
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 867
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 868
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 869
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 870
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 871
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 872
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 873
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 874
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 875
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 876
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 877
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 878
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 879
OPEN Alliance
The "Number of Option 1" of the Type 2 Entry format layout shall carry the
Synopsys number of options the first option run uses. Note : SubscribeEventgroupAck is
under Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- Num of Opt 1 in Entry Array is greater than or equal to
1
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Notification Message
Pass Criteria
8. TESTER: Verify that received SOME/IP Notification Message contains:
- Num of Opt 1 in Entry Array is greater than or equal to 1
Reference Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 880
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 881
OPEN Alliance
The Service ID field of the Type 2 Entry format layout shall carry the Service ID of
the eventgroups service, statically configured using the parameter
Synopsys
SdServerServiceID and SdClientServiceID, depending on being a server or client
entry. Note : SubscribeEventgroupAck is under Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
Test through
Procedure <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOME/IP Notification Message
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3
Reference
[SWS_SD_00193] Page 32 'Message format' (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 882
OPEN Alliance
The Instance ID field of the Type 2 Entry format layout shall carry the Instance ID
of the eventgroups service statically configured using the parameter
Synopsys
SdServerServiceInstanceID and SdClientServiceInstanceID, depending on being a
server or client entry. Note : SubscribeEventgroupAck is unnder Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
Test - Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- Instance ID in Entry Array is set to
<SERVICE-ID-1-INSTANCE-ID>
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Notification Message
Pass Criteria 8. TESTER: Verify that received SOME/IP Notification Message contains:
- Instance ID in Entry Array is set to
<SERVICE-ID-1-INSTANCE-ID>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 883
OPEN Alliance
The Major Version field of the Type 2 Entry format layout shall carry the
SdServerServiceMajorVersion and SdClientServiceMajorVersion, depending on
Synopsys
being a server or client entry. Note : SubscribeEventgroupAck is under Entry Type
2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- Major Version in Entry Array is set to
<SERVICE-ID-1-MAJ-VER>
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 884
OPEN Alliance
The TTL field of the Type 2 Entry Entry format layout defines the lifetime of the
entry in seconds configured using the parameter SdServerTimerTTL and
Synopsys
SdClientTimerTTL, except for Stop- or Nack-Entries, which use a TTL of 0. Note :
SubscribeEventgroupAck is under Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Test 5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
Procedure through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 885
OPEN Alliance
SOMEIPSRV_FORMAT_27: Reserved field, which follows the TTL field of the Type 2
Entry
The Reserved field, which follows the TTL field of the Type 2 Entry format
Synopsys layout, shall be statically set to 0x0000. Note : SubscribeEventgroupAck is under
Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 886
OPEN Alliance
The Eventgroup ID field of the Type 2 Entry format layout shall carry the ID of an
Synopsys Eventgroup, configured using the parameter SdConsumedEventGroupID. Note :
SubscribeEventgroupAck is under Entry Type 2
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Test Procedure 0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 887
OPEN Alliance
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOME/IP Notification Message
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3
Reference
[SWS_SD_00204] Page 33 'Message format' (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 888
OPEN Alliance
Synopsys The Length field of the IPv4 Endpoint Option shall be set to 0x0009
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
Test Procedure - Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_ENDPOINT
- SOMEIP Expected Number Of IPv4 Endpoint Option set to 1
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Length of IPv4 EndPoint Option is set to 0x0009
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 5. TESTER: Verify that received SOME/IP Notification Message contains:
- Length of IPv4 EndPoint Option is set to 0x0009
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3.9
Reference
[SWS_SD_00209] Page 36 'Options Array' (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 889
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 890
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 891
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 892
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 893
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 894
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 895
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 896
OPEN Alliance
The Type field [8 bits] of the IPv4 Multicast Option shall be statically set to
Synopsys
0x14.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- Type of Option Array is set to
SOMEIP_OPTION_IPV4_MULTICAST
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Notification Message
Pass Criteria
8. TESTER: Verify that received SOME/IP Notification Message contains:
- Type of Option Array is set to SOMEIP_OPTION_IPV4_MULTICAST
Reference Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3.9
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 897
OPEN Alliance
The Reserved field [8 bits] of the IPv4 Multicast Option (followed by the IPv4-
Synopsys
Address field) of the Configuration Option segment shall be statically set to 0x00.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
Test Procedure - EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_MULTICAST
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- First Reserved Field in IPv4 Multicast Option is set to
0x00
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 898
OPEN Alliance
The IPv4-Address field [32 bits] of the IPv4 Multicast Option shall be set to the
Synopsys
Multicast IP address of the Eventgroup.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
Test Procedure <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_MULTICAST
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 899
OPEN Alliance
The Reserved field [8 bits] of the IPv4 Multicast Option shall statically be set to
Synopsys
0x00.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
Test Procedure 4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Entry Array set to <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 900
OPEN Alliance
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_MULTICAST
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- Second Reserved Field in IPv4 Multicast Option is set
to
0x00
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Notification Message
Pass Criteria 8. TESTER: Verify that received SOME/IP Notification Message contains:
- Second Reserved Field in IPv4 Multicast Option is set to
0x00
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3.9
Reference
[SWS_SD_00394] Page 39 'Options Array' (MUST)
Notes
SOMEIPSRV_OPTIONS_13: Layer 4 Protocol field of the IPv4 Multicast Option for UDP
The Layer 4 Protocol field [8 bits] (L4-Proto) of the IPv4 Multicast Option shall
Synopsys
be set to 0x11 (UDP).
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
Test Procedure 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 901
OPEN Alliance
The Port Number field [16 bits] of the IPv4 Multicast Option shall carry the port
Synopsys
number for transporting Multicast Events of the Eventgroup.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
Test Procedure <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 902
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 903
OPEN Alliance
SOMEIPSRV_OPTIONS_15: Layer 4 Protocol field of the IPv4 Endpoint Option for TCP
The Layer 4 Protocol field [8 bits] (L4-Proto) of the IPv4 Endpoint Option shall be
Synopsys set to one of the following values, depending on the port specified: 0x06: TCP
0x11: UDP NOTE: Checking For TCP.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
Test Procedure - Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_ENDPOINT
- SOMEIP Expected Number Of IPv4 Endpoint Option set to 1
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Transport Protocol in IPv4 EndPoint Option is set to 0x06
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 5. TESTER: Verify that received SOME/IP Notification Message contains:
- Transport Protocol in IPv4 EndPoint Option is set to 0x06
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.3.9
Reference
[SWS_SD_00214] Page 37 'Options Array' (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 904
OPEN Alliance
Instance ID shall be set to 0xFFFF, if all service instances shall be returned. It shall
Synopsys be set to the Instance ID of a specific service instance, if just a single service
instance shall be returned. NOTE: Checking For Instance ID 0xFFFF.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 2
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Instance ID set to
0xFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Expected Offer Services' Service ID set to <SERVICE-ID-1>
Test Procedure - Number Of Expected Offer Service Entries set to 2
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Number of expected Offer Service Entry is set to 2
6. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 2 to <extractedInstID2>
7. TESTER: Verify that received SOME/IP Notification Message
contains:
- Service Instance ID of Offer Service Entry 1 is not set
to
extractedInstID2
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
- Number of expected Offer Service Entry is set to 2
Pass Criteria
7. TESTER: Verify that received SOME/IP Notification Message contains:
- Service Instance ID of Offer Service Entry 1 is not set to
extractedInstID2
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 905
OPEN Alliance
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.1 Find
Reference
Service Entry [TR_SOMEIP_00351] Page 66 (MUST)
Notes
Instance ID shall be set to 0xFFFF, if all service instances shall be returned. It shall
Synopsys be set to the Instance ID of a specific service instance, if just a single service
instance shall be returned. NOTE: Checking For Specific Instance ID.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 2
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Instance ID set to
0xFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Expected Offer Services' Service ID set to <SERVICE-ID-1>
- Number Of Expected Offer Service Entries set to 2
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
Test Procedure contains:
- Number of expected Offer Service Entry is set to 2
6. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 2 to <extractedInstID2>
7. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Instance ID set to
extractedInstID1
- Service ID in Entry Array set to <SERVICE-ID-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 906
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 907
OPEN Alliance
Major Version shall be set to 0xFF, that means that services with any version shall
Synopsys be returned. If set to value different than 0xFF, services with this specific major
version shall be returned only. NOTE: Checking For Major Version 0xFF.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Major Version set to
0xFF
- SOME/IP Find Service Entry TTL set to 0xFFFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
Test Procedure 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Major Version in Entry Array is set to
<SERVICE-ID-1-MAJ-VER>
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria
- Major Version in Entry Array is set to
<SERVICE-ID-1-MAJ-VER>
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.1 Find
Reference
Service Entry [TR_SOMEIP_00351] Page 66 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 908
OPEN Alliance
Major Version shall be set to 0xFF, that means that services with any version shall
Synopsys be returned. If set to value different than 0xFF, services with this specific major
version shall be returned only. NOTE: Checking For Specific Major Version.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Major Version set to
<SERVICE-ID-1-MAJ-VER>
- SOME/IP Find Service Entry TTL set to 0xFFFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
Test Procedure 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Major Version in Entry Array is set to
<SERVICE-ID-1-MAJ-VER>
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria
- Major Version in Entry Array is set to
<SERVICE-ID-1-MAJ-VER>
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.1 Find
Reference
Service Entry [TR_SOMEIP_00351] Page 66 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 909
OPEN Alliance
Minor Version shall be set to 0xFFFF FFFF, that means that services with any
version shall be returned. If set to a value different to 0xFFFF FFFF, services with
Synopsys
this specific minor version shall be returned only. NOTE: Checking For Minor
Version 0xFFFFFFFF.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Minor Version set to
0xFFFFFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
Test 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Procedure 0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Minor Version in Entry Array is set to
<SERVICE-ID-1-MINOR-VER>
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria
- Minor Version in Entry Array is set to
<SERVICE-ID-1-MINOR-VER>
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.1 Find
Reference
Service Entry [TR_SOMEIP_00351] Page 66 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 910
OPEN Alliance
Minor Version shall be set to 0xFFFF FFFF, that means that services with any
version shall be returned. If set to a value different to 0xFFFF FFFF, services with
Synopsys
this specific minor version shall be returned only. NOTE: Checking For Specific
Minor Version.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Minor Version set to
<SERVICE-ID-1-MINOR-VER>
- Service ID in Entry Array set to <SERVICE-ID-1>
Test 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Procedure 0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Minor Version in Entry Array is set to
<SERVICE-ID-1-MINOR-VER>
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria
- Minor Version in Entry Array is set to
<SERVICE-ID-1-MINOR-VER>
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.1 Find
Reference
Service Entry [TR_SOMEIP_00351] Page 66 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 911
OPEN Alliance
TTL shall be set to the lifetime of the service instance. After this lifetime the
Synopsys
service instance shall considered not been offered.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- TTL in Entry Array is set to <SERVICE-ID-1-TTL>
6. TESTER: Wait till <SERVICE-ID-1-TTL> To Timeout offer service
from DUT
Test Procedure 7. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
8. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
9. DUT: Does not send SOME/IP Response Message
10. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 5. TESTER: Verify that received SOME/IP Notification Message contains:
- TTL in Entry Array is set to <SERVICE-ID-1-TTL>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 912
OPEN Alliance
Offer Service entries shall always reference at least an IPv4 or IPv6 Endpoint
Synopsys
Option to signal how the service is reachable. NOTE: Test is for IPv4.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
Test Procedure - Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOMEIP Expected Number Of IPv4 Endpoint Option is
greater
than or equal to 1
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria
- SOMEIP Expected Number Of IPv4 Endpoint Option is greater
than or equal to 1
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.2
Reference
Offer Service Entry [TR_SOMEIP_00357] Page 67 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 913
OPEN Alliance
The IP addresses and port numbers of the Endpoint Options shall also be used for
transporting events and notification events, In the case of UDP this information is
Synopsys
used for the source address and the source port of the events and notification events.
NOTE: This test is for UDP port.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOMEIP Expected Number Of IPv4 Endpoint Option is greater
than or equal to 1
6. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Transport Port to <extractedport>
Test 7. TESTER: Extracts the content of Service Instance ID of Offer
Procedure Service
Entry 1 to <extractedInstID1>
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 914
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 915
OPEN Alliance
The stop offer service entry type shall be used to stop offering service instances.
Stop Offer Service entries shall set the entry fields exactly like the Offer Service
Synopsys
entry they are stopping, except: TTL shall be set to 0x000000. NOTE: Check For
TTL.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Test - Service ID in Entry Array set to <SERVICE-ID-1>
Procedure 4. DUT: Sends SOME/IP Notification Message
5. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_STOP_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
7. DUT: Sends SOME/IP Notification Message
8. TESTER: Verify that received SOME/IP Notification Message
contains:
- TTL in Entry Array is set to 0
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Notification Message
Pass Criteria
8. TESTER: Verify that received SOME/IP Notification Message contains:
- TTL in Entry Array is set to 0
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.1.3 Stop
Reference
Offer Service Entry [TR_SOMEIP_00363] page 68 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 916
OPEN Alliance
Synopsys The Subscribe Eventgroup entry type shall be used to subscribe to an eventgroup.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOMEIP Expected Number Of IPv4 Endpoint Option is
greater
than or equal to 1
6. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Transport Port to <extractedport>
7. TESTER: Extracts the content of Service Instance ID of Offer
Test Procedure Service
Entry 1 to <extractedInstID1>
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 917
OPEN Alliance
The Stop Subscribe Eventgroup entry type shall be used to stop subscribing to
eventgroups. Stop Subscribe Eventgroup entries shall set the entry fields exactly
Synopsys
like the Subscribe Eventgroup entry they are stopping, except: TTL shall be set to
0x000000.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
Test 2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
Procedure through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 918
OPEN Alliance
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOMEIP Expected Number Of IPv4 Endpoint Option is greater
than or equal to 1
6. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Transport Port to <extractedport>
7. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
10. DUT: Sends SOME/IP Notification Message
11. DUT CONFIGURE: Trigger Event on <DIface-0> with the following
informations
- Event ID : <EVENT-ID-1-EG-ID-1>
- Event Group ID : <EVENT-GROUP-ID-1-SI-1>
- Service ID : <SERVICE-ID-1>
12. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Message Expected UDP Dest Port set to
extractedport
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-1>
13. DUT: Sends SOME/IP Notification Message
14. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_STOP_SUBSCRIBE
- SOME/IP Subscribe Eventgroup Entry TTL set to 0
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 919
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 920
OPEN Alliance
The Subscribe Eventgroup Acknowledgment entry type shall be used to indicate that
Subscribe Eventgroup entry was accepted. Subscribe Eventgroup Acknowledgment
entries shall set the entry fields in the following way: Type shall be set to 0x07
Synopsys
(SubscribeEventgroupAck). Service ID, Instance ID, Major Version, Eventgroup ID,
TTL, and Reserved shall be the same value as in the Subcribe that is being
answered.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
Test <DIface-0> containing :
Procedure - Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- SOME/IP Subscribe Eventgroup Entry TTL set to 0xFFFFFF
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
- Major Version in Subscribe EventGroup Entry set to
<SERVICE-ID-1-MAJ-VER>
- Reserved Field in Subscribe EventGroup Ack Entry set to 0
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
8. DUT: Sends SOME/IP Notification Message
9. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry is set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 921
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 922
OPEN Alliance
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- SOME/IP Subscribe Eventgroup Entry TTL set to 0xFFFFFF
- Service ID in Subscribe Eventgroup Entry set to
<UNKNOWN-SERVICE-ID>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
- Major Version in Subscribe EventGroup Entry set to
<SERVICE-ID-1-MAJ-VER>
- Reserved Field in Subscribe EventGroup Ack Entry set to 0
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <UNKNOWN-SERVICE-ID>
8. DUT: Sends SOME/IP Notification Message
9. TESTER: Verify that received SOME/IP Notification Message
contains:
- TTL in Subscribe EventGroup Ack Entry is set to 0
10. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
8. DUT: Sends SOME/IP Notification Message
Pass Criteria
9. TESTER: Verify that received SOME/IP Notification Message contains:
- TTL in Subscribe EventGroup Ack Entry is set to 0
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.4.2.4
Reference
Subscribe Eventgroup Negative Acknowledgement (Subscribe (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 923
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 924
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 925
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 926
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 927
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 928
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 929
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 930
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 931
OPEN Alliance
After sending the first message the Repetition Phase of this Service Instance/these
Synopsys Service Instances is entered. After each message sent in the Repetition Phase the
delay is doubled.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
4. TESTER: <CLIENT-1> Listens (upto
<SERVICE-ID-1-REP-BASE-INTV*3+ParamToleranceTime> second)
on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
5. DUT: Sends 2 SOME/IP Notification Messages
Test Procedure 6. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
(<SERVICE-ID-1-REP-BASE-INTV*2> -
<ParamToleranceTimeMillisec>) micro second
7. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is less than
(<SERVICE-ID-1-REP-BASE-INTV*2> +
<ParamToleranceTimeMillisec>) micro second
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
5. DUT: Sends 2 SOME/IP Notification Messages
6. TESTER: Verify that the time interval between
Pass Criteria
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 932
OPEN Alliance
(<SERVICE-ID-1-REP-BASE-INTV*2> -
<ParamToleranceTimeMillisec>) micro second
7. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is less than
(<SERVICE-ID-1-REP-BASE-INTV*2> +
<ParamToleranceTimeMillisec>) micro second
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.5.1
Reference Startup Behavior [TR_SOMEIP_00404], [TR_SOMEIP_00406] Page 71
(SHOULD)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 933
OPEN Alliance
In the Main Phase Offer Messages and Publish Messages shall be sent cyclically
Synopsys
if a CYCLIC_OFFER_DELAY is configured.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
4. TESTER: Wait till <SERVICE-ID-1-TOTAL-REP-INTV> For DUT to
enter
Main Phase
5. TESTER: <CLIENT-1> Listens (upto
<SERVICE-ID-1-CYCLE-INTV*2+ParamToleranceTime> second) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
6. DUT: Sends 2 SOME/IP Notification Messages
7. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
(<SERVICE-ID-1-CYCLE-INTV> - <ParamToleranceTime>)
second
8. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is less than
(<SERVICE-ID-1-CYCLE-INTV> + <ParamToleranceTime>)
second
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
6. DUT: Sends 2 SOME/IP Notification Messages
7. TESTER: Verify that the time interval between
Pass Criteria
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 934
OPEN Alliance
SOMEIPSRV_SD_BEHAVIOR_03: Response if the last offer was more than half of cyclic
offer delay
Find messages received with the Unicast Flag set to 1, shall be answered with a
Synopsys multicast RESPONSE if the last offer was sent 1/2 CYCLIC_OFFER_DELAY or
longer ago.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
4. TESTER: Wait till <SERVICE-ID-1-TOTAL-REP-INTV> For DUT to
enter
Main Phase
5. TESTER: <CLIENT-1> Listens (upto <SERVICE-ID-1-CYCLE-INTV>
second)
Test Procedure on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
6. DUT: Sends SOME/IP Notification Message
7. TESTER: Wait till (<SERVICE-ID-1-CYCLE-INTV>/2) For DUT to
consume
1/2 Cyclic_Offer_Delay
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 935
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 936
OPEN Alliance
Find messages received with Unicast Flag set to 0 (multicast), shall be answered
Synopsys
with a multicast response.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
4. TESTER: Wait till <SERVICE-ID-1-TOTAL-REP-INTV> For DUT to
enter
Main Phase
5. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
Test Procedure <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Unicast Flag in Notification Message set to 0
- Service ID in Entry Array set to <SERVICE-ID-1>
6. TESTER: <CLIENT-1> Listens (upto <SERVICE-ID-1-CYCLE-INTV>
second)
on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
- SOME/IP Message Expected IP Dst Address set to
<SOME_IP_MULTICAST_IP_ADDR>
7. DUT: Sends SOME/IP Notification Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
3. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOME/IP Notification Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.7.5.2
Reference
Server Answer Behavior [TR_SOMEIP_00423] Page 73 (SHOULD)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 937
OPEN Alliance
Synopsys The Stop Offer Service entry type shall be used to stop offering Service Instances.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
Test Procedure <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set
to
extractedInstID1
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
8. DUT: Sends SOME/IP Notification Message
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 938
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 939
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 940
OPEN Alliance
- Service ID : <SERVICE-ID-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-1>
11. DUT: Sends SOME/IP Notification Message
12. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_STOP_SUBSCRIBE
- SOME/IP Subscribe Eventgroup Entry TTL set to 0x000000
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set
to
<SERVICE-ID-1-INSTANCE-ID>
13. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-1>
14. DUT: Does not send SOME/IP Notification Message
15. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
8. DUT: Sends SOME/IP Notification Message
Pass Criteria
11. DUT: Sends SOME/IP Notification Message
14. DUT: Does not send SOME/IP Notification Message
Specification of Service Discovery V1.2.0 R4.1 Rev 3 Section 7.4.6.2 Page 50
Reference
'StopSubscribeEventgroup entry' (SHOULD)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 941
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 942
OPEN Alliance
The Service-Instance-IDs of 0x0000 and 0xFFFF shall not be used for a service,
Synopsys
since 0x0000 is reserved and 0xFFFF is used to describe all service instances.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- SOME/IP Find Service Entry Service Instance ID set to
0xFFFF
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
Test Procedure - Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- Service Instance ID of Offer Service Entry 1 is not set
to 0
- Service Instance ID of Offer Service Entry 1 is not set
to
0xFFFF
6. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message contains:
Pass Criteria - Service Instance ID of Offer Service Entry 1 is not set to 0
- Service Instance ID of Offer Service Entry 1 is not set to
0xFFFF
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.1
Reference
Definition of Identifiers [TR_SOMEIP_00008] Page 14 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 943
OPEN Alliance
Methods shall use Method-IDs with the highest bit set to 0, while the Method-IDs
Synopsys highest bit shall be set to 1 for events and notifications of fields. NOTE: Checking
for notification.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Verify that received SOME/IP Notification Message
contains:
- SOMEIP Expected Number Of IPv4 Endpoint Option is
greater
than or equal to 1
6. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Test Procedure Transport Port to <extractedport>
7. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
8. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 944
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 945
OPEN Alliance
For the response and error message the IP addresses and port number of the
Synopsys transport protocol shall match the request message. NOTE: Checking for Response
message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
Test Procedure - SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Message Expected IP Src Address set to
<SERVER1-IP-ADDR>
- SOME/IP Message Expected IP Dst Address set to
<CLIENT1-IP-ADDR>
- SOME/IP Message Expected UDP Src Port set to
<SERVICE-ID-1-UDP-PORT>
- SOME/IP Message Expected UDP Dest Port set to
<CLIENT1-UDP-PORT>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
Pass Criteria 4. DUT: Sends SOME/IP Notification Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 946
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 947
OPEN Alliance
With 16 Bit Service-ID and a 16 Bit Method-ID starting with a 0-Bit, this allows
Synopsys for up to 65536 services with up to 32768 methods each. NOTE: Checking for 0 bit
in MSB of Method ID in Response Message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
Test Procedure <DIface-0> containing :
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: Verify that received SOME/IP Response Message contains:
- 0-Bit field of Method/EventID in SOME/IP Packet Header is
set to 0
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Response Message
Pass Criteria 8. TESTER: Verify that received SOME/IP Response Message contains:
- 0-Bit field of Method/EventID in SOME/IP Packet Header is
set to 0
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.2.1
Reference
Structure of the Message ID [TR_SOMEIP_00038] Page 18 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 948
OPEN Alliance
When generating a response message, the server has to copy the Request ID from
Synopsys
the request to the response message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT
through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
Test Procedure <CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: Verify that received SOME/IP Response Message
contains:
- SOME/IP Packet Expected Header Request ID is set to
<CLIENT1-CURR-REQUEST-ID>
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Response Message
Pass Criteria 8. TESTER: Verify that received SOME/IP Response Message contains:
- SOME/IP Packet Expected Header Request ID is set to
<CLIENT1-CURR-REQUEST-ID>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 949
OPEN Alliance
Request IDs might be reused as soon as the response arrived or is not expected to
Synopsys
arrive anymore (timeout). NOTE: Testing first condition where response arrived.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
Test Procedure <SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 950
OPEN Alliance
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
10. DUT: Sends SOME/IP Response Message
11. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 7. DUT: Sends SOME/IP Response Message
10. DUT: Sends SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.4
Reference
Request ID [32 Bit] [TR_SOMEIP_00044] Page 19 (MUST)
Notes
Protocol Version is an 8 Bit field containing the SOME/IP protocol version, which
Synopsys
currently shall be set to 0x01.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Test Procedure - Protocol Version set to 0x01
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Protocol Version set to 0xFF
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 951
OPEN Alliance
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_WRONG_PROTOCOL_VERSION
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
8. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Protocol Version set to 0x01
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Protocol Version set to 0x01
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
10. DUT: Sends SOME/IP Response Message
11. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
10. DUT: Sends SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.5
Reference
Protocol Version [8 Bit] [TR_SOMEIP_00052] Page 20 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 952
OPEN Alliance
Interface Version is an 8 Bit field that contains the Major Version of the Service
Synopsys
Interface.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
Test Procedure <SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: Verify that received SOME/IP Response Message contains:
- Interface Version is set to <SERVICE-ID-1-INTF-VER-MAJ>
9. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<UNKNOWN-INTF-VER-MAJ-SI-1>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 953
OPEN Alliance
<METHOD-ID-1-SI-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Interface Version set to <UNKNOWN-INTF-VER-MAJ-SI-1>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_WRONG_INTERFACE_VERSION
11. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
12. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Response Message
Pass Criteria 8. TESTER: Verify that received SOME/IP Response Message contains:
- Interface Version is set to <SERVICE-ID-1-INTF-VER-MAJ>
11. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.6
Reference
Interface Version [8 Bit] [TR_SOMEIP_00053] Page 20 (MUST)
Notes
The Message Type field is used to differentiate different types of messages and shall
contain the following values. 0x00 REQUEST A request expecting a response (even
Synopsys
void). 0x80 RESPONSE The response message. NOTE: Testing Response message
after sending a request.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
Test - Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 954
OPEN Alliance
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Interface Version set to <SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.7
Reference
Message Type [8 Bit] [TR_SOMEIP_00055] Page 20 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 955
OPEN Alliance
The Message Type field is used to differentiate different types of messages and
Synopsys shall contain the following values. 0x01 REQUEST_NO_RETURN A fire&forget
request.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOMEIP_MSG_TYPE_REQUEST_NO_RETURN
Message
to DUT through <DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
Test Procedure <CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Does not send SOME/IP Response Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Does not send SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.7
Reference
Message Type [8 Bit] [TR_SOMEIP_00055] Page 20 (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 956
OPEN Alliance
The Message Type field is used to differentiate different types of messages and
Synopsys shall contain the following values. 0x40 REQUEST_ACK Acknowledgment for
REQUEST (optional).
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
Test Procedure <CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOMEIP_MSG_TYPE_REQUEST_ACK Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOMEIP_MSG_TYPE_REQUEST_ACK Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.7
Reference
Message Type [8 Bit] [TR_SOMEIP_00055] Page 20 (MAY)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 957
OPEN Alliance
The Message Type field is used to differentiate different types of messages and
Synopsys shall contain the following values. 0x81 ERROR The response containing an error.
NOTE: Checking for error UNKNOWN Service ID.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
Test Procedure - SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<UNKNOWN-SERVICE-ID>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 958
OPEN Alliance
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <UNKNOWN-SERVICE-ID>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_UNKNOWN_SERVICE
10. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
11. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 7. DUT: Sends SOME/IP Response Message
10. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.7
Reference
Message Type [8 Bit] [TR_SOMEIP_00055] Page 20 (MUST)
Notes
The Return Code is used to signal whether a request was successfully been
Synopsys processed. NOTE: Checking for Normal Request Response Communication i.e.
Error Code E_OK.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
Test Procedure 0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 959
OPEN Alliance
<METHOD-ID-1-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
7. DUT: Sends SOME/IP Response Message
8. TESTER: Verify that received SOME/IP Response Message contains:
- Return Code is set to SOMEIP_RET_CODE_E_OK
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
7. DUT: Sends SOME/IP Response Message
Pass Criteria
8. TESTER: Verify that received SOME/IP Response Message contains:
- Return Code is set to SOMEIP_RET_CODE_E_OK
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.2.3.8
Reference Return Code [8 Bit] [TR_SOMEIP_00058, TR_SOMEIP_00191] Page 21
(MUST)
Notes
The Return Code is used to signal whether a request was successfully been
Synopsys processed. NOTE: Checking for Error in case of Unknown Method ID in Request
Response Communication i.e. Error Code E_UNKNOWN_METHOD.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
Test - Service ID in Entry Array set to <SERVICE-ID-1>
Procedure 3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 960
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 961
OPEN Alliance
The client and server shall use a single TCP connection for all methods, events,
Synopsys
and notifications of a service instance. NOTE: This test is for methods.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
Test Procedure <CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-2>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-2>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-2>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-2>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.1.2 TCP
Reference
Binding [TR_SOMEIP_00150] Page 33 (MUST)
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 962
OPEN Alliance
Notes
The client and server shall use a single TCP connection for all methods, events,
Synopsys
and notifications of a service instance. NOTE: This test is for Notifications.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-2>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6.
7. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
Test Procedure <DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-2>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-2>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
8. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-2>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-2>
9. DUT: Sends SOME/IP Notification Message
10.
11. DUT CONFIGURE: Trigger Event on <DIface-0> with the following
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 963
OPEN Alliance
informations
- Event ID : <EVENT-ID-1-EG-ID-2>
- Event Group ID : <EVENT-GROUP-ID-1-SI-2>
- Service ID : <SERVICE-ID-2>
12. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-2>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-2>
13. DUT: Sends SOME/IP Notification Message
14. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 9. DUT: Sends SOME/IP Notification Message
13. DUT: Sends SOME/IP Notification Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.1.2 TCP
Reference
Binding [TR_SOMEIP_00150] Page 33 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 964
OPEN Alliance
The getter of a field shall be a request/response call that has an empty payload in
Synopsys the request message and the value of the field in the payload of the response
message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
Test Procedure - SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-GET-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-GET-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
7. DUT: Sends SOME/IP Response Message
8. TESTER: Extracts the content of SOME/IP Packet Length to
<extractedPktLen>
9. TESTER: Verify that received SOME/IP Response Message contains:
- SOME/IP Expected Response Message Payload is set to
<METHOD-ID-GET-SI-1-RESP-PAYLOAD-SERIALIZED>
10. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
Pass Criteria 4. DUT: Sends SOME/IP Notification Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 965
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 966
OPEN Alliance
Fire & Forget messages shall not return an error. The system shall not return an
Synopsys
error message for fire&forget methods.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Test Procedure 5. TESTER: <CLIENT-1> Sends SOMEIP_MSG_TYPE_REQUEST_NO_RETURN
Message
to DUT through <DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<UNKNOWN-METHOD-ID-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 967
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 968
OPEN Alliance
SOMEIPSRV_RPC_07: Ignore the two most significant bits from return code
The receiver of a return code shall ignore the values of the two most significant
Synopsys
bits.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
Test Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT
through
<DIface-0> containing :
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 969
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 970
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 971
OPEN Alliance
For request/response methods the error message shall copy over the fields of the
SOME/IP header (i.e. Message ID, Request ID, and Interface Version) but not the
Synopsys
payload. In addition Message Type and Return Code have to be set to the
appropriate values. NOTE: Checking for No Payload in Error message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
Test <SERVICE-ID-1-INTF-VER-MAJ>
Procedure - SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<UNKNOWN-METHOD-ID-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <UNKNOWN-METHOD-ID-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_UNKNOWN_METHOD
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
8. TESTER: Verify that received SOMEIP_MSG_TYPE_ERROR Message
contains:
- SOME/IP Packet Header Length is set to 8
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 972
OPEN Alliance
The system shall not return an error message for events/notifications and
Synopsys fire&forget methods if the Message Type is set incorrectly to Request or Response.
NOTE: Checking for Fire and Forget Method.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
Test Procedure - SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-FIRE-FORGET-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to
<METHOD-ID-FIRE-FORGET-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_NOT_OK
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 973
OPEN Alliance
The setter of a field shall be a request/response call that has the desired valued of
Synopsys the field in the payload of the request message and the value that was set to field in
the payload of the response message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
Test Procedure <DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-2-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-2-SI-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 974
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 975
OPEN Alliance
The notifier shall send an event message that transports the value of a field on
Synopsys
change and follows the rules for events.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
Test Procedure - Service ID in Subscribe Eventgroup Entry set to
<SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set
to
extractedInstID1
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
8. DUT: Sends SOME/IP Notification Message
9. DUT CONFIGURE: Trigger Event on <DIface-0> with the following
informations
- Event ID : <EVENT-ID-1-EG-ID-1>
- Event Group ID : <EVENT-GROUP-ID-1-SI-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 976
OPEN Alliance
- Service ID : <SERVICE-ID-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-1>
11. DUT: Sends SOME/IP Notification Message
12. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 8. DUT: Sends SOME/IP Notification Message
11. DUT: Sends SOME/IP Notification Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.5 Fields
Reference
[TR_SOMEIP_00183] Page 38 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 977
OPEN Alliance
While different Services shall be able to share the same port number of the transport
layer protocol used, multiple Service-Instances of the same service on one single
Synopsys
ECU shall listen on different ports per Service-Instance. NOTE: Checking For case -
Different Services same port.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-2>
- Number Of Instances : 1
3. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
- Service ID in Entry Array set to <SERVICE-ID-2>
4. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Test - Service ID in Entry Array set to <SERVICE-ID-1>
Procedure - Service ID in Entry Array set to <SERVICE-ID-2>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_ENDPOINT
- SOMEIP Expected Number Of IPv4 Endpoint Option set to 1
5. DUT: Sends SOME/IP Notification Message
6. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Transport Port to <extractedTransPort>
7. TESTER: Set Destination Port Of client1 to extractedTransPort
8. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
9. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 978
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 979
OPEN Alliance
SOMEIPSRV_RPC_14: Different instances of the same service must use different ports
While different Services shall be able to share the same port number of the transport
layer protocol used, multiple Service-Instances of the same service on one single
Synopsys
ECU shall listen on different ports per Service-Instance. NOTE: Checking For case -
Different instances of same Service different port.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 2
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Expected Offer Services' Service ID set to <SERVICE-ID-1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_ENDPOINT
- SOMEIP Expected Number Of IPv4 Endpoint Option set to 2
- Number Of Expected Offer Service Entries set to 2
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Test Entry 2 to <extractedInstID2>
Procedure 6. TESTER: Verify that received SOME/IP Notification Message
contains:
- Service Instance ID of Offer Service Entry 1 is not set to
extractedInstID2
7. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Number 1
Transport Port to <extractedTransPort1>
8. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Number 2
Transport Port to <extractedTransPort2>
9. TESTER: Set Destination Port Of client1 to extractedTransPort1
10. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 980
OPEN Alliance
<METHOD-ID-1-SI-1>
11. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
12. DUT: Sends SOME/IP Response Message
13. TESTER: Set Destination Port Of client1 to extractedTransPort2
14. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-2-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<METHOD-ID-1-SI-1>
15. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <METHOD-ID-1-SI-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
16. DUT: Sends SOME/IP Response Message
17. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
6. TESTER: Verify that received SOME/IP Notification Message contains:
- Service Instance ID of Offer Service Entry 1 is not set to
Pass Criteria
extractedInstID2
12. DUT: Sends SOME/IP Response Message
16. DUT: Sends SOME/IP Response Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.1.3
Reference
Multiple Service-Instances [TR_SOMEIP_00163] Page 35 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 981
OPEN Alliance
Synopsys Update on change - send an update as soon as a "value" changes (e.g. door open)
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
Test Procedure <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
8. DUT: Sends SOME/IP Notification Message
9. DUT CONFIGURE: Trigger Event on <DIface-0> with the following
informations
- Event ID : <EVENT-ID-1-EG-ID-1>
- Event Group ID : <EVENT-GROUP-ID-1-SI-1>
- Service ID : <SERVICE-ID-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 982
OPEN Alliance
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-1-EG-ID-1>
11. DUT: Sends SOME/IP Notification Message
12. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria 8. DUT: Sends SOME/IP Notification Message
11. DUT: Sends SOME/IP Notification Message
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.4.1
Reference
Strategy for sending notifications [TR_SOMEIP_00176] Page 37 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 983
OPEN Alliance
Synopsys Cyclic update - send an updated value in a fixed interval (e.g. every 300 ms)
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Entry 1 to <extractedInstID1>
6. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE
- Service ID in Subscribe Eventgroup Entry set to
Test Procedure <SERVICE-ID-1>
- EventGroup ID in Subscribe Eventgroup Entry set to
<EVENT-GROUP-ID-1-SI-1>
- Service Instance ID in Subscribe Eventgroup Entry set to
extractedInstID1
7. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-
0>
- Entry Type set to SOMEIP_ENTRY_SUBSCRIBE_ACK
- SOME/IP Expected Service ID in Subscribe EventGroup Ack
Entry set to <SERVICE-ID-1>
- SOME/IP Expected Service Instance ID in Subscribe
EventGroup Ack Entry set to extractedInstID1
- SOME/IP Expected EventGroup ID in Subscribe EventGroup
Ack
Entry set to <EVENT-GROUP-ID-1-SI-1>
8. DUT: Sends SOME/IP Notification Message
9. DUT CONFIGURE: Trigger Event on <DIface-0> with the following
informations
- Event ID : <EVENT-ID-2-EG-ID-1>
- Event Group ID : <EVENT-GROUP-ID-1-SI-1>
- Service ID : <SERVICE-ID-1>
10. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 984
OPEN Alliance
<DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Return Code set to SOMEIP_RET_CODE_E_OK
- SOME/IP Expected Event ID in SOME/IP Header set to
<EVENT-ID-2-EG-ID-1>
11. DUT: Sends 2 SOME/IP Notification Messages
12. TESTER: Verify that the time interval between
reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
(<EVENT-ID-2-EG-ID-1-CYCLIC-TIME> -
<ParamToleranceTimeMillisec>) micro second
13. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
8. DUT: Sends SOME/IP Notification Message
11. DUT: Sends 2 SOME/IP Notification Messages
12. TESTER: Verify that the time interval between
Pass Criteria reception of 1st SOME/IP Notification Message and 2nd
SOME/IP Notification Message
is greater than
(<EVENT-ID-2-EG-ID-1-CYCLIC-TIME> -
<ParamToleranceTimeMillisec>) micro second
Example for a Serialization Protocol (SOME/IP) V1.1.0 R4.1 Rev 3 s6.3.4.1
Reference
Strategy for sending notifications [TR_SOMEIP_00176] Page 37 (MUST)
Notes
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 985
OPEN Alliance
When having more than one instance of a service a TCP connection per services
Synopsys
instance is needed.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 2
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on
<DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Expected Offer Services' Service ID set to <SERVICE-ID-
1>
- SOMEIP Expected Type of Option set to
SOMEIP_OPTION_IPV4_ENDPOINT
- SOMEIP Expected Number Of IPv4 Endpoint Option set to 2
- Number Of Expected Offer Service Entries set to 2
4. DUT: Sends SOME/IP Notification Message
5. TESTER: Extracts the content of Service Instance ID of Offer
Service
Test Procedure Entry 2 to <extractedInstID2>
6. TESTER: Verify that received SOME/IP Notification Message
contains:
- Service Instance ID of Offer Service Entry 1 is not set
to
extractedInstID2
7. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Number 1
Transport Port to <extractedTransPort1>
8. TESTER: Extracts the content of SOMEIP IPv4 Endpoint Option
Number 2
Transport Port to <extractedTransPort2>
9. TESTER: Set Destination Port Of client1 to extractedTransPort1
10. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT
through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 986
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 987
OPEN Alliance
For request/response methods the error message shall copy over the fields of the
SOME/IP header (i.e. Message ID, Request ID, and Interface Version) but not the
Synopsys
payload. In addition Message Type and Return Code have to be set to the
appropriate values. NOTE: Checking For Message ID.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
Test <SERVICE-ID-1-INTF-VER-MAJ>
Procedure - SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<UNKNOWN-METHOD-ID-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- SOME/IP Packet Expected Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_UNKNOWN_METHOD
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
8. TESTER: Verify that received SOMEIP_MSG_TYPE_ERROR Message
contains:
- SOME/IP Expected Service ID is set to <SERVICE-ID-1>
- SOME/IP Expected Method ID is set to
<UNKNOWN-METHOD-ID-SI-1>
9. DUT CONFIGURE: Stop Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
Pass Criteria
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 988
OPEN Alliance
For request/response methods the error message shall copy over the fields of the
SOME/IP header (i.e. Message ID, Request ID, and Interface Version) but not the
Synopsys
payload. In addition Message Type and Return Code have to be set to the
appropriate values. NOTE: Checking For Request ID.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
Test <DIface-0> containing :
Procedure - SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
- SOME/IP Send Request Message Method ID set to
<UNKNOWN-METHOD-ID-SI-1>
6. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
- SOME/IP Expected Service ID set to <SERVICE-ID-1>
- SOME/IP Expected Method ID set to <UNKNOWN-METHOD-ID-SI-1>
- SOME/IP Expected Return Code set to
SOMEIP_RET_CODE_E_UNKNOWN_METHOD
7. DUT: Sends SOMEIP_MSG_TYPE_ERROR Message
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 989
OPEN Alliance
For request/response methods the error message shall copy over the fields of the
SOME/IP header (i.e. Message ID, Request ID, and Interface Version) but not the
Synopsys
payload. In addition Message Type and Return Code have to be set to the
appropriate values. NOTE: Checking For Interface Version.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Start Service on <DIface-0> with the following
informations
- Service ID : <SERVICE-ID-1>
- Number Of Instances : 1
2. TESTER: <CLIENT-1> Sends SOME/IP Notification Message to DUT
through
<DIface-0> containing :
- Entry Type set to SOMEIP_ENTRY_FIND_SERVICE
- Service ID in Entry Array set to <SERVICE-ID-1>
3. TESTER: <CLIENT-1> Listens (upto <ParamListenTime>) on <DIface-0>
Test - Entry Type set to SOMEIP_ENTRY_OFFER_SERVICE
Procedure - Service ID in Entry Array set to <SERVICE-ID-1>
4. DUT: Sends SOME/IP Notification Message
5. TESTER: <CLIENT-1> Sends SOME/IP Request Message to DUT through
<DIface-0> containing :
- SOME/IP Packet Send Header Request ID set to
<CLIENT1-CURR-REQUEST-ID>
- SOME/IP Packet Send Header Interface Version set to
<SERVICE-ID-1-INTF-VER-MAJ>
- SOME/IP Send Request Message Service ID set to
<SERVICE-ID-1>
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 990
OPEN Alliance
Restriction Level:
Public OPEN Alliance Automotive Ethernet ECU Test Specification | Jan-16 991