Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 14543-3-2-07 (ISO/IEC 14543-3-2:2007) — Communication Protocol for Home Electronic Systems: MS/TP over IP
A Technical Guide to Understanding and Implementing the Master-Slave/Token-Passing Protocol over IP Networks
Scope and Purpose of IEC 14543-3-2-07
The standard ISO/IEC 14543-3-2:2007, commonly referred to as IEC 14543-3-2-07, is a fundamental element of the Home Electronic System (HES) architecture series. It defines the communication protocol for transmitting Master-Slave/Token-Passing (MS/TP) data frames over Internet Protocol (IP) networks. This standard enables the integration of field-level control networks with IP backbones, facilitating remote monitoring, control, and management in smart homes, buildings, and industrial environments.
Within the ISO/IEC 14543 multi-part framework, Part 3-2 specifies the protocol that encapsulates MS/TP frames into UDP segments, preserving the deterministic behavior of the original token-passing bus while leveraging IP infrastructure. The standard addresses:
- Frame format and encapsulation headers
- Address mapping between MS/TP addresses and IP addresses
- Timing constraints to maintain token rotation and response integrity
- Procedures for broadcast and multicast support
Applicable to building automation, home control, and industrial automation systems that rely on MS/TP variants (e.g., LonTalk, BACnet MS/TP), this standard fills a critical interoperability gap between legacy fieldbuses and modern IP networks.
Tip: When planning an HES deployment, verifying that the target MS/TP protocol (LonWorks, BACnet, etc.) explicitly references ISO/IEC 14543-3-2 ensures seamless encapsulation compatibility.
Technical Requirements and Protocol Specification
The protocol operates at the network layer of the HES architecture, directly encapsulating MS/TP frames into UDP datagrams. Key technical parameters are summarized in Table 1.
| Parameter | Specification |
|---|---|
| Transport protocol | UDP (IPv4 or IPv6) |
| Default UDP port | 4700 (optional, configurable per deployment) |
| Maximum frame size (MTU) | 1500 bytes (Ethernet); fragmentation handled by IP layer |
| Address mapping | Map 16‑bit MS/TP identifiers to IP addresses and UDP ports |
| Frame encapsulation header | 4 octets: version, flags, length field, option byte |
| Timing compliance | Token rotation time ≤ 500 ms; response timeout ≤ 20 ms |
| Broadcast/multicast | Yes – via IP multicast group (recommended) or directed broadcast |
| Security | Not specified in the standard; implement IPsec, TLS, or application-layer security |
The encapsulation header indicates the version of the protocol and carries flags to manage segmentation (if the MS/TP frame exceeds the path MTU). The standard mandates that all implementations support a minimum reassembly buffer of 1500 bytes.
Addressing and Frame Delivery
Each HES device on the IP network is uniquely identified by its IP address and UDP port. The address mapping function (optional but recommended) translates between local 16‑bit MS/TP addresses and their corresponding IP endpoints. The standard supports three delivery modes:
- Unicast: Point-to-point transmission to a single IP destination.
- Multicast: Efficient delivery to all devices belonging to a predefined group (preferred for broadcast frames).
- Broadcast: Limited broadcast to all devices on the same subnet (fallback when multicast not available).
Warning: Maintaining timing constraints over IP requires careful network engineering. Excessive latency, jitter, or packet loss can cause token timeouts and disrupt MS/TP deterministic behavior. Use dedicated VLANs or QoS marking when deploying in converged networks.
Implementation Highlights for MS/TP over IP Gateways
Successful deployment of systems conforming to IEC 14543-3-2-07 hinges on proper gateway design and protocol integration. The following aspects are critical.
Gateway Architecture
A typical gateway bridges one or more MS/TP fieldbus segments with an IP network. It performs encapsulation/decapsulation, address translation, and token management. The gateway must buffer MS/TP frames awaiting IP transmission and handle retries for lost UDP packets.
Token Management and Determinism
Because MS/TP relies on a token for bus access, the gateway must emulate the token passing scheme when dealing with remote devices. This is usually achieved by creating a “virtual token” that circulates among the gateway and its local MS/TP nodes. The standard does not prescribe an exact algorithm but requires that the token rotation time on the local MS/TP segment remain within the original timing bounds.
Interoperability Testing
Gateways from different manufacturers should be tested together using conformance test suites defined by ISO/IEC 14543-3-2:2007. The standard includes a Protocol Implementation Conformance Statement (PICS) template to document supported options. Key interoperability checkpoints include:
- Correct encapsulation and decapsulation of MS/TP data
- Address mapping consistency across multiple gateways
- Token timing preservation under various IP network loads
- Handling of broadcast and multicast frames
Success Story: A large European building automation project integrated LonWorks MS/TP devices across six buildings using a municipal IP backbone. By strictly following the timing and encapsulation rules of IEC 14543-3-2-07, engineers achieved a token rotation time of 180 ms (well under the 500 ms limit) with zero packet loss over three years of operation.
Compliance and Certification Requirements
Compliance with IEC 14543-3-2-07 is typically voluntary unless specified by project contracts or local regulations. For Canada, the standard is adopted as CAN/CSA‑ISO/IEC 14543‑3‑2‑07, making compliance mandatory for certain government or public‑sector projects.
Testing and Certification
Conformance testing verifies that an implementation matches the PICS and passes a set of standardised test cases covering:
- Encapsulation header format and parsing
- Address mapping functions
- Timing behavior (token rotation, response delays)
- Multicast/broadcast delivery
- Error handling and recovery
Certification is performed by accredited laboratories that comply with ISO/IEC 17025. After passing, products can display the CSA certification mark for the Canadian market or the ISO/IEC conformity mark globally.
Consequences of Non‑Compliance
Devices that do not conform to the standard may cause network instability, communication black holes, and in safety‑critical systems, may lead to hazardous conditions. For example, improper handling of the token timing could result in a “token‑loss” scenario that halts all MS/TP communication on that segment.
Danger: In life‑safety applications (e.g., fire alarm or emergency lighting networks), non‑compliant MS/TP over IP implementations can delay critical messages, potentially violating local safety codes. Always ensure the full communication chain is certified against IEC 14543-3-2-07.
The standard is maintained by ISO/IEC JTC 1/SC 25 (Interconnection of information technology equipment). Users and implementers should monitor amendments or corrigenda issued after the 2007 edition to stay current.
Frequently Asked Questions
Q: What is the primary application of IEC 14543-3-2-07?
A: It is used in building automation, home automation, and smart grid systems to integrate legacy MS/TP fieldbuses (such as LonWorks or BACnet MS/TP) with IP networks, allowing remote control, monitoring, and data exchange over standard Ethernet infrastructure.
A: It is used in building automation, home automation, and smart grid systems to integrate legacy MS/TP fieldbuses (such as LonWorks or BACnet MS/TP) with IP networks, allowing remote control, monitoring, and data exchange over standard Ethernet infrastructure.
Q: Does the standard include security mechanisms?
A: No, IEC 14543-3-2-07 does not specify security features. Implementers are encouraged to use IPsec, TLS, or application‑layer authentication/encryption to protect transmission integrity and confidentiality.
A: No, IEC 14543-3-2-07 does not specify security features. Implementers are encouraged to use IPsec, TLS, or application‑layer authentication/encryption to protect transmission integrity and confidentiality.
Q: Is IEC 14543-3-2-07 compatible with BACnet MS/TP?
A: Yes, because BACnet MS/TP is a profile of the general MS/TP protocol (carried over EIA‑485). The encapsulation and timing rules in this standard are applicable to any MS/TP frame, including those of BACnet. However, check additional BACnet‑specific requirements (e.g., BACnet/IP tunneling) that may also apply.
A: Yes, because BACnet MS/TP is a profile of the general MS/TP protocol (carried over EIA‑485). The encapsulation and timing rules in this standard are applicable to any MS/TP frame, including those of BACnet. However, check additional BACnet‑specific requirements (e.g., BACnet/IP tunneling) that may also apply.
Q: What does “HES” stand for?
A: HES stands for Home Electronic System, the family of standards defined in ISO/IEC 14543 that covers the architecture, communication protocols, and interoperability requirements for electronic systems in homes and buildings.
A: HES stands for Home Electronic System, the family of standards defined in ISO/IEC 14543 that covers the architecture, communication protocols, and interoperability requirements for electronic systems in homes and buildings.
© 2026 – IEC 14543-3-2-07 Technical Article. All rights reserved.