Table of Contents
1Scope
2References
3Definitions
4Abbreviations
5Generalaspects
5.1Overview
5.2Unifiedsignallingrequirementsmethodology
6Businessmodel
6.1Overviewofthebusinessmodeldomainstructure
6.2Descriptionofthedomainsinthebusinessmodel
7Informationobjectmodel
7.1General
7.2Localviewoftheinformationobjectmodel
7.3Descriptionofsessioncontrolclasses
7.4Descriptionofresourcecontrolclasses
7.5Descriptionofcallcontrolclasses
7.6Descriptionofbearercontrolclasses
7.7Descriptionoftransportcontrolclasses
7.8Descriptionofcommonclassattributes
7.9Descriptionofsessioncontrolclassattributes
7.10Descriptionofresourcecontrolclassattributes
7.11Descriptionofcallcontrolclassattributes
7.12Descriptionofbearercontrolclassattributes
7.13Call,bearerandtransportcontrolsegment
relationships
8Computationalobjectmodel
8.1Descriptionoftheunifiedfunctionalmodel
8.2Definitionoffunctionalentities
9Engineeringviews
9.1Physicalengineeringscenarios
9.1.1Physicalengineeringscenarioshowing
thecallcontrolandbearercontrol
service-independentportions
9.1.2Physicalengineeringscenarioshowing
aseparatetransportnetwork
implementation
9.2Businessviewscenarios
9.2.1Businessviewscenarioshowingnetwork
connectivityproviderINfunctionality
10Descriptionofmanagement-relatedfunctionalities
10.1TMNmodelincorporatingfunctionalentities
10.2TMNmodelincorporatingphysicalelements
AnnexA-Networkconnectiontopologytypes
AnnexB-Ownershipcapabilityrequirements
AnnexC-UMLnotation
AppendixI-Businessmodellogicalreferencepoints
I.1-Informationflowreferencemodel
I.2-Networkconnectivityprovidergroup
I.3-Retailergroup
I.4-Brokergroup
I.5-Consumer-serviceprovidergroup Abstract
Defines the general aspects for developing unified signalling requirements. The general aspects are specified as business models, information object models, functional entity models and engineering models.
