POSSIBLE Projector Subunits (Subsystems)and Their Contents
Rick Landau , Dell, andProjector & Display Management BOF2006/09/13
2
Proposal and Examples Only
• Suggestions based on model that we discussed last week
• Possible contents of the various subunits
– Suggestive lists, not exhaustive
• Long lists, need to decide later
– What to include in the specs
– What is mandatory versus optional
• Leave room for expansion
3
Need Formal Definitions
• We need to define subunits formally
– What are its purpose and content?
– How it is distinguished from other subunits?
• Then define data items within subunits formally
– Name, contents, semantics, usage
– What shall we call it, in SNMP and Web contexts?
– What does it contain? How do the agent and the user interpret its contents?
– How do the agent and the user manipulate it?
– Careful to distinguish setting versus state
– (Probably not precise data syntax, which sometimes depends on the access protocol)
4
5
Scope
• What's in, what's out
• What functions, e.g., management rather than discovery
• (Management of discovery protocols, e.g., disabling UPnP)
6
Subunits of a Projector
• General information
– Power states - RM
• Localization
• Interlocks - RBL
• Display - HM & KA
• Light Source - HM & KA
• Video Quality - HM & KA
• Optics - RBL
• Thermal Management - ND
– Fans– Filters– Temperature sensors
• System controller - RR
• Interfaces - RR
• Transports Capabilities - RR
• Interpreters & Codecs - RR
• Console
• Audio
• Alerts
• FRUs
7
General Information
• Identification
– Manufacturer, model, serial number
• Status
– Power state
– Age, unit
– Temperature, unit
• Settings
– Current language for console, SNMP, web server
– Date, time
– Power on/off
• Current status values (may be here or in related groups)
– E.g., video connector in use, video mode, audio source, etc.
8
Localization
• Language, region, character set
• If this group is absent, assume English
9
Interlocks
• Description
• Status
10
Display Capabilities
• Physical size (for display, not projector): Horizontal, Vertical, unit
(Note that Horizontal, Vertical, Width, and Height will be tricky to define, given that the device may be mounted in different positions.)
• Resolution: W pixels, H pixels
– Pixel aspect ratio
• Color model, color depth, bits
• Mounting options: landscape, portrait, upside down
• Mounting settings: front/rear, floor/ceiling, landscape/portrait
11
Signal Sources
• Video
• Audio
12
Light Source
• Lamp type, technology, part number for replacement
– Multiple lamps for some DLPs
– Even backlighting is replaceable in LCDs
– Replaceable modules of LEDs
– Maybe multiple part numbers for a single item (e.g., different brightnesses)
• Status
• Age, unit, max age
• On/off cycles
• Power save mode settings
– Blanking, standby, off (may need careful wording to avoid submarine patents)
– Timeouts, enable/disable
– No-signal image
13
Current Video State
• Current source (here or in General group? Probably general)
• Input color space: 4-2-2, 4-4-4
• input sync polarity, H and V frequencies, HxV pixels, aspect ratio, Interlace/progressive, color system
• Part of current profile– Current mode settings
• Picture mode: PowerPoint, photo, video, cinema
• Maintain aspect ratio? Stretch, crop, squeeze modes
– Appearance
• Color temperature
• Brightness, contrast, gamma (more than one parameter, choice of curve from set, separate curves per color)– Optional to protect trade secrets
• Color intensities
• Saturation, sharpness, tint
• White intensity
• Noise reduction
• H and V position, size
• closed captioning,
• dynamic color balance for colored targets (move to installation settings)
14
Saved Profiles per Source
• All the same attributes as the current state, including
– Mode
– Others (on previous page)
• Other features not stored in profile (move this)
– Picture-in-picture, picture-by-picture settings
15
Optics
• Focus level
– Autofocus enable
• Zoom level
• Keystoning H and V levels
– Autokeystone enable
(Again, Horizontal, Vertical, Up, Down, Left, Right need to be defined very carefully)
16
Thermal Management Group
• Fans
• Filters
• Temperature sensors
17
Fans
– Name, location, part number for replacement, replacement cycle
– Status
– Speed setting, reading, maybe very coarse measurements
– Maybe thresholds for speeds
18
Filters
– Name, location, part number for replacement
– Age, unit, replacement cycle
19
Temperature and other thresholds
– Multiple
– Simple sensors or scalar settings
20
System controller
• Battery backup status
• Timer programmed events
• Multiple controllers
– Identification
• Firmware versions
• Upgradeable?
– Controller status or errors, esp. for subcontrollers
• History
21
Interfaces
• (Every connector, including hand remote control)
• Enable/disable
– Including power switch
• Status
22
Transport Mechanisms XXXX
• Description
• Enable/disable
• For protocols spoken on interfaces, e.g.,
– IP parameters: addr, mask, broadcast, DNS, DHCP
– Wireless parameters: IP, WEP, WPA, wi-fi radio
– USB parameters
– IR format
– Serial line protocols
• May need to include multiple entries in the network stack, e.g., IP and HTTP, MMS, RealMedia, etc.
(The combination of interface, channel, and video mode parameters needs a very general data model, not just linear lists of settings.)
23
Transport Capabilities
(examples only, not exhaustive)
Interfaces
physical interface, e.g., ethernet
enable/disable
Transports
ISO layer 2, e.g., IP, wireless
appropriate parameters
Session protocols
RealMedia, Windows Media, SIP, RTTP
HTTP, RDP
enable/disable
Payload formats (codecs)
MPEGs, JPG, PDLs
(Associations come later)
24
Interpreters, Codecs
• Interpreter types available
– E.g., JPG, PDF
– Packetized video
– MPEG
• Capabilites, interactions between content, transport, connector
25
Console
• Buttons
– Description
– Enable/disable functions for some buttons
• Lights
– Description, color capabilities
• Physical display (e.g., LCD panel on device)
– Contents
• On-screen display
– Localizable
26
Audio
• Current source
• Settings: mute, volume, tone, treble, bass, theater sound, noise reduction
27
Alerts
• Log of previous alert conditions
• Asynchronous delivery
– Methods: traps, email, SMS, pager
• Enable/disable classes of alert conditions
• Overflow management discipline: ring buffer, aging, etc.
28
FRUs (Field Replaceable Units)
• Part numbers, and serial numbers if available, for field-replaceable units
• Subunit ID
• Description
• Part number
• Serial number
• Customer replaceable? Training level maybe.
29
Additional Questions
• Need a clear statements of intellectual property considerations
• Example:
– This specification includes no information on the subject of patents, trademarks, or licenses.
– The presence of a management object does not imply a license to implement a related feature using any particular technology.
– All vendors should submit PWG "Letter of Assurance" stating intellectual property claims and non-claims.
30
Next Steps
• Describe use cases for management of projectors and displays
• Define architectural subunits
• Establish a template for specification of a data item
• Begin to define data items, starting with easy ones
– Examples of MIBs contributed by vendors
31
Next Meeting
• Concall Monday, Sept 25 PM (US) / Tuesday, Sept 26 AM (Asia)
32
Use Cases
• Basic asset inventory: what do I have installed, what spare parts do I need to stock? ND
• Predict consumption of spares: how old are the lamps, filters, when will they need replacement? ND
• Restore device to its default setup. RBL
• Read the setup of the device to establish default. RBL
• Restore device to profile appropriate to next usage, depends on customer. RM
• Turn device on/off based on hours of operation. RR
• Turn projector off every night to save power and lamp. RR
• Predict usage of consumables based on environmental history, e.g., humidity, dust. HM
• Does the firmware need updating?
• Alert condition, send out person with right training and parts in hand.
33
Representational Considerations
• Guideline: If a management application will make decisions based on a piece of data, then the data must be rigidly structured.
– Integers instead of strings for numeric values
– Enumerated values where possible
• Need careful description of repeating groups of properties versus multi-valued properties