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

equipment-type-name in response of /v1/provide-list-of-actual-device-equipment is outside TR-532v2.0 #50

Open
openBackhaul opened this issue Apr 5, 2024 · 1 comment
Assignees

Comments

@openBackhaul
Copy link
Owner

openBackhaul commented Apr 5, 2024

Problem:
The equipment-type-name attribute from the responseBody of /v1/provide-list-of-actual-device-equipment is filled from data provided in /core-model-1-4:control-construct/equipment/actual-equipment/manufactured-thing/equipment-type/type-name.
The typeName attribute from the ONF CoreIM is outside the TransmitterEquipment Spec. and should not be used.

Potential Solution:

  • A new /v2/provide-list-of-actual-device-equipment service shall be defined.
  • It shall be a copy of the existing /v1/provide-list-of-actual-device-equipment service, except the following changes:
    • Its responseBody shall no longer contain a equipment-type-name attribute.
    • Instead there shall be a new equipment-part-type-identifier attribute. This new attribute shall be filled from the equipment-part-type-identifier attribute in the ResponseBody of the MWDI://v2/provide-list-of-actual-device-equipment service.
  • The existing /v1/provide-list-of-actual-device-equipment service shall be marked "Deprecated" as its life cycle state.

First, it shall be checked, whether part-type-identifier fulfills the clients' needs. Alternatively, coverage of TransmitterEquipment Spec. may be expanded on ActualEquipment :: typeName.

@openBackhaul
Copy link
Owner Author

See directly related MWDI issue#920.

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

No branches or pull requests

1 participant