PEERing In, PEERing Out: Peer Education Approaches in Cultural Diversity Projects
AdvOSS Software Architectures. Target Markets Wimax/4G LTECDMA Broadband Prepaid Voice Residential...
-
Upload
garey-clarence-bradford -
Category
Documents
-
view
215 -
download
0
Transcript of AdvOSS Software Architectures. Target Markets Wimax/4G LTECDMA Broadband Prepaid Voice Residential...
AdvOSS Software Architectures
Target Markets
Wimax/4G
LTE
CDMA
Broadband
Prepaid Voice
Residential VoBB
SIP Trunking
VoIP Peering
Carrier Grade Quality
AdvOSS platforms offer carrier grade quality for its products. These quality benefits are achieved through a combination of:
0Enabling Technologies0Software Architectures
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.
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
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:0SIP0Radius0Diameter
Service Delivery Platform
SIP Radius
Asynchronous Middleware for Parallel Systems (AMPS)
OPERATING SYSTEM
Diameter
3. Service Delivery EngineAdvOSS 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
Service Logic & Workflow Layer
Protocol Specific interface Layer
Service Logic & Workflow For
Radius Applications
Service Logic & Workflow For
Diameter Applications
Service Logic & Workflow For
Diameter Applications
Service Logic & Workflow For
SIP Applications
RadiusFrontend
DiameterFrontend
SIPFrontend
Wi-MaxService Delivery
Function
LTE NetworkAccess Function
Evolved PacketCore Policy
Enforcement Funtion
IMSCall Control
Network element specific Radius Interface
Standard Diameter Interface
Standard Diameter InterfaceStandard SIP
Interface
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.
IVR
Transcoding
Proxy
Conferencing
IVR
IVR
IVR
Proxy Proxy
Proxy
Transcoding
Transcoding Conferencing
Proxy
IVRTranscoding
Conferencing
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.
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.
6. Packet Router
Dispatcher
Dispatcher / Server Architecture
External Elements External Elements
Serving Nodes Serving Nodes Serving Nodes Serving Nodes
Clients Clients Clients Clients
7. DTMS
DTMS (Database and Transaction Management System) is an AdvOSS database abstraction layer and provides for:0Database independence0Support for distributed databases
DBMS
Transactional API’s
Database Abstration
8. SysLog
SysLog is AdvOSS’ own technology for reliable very high speed logging of records into databases or text files.
SysLogApplication
Files
Database
Event SourcesEvent Sources Reliable Persistent Storage
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:0Xproc (a w3c standard for pipelined workflows)0Groovy Pipelines (Proprietary language)0SCCXML (Through AdvOSS SDP)
9. Orchestrator
Orchestrator
Work Flow Processing Engine
Work Flow Processing EngineClient Request
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.
1. Layered Architecture
AdvOSS products are designed in layers which typically are:0Dispatching0Applications
0 Processes0 APIs
0Database Processing
Dispatcher / Packet Router
Client Requests
Application Nodes
Database
Database Abstraction
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.
Work Flow Processor
Client Process Requests
API
API
API
API
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.
Processing
Processing
Processing NO
YES
Policy ServerPolicy ServerPolicy Query
Business Logic APIs
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.
Event Rendezvous
API ComponentComponent
API
API
API
ComponentComponent
ComponentComponent
ComponentComponent
5. Shared Information & DataAll 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.
Shared Information & Data Model
Application Application Application Application
6. Role Aware Alerting
All AdvOSS APIs send error messages that are already classified according to SLA roles of:0Operations0Configuration0Network0Work Flow and IT0Database0Code
API Alerting
Database
IT
Administration
System Admin
Network Admin
Subscriber
Operations
7. Extensible Data ModelsAll AdvOSS data models are infinitely extensible and enable to add new attributes for every object as and when required.
8. XML based core processingAll core processing within applications is based on XML that allows easy extensions of code or meta data or data models.
Protocol To XML North Bound
XML Based Core Processing
Database
XML to Protocol South Bound
Edge Translation
Application Application Application Application
9. Multi-Master DatabasesAll AdvOSS databases are deployed in multi-master configuration
Master Master
Master
Slave
Slave
Slave
10. Monitoring InterfacesAll AdvOSS Products provide extensive interfaces for monitoring of key performance indicators. This includes interfaces for different monitoring systems including through SNMP, XML or web.
Application
PerformanceMetrics
Monitoring Agents
SNMP Manager
Monitoring Application
11.RESTful APIs
All AdvOSS Products GUI is written on top of RESTful APIs allowing easy integration with third party north bound systems.
Rest APIs
API API API API
External Clients
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.
Processing
SuccessRollback
Processing
SuccessRollback
Processing
SuccessRollback
Commit
NO
yes
NO
yes
NO
Yes
Business Benefits
Above mentioned enabling technologies and architectural aspects are used to derive multiple business benefits.
1. High AvailabilityAdvOSS High Availability framework allows the system to continue functioning in the condition of a hardware or network failure
Scenario 1: Failure of Application NodeThe Packet Router sends the packets to other nodes for processing
X
Application Node-1Application Node-1
Application Node-2Application Node-2Packet RouterPacket Router
Application Node-3Application Node-3
Application Node-4Application Node-4
Scenario 2: Failure of Packet RouterThe AdvOSS Heart-Beat application moves packet routing to secondary node
Application Node-1Application Node-1
Application Node-2Application Node-2Packet Router-1Packet Router-1
Application Node-3Application Node-3
Application Node-4Application Node-4
Packet Router-2(standby)Packet Router-2(standby)
Request
Packet Router-1Packet Router-1
Request
Application Node-1Application Node-1
Application Node-2Application Node-2
Application Node-3Application Node-3
Application Node-4Application Node-4
Packet Router-2(standby)Packet Router-2(standby)
Scenario 3: Failure of DatabaseAdvOSS DTMS application moves traffic to secondary master server in the database.
PrimaryDatabase
Secondary Database
DTMSIncoming Requests
PrimaryDatabase
Secondary Database
DTMSIncoming Requests
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.
Application Node ScalabilityPacket Router distributes the load onto multiple Application Nodes. Application nodes can be added as many as needed.
Packet Router ScalabilityPacket 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
Database ScalabilityMore nodes can be added in the multi-master ring for distribution of read loads onto multiple database server.
Multi-MasterReplication
DataBase DataBase
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
Application Node RedundancyPacket Router keeps all application nodes in active load-sharing.
75% LoadApplication Node-1Application Node-1
75% Load
Application Node-2Application Node-275% Load
75% Load
Application Node-3Application Node-3
Application Node-4Application Node-4
Packet RouterPacket Router X Application Node-1Application Node-1
100% Load
Application Node-2Application Node-2100% Load
100% Load
Application Node-3Application Node-3
Application Node-4Application Node-4
Packet RouterPacket Router
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.
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
Master Master
Master
Slave
Slave
Slave
4. Disaster Recovery And Geographical Redundancy
Master / Slave Replication
Remote Multi-Master replication
Enables Geographical Redundancy
5. Live Upgradability
Dispatcher / Node model allows to bring down a node and upgrade it while other nodes are servingHeart-Beat allows to move IP to other servers and upgrade the dispatcher node if needed.
6. Live re-configurability
XML based configuration filesThat can be reloaded while servers are running
7. Overload protection
Admission Control on ingress and rate limiting on egress provides over load protection
Ingress Egress
Admission Control Rate limiting
Application
8. Service Assurance
Service Assurance aware applications that continue to deliver service while some resources are unavailable
Application
DatabaseX
Service Assurance Policies
9. Customizability
SCCXML based work flows for AAAXproc or groovy based work flows for GUI
10. Adaptability
Policy Driven APIs and architectures allow adapting to changes business needs and rules
Processing
Processing
Processing NO
YES
Policy ServerPolicy ServerPolicy Query
Business Logic APIs
11. Extensibility
XML cores and extensible data models allow extending the core functionality and data models.
12. Testing and Staging
Debugging criteria in packet router
Serving Application Node
Staging Application Node
Packet RouterPacket Router
Matching Criteria
13. Usability
All operations teams have a highly usable web based GUI available to them.
All administrative tasks have a desktop based GUI available to them.
Usability
14. Security
Provisioning Engine based deployment modelRole based security
Self Care Portal
DMZ
Administrator PortalRole Based Security
Provisioning Engine Client Authentication
Request Validation
Firewall
Network Elements
Public Internet
15. Auditability
Role based security
Detailed audit trail
16. Monitoring
SNMP agentsOther performance monitoring countersAlerting interfacesCentralized Alerting application
Application
PerformanceMetrics
Monitoring Agents
SNMP Manager
Monitoring Application
Contact Us
Website: http://AdvOSS.comEmail: [email protected] Head Office: 10691 Shellbridge Way, Suite 120
Richmond, BC V6X 2W8, Canada
Tel: +1 (604) 800 0269