|
ETSI Standard
Environmental Engineering (EE);
Monitoring and control interface for
infrastructure equipment (Power, Cooling and
environment systems used in telecommunication networks);
Part 2: DC power system control and
monitoring information model
---------------------- Page: 1 ----------------------
2 ETSI ES 202 336-2 V1.1.1 (2009-03)
Reference
DES/EE-02037-2
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 2009.
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
---------------------- Page: 2 ----------------------
3 ETSI ES 202 336-2 V1.1.1 (2009-03)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 9
4 DC power supply system . 10
Annex A (normative): Summary of mandatory monitoring/supervision information and
f unctions . 12
A.1 DC POWER SUPPLY SYSTEMS . . 12
A.1.1 Table for DC power supply system without back-up . 12
A.1.2 Table for DC power supply system with back-up . 13
Annex B (informative): Summary of non-mandatory monitoring/supervision information
and functions . 15
B.1 DC power supply system without back-up . 15
B.2 DC power supply system with back-up . 16
B.3 DC power supply rectifier . 17
Annex C (normative): Mandatory XML structure and elements . 18
C.1 Structure of an XML document for a DC power supply system . 18
C.2 The specific XML elements of a DC power supply system . 19
Annex D (informative): Examples of XML elements for a DC power supply system . 20
D.1 The elements of a DC power supply system . 20
D.2 The elements of a DC power supply system . 21
D.3 The elements of a DC power supply system . 21
D.4 The elements of a DC power supply system . 22
D.5 The elements of a DC power supply system . 22
D.6 The elements of a DC power supply system. 22
D.7 The elements of a DC power supply system . 23
D.8 The elements of a DC power supply rectifier . 23
D.9 The elements of a DC power supply rectifier . 23
D.10 The elements of a DC power supply rectifier. 23
D.11 The elements of a DC power supply rectifier. 23
D.12 The elements of a DC power supply rectifier . 24
D.13 The elements of a DC power supply rectifier . 24
ETSI
---------------------- Page: 3 ----------------------
4 ETSI ES 202 336-2 V1.1.1 (2009-03)
Annex E (informative): Bibliography . 25
History . 26
ETSI
---------------------- Page: 4 ----------------------
5 ETSI ES 202 336-2 V1.1.1 (2009-03)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Environmental Engineering (EE).
The present document is part 2 of a multi-part deliverable covering Monitoring and control interface for infrastructure
equipment (Power, Cooling and environment systems used in telecommunication networks), 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".
ETSI
---------------------- Page: 5 ----------------------
6 ETSI ES 202 336-2 V1.1.1 (2009-03)
1 Scope
The present document applies to monitoring and control of DC power supply systems for telecommunication
equipment.
The present document defines:
• The monitored and controlled DC power supply system architectures.
• The minimum set of exchanged information required at the interface, described in "natural language" in text
tables.
• The XML files with tags and variables corresponding to the data in the tables.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
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 indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 202 336-1: "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 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".
ETSI
---------------------- Page: 6 ----------------------
7 ETSI ES 202 336-2 V1.1.1 (2009-03)
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] IEEE 802.1 to 11: "IEEE Standard for Local and Metropolitan Area Networks: Overview and
Architecture".
[i.2] ISO/IEC 10164 (all parts): "Information technology - Open Systems Interconnection".
[i.3] ISO/IEC 8879:"Information processing - Text and office systems - Standard Generalized Markup
Language (SGML)".
[i.4] IEC 60896 (all parts): "Stationary lead-acid batteries".
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
standards 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 should be understood by itself by an operator and should always have at least one
severity qualification or codification (colour, level, etc.). Example: rectifier failure, battery low voltage,
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 block: battery cell (e.g. 2 V for lead-acid) connected and placed in the same container (forming 4 V, 6 V or
12 V blocks)
battery cell: basic electrochemical element (e.g. a 2 Vnominal cell for a high capacity 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
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
---------------------- Page: 7 ----------------------
8 ETSI ES 202 336-2 V1.1.1 (2009-03)
Data Gathering Unit (DGU): functional unit used for several functions:
• collect serial, digital, and analog data from several equipment;
• 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 Control Protocol (DHCP): protocol used for self configuration of TCP/IP parameters of a workstation
assigning IP address and a subnetwork 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 [i.1].
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 event signal should be understood by itself by an operator and should always have at least one
severity qualification or codification (colour, level, etc.). It should be 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".
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.
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
ETSI
---------------------- Page: 8 ----------------------
9 ETSI ES 202 336-2 V1.1.1 (2009-03)
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 [i.2].
warning: low severity alarm
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.
Windows: virtual area on the display that corresponds to a specific application
web: common name for the Internet or Intranet
XCU: CU enabled to communicate using XML interface as defined in the present document
XHTML: stricter and cleaner version of HTML. XHTML consists of all the elements in HTML 4.01 combined with
the syntax of XML. It can be read by all XML browser (see W3C)
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 [i.3]). documents.XML is designed to describe data and focus on what data is. XML
should be discerned from the well known Hypertext Transfer Mark-up Language (HTML) which was
designed to display data and to focus on how data looks.
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:
CSS Control form Style Sheet
CU Control Unit of an equipment
DGU Data Gathering Unit
DHCP Dynamic Host Control Protocol
DNS Dynamic Name Server
DTD Document Type Definition
HTML Hypertext Transfer Make-up Language
HTTP Hypertext Transfer Protocol
I Average output load current (DC)
Av
I Total battery current (DC)
Batt
I Total output load current (DC)
Load
IP Internet Protocol
I Total rectifier output current (DC)
Rect
LAN Local Array Network
MIB Management Information Base
MN Management network
ETSI
---------------------- Page: 9 ----------------------
10 ETSI ES 202 336-2 V1.1.1 (2009-03)
PHP Hypertext Preprocessor
REST REpresentational State Transfer
RMA Remote Management Application
SMF Systems Management Function
SOAP Simple Object Access Protocol
TCP Transmission Control Protocol for IP
W3C World Wide Web Consortium
XCU XML enabled CU
XML eXtensible Markup Language (see W3C)
XSD XML Schema Definition
XSL eXtensible Style sheet Language
4 DC power supply system
The DC system subset described in ES 202 336-1 [1] transforms AC interface from mains or AC back-up engine
defined in EN 300 132-3 [3], in DC voltage on interface A defined in EN 300 132-2 [2] or EN 300 132-3 [3] for
telecom centre or defined for local or remote power supply of access network equipment in EN 302 099 [4].
The DC power systems addressed by the present document are depicted in figures 1 and 2. One single control unit XCU
can monitor and control several power cabinets through field bus. Field bus is outside the scope of the present
document.
Mandatory monitoring/ supervision information and functions are given in annex A.
Non-mandatory (optional) monitoring/ supervision information and functions are given in annex B.
Figure 1: Simple DC power supply system with no battery backup
Rectifier Modules
Output
distribution
IRect ILoad
AC DC Bus (V dc)
IBatt
AC
AC
Battery strings
Figure 2: Modular DC power supply system with battery backup
ETSI
---------------------- Page: 10 ----------------------
11 ETSI ES 202 336-2 V1.1.1 (2009-03)
The main elements of DC power supply systems are:
- Rectifier (one or more) that converts AC voltage to DC voltage (i.e. 230 VAC to DC voltage).
NOTE: Other alternative energy sources may be used to provide DC power e.g. Photovoltaic, wind turbine, etc.
- Battery (one or more strings of cells) that stores energy and can power the loads when AC interrupts or
rectifiers fail. There can be test and permanent battery monitoring system to reduce the failure detection time
and the MTTR.
- Protection and distribution (DC bus, breaker, etc.) to power different user loads and discriminate faults
- A system monitoring and control unit (XCU) to monitor voltage, current, power, temperature, etc., extend
alarms and provide system control functionality.
Several measurements are possible: rectifier states, rectifier voltage and current, battery voltage, current and
temperature, user load currents, etc.
Several controls are possible to adjust rectifier voltage and current, to optimize the load between rectifiers for energy
saving and higher reliability, to start a battery test procedure.
Table TP1 (Table Power in annex A) corresponds to mandatory data that shall be provided for a minimal DC system
without back-up, and TP1x (see annex B) includes data that should be provided in addition to mandatory one.
Table TP2 (see annex B) corresponds to mandatory data that shall be provided for a common rectifier/battery DC
system with back-up, and TP2x (see annex B) includes data that should be provided in addition to mandatory one.
Annex C standardizes XML coding structures for these data.
ETSI
---------------------- Page: 11 ----------------------
12 ETSI ES 202 336-2 V1.1.1 (2009-03)
Annex A (normative):
Summary of mandatory monitoring/supervision information
and functions
This annex gathers the information needed on the Remote Management Application (RMA) for different types of power
supplies. It specifies the mandatory requirements that must be provided in all cases.
NOTE 1: These tables do not specify the power equipment by itself. These tables refer to subsets or devices that are
not necessarily present in each equipment configuration. As a matter of fact, one alarm and its class apply
only in case of the presence of this subset or device.
When an optional alarm that requires a parameter set is present, the corresponding parameter set is mandatory in the
control section in order to allow remote adjustment under appropriate login procedure.
According to their element type (Description, Alarm, Data, etc.), as defined in ES 202 336-1 [1] the information shall
be provided by the Control Unit (XCU).
NOTE 2: If there is no XCU this data should be provided by the Data Gathering Unit (DGU).
When a CU has a field databus connected to the DGU, at least, the DGU shall store data (record measurements, log
files). The XCU which has the XML interface over Ethernet TCP/IP, shall store these data.
NOTE 3: The "Explanation" column provided in the following data tables has been used where necessary to further
explain the statements in the "Monitored information" column. The "Element type" column gives the
assigned name used in XML coding and the "Monitored information" column provides details of the
condition or state being monitored. The identifiers used in the Type column of the following tables are
described in ES 202 336-1 [1].
NOTE 4: Partial communication network failures e.g. XCU link fault should be detected by an upper element of the
network e.g. the RMA (refer to figure 1 of ES 202 336-1 [1]).
NOTE 5: Clause 9.4.4 of ES 202 336-1 [1] details the parameters associated with XML elements e.g. time delay,
severity of alarm element. The tables below do not include the application of these parameters.
A.1 DC POWER SUPPLY SYSTEMS
A.1.1 Table for DC power supply system without back-up
Table TP1 minimum set of monitored information
Element type Monitored information Explanation
description Device description
One rectifier failure at least
alarm
Partial network failure (high error rate, XCU-DGU link fault, etc.)
event None
data None
data record None
config None
All XCU alarm/event/test/command parameters (time-out, counter, thresholds, etc.) if
any
control
XCU program download with default to previous release
Default values resetting (safe value for XCU)
ETSI
---------------------- Page: 12 ----------------------
13 ETSI ES 202 336-2 V1.1.1 (2009-03)
A.1.2 Table for DC power supply system with back-up
NOTE: Partial network failure (high error rate, XCU-DGU link fault, etc.) is raised by the DGU, not the DC
power system.
Any network communication failure on the DC XCU interface shall be detected by the DC power supervision unit.
Table TP2 minimum set of monitored information
Element type Monitored information Explanation
description device description (hardware and software)
Input/output and battery protective device (gathered or unitary information) AC or DC
Fuse/Circuit Breaker
open or tripped
Battery discharge (e.g. due to mains loss, mains out of limits or not enough rectifier
power)
Battery test failure Battery failed to pass
defined test criteria
e.g. autonomy time,
voltage threshold
Output low voltage Voltage of the DC bus
falls below pre-set
threshold, e.g. due to
battery discharge
Battery over-temperature Battery temperature
exceeds high limit
alarm
setting
One rectifier failure Failure of a single
rectifier module
e.g. loss of DC power
output
Greater than one rectifier failure Failure of more than
one rectifier module
e.g. loss of DC power
output from greater
than one rectifier
Mains failure Loss of AC input to
DC power system
XCU reset Indication of restart
by user or automatic
watchdog
Alarm set and clear
Details of any change of configuration of DC system Change of
configuration
e.g. float voltage
event change from 54,5 V
to 55 V
Change of operating mode of DC system Change of operation
e.g. Boost charge ,
battery operation ,
battery test,
DC voltage (±0,1 V)
- this precision is required for floating voltage (e.g. 54,6 V) derating detection
and temperature charge compensation (around -3 mV/K/cell).
Charge and discharge battery current I
Batt
DC output load current I (±2 %) Can be measured
Load
directly or calculated
data
from measured
values of total rectifier
output current minus
the battery current
i.e. I = I - I
Load Rect Batt
Average value of DC output load current I (±5 %) over a preset time window
Av
ETSI
---------------------- Page: 13 ----------------------
14 ETSI ES 202 336-2 V1.1.1 (2009-03)
Element type Monitored information Explanation
Battery discharge alarm duration Time period over
which battery is
discharging e.g.
caused by actual
mains supply failure
or insufficient output
power from rectifiers
due to failure.
Battery temperature (±2°C)
XCU program download with default to previous release
Battery temperature Battery temperature
data log at 1 hour
interval limited to a
defined number of
records
DC output current Average current data
log e.g. at 5 min
data record
interval limited to a
defined number of
records
DC output voltage Voltage record e.g. at
1 hour interval limited
to a defined number
of records
Date and time
Sliding time window to capture maximum output DC current Period of time over
config
All XCU alarm/event/test/command parameters (time-out, counter, thresholds, etc.) which power data
logging is carried out
Any forced change of operating mode e.g. battery discharge test, boost charge
control XCU program download with default to previous release
Default values resetting (safe value for XCU)
ETSI
---------------------- Page: 14 ----------------------
15 ETSI ES 202 336-2 V1.1.1 (2009-03)
Annex B (informative):
Summary of non-mandatory monitoring/supervision
information and funct
...