1 / 56

AdvOSS Software Architectures

AdvOSS Software Architectures. Target Markets. Carrier Grade Quality. AdvOSS platforms offer carrier grade quality for its products. These quality benefits are achieved through a combination of: Enabling Technologies Software Architectures. Enabling Technologies.

vivien
Download Presentation

AdvOSS Software Architectures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AdvOSS Software Architectures

  2. Target Markets

  3. Carrier Grade Quality AdvOSS platforms offer carrier grade quality for its products. These quality benefits are achieved through a combination of: • Enabling Technologies • Software Architectures

  4. Enabling Technologies These are a range of technologies that are used by AdvOSS in its platforms to achieve quality objectives. Many of these technologies are developed by AdvOSS. Others are third party technologies or features used by AdvOSS to achieve its quality ends.

  5. 1. AMPS AMPS (Asynchronous Middleware of Parallel Systems) It is an AdvOSS own technology. It is a middleware that is internally running on a high performance asynchronous processing engine and offers many aspects of reliability, efficiency and others. Details can be found at http://OpenAMPS.org

  6. 2. Protocol Stacks AdvOSS has its own developed protocol stacks that are built on top of AMPS. These stacks are available for the following protocols: • SIP • Radius • Diameter

  7. 3. Service Delivery Engine AdvOSS SDE is a Service Creation Engine with a service execution engine that allows high speed execution of work flows. SDE is based on industry standard CCXML (Call Control XML). We have made proprietary extensions to it and call it SCCXML (Service Creation and Control XML). Details can be found at http://sccxml.org

  8. 4. Media Server AdvOSS Media Server is a powerful media handling server that realizes industry standard MSCML (Media Server Control Markup Language) with some proprietary extensions.

  9. 5. Heart-Beat AdvOSS Heart-Beat is a High Availability framework that exposes Virtual IP connections upon identical servers and the heart-beat mechanism allows an automatic IP take over from one server to the other when one server goes down.

  10. 6. Packet Router Packet Router is yet another AdvOSS technology that is based on AdvOSS’ own protocol stacks and AMPS. It allows load distribution and dispatching of layer 7 packets at high speed. A layer 4 and a layer 7 dispatcher together achieve highest speed load distribution among serving nodes.

  11. 6. Packet Router

  12. 7. DTMS DTMS (Database and Transaction Management System) is an AdvOSS database abstraction layer and provides for: • Database independence • Support for distributed databases

  13. 8. SysLog SysLog is AdvOSS’ own technology for reliable very high speed logging of records into databases or text files.

  14. 9. Orchestrator Orchestrator is yet another AdvOSS technology part of AdvOSS Provisioning Engine that allows work flow execution through any external third party work flow execution engine.Following languages are supported out of the box: • Xproc (a w3c standard for pipelined workflows) • Groovy Pipelines (Proprietary language) • SCCXML (Through AdvOSS SDP)

  15. 9. Orchestrator

  16. Software Architectures In addition to the above mentioned enabling technologies, AdvOSS uses many aspects of software architecture and design in its products to achieve quality objectives.

  17. 1. Layered Architecture AdvOSS products are designed in layers which typically are: • Dispatching • Applications • Processes • APIs • Database Processing

  18. 2. Work Flow driven processes All AdvOSS Applications are written in work flow languages which are open source and work on a work flow processing engine.

  19. 3. Policy Driven APIs All AdvOSS APIs are transactional in nature and embed all the business logic in them. To keep them compliant with changing business rules, they all designed to work with Policy Servers that allows realization of company policies into the APIs.

  20. 4. Service Oriented Architectures All AdvOSS Products are designed based on a SOA (Service Oriented Architecture) enabling an operator to extend the functionality through loosely coupled components.

  21. 5. Shared Information & Data All AdvOSS Platforms are designed on a shared information and data model. This SID is shared among all products in all platforms of Service Delivery, Service Management and Service Charging.

  22. 6. Role Aware Alerting All AdvOSS APIs send error messages that are already classified according to SLA roles of: • Operations • Configuration • Network • Work Flow and IT • Database • Code

  23. 7. Extensible Data Models All AdvOSS data models are infinitely extensible and enable to add new attributes for every object as and when required.

  24. 8. XML based core processing All core processing within applications is based on XML that allows easy extensions of code or meta data or data models.

  25. 9. Multi-Master Databases All AdvOSS databases are deployed in multi-master configuration

  26. 10. Monitoring Interfaces All AdvOSS Products provide extensive interfaces for monitoring of key performance indicators. This includes interfaces for different monitoring systems including through SNMP, XML or web.

  27. 11.RESTful APIs All AdvOSS Products GUI is written on top of RESTful APIs allowing easy integration with third party north bound systems.

  28. 12. Transactional APIs All AdvOSS Products have their own basic API. This API exposes all business logic as methods that are coded as a single transaction.

  29. Business Benefits Above mentioned enabling technologies and architectural aspects are used to derive multiple business benefits.

  30. 1. High Availability AdvOSS High Availability framework allows the system to continue functioning in the condition of a hardware or network failure

  31. Scenario 1: Failure of Application Node The Packet Router sends the packets to other nodes for processing

  32. Scenario 2: Failure of Packet Router The AdvOSS Heart-Beat application moves packet routing to secondary node

  33. Scenario 3: Failure of Database AdvOSS DTMS application moves traffic to secondary master server in the database.

  34. 2. Scalability AdvOSS Scalability Architecture allows a Service Provider to start small and grow as much as needed.Packet Router along with the dispatcher / serving node model allows for addition of new serving nodes on the fly for applications. For databases, multi-master deployment model allows for scaling out and adding new nodes for further processing.

  35. Application Node Scalability Packet Router distributes the load onto multiple Application Nodes. Application nodes can be added as many as needed. Packet Router Scalability Packet Router is very efficient load distributor and works on Layer 7 load balancing. If needed, a Layer 4 load balancer can be added and multiple Layer 7 packet routers can be added

  36. Database Scalability More nodes can be added in the multi-master ring for distribution of read loads onto multiple database server.

  37. 3. Redundancy AdvOSS Redundancy Architecture allows a Service Provider to keep extra resources either in load-sharing or hot-standby mode and use them in case of failures

  38. Application Node Redundancy Packet Router keeps all application nodes in active load-sharing.

  39. Packet Router Redundancy: AdvOSS Heart-Beat framework allows a Service Provider to keep two packet router nodes where one stays as a hot-standby and assumes the load on failure of primary node.

  40. Database Redundancy: Multi-master Replication allows to keep extra databases fully ready with latest data in sync. In case of failure, such extra database nodes are used by DTMS automatically

  41. 4. Disaster Recovery And Geographical Redundancy Master / Slave Replication Remote Multi-Master replication Enables Geographical Redundancy

  42. 5. Live Upgradability Dispatcher / Node model allows to bring down a node and upgrade it while other nodes are serving Heart-Beat allows to move IP to other servers and upgrade the dispatcher node if needed.

  43. 6. Live re-configurability XML based configuration files That can be reloaded while servers are running

  44. 7. Overload protection Admission Control on ingress and rate limiting on egress provides over load protection

  45. 8. Service Assurance Service Assurance aware applications that continue to deliver service while some resources are unavailable

  46. 9. Customizability SCCXML based work flows for AAA Xproc or groovy based work flows for GUI

  47. 10. Adaptability Policy Driven APIs and architectures allow adapting to changes business needs and rules

  48. 11. Extensibility XML cores and extensible data models allow extending the core functionality and data models.

  49. 12. Testing and Staging Debugging criteria in packet router

More Related