FOREWORD
INTRODUCTION
1 Scope
1.1 General
1.2 Application profile
2 Normative references
3 Definitions
3.1 Terms
3.2 Abbreviations
3.3 Conventions
3.4 Protocol data types
3.5 Non-protocol types
3.6 Literals
4 Dependence on T-profile
4.1 General
4.2 LNA-LNA or MAU-LNA communication
4.3 Services required
4.4 Services required, but not used by the A-profile
4.5 Variable quality of service attributes
4.5.1 Reliability and safety
4.5.2 Real time response
4.5.3 Support for stream data
4.5.4 Maximum and minimum message lengths
4.6 Congestion and flow control
5 Functional requirements for MAU
5.1 General overview
5.2 MAU configuration management
5.2.1 Define MAU parameters (MauInitialize)
5.2.2 Connection open request (MauOpen)
5.2.3 Connection close (MauClose)
5.2.4 MAU state change call-back (MauState)
5.3 Session management, authentication and congestion
control
5.3.1 Session control and authentication
5.3.2 Congestion control (MauSession)
5.3.3 Request and connection limiting
5.4 Interface and connection point overview
5.4.1 Special considerations for anonymous
broadcast (ABC)
5.4.2 MCP membership in interfaces
5.4.3 MCP attributes
5.4.4 Modify MCP attributes (McpGet, McpSet)
5.4.5 Interface attributes
5.4.6 Modify interface attributes (IfGet, IfSet)
5.5 Interface management
5.5.1 Define interface (IfTable)
5.5.2 Remove interface (IfRemove)
5.5.3 Establish interface connection (IfOpen)
5.5.4 Close interface (IfClose)
5.5.5 Interface state change call-back
(InterfaceState)
5.6 MCP transactions
5.6.1 Function type transactions
5.6.2 Non-acknowledged write transactions
5.6.3 Subscribe type transactions
5.6.4 Individual subscribe transactions
5.6.5 Client side initiation (TransActivate)
5.6.6 Transaction cancellation (TransCancel)
5.6.7 Client side transaction state change
(TransClientState)
5.6.8 Server side transaction state change
(TransServerState)
5.7 Bulk data transfer
6 Functional requirements for LNAs
6.1 Context diagram and functional overview
6.2 MAU name management (MauAck, MauRequest,
SessionClose)
6.2.1 Duplicate MAU names
6.2.2 Local MAU names
6.2.3 Remote MAU names
6.3 LNA-LNA session management
6.3.1 Heard about LNA
6.3.2 Known LNA
6.3.3 Dead LNA
6.3.4 The LNA watchdog function
6.4 Local MAU connection management
6.4.1 MAU identification
6.4.2 Local MAU states
6.4.3 Starting MAU management
6.4.4 Ending MAU management
6.5 MAU control MCP
6.5.1 General overview
6.5.2 Functionality
6.5.3 Watchdog service
6.6 Session management
6.6.1 General principles
6.6.2 MAU session information
6.6.3 Session codes used for authentication
6.7 Accept type interface management
6.7.1 General overview
6.7.2 Possible errors in interface definitions
or connection requests
6.7.3 Special handling of anonymous broadcast
interfaces
6.7.4 Definition and removal of accept interface
6.7.5 Establishing and closing connections to
accept interfaces
6.8 Connect type interface management
6.9 General transaction management
6.9.1 MCP identity and transaction address
6.9.2 Transaction identity
6.9.3 Session identity
6.9.4 Transaction types
6.9.5 Exception handling
6.10 Accept side transaction management
6.10.1 Read, write and function transaction
handling
6.10.2 Non-acknowledged write request
6.10.3 Initial subscribe
6.10.4 Initial individual subscribe
6.10.5 Server initiated subscribe acknowledgement
6.10.6 Server initiated individual subscribe
acknowledgement
6.10.7 Anonymous broadcast subscribe
6.10.8 Cancellation of a transaction
6.11 Connect side transaction management
6.12 LNA-MAU
6.13 Use of priority levels in LNA
6.14 Congestion control
6.14.1 Congestion cases
6.14.2 LNA requirements
6.14.3 MAU requirements
7 Protocol defined as sequence diagrams
7.1 General conventions
7.1.1 Broken connections
7.1.2 Exception handling
7.2 LNA management
7.2.1 Opening LNA-LNA connection
7.2.2 LNA watchdog functionality
7.2.3 Congestion control
7.3 Opening and closing MAU sessions
7.3.1 MAU to MAU communication via same LNA
7.3.2 Opening a MAU session
7.3.3 Closing a MAU session
7.3.4 Finding a remote MAU in LNA
7.3.5 Server MAU or LNA dies
7.4 Opening and closing interfaces
7.4.1 Opening accept interface
7.4.2 Closing accept IF
7.4.3 Opening connect IF
7.4.4 Closing connect interface
7.5 Data transfer messages
7.5.1 Data transfer of read, write or function
type
7.5.2 Subscribe data transfers
7.5.3 Data transfer cancel and transfer timeout
8 Message definitions
8.1 Introduction
8.1.1 Common message format
8.2 MAU-LNA messages
8.2.1 Message format
8.2.2 MAU session control
8.2.3 Interface definition messages
8.2.4 Data transfer messages
8.3 LNA-LNA message formats for reliable link
8.3.1 General message format
8.3.2 Connection management
8.3.3 MAU management
8.3.4 Interface connection management
8.3.5 Data transfer management
8.4 LNA-LNA message formats for multicast link
8.4.1 General message format
8.4.2 Different multi-cast ports
8.4.3 Name look-up and watchdog messages
8.4.4 Data transfer messages
8.4.5 Anonymous broadcast message details
9 General identity codes
9.1 Protocol and software version codes
9.2 Network address, node number and LNA id
(address_m, word32_m)
9.3 MAU identity (mauname_m, mauid_m)
9.4 Data object and MCP identity (mcid_m)
9.5 Interface code (mcid_m)
9.6 Data object name (mcname_m, mciname_m)
9.7 Interface name (ifname_m)
9.8 Session identity (word16_m)
9.9 Transaction identity (word32_m)
9.10 Format string
9.10.1 Data record format encoding
9.10.2 Transaction type coding
9.10.3 Complete format string
9.11 Password (password_m)
10 Data marshalling
10.1 Introduction
10.2 Network octet order
10.2.1 General
10.2.2 Basic types
10.2.3 Composite types
10.2.4 Messages
10.3 Pack and unpack routines
10.3.1 Introduction
10.3.2 Pack routine
10.3.3 Unpack routine
11 Communication link between MAU and LNA
11.1 Introduction
11.1.1 General service specification
11.1.2 Point to point
11.1.3 Connection oriented
11.1.4 Symmetrical and full duplex
11.1.5 Message based
11.1.6 Priority
11.1.7 Buffering and flow control
11.1.8 Reliable transfer
11.1.9 Error reporting
12 General principles for module functionality
12.1 Flexibility in receiving, conservatism in sending
12.2 Garbled messages
12.3 Closed communication links
Annex A (normative) Message codes
Annex B (normative) Error codes and message field values
Annex C (normative) Symbolic constants
Annex D (informative) Compatibility between MiTS and the
IEC 61162-400 series