To be changed in the TR document, but not in the UML.
Adding an additional chapter 6.6 TxPower Interpretation to TR-532 with the following content: "
AirInterface::AirInterfaceConfiguration::txPower shall be interpreted as a maximum value. Independently from any Adaptive Modulation or Automated Transmit Power Control configuration, the actually operated transmit power shall never exceed this value.
While Adaptive Modulation is increasing the operated modulation scheme, the transmit power, which is available as a maximum at the device, is declining. In case the transmit power, which is available as a maximum at the device, is falling below the configured txPower, the device shall operate at the maximum possible transmit power.
The validation process of the Netconf server inside the device shall accept an Adaptive Modulation configuration, if the txPower value is lower or equal to the maximum possible transmit power in at least one of the modulation schemes, which are included in the choosen modulation range."
Content of the Mantis Bugtracker:
|Description||Example: The device already has the following configuration |
adaptiveModulationIsOn==1, modulationMin==4 and modulationMax==256 and txPower shall be configured in the next step.
Would it be the txPower in the lowest, highest or current modulation?
TR-532 to be amended to rule out any ambiguity in regards to the meaning of txPower and the behaviour of the actual transmit power in case of modulation changes due to varying attenuation in the transmission path.
A potential solution might be defining txPower to have a legal value, if it can be reached in any of the configured modulations, but will never be exceeded in any of the allowed modulations.