1 Scope
2
References
3
Definitions, abbreviations, and conventions
3.1 Definitions
3.2 Abbreviations
3.3 Conventions
4
General overview
4.1 Entity-relationship models
4.1.1
Entity-relationship diagram for the service node (Figure 2)
4.1.2 Entity-relationship diagram for the
access network (Figure 3)
4.2 Inheritance hierarchy
5
Formal definitions
5.1 Object classes
5.1.1 Profiling notes for imported classes
5.1.2 Definition of classes
5.2 Name bindings
5.2.1 vclLup-vpcLupVb52
5.2.2 vpcLupVb52-uniAccessVb5
5.3 Definition of
packages
5.3.1 lupVcLevelProfilePkg (Logical user port
VC Level profile package)
5.4 Definition of attributes
5.4.1 bbccRequired (B-BCC required)
5.4.2 connectionIdentifierFlag (Connection
identifier flag)
5.4.3 vcCtpPtr (VC CTP pointer)
5.4.4 vciAtLup (VCI at the logical user port)
5.4.5 vclLupId (VC link at the logical user
port identifier)
5.5 Definition of actions
5.5.1 resetBbcc (reset BBCC protocol)
5.6 Definition of notifications
5.6.1 presyncBbccResult (result of
presynchronization of BBCC protocol)
5.6.2 resetBbccResult (result of reset of BBCC
protocol)
6
Type definitions
7
Protocol stacks
Annex A – Management requirements
A.1 Q3(AN) and Q3(SN) requirements
A.1.1 General management requirements
A.1.2 Real-time
management coordination requirements
Annex B – Relationship between VB5.2 interfaces and the management model
B.1 Introduction
B.2 LSP, LUP and VPCI labels
B.3 Shutting down
B.4 Blocking and unblocking
B.5 VPCI consistency checking
B.6 Interface start-up
B.6.1 B-BCC start-up from SN side
B.6.2 B-BCC start-up from AN side
B.7 LSP identity checking
B.8 RTMC reset
B.9 B-BCC reset
B.10 Congestion
Annex C – State transitions
C.1 State transition tables for AN
C.2 State transition tables for SN
Appendix I – Bibliography
Appendix II – Instantiation example
II.1 Conventions
II.2 Example of VPs/VCs allocation at the AN and the SN
II.3 Instantiation of managed objects in the AN
II.4 Instantiation of managed objects at the SN