1
Scope
2 References
3 Definitions
4 Abbreviations
5 General aspects
5.1 Overview
5.2 Unified signalling requirements
methodology
6 Business model
6.1 Overview of the business model
domain structure
6.2 Description of the domains in the
business model
6.2.1 Consumer
6.2.2 Broker
6.2.3 Retailer
6.2.4 Service provider
6.2.5 Network connectivity provider
7 Information object model
7.1 General
7.1.1 Object modelling and signalling requirements
7.1.2 Views of sessions, resources, calls and connections
7.2 Local view of the information
object model
7.3 Description of session control
classes
7.3.1 Session
7.3.2 Direct/remote session association
7.4 Description of resource control
classes
7.4.1 Resource group (RG)
7.4.2 Direct/remote resource group association
7.4.3 Resource
7.4.4 Direct/remote resource association
7.4.5 Resource component
7.5 Description of call control
classes
7.5.1 Service component
7.5.2 Call
7.5.3 Direct/remote call association
7.6 Description of bearer control
classes
7.6.1 Network connection
7.6.2 Network connection association
7.6.3 Bearer branch
7.6.4 Service module
7.7 Description of transport control
classes
7.7.1 Transport connection
7.7.2 Transport link
7.8 Description of common class
attributes
7.8.1 Party end point network address
7.8.2 Communication configuration
7.9 Description of session control
class attributes
7.9.1 Session party end point ID
7.9.2 Party end point business type
7.9.3 Session ID
7.9.4 Session owner
7.9.5 Session association ID
7.9.6 Session type
7.10 Description of resource control
class attributes
7.10.1 Resource group party end point ID
7.10.2 Resource group ID
7.10.3 Resource group owner
7.10.4 Resource group association ID
7.10.5 Resource party end point ID
7.10.6 Resource ID
7.10.7 Resource owner
7.10.8 Resource association ID
7.10.9 Resource component ID
7.10.10 Resource component characteristics
7.11 Description of call control class
attributes
7.11.1 Call party end point ID
7.11.2 Call ID
7.11.3 Call owner
7.11.4 Party owner
7.11.5 Call association ID
7.11.6 Service component ID
7.11.7 Service component characteristics
7.11.8 Service component traffic descriptor requirements
7.11.9 Service component QoS descriptor requirements
7.12 Description of bearer control
class attributes
7.12.1 Transit network ID
7.12.2 Network connection party end point ID
7.12.3 Network-oriented low layer information
7.12.4 Network connection topology type
7.12.5 Network connection ID
7.12.6 Network connection owner
7.12.7 Bearer branch owner
7.12.8 Network connection association ID
7.12.9 Service module ID
7.12.10 Multiplexing method
7.13 Call, bearer and transport control
segment relationships
7.13.1 Call control segment
7.13.2 Bearer control segment
7.13.3 Transport control segment
7.13.4 Relationships between call, bearer and transport control segments
8 Computational object model
8.1 Description of the unified
functional model
8.2 Definition of functional entities
8.2.1 Network switching element (X)
8.2.2 Fabric management (FM)
8.2.3 Transport control (TC)
8.2.4 Bearer control (BC)
8.2.5 Call control (CC)
8.2.6 Resource control (RC)
8.2.7 Session control (SeC-N and SeC-T)
8.2.8 Network's service control function (nSCF)
8.2.9 Network's service data function (nSDF)
8.2.10 User's service control function (uSCF)
8.2.11 User's service data function (uSDF)
8.2.12 Location registration control function (LRCFh)
8.2.13 Location registration data function (LRDFh)
8.2.14 Authentication control function (ACFh)
8.2.15 Authentication data function (ADFh)
8.2.16 Service control (SC-T and SC-N)
8.2.17 User application control (UAC)
9 Engineering views
9.1 Physical engineering scenarios
9.1.1 Physical engineering scenario showing the call control and bearer
control service‑independent portions
9.1.2 Physical engineering scenario showing a
separate transport network implementation
9.2 Business view scenarios
9.2.1 Business view scenario showing network connectivity provider IN
functionality
10 Description of management-related functionalities
10.1 TMN model incorporating functional
entities
10.2 TMN model incorporating physical
elements
Annex A – Network connection topology types
Annex B – Ownership capability requirements
Annex C – UML notation
Appendix I – Business model logical reference points
I.1 Information flow reference model
I.2 Network connectivity provider
group
I.3 Retailer group
I.4 Broker group
I.5 Consumer-service provider group