ADTF  v2.14.3
ADTF UDP Network

Simple ADTF UDP Control Protocol

The UDP Packages described in ADTF UDP Extension are used to communicate within the ADTF UDP Network. The ADTF UDP Network is one possibility to establish connections between ADTF and non-ADTF systems. An ADTF UDP Network is organized through a simple channel-based Server-Client Configuration.

There are 4 roles an ADTF UDP Network participant can have:

  1. Simple ADTF UDP Sender
  2. Simple ADTF UDP Receiver
  3. ADTF UDP Channel Client
  4. ADTF UDP Channel Server

To configure connections between an ADTF system, which contains an ADTF Filtergraph Manager, to a non-ADTF system you have to use the Untyped Communication. See the description on ADTF FilterGraph Manager uses the Message Bus Service.

The communication as an ADTF UDP Sender

  • ADTF UDP Sender will only send data to another participant within the network
  • The connection can only be a direct point-2-point
  • The used UDP packages can be the tADTFDXUDPHeader, tADTFDXUDPHeaderASync
Use case: Sending data as ADTF UDP Sender to an ADTF UDP Channel Server

The illustration shows:

  • the sender sends messages with no message identifier to the port 5000 of an ADTF UDP Channel Server
  • the sender sends messages with the message identifier "msg_raw" to the port 5000 of an ADTF UDP Channel Server


messagebus_udp_network_sender.png
Principal of UDP Sender

If you use the ADTF Filtergraph Manager on the ADTF System you should only use ASYNC UDP Packages (tADTFDXUDPHeaderASync).

The communication as an ADTF UDP Receiver

  • ADTF UDP Receiver will only receive data from another participant within the network
  • The connection can only be a direct point-2-point
  • The used UDP packages can be the tADTFDXUDPHeader or tADTFDXUDPHeaderASync
  • The network partner can be an ADTF UDP Sender or an ADTF UDP Channel Client
Use case: Receiving data as ADTF UDP Receiver

The illustration shows:

  • the receiver gets messages with no message identifier on the port 5000
  • the receiver gets messages with the message identifier "msg_raw" on the port 5000


messagebus_udp_network_receiver.png
Principal of UDP Receiver

If you use the ADTF Filtergraph Manager on the ADTF System you will only get ASYNC UDP Packages (tADTFDXUDPHeaderASync).

The communication as an ADTF UDP Client

Use case: Establish a connection as ADTF UDP Channel Client

The illustration shows:

  • the ADTF UDP Channel Server listens to the port 5000
  • the ADTF UDP Channel Server expects the client listening to 5001
  • the port number pair can also configured to a different port number set (i.e. 6666 and 6667)
  • the client starts a connection by sending an ASYNC message with no data area (ui32MsgSize == 0) and the message identifier "subscribe"
  • the client will get an ASYNC message "subscribed" from the server as answer
  • the client sends ASYNC "subscribe" as long as it did not receive the ASYNC "subscribed"
  • the client sends messages with the message identifier "msg_raw" to the port 5000 of the server
  • the client can receive ASYNC messages (i.e. in this case the ASYNC "msg2_raw") on port 5001


messagebus_udp_network_client_1.png
Principal of UDP Client - ASYNC
Use case: SYNC connection as ADTF UDP Channel Client

The illustration shows:

  • the port number pair can also be configured to a different port number set (i.e. 6666 and 6667)
  • the client sends a SYNC message "msg_raw" where the requested message for the answer is "msg_raw_reply"
  • the server will send an ASYNC "msg_raw_reply" as answer to the SYNC message
  • the client wants to stop connection and sends ASYNC "unsubscribe"
  • the server responds "unsubscribed"


messagebus_udp_network_client_2.png
Principal of UDP Client - SYNC

Additional Task as an ADTF UDP Channel Server

Use case: Share Messages coming from an ADTF UDP Channel Client

The illustration shows:

  • the ADTF UDP Channel Server listens to the port 5000
  • the ADTF UDP Channel Server expects all clients listening to 5001
  • the port number pair can also be configured to a different port number set (i.e. 6666 and 6667)
  • one client will send an ASYNC "msg_raw" to the server
  • the server will provide this data to the "msg_raw" pin of the remote subgraph
  • the server will share this ASYNC "msg_raw" to all other subscribed clients


messagebus_udp_network_server_1.png
Principal of

ADTF UDP Channel Server - Sharing messages

Use case: Share Message which will be send on the Channel

The illustration shows:

  • the ADTF Filtergraph Manager will send a "msg_raw" on the channel
  • the server will share this ASYNC "msg_raw" to all other subscribed clients


messagebus_udp_network_server_2.png
Principal of

ADTF UDP Channel Server - Sharing messages


Copyright © Audi Electronics Venture GmbH. All rights reserved. (Generated on Fri Mar 22 2019 by doxygen 1.8.10)