Mesh Model

When specification content indicates that there are multiple alternatives to satisfy specification requirements, if one alternative is explained or illustrated in an example it is not intended to limit other alternatives that the specification requirements permit.

It is the goal of Bluetooth SIG that specifications are clear, unambiguous, and do not contain discrepancies. However, members can report any perceived discrepancy by filing an erratum and can request a test case waiver as appropriate.

When a state is bound to another state, a change in one state results in a change in the other state. Bound states may be from different models, and may be in one or more elements.

For example, a common type of binding is between a ‘Level’ state and an ‘OnOff’ state, such as the Generic Power Level state (see Section 3.1.5) and the Generic OnOff state (see Section 3.1.1): changing the Level to zero changes the bound OnOff state to Off, and changing the Level to a non-zero value changes the bound OnOff state to On. Such binding is a unidirectional binding. Bindings also may be bidirectional such as changing the OnOff state to Off changes the bound Level state to zero, and changing the OnOff state to On changes the bound Level state to its last known non-zero value. The binding rules are defined explicitly in state definitions.

Multiple states can be grouped together as a shorthand notation referred to as a composite state. This allows a model to refer to this composite state instead of each of the individual grouped states. For example, the Light Lightness state (see Section 6.1.2) includes the following states:

A model can refer to changes in the Light Lightness state instead of individually referencing each change to the Light Lightness Actual, Light Lightness Last, and Light Lightness Default states.

Messages may support transactions. A client can send a series of state-changing messages such as Set, Recall, or Clear within a single transaction. A transaction is considered unique in the context of a Transaction Identifier (if present in a message), a Source Address, a Destination Address, and an instance of a state. Specific behaviors for transactions are included in model behaviors.

If the Transaction Identifier is not present in a message, then the context of the response message can be determined by the value of a field containing a status code and/or the presence of optional and/or conditional fields in the response message.

This light controller and scene control example illustrates the application of the model relationship principles introduced in Section 1.4.4.

The device is a color temperature-selectable luminaire that has a built-in controller that automatically adjusts the dim level based on ambient light conditions. The device also supports scene-setting of the dim level and controller parameters separately from the color temperature (that is, using a scene to change the color temperature of the luminaire does not change the brightness or the controller parameters).

Figure 1.4 shows the Composition Data for a node implementing this functionality.

Figure 1.4. Example Composition Data showing the relationship between the states stored with each scene server and the instantiated functionalities distributed on the elements

The Light Lightness Server model is a base model for both the Light LC Server model (the main model for light controller functionality) and the Light CTL Server model (the main model for tunable white functionality). However, the Light CTL Server model and the Light CTL Temperature Server model (the corresponding model) are stored with different scene servers to meet the device’s functional requirements.

This example illustrates a successful application of the model relationship principles, because:

It would be a mistake to move the first scene server from Element 0 to Element 2, and then instantiate a new element and move the second scene server and the Light CTL Temperature Server model to the new element (Element 3). That would be an unsuccessful application of the model relationship principles, because it is not necessary to place the scene server on its own element to achieve the desired functionality (i.e., the scene server can be instantiated on Element 0).

This dual-channel tunable white luminaire example illustrates the application of the model relationship principles introduced in Section 1.4.4.

The device is a driver that has two output channels for color temperature-controllable luminaires.

Figure 1.5 shows the Composition Data for a node implementing this functionality.

Figure 1.5. Example Composition Data for a driver with two color temperature-selectable output channels

This example illustrates a successful application of the model relationship principles, because:

It would be a mistake to place the first instance of the Light CTL Server model on Element 0, the second instance of the Light CTL Server model on Element 1, and then the two instances of the Light CTL Temperature Server model on Element 3 and Element 4. Although this would allow for unambiguous message dispatch, this would be an unsuccessful application of the model relationship principles. These principles do not permit interleaving a new instance of a Light CTL Server model before instantiating the corresponding models of the initial Light CTL Server model.

To represent a length in decimeters with a resolution of 1 decimeter within a characteristic value, the following values are used:

To represent a duration in 256ths of a second with a precision of 1/256 of a second within a characteristic value, the following values are used:

To represent the horizontal dilution of precision with an accuracy of 1/5 with a precision of 1/5 within a characteristic value, the following values are used:

Because binary states cannot support transitions, when changing to 0x01 (On), the Generic OnOff state shall change immediately when the transition starts, and when changing to 0x00, the state shall change when the transition finishes.

Figure 3.1 illustrates the behavior for a Generic OnOff state bound to a Generic Power Actual state (see Section 3.1.5.1.2) when changing to 0x01 (On). Figure 3.2 illustrates the behavior for a Generic OnOff state bound to a Generic Power Actual state when changing to 0x00 (Off).

Figure 3.1. Binary state transitions from 0x00 to 0x01

Figure 3.2. Binary state transitions from 0x01 to 0x00

The Default Transition Step Resolution field shall use the Transition Step Resolution format (see Section 3.1.10.1) of the Generic Default Transition Time.

The Default Transition Number of Steps field shall use the Transition Number of Steps format (see Section 3.1.10.2) of the Generic Transition Time.

Default Transition Number of Steps shall not be set to a value of 0x3F.

The Generic Power Actual state determines the linear percentage of the maximum power level of an element, representing a range from 0 percent through 100 percent. The value is derived using the following formula:

The state is bound to the Generic Level state (see Section 3.1.2) and the Generic OnOff state (see Section 3.1.1). The values for the Generic Power Actual state are defined in Table 3.4.

An element that has the Generic Power Actual set to 0x0000 may continue to power the wireless communications and the microcontroller necessary to change the Generic Power Actual state back to a non-zero value.

Additional regulatory requirements may determine the maximum energy use when the element has the Generic Power Actual state set to 0x0000.

The Generic Power Last state is a 16-bit value representing a percentage ranging from (1/65535) percent to 100 percent. The value is derived using the following formula:

The purpose of the Generic Power Last state is to store the last known non-zero value of the Generic Power Actual state, which is a result of a completed transactional change of the state. Depending on the value of the Generic OnPowerUp state (see Section 3.1.4), It may also be used as a default value when an element is powered up.

Whenever the Generic Power Actual state is changed to a non-zero value as a result of a non-transactional message or a completed sequence of transactional messages, the value of the Generic Power Last state shall be set to the value of the Generic Power Actual state.

The values for the Generic Power Last state are defined in Table 3.5.

The Generic Power Default state is a 16-bit value ranging from 0 through 65535. Values from 0x0001 through 0xFFFF represent the percentage of power level, derived using the following formula:

Value 0x0000 has a special meaning defined: use the value of the Generic Power Last state as the default value. The purpose of the Generic Power Default state is to determine the power level of an element when the device is powered up and when the Generic OnPowerUp state (see Section 3.1.4) bound to the Generic Power Level state is set to 0x01 (Default).

The values for the Generic Power Default state are defined in Table 3.6.

The Generic Power Range state determines the minimum and maximum power levels of an element relative to the maximum power level an element can output. This is a pair of 16-bit unsigned integers: Generic Power Range Min and Generic Power Range Max.

The Generic Power Range Min state determines the minimum non-zero power level an element can be configured to. The Generic Power Range Max state determines the maximum power level an element can be configured to. The values for the states are defined in Table 3.7.

The Generic Battery Level state is a value ranging from 0 percent through 100 percent. The values for the state are defined in Table 3.8.

The Generic Battery Time to Discharge state is a 24-bit unsigned value ranging from 0 through 0xFFFFFF. The values for the state are defined in Table 3.9.

The Generic Battery Time to Charge state is a 24-bit unsigned value ranging from 0 through 0xFFFFFF. The values for the state are defined in Table 3.10.

As defined in Table 3.11, the Generic Battery Flags state is a concatenation of four 2-bit bit fields: Presence, Indicator, Charging, and Serviceability. The values for the state are defined in Table 3.11.

The Global Latitude field describes the global WGS84 North coordinate of the element. The format of the field is a signed integer of size 32 bits encoded as signed magnitude.

The relationship between Latitude X in the range [-90°, 90°] and the encoded number N is derived using the following formula:

where N is bounded to the range -2³¹+1≤N≤2³¹-1. If N exceeds the bounds, the closest value within the bounds shall be used.

The floor operation shall be performed according to IEEE standards.

The value 0x80000000 in the Global Latitude field indicates the Global Latitude is not configured.

The Global Longitude field describes the global WGS84 East coordinate of the element. The format of the field is a signed integer of size 32 bits encoded as signed magnitude.

Note: The global WGS84 East coordinate and longitude are based on the WGS84 datum [3].

The relationship between Longitude X in the range [-180°, 180°] and the encoded number N is derived using the following formula:

where N is bounded to the range -2³¹+1≤N≤2³¹-1. If N exceeds the bounds, the closest value within the bounds shall be used.

The floor operation shall be performed according to IEEE standards.

The value 0x80000000 in the Global Latitude field indicates the Global Longitude is not configured.

The Global Altitude field determines the altitude of the device above the WGS84 datum. It expresses the altitude beyond the WGS84 ellipsoid of the element that exposed its position. This is a 16-bit signed integer in meters.

The values for the state are defined in Table 3.17.

The Local North field describes the North coordinate of the device using a local coordinate system. It is relative to the north orientation on a predefined map. The format of the field is a signed integer of size 16 bits.

The Local North value is encoded in decimeters and has a range of -32767 decimeters through 32767 decimeters. The value 0x8000 means the Local North information is not configured.

The Local East field describes the East coordinate of the device using a local coordinate system. It is relative to the east orientation of a predefined map. The format of the field is a signed integer of size 16 bits.

The Local East value is encoded decimeters and it ranges from -32767 decimeters through 32767 decimeters. The value 0x8000 means the Local East information is not configured.

The Local Altitude field determines the altitude of the device relative to the Generic Location Global Altitude. This is a 16-bit signed integer in decimeters.

The valid range is from -32768 decimeters through 32765 decimeters.

The values for the state are defined in Table 3.18.

The Floor Number field describes the floor number where the element is installed.

The floor number, N, is encoded as X=N+20, where X is the encoded floor number.

Floor number=-20 (X=0) has a special meaning, indicating the floor -20, and also any floor below that.

Floor number=232 (X=252) has a special meaning, indicating the floor 232, and also any floor above that.

The values for the state are defined in Table 3.19.

The format of the field is an unsigned integer of size 8 bits.

The Uncertainty field is a 16-bit bit field that describes the uncertainty of the location information the element exposes. The field consists of several values. The meaning of each bit is described in Table 3.20.

The Stationary field indicates whether the device broadcasting the location information has a stationary location or is mobile. The values of the Stationary field are defined Table 3.21.

The Update Time field indicates the time (t) elapsed since the last update of the device's position, measured in seconds, using the following formula:

The field value (x) is a 4-bit value ranging from 0 through 15. The represented Update Time value range is from 0.125 seconds through 4096 seconds.

If the Stationary field is set to the Stationary value, the Update Time field value can be ignored.

The Precision field indicates a location precision with the formula:

The field value (y) is a 4-bit value ranging from 0 through 15. The represented Precision value range is from 0.125 meters through 4096 meters.

Generic User Property is a state representing a device property of an element. Depending on how the device property is defined, this may be a read-only state or a read-write state. The values for the state are defined in Table 3.22.

Generic Admin Property is a state representing a device property of an element that can be read or written. The values for the state are defined in Table 3.25.

Generic Manufacturer Property is a state representing a device property of an element that is programmed by a manufacturer and can be read. The values for the state are defined in Table 3.28.

The Client Property ID field is a 2-octet Assigned Number value that references a device property (see Section 2).

The values for the field are defined in Table 3.32.

The Transition Step Resolution field is a 2-bit bit field that determines the resolution of the Generic Transition Time. The field values represent the states defined in Table 3.34.

The Transition Number of Steps field is a 6-bit value that determines the number of transition steps. The field values represent the states defined in Table 3.35.

Generic OnOff Get is an acknowledged message used to get the Generic OnOff state of an element (see Section 3.1.1).

The response to the Generic OnOff Get message is a Generic OnOff Status message.

The structure of the message is defined in Table 3.36.

The Opcode field shall contain the opcode value for the Generic OnOff Get message defined in the Assigned Numbers document [10].

Generic OnOff Set is an acknowledged message used to set the Generic OnOff state of an element (see Section 3.1.1).

The response to the Generic OnOff Set message is a Generic OnOff Status message.

The structure of the message is defined in Table 3.37.

The Opcode field shall contain the opcode value for the Generic OnOff Set message defined in the Assigned Numbers document [10].

The OnOff field identifies the Generic OnOff state of the element (see Section 3.1.1).

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.1.2.2.

If present, the Transition Time field identifies the time that an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic OnOff Set Unacknowledged is an unacknowledged message used to set the Generic OnOff state of an element (see Section 3.1.1).

The structure of the message is defined in Table 3.38.

The Opcode field shall contain the opcode value for the Generic OnOff Set Unacknowledged message defined in the Assigned Numbers document [10].

The OnOff field identifies the Generic OnOff state of the element (see Section 3.1.1).

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.1.2.2.

If present, the Transition Time field identifies the time that an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic OnOff Status is an unacknowledged message used to report the Generic OnOff state of an element (see Section 3.1.1).

The structure of the message is defined in Table 3.39.

The Opcode field shall contain the opcode value for the Generic OnOff Status message defined in the Assigned Numbers document [10].

The Present OnOff field identifies the present Generic OnOff state of the element (see Section 3.1.1).

If present, the Target OnOff field identifies the target Generic OnOff state that the element is to reach (see Section 3.1.1).

If present, the Remaining Time field identifies the time it will take the element to complete the transition to the target Generic OnOff state of the node (see Section 1.4.1.1 and 3.1.1).

Generic Level Get is an acknowledged message used to get the Generic Level state of an element (see Section 3.1.2).

The response to the Generic Level Get message is a Generic Level Status message.

The structure of the message is defined in Table 3.40.

The Opcode field shall contain the opcode value for the Generic Level Get message defined in the Assigned Numbers document [10].

Generic Level Set is an acknowledged message used to set the Generic Level state of an element (see Section 3.1.2) to a new absolute value.

The response to the Generic Level Set message is a Generic Level Status message.

The structure of the message is defined in Table 3.41.

The Opcode field shall contain the opcode value for the Generic Level Set message defined in the Assigned Numbers document [10].

The Level field identifies the Generic Level state of the element (see Section 3.1.2).

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.2.2.2.

If present, the Transition Time field identifies the time that an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Level Set Unacknowledged is an unacknowledged message used to set the Generic Level state of an element (see Section 3.1.2) to a new absolute value.

The structure of the message is defined in Table 3.42.

The Opcode field shall contain the opcode value for the Generic Level Set Unacknowledged message defined in the Assigned Numbers document [10].

The Level field identifies the Generic Level state of the element (see Section 3.1.2).

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.2.2.2.

If present, the Transition Time field identifies the time that an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Delta Set is an acknowledged message used to set the Generic Level state of an element (see Section 3.1.2) by a relative value. The message is transactional – it supports changing the state by a cumulative value with a sequence of messages that are part of a transaction.

The response to the Generic Delta Set message is a Generic Level Status message.

The structure of the message is defined in Table 3.43.

The Opcode field shall contain the opcode value for the Generic Delta Set message defined in the Assigned Numbers document [10].

The Delta Level field identifies the increase (when positive) or decrease (if negative) of the Generic Level state of the element (see Section 3.1.2).

The TID field is a transaction identifier and shall be used to logically group a series of Generic Delta Set and Generic Delta Set Unacknowledged messages. When starting a new transaction, TID should be assigned a least recently used value, as described in Section 3.4.2.2.3.

The Transition Time field identifies the time that an element will take to transition to the target state from the present state. The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Delta Set Unacknowledged is an unacknowledged message used to set the Generic Level state of an element (see Section 3.1.2) by a relative value.

The structure of the message is defined in Table 3.44.

The Opcode field shall contain the opcode value for the Generic Delta Set Unacknowledged message defined in the Assigned Numbers document [10].

The Delta Level field identifies the increase (when positive) or decrease (if negative) of the Generic Level state of the element (see Section 3.1.2).

The TID field is a transaction identifier and shall be used to logically group a series of Generic Delta Set and Generic Delta Set Unacknowledged messages. When starting a new transaction, TID should be assigned a least recently used value, as described in Section 3.4.2.2.3.

If present, the Transition Time field identifies the time an element will take to transition to the target state from the present state. The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Move Set is an acknowledged message used to start a process of changing the Generic Level state of an element (see Section 3.1.2) with a defined transition speed.

The response to the Generic Move Set message is a Generic Level Status message.

The structure of the message is defined in Table 3.45.

The Opcode field shall contain the opcode value for the Generic Move Set message defined in the Assigned Numbers document [10].

The Delta Level field shall be used to calculate the speed of the transition of the Generic Level state.

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.2.2.4.

If present, the Transition Time field shall be used to calculate the speed of the transition of the Generic Level state. The Transition Time field shall use the format defined in Section 3.2.9. If the resulting Transition Time is equal to 0 or is undefined, the Generic Move Set command will not initiate any Generic Level state change.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Move Set Unacknowledged is an unacknowledged message used to start a process of changing the Generic Level state of an element (see Section 3.1.2) with a defined transition speed.

The structure of the message is defined in Table 3.46.

The Opcode field shall contain the opcode value for the Generic Move Set Unacknowledged message defined in the Assigned Numbers document [10].

The Delta Level field shall be used to calculate the speed of the transition of the Generic Level state.

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.2.2.4.

If present, the Transition Time field shall be used to calculate the speed of the transition of the Generic Level state. The Transition Time field shall use the format defined in Section 3.2.9. If the resulting Transition Time is equal to 0 or undefined, the Generic Move Set command will not initiate any Generic Level state change.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Level Status is an unacknowledged message used to report the Generic Level state of an element (see Section 3.1.2).

The structure of the message is defined in Table 3.47.

The Opcode field shall contain the opcode value for the Generic Level Status message defined in the Assigned Numbers document [10].

The Present Level field identifies the present Generic Level state of the element (see Section 3.1.2).

If present, the Target Level field identifies the target Generic Level state that the element is to reach (see Section 3.1.2).

If present, the Remaining Time field identifies the time that it will take the element to complete the transition to the target Generic Level state of the element (see Section 3.1.2).

Generic Default Transition Time Get is an acknowledged message used to get the Generic Default Transition Time state of an element (see Section 3.1.3).

The response to the Generic Default Transition Time Get message is a Generic Default Transition Time Status message.

The structure of the message is defined in Table 3.48.

The Opcode field shall contain the opcode value for the Generic Default Transition Time Get message defined in the Assigned Numbers document [10].

Generic Default Transition Time Set is an acknowledged message used to set the Generic Default Transition Time state of an element (see Section 3.1.3).

The response to the Generic Default Transition Time Set message is a Generic Default Transition Time Status message.

The structure of the message is defined in Table 3.49.

The Opcode field shall contain the opcode value for the Generic Default Transition Time Set message defined in the Assigned Numbers document [10].

The Transition Time field identifies the Generic Default Transition Time state of the element (see Section 3.1.3).

Generic Default Transition Time Set Unacknowledged is an unacknowledged message used to set the Generic Default Transition Time state of an element (see Section 3.1.3).

The structure of the message is defined in Table 3.50.

The Opcode field shall contain the opcode value for the Generic Default Transition Time Set Unacknowledged message defined in the Assigned Numbers document [10].

The Transition Time field identifies the Generic Default Transition Time state of the element (see Section 3.1.3).

Generic Default Transition Time Status is an unacknowledged message used to report the Generic Default Transition Time state of an element (see Section 3.1.3).

The structure of the message is defined in Table 3.51.

The Opcode field shall contain the opcode value for the Generic Default Transition Time Status message defined in the Assigned Numbers document [10].

The Transition Time field identifies the Generic Default Transition Time state of the element (see Section 3.1.3).

Generic OnPowerUp Get is an acknowledged message used to get the Generic OnPowerUp state of an element (see Section 3.1.4).

The response to the Generic OnPowerUp Get message is a Generic OnPowerUp Status message.

The structure of the message is defined in Table 3.52.

The Opcode field shall contain the opcode value for the Generic OnPowerUp Get message defined in the Assigned Numbers document [10].

Generic OnPowerUp Set is an acknowledged message used to set the Generic OnPowerUp state of an element (see Section 3.1.4).

The response to the Generic OnPowerUp Set message is a Generic OnPowerUp Status message.

The structure of the message is defined in Table 3.53.

The Opcode field shall contain the opcode value for the Generic OnPowerUp Set message defined in the Assigned Numbers document [10].

The OnPowerUp field identifies the Generic OnPowerUp state of the element (see Section 3.1.4).

Generic OnPowerUp Set Unacknowledged is an unacknowledged message used to set the Generic OnPowerUp state of an element (see Section 3.1.4).

The structure of the message is defined in Table 3.54.

The Opcode field shall contain the opcode value for the Generic OnPowerUp Set Unacknowledged message defined in the Assigned Numbers document [10].

The OnPowerUp field identifies the Generic OnPowerUp state of the element (see Section 3.1.4).

Generic OnPowerUp Status is an unacknowledged message used to report the Generic OnPowerUp state of an element (see Section 3.1.4).

The structure of the message is defined in Table 3.55.

The Opcode field shall contain the opcode value for the Generic OnPowerUp Status message defined in the Assigned Numbers document [10].

The OnPowerUp field identifies the Generic OnPowerUp state of the element (see Section 3.1.4).

Generic Power Level Get message is an acknowledged message used to get the Generic Power Actual state of an element (see Section 3.1.5.1).

The response to the Generic Power Level Get message is a Generic Power Level Status message.

The structure of the message is defined in Table 3.56.

The Opcode field shall contain the opcode value for the Generic Power Level Get message defined in the Assigned Numbers document [10].

Generic Power Level Set is an acknowledged message used to set the Generic Power Actual state of an element (see Section 3.1.5.1).

The response to the Generic Power Level Set message is a Generic Power Level Status message.

The structure of the message is defined in Table 3.57.

The Opcode field shall contain the opcode value for the Generic Power Level Set message defined in the Assigned Numbers document [10].

The Power field identifies the target Generic Power Actual state of the element, as defined in Section 3.1.5.1.

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.5.2.2.

If present, the Transition Time field identifies the time an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Power Level Set Unacknowledged is an unacknowledged message used to set the Generic Power Actual state of an element (see Section 3.1.5.1).

The structure of the message is defined in Table 3.58.

The Opcode field shall contain the opcode value for the Generic Power Level Set Unacknowledged message defined in the Assigned Numbers document [10].

The Power field identifies the target Generic Power Actual state of the element, as defined in Section 3.1.5.1.

The TID field is a transaction identifier indicating whether the message is a new message or a retransmission of a previously sent message, as described in Section 3.4.5.2.2.

If present, the Transition Time field identifies the time an element will take to transition to the target state from the present state (see Section 1.4.1.1). The Transition Time field shall use the format defined in Section 3.2.9.

If present, the Delay field identifies the message execution delay, representing a time interval between receiving the message by a model and executing the associated model behaviors.

Generic Power Level Status is an unacknowledged message used to report the Generic Power Actual state of an element (see Section 3.1.5.1).

The structure of the message is defined in Table 3.59.

The Opcode field shall contain the opcode value for the Generic Power Level Status message defined in the Assigned Numbers document [10].

The Present Power field identifies the Generic Power Actual state of the element, as defined in Section 3.1.5.1.

If present, the Target Power field identifies the target Generic Power Actual state that the element is to reach (see Section 3.1.5.1).

If present, the Remaining Time field identifies the time it will take the element to complete the transition to the target Generic Power Actual state of the element (see Section 1.4.1.1 and 3.1.5.1).

Generic Power Last Get is an acknowledged message used to get the Generic Power Last state of an element (see Section 3.1.5.1.1).

The response to a Generic Power Last Get message is a Generic Power Last Status message.

The structure of the message is defined in Table 3.60.

The Opcode field shall contain the opcode value for the Generic Power Last Get message defined in the Assigned Numbers document [10].

Generic Power Last Status is an unacknowledged message used to report the Generic Power Last state of an element (see Section 3.1.5.1.1).

The structure of the message is defined in Table 3.61.

The Opcode field shall contain the opcode value for the Generic Power Last Status message defined in the Assigned Numbers document [10].

The Power field identifies the Generic Power Last state of the element, as defined in Section 3.1.5.1.1.

Generic Power Default Get is an acknowledged message used to get the Generic Power Default state of an element (see Section 3.1.5.3).

The response to a Generic Power Default Get message is a Generic Power Default Status message.

The structure of the message is defined in Table 3.62.

The Opcode field shall contain the opcode value for the Generic Power Default Get message defined in the Assigned Numbers document [10].

Generic Power Default Set is an acknowledged message used to set the Generic Power Default state of an element (see Section 3.1.5.3).

The response to the Generic Power Default Set message is a Generic Power Default Status message.

The structure of the message is defined in Table 3.63.

The Opcode field shall contain the opcode value for the Generic Power Default Set message defined in the Assigned Numbers document [10].

The Power field identifies the Generic Power Default state of the element, as defined in Section 3.1.5.3.

Generic Power Default Set Unacknowledged is an unacknowledged message used to set the Generic Power Default state of an element (see Section 3.1.5.3).

The structure of the message is defined in Table 3.64.

The Opcode field shall contain the opcode value for the Generic Power Default Set Unacknowledged message defined in the Assigned Numbers document [10].

The Power field identifies the Generic Power Default state of the element, as defined in Section 3.1.5.3.

Generic Power Default Status is an unacknowledged message used to report the Generic Power Default state of an element (see Section 3.1.5.3).

The structure of the message is defined in Table 3.65.

The Opcode field shall contain the opcode value for the Generic Power Default Status message defined in the Assigned Numbers document [10].

The Power field identifies the Generic Power Default state of the element, as defined in Section 3.1.5.3.

Generic Power Range Get is an acknowledged message used to get the Generic Power Range state of an element (see Section 3.1.5.4).

The response to the Generic Power Range Get message is a Generic Power Range Status message.

The structure of the message is defined in Table 3.66.

The Opcode field shall contain the opcode value for the Generic Power Range Get message defined in the Assigned Numbers document [10].

Generic Power Range Set is an acknowledged message used to set the Generic Power Range state of an element (see Section 3.1.5.4).

The response to the Generic Power Range Set message is a Generic Power Range Status message.

The structure of the message is defined in Table 3.67.

The Opcode field shall contain the opcode value for the Generic Power Range Set message defined in the Assigned Numbers document [10].

The Range Min field identifies the Generic Power Range Min field of the Generic Power Range state of the element (see Section 3.1.5.4).

The Range Max field identifies the Generic Power Max field of the Generic Power Range state of the element (see Section 3.1.5.4).

The value of the Range Max field shall be greater or equal to the value of the Range Min field.

Generic Power Range Set Unacknowledged is an unacknowledged message used to set the Generic Power Range state of an element (see Section 3.1.5.4).

The structure of the message is defined in Table 3.68.

The Opcode field shall contain the opcode value for the Generic Power Range Set Unacknowledged message defined in the Assigned Numbers document [10].

The Range Min field identifies the Generic Power Range Min field of the Generic Power Range state of the element (see Section 3.1.5.4).

The Range Max field identifies the Generic Power Max field of the Generic Power Range state of the element (see Section 3.1.5.4).

The value of the Range Max field shall be greater or equal to the value of the Range Min field.

Generic Power Range Status is an unacknowledged message used to report the Generic Power Range state of an element (see Section 3.1.5.4).

The structure of the message is defined in Table 3.69.

The Opcode field shall contain the opcode value for the Generic Power Range Status message defined in the Assigned Numbers document [10].

The Status Code field identifies the Status Code for the last operation on the Generic Power Range state. The allowed values for status codes and their meanings are documented in Section 7.2.

The Range Min field identifies the Generic Power Range Min field of the Generic Power Range state of the element (see Section 3.1.5.4).

The Range Max field identifies the Generic Power Range Max field of the Generic Power Range state of the element (see Section 3.1.5.4).

Generic Battery Get message is an acknowledged message used to get the Generic Battery state of an element (see Section 3.1.6).

The response to the Generic Battery Get message is a Generic Battery Status message.

The structure of the message is defined in Table 3.70.

The Opcode field shall contain the opcode value for the Generic Battery Get message defined in the Assigned Numbers document [10].

Generic Battery Status is an unacknowledged message used to report the Generic Battery state of an element (see Section 3.1.6).

The structure of the message is defined in Table 3.71.

The Opcode field shall contain the opcode value for the Generic Battery Status message defined in the Assigned Numbers document [10].

The Battery Level field identifies the Generic Battery Level state of the element, as defined in Section 3.1.6.1.

The Time to Discharge field identifies the Generic Battery Time to Discharge state of the element, as defined in Section 3.1.6.2.

The Time to Charge field identifies the Generic Battery Time to Charge state of the element, as defined in Section 3.1.6.3.

The Flags field identifies the Generic Battery Flags state of the element, as defined in Section 3.1.6.4.

Generic Location Global Get message is an acknowledged message used to get the selected fields of the Generic Location state of an element (see Section 3.1.7).

The response to the Generic Location Global Get message is a Generic Location Global Status message.

The structure of the message is defined in Table 3.72.

The Opcode field shall contain the opcode value for the Generic Location Global Get message defined in the Assigned Numbers document [10].

Generic Location Global Set is an acknowledged message used to set the selected fields of the Generic Location state of an element (see Section 3.1.7).

The response to the Generic Location Global Set message is a Generic Location Global Status message.

The structure of the message is defined in Table 3.73.

The Opcode field shall contain the opcode value for the Generic Location Global Set message defined in the Assigned Numbers document [10].

The Global Latitude field identifies the Generic Location Global Latitude state of the element, as defined in Section 3.1.7.1.

The Global Longitude field identifies the Generic Location Global Longitude state of the element, as defined in Section 3.1.7.2.

The Global Altitude field identifies the Generic Location Global Altitude state of the element, as defined in Section 3.1.7.6.

Generic Location Global Set Unacknowledged is an unacknowledged message used to set the selected fields of the Generic Location state of an element (see Section 3.1.7).

The structure of the message is defined in Table 3.74.

The Opcode field shall contain the opcode value for the Generic Location Global Set Unacknowledged message defined in the Assigned Numbers document [10].

The Global Latitude field identifies the Generic Location Global Latitude state of the element, as defined in Section 3.1.7.1.

The Global Longitude field identifies the Generic Location Global Longitude state of the element, as defined in Section 3.1.7.2.

The Global Altitude field identifies the Generic Location Global Altitude state of the element, as defined in Section 3.1.7.6.

Generic Location Global Status is an unacknowledged message used to report the selected fields of the Generic Location state of an element (see Section 3.1.7).

The structure of the message is defined in Table 3.75.

The Opcode field shall contain the opcode value for the Generic Location Global Status message defined in the Assigned Numbers document [10].

The Global Latitude field identifies the Generic Location Global Latitude state of the element, as defined in Section 3.1.7.1.

The Global Longitude field identifies the Generic Location Global Longitude state of the element, as defined in Section 3.1.7.2.

The Global Altitude field identifies the Generic Location Global Altitude state of the element, as defined in Section 3.1.7.6.

Generic Location Local Get message is an acknowledged message used to get the selected fields of the Generic Location state of an element (see Section 3.1.7).

The response to the Generic Location Local Get message is a Generic Location Local Status message.

The structure of the message is defined in Table 3.76.

The Opcode field shall contain the opcode value for the Generic Location Local Get message defined in the Assigned Numbers document [10].

Generic Location Local Set is an acknowledged message used to set the selected fields of the Generic Location state of an element (see Section 3.1.7).

The response to the Generic Location Local Set message is a Generic Location Local Status message.

The structure of the message is defined in Table 3.77.

The Opcode field shall contain the opcode value for the Generic Location Local Set message defined in the Assigned Numbers document [10].

The Local North field identifies the Generic Location Local North state of the element, as defined in Section 3.1.7.4.

The Local East field identifies the Generic Location Local East state of the element, as defined in Section 3.1.7.5.

The Local Altitude field identifies the Generic Location Local Altitude state of the element, as defined in Section 3.1.7.6.

The Floor Number field identifies the Generic Location Floor Number state of the element, as defined in Section 3.1.7.7.

The Uncertainty field identifies the Generic Location Uncertainty state of the element, as defined in Section 3.1.7.8.

Generic Location Local Set Unacknowledged is an unacknowledged message used to set the selected fields of the Generic Location state of an element (see Section 3.1.7).

The structure of the message is defined in Table 3.78.

The Opcode field shall contain the opcode value for the Generic Location Local Set Unacknowledged message defined in the Assigned Numbers document [10].

The Local North field identifies the Generic Location Local North state of the element, as defined in Section 3.1.7.4.

The Local East field identifies the Generic Location Local East state of the element, as defined in Section 3.1.7.5.

The Local Altitude field identifies the Generic Location Local Altitude state of the element, as defined in Section 3.1.7.6.

The Floor Number field identifies the Generic Location Floor Number state of the element, as defined in Section 3.1.7.7.

The Uncertainty field identifies the Generic Location Uncertainty state of the element, as defined in Section 3.1.7.8.

Generic Location Local Status is an unacknowledged message used to report the selected fields of the Generic Location state of an element (see Section 3.1.7).

The structure of the message is defined in Table 3.79.

The Opcode field shall contain the opcode value for the Generic Location Local Status message defined in the Assigned Numbers document [10].

The Local North field identifies the Generic Location Local North state of the element, as defined in Section 3.1.7.4.

The Local East field identifies the Generic Location Local East state of the element, as defined in Section 3.1.7.5.

The Local Altitude field identifies the Generic Location Local Altitude state of the element, as defined in Section 3.1.7.6.

The Floor Number field identifies the Generic Location Floor Number state of the element, as defined in Section 3.1.7.7.

The Uncertainty field identifies the Generic Location Uncertainty state of the element, as defined in Section 3.1.7.8.

Generic User Properties Get is an acknowledged message used to get the list of Generic User Property states of an element (see Section 3.1.8).

The response to the Generic User Properties Get message is a Generic User Properties Status message.

The structure of the message is defined in Table 3.80.

The Opcode field shall contain the opcode value for the Generic User Properties Get message defined in the Assigned Numbers document [10].

Generic User Properties Status is an unacknowledged message used to report a list of the Generic User Properties states of an element (see Section 3.1.8).

The message is sent as a response to the Generic User Properties Get message or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.81.

The Opcode field shall contain the opcode value for the Generic User Properties Status message defined in the Assigned Numbers document [10].

The User Property IDs field contains a sequence of all Generic User Property ID states of an element (see Section 3.1.8).

Generic User Property Get is an acknowledged message used to get the Generic User Property state of an element (see Section 3.1.8).

The response to the Generic User Property Get message is a Generic User Property Status message.

The structure of the message is defined in Table 3.82.

The Opcode field shall contain the opcode value for the Generic User Property Get message defined in the Assigned Numbers document [10].

The User Property ID field identifies a Generic User Property ID state of an element (see Section 3.1.8).

Generic User Property Set is an acknowledged message used to set the Generic User Property state of an element (see Section 3.1.8).

The response to the Generic User Property Set message is a Generic User Property Status message.

The structure of the message is defined in Table 3.83.

The Opcode field shall contain the opcode value for the Generic User Property Set message defined in the Assigned Numbers document [10].

The User Property ID field identifies a User Property ID state of an element (see Section 3.1.8.1.1).

The User Property Value field identifies a User Property Value state of an element (see Section 3.1.8.1.3).

Generic User Property Set Unacknowledged is an unacknowledged message used to set the Generic User Property state of an element (see Section 3.1.8).

The structure of the message is defined in Table 3.84.

The Opcode field shall contain the opcode value for the Generic User Property Set Unacknowledged message defined in the Assigned Numbers document [10].

The User Property ID field identifies a User Property ID state of an element (see Section 3.1.8.1.1).

The User Property Value field identifies a User Property Value state of an element (see Section 3.1.8.1.3).

Generic User Property Status is an unacknowledged message used to report the Generic User Property state of an element (see Section 3.1.8).

The message is sent as a response to the Generic User Property Get message and the Generic User Property Set message, or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.85.

The Opcode field shall contain the opcode value for the Generic User Property Status message defined in the Assigned Numbers document [10].

The User Property ID field identifies a User Property ID state of an element (see Section 3.1.8.1.1).

The User Access field identifies a User Access state of an element (see Section 3.1.8.1.2).

The User Property Value field identifies a User Property Value state of an element (see Section 3.1.8.1.3).

Generic Admin Properties Get is an acknowledged message used to get the list of Generic Admin Property states of an element (see Section 3.1.8.2).

The response to the Generic Admin Properties Get message is a Generic Admin Properties Status message.

The structure of the message is defined in Table 3.86.

The Opcode field shall contain the opcode value for the Generic Admin Properties Get message defined in the Assigned Numbers document [10].

Generic Admin Properties Status is an unacknowledged message used to report a list of the Generic Admin Properties states of an element (see Section 3.1.8.2).

The message is sent as a response to the Generic Admin Properties Get message or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.87.

The Opcode field shall contain the opcode value for the Generic Admin Properties Status message defined in the Assigned Numbers document [10].

The Admin Property IDs field contains a sequence of all Generic Admin Property ID states of an element (see Section 3.1.8.2).

Generic Admin Property Get is an acknowledged message used to get the Generic Admin Property state of an element (see Section 3.1.8.2).

The response to the Generic Admin Property Get message is a Generic Admin Property Status message.

The structure of the message is defined in Table 3.88.

The Opcode field shall contain the opcode value for the Generic Admin Property Get message defined in the Assigned Numbers document [10].

The Admin Property ID field identifies an Admin Property ID state of an element (see Section 3.1.8.2.1).

Generic Admin Property Set is an acknowledged message used to set the Generic Admin Property state of an element (see Section 3.1.8.2).

The response to the Generic Admin Property Set message is a Generic Admin Property Status message.

The structure of the message is defined in Table 3.89.

The Opcode field shall contain the opcode value for the Generic Admin Property Set message defined in the Assigned Numbers document [10].

The Admin Property ID field identifies an Admin Property ID state of an element (see Section 3.1.8.2.1).

The Admin User Access field identifies an Admin User Access state of an element (see Section 3.1.8.2.2).

The Admin Property Value field identifies an Admin Property Value state of an element (see Section 3.1.8.2.3).

Generic Admin Property Set Unacknowledged is an unacknowledged message used to set the Generic Admin Property state of an element (see Section 3.1.8.2).

The structure of the message is defined in Table 3.90.

The Opcode field shall contain the opcode value for the Generic Admin Property Set Unacknowledged message defined in the Assigned Numbers document [10].

The Admin Property ID field identifies an Admin Property ID state of an element (see Section 3.1.8.2.1).

The Admin User Access field identifies an Admin User Access state of an element (see Section 3.1.8.2.2).

The Admin Property Value field identifies an Admin Property Value state of an element (see Section 3.1.8.2.3).

Generic Admin Property Status is an unacknowledged message used to report the Generic Admin Property state of an element (see Section 3.1.8.2).

The message is sent as a response to the Generic Admin Property Get message and the Generic Admin Property Set message, or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.91.

The Opcode field shall contain the opcode value for the Generic Admin Property Status message defined in the Assigned Numbers document [10].

The Admin Property ID field identifies an Admin Property ID state of an element (see Section 3.1.8.2.1).

The Admin User Access field identifies an Admin User Access state of an element (see Section 3.1.8.2.2).

The Admin Property Value field identifies an Admin Property Value state of an element (see Section 3.1.8.2.3).

Generic Manufacturer Properties Get is an acknowledged message used to get the list of Generic Manufacturer Property states of an element (see Section 3.1.8).

The response to the Generic Manufacturer Properties Get message is a Generic Manufacturer Properties Status message.

The structure of the message is defined in Table 3.92.

The Opcode field shall contain the opcode value for the Generic Manufacturer Properties Get message defined in the Assigned Numbers document [10].

Generic Manufacturer Properties Status is an unacknowledged message used to report a list of the Generic Manufacturer Properties states of an element (see Section 3.1.8).

The message is sent as a response to the Generic Manufacturer Properties Get message or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.93.

The Opcode field shall contain the opcode value for the Generic Manufacturer Properties Status message defined in the Assigned Numbers document [10].

The Manufacturer Property IDs field contains a sequence of all Generic Manufacturer Property ID states of an element (see Section 3.1.8).

Generic Manufacturer Property Get is an acknowledged message used to get the Generic Manufacturer Property state of an element (see Section 3.1.8).

The response to the Generic Manufacturer Property Get message is a Generic Manufacturer Property Status message.

The structure of the message is defined in Table 3.94.

The Opcode field shall contain the opcode value for the Generic Manufacturer Property Get message defined in the Assigned Numbers document [10].

The Manufacturer Property ID field identifies a Manufacturer Property ID state of an element (see Section 3.1.8.3.1).

Generic Manufacturer Property Set is an acknowledged message used to set the Generic Manufacturer Property User Access state of an element (see Section 3.1.8.3.1).

The response to the Generic Manufacturer Property Set message is a Generic Manufacturer Property Status message.

The structure of the message is defined in Table 3.95.

The Opcode field shall contain the opcode value for the Generic Manufacturer Property Set message defined in the Assigned Numbers document [10].

The Manufacturer Property ID field identifies a Manufacturer Property ID state of an element (see Section 3.1.8.3.1).

The Manufacturer User Access field identifies a Manufacturer User Access state of an element (see Section 3.1.8.3.2).

The Generic Manufacturer Property Set Unacknowledged is an unacknowledged message used to set the Generic Manufacturer Property User Access state of an element (see Section 3.1.8).

The structure of the message is defined in Table 3.96.

The Opcode field shall contain the opcode value for the Generic Manufacturer Property Set Unacknowledged message defined in the Assigned Numbers document [10].

The Manufacturer Property ID field identifies a Manufacturer Property ID state of an element (see Section 3.1.8.3.1).

The Manufacturer User Access field identifies a Manufacturer User Access state of an element (see Section 3.1.8.3.2).

The Generic Manufacturer Property Status is an unacknowledged message used to report the Generic Manufacturer Property state of an element (see Section 3.1.8).

The message is sent as a response to the Generic Manufacturer Property Get and Generic Manufacturer Property Set messages or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.97.

The Opcode field shall contain the opcode value for the Generic Manufacturer Property Status message defined in the Assigned Numbers document [10].

The Manufacturer Property ID field identifies a Manufacturer Property ID state of an element (see Section 3.1.8.3.1).

The Manufacturer User Access field identifies a Manufacturer User Access state of an element (see Section 3.1.8.3.2).

The Manufacturer Property Value field identifies a Manufacturer Property Value state of an element (see Section 3.1.8.3.3).

Generic Client Properties Get is an acknowledged message used to get the list of Generic Client Property states of an element (see Section 3.1.9).

The response to the Generic Client Properties Get message is a Generic Client Properties Status message.

The structure of the message is defined in Table 3.98.

The Opcode field shall contain the opcode value for the Generic Client Properties Get message defined in the Assigned Numbers document [10].

The Client Property ID field contains the smallest Property ID the client is requesting (see Section 3.1.9).

The Generic Client Properties Status is an unacknowledged message used to report a list of the Generic Client Properties states of an element (see Section 3.1.9).

The message is sent as a response to the Generic Client Properties Get message or may be sent as an unsolicited message.

The structure of the message is defined in Table 3.99.

The Opcode field shall contain the opcode value for the Generic Client Properties Status message defined in the Assigned Numbers document [10].

The Client Property IDs field contains a sequence of all Generic Client Property ID states of an element (see Section 3.1.9).