Interaction with: DHCP Server DNS Server NM GDS DNS Server NM CFS NM NM NM 126.96.36.199 MAR 2018 Visit us at stand 11.505 DS_DISCOVERY NAME DS_DEVICE_NAME Application specific state machine Preliminary Name Configured? Next stop: Moxa railway solutions … please exit here for reliability, robustness and speed. • EN50155/50121 compliance and IRIS certification for maximum quality • IP-based surveillance and security system • Networking and computing solutions with high-performance IP connectivity Convenient, safe, efficient – at any speed. www.moxa.com/rail Technology periodic transmission, to guarantee bandwidth reservations and bounded latency for certain traffic classes. The primary application is in audio/video broadcasting. IEEE 802.1Qcc: This standard provides specification of protocols, procedures and managed objects used for TSN configuration, mainly used in an already running system. Three configuration models are described: 1) Fully Centralized Model suitable for all TSN mechanisms and necessary when using Qbv 2) Fully Distributed Model suitable when no scheduled changes are needed 3) Centralized Network/Distributed User Model As isochronous traffic is often used in industrial networks, usage of the Qbv mechanism is inevitable, and thus we use the fully centralized configuration model. This model specifies the CUC (Centralized User Configuration) and the CNC (Centralized Network Configuration) functions. The CUC(s) specify user requirements regarding cycle times and transmitted process data and pass them to the CNC. The CNC calculates the TSN configuration including the communication schedules necessary to satisfy the requirements by using standardized YANG18 models. The CNC distributes the configuration to switches (bridges) by using a YANG-based management protocol (such as NETCONF over TLS). The CNC sends the endpoint configuration to the CUC. RESTCONF shall be used as the communication protocol between CUC and CNC. The CUC then appropriately distributes the endpoint configuration to the corresponding endpoints. IEEE 802.1CB: Used to provide seamless redundancy for ring and mesh topologies. .1CB allows redundancy planning on a per data stream basis, which enables much better bandwidth efficiency than legacy redundancy solutions. Further standards IEEE 802.1Qbu & IEEE 802.3br (optional): Frame preemption can be used to maximize throughput of besteffort traffic in case that scheduled (Qbv) mechanisms are being used. Preemption is not suitable for traffic types other than best-effort, as it invalidates any guarantees on those. In the case of Gigabit, the gain for best-effort is negligible, however. I E E E 8 0 2 . 1 C S (optional): Extension o f A V B ’ s s t r e a m reservation protocol is a project just started. It defines an alternative, currently not compatible, configuration path (aka the “fully distributed configuration model”) for applications with only type III traffic (and best-effort), and is hence of limited use for industrial applications. Summary Compulsory standards hence are .1AS(-Rev), Qbv, .1CB, and Qcc with fully centralized model plus NETCONF over TLS. AVnu Alliance members are defining the conformance and interoperability guidelines for implementation DS_DHCP DS_SECURITY DS_UPDATE DS_ACTIVATE DS_READY DS_APPLICATION e.g. AS_OPERATIONAL of these standards. Layers 3-6: For OPC UA Client/Server, TCP/ IP connections with optional security (TLS) are supported. For Pub/Sub connections, either UADP25 over UDP/IP or UADP directly over raw Ethernet are supported. Security is handled in the UADP layer. Other transport options for UADP (i.e. cloud protocols) fall outside scope. NETCONF also uses TCP/IP with TLS. HTTP(S) is optional for firmware updates and web applications on devices. Static IP Address? yes yes no no Depiction of OPC UA TSN in the OSI reference model.
Industrial Ethernet Book 105
To see the actual publication please follow the link above