| 7am PDT | 10am EDT | 14:00 UTC | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST |
Please use this link (thanks to Telefonica)
(please feel free to correct, update your names Thank you very much!!!)
the attached document consolidates the content of Pawel+Martin+Alex’s AirEquipment specification into the already existing WireEquipment_1.0.0-tsp.190920.1230+spec.1.docx
Tasks: Please review and add inline comment to the document
unitl and latest until .
Roberto: different configurations (e.g. 2+0, 1+1) are covered by CoreModel (serverLTPs, clientLTPs, fcSwitch)
Firmware Release and Licenses might influence Interface Capabilities #15
Currently, the characteristics expressed by the attributes at the ManufacturedThing class of the Core IM are the base for deciding, which Capability attributes to attach to a new instance of an LTP.
This expresses the dependency also to the hardware release.
Dependencies between interface Capabilities and firmware release or licenses are not documented.
Covered by previous topic - see above
How to express, 2 physical interfaces ending optional in a one EthernetContainer?
Please see Contributions by SIAE (Martin Skorupski to be added)
radio-signal-id: proposal of simplification - link to issue - air39
The comment of the expectedRadioSignalID attribute should get additional phase "Only relevant, if expectedEqualsTransmittedRadioSignalID==false.".
AI: Martin think where in TR docs such "rule" are documented.
Other similar cases:
config attribute, where the device supports only one value.
e.g. Maintenance Timer:
should be handled in future.
AI: should be agreed in ONF 5G-xHaul.