ETSI ES 202 336-1 V1.2.1 (2011-07)
Environmental Engineering (EE); Monitoring and Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment Systems used in Telecommunication Networks) Part 1: Generic Interface
Environmental Engineering (EE); Monitoring and Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment Systems used in Telecommunication Networks) Part 1: Generic Interface
RES/EE-02039-1
Okoljski inženiring (EE) - Nadzorovalni in krmilni vmesnik za infrastrukturno opremo (elektroenergetski, hladilni in stavbni okoljski sistemi v telekomunikacijskih omrežjih) - 1. del: Generični vmesnik
General Information
Standards Content (Sample)
Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
ETSI Standard
Environmental Engineering (EE);
Monitoring and Control Interface for Infrastructure Equipment
(Power, Cooling and Building Environment Systems used in
Telecommunication Networks)
Part 1: Generic Interface
�
2 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
Reference
RES/EE-02039-1
Keywords
control, interface, management, power, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2011.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 11
4 Monitoring and Control (M&C) overview . 13
4.1 Infrastructure equipment management network general description . 13
4.2 IEM&C management network example . 16
4.3 IEM&C management network HMI description . 16
5 Equipment IEM&C main goals . 17
5.1 Data in the IEM&C network . 17
5.1.1 Mandatory data in the IEM&C network . 17
5.1.2 Optional data in the IEM&C network . 18
5.2 High level application and data structure flexibility . 18
5.3 Data interface complexity and structure . 19
5.3.1 Information . 19
5.3.2 Status and event . 19
5.3.3 Alarm severity and event class . 20
6 IEM&C management typical content subsets . 20
6.1 DC power system (part 2) . 22
6.2 AC UPS power system (part 3) . 23
6.3 AC distribution switchboard (part 4) . 23
6.4 AC diesel back-up generator (part 5) . 24
6.5 Thermal environment and cooling system (part 6) . 24
6.5.1 Thermal environment of equipment rooms . 24
6.5.2 Fan system . 24
6.5.3 Cooling system with compressors . 24
6.5.4 Chilled water cooling system . 24
6.6 Other utilities system (part 7) . 25
6.7 Remote power feeding system (part 8) . 25
6.8 Alternative power systems (part 9) . 25
6.9 AC inverter power system (part 10) . 25
7 IEM&C management interface and network architecture . 25
7.1 Location of intelligence . 26
7.2 XCU, DGU, LMA management interface . 26
7.3 Interface and protocol diversity . 26
7.4 Open interface and software . 27
7.5 Interface levels . 28
7.5.1 Alarm and state loops interface on XCU or DGU output . 28
7.5.2 Low level protocol equipment CU mediation by DGU . 28
7.5.3 XCU and DGU high level protocol interface . 28
7.5.4 Hybrid network element solutions . 29
7.6 Transport Control Layer . 29
7.7 Physical and network layer . 29
7.8 Progressive Network Evolution . 30
8 Supervisor functions and performance . 31
ETSI
4 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
9 Data Structure Format and Syntax of the XML Document, For Exchange Between CU or DGU
and LMA or RMA by IEM&C agent . . 32
9.1 The description of XML elements . 32
9.2 The order of the XML elements . 32
9.3 The hierarchic rule. 33
9.4 Standard elements of any equipment, system or subsystem . 34
9.4.1 Standard elements . 34
9.4.2 Alarm and event message . 35
9.4.3 The element . 37
9.4.4 The element . 38
9.4.5 The element . 39
9.4.6 The element . 40
9.4.7 The element. 41
9.4.8 The element . 44
9.4.9 The element . 44
9.4.10 Example: XML document related to a generic equipment . 45
9.5 XML Document Compliance Verification . 45
9.6 The element . 54
9.6.1 Recommendation about the of the element . 55
9.7 The element . 56
Annex A (normative): Communication between LMA/RMA and IEM&C agent using REST . 58
A.1 Communication initiated by the LMA/RMA . 58
A.1.1 The GET method . 59
A.1.2 The POST method . 60
A.2 Communication initiated by DGU/XCU . 61
Annex B (informative): Data Coherence and reliability for IEM&C . 62
B.1 Data integrity, coherence and management network reliability . 62
B.2 Application data coherence and integrity . 62
B.3 Naming and data origin . 62
B.4 CU,DGU reliability . 63
B.5 LMA reliability . 63
B.6 RMA reliability . 63
B.7 Ethernet and IP network reliability . 64
B.8 Computer and OS reliability. 64
B.9 Application reliability. 64
B.10. XML Message posting reliability . 65
Annex C (informative): Network Element Functions and software architecture and choices . 66
C.1 General description. 66
C.2 Functions of the RMA . 67
C.3 Data analysis . . 68
C.4 Safety monitoring input provision . 68
C.5 Software working and development environment . 68
Annex D (informative): Network capacity and timing . 69
D.1 Management and Network Capacity . 69
D.2 Memory capacity . 69
ETSI
5 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
D.3 Timing performance . 69
Annex E (informative): Overview of the XML format . 70
E.1 XML . 70
E.2 XML declaration . 70
E.3 XML element, XML root element and XML child element . 70
E.4 XML document . 71
E.5 XML Attribute . 71
E.6 XML Schema . 71
E.7 XML Schema Datatypes . 72
E.8 XSL Languages . 73
E.9 XSLT . 73
E.10 XPath . 73
Annex F (informative): Hints about the choice of OSI or IP models, physical network layers
and intranet-Ethernet access protocols . 74
F.1 OSI and IP models . 74
F.2 Details on IP layers. 75
F.2.1 Application Layer . 75
F.2.2 Transport Layer . 76
F.2.3 Network Layer . 76
F.2.4 Link Layer . 76
F.3 Internet- Ethernet access protocol PPPoE, PPPoA, PoS . 77
F.3.1 PPPoE . 77
F.3.2 PPP service . 78
F.3.3 Other PPP . 78
Annex G (informative): Bibliography . 79
History . 80
ETSI
6 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This final draft ETSI Standard (ES) has been produced by ETSI Technical Committee Environmental Engineering (EE),
and is now submitted for the ETSI standards Membership Approval Procedure.
The present document is part 1 of a multi-part deliverable covering power, cooling and building environment systems
control and monitoring guidance, as identified below:
Part 1: "Generic Interface";
Part 2: "DC power system control and monitoring information model";
Part 3: "AC UPS power system control and monitoring information model";
Part 4: "AC distribution power system control and monitoring information model";
Part 5: "AC diesel back-up generator system control and monitoring information model";
Part 6: "Air conditioning system control and monitoring information model";
Part 7: "Other utilities system control and monitoring information model";
Part 8: "Remote power feeding system control and monitoring information model";
Part 9: "Alternative power systems control and monitoring information model";
Part 10: "AC inverter power system control and monitoring information model".
ETSI
7 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
1 Scope
The present document applies to monitoring and control of Infrastructure Environment i.e. power, cooling and building
environment systems for telecommunication centres and access network locations.
Interoperability of heterogeneous management interfaces and systems with multi-vendor equipment is the key issue.
The present document gives a general approach from equipment to management system.
The multi-part deliverable is composed of a generic core part (the present document) and several specific parts for
equipment category (ES 202 336-2 and following [15] and [i.14]).
The core document defines:
• The site equipment map and its division in functional subsets e.g. DC system which introduces part 2 and
following parts of this multi-part deliverable.
• The generic set of exchanged information required at the interface of equipment, which is instanced for each
equipment subset in part 2 and following parts of this multi-part deliverable.
• The minimum requirement for network architecture allowing some compatibility with old existing interface
and the mechanism to exchange data between network element.
• The data interface protocol for remote or local site management (Machine to Machine Interface MMI) and
Human Machine Interface HMI for monitoring and controlling.
• Recommendations for sure management network such as dependability, data back-up, data coherence and
synchronization all along the management network, response time, fault detection and partial service in case of
failure.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI ETS 300 132-1: "Equipment Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 1: Operated by alternating current (AC) derived from direct
current (DC) sources".
[2] ETSI EN 300 132-2: "Environmental Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 2: Operated by direct current (DC)".
[3] ETSI EN 300 132-3: "Environmental Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 3: Operated by rectified current source, alternating current
source or direct current source up to 400 V".
[4] ETSI EN 302 099: "Environmental Engineering (EE); Powering of equipment in access network".
[5] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".
ETSI
8 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
[6] ITU-T Recommendation M.3100: "Generic network information model".
[7] ITU-T Recommendation X.733: "Information technology - Open Systems Interconnection -
Systems Management: Alarm reporting function".
[8] IEC 60839-5-4: "Alarm systems - Part 5: Requirements for alarm transmission systems -
Section 4: Alarm transmission systems using dedicated alarm transmission paths".
[9] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data
Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to
public data networks by dedicated circuit".
[10] IETF RFC 2616: "Hypertext Transfer Protocol - HTTP/1.1".
[11] ISO/IEC 7498: "Open Systems Interconnection (OSI) - Basic Reference Model".
[12] IEEE 802.series (all parts): "IEEE Standard for Telecommunications and Information Exchange
Between systems - Local and metropolitan area networks".
[13] ISO/IEC 10164 (all parts): "Information technology - Open Systems Interconnection - Systems
Management".
[14] ISO/IEC 8879: "Information processing - Text and office systems - Standard Generalized Markup
Language (SGML)".
[15] ETSI ES 202 336 (parts 2, 3, 5, 7 and 8): "Environmental Engineering (EE); Monitoring and
Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment
Systems used in Telecommunication Networks)".
[16] IEC 61076-2-101: "Connectors for electronic equipment - Product requirements -
Part 2-101: Circular connectors - Detail specification for M12 connectors with screw-locking".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 102 121: "Environmental Engineering (EE); Guidance for power distribution to
telecommunication and datacom equipment".
[i.2] ETSI TR 102 336: "Environmental Engineering (EE); Power and cooling system control and
monitoring guidance".
[i.3] REST.
NOTE: Described in: http://en.wikipedia.org/wiki/REST,
http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm (Ref article from Roy Thomas)
and http://www.peej.co.uk/articles/rest.html .
[i.4] IETF RFC 2516: "A Method for Transmitting PPP Over Ethernet (PPPoE)".
[i.5] IETF RFC 1191: "Path MTU discovery".
[i.6] IETF RFC 871: "Perspective on the ARPANET reference model".
[i.7] IETF RFC 1662: "PPP in HDLC-like Framing".
[i.8] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".
[i.9] IETF RFC 2364: "PPP Over AAL5".
[i.10] IETF RFC 2615: "PPP over SONET/SDH".
[i.11] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".
ETSI
9 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
[i.12] ISO/IEC 8327: "Information technology -- Open Systems Interconnection -- Connection-oriented
Session protocol: Protocol specification".
[i.13] IEC/TR 62102: "Electrical safety –Classification of interfaces for equipment to be connected to
information and communications technology networks".
[i.14] ETSI ES 202 336 (parts 4, 6, 9 and 10): "Environmental Engineering (EE); Monitoring and
Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment
Systems used in Telecommunication Networks)".
NOTE: These standards are not yet publicly available.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
NOTE: Terms referring to energy interface, equipment and distribution are described in power distribution
guidance and standards ETS 300 132-1 [1], EN 300 132-2 [2], EN 300 132-3 [3] for AC and DC interface
and EN 302 099 [4] for access network equipment powering.
alarm: any information signalling abnormal state, i.e. different to specified normal state of hardware, software,
environment condition (temperature, humidity, etc.)
NOTE: The alarm signal can be understood by itself by an operator and have at least one severity qualification or
codification (colour, level, etc.).
alarm loop: electrical loop which open or closed state correspond to alarm start (set) or end (clear) state
alarm message: text parts of the alarm structure
alarm structure: organized set of information fields in an alarm data frame (time stamp, set/clear, text, etc.)
battery: complete arrangement of battery cells or blocks in one string or more in parallel
battery cell: basic electrochemical element (e.g. 2 V for lead acid battery)
battery string: number of serially interconnected battery blocks or cells
client post: any device (laptop, PDA, console, etc.) connected to servers via the operation system networks to perform
maintenance or supervision operations
NOTE: It is independent of object class and object properties. The most common functions are GET and SET,
equivalent to monitor and control.
Common Management Information Protocol (CMIP): protocol using CMIS service to obtain remote monitoring and
control
NOTE: CMIP is much richer than SNMP but much more complex to implement.
Common Management Information Service (CMIS): generic services to handle objects (operation and notification of
results)
Control Unit (CU): integrated unit in an equipment to monitor and control this equipment through sensors and
actuators
Control form Style Sheet (CSS): simple mechanism for adding style (e.g. fonts, colours, spacing) to Web documents,
Tutorials, books, mailing lists for users, etc.
ETSI
10 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
Data Gathering Unit (DGU): functional unit used for several functions:
• collect serial, digital, and analogue data;
• option to send (output) serial or digital commands;
• forward/receive information to/from the Local/Remote Management Application via agreed protocols;
• mediation between interfaces and protocols.
NOTE: This function may be integrated as part of specific equipment.
Dynamic Host Configuration Protocol (DHCP): protocol used for self configuration of TCP/IP parameters of a
workstation assigning IP address and a sub network mask
NOTE: DHCP may also configure DNS.
Dynamic Name Server (DNS): associates a single domain name to an IP address
dynamic synoptic: dynamic display of geographical maps, networks, installations and equipment
Ethernet: LAN protocol
NOTE: Equivalent to IEEE 802.1 to 11 [12].
event: any information signalling a change of state which is not an alarm: e.g. battery test, change of state of battery
charge
NOTE: The alarm signal can be understood by itself by an operator and have at least one severity qualification or
codification (colour, level, etc.). It is transmitted in a formatted structure with text message and other
fields like for alarm, e.g. an event can be coded as an alarm with severity "0".
eXtensible Mark-up Language (XML): application profile or restricted form of SGML
NOTE: By construction, XML documents are conforming SGML the Standard Generalized Markup Language
(ISO/IEC 8879 [14]). documents.XML is designed to describe data and focus on what data is. XML is
different from the well known Hypertext Transfer Mark-up Language (HTML) which was designed to
display data and to focus on how data looks.
Guidelines for Definition of Managed Objects (GDMO): syntax specification for the classification of objects and
properties
NOTE: Associated to ASN.1 language for object definition.
infrastructure equipment: power, cooling and building environment systems used in telecommunications centres and
Access Networks locations
EXAMPLE: Cabinets, shelters, underground locations, etc.
Intranet: internal company network generally using Ethernet protocol and extended IP addresses
logbook: chronological file that contains alarm and event messages may be paper or electronic
Management Information Base (MIB): dynamic data base that gathers all objects and should evolve to include
automatic and manual configuration tools with self coherence tests
menu: list of possible input command choices that may be presented in different ways on a display
NOTE: Selection is normally made by a keyboard, a pointing device, a mouse or directly by finger on a sensitive
screen.
object: class description of items that accept a set of properties or functions
NOTE: Generic objects can include more specific items and inherit from their properties. If correctly structured,
object programming can allow the system to evolve, i.e. be more future-proof. The code should
intrinsically be open and structured.
ETSI
11 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
Hypertext Preprocessor (PHP): powerful tool for making dynamic and interactive Web pages
pop-up: information or command screen that appears when a menu choice is selected
NOTE: For example this may be a pop-up menu when the pointer is on a title button.
REpresentational State Transfer (REST): way to build an application for distributed system as www
Simple Object Access Protocol (SOAP): way to communicate between applications running on different operating
systems, with different technologies and programming languages
NOTE: SOAP communicates over HTTP, because HTTP is supported by all Internet browsers and servers, SOAP
traffic is not blocked by firewalls and proxy servers (see W3C).
Systems Management Function (SMF): object properties or classes with projection on CMIS application context
communication
NOTE: Set of ISO system management functions according to ISO/IEC 10164 [13].
warning: low severity alarm
windows: virtual area on the display that corresponds to a specific application
web: common name for the Internet or Intranet
World Wide Web Consortium (W3C): consortium founded in October 1994 to develop common interoperable
protocols and promote World Wide Web
NOTE: See http://www.w3c.org.
XML enabled CU (XCU): CU enabled to communicate using XML interface as defined in the present document
eXtended HTML (XHTML): stricter and cleaner version of HTML. XHTML consists of all the elements in HTML
4.01 combined with the syntax of XML
NOTE: It can be read by all XML browser (see W3C).
XML Schema Definition (XSD): new more detailed XML description compared to the previous one, the DTD
eXtensible Style sheet Language (XSL): language for expressing style sheets
NOTE: It consists of two parts, a language for transforming XML documents, and an XML vocabulary for
specifying formatting semantics. An XSL style sheet specifies the presentation of a class of XML
documents by describing how an instance of the class is transformed into an XML document that uses the
formatting vocabulary.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Alternative Current
ADSL Asynchronous Digital Subscriber Line
API Application Programming Interface
ASN.1 Abstract Syntax Notation One
ATM Asynchronous Transfer Mode
CHAP Challenge-Handshake Authentication Protocol
CIM Common Information Model
CMIP Common Management Information Protocol (OSI)
CMIS Common Management Information Service (OSI)
CSMA/CD Carrier Sense Multiple Access with Collision Detection
CSS Control form Style Sheet
CU Control Unit
DB Database
DC Direct Current
DCF Data Communication Function in TMN
ETSI
12 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
DEG Diesel Engine Generator
DGU Data Gathering Unit
DHCP Dynamic Host Configuration Protocol
DNS Dynamic Name Server
DSL Digital Subscriber Line
DTD Document Type Definition
EMC Electro Magnetic Compatibility
EP Exploitation Post
FCS Frame Check Sequence
FTP File Transfer Protocol
GDMO Guidelines for Definition of Managed Objects
GSM Global System for Mobile
HMI Human-Machine Interface
HTML HyperText Transfer Mark up Language
HTTP HyperText Transfer Protocol
HTTPS HyperText Transfer Protocol Secure
IEM&C Infrastructure Equipment Monitoring & Control (mediation agent)
IP Internet Protocol
IPCP Internet Protocol Control Protocol
ISDN Integrated Service Digital Network
LCP Link Control Protocol
LED Light Emitting Device
LLC Logical Link Control
LMA Local Management Application
LON Local Operated Network
M&C Monitoring and Control
MAC Media Access Control address
MCF Management Communication Function (in TMN)
MEP Mobile Exploitation Post
MF Mediation Function (in TMN)
MIB Management Information Base
NOTE: In SNMP for example.
MMC Maintenance Management Computer
MMI Machine to Machine Interface
MTTR Mean Time To Repair
MTU Maximum Transmission Unit
NEF Network Element Function (in TMN)
NEM Network Element Management
NMS Network Management System
OLE Object Linking and Embedding
OPC OLE for Process Control
OSF Operating System Function (in TMN)
OSI Open Service Interconnexion (in TMN)
PAP Password Authentication Protocol
PDA Personal Digital Assistant
PHP Hypertext Preprocessor
PoS Packet over SONET
POTS Plain Old Telephone Service
PPPoA Point-To-Point Protocol over ATM
PPPoE Point-to-Point Protocol over Ethernet
PSTN Public Switched Telephone Network
REST REpresentational State Transfer
RFC Request For Comments
RMA Remote Management Application
RPC Remote Procedure Calls
SCTP Stream Control Transfer Protocol
SDH Synchronous Data Hierarchy
SGML Standard Generalized Markup Language
NOTE: See ISO/IEC 8879 [14].
ETSI
13 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
SMF Systems Management Functions
SMS Short Message System
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SOAP Simple Object Access Protocol
TCP Transmission Control Protocol for IP
TMN Telecommunications Management Network
NOTE: See ITU-T Recommendation M.3010 [5].
UDP Use Datagram Protocol
UPS Uninterruptible Power Supply
URI Uniform Resource Identifier
URL Uniform Resource Locator
USB Universal Serial Bus
VPN Virtual Private Network
WSF Work Station Function
WAN Wide Array Network
W3C World Wide Web Consortium
xDSL Digital Subscriber Line
XCU XML enabled CU
XML eXtensible Mark-up Language (see W3C)
XHTML eXtended HTML
XSD XML Schema Definition
XSL Extensible Stylesheet Language
XSLT eXtensible Stylesheet Language Transformation
XSLTb eXtensible Style Language Transformation (attribute b)
4 Monitoring and Control (M&C) overview
Monitoring and control of power, cooling and building environment systems are used to simplify operation, to reduce
maintenance time and site intervention, to reduce human error risk, to give useful data for statistical analysis and
management (i.e. operation cost, reliability or quality management, power consumption estimation).
To achieve this purpose, monitored information and control are needed:
• The information are alarms, events, measurements, data recordings and events logs.
• The controls are commands to the equipment, alarm acknowledge, configuration and settings.
Several management levels are possible for telecommunication installations and equipment. They are described
considering complexity of the system, response time and required level of details from basic alarms to complex analysis
level. In many cases, the same basic information is needed from the equipment-monitoring interface but address
different services that prepares information as requested by users categories.
4.1 Infrastructure equipment management network general
description
Infrastructure Equipment (powering, cooling, building facilities) management network is a subset of TMN.
The infrastructure equipment management network can be defined by functional interfaces between network elements.
Referring to ITU-T Recommendation M.3010 documents for nomenclature [5] and [6], the element can be understood
as generic part of Telecommunication Management Network (TMN):
• The Control Unit (CU) is dedicated to control one or more equipment in a site.
ETSI
14 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
• The XCU connects to e.g. a legacy equipment and translates its data to conform to the "TMN" standardized
format X. The XCU may also be a unit that gathers building facilities alarm loops and makes them available in
the standardized format X. These XCU are Network Element Function (NEF) in
ITU-T Recommendation M.3010 [5].
• The Data Gathering Unit (DGU) is used to gather one or more CU field bus to adapt with TMN protocol and
format. The DGU is a Mediation Function in ITU-T Recommendation M.3010 [5] (MF).
• CU and DGU may be combined in the same unit, especially in the case of small centers where there are few
building facilities alarm loops and few equipment.
• The Local Management Application (LMA) and Remote (RMA) servers process information received from
the XCU and DGU to achieve the functionalities of the management system i.e. Operating System
Function (OSF) in ITU-T Recommendation M.3010 [5].
• LMA can be combined with XCU or DGU.
• The Exploitation Post (EP) offers the man-machine interface. It can be integrated to the LMA/RMA or not
e.g. on Mobile Exploitation Post (MEP). These entity manages the interactive presentation to the user to
monitor and control the equipment. (Work Station Function (WSF) in ITU-T Recommendation M.3010 [5]).
Several XCU and DGU can be managed within this network by one (or perhaps several) LMA, RMA. There may also
be several users connected through the network, to one server or one equipment. The application controlling such a
network with multi-user and with different user rights levels is a Network Element Management system (NEM system
in ITU-T Recommendation M.3010 [5]).
Figure 1 presents the network architecture in respect to scope requirements for communication interfaces:
• between the DGU or XCU and the LMA or RMA;
• between EP or MEP and the RMA or DGU or XCU;
• alarms contacts or loops output interface backuping IP network.
NOTE: The field level interface of CU are out of the scope:
- Equipment or room sensors interfaces to XCU or DGU.
- Interface between XCU and DGU.
ETSI
15 Final draft ETSI ES 202 336-1 V1.1.3 (2011-05)
SCOPE REQUIREMENTS
RMA : Interface, Functions, Reliability,
RMA(OSF)
Performance
...
ETSI Standard
Environmental Engineering (EE);
Monitoring and Control Interface for Infrastructure Equipment
(Power, Cooling and Building Environment Systems used in
Telecommunication Networks)
Part 1: Generic Interface
�
2 ETSI ES 202 336-1 V1.2.1 (2011-07)
Reference
RES/EE-02039-1
Keywords
control, interface, management, power, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2011.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI ES 202 336-1 V1.2.1 (2011-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 11
4 Monitoring and Control (M&C) overview . 13
4.1 Infrastructure equipment management network general description . 13
4.2 IEM&C management network example . 16
4.3 IEM&C management network HMI description . 16
5 Equipment IEM&C main goals . 17
5.1 Data in the IEM&C network . 17
5.1.1 Mandatory data in the IEM&C network . 17
5.1.2 Optional data in the IEM&C network . 18
5.2 High level application and data structure flexibility . 18
5.3 Data interface complexity and structure . 19
5.3.1 Information . 19
5.3.2 Status and event . 19
5.3.3 Alarm severity and event class . 20
6 IEM&C management typical content subsets . 20
6.1 DC power system (part 2) . 22
6.2 AC UPS power system (part 3) . 23
6.3 AC distribution switchboard (part 4) . 23
6.4 AC diesel back-up generator (part 5) . 24
6.5 Thermal environment and cooling system (part 6) . 24
6.5.1 Thermal environment of equipment rooms . 24
6.5.2 Fan system . 24
6.5.3 Cooling system with compressors . 24
6.5.4 Chilled water cooling system . 24
6.6 Other utilities system (part 7) . 25
6.7 Remote power feeding system (part 8) . 25
6.8 Alternative power systems (part 9) . 25
6.9 AC inverter power system (part 10) . 25
7 IEM&C management interface and network architecture . 25
7.1 Location of intelligence . 26
7.2 XCU, DGU, LMA management interface . 26
7.3 Interface and protocol diversity . 26
7.4 Open interface and software . 27
7.5 Interface levels . 28
7.5.1 Alarm and state loops interface on XCU or DGU output . 28
7.5.2 Low level protocol equipment CU mediation by DGU . 28
7.5.3 XCU and DGU high level protocol interface . 28
7.5.4 Hybrid network element solutions . 29
7.6 Transport Control Layer . 29
7.7 Physical and network layer . 29
7.8 Progressive Network Evolution . 30
8 Supervisor functions and performance . 31
ETSI
4 ETSI ES 202 336-1 V1.2.1 (2011-07)
9 Data Structure Format and Syntax of the XML Document, For Exchange Between CU or DGU
and LMA or RMA by IEM&C agent . . 32
9.1 The description of XML elements . 32
9.2 The order of the XML elements . 32
9.3 The hierarchic rule. 33
9.4 Standard elements of any equipment, system or subsystem . 34
9.4.1 Standard elements . 34
9.4.2 Alarm and event message . 35
9.4.3 The element . 37
9.4.4 The element . 38
9.4.5 The element . 39
9.4.6 The element . 40
9.4.7 The element. 41
9.4.8 The element . 44
9.4.9 The element . 44
9.4.10 Example: XML document related to a generic equipment . 45
9.5 XML Document Compliance Verification . 45
9.6 The element . 54
9.6.1 Recommendation about the of the element . 55
9.7 The element . 56
Annex A (normative): Communication between LMA/RMA and IEM&C agent using REST . 58
A.1 Communication initiated by the LMA/RMA . 58
A.1.1 The GET method . 59
A.1.2 The POST method . 60
A.2 Communication initiated by DGU/XCU . 61
Annex B (informative): Data Coherence and reliability for IEM&C . 62
B.1 Data integrity, coherence and management network reliability . 62
B.2 Application data coherence and integrity . 62
B.3 Naming and data origin . 62
B.4 CU,DGU reliability . 63
B.5 LMA reliability . 63
B.6 RMA reliability . 63
B.7 Ethernet and IP network reliability . 64
B.8 Computer and OS reliability. 64
B.9 Application reliability. 64
B.10 XML Message posting reliability . 65
Annex C (informative): Network Element Functions and software architecture and choices . 66
C.1 General description. 66
C.2 Functions of the RMA . 67
C.3 Data analysis . . 68
C.4 Safety monitoring input provision . 68
C.5 Software working and development environment . 68
Annex D (informative): Network capacity and timing . 69
D.1 Management and Network Capacity . 69
D.2 Memory capacity . 69
ETSI
5 ETSI ES 202 336-1 V1.2.1 (2011-07)
D.3 Timing performance . 69
Annex E (informative): Overview of the XML format . 70
E.1 XML . 70
E.2 XML declaration . 70
E.3 XML element, XML root element and XML child element . 70
E.4 XML document . 71
E.5 XML Attribute . 71
E.6 XML Schema . 71
E.7 XML Schema Datatypes . 72
E.8 XSL Languages . 73
E.9 XSLT . 73
E.10 XPath . 73
Annex F (informative): Hints about the choice of OSI or IP models, physical network layers
and intranet-Ethernet access protocols . 74
F.1 OSI and IP models . 74
F.2 Details on IP layers. 75
F.2.1 Application Layer . 75
F.2.2 Transport Layer . 76
F.2.3 Network Layer . 76
F.2.4 Link Layer . 76
F.3 Internet- Ethernet access protocol PPPoE, PPPoA, PoS . 77
F.3.1 PPPoE . 77
F.3.2 PPP service . 78
F.3.3 Other PPP . 78
Annex G (informative): Bibliography . 79
History . 80
ETSI
6 ETSI ES 202 336-1 V1.2.1 (2011-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Environmental Engineering (EE).
The present document is part 1 of a multi-part deliverable covering power, cooling and building environment systems
control and monitoring guidance, as identified below:
Part 1: "Generic Interface";
Part 2: "DC power system control and monitoring information model";
Part 3: "AC UPS power system control and monitoring information model";
Part 4: "AC distribution power system control and monitoring information model";
Part 5: "AC diesel back-up generator system control and monitoring information model";
Part 6: "Air conditioning system control and monitoring information model";
Part 7: "Other utilities system control and monitoring information model";
Part 8: "Remote power feeding system control and monitoring information model";
Part 9: "Alternative power systems control and monitoring information model";
Part 10: "AC inverter power system control and monitoring information model".
ETSI
7 ETSI ES 202 336-1 V1.2.1 (2011-07)
1 Scope
The present document applies to monitoring and control of Infrastructure Environment i.e. power, cooling and building
environment systems for telecommunication centres and access network locations.
Interoperability of heterogeneous management interfaces and systems with multi-vendor equipment is the key issue.
The present document gives a general approach from equipment to management system.
The multi-part deliverable is composed of a generic core part (the present document) and several specific parts for
equipment category (ES 202 336-2 and following [15] and [i.14]).
The core document defines:
• The site equipment map and its division in functional subsets e.g. DC system which introduces part 2 and
following parts of this multi-part deliverable.
• The generic set of exchanged information required at the interface of equipment, which is instanced for each
equipment subset in part 2 and following parts of this multi-part deliverable.
• The minimum requirement for network architecture allowing some compatibility with old existing interface
and the mechanism to exchange data between network element.
• The data interface protocol for remote or local site management (Machine to Machine Interface MMI) and
Human Machine Interface HMI for monitoring and controlling.
• Recommendations for sure management network such as dependability, data back-up, data coherence and
synchronization all along the management network, response time, fault detection and partial service in case of
failure.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI ETS 300 132-1: "Equipment Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 1: Operated by alternating current (AC) derived from direct
current (DC) sources".
[2] ETSI EN 300 132-2: "Environmental Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 2: Operated by direct current (DC)".
[3] ETSI EN 300 132-3: "Environmental Engineering (EE); Power supply interface at the input to
telecommunications equipment; Part 3: Operated by rectified current source, alternating current
source or direct current source up to 400 V".
[4] ETSI EN 302 099: "Environmental Engineering (EE); Powering of equipment in access network".
[5] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".
ETSI
8 ETSI ES 202 336-1 V1.2.1 (2011-07)
[6] ITU-T Recommendation M.3100: "Generic network information model".
[7] ITU-T Recommendation X.733: "Information technology - Open Systems Interconnection -
Systems Management: Alarm reporting function".
[8] IEC 60839-5-4: "Alarm systems - Part 5: Requirements for alarm transmission systems -
Section 4: Alarm transmission systems using dedicated alarm transmission paths".
[9] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data
Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to
public data networks by dedicated circuit".
[10] IETF RFC 2616: "Hypertext Transfer Protocol - HTTP/1.1".
[11] ISO/IEC 7498: "Open Systems Interconnection (OSI) - Basic Reference Model".
[12] IEEE 802.series (all parts): "IEEE Standard for Telecommunications and Information Exchange
Between systems - Local and metropolitan area networks".
[13] ISO/IEC 10164 (all parts): "Information technology - Open Systems Interconnection - Systems
Management".
[14] ISO/IEC 8879: "Information processing - Text and office systems - Standard Generalized Markup
Language (SGML)".
[15] ETSI ES 202 336 (parts 2, 3, 5, 7 and 8): "Environmental Engineering (EE); Monitoring and
Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment
Systems used in Telecommunication Networks)".
[16] IEC 61076-2-101: "Connectors for electronic equipment - Product requirements -
Part 2-101: Circular connectors - Detail specification for M12 connectors with screw-locking".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 102 121: "Environmental Engineering (EE); Guidance for power distribution to
telecommunication and datacom equipment".
[i.2] ETSI TR 102 336: "Environmental Engineering (EE); Power and cooling system control and
monitoring guidance".
[i.3] REST.
NOTE: Described in: http://en.wikipedia.org/wiki/REST,
http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm (Ref article from Roy Thomas)
and http://www.peej.co.uk/articles/rest.html .
[i.4] IETF RFC 2516: "A Method for Transmitting PPP Over Ethernet (PPPoE)".
[i.5] IETF RFC 1191: "Path MTU discovery".
[i.6] IETF RFC 871: "Perspective on the ARPANET reference model".
[i.7] IETF RFC 1662: "PPP in HDLC-like Framing".
[i.8] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".
[i.9] IETF RFC 2364: "PPP Over AAL5".
[i.10] IETF RFC 2615: "PPP over SONET/SDH".
[i.11] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".
ETSI
9 ETSI ES 202 336-1 V1.2.1 (2011-07)
[i.12] ISO/IEC 8327: "Information technology -- Open Systems Interconnection -- Connection-oriented
Session protocol: Protocol specification".
[i.13] IEC/TR 62102: "Electrical safety –Classification of interfaces for equipment to be connected to
information and communications technology networks".
[i.14] ETSI ES 202 336 (parts 4, 6, 9 and 10): "Environmental Engineering (EE); Monitoring and
Control Interface for Infrastructure Equipment (Power, Cooling and Building Environment
Systems used in Telecommunication Networks)".
NOTE: These standards are not yet publicly available.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
NOTE: Terms referring to energy interface, equipment and distribution are described in power distribution
guidance and standards ETS 300 132-1 [1], EN 300 132-2 [2], EN 300 132-3 [3] for AC and DC interface
and EN 302 099 [4] for access network equipment powering.
alarm: any information signalling abnormal state, i.e. different to specified normal state of hardware, software,
environment condition (temperature, humidity, etc.)
NOTE: The alarm signal can be understood by itself by an operator and have at least one severity qualification or
codification (colour, level, etc.).
alarm loop: electrical loop which open or closed state correspond to alarm start (set) or end (clear) state
alarm message: text parts of the alarm structure
alarm structure: organized set of information fields in an alarm data frame (time stamp, set/clear, text, etc.)
battery: complete arrangement of battery cells or blocks in one string or more in parallel
battery cell: basic electrochemical element (e.g. 2 V for lead acid battery)
battery string: number of serially interconnected battery blocks or cells
client post: any device (laptop, PDA, console, etc.) connected to servers via the operation system networks to perform
maintenance or supervision operations
NOTE: It is independent of object class and object properties. The most common functions are GET and SET,
equivalent to monitor and control.
Common Management Information Protocol (CMIP): protocol using CMIS service to obtain remote monitoring and
control
NOTE: CMIP is much richer than SNMP but much more complex to implement.
Common Management Information Service (CMIS): generic services to handle objects (operation and notification of
results)
Control Unit (CU): integrated unit in an equipment to monitor and control this equipment through sensors and
actuators
Control form Style Sheet (CSS): simple mechanism for adding style (e.g. fonts, colours, spacing) to Web documents,
Tutorials, books, mailing lists for users, etc.
ETSI
10 ETSI ES 202 336-1 V1.2.1 (2011-07)
Data Gathering Unit (DGU): functional unit used for several functions:
• collect serial, digital, and analogue data;
• option to send (output) serial or digital commands;
• forward/receive information to/from the Local/Remote Management Application via agreed protocols;
• mediation between interfaces and protocols.
NOTE: This function may be integrated as part of specific equipment.
Dynamic Host Configuration Protocol (DHCP): protocol used for self configuration of TCP/IP parameters of a
workstation assigning IP address and a sub network mask
NOTE: DHCP may also configure DNS.
Dynamic Name Server (DNS): associates a single domain name to an IP address
dynamic synoptic: dynamic display of geographical maps, networks, installations and equipment
Ethernet: LAN protocol
NOTE: Equivalent to IEEE 802.1 to 11 [12].
event: any information signalling a change of state which is not an alarm: e.g. battery test, change of state of battery
charge
NOTE: The alarm signal can be understood by itself by an operator and have at least one severity qualification or
codification (colour, level, etc.). It is transmitted in a formatted structure with text message and other
fields like for alarm, e.g. an event can be coded as an alarm with severity "0".
eXtensible Mark-up Language (XML): application profile or restricted form of SGML
NOTE: By construction, XML documents are conforming SGML the Standard Generalized Markup Language
(ISO/IEC 8879 [14]). documents.XML is designed to describe data and focus on what data is. XML is
different from the well known Hypertext Transfer Mark-up Language (HTML) which was designed to
display data and to focus on how data looks.
Guidelines for Definition of Managed Objects (GDMO): syntax specification for the classification of objects and
properties
NOTE: Associated to ASN.1 language for object definition.
infrastructure equipment: power, cooling and building environment systems used in telecommunications centres and
Access Networks locations
EXAMPLE: Cabinets, shelters, underground locations, etc.
Intranet: internal company network generally using Ethernet protocol and extended IP addresses
logbook: chronological file that contains alarm and event messages may be paper or electronic
Management Information Base (MIB): dynamic data base that gathers all objects and should evolve to include
automatic and manual configuration tools with self coherence tests
menu: list of possible input command choices that may be presented in different ways on a display
NOTE: Selection is normally made by a keyboard, a pointing device, a mouse or directly by finger on a sensitive
screen.
object: class description of items that accept a set of properties or functions
NOTE: Generic objects can include more specific items and inherit from their properties. If correctly structured,
object programming can allow the system to evolve, i.e. be more future-proof. The code should
intrinsically be open and structured.
ETSI
11 ETSI ES 202 336-1 V1.2.1 (2011-07)
Hypertext Preprocessor (PHP): powerful tool for making dynamic and interactive Web pages
pop-up: information or command screen that appears when a menu choice is selected
NOTE: For example this may be a pop-up menu when the pointer is on a title button.
REpresentational State Transfer (REST): way to build an application for distributed system as www
Simple Object Access Protocol (SOAP): way to communicate between applications running on different operating
systems, with different technologies and programming languages
NOTE: SOAP communicates over HTTP, because HTTP is supported by all Internet browsers and servers, SOAP
traffic is not blocked by firewalls and proxy servers (see W3C).
Systems Management Function (SMF): object properties or classes with projection on CMIS application context
communication
NOTE: Set of ISO system management functions according to ISO/IEC 10164 [13].
warning: low severity alarm
windows: virtual area on the display that corresponds to a specific application
web: common name for the Internet or Intranet
World Wide Web Consortium (W3C): consortium founded in October 1994 to develop common interoperable
protocols and promote World Wide Web
NOTE: See http://www.w3c.org.
XML enabled CU (XCU): CU enabled to communicate using XML interface as defined in the present document
eXtended HTML (XHTML): stricter and cleaner version of HTML. XHTML consists of all the elements in HTML
4.01 combined with the syntax of XML
NOTE: It can be read by all XML browser (see W3C).
XML Schema Definition (XSD): new more detailed XML description compared to the previous one, the DTD
eXtensible Style sheet Language (XSL): language for expressing style sheets
NOTE: It consists of two parts, a language for transforming XML documents, and an XML vocabulary for
specifying formatting semantics. An XSL style sheet specifies the presentation of a class of XML
documents by describing how an instance of the class is transformed into an XML document that uses the
formatting vocabulary.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Alternative Current
ADSL Asynchronous Digital Subscriber Line
API Application Programming Interface
ASN.1 Abstract Syntax Notation One
ATM Asynchronous Transfer Mode
CHAP Challenge-Handshake Authentication Protocol
CIM Common Information Model
CMIP Common Management Information Protocol (OSI)
CMIS Common Management Information Service (OSI)
CSMA/CD Carrier Sense Multiple Access with Collision Detection
CSS Control form Style Sheet
CU Control Unit
DB Database
DC Direct Current
DCF Data Communication Function in TMN
ETSI
12 ETSI ES 202 336-1 V1.2.1 (2011-07)
DEG Diesel Engine Generator
DGU Data Gathering Unit
DHCP Dynamic Host Configuration Protocol
DNS Dynamic Name Server
DSL Digital Subscriber Line
DTD Document Type Definition
EMC Electro Magnetic Compatibility
EP Exploitation Post
FCS Frame Check Sequence
FTP File Transfer Protocol
GDMO Guidelines for Definition of Managed Objects
GSM Global System for Mobile
HMI Human-Machine Interface
HTML HyperText Transfer Mark up Language
HTTP HyperText Transfer Protocol
HTTPS HyperText Transfer Protocol Secure
IEM&C Infrastructure Equipment Monitoring & Control (mediation agent)
IP Internet Protocol
IPCP Internet Protocol Control Protocol
ISDN Integrated Service Digital Network
LCP Link Control Protocol
LED Light Emitting Device
LLC Logical Link Control
LMA Local Management Application
LON Local Operated Network
M&C Monitoring and Control
MAC Media Access Control address
MCF Management Communication Function (in TMN)
MEP Mobile Exploitation Post
MF Mediation Function (in TMN)
MIB Management Information Base
NOTE: In SNMP for example.
MMC Maintenance Management Computer
MMI Machine to Machine Interface
MTTR Mean Time To Repair
MTU Maximum Transmission Unit
NEF Network Element Function (in TMN)
NEM Network Element Management
NMS Network Management System
OLE Object Linking and Embedding
OPC OLE for Process Control
OSF Operating System Function (in TMN)
OSI Open Service Interconnexion (in TMN)
PAP Password Authentication Protocol
PDA Personal Digital Assistant
PHP Hypertext Preprocessor
PoS Packet over SONET
POTS Plain Old Telephone Service
PPPoA Point-To-Point Protocol over ATM
PPPoE Point-to-Point Protocol over Ethernet
PSTN Public Switched Telephone Network
REST REpresentational State Transfer
RFC Request For Comments
RMA Remote Management Application
RPC Remote Procedure Calls
SCTP Stream Control Transfer Protocol
SDH Synchronous Data Hierarchy
SGML Standard Generalized Markup Language
NOTE: See ISO/IEC 8879 [14].
ETSI
13 ETSI ES 202 336-1 V1.2.1 (2011-07)
SMF Systems Management Functions
SMS Short Message System
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SOAP Simple Object Access Protocol
TCP Transmission Control Protocol for IP
TMN Telecommunications Management Network
NOTE: See ITU-T Recommendation M.3010 [5].
UDP Use Datagram Protocol
UPS Uninterruptible Power Supply
URI Uniform Resource Identifier
URL Uniform Resource Locator
USB Universal Serial Bus
VPN Virtual Private Network
WSF Work Station Function
WAN Wide Array Network
W3C World Wide Web Consortium
xDSL Digital Subscriber Line
XCU XML enabled CU
XML eXtensible Mark-up Language (see W3C)
XHTML eXtended HTML
XSD XML Schema Definition
XSL Extensible Stylesheet Language
XSLT eXtensible Stylesheet Language Transformation
XSLTb eXtensible Style Language Transformation (attribute b)
4 Monitoring and Control (M&C) overview
Monitoring and control of power, cooling and building environment systems are used to simplify operation, to reduce
maintenance time and site intervention, to reduce human error risk, to give useful data for statistical analysis and
management (i.e. operation cost, reliability or quality management, power consumption estimation).
To achieve this purpose, monitored information and control are needed:
• The information are alarms, events, measurements, data recordings and events logs.
• The controls are commands to the equipment, alarm acknowledge, configuration and settings.
Several management levels are possible for telecommunication installations and equipment. They are described
considering complexity of the system, response time and required level of details from basic alarms to complex analysis
level. In many cases, the same basic information is needed from the equipment-monitoring interface but address
different services that prepares information as requested by users categories.
4.1 Infrastructure equipment management network general
description
Infrastructure Equipment (powering, cooling, building facilities) management network is a subset of TMN.
The infrastructure equipment management network can be defined by functional interfaces between network elements.
Referring to ITU-T Recommendation M.3010 documents for nomenclature [5] and [6], the element can be understood
as generic part of Telecommunication Management Network (TMN):
• The Control Unit (CU) is dedicated to control one or more equipment in a site.
ETSI
14 ETSI ES 202 336-1 V1.2.1 (2011-07)
• The XCU connects to e.g. a legacy equipment and translates its data to conform to the "TMN" standardized
format X. The XCU may also be a unit that gathers building facilities alarm loops and makes them available in
the standardized format X. These XCU are Network Element Function (NEF) in
ITU-T Recommendation M.3010 [5].
• The Data Gathering Unit (DGU) is used to gather one or more CU field bus to adapt with TMN protocol and
format. The DGU is a Mediation Function in ITU-T Recommendation M.3010 [5] (MF).
• CU and DGU may be combined in the same unit, especially in the case of small centers where there are few
building facilities alarm loops and few equipment.
• The Local Management Application (LMA) and Remote (RMA) servers process information received from
the XCU and DGU to achieve the functionalities of the management system i.e. Operating System
Function (OSF) in ITU-T Recommendation M.3010 [5].
• LMA can be combined with XCU or DGU.
• The Exploitation Post (EP) offers the man-machine interface. It can be integrated to the LMA/RMA or not
e.g. on Mobile Exploitation Post (MEP). These entity manages the interactive presentation to the user to
monitor and control the equipment. (Work Station Function (WSF) in ITU-T Recommendation M.3010 [5]).
Several XCU and DGU can be managed within this network by one (or perhaps several) LMA, RMA. There may also
be several users connected through the network, to one server or one equipment. The application controlling such a
network with multi-user and with different user rights levels is a Network Element Management system (NEM system
in ITU-T Recommendation M.3010 [5]).
Figure 1 presents the network architecture in respect to scope requirements for communication interfaces:
• between the DGU or XCU and the LMA or RMA;
• between EP or MEP and the RMA or DGU or XCU;
• alarms contacts or loops output interface backuping IP network.
NOTE: The field level interface of CU are out of the scope:
- Equipment or room sensors interfaces to XCU or DGU.
- Interface between XCU and DGU.
ETSI
15 ETSI ES 202 336-1 V1.2.1 (2011-07)
SCOPE REQUIREMENTS
RMA : Interface, Functions, Reliability,
RMA(OSF)
Performance
Alarms
Fine monitoring & tuning
EP (WSF)
LAN and WAN OSN : Reliability, Performance
on POTS, DSL, radio, …
WAN (OSN)
(alarms synthesis path in doted line)
EP or MEP : Interface
site LAN
LMA : Interface, Functions, Reliability,
LMA (OSF)
Performance
XCU (NEF)
Equipment
DGU (MF)
Digital field bus or discrete input/outputs
XUC, DGU : Interface, Data Model, Interface
and Structure (XML, html, REST.)
Equipment
Figure 1: Scope requirements on Fu
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...