Table of Contents
1Scope
2References
3Abbreviationsandacronyms
4Introduction
4.1SDF-SDFrelationship
4.2IntroductiontotheINX.500DSPandDISPsubset
4.3Versionsandtherulesforextensibility
5FSMforSDF
5.1Overview
5.2SDME-FSM
5.3SDFstatetransitionmodelforSDF-relatedstates
6Detailedoperationprocedure
6.1ChainedExecuteprocedure
6.2IN-ChainedAddEntryprocedure
6.3IN-ChainedModifyEntryprocedure
6.4IN-ChainedRemoveEntryprocedure
6.5IN-ChainedSearchprocedure
6.6IN-CoordinateShadowUpdateprocedure
6.7IN-DSABindprocedure
6.8IN-DSAShadowBindprocedure
6.9IN-RequestShadowUpdateprocedure
6.10IN-Unbindprocedure
6.11IN-UpdateShadowprocedure
6.12TFCBindprocedure
6.13TrafficFlowControlprocedure
6.14Operationtimervalues
7Parameters
7.1AgreementID
7.2Argument
7.3ControlType
7.4Duration
7.5IN-ChainedArgument
7.6IN-ChainedResult
7.7Information
7.8LastUpdate
7.9RequestedStrategy
7.10Result
7.11Security
7.12SecurityParameters
7.13TfcCriteria
7.14UpdatedInfo
7.15UpdateStrategy
7.16UpdateTime
7.17UpdateWindow
7.18WasChained
8Errors
8.1Operationrelatederrorprocedures
9ServiceassumedfromTCAP
9.1Normalprocedures
9.2Abnormalprocedures
9.3Dialoguehandling
9.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 IN CS-N.
