An initial rough proposal for a model style that allows a single model to cover all cases of the knowledge layer (full or none; per instance). The solution will impacts the Spec hierarchy but not the resource hierarchy.
There is request to discuss how to use the lifecycleState model for network inventory.
For example, how to add the time that something is planned to be added or removed.
There is the Tempoal expression model.
It covers repetition. Could degenerate to one-time
Keep track of the time of event
Use notification and streaming
How to use the UUID, e.g.,
Equipment Holder and the contained Equipment, which could be one (the current one in the holder) or multiple (0..* for the planned/potential ones)
Mixing of lifecycle and ownership
Restructure of the document TR-512.3
Revised TR-512.3 to move out the lifecycle state material
Have a separate document, TR-512.17 (new) for lifecycle state. Yet to be agreed.
Multi-pointed Media Channels: Multi-source multi-destination
TR-512.A.4 Figure 4-28
Representation of topology and frequency slot occupancy
Agree to use the Bidirectional overlaid trees approach to tackle the issue
Nigel Davis Start to draw simple single tree, find minimal forms, then draw the overlaid tree, then use in both TAPI and Core
Pattern of simple tree (non-intersecting)
Primitives: Merge (M) / Split (S)
n nodes: 2**n options
e.g., 2 nodes: 2**2=4 options: MM, MS, SM, SS
Pattern of overlaid trees
Might waste wavelenth
2021.02.04 brief discussion
Simple tree structure to evaluate network blocking
Build tree structure for each of the points (Transponders or ROADMs), then use overlay tree to evaluate blocking.
For each of the originating points (e.g., A, B, C, D, etc.), build a transmit tree through the intermedate coupler/splitter nodes to the end points (i.e.,A-188.8.131.52.5-J; A-184.108.40.206.5.-L; etc.), then look at the overlapping segments (e.g., 2.3) of the overlaid trees (e.g., A-220.127.116.11.5-J and C-2.3-G).
Identify the disjoint trees (e.g, B and C)
Nigel DavisMalcolm Betts Write text to explain the restriction and rules for bi/uni-directional for evaluating network blocking. Aim for adding to TR-512.A.4 (section 4.4.9)
2021.02.17 brief discussion
Review of writeup on multi-point MC restriction/rules
Clarification on the control model needed by ITU-T Q14/15