1 Scope
2
References
3
Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
4
Abbreviations and acronyms
5
Conventions
5.1 UML modelling conventions
5.1.1 Model artifact naming
conventions
5.1.2 Reviewing UML diagrams
5.2 Model artefact lifecycle stereotype
conventions
5.3 Forwarding entity terminology conventions
5.4 Conditional package conventions
5.5 Pictorial diagram conventions
6
Model overview
6.1 Development and use of the ITU-T G.7711
generic information model
6.1.1 Common information model
6.1.2 Purpose specific
information model view
6.1.3 Data schema
6.1.4 Interface encoding
6.2 Core network model – Forwarding and
termination model (Annex B)
6.3 Core foundation model (Annex C)
6.3.1 Naming and identifiers
6.3.2 States
6.4 Core network model – Topology model (Annex
D)
6.5 Core network model – Resilience model (Annex E)
6.6 Core physical model (Annex F)
6.7 Core specification model (Annex G)
6.8 Control model (Annex H)
6.9 OAM model (Annex I)
6.10 Interaction pattern model (Annex J)
6.11 Processing construct model (Annex K)
6.12 Software model (Annex L)
6.13 Party model (Annex M)
6.14 Location model (Annex N)
6.15 Compute (Annex O)
6.16 Core foundation model – States
6.17 Temporal expression model (Annex R)
7 Other aspects
7.1 Key reference materials
7.2 Data dictionary
7.3 Terminology mapping
7.4 Core model enhancement
8 UML model Papyrus files
Annex A Modelling principles and guidelines, and
tooling
A.1 UML modelling guidelines
A.2 Papyrus and Github guidelines
A.3 Tool versions
Annex B Forwarding and termination model
B.1 Forwarding and termination model detail
B.1.1 Termination model
B.1.2 Forwarding
B.1.3 Clock, timing and synchronization
B.1.4 NetworkElement, NetworkControlDomain and SdnController
B.2 Explanatory figures
B.2.1 Forwarding
B.2.2 Termination
B.2.3 Network considerations
B.2.4 Directionality
B.2.5 Relationships to the physical connector (Pin and AccessPort)
B.3 Work in progress
Annex C Foundation – Identifiers and naming
C.1 Naming and identifiers
C.1.1 Key considerations
C.1.2 Classes and attributes
C.1.3 DataTypes
C.1.4 Use of names, identifiers and addresses
Annex D Topology model
D.1 Topology model
D.1.1 Topology model overview
D.1.2 Topology model detail
D.1.3 Topology model classes,
related classes and structures
D.1.4 Topological properties of
the ForwardingEntity
D.1.5 Model showing topology,
forwarding and termination
D.1.6 Further defining the Link
D.2 Explanatory figures
D.2.1 Basic topology
D.2.2 Topology in a control
context
D.2.3 Topology and views
D.2.4 View boundaries and
intermediates
D.2.5 The FdPort
D.2.6 More on views and
names/identifiers – The FC representing a Call
D.2.7 Off-network reference and
the clients view
D.2.8 Serial-compound Links
D.2.9 Transitional Links
D.2.10 Multi-port Link
D.2.11 State dependency
D.2.12 Inverse multiplexing
D.2.13 Topology in a deep
inspection context
D.3 Work in progress
D.3.1 Detailed properties of
topology
D.3.2 Cost algorithms
D.3.3 FC/Link convergence
D.3.4 NearEnd/FarEnd,
Input/output and ingress/egress
D.3.5 Complex transitional
Links
D.3.6 Non-orthogonal FDs
Annex E Resilience model
E.1 Resilience model detail
E.1.1 Resilience pattern
E.1.2 Resilience model
E.1.3 Key to diagrams
E.1.4 Further explanation of
the model
E.2 Protection schemes considered
E.3 Protection of other functions of physical
things
E.4 Work in progress
E.4.1 Signalling information flow
E.4.2 Additional considerations for FcRoute
E.4.3 Representation alternatives – Partition or route
E.4.4 Relationship to the ProtectionGroup approach
Annex F Physical model
F.1 Physical model detail
F.1.1 Equipment pattern
F.1.2 Equipment Detail
F.1.3 Connector to LTP model
F.1.4 Equipment to function sketch
F.1.5 FRU and non-FRU
F.1.6 Connector rules
F.1.7 Expected and actual
F.1.8 Specification
F.1.9 Physical connector and conceptual port
F.2 Work in progress
F.2.1 Addressing
F.2.2 Physical to functional model
F.2.3 Actual vs expected
Annex G Specification model
G.1 Introduction to the specification model
G.1.1 Introduction to the CIM specification approach
G.1.2 Rationale for, and features of, the ONF specification approach
G.1.3 The mechanism compared to other mechanisms
G.1.4 Introduction to this document
G.2 Purpose of the specification model
G.2.1 Background
G.2.2 Cases considered
G.2.3 Resultant representations and principles
G.2.4 Adoption and migration considerations
G.2.5 Enabling innovation while removing unnecessary variation
G.3 Dedicated specification structures
G.3.1 Forwarding specification
G.3.2 LogicalTerminationPoint and LayerProtocol specification
G.3.3 ForwardingDomain and Link specification
G.3.4 PC, ControlComponent and
CASC spec considerations
G.3.5 Acquiring the
specifications run time
G.3.6 Work on the general
pattern
Annex H Control model
H.1 Model of control component and views
H.1.1 Background
H.1.2 The control model in the
context of the core classes
H.1.3 The control model core
H.1.4 Further description
H.1.5 Relationship to previous
model
H.1.6 Relationship to the other
key classes
H.1.7 Model in context –
directly controlled things
H.1.8 General discussion
H.2 Understanding the control component and view
model
H.2.1 Rationale
H.2.2 Implications
H.2.3 The patterns behind the
model
H.2.4 Identifiers, naming and
addressing
H.2.5 Resilience in the control
system
H.2.6 Controller view
considerations
H.2.7 Dismantling the NE – Some
rationale
H.2.8 The control model applied
to the "Controller"
H.2.9 The
configurationAndSwitchControl (CASC)
H.3 The ControlTask
H.3.1 Overview of Tasks
H.3.2 The ControlTask model
H.4 Operations
H.4.1 The basic model
H.4.2 Provider and User role
detail
H.4.3 Long-lived operations and
universal structures
H.4.4 The full model
H.5 Providing information
H.5.1 At the core of the
management-control system
H.5.2 Autonomous provision of
information
H.5.3 Overview of streaming
characteristics
H.5.4 A compacted log driving a stream
H.5.5 Use of the signal and Get
H.5.6 The streaming model
H.5.7 Operation of the streams
H.5.8 GET/POST/PUT/PATCH
H.5.9 Snapshot stream
H.5.10 Streaming requests for change
H.6 Future considerations
H.6.1 Task flow
H.6.2 Clarification of use of CD, VMF and EC
H.6.3 Control hierarchy, peering and fractals
H.6.4 Client intent generation
H.6.5 Intent receiver
H.6.6 Constraint form
H.6.7 Forms of log
Annex I OAM model
I.1 Operations, administration and maintenance (OAM)
I.1.1 Background
I.2 The model
I.2.1 Traditional models
I.2.2 Core OAM modelling
I.2.3 Measurement of multiple flows
I.2.4 OAM and measurement lifecycle
I.3 Further considerations
I.4 Future considerations
I.4.1 Maintenance signal flow
I.4.2 Measurement of multiple flows
I.4.3 OAM and measurement lifecycle
I.4.4 Storage considerations
I.4.5 Various process output forms
I.4.6 Measurement strategies
I.4.7 OAM examples
Annex J Interaction patterns
J.1 Introduction to the interaction patterns
J.1.1 Background to the work
J.1.2 Goals
J.1.3 Aspects of the work
J.1.4 Some terminology
J.1.5 Introduction to this
annex
J.2 Purpose and essentials of the operation
patterns
J.2.1 Background
J.2.2 The model
J.2.3 The structure
J.2.4 "Foldaway
complexity" explained
J.2.5 Discussion
J.3 Future work
Annex K Processing construct
K.1 Purpose and essentials of processing
construct
K.1.1 Background
K.1.2 Model
K.1.3 PC/CD model
K.1.4 Related classes
K.2 Explanatory figures
K.2.1 Multi- functional device
example
K.2.2 Distributed device
K.2.3 PTP clock example
K.2.4 ERPS ITU-T G.8032 example
K.3 Further considerations
Annex L Software
L.1 Purpose and essentials of the Software model
L.1.1 Background
L.1.2 Model
L.2 Software examples
Annex M
Party
M.1 Party model
detail
M.1.1 Party model
M.1.2 Further detail
M.2 Party model examples
M.2.1 Employee
M.2.2 Customer contact
M.2.3 Device owner
Annex N
Location
N.1 Location model detail
N.1.1 Location model
N.1.2 Further detail
N.2 Location model examples
N.2.1 Site Contact
N.2.2 Global and local location options
N.2.3 Device Location
N.2.4 Wifi heat map
N.2.5 Complex address
Annex O Compute model
O.1 Introduction to compute
O.1.1 Background
O.1.2 Storage extent
O.1.3 Partitioning and aggregation
O.1.4 Storage pooling
O.2 Compute model and context
O.2.1 ComputeConstruct positioning
O.2.2 The ComputePool model
O.2.3 Compute model data types
O.2.4 Relationship to file system and software
O.3 A simple compute example
O.4 Model considerations
O.4.1 Pooling
O.4.2 Partitioning and aggregation
O.4.3 Items for further investigation
Annex P
Annex Q
Foundation – State
Q.1 CoreFoundationModel
Q.1.1 States
Annex R Temporal expression
R.1 Temporal expression model detail
R.1.1 Temporal Expression class model
R.1.2 Temporal expression data types
R.1.3 Enumeration Types
R.1.4 Further detail
R.2 Examples of combination
R.2.1 Union within a property
R.2.2 Intersection between
properties in augments
R.2.3 Union of TeElements into
a TemporalExpression
R.2.4 Applying an
IncorporatedTe
R.3 Using the temporal model
R.3.1 Application to elements
of the domain model
R.3.2 Application to deal with
plan deviations and plan alternatives
R.4 Specific examples
R.4.1 Garden waste collection
R.5 Further work
R.5.1 Exclusion conflict action
Appendix I Mapping of ITU-T G.7711 to ONF technical
recommendations
I.1 Model structural patterns and architecture
(Appendix V)
I.2 Rationale behind the CIM (Appendix VI)
I.3 Analogue and media (L0) examples (Appendix
VII)
I.4 Circuit switched (L1 & L2) examples
(Appendix VIII)
I.5 Packet switched (L2 & L3) examples
(Appendix IX)
I.6 Control and signalling examples (Appendix X)
I.7 Timing and synchronization examples
(Appendix XI)
I.8 Processing construct examples (Appendix XII)
I.9 Specification examples (Appendix XIII)
I.10 Resilience examples (Appendix XIV)
I.11 Application (L4 and above) examples
(Appendix XV)
I.12 Software examples (Appendix XVI)
I.13 Controller lifecycle and security (Appendix
XVII)
Appendix II Data dictionary
Appendix III Terminology mapping
III.1 Terminology mapping table
III.2 Detailed view of transport application
programming interface to core model mapping
Appendix IV Future enhancements
IV.1 Future work areas
IV.2 Some detailed notes on future work
IV.2.1 Model structure rules
IV.2.2 Lifecycle dependency
IV.2.3 Multiplicity restrictions
Appendix V Model structure, patterns and architecture
V.1 A progression patterns – intertwining and unfolding
V.1.1 Hypergraph pattern
V.1.2 Developing the Component – System pattern from Hypergraph
V.1.3 The component – System pattern
V.1.4 Encapsulation pattern
V.1.5 Transfer – Transform pattern
V.1.6 Realized potential
V.1.7 Protocol "layering"
V.1.8 Forwarding phases
V.1.9 Information architecture
V.1.10 Views of the architecture
V.1.11 Deriving relevant application models
V.1.12 The component and the classes in the CoreNetworkModel
V.1.13 The extended Component-Port pattern
V.1.14 The Component – System pattern illustrated
Appendix VI Model rationale
VI.1 Business need
VI.2 Benefit of the CIM
VI.3 Model evolution
VI.3.1 Agile approach for model evolution
VI.3.2 Industry cooperation in model evolution
Appendix VII Analogue and media (Layer 0) examples
Appendix VIII Circuit switched (L1 and L2) examples
VIII.1 General circuit
examples
VIII.1.1 Basic OTN device example
VIII.2 Circuit layer examples
VIII.2.1 Single layer examples
VIII.2.2 Multi-layer examples
Appendix IX Packet switched (L2 and L3) examples
IX.1 General examples
IX.1.1 Basic Ethernet device
IX.1.2 Sophisticated Ethernet
device
IX.2 Ethernet examples
IX.2.1 Ethernet single-layer
example
IX.2.2 Ethernet multi-layer
example
IX.2.3 Ethernet & MPLS-TP
multi-layer example
Appendix X Control and interaction examples
X.1 Control
X.1.1 The Basic "Network
Element"
X.1.2 ONF SDN controller
X.1.3 Generalized control
function
X.1.4 Ethernet ring protection
system (ERPS, ITU-T G.8032)
Appendix XI Timing and synchronization examples
Appendix XII Processing construct examples
XII.1 General examples
XII.1.1 Types of processing
construct
XII.1.2 PTP clock example
XII.1.3 ERPS ITU-T G.8032 example
Appendix XIII Specification examples
XIII.1 General examples
XIII.1.1 The FD and FC Spec
XIII.1.2 Applying rules
XIII.1.3 LTP spec examples
Appendix XIV Resilience examples
XIV.1 Linear protection schemes
XIV.1.1 1?1 cases
XIV.1.2 1?1 open protection cases
XIV.1.3 1:N Cases
XIV.2 Mesh network cases
XIV.2.1 N:1 with multicast nodal
cases
XIV.3 Ethernet ring protection [ITU-T G.8032]
XIV.4 Other protected ring schemes
XIV.4.1 Network wrapping
XIV.4.2 Network steering
XIV.4.3 The model in detail for
both steering and wrapping
Appendix XV Application (L4 and above) examples
Appendix XVI Software examples
XVI.1 General examples
XVI.1.1 Routing 'Process' on a
router
XVI.1.2 Simple Host with Host OS
VMM
XVI.1.3 Simple host with
container engine and containers
XVI.1.4 CPU, memory and storage
example
XVI.1.5 FPGA example
XVI.1.6 Soft switch example
XVI.1.7 Constraint domain example
Appendix XVII Controller lifecycle and security
XVII.1 Overview and context
XVII.1.1 Business context
XVII.1.2 Management control
architecture
XVII.1.3 Controller internal
architecture
XVII.2 Formation of a controller
XVII.2.1 Forming the service
definition and the catalogue
XVII.2.2 Specific service
assumptions
XVII.2.3 Progressing through the
formation
XVII.3 Building a controller
XVII.3.1 Platform creation
(Compute administration)
XVII.3.2 Assign network resources
(network administration)
XVII.3.3 Configure server contexts
(controller administrator)
XVII.4 Control service and various deployments
XVII.4.1 Example deployment
scenarios
XVII.4.2 Multiple views
XVII.4.3 Building a client context
XVII.5 Security considerations
XVII.5.1 Deployment assumptions
XVII.5.2 Access control for users
on the EC port
XVII.6 Timeline examples
Bibliography