Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.329  Word version:  17.0.0

Top   Top   None   None   Next
1…   6…

 

1  Scopep. 6

The present document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on the Diameter base protocol as specified in RFC 6733.
The present document is applicable to:
  • The Sh interface between an AS and the HSS.
  • The Sh interface between an SCS and the HSS.
Whenever it is possible this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter base protocol as specified in RFC 6733. Where this is not possible, extensions to the Diameter base protocol as specified in RFC 6733 are defined within this document.
Up

2  Referencesp. 6

The following documents contain provisions, which through reference in this text constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; signalling flows and message contents".
[2]
TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
[3]
RFC 2960:  "Stream Control Transmission Protocol".
[4]  Void.
[5]
RFC 2234:  "Augmented BNF for syntax specifications".
[6]
TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; protocol details".
[7]
RFC 3589:  "Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5".
[8]
ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[9]
TR 33.978: "Security aspects of early IP Multimedia Subsystem (IMS) (Release 6)".
[10]
TS 29.364: "IMS Application Server Service Data Descriptions for AS interoperability".
[11]
TS 29.002: "Mobile Application Part (MAP) specification".
[12]
RFC 7683:  "Diameter Overload Indication Conveyance".
[13]
RFC 7944:  "Diameter Routing Message Priority".
[14]
RFC 8583:  "Diameter Load Information Conveyance".
[15]
RFC 6733:  "Diameter Base Protocol".
[16]
TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
Up

3  Definitions, symbols and abbreviationsp. 7

3.1  Definitionsp. 7

Refer to RFC 6733 for the definitions of some terms used in this document.
For the purposes of the present document, the following terms and definitions apply.
Attribute-Value Pair:
see RFC 6733, it corresponds to an Information Element in a Diameter message.
Server:
SIP-server.
User data:
user profile data.

3.2  Abbreviationsp. 7

For the purposes of the present document, the following abbreviations apply:
AAA
Authentication, Authorization and Accounting
AS
Application Server
ABNF
Augmented Backus-Naur Form
AVP
Attribute-Value Pair
CN
Core Network
DRMP
Diameter Routing Message Priority
DSCP
Differentiated Services Code Point
HSS
Home Subscriber Server
IANA
Internet Assigned Numbers Authority
IETF
Internet Engineering Task Force
IMS
IP Multimedia Subsystem
NDS
Network Domain Security
RFC
Request For Comment
SCTP
Stream Control Transport Protocol
UCS
Universal Character Set
URL
Uniform Resource Locator
UTF
UCS Transformation Formats
Up

4  Generalp. 7

The Diameter base protocol as specified in RFC 6733 shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 6 of this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified.

5  Use of the Diameter base protocolp. 8

The same clarifications of clause 5 of TS 29.229 shall apply to the Sh interface. An exception is that the application identifier for this application is defined in clause 6.

Up   Top   ToC