< draft-ietf-eman-battery-mib-17.txt   draft-ietf-eman-battery-mib-18.txt >
Network Working Group J. Quittek Network Working Group J. Quittek
Internet-Draft R. Winter Internet-Draft R. Winter
Intended status: Standards Track T. Dietz Intended status: Standards Track T. Dietz
Expires: June 20, 2015 NEC Europe Ltd. Expires: September 25, 2015 NEC Europe Ltd.
December 17, 2014 March 24, 2015
Definition of Managed Objects for Battery Monitoring Definition of Managed Objects for Battery Monitoring
draft-ietf-eman-battery-mib-17 draft-ietf-eman-battery-mib-18
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines managed objects that provide information on In particular, it defines managed objects that provide information on
the status of batteries in managed devices. the status of batteries in managed devices.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 20, 2015. This Internet-Draft will expire on September 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 5 2. The Internet-Standard Management Framework . . . . . . . . . . 6
3. Design of the Battery MIB Module . . . . . . . . . . . . . . . 6 3. Design of the Battery MIB Module . . . . . . . . . . . . . . . 7
3.1. MIB Module Structure . . . . . . . . . . . . . . . . . . . 6 3.1. MIB Module Structure . . . . . . . . . . . . . . . . . . . 7
3.2. Battery Technologies . . . . . . . . . . . . . . . . . . . 8 3.2. Battery Technologies . . . . . . . . . . . . . . . . . . . 9
3.2.1. Guidelines for Adding Battery Technologies . . . . . . 9 3.2.1. Guidelines for Adding Battery Technologies . . . . . . 10
3.3. Battery Identification . . . . . . . . . . . . . . . . . . 9 3.3. Battery Identification . . . . . . . . . . . . . . . . . . 10
3.4. Charging Cycles . . . . . . . . . . . . . . . . . . . . . 10 3.4. Charging Cycles . . . . . . . . . . . . . . . . . . . . . 11
3.5. Imported Definitions . . . . . . . . . . . . . . . . . . . 10 3.5. Imported Definitions . . . . . . . . . . . . . . . . . . . 11
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 32 5. Security Considerations . . . . . . . . . . . . . . . . . . . 33
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
6.1. SMI Object Identifier Registration . . . . . . . . . . . . 34 6.1. SMI Object Identifier Registration . . . . . . . . . . . . 36
6.2. Battery Technology Registration . . . . . . . . . . . . . 35 6.2. Battery Technology Registration . . . . . . . . . . . . . 36
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.1. Normative References . . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . . 37
8.2. Informative References . . . . . . . . . . . . . . . . . . 36 8.2. Informative References . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
Today, more and more managed devices contain batteries that supply Today, more and more managed devices contain batteries that supply
them with power when disconnected from electrical power distribution them with power when disconnected from electrical power distribution
grids. Common examples are nomadic and mobile devices, such as grids. Common examples are nomadic and mobile devices, such as
notebook computers, netbooks, and smart phones. The status of notebook computers, netbooks, and smart phones. The status of
batteries in such a device, particularly the charging status is batteries in such a device, particularly the charging status is
typically controlled by automatic functions that act locally on the typically controlled by automatic functions that act locally on the
device and manually by users of the device. device and manually by users of the device.
skipping to change at page 3, line 26 skipping to change at page 3, line 26
these devices by network management systems. This document defines a these devices by network management systems. This document defines a
portion of the Management Information Base (MIB) that provides a portion of the Management Information Base (MIB) that provides a
means for monitoring batteries in or attached to managed devices. means for monitoring batteries in or attached to managed devices.
The Battery MIB module defined in Section 4 meets the requirements The Battery MIB module defined in Section 4 meets the requirements
for monitoring the status of batteries specified in RFC 6988 for monitoring the status of batteries specified in RFC 6988
[RFC6988]. [RFC6988].
The Battery MIB module provides for monitoring the battery status. The Battery MIB module provides for monitoring the battery status.
According to the framework for energy management [RFC7326] it is an According to the framework for energy management [RFC7326] it is an
Energy Managed Object, and thus, MIB modules such as the Power and Energy Managed Object, and thus, MIB modules such as the Power and
Energy Monitoring MIB [I-D.ietf-eman-energy-monitoring-mib] could in Energy Monitoring MIB [RFC7460] could in principle be implemented for
principle be implemented for batteries. The Battery MIB extends the batteries. The Battery MIB extends the more generic aspects of
more generic aspects of energy management by adding battery-specific energy management by adding battery-specific information. Amongst
information. Amongst other things, the Battery MIB enables the other things, the Battery MIB enables the monitoring of:
monitoring of:
o the current charge of a battery, o the current charge of a battery,
o the age of a battery (charging cycles), o the age of a battery (charging cycles),
o the state of a battery (e.g. being re-charged), o the state of a battery (e.g. being re-charged),
o last usage of a battery, o last usage of a battery,
o maximum energy provided by a battery (remaining and total o maximum energy provided by a battery (remaining and total
capacity). capacity).
Further, means are provided for battery-powered devices to send Further, means are provided for battery-powered devices to send
notifications when the current battery charge has dropped below a notifications when the current battery charge has dropped below a
skipping to change at page 4, line 28 skipping to change at page 4, line 27
A traditional type of managed device containing batteries is an A traditional type of managed device containing batteries is an
Uninterruptible Power Supply (UPS) system; these supply other devices Uninterruptible Power Supply (UPS) system; these supply other devices
with electrical energy when the main power supply fails. There is with electrical energy when the main power supply fails. There is
already a MIB module for managing UPS systems defined in RFC 1628 already a MIB module for managing UPS systems defined in RFC 1628
[RFC1628]. The UPS MIB module includes managed objects for [RFC1628]. The UPS MIB module includes managed objects for
monitoring the batteries contained in an UPS system. However, the monitoring the batteries contained in an UPS system. However, the
information provided by the UPS MIB objects is limited and tailored information provided by the UPS MIB objects is limited and tailored
the particular needs of UPS systems. the particular needs of UPS systems.
There is a huge variety of battery technologies and it is evolving in
time. For different applications, different battery technologies are
preferable, for example, because of different weight, cost,
robustness, charging time, etc. Some technologies, such as lead acid
batteries are constantly in use for decades, while others, such as
nickel based battery technologies (nickel-cadmium, nickel-metal
hydride) have to a wide extend been replaced by lithium based battery
technologies (lithium-ion, lithium polymer).
The Battery MIB module uses a generic abstraction of batteries that
is independent of particular battery technologies and expected to be
applicable to future technologies as well. While identification of a
particular battery technology is supported by an extensible list of
battery technology identifiers (see Section 3.2), individual
properties of the technologies are not modelled by the abstraction.
In particular, methods for charging a battery and their parameters,
that vary a lot between different technologies, are not individually
modelled.
Instead, the Battery MIB module uses a simple common charging model
with batteries being in one of the states 'charging', 'maintaining
charge', 'not charging', and 'discharging'. Control of the charging
process is limited to requests for transitions between these states.
For charging controllers that use charging state engines with more
states, implementations of the Battery MIB module need to map those
states to the four listed ones.
For energy management systems that require finer grained control of
the battery charging process, additional means need to be developed,
such as, for example, MIB modules that model richer sets of charging
states and parameters for charging states.
All use cases sketched above assume that the batteries are contained All use cases sketched above assume that the batteries are contained
in a managed entity. In a typical case, this entity also hosts the in a managed entity. In a typical case, this entity also hosts the
SNMP applications (command responder, notification generator) and the SNMP applications (command responder, notification generator) and the
charging controller for contained batteries. For definitions in this charging controller for contained batteries. For definitions in this
document it is not strictly required that batteries are contained in document it is not strictly required that batteries are contained in
the same managed entity, even though the BATTERY-MIB module, that is the same managed entity, even though the BATTERY-MIB module, that is
defined further below, uses the containment tree of the ENTITY-MIB defined further below, uses the containment tree of the ENTITY-MIB
module [RFC6933] for battery indexing. module [RFC6933] for battery indexing.
External batteries can be supported as long as the charging External batteries can be supported as long as the charging
skipping to change at page 16, line 51 skipping to change at page 17, line 51
A value of 0 indicates that the maximal charging current is A value of 0 indicates that the maximal charging current is
unknown." unknown."
::= { batteryEntry 8 } ::= { batteryEntry 8 }
batteryTrickleChargingCurrent OBJECT-TYPE batteryTrickleChargingCurrent OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliampere" UNITS "milliampere"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object provides the recommended current to be used for "This object provides the recommended average current
trickle charging the battery in units of milliampere (mA). to be used for trickle charging the battery in units of
milliampere (mA).
Typically, this is a value recommended by the manufacturer Typically, this is a value recommended by the manufacturer
of the battery or by the manufacturer of the charging of the battery or by the manufacturer of the charging
circuit. circuit.
A value of 0 indicates that the recommended trickle charging A value of 0 indicates that the recommended trickle charging
current is unknown." current is unknown."
::= { batteryEntry 9 } ::= { batteryEntry 9 }
batteryActualCapacity OBJECT-TYPE batteryActualCapacity OBJECT-TYPE
skipping to change at page 18, line 30 skipping to change at page 19, line 31
determined. determined.
For batteries of type primary(1) the value of this object is For batteries of type primary(1) the value of this object is
always '0000000000000000'H." always '0000000000000000'H."
::= { batteryEntry 12 } ::= { batteryEntry 12 }
batteryChargingOperState OBJECT-TYPE batteryChargingOperState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
charging(2), charging(2),
fastCharging(3), maintainingCharge(3),
maintainingCharge(4), noCharging(4),
noCharging(5), discharging(5)
discharging(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the current charging state of the "This object indicates the current charging state of the
battery. battery.
Value unknown(1) indicates that the charging state of the Value unknown(1) indicates that the charging state of the
battery cannot be determined. battery cannot be determined.
Value charging(2) indicates that the battery is being Value charging(2) indicates that the battery is being
charged in a way that the charge of the battery increases. charged in a way that the charge of the battery increases.
Value fastCharging(3) indicated that the battery is being Value maintainingCharge(3) indicates that the battery is
charged rapidly, i.e. faster than in the charging(2) state. being charged with a low average current that compensates
If multiple fast charging states exist, all of these
states are indicated by fastCharging(3).
Value maintainingCharge(4) indicates that the battery is
being charged with a low current that compensates
self-discharging. This includes trickle charging, float self-discharging. This includes trickle charging, float
charging and other methods for maintaining the current charging and other methods for maintaining the current
charge of a battery. charge of a battery. In typical implementations of charging
controllers, state maintainingCharge(3) is only applied
if the battery is fully charged or almost fully charged.
Value noCharging(5) indicates that the battery is not being Value noCharging(4) indicates that the battery is not being
charged or discharged by electric current between the charged or discharged by electric current between the
battery and electric circuits external to the battery. battery and electric circuits external to the battery.
Note that the battery may still be subject to Note that the battery may still be subject to
self-discharging. self-discharging.
Value discharging(6) indicates that the battery is being Value discharging(5) indicates that the battery is being
discharged and that the charge of the battery decreases." discharged and that the charge of the battery decreases."
::= { batteryEntry 13 } ::= { batteryEntry 13 }
batteryChargingAdminState OBJECT-TYPE batteryChargingAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
charging(2), notSet(1),
fastCharging(3), charge(2),
maintainingCharge(4), chargeAndMaintainCharge(3),
noCharging(5), doNotCharge(4),
discharging(6), discharge(5)
notSet(7)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates the desired "The value of this object indicates the desired
charging state of the battery. The real state is charging state of the battery. The real state is
indicated by object batteryChargingOperState. See the indicated by object batteryChargingOperState. See the
definition of object batteryChargingOperState for a definition of object batteryChargingOperState for a
description of the values. description of the values.
When this object is initialized by an implementation of the When this object is initialized by an implementation of the
BATTERY-MIB module, its value is set to notSet(7). BATTERY-MIB module, its value is set to notSet(1).
However, a SET request can only set this object to either However, a SET request can only set this object to either
charging(2), fastCharging(3), maintainingCharge(4), charge(2), chargeAndMaintainCharge(3), doNotCharge(4), or
noCharging(5), or discharging(6). Attempts to set this discharge(5). Attempts to set this object to notSet(1)
object to notSet(7) will always fail with an will always fail with an 'inconsistentValue' error.
'inconsistentValue' error. In case multiple fast charging
states exist, the battery logic can choose an appropriate
fast charging state - preferably the fastest.
When the batteryChargingAdminState object is set, then the When the batteryChargingAdminState object is set, then the
BATTERY-MIB implementation must try to set the battery BATTERY-MIB implementation must try to set the battery
to the indicated state. The result will be indicated by to the indicated state. The result will be indicated by
object batteryChargingOperState. object batteryChargingOperState.
Setting object batteryChargingAdminState to value
chargeAndMaintainCharge(3) is a request for first
charging the battery in state charging(2) and then
entering state maintainingCharge(3). If the battery
is already fully charged or almost fully charged,
then setting object batteryChargingAdminState to value
chargeAndMaintainCharge(3) is a request for entering
state maintainingCharge(3).
Setting object batteryChargingAdminState to value
charge(2) is a request for first entering operational
state charging(2) until the battery is fully charged
and then entering operational state noCharging(4).
When operational state noCharging(4) is entered, the
value of object batteryChargingAdminState is reset to
notSet(1).
If the battery is already fully charged or almost fully
charged, then setting object batteryChargingAdminState
to value charge(2) is a request for entering state
noCharging(4). When operational state noCharging(4) is
entered, the value of object batteryChargingAdminState
is reset to notSet(1).
Setting object batteryChargingAdminState to value
doNotCharge(4) is a request for entering operational
state noCharging(4).
Setting object batteryChargingAdminState to value
discharge(5) is a request for entering operational
state discharging(5).
Due to operational conditions and limitations of the Due to operational conditions and limitations of the
implementation of the BATTERY-MIB module, changing the implementation of the BATTERY-MIB module, changing the
battery status according to a set value of object battery status according to a set value of object
batteryChargingAdminState may not be possible. batteryChargingAdminState may not be possible.
Setting the value of object batteryChargingAdminState Setting the value of object batteryChargingAdminState
may result in not changing the state of the battery may result in not changing the state of the battery
to this value or even in setting the charging state to this value or even in setting the charging state
to another value. For example, setting to another value than the requested one. For example,
batteryChargingAdminState to value fastCharging(3) may the charging controller might at any time decide to
have no effect when the battery logic is not allowing enter state discharging(5), if there is an operational
fast charging due to temperature constraints." need to use the battery for supplying power."
::= { batteryEntry 14 } ::= { batteryEntry 14 }
batteryActualCharge OBJECT-TYPE batteryActualCharge OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliampere hours" UNITS "milliampere hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object provides the actual charge of the battery "This object provides the actual charge of the battery
in units of milliampere hours (mAh). in units of milliampere hours (mAh).
skipping to change at page 37, line 5 skipping to change at page 38, line 26
8.2. Informative References 8.2. Informative References
[RFC6988] Quittek, J., Chandramouli, M., Winter, R., Dietz, T., and [RFC6988] Quittek, J., Chandramouli, M., Winter, R., Dietz, T., and
B. Claise, "Requirements for Energy Management", RFC 6988, B. Claise, "Requirements for Energy Management", RFC 6988,
September 2013. September 2013.
[RFC7326] Parello, J., Claise, B., Schoening, B., and J. Quittek, [RFC7326] Parello, J., Claise, B., Schoening, B., and J. Quittek,
"Energy Management Framework", RFC 7326, September 2014. "Energy Management Framework", RFC 7326, September 2014.
[I-D.ietf-eman-energy-monitoring-mib] [RFC7460] Chandramouli, M., Claise, B., Schoening, B., Quittek, J.,
Chandramouli, M., Claise, B., Schoening, B., Quittek, J., and T. Dietz, "Monitoring and Control MIB for Power and
and T. Dietz, "Power, Energy Monitoring and Control MIB", Energy", RFC 7460, March 2015.
draft-ietf-eman-energy-monitoring-mib-13 (work in
progress), November 2014.
[RFC1628] Case, J., "UPS Management Information Base", RFC 1628, [RFC1628] Case, J., "UPS Management Information Base", RFC 1628,
May 1994. May 1994.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[SBS] "Smart Battery Data Specification", Revision 1.1, [SBS] "Smart Battery Data Specification", Revision 1.1,
December 1998. December 1998.
 End of changes. 27 change blocks. 
68 lines changed or deleted 120 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/