scope:

Overview and Scope

This service definition is compliant with the UPnP Device Architecture version 1.0.

This service-type provides an indication about house occupancy status and operational mode. It is commonly used as a mechanism for influencing the state of Devices and/or Control Points depending upon whether people are in the house. Typical applications are: e.g. switching on or off lights, air-conditioning etc.

Occupancy status can be derived i) directly from an occupant via a user interface, or ii) indirectly by algorithms such as a calendar program, or iii) indirectly by heuristics that determine the status from subsystem or device activity. That is to say: this service type would be implemented in two types of occupancy "detector" devices:

• A physical switch (e.g. a home/away push button on a device).

• A "virtual" switch that uses some kind of algorithm or heuristics to work out if the house is occupied (e.g. a calendar or a predictive algorithm).

In case a) the physical detection device would incorporate this occupancy service, but in case b) the MMI of the device that contains the algorithm would incorporate this occupancy service.

This service is a "source" of UPnP event messages. Control Points that are interested to be updated about the occupancy state of the house should subscribe to receive events from this service type. (However, Control Points are also permitted to "poll" the service from time to time in order to enquire about the current occupancy state).

This service template does not address:

• Presence detection for security alarm purposes.

• Actual number of persons in the building (or building part) e.g. for demand controlled ventilation in (say) a conference room.