CHAPTER 3: IEC 61850 COMMUNICATION OVERVIEWUR FAMILY – COMMUNICATIONS GUIDE 3-73Figure 3-3: IEC 61850 DataSets3.1.4 TxGOOSEGOOSE is a service for communicating trip and blocking signals between IEDs. It is expected to be executed in the order ofthree milliseconds for Type 1A "Trip" messages within a substation. Publishing of each GOOSE message is controlled by acontrol block in the information model of the publishing device, which since UR 7.30 is represented by a TxGOOSE element.Each GOOSE message includes the values of all of the members of the dataset to which it is configured, and a number offields that can be used by the subscriber to identify the particular GOOSE message it subscribes to. The identification fieldsare as follows:• Destination MAC address — A multicast address that selects the set of destination IEDs• Source MAC address — A globally unique identification of the publisher• APPID — A number that is recommended by the standard to be unique within the system• gocbRef — A reference to the control block object that controls message publishing• datSet — A reference to the dataset whose members are published• goID — A string that allows a user to assign an identification to the GOOSE message• confRev — Configuration revision number to identify changes affecting message content• ndsCom — A Boolean flag that indicates the publisher needs to be commissioned• numDatSetEntries — The number of members in the datasetTo facilitate rapid processing in both the publisher and subscriber, the MMS/TCP/IP stacks are bypassed; GOOSE messagesinterface directly to the Ethernet layer. To avoid the publisher having to compose and send sequentially individualmessages to each subscriber, multicast addressing is used whereby the network copies each transmitted GOOSEmessages to all subscribers on the same VLAN. Finally, to avoid the long delays that handshaking type protocols canintroduce when a packet is lost, GOOSE instead employs a scheme whereby messages encoding a change of state arerepeated several times; if the first event message is lost, the closely following repetition gets through.