Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calculation of the OperationalState of the ExpectedEquipment not clearly defined #38

Open
openBackhaul opened this issue Mar 7, 2024 · 2 comments

Comments

@openBackhaul
Copy link
Owner

Problem:

  • Section ActualEquipment in Chapter 9 of TransmitterEquipment Specification is requesting for the ActualEquipment object (incl. associated objects) to contain as much as possible information about the currently plugged hardware component, but at least a list of specified attributes. So the listed attributes are to be represented as a minimum.
  • Section ExpectedEquipment in Chapter 9 of TransmitterEquipment Specification is requesting for an exact list of attributes to be copied from the ActualEquipment if not configured differently from the user before the hardware got plugged.
  • Section ExpectedEquipment in Chapter 10 of TransmitterEquipment Specification is defining the OperationalState of the ExpectedEquipment to be disabled unless there is an ActualEquipment that has the same values in all attributes that are not empty in the ExpectedEquipment.
  • There is no definition, of the group of attributes that have to be taken into account for this comparison.
  • Some of the attributes cannot represent an empty string (due to pattern or integer).

Potential Solutions:

  • Section ExpectedEquipment in Chapter 10 of TransmitterEquipment Specification should be complemented by a definition of the attributes that shall exclusively been taken into account (e.g. ManufacturerProperties::manufacturerIdentifier, ManufacturerProperties::manufacturerName, EquipmentType::partTypeIdentifier and EquipmentType::version).
  • Section ActualEquipment in Chapter 9 should define a defaultValue, which shall be represented in case the value cannot be taken from the hardware, for every listed attribute.
@openBackhaul openBackhaul self-assigned this Mar 7, 2024
@openBackhaul
Copy link
Owner Author

openBackhaul commented Apr 2, 2024

Decision during the LF ONMI x-haul call on 24th of April 2024:
Updated by adding "ActualEquipment and ExpectedEquipment " in the second part on 9th of April 2024:

  • The existing §35 in the section ExpectedEquipment of Chapter 10 of the TransmitterEquipment Specification shall be replaced by the following formulation:
    "
    The value of the ExpectedEquipment::operationalState attribute must be 'disabled', unless an ActualEquipment object is instantiated (regardless of its operational state) that has the exact same values in the following attributes, in which case the ExpectedEquipment::operationalState attribute must be 'enabled':

    • ManufacturedThing :: manufacturerName
    • ManufacturedThing :: partTypeIdentifier
    • ManufacturedThing :: version

    "

  • Some of the relevant values may not be supported as a concept by the vendor or not be available due to unavailability on the device. Default values shall be defined for ActualEquipment and ExpectedEquipment to harmonize the handling of such situations across implementations. Even after a possible restructuring of Chapter 9 of the TransmitterEquipment Specification, the attributes listed above shall be described as follows:

    • ManufacturerProperties :: manufacturerName : String = ""
    • EquipmentType :: partTypeIdentifier : String = ""
    • EquipmentType :: version : String = ""

@openBackhaul
Copy link
Owner Author

Has been updated in Equipment_3.0.0-tsi.240515.1100+spec.1.doc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant