Technical Product Description

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Standards Alignment

The following sections describe how WebLogic SIP Server complies with various specifications and RFCs:


Overview of WebLogic SIP Server Standards Alignment

WebLogic SIP Server is developed with special attention to Internet Engineering Task Force and 3rd Generation Partnership Project 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, WebLogic SIP Server places priority on compliance with those specifications. In cases where specifications are part of a larger release plan, as with the 3GPP, BEA 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.


Java Sun Recommendation (JSR) Standards Compliance

WebLogic SIP Server is compliant with J2EE versions 1.4 and 1.3 and the corresponding J2EE component specifications. See Standards Support in the WebLogic Server 9.2 documentation for more details.

WebLogic SIP Server is further enhanced by the addition of a SIP Servlet container defined by JSR 116: “SIP Servlet API.”

WebLogic SIP 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.


IETF RFC Compliance

The following table lists the WebLogic SIP Server level of compliance to common Internet Engineering Task Force (IETF) Requests for Comment (RFCs) and Internet drafts. The level of compliance is defined as follows:


3GPP R6 Specification Conformance

Table 5-2, 3GPP R6 Specification Conformance, on page 5-12 summarizes the ability of WebLogic SIP Server to support implementation of the enablers or application functions identified by each applicable 3GPP Release 6 specification.

Other than the exceptions noted, WebLogic SIP 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 WebLogic SIP Server Sip Servlet Container is to pass unrecognized headers, request methods and payloads to SIP Servlets using normal SIP Servlet API procedures.

Table 5-2 3GPP R6 Specification Conformance
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)”
  • WebLogic SIP Server does not enforce the requirement that only one p-charging-function-address header per SIP request as described in sub-section WebLogic SIP Server does enforce uniqueness.
  • WebLogic SIP 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)”
  • WebLogic SIP 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.
  • WebLogic SIP 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)”
  • WebLogic SIP 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)”
  • WebLogic SIP 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)”
  • WebLogic SIP Server does not provide support for IETF RFC 3310: “Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)”.
  • WebLogic SIP 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)”
  • WebLogic SIP Server supports the Application Server role in the GAA.

  Back to Top       Previous  Next