ISO 247913 Device Management Proposal

1
ISO 24791-3 Device Management Proposal

• by
• James McGinley Intel
• Scott Barvick Reva Systems

2
Agenda

• ISO 24791.3 Guiding Principles
• EPC Device Management Overview
• Reader Management
• Reader Operations - DCI
• ISO 24791.3 sub component overview
• Discovery Interrogator
• Discovery Interrogator Controller
• Provisioning Interrogator
• Interrogator Software Upgrade
• Configuration Interrogator
• Configuration - Interrogator Controller
• Diagnostics Performance Monitoring
• Error Reporting

3
ISO 24791-3 Guiding Principles

• ISO 24791.3 will focus on existing network
  management mechanisms (ex. SNMP) however will not
  necessarily preclude the use of emerging
  mechanisms (ex. XML)
• ISO 24791.3 will adopt and modify EPCglobal
  device management standards
• Where work is clearly ongoing in EPC but has not
  yet been ratified, ISO 24791.3 shall align with
  EPC work and wait for completion if necessary.
• Where work is not ongoing, ISO 24791.3 shall
  create as necessary
• The expectation is that direct adoption will be
  possible in most cases as by its definition
  device management is not market vertical specific
• ISO 24791.3 may have dependencies on other
  24791.x components. This shall be determined via
  joint reviews of the other components and
  agreement of partitioning within the team.

4
EPCglobal Device Management Overview

• Reader Management (RM)
• Ratified and released to public at v1 Dec 06
• http//www.epcglobalinc.org/standards/RM_Ratified_
  Standard_Dec_5_2006.pdf
• Agnostic of type of reader (fixed, handheld, etc)
  and reader technology (UHF, HF, Barcode) and by
  definition market vertical.
• Defines both an SNMP and XML MTB. Focus of
  24791-3 is on SNMP but will not preclude other
  MTB development at a later point if deemed
  necessary by the market.
• No further work yet chartered for Reader
  Management group.
• Reader Operations WG DCI ongoing work is
  applicable to device provisioning.
• Standard mechanisms for provisioning already
  common place in network management arena.
• New service discovery specification developing
• Reader Operations WG chartered with developing
  standards that will be applicable to 24791-5

5
EPCglobal Device Management Overview

• EPCglobal RM Object Model in 24791-1 Architecture

6
EPCglobal Device Management Overview

• RM Object Model-to-MIB module examples
• epcgReaderNotifs OBJECT IDENTIFIER
  epcgReaderMIB 0
• epcgReaderObjects OBJECT IDENTIFIER
  epcgReaderMIB 1
• epcgReaderConformance OBJECT IDENTIFIER
  epcgReaderMIB 2
• epcgReaderDevice OBJECT IDENTIFIER
  epcgReaderObjects 1
• epcgReadPoints OBJECT IDENTIFIER
  epcgReaderObjects 2
• epcgAntennaReadPoints OBJECT IDENTIFIER
  epcgReaderObjects 3
• epcgIoPorts OBJECT IDENTIFIER
  epcgReaderObjects 4
• epcgSources OBJECT IDENTIFIER
  epcgReaderObjects 5
• epcgNotificationChannels OBJECT IDENTIFIER
  epcgReaderObjects 6
• epcgTriggers OBJECT IDENTIFIER
  epcgReaderObjects 7

7
EPCglobal Device Management Overview

• RO Discovery, Configuration, Initialization
  (DCI)
• 2 Phase model taking shape
• Network Provisioning
• Based on existing network operations
• Static configuration and DHCP-based operation
• Consensus on this part, supports contributed use
  cases
• Service Discovery
• Provides dynamic discovery of firmware,
  configuration, and LLRP client services
• IETF CAPWAP protocol provides these services,
  others possible

8
EPCglobal Device Management Overview
DCI Overview
Phase 1Resolution
Phase 2Resolution
Start RO
(Static/manual, DHCP, DNS)
(Static/manual,CAPWAP, XML/SOAP/HTTP)
(LLRP, HLRP)
9
IP Configuration - Interrogator

• Theory
• Defines how the interrogator obtains it network
  address and related information. Need model which
  supports multiple methods, including
• Static always needs to be a possibility
• Dynamic required for scalable implementations
• This standard may address discovery of
  interrogator IP address by other entities in the
  architecture including SNMP management systems
  and RO clients.
• Example Implementation
• Static IP information pre-configured
• Dynamic IP obtained through DHCP, with options
  as a possibility
• Dynamic discovery of end system IP addresses by
  SNMP management systems is possible, both on
  local and remote network segments.
• EPC Status
• Consensus in Reader Operations DCI group on the
  use of static and DHCP-based interrogator IP
  address allocation.

10
Discovery - Interrogator Controller

• Theory
• Related to discovery of service capabilities for
  Device Interface Client. Provisioning of IP
  address of host platform not in scope.
• Example Implementation
• DHCP options at reader IP address acquisition
  time could provide Device Interface Client
  endpoint IP address(es)
• Multicast/broadcast network service discovery
  possible for low configuration discovery
• EPC Status
• Reader Operations Group DCI refining functional
  requirements for service discovery to be followed
  by specification of applicable protocols.

11
Provisioning - Interrogator

• Theory
• Provisioning of deployment services at
  initialisation and also update of provisioning
  information during normal operation. Also covers
  software image management. Need model to support
  multiple scenarios
• Pre-configured devices
• Dynamic provisioning at any time during operation
• May include security credentials as defined in
  24791-6
• Example Implementation
• DHCP/BootP options can provide configuration file
  and image to download
• IETF CAPWAP does this for wifi
• EPC Status
• Reader Operations Group DCI refining functional
  requirements for services to be followed by
  specification of applicable protocols.

12
Software Upgrade

• Theory
• Ability to change software version during
  Interrogator operation. Could be push or pull,
  several feature and infrastructure options here.
• Example Implementation
• DHCP/BootP forced renew operation
• IETF CAPWAP does this for wifi
• EPC Status
• Reader Operations Group DCI refining functional
  requirements for service providers to be followed
  by specification of applicable protocols.

13
Configuration - Interrogator

• Theory
• Process of setting operational parameters that
  change relatively infrequently. These
  parameters lie between Provisioning and
  Operational control through Device Interface.
• Need to define partitioning between device
  management 24791.5 device interface
• Difficult to standardize because common
  representation of parameters across vendors'
  implementation are difficult.
• May include security credentials as defined in
  24791-6
• Example Implementation
• SNMP with writable attribute for example an
  Admin/Operational state for a read points would
  be attributes you may expect to be on any reader.
• EPC Status
• Some attributes captured by EPC RM Spec, ex.
  ReadPoint Admin States

14
Configuration Data Management Service Endpoint

• Theory
• Process of setting operational parameters that
  change relatively infrequently. These
  parameters lie between Provisioning and
  Operational control through Device Interface.
  Separation of Data Management endpoint from
  computing platform helps ability to standardize
  here.
• Example Implementation
• SNMP with writable attributes
• Web Service interface
• EPC Status
• EPCglobal architecture has a provision for this
  function, but no work underway

15
Diagnostics

• Theory
• Hardware diagnostics on Interrogator, software on
  other components
• Usually not standardised on any technology as are
  very implementation specific. May not be anything
  we can standardise on for interrogator.
• Example Implementation
• Usually very implementation specific. For example
  in the telecoms industry a product may have a
  test loopback mode.
• EPC Status
• No work underway on this topic.

16
Performance Monitoring

• Theory
• Capturing of statistics which would be useful in
  determining the health of operation of the
  device. For example and state data to assess
  proper operation
• Will need to limit to common attributes across
  various protocols
• Example Implementation
• SNMP MIB, for example reads success, read
  fails, etc.
• Web Service
• EPC Status
• Reader Management MIB contains various PM
  counters.

17
Error Reporting

• Theory
• The error reporting sections seeks to define,
  generic error conditions associated with RIFD
  interrogators. It also provides guidelines to
  allow interrogator vendors define enterprise
  extensions and a mechanism which allows system
  level device management applications maintain an
  accurate view of the health of an RFID
  interrogator.
• Example Implementation
• Define list of generic reports initialization
  complete, provisioning failure, performance
  monitoring alerts
• Define list of minimal information contained by
  report report id, report unique sequence number,
  time date, etc.
• EPC Status
• Reader Management defines common error conditions