- 1. Introduction
- 2. What Is GOOSE Communication?
- 3. What Is MMS Communication?
- 4. Main Technical Differences Between GOOSE and MMS
- 5. Communication Architecture: Layer 2 vs TCP/IP
- 6. Communication Speed and Performance
- 7. Practical Application: GOOSE for Protection Interlocking
- 8. Practical Application: MMS for SCADA Monitoring
- 9. Can GOOSE and MMS Be Used Together?
- 10. Dataset Engineering: GOOSE vs MMS
- 11. GOOSE and MMS Control Blocks
- 12. Network Configuration for GOOSE and MMS
- 13. Wireshark Analysis: GOOSE vs MMS
- 14. Common GOOSE Problems
- 15. Common MMS Problems
- 16. Engineering MiCOM Relays for GOOSE and MMS
- 17. Choosing Between GOOSE and MMS
- 18. Cybersecurity Considerations
- 19. Practical Commissioning Checklist
- 20. Conclusion
- 21. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
IEC 61850 provides standardized communication services for protection, control, monitoring and substation automation.
Two of its most important communication mechanisms are:
- GOOSE (Generic Object-Oriented Substation Event): Used for fast event-driven communication between IEDs.
- MMS (Manufacturing Message Specification): Used for client-server communication, data access, reporting and control.
Both communication mechanisms are widely used in modern digital substations. However, they have different architectures, communication methods, engineering requirements and applications.
For engineers working with MiCOM protection relays, understanding the differences between GOOSE and MMS is essential when designing protection communication, integrating relays with SCADA systems and commissioning IEC 61850 networks.
This article explains both services, compares their technical characteristics and provides practical examples of their use in MiCOM protection systems.
An important point: IEC 61850 capabilities are not identical across all MiCOM models. Always verify the exact relay model, order code, firmware, communication hardware and supported services using the manufacturer’s documentation, MICS, PICS, PIXIT and ICD files.
2. What Is GOOSE Communication?
GOOSE is an event-driven communication service defined in IEC 61850-8-1.
It allows IEDs to exchange information directly through Ethernet multicast messages.
In conventional substations, protection signals are commonly exchanged using copper wiring connected to binary inputs and outputs.
For example:
- Relay A operates its protection function.
- Relay A activates a binary output.
- The output is wired to Relay B.
- Relay B receives the signal through a binary input.
With GOOSE communication, a compatible publisher can transmit the corresponding information over an Ethernet network, and a compatible subscriber can receive it without requiring a dedicated copper connection between the two relays.
2.1 Typical GOOSE Applications
GOOSE can be used for:
- Protection trip signals.
- Protection blocking signals.
- Interlocking.
- Breaker failure initiation.
- Permissive protection schemes.
- Breaker status transmission.
- Disconnector status transmission.
- Busbar protection communication.
- Transfer trip applications, where supported and appropriately engineered.
2.2 GOOSE Communication Architecture
+-------------------+ +-------------------+
| MiCOM Relay A | | MiCOM Relay B |
| | | |
| Protection Logic | | Protection Logic |
| | | |
| GOOSE Publisher |------->| GOOSE Subscriber |
+---------+---------+ +---------+---------+
| |
+-------------+--------------+
|
Ethernet Switch
The publisher sends GOOSE messages, and the subscriber processes the received dataset.
GOOSE uses Ethernet multicast communication and does not require TCP/IP.
Its Ethernet EtherType is 0x88B8.
3. What Is MMS Communication?
MMS is a client-server communication mechanism used by IEC 61850.
In a typical substation, protection relays operate as MMS servers, while station controllers or SCADA systems operate as MMS clients.
The client establishes communication with the relay and accesses its available IEC 61850 data model.
3.1 Typical MMS Applications
MMS is commonly used for:
- Reading protection indications.
- Reading circuit breaker status.
- Reading current and voltage measurements.
- Receiving alarms.
- Receiving event reports.
- General interrogation.
- Operating supported switchgear through control services.
- Browsing logical devices and logical nodes.
3.2 MMS Communication Architecture
+----------------------------+
| SICAM PAS / SCADA System |
| |
| IEC 61850 MMS Client |
+-------------+--------------+
|
|
Ethernet Network
|
|
+-------------v--------------+
| MiCOM Protection Relay |
| |
| IEC 61850 MMS Server |
| |
| Logical Devices |
| Logical Nodes |
| Data Objects |
| Data Attributes |
+----------------------------+
MMS communication generally uses TCP/IP and TCP port 102.
Unlike GOOSE, MMS is not a direct Layer 2 multicast service.
4. Main Technical Differences Between GOOSE and MMS
The most important differences are summarized below.
| Feature | GOOSE | MMS |
|---|---|---|
| Communication model | Publisher/subscriber | Client/server |
| Main purpose | Event-driven IED communication | Data access, reporting and control |
| Transport | Ethernet Layer 2 | TCP/IP |
| Ethernet type | 0x88B8 | MMS carried over TCP |
| TCP connection | No | Yes |
| Multicast | Yes | Not the normal MMS client-server model |
| Dataset | Yes | Yes |
| Control block | GoCB | RCB for reporting |
| Typical use | Interlocking and protection signals | SCADA and station automation |
| Communication direction | Publisher to subscribers | Client requests and server responses |
| Event reporting | State-based retransmission | Report trigger mechanisms |
| Buffered reporting | Not the same as MMS BRCB | Supported through BRCB where implemented |
GOOSE and MMS are complementary services. One does not replace the other.
5. Communication Architecture: Layer 2 vs TCP/IP
One of the most important technical differences is the communication layer.
5.1 GOOSE Layer 2 Communication
GOOSE messages are transmitted directly over Ethernet.
A simplified frame structure is:
+--------------------------+
| Destination MAC Address |
+--------------------------+
| Source MAC Address |
+--------------------------+
| VLAN Tag (if configured) |
+--------------------------+
| EtherType: 0x88B8 |
+--------------------------+
| GOOSE Protocol Data |
+--------------------------+
| Ethernet Frame Check |
+--------------------------+
Because GOOSE does not use TCP/IP, it does not require IP routing in the same way as MMS.
However, the Ethernet network must be designed to forward multicast GOOSE traffic correctly.
5.2 MMS TCP/IP Communication
MMS communication uses a TCP/IP-based protocol stack.
A simplified structure is:
+--------------------------+
| IEC 61850 MMS Services |
+--------------------------+
| Presentation / Session |
+--------------------------+
| TCP |
+--------------------------+
| IP |
+--------------------------+
| Ethernet |
+--------------------------+
The client establishes a TCP connection, generally using port 102, and then establishes the required application association.
6. Communication Speed and Performance
GOOSE is designed for fast event-driven communication.
It is particularly useful where protection and control functions require rapid signal exchange.
MMS is designed for client-server data access, reporting and control.
It is generally not the preferred mechanism for time-critical protection interlocking or fast relay-to-relay trip signalling.
6.1 GOOSE Transmission Behaviour
When a published dataset changes state, the GOOSE publisher transmits a new message.
Important fields include:
stNum: State number.sqNum: Sequence number.timeAllowedToLive: Expected message validity interval.confRev: Configuration revision.- APPID.
- Destination multicast MAC address.
After a state change, the publisher typically retransmits the new state using a fast initial retransmission sequence, followed by progressively longer retransmission intervals.
This helps subscribers receive the latest state even if individual messages are lost.
6.2 MMS Communication Behaviour
MMS communication depends on:
- TCP connection.
- Application association.
- Client requests.
- Server responses.
- Reporting configuration.
- Network performance.
It is suitable for monitoring and supervisory control, but should not be selected as a substitute for a validated fast protection communication scheme.
6.3 Important Performance Consideration
GOOSE is designed for time-critical applications, but actual end-to-end performance depends on:
- Relay processing time.
- Network topology.
- Ethernet switch performance.
- Traffic loading.
- VLAN and QoS configuration.
- Redundancy architecture.
- Subscriber processing.
Do not assume a fixed operating time for every GOOSE application. Performance must be assessed and tested for the actual system.
7. Practical Application: GOOSE for Protection Interlocking
Consider two feeders connected to a common busbar.
The objective is to exchange blocking information between their protection relays.
Conventional Wiring
Relay A Binary Output
|
|
Copper Cable
|
|
Relay B Binary Input
IEC 61850 GOOSE
+----------------+ +----------------+
| MiCOM Relay A | | MiCOM Relay B |
| | | |
| GOOSE |--------->| GOOSE |
| Publisher | Ethernet | Subscriber |
+----------------+ +----------------+
Operating Principle
- Relay A detects the required protection condition.
- Its application logic changes the relevant signal.
- The GOOSE publisher transmits the updated dataset.
- Relay B receives the message.
- The subscribed signal is processed by Relay B.
- Relay B uses the signal in its protection logic.
The application logic, interlocking and communication-failure response must be engineered and tested.
8. Practical Application: MMS for SCADA Monitoring
Consider a substation with several MiCOM feeder relays connected to a Siemens SICAM PAS station controller.
The objective is to collect:
- Breaker status.
- Protection trip indications.
- Protection start indications.
- Current measurements.
- Voltage measurements.
- Alarm information.
The architecture is:
+---------------------------+
| SICAM PAS |
| |
| IEC 61850 MMS Client |
+-------------+-------------+
|
Ethernet Network
|
+------+------+
| |
+------v------+ +----v---------+
| MiCOM Relay | | MiCOM Relay |
| Feeder 1 | | Feeder 2 |
| MMS Server | | MMS Server |
+-------------+ +--------------+
The station controller establishes MMS associations with the relays and obtains the required information through supported data access and reporting services.
9. Can GOOSE and MMS Be Used Together?
Yes. In fact, using both services together is common in IEC 61850 substations.
GOOSE handles fast IED-to-IED communication, while MMS provides monitoring, reporting and supervisory control.
For example, a MiCOM feeder relay may:
- Publish a protection blocking signal through GOOSE.
- Subscribe to a breaker failure signal from another relay.
- Provide current measurements to SICAM PAS through MMS.
- Report protection operations to SCADA through MMS.
- Receive supported control commands through MMS.
These communication services operate independently but can be part of the same substation automation architecture.
10. Dataset Engineering: GOOSE vs MMS
Both GOOSE and MMS can use datasets.
However, their associated control blocks and communication purposes differ.
10.1 GOOSE Dataset
A GOOSE dataset contains information to be transmitted by a GOOSE publisher.
Example:
DS_PROTECTION
├── PTOC1.Op.general
├── PTRC1.Tr.general
├── XCBR1.Pos.stVal
└── GGIO1.Ind1.stVal
The exact references must be checked in the actual IED data model.
The dataset is associated with a GOOSE control block, represented by GSEControl in SCL.
10.2 MMS Reporting Dataset
An MMS reporting dataset contains information selected for reporting to an MMS client.
Example:
DS_SCADA
├── XCBR1.Pos.stVal
├── PTOC1.Op.general
├── MMXU1.A.phsA.cVal.mag.f
└── MMXU1.A.phsB.cVal.mag.f
The dataset is associated with a Report Control Block.
The report control block determines how the client receives the information.
11. GOOSE and MMS Control Blocks
The two services use different control blocks.
| GOOSE | MMS |
|---|---|
| GOOSE Control Block (GoCB) | Report Control Block (RCB) |
| Configures GOOSE publication | Configures MMS reporting |
| References a GOOSE dataset | References an MMS reporting dataset |
| Defines GOOSE communication parameters | Defines report behavior and options |
| Supports publisher/subscriber communication | Supports client-server reporting |
11.1 GOOSE Control Block
The GOOSE control block defines the publication of a dataset.
Its engineering involves:
- GOOSE identifier.
- Dataset reference.
- APPID.
- Destination MAC address.
- VLAN parameters.
- Configuration revision.
11.2 Report Control Block
The report control block defines reporting behavior.
Two common types are:
- URCB: Unbuffered Report Control Block.
- BRCB: Buffered Report Control Block.
A BRCB can retain report events during temporary client disconnection, subject to buffer capacity and implementation.
A URCB does not provide the same persistent event buffering behavior.
12. Network Configuration for GOOSE and MMS
Although both services may share the same physical Ethernet infrastructure, their network requirements differ.
12.1 GOOSE Network Configuration
Important parameters include:
- Multicast destination MAC.
- APPID.
- VLAN ID.
- VLAN priority.
- Switch multicast forwarding.
- QoS configuration.
- Network redundancy, where supported.
GOOSE multicast forwarding must be configured correctly across the relevant Ethernet switches.
12.2 MMS Network Configuration
Important parameters include:
- IP address.
- Subnet mask.
- Default gateway, where required.
- TCP port 102 accessibility.
- Routing.
- Firewall rules.
- Client-server communication configuration.
12.3 VLAN Segmentation Example
A substation may use separate VLANs for different communication purposes.
| VLAN | Example purpose |
|---|---|
| VLAN 10 | Protection GOOSE |
| VLAN 20 | MMS and SCADA |
| VLAN 30 | Engineering access |
| VLAN 40 | Other automation traffic |
These are illustrative VLAN allocations. Actual network design should follow the project’s cybersecurity and communication requirements.
13. Wireshark Analysis: GOOSE vs MMS
Wireshark is particularly useful when diagnosing IEC 61850 communication problems.
13.1 GOOSE Filter
goose
Alternatively:
eth.type == 0x88b8
Check:
- Source MAC address.
- Destination MAC address.
- APPID.
- VLAN ID.
stNum.sqNum.timeAllowedToLive.confRev.- Dataset values.
13.2 MMS Filter
tcp.port == 102
Check:
- TCP connection establishment.
- Association establishment.
- MMS requests.
- MMS responses.
- Read services.
- Reporting messages.
- Control services, where applicable.
13.3 Additional TCP Filters
tcp.analysis.retransmission
tcp.flags.reset == 1
These filters help investigate TCP communication problems affecting MMS.
They do not directly diagnose GOOSE because GOOSE is not carried over TCP.
14. Common GOOSE Problems
| Problem | Possible cause | Recommended action |
|---|---|---|
| Subscriber does not receive messages | Multicast forwarding issue | Check Ethernet switches |
| Wrong signal received | Incorrect dataset mapping | Check FCDA and subscriber references |
| GOOSE configuration mismatch | Incorrect configuration revision | Check publisher and subscriber configuration |
| Communication supervision alarm | Messages not received within expected interval | Check network and publisher |
| VLAN communication failure | Incorrect VLAN configuration | Verify switch port membership |
| Incorrect protection response | Wrong application logic | Perform end-to-end testing |
15. Common MMS Problems
| Problem | Possible cause | Recommended action |
|---|---|---|
| TCP connection failure | Incorrect IP or firewall rule | Check network connectivity and port 102 |
| MMS association failure | Client-server configuration issue | Check association settings |
| Data model browsing failure | Incorrect device description or unsupported service | Verify ICD and device capabilities |
| Missing SCADA points | Incorrect data mapping | Check logical node references |
| Reports not received | RCB not enabled or configured incorrectly | Check reporting configuration |
| Control command rejected | Incorrect control model or interlocking | Verify control configuration |
16. Engineering MiCOM Relays for GOOSE and MMS
MiCOM IEC 61850 engineering can involve device-specific engineering tools and system-level configuration tools.
S1 Agile is used for supported MiCOM device engineering.
A separate IEC 61850 system configurator may be required for system-level SCL engineering, including relationships between IEDs.
A typical engineering workflow is:
- Identify the MiCOM relay model and firmware.
- Verify its IEC 61850 capabilities.
- Obtain the correct ICD file.
- Configure the relay’s communication settings.
- Create the substation engineering project.
- Define GOOSE datasets and control blocks.
- Configure GOOSE subscriber relationships.
- Define MMS reporting datasets.
- Configure report control blocks where supported.
- Configure the SCADA client.
- Validate the SCL configuration.
- Transfer approved configuration files using the supported procedure.
- Test GOOSE communication.
- Test MMS communication.
- Complete end-to-end commissioning.
Do not assume that all MiCOM relays support identical GOOSE and MMS functions or that S1 Agile handles every system-level configuration task.
17. Choosing Between GOOSE and MMS
The correct communication service depends on the application.
| Application | Recommended IEC 61850 service |
|---|---|
| Relay-to-relay blocking | GOOSE |
| Fast interlocking | GOOSE |
| Protection signal exchange | GOOSE |
| Breaker status to SCADA | MMS reporting |
| Current and voltage monitoring | MMS |
| Alarm reporting | MMS |
| Logical device browsing | MMS |
| Supervisory control | MMS control services, where supported |
| Event reporting | MMS reporting |
| Direct IED-to-IED event communication | GOOSE |
For time-critical protection applications, GOOSE is generally the appropriate service where the devices and protection scheme support it.
For SCADA monitoring and supervisory operations, MMS is generally the appropriate service.
18. Cybersecurity Considerations
Both GOOSE and MMS must be included in the substation cybersecurity design.
Important considerations include:
- Network segmentation.
- Controlled access to engineering workstations.
- Ethernet switch security.
- Firewall rules for MMS.
- Monitoring of unexpected GOOSE traffic.
- Protection of SCL configuration files.
- Access control and authentication.
- Configuration backup and change management.
- Application of relevant IEC 62351 guidance.
GOOSE should not be assumed to be encrypted or authenticated by default.
Similarly, ordinary MMS communication should not be assumed to provide encryption without appropriate security capabilities and configuration.
19. Practical Commissioning Checklist
GOOSE Testing
- Verify publisher configuration.
- Check dataset members.
- Verify GoCB parameters.
- Check multicast MAC address.
- Verify APPID.
- Check VLAN ID and priority.
- Confirm subscriber mapping.
- Capture GOOSE messages in Wireshark.
- Verify
stNumandsqNum. - Test signal changes.
- Test communication failure behavior.
- Complete end-to-end application testing.
MMS Testing
- Verify relay IP address.
- Check TCP port 102.
- Establish MMS association.
- Browse the data model.
- Verify logical nodes and data objects.
- Test read services.
- Verify quality and timestamp.
- Configure and test reporting.
- Test BRCB recovery where supported.
- Test control services where applicable.
- Verify SCADA point mapping.
20. Conclusion
GOOSE and MMS are two essential communication mechanisms in IEC 61850-based protection and substation automation systems.
GOOSE is designed for event-driven communication between IEDs and is particularly useful for protection signalling, interlocking and blocking applications.
MMS provides client-server communication for data access, monitoring, reporting and supported supervisory control functions.
For MiCOM protection relays, engineers should understand both services and their respective engineering requirements.
A successful IEC 61850 project requires correct data model configuration, datasets, control blocks, network design, device compatibility verification and end-to-end testing.
Using GOOSE and MMS together allows modern substations to combine fast protection communication with comprehensive SCADA monitoring and control.
21. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM protection relays, IEC 61850 communication and substation automation.
Our training covers:
- MiCOM relay configuration and engineering.
- IEC 61850 architecture.
- GOOSE publisher and subscriber configuration.
- MMS client-server communication.
- GOOSE and MMS testing.
- Dataset and control block engineering.
- ICD, CID, IID and SCD files.
- SICAM PAS integration.
- Wireshark communication analysis.
- Practical protection and control applications.
Training formats:
- Pre-recorded video courses.
- Structured self-paced training.
- Face-to-face training.
- Customized in-house training for companies and utilities.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Website: https://elec-engg.com/
