1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes

2022-05-04 5G-xHaul Meeting notes

00:01

supported-affected-protocol-list capability is missing

• approved as proposed

Adding new layer-protocol discussion

• Sketch

Current Assumption - not agreed - just for discussion purposes:

1. a split between SyncE LTPs and PTP LTPs is useful
2. a split between SyncE Clocks and PTP Clocks is useful
3. There is a difference between Boundary Clocks and Transparent clocks and MasterClocks and Client Clocks?
4. There is no need to address grand-master clocks in the 5G-xHaul model, because the addresses devices are not (and never will be Grand-Master Clocks)
5. An FC for PTP is needed to express the status of the selected source
6. An FC for SyncE is needed to express the status of the selected source and the configuration of possible sources

Idea: use augment for name/extension attributes - instead of documentation out side of UML and YANG

Addresses the limitations (rw/ro, units, ...)

Requirements from TEF:

https://github.com/openBackhaul/firmware/blob/tsp/BackUpAndRestore/BackUpAndRestoreRequirements.md

Comments could be addressed by adding issues in GitHub.

• Backup and Restore Operations

  • backup configuration to FTP server
  • restore configuration from FTP server AND activate
  • abord operation individual for backup and restore
  • rollback to previous configuration stored in the device
  • applyRestoreOperation
• Note: Mediator Instance Manager backup-and-restore functions are covered by app and cloud functions
  
  

• status

  • backupOperationStatus
  • restoreOperationStatus