Table of Contents
1Scope
2References
3Abbreviationsandacronyms
4Introduction
4.1SCF-SDFrelationship
4.2IntroductiontothereuseofX.500forSDF
interfaces
4.3Versionsandtherulesforextensibility
5ServiceControlFunction(SCF)Model
6ServiceDataFunction(SDF)Model
6.1General
6.2SDFcomponents
6.3DatatypeshandledbySDF
7FSMforSCF
7.1Overview
7.2SCME-FSM
7.3SDF-relatedstates(SCSM-SDF)
8FSMforSDF
8.1Overview
8.2SDME-FSM
8.3SDFstatetransitionmodelforSCF-relatedstates
9Detailedoperationsprocedure
9.1IN-Executeprocedure
9.2IN-AddEntryprocedure
9.3IN-DirectoryBindprocedure
9.4IN-ModifyEntryprocedure
9.5IN-RemoveEntryprocedure
9.6IN-Searchprocedure
9.7IN-Unbindprocedure
9.8TFCBindprocedure
9.9TrafficFlowControlprocedure
9.10Operationtimervalues
10Parameters
10.1BaseObject
10.2Changes
10.3CheckOverspecified
10.4CommonResults
10.5ControlType
10.6Credentials
10.7Duration
10.8Entry
10.9Filter
10.10IN-CommonArguments
10.11Information
10.12Input-assertions
10.13MatchedValuesOnly
10.14Method-id
10.15Null
10.16Object
10.17Output-assertions
10.18SearchAliases
10.19SearchInfo
10.20Security
10.21Selection
10.22Specific-input
10.23Specific-output
10.24Subset
10.25TargetSystem
10.26TfcCriteria
10.27UncorrelatedSearchInfo
10.28Versions
10.29WasChained
11Errors
11.1Operation-relatederrorprocedures
12ServiceassumedfromTCAP
12.1Normalprocedures
12.2Abnormalprocedures
12.3Dialoguehandling
12.4Componenthandling
AnnexA-ASN.1definitions(electronicattachment) Abstract
Describes the protocol realizing the Q.1241 Distributed Functional Plane in a service and vendor implementation independent manner, as constrained by the capabilities of the embedded base of network technology. It provides the flexibility to allocate distributed functionality into multiple physical network configurations and to evolve IN from IN CS-4 to some future CS-N.
