Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2021-10-06 5G-xHaul Meeting notes
Skip to end of metadata
Go to start of metadata

 | 2am PDT | 5am EDT | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |


Web Conference:

https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=m849236edb092dffd10071725f5b8839f 

Invited:

(please feel free to correct and update your names (wink) Thank you very much!!!) 

Info to: 

Goals

  • going forward


Mailings

Discussion items

TimeItemWhoNotes
00:00Chair topic 
no update 

00:03

Admin

Next meetings

2021-10-13: Martin Skorupski

2021-10-20: Martin Skorupski

2021-10-27: Martin Skorupski

2021-11-03: Martin Skorupski

00:05AirInterface - rxThresholdMichael Binder 

AirInterface #53

  • devices with desired receive-level for remote site
  • upper = lower
    • limitation: handling of alignment between both
    • rule: configuration should express the intent by the operator
    • consequence: setting of default of the 'other' value


new proposal from 2021-10-06

Please see comments of AirInterface #53

Note:

Does aptc increase or decrease the power?

ATPC was designed to avoid interference. 

00:32issues labeled "yang to be provided"@Prathiba

A list of related "issues" send by email to Martin → handled "offline" to be presented next week

9 issues could be provided by Prathiba on demand 

"NMDA alternative" is the main upcoming change on UML and later on YANG

Procedure:

  • UML-to-be-changed to be provided (except NMDA)
  • then updated yangs to be provided to the group
00:Synchronization

@Alexander Wenk

@Prathiba

Some answer about modeling and mappings can be found here

Working Assumption to be proven about figure 7-21 – UML model diagram – CdSpecificView

  • PtpDomainConstraint_Pac is a model OUTSIDE of the device (control-construct)
    • There is the first expectation that all attributes are already in the LTP(Sync) and CLOCK object class.
  • NeSync_Pac
    • under the assumption that "Ne..." mean "NetworkElement..." the "NeSync_Pac" could be called "ControlConstructSync_Pac" and attached to the ControlConstruct itself


CoreModel

  • ControlConstruct
    • LTP
      • - e-m-b-e-d-d-e-d-C-l-o-c-k- (ref to a clock)


Proposal

  • ControlConstruct
    • LTP
      • LP
        • synchPac
          • ref-to-clock


AI: How to deal with refactoring of the CoreModel to get all references from SyncModel to ControlContruct. 



END OF THE MEETING

00:

Relation between planning and actual data from the network


@Andreas Lattoch

Quick synch from last week

  • connector types to be standardized
  • work in progress - to be continued
  • Current work bases on the "EquipmentModel"
00:00Mediator Instance Manager

Thorsten Heinze

Pre- Discussion happened yesterday 

  • info send by Thorsten on Monday 2021-05-177
  • in addition Thorsten will send the "background discussion slide"....

Mediator Instance Manager 

  • What is the protocol? NETCONF or REST or RESTCONF or ...
    • Working Assumption:  not decided
    • SIAE would like to decide based on efforts after analysis. 
    • UML include the "service" - but not the operational and maintenance layer
    • YAML (OpenAPI3) → UML (papyrus) → YANG → 

2021-05-25

  • Any questions?
    • no questions

2021-06-16

  • please see "App layer on top of the SDN controller" above.

Action items