Table of Contents
1Scope
2References
3Definitions
4Abbreviationsandacronyms
5Rsinterface
5.1Overview
5.2Rsreferencemodel
5.3Functionalelementsandcapabilities
6SCEsession-specificprocedures
6.1ProceduresatthePD-PE
6.2ProceduresattheSCE
6.3IMS-relatedSCEprocedures
7Protocolspecification
8UseoftheDiameterbaseprotocol
8.1SecuringDiametermessages
8.2Accountingfunctionality
8.3Useofsessions
8.4Transportprotocol
8.5Routingconsiderations
8.6Advertisingapplicationsupport
9Messagespecification
9.1Commands
9.2Experimental-Result-CodeAVPvalues
9.3AVPs
9.4Useofnamespaces
10Securityconsiderations
AnnexA-SupportforSIPforking
A.1SupportforSIPforking
AnnexB-QoSparametermappingforSDP
B.1SDPtoserviceinformationmappinginSCE
AnnexC-Derivationofflownumbers
C.1Purposeandscope
C.2Conceptualframework
C.3Examples
AppendixI-MappingofRsinformationcomponentstoQ.3301.1
AppendixII-ITU-TregistryforITU-T-definedDiameter
attribute-valuepairs(AVPs)
Bibliography Abstract
Describes the rcp1 protocol, a protocol between service control entities (SCE) in the Services Stratum and the Policy Decision Physical Entity (PD-PE) in the Resource and Admission Control Function block.
