Diameter Servlet Container for Converged Application Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Diameter applications cannot leverage traditional Java Servlet strengths such as high availability, flexible request dispatching, application packaging, application tooling, application deployment, load balancing, and converged session affinity in a clustered environment due to the inability to write Diameter application logic using Java Servlet technologies.
Innovation Solution
A servlet-based programming model is developed to support Diameter applications, providing a 'base protocol' servlet and base application servlets for each Diameter interface, which integrate with the J2EE application model and SIP specifications, enabling Diameter applications to utilize shared servlet contexts and containers for enhanced functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Diameter application logic is written using traditional Java Servlet technologies, then high availability, flexible request dispatching, application packaging, application tooling, application deployment, load balancing, and converged session affinity are improved, but the inability to write Diameter applications using Servlet technologies prevents these improvements
Solution Approach 1:
A Diameter Servlet Container is introduced as an intermediary layer between the Diameter protocol stack and the Java Servlet ecosystem. This container acts as a mediator that translates Diameter protocol messages into Servlet-compatible requests and responses, enabling Diameter applications to leverage Java Servlet strengths without requiring direct Servlet technology implementation for Diameter logic.
Solution Approach 2:
The Diameter Servlet Container provides universal functionality by supporting multiple Diameter protocols (Rx, Ro, Cx, Dx interfaces) within a single unified architecture. It enables a single container to handle diverse Diameter application types, making the system versatile while maintaining high availability and load balancing capabilities through standard Java Servlet mechanisms.
2Ease of manufacture
If a servlet-based programming model is developed for Diameter applications, then application packaging and deployment flexibility are improved, but device complexity increases due to integration requirements
Solution Approach 1:
The system is segmented into distinct modular components: the Diameter Servlet Container, base protocol servlets, and application-specific servlets. This segmentation allows each component to be developed, tested, and deployed independently, simplifying the packaging process while reducing integration complexity through clear interface definitions between modules.
Solution Approach 2:
The architecture employs a nested structure where application servlets extend base protocol servlets, which in turn extend the Diameter Servlet Container. This nesting enables inheritance and reuse of functionality at multiple levels, reducing overall system complexity while maintaining packaging flexibility through modular component assembly.
3Adaptability or versatility
If base protocol servlets and base application servlets are provided for each Diameter interface, then adaptability and versatility are improved, but device complexity increases
Solution Approach 1:
Base protocol servlets are designed as universal multi-functional components that can handle multiple Diameter interfaces (Rx, Ro, Cx, Dx) through a common architecture. This universality reduces the need for separate dedicated servlet classes for each interface, thereby improving adaptability without proportionally increasing device complexity.
Solution Approach 2:
The base protocol servlets utilize parameter changes and configuration mechanisms to adapt their behavior across different Diameter interfaces. By changing operational parameters rather than creating entirely new servlet classes for each interface, the system achieves versatility while minimizing the increase in device complexity.
Data Source
AI summary
Mechanisms for developing Diameter applications are provided. The mechanisms extend the application server servlet model to support Diameter applications. A “base protocol” servlet is provided that handles the basic Diameter protocol functionality. Base application servlets are provided for each Diameter interface (for example, an “Sh” base servlet for the IMS “Sh” interface). These servlets are base classes for application code. The base application servlets implement additional semantics on top of the base protocol servlet to support additional attribute-value pair semantics. With the system and method, Diameter servlets share the same ServletContext as HTTP and SIP servlets. This mechanism facilitates communication between the various application entities and facilitates generation of converged applications.