0% found this document useful (0 votes)
226 views11 pages

OA - Automotive - Ethernet - ECU - TestSpecification - Layer - 3-7 - v3.0 - Final-210-220

The document describes tests to verify that a user interface for UDP allows: 1. Creation of new receive ports 2. Receive operations that return data octets and source port/address indications 3. Operations to send datagrams specifying data, source and destination ports/addresses Specifically, it provides test procedures to verify that the interface allows specifying source and destination ports and addresses when sending datagrams, and returns source port, address, and data when receiving datagrams. The tests are only run if the DUT supports dynamic interfaces.

Uploaded by

yaoqinran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
226 views11 pages

OA - Automotive - Ethernet - ECU - TestSpecification - Layer - 3-7 - v3.0 - Final-210-220

The document describes tests to verify that a user interface for UDP allows: 1. Creation of new receive ports 2. Receive operations that return data octets and source port/address indications 3. Operations to send datagrams specifying data, source and destination ports/addresses Specifically, it provides test procedures to verify that the interface allows specifying source and destination ports and addresses when sending datagrams, and returns source port, address, and data when receiving datagrams. The tests are only run if the DUT supports dynamic interfaces.

Uploaded by

yaoqinran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

OPEN Alliance

5.6.5.5 User Interface

UDP_USER_INTERFACE_01: User Interface - New Receive Port


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to create 10 receive ports on <DIface-0>
Test 2. DUT: Create 10 receive ports on <DIface-0>
Procedure 3. TESTER: Verify using Upper Tester that application layer of DUT has created 10
receive ports on <DIface-0>
2. DUT: Create 10 receive ports on <DIface-0>
Pass Criteria 3. TESTER: Verify using Upper Tester that application layer of DUT has created 10
receive ports on <DIface-0>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 210
OPEN Alliance

UDP_USER_INTERFACE_02: User Interface - Data octets


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to listen on port <unusedUDPDstPort1>
on <DIface-0>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
3. TESTER: <HOST-1> Sends Message to DUT through <DIface-0>
Test containing:
Procedure - Destination UDP Port field set to <unusedUDPDstPort1>
- UDP send data set to <UDPDefaultData>
4. TESTER: Verify using Upper Tester that application layer has got
UDP Message containing:
- UDP data equal to <UDPDefaultData>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
4. TESTER: Verify using Upper Tester that application layer has got
Pass Criteria
UDP Message containing:
- UDP data equal to <UDPDefaultData>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 211
OPEN Alliance

UDP_USER_INTERFACE_03: User Interface – Return Source Port


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to listen on port <unusedUDPDstPort1>
on <DIface-0>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
3. TESTER: <HOST-1> Sends Message to DUT through <DIface-0>
Test containing:
Procedure - Source UDP Port field set to <unusedUDPSrcPort>
- Destination UDP Port field set to <unusedUDPDstPort1>
4. TESTER: Verify using Upper Tester that DUT received
UDP Message containing:
- UDP Source Port field set to <unusedUDPSrcPort>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
4. TESTER: Verify using Upper Tester that DUT received
Pass Criteria
UDP Message containing:
- UDP Source Port field set to <unusedUDPSrcPort>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 212
OPEN Alliance

UDP_USER_INTERFACE_04: User Interface – Return Source IP Address


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to listen on port <unusedUDPDstPort1>
on <DIface-0>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
3. TESTER: <HOST-1> Sends Message to DUT through <DIface-0>
Test containing:
Procedure - Source IP Address field set to <AIface-0-IP>
- Destination UDP Port field set to <unusedUDPDstPort1>
4. TESTER: Verify using Upper Tester that application layer received
an IP Packet containing a UDP Message containing:
- IP source address equal to <AIface-0-IP>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
4. TESTER: Verify using Upper Tester that application layer received
Pass Criteria
UDP Message containing:
- UDP source address equal to <AIface-0-IP>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 213
OPEN Alliance

UDP_USER_INTERFACE_05: User Interface - Source Port (to be sent)


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
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
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 214
OPEN Alliance

UDP_USER_INTERFACE_06: User Interface - Destination Port (to be sent)


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Externally cause DUT to send a UDP Message with destination
port set to <testerUDPPort> 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:
- Destination UDP Port field is set to <testerUDPPort>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received UDP Message contains:
- Destination UDP Port field is set to <testerUDPPort>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 215
OPEN Alliance

UDP_USER_INTERFACE_07: User Interface - Source IP Address (to be sent)


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Externally cause DUT to send a UDP Message with source
address set to <DIface-0-IP> 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 IP Address field is set to <DIface-0-IP>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received UDP Message contains:
- Source IP Address field is set to <DIface-0-IP>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 216
OPEN Alliance

UDP_USER_INTERFACE_08: User Interface - Destination Address (to be sent)


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
Synopsis
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]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. TESTER: Externally cause DUT to send a UDP Message with destination
address set to <AIface-0-IP> 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 IP Packet containing a UDP Message containing:
- Destination IP Address field is set to <AIface-0-IP>
3. DUT: Sends Message
Pass Criteria 4. TESTER: Verify that received IP Packet containing a UDP Message containing:
- Destination IP Address field is set to <AIface-0-IP>
Test Iterations
Notes Derived from RFC 768 Page 2 'User Interface' (MUST)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 217
OPEN Alliance

5.6.5.6 Introduction

UDP_INTRODUCTION_01: Introduction – Broadcast Destination Address (optional)


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.
Synopsis
[Note: In this test we verify that DUT will deny UDP message with broadcast destination
Address. Note: this test inverts the RFC requirement due to security negotiations]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to listen on port <unusedUDPDstPort1>
on <DIface-0>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
3. TESTER: <HOST-1> Sends Message to DUT through <DIface-0>
Test containing:
Procedure - Destination IP Address field set to <AIface-0-BcastIP>
- Destination UDP Port field set to <unusedUDPDstPort1>
4. TESTER: Verify using Upper Tester that application layer did not receive UDP Message
containing:
- destination address equal to <AIface-0-BcastIP>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
4. TESTER: Verify using Upper Tester that application layer did not receive UDP Message
Pass Criteria
containing:
- destination address equal to <AIface-0-BcastIP>
Test Iterations
Notes Derived from RFC 1122 Section 4.1.1 Page 77 'Introduction' (SHOULD)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 218
OPEN Alliance

UDP_INTRODUCTION_02: Introduction – Multicast Destination Address (optional)


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.
Synopsis
[Note: In this test we verify that DUT will deny UDP message with multicast destination
Address. Note: this test inverts the RFC requirement due to security negotiations]
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. DUT CONFIGURE: Externally cause DUT to listen on port <unusedUDPDstPort1>
on <DIface-0>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
3. TESTER: <HOST-1> Sends Message to DUT through <DIface-0>
Test containing:
Procedure - Destination IP Address field set to <allSystemMCastAddr>
- Destination UDP Port field set to <unusedUDPDstPort1>
4. TESTER: Verify using Upper Tester that application layer did not receive UDP Message
containing:
- destination address equal to <allSystemMCastAddr>
2. DUT: Listen on port <unusedUDPDstPort1> on <DIface-0>
4. TESTER: Verify using Upper Tester that application layer did not receive UDP Message
Pass Criteria
containing:
- destination address equal to <allSystemMCastAddr>
Test Iterations
Notes Derived from RFC 1122 Section 4.1.1 Page 77 'Introduction' (SHOULD)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 219
OPEN Alliance

UDP_INTRODUCTION_03: Introduction – Pending Listen Call


If a datagram arrives addressed to a UDP port for which there is no pending LISTEN call,
Synopsis
UDP SHOULD send an ICMP Port Unreachable message.
Prerequisites Check section prerequisites
Test setup Topology 1
Test Input
Check section general Input Parameters
Parameters
1. TESTER: <HOST-1> Sends Message to DUT through <DIface-0> containing:
- Destination IP Address field set to <DIface-0-IP>
Test Procedure - Destination UDP Port field set to <unusedUDPDstPort1>
2. TESTER: <HOST-1> Listens (up to<ParamListenTime>) on <DIface-0>
3. DUT: Sends <ICMP-Dest-Unrchbl> Message
Pass Criteria 3. DUT: Sends <ICMP-Dest-Unrchbl> Message
Test Iterations
Notes Derived from RFC 1122 Section 4.1.3.1 Page 77 'Ports' (SHOULD)

Restriction Level: OPEN Technical Members Only


OPEN Alliance Automotive Ethernet ECU Test Specification Layer 3-7 May-20 220

You might also like