1
Scope
1.1 Purpose
1.2 Application
1.3 Recommendation roadmap
2
Normative references
3
Definitions
3.1 Definitions from ITU-T X.701
3.2 Definitions from ITU-T X.703
3.3 Definitions from
ITU-T Q.816
4
Abbreviations
5
Conventions
5.1 Recommendation conventions
5.2 Compiling the IDL
6 Coarse-grained interface design
considerations
6.1 Reduced number of IORs
6.2 Ability to derive IORs
6.3 Application of framework services
6.4 Distinguishing between the two
types of objects
6.5 Hierarchical naming
6.6 Migration of modelled entities
across approaches
6.7 Migration of modelled entities
across technologies
6.8 Equivalent distinguished names
7 Framework and requirements
overview
7.1 Framework overview
7.2 Coarse-grained extensions overview
7.2.1 The facade design pattern
7.2.2 Managed object name extension
7.2.3 Support services for facade-accessible managed objects
7.2.4 Facade modelling
8 Framework common object services
usage requirements for supporting coarse‑grained interfaces
8.1 The naming service
8.1.1 Naming service use on coarse-grained interfaces
8.1.2 Facade interface names
8.1.3 Managed object name extension
8.1.4 Object name comparisons
8.1.5 Storing managed object names in the naming service
8.1.6 Naming service requirements for coarse-grained interfaces
8.2 Notification service
8.3 Telecom log service
8.4 Messaging service
8.5 Security service
8.6 Transaction service
9 Framework support services
requirements for supporting coarse-grained interfaces
9.1 The factory finder service
9.2 The channel finder service
9.3 The terminator service
9.4 The multiple-object operation
service
9.5 Heartbeat
service
9.6 Containment service
9.6.1 Containment
service rationale
9.6.2 Containment service description
10 Compliance and conformance
10.1 System conformance
10.1.1 Conformance points
10.1.2 Basic conformance profile
10.2 Conformance statement guidelines
Annex A – Coarse-grained framework
support services IDL