ES 201 386 : 1.1.1

Intellectual Property Rights
Foreword
1 Scope
2 References
3 Abbreviations
4 Rationale
5 Overview
6 Technical approach
  6.1 SSF functional decomposition
  6.2 SSF management requirements
  6.3 SSF management information model
7 Introduction to the SSF model
8 Management requirements for the SSF sub entities
  8.1 Introduction
  8.2 Operational Requirements and Activities
9 Informal description of Managed Object Classes
  9.1 SSF Object Model (informal)
  9.2 Relation to other object models
Annex A (informative): SSF scenarios
      A.1 Basic IN Call scenarios
      A.2 Specialized Resource scenarios
      A.3 Charging scenario
      A.4 Call Gapping and Service Filtering scenarios
      A.5 Activity Test scenario
      A.6 "Call Information" scenario
      A.7 "InitiateCallAttempt" scenarios
      A.8 "ResetTimer" scenarios
Annex B (informative): The Basic Call State Model control
        (BCSM control)
      B.1 BCSM control
      B.2 TDP Processing
Annex C (informative): Modelling the relationship between
        Trigger Bases and IN Triggers
History

Specify management requirements and a management information model (object classes in GDMO & ASN.1 and inheritance and containment hierarchies, but excluding MOCS) for the IN CS-2 SSF functionality. Only the management of IN specific functionality will be subject to this ETS: It will include the management of TC and INAP, it will not address non-IN specific call control functionality. The management information model for INAP that will be developed is expected to be largely re-usable for the INAP stacks in other IN functional entities (e.g. SCF, SRF). Provides a set of management interface specifications that can be used by operators and vendors in the procurement/offerings of new SSF functionality and as a first step towards a more complete specification of standard IN management solutions.