Oracle® Communications Converged Application Server Concepts Release 5.1 Part Number E27705-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how Oracle Communications Converged Application Server complies with various specifications and RFCs.
Converged Application Server is developed with special attention to Internet Engineering Task Force (IETF) and 3rd Generation Partnership Project (3GPP) specifications. Feature development is prioritized according to general market trends, both observed and predicted. In cases where certain specifications are obsolete or where Internet drafts are formalized as 'Request For Comments' standards, Converged Application Server places priority on compliance with those specifications. In cases where specifications are part of a larger release plan, as with the 3GPP, Oracle prioritizes compliance with the latest ratified release (in this case, Release 6). This should not be presumed to mean that the product is not compliant with subsequent versions of component specifications, although this document does not summarize compliance with those specifications.
Converged Application Server is compliant with Java EE version 5.0 and the corresponding Java EE component specifications.
Converged Application Server is further enhanced by the addition of a SIP Servlet container defined by JSR 289: "SIP Servlet API."
Converged Application Server has executed all related Test Compatibility Kits (TCKs) and has met the formal requirements established by Sun Microsystems for formal public statements of compliance.
The following table lists the Converged Application Server level of compliance to common IETF Requests for Comment (RFCs) and Internet drafts. The level of compliance is defined as follows:
Yes—Indicates that Converged Application Server directly supports the feature or specification.
Yes (Platform)—Indicates Converged Application Server can host applications or components that implement the RFC. However, the RFC or feature has no impact on the transaction layer of the protocol or on the behavior of the SIP Servlet container.
Table 6-1 Converged Application Server IETF Compliance
RFC or Specification Number | Title | Compliant? | Additional Information |
---|---|---|---|
761 |
DoD Standard Transmission Control Protocol |
Yes |
See |
768 |
User Datagram Protocol |
Yes |
See |
1157 |
A Simple Network Management Protocol (SNMP) |
Yes |
Converged Application Server supports SNMP V2c traps. See |
1847 |
Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted |
Yes (Platform) |
Converged Application Server supports applications that consume or generate signed or encrypted multipart MIME objects. See |
1901 |
Introduction to Community-based SNMPv2 |
Yes |
Converged Application Server supports SNMP V2c traps. See |
1905 |
Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) |
Yes |
Converged Application Server supports SNMP V2c traps. See |
1906 |
Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) |
Yes |
Converged Application Server supports SNMP over both TCP and UDP. See |
1907 |
Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) |
Yes (Platform) |
See |
2183 |
Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
2246 |
The TLS Protocol Version 1.0 |
Yes |
Converged Application Server supports TLS. See |
2460 |
Internet Protocol, Version 6 (IPv6) Specification |
Yes |
See |
2543 |
SIP: Session Initiation Protocol (v1) |
Yes |
Converged Application Server supports backward compatibility as described in this specification. See |
2571 |
An Architecture for Describing SNMP Management Frameworks |
Yes |
See |
2572 |
Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) |
Yes |
See |
2573 |
SNMP Applications |
Yes |
See |
2574 |
User-based Security Model (USM) for version 3 of theSimple Network Management Protocol (SNMPv3) |
Yes |
See |
2575 |
View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
Yes |
See |
2576 |
Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework |
Yes |
See |
2616 |
Hypertext Transfer Protocol -- HTTP 1.1 |
Yes |
See |
2617 |
HTTP Authentication: Basic and Digest Access Authentication |
Yes |
See |
2782 |
A DNS RR for specifying the location of services (DNS SRV) |
Yes |
See |
2786 |
Diffie-Helman USM Key Management Information Base and Textual Convention |
Yes |
See |
2806 |
URLs for Telephone Calls |
Yes |
See |
2848 |
The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services |
Yes (Platform) |
Note that implementing PINT services implies a pre-IMS architecture. Although Oracle favors the 3GPP/TISPAN architecture and approach to class 4/5 Service Emulation and does not advocate PINT, it is possible to implement PINT service elements using Converged Application Server. See |
2960 |
Stream Control Transmission Protocol |
Yes |
SCTP supported only for Diameter traffic. See |
2976 |
The SIP INFO Method |
Yes |
See |
3204 |
MIME media types for ISUP and QSIG Objects |
Yes (Platform) |
Converged Application Server does not directly consume or generate ISUP and QSIG objects, but it supports applications that consume or generate these objects. See |
3261 |
SIP: Session Initiation Protocol |
Yes |
See |
3262 |
Reliability of Provisional Responses in the Session Initiation Protocol (SIP) |
Yes |
See |
3263 |
Session Initiation Protocol (SIP): Locating SIP Servers |
Yes |
See |
3264 |
An Offer/Answer Model with Session Description Protocol (SDP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3265 |
Session Initiation Protocol (SIP)-Specific Event Notification |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3268 |
Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS) |
Yes (Platform) |
Converged Application Server supports cryptographic services, but specific algorithms that are used are subject to local availability and export control. See |
3311 |
The Session Initiation Protocol (SIP) UPDATE Method |
Yes |
Converged Application Server supports applications that conform to this specification. See |
3312 |
Integration of Resource Management and Session Initiation Protocol (SIP). |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3313 |
Private Session Initiation Protocol (SIP) Extensions for Media Authorization |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3323 |
A Privacy Mechanism for the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3325 |
Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks |
Yes |
See |
3326 |
The Reason Header Field for the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3327 |
Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts. |
Yes (Platform) |
See |
3351 |
User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3372 |
Session Initiation Protocol for Telephones (SIP-T): Context and Architectures |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3420 |
Internet Media Type message/sipfrag |
See |
|
3428 |
Session Initiation Protocol (SIP) Extension for Instant Messaging |
Yes |
See |
3455 |
Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3515 |
The Session Initiation Protocol (SIP) Refer Method. |
Yes |
See |
3524 |
Mapping of Media Streams to Resource Reservation Flows |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3556 |
Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3578 |
Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification, but it does not provide an ISUP interface. See |
3581 |
An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing |
Yes |
See |
3589 |
Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5 |
Yes |
See |
3588 |
Diameter Base Protocol |
Yes |
See |
3605 |
Real Time Control Protocol (RTCP) attribute in Session Description Protocol ((SDP) |
Yes (Platform) |
|
3608 |
Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration. |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification, but it does not provide a means of storing the ServiceRoute established during registration. This functionality can be implemented as part of the application. See |
3665 |
Session Initiation Protocol (SIP) Basic Call Flow Examples. |
Yes |
Converged Application Server supports applications that conform to this specification. See |
3666 |
Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3680 |
A Session Initiation Protocol (SIP) Event Package for Registrations |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3689 |
General Requirements for Emergency Telecommunication Service (ETS) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3690 |
IP Telephony Requirements for Emergency Telecommunication Service (ETS) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3702 |
Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP) |
Yes |
Converged Application Server version supports JDBC and LDAP. See |
3725 |
Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) |
Yes |
Converged Application Server supports applications that conform to this specification. See |
3761 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) |
Yes |
See |
3764 |
Enumservice Registration for Session Initiation Protocol (SIP) Addresses-of-Record |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3824 |
Using E.164 numbers with the Session Initiation Protocol (SIP) |
Yes |
See |
3826 |
The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model |
Yes |
See |
3840 |
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3841 |
Caller Preferences for the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3853 |
S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3891 |
The Session Initiation Protocol (SIP) 'Replaces' Header |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3892 |
The Session Initiation Protocol (SIP) Referred-By Mechanism |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3893 |
Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3903 |
Session Initiation Protocol (SIP) Extension for Event State Publication |
Yes |
See |
3911 |
The Session Initiation Protocol (SIP) "Join" Header |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3959 |
The Early Session Disposition Type for the Session Initiation Protocol (SIP) |
See |
|
3960 |
Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
3966 |
The tel URI for Telephone Numbers |
Yes |
See |
4028 |
Session Timers in the Session Initiation Protocol (SIP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
4032 |
Update to the Session Initiation Protocol (SIP) Preconditions Framework |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
4244 |
An Extension to the Session Initiation Protocol (SIP) for Request History Information |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
4320 |
Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction |
Yes |
See |
4321 |
Problems Identified Associated with the Session Initiation Protocol's (SIP) Non_INVITE Transaction |
Yes |
See |
4474 |
Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) |
Yes |
See |
4483 |
A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
4566 |
SDP: Session Description Protocol |
Yes |
Converged Application Server supports applications that consume or generate SDP. See |
4825 |
The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
5888 |
The Session Description Protocol (SDP) Grouping Framework |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
5806 |
Diversion Indication in SIP |
Yes |
Converged Application Server supports applications that conform to this specification. See |
draft-donovan-mmusic-183-00 |
SIP 183 Session Progress Message Draft |
Yes (Platform) |
Converged Application Server supports applications that conform to this specification. See |
draft-ietf-sip-gruu-15 |
Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP) |
Yes |
See |
draft-reeder-snmpv3-usm-3desede-00 |
Extension to the User-Based Security Model (USM) to Support Triple-DES EDE in "Outside" CBC Mode |
Yes |
See
|
Table 6-2 summarizes the ability of Converged Application Server to support implementation of the enablers or application functions identified by each applicable 3GPP Release 6 specification.
Other than the exceptions noted, Converged Application Server does not impose any restrictions on implementing applications or functions that are compliant with those associated with the Application Server entity described in the specification. In some cases, applications must implement support for SIP methods or headers. The default behavior of the Converged Application Server Sip Servlet Container is to pass unrecognized headers, request methods and payloads to SIP Servlets using normal SIP Servlet API procedures.
Table 6-2 3GPP R6 Specification Conformance
Specification | Comments |
---|---|
3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2 (Release 6)" |
No comments. |
3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 6)" |
Converged Application Server does not enforce the requirement that only one p-charging-function-address header per SIP request as described in sub-section 5.7.1.2. Converged Application Server does enforce uniqueness. Converged Application Server does not provide privacy support as described in sub-section 5.7.3. |
3GPP TS 23.141: "Presence Service; Architecture and Functional description (Release 6)" |
Converged Application Server does not natively support the Ph (MAP), Pl (LIF-MLP), Px (DIAMETER Cx/Dx), Pg (phase 4, 3GPP Release 5),Pc (CAMEL phase 4, 3GPP Release 5) or Pr, Pk and Pp (RADIUS) reference points. Converged Application Server does not support IPv6 as required for the Presence User Agent (Peu) reference point as required in sub-section 4.3.1. |
3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2 (Release 6)" |
No comments. |
3GPP TS 24.247 "Messaging using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (Release 6)" |
Converged Application Server does not provide support for the Message Session Relay Protocol (MSRP), although it is presumed that an MSRP relay will typically be implemented as a Media Resource Function in the IMS architecture. |
3GPP TS 24.841: "Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details (Release 6)" |
Converged Application Server does not provide support for IETF RFC 3310: "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)". |
3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details (Release 6)" |
Converged Application Server does not provide support for IETF RFC 3310: "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)". Converged Application Server supports the 'X-3GPP-Asserted-Identity extension-header' for use in applying access control and authorization constraints within the integrated security framework. |
3GPP TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents" |
No comments. |
3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details" |
No comments. |
3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications" |
No comments. |
3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) (Release 6)" |
Converged Application Server supports the Application Server role in the GAA. |