feat: added new information flow diagram

docs/patterns/connect&exchange/README.md

@@ -130,7 +130,8 @@ But in the end you will ALWAYS have applications or services behind the EDC whic
 
 The only thing that it creates is a "PIPE" in between the companies and the connection remains open.
 
-<!-- Specify what PIPE means with the a diagram-->
+![Connect and Exchange Pipe](./media/edc-connector-infoflow.svg)
+
 
 Using the EDR interface applications are able to negotiate assets from the catalog without needing to execute a transfer to retrieve the authorization. That was often a problem because the applications always required a "DNS resolvable domain" for the EDR token to be call backed into the application. But with the EDR interface now the application can be deployed in the local machine from the consumer or in a private infrastructure and there it can still interact with the EDC, retrieving data and communicating with the other EDC (provider). Using the EDR interface the EDC will keep the channel open until any of the conditions change, allowing data to be exchanged in a very efficient way.
 

docs/patterns/connect&exchange/media/edc-connector-infoflow.svg.license

@@ -0,0 +1,12 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2024, 2025 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
+