Open and Monetize Telecom Networks: BEA WebLogic Network Gatekeeper Thomas Gronberg Director WLNG Product Management BEA Systems Inc.

BEA Confidential | 2 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 3 Telecom Industry Challenges Service Provider Consolidation & Competition Decreasing ARPU High Costs Convergence Single Service Orientation Voice Internet Wireless Wi-Fi Cable VoIP Media Duplicate Network Infra For Each New Service Consolidation of Networks, Bandwidth, Subscriber Base

BEA Confidential | 4 Network Infrastructure Business Environment End-Users & Devices Common Challenges New Services Short lived Long lived Risks Innovation Segmentation Business Models Increasing Network Bandwidth Adoption of Converged IT-Telecom Standards Multiple Vendors (IT and Telecom) Internet Experience Multimedia Devices Multi-Access, Intelligent Devices Expectations User Experience Privacy Loyalty

BEA Confidential | 5 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 6 Telecom Web Services & Parlay X Now all developers – not just telecom experts – can easily build carrier-grade telecom applications using BEA WebLogic Network Gatekeeper Standards-based, High-Level Interfaces Parlay X Web Services from The Parlay Group 1 Access to Core Network Capabilities Messaging, Call Control, Location, Charging 2 Leverage Off-the-Shelf Developer Tools BEA WebLogic Workshop 3

BEA Confidential | 7 Parlay & Open Service Access (OSA) Parlay/OSA & Parlay X Telecom Web Services Parlay/OSA Applications Wireline WirelessIP Parlay Group & OSA Founded in 1998 Industry consortia of over 75 IT and telecom companies, including network operators, IT vendors, NEPs, and ISVs. Develops and publishes the Parlay API specifications Parlay/OSA & Parlay X Telecom industry standard API specification defined by ETSI, 3GPP, and Parlay Group Standard interface for 3 rd party applications to access operators network service capabilities Parlay/OSA is defined in UML Parlay X is high-level Web Services abstraction of Parlay/OSA APIs

BEA Confidential | 8 Parlay and Parlay X Network Architecture SERVICE DELIVERY LAYER APPLICATION & SERVICES LAYER NETWORK LAYER Wireline WirelessIP Parlay App Server Parlay/OSA Gateway FrameworkService Capability Servers CORBA Parlay X Web Services Gateway WSDL CORBA Network Protocols (MM7, LIF, SMPP, etc.) Network Protocols (SIP, INAP, CAP, etc.)

BEA Confidential | 9 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 10 BEA WebLogic Network Gatekeeper (WLNG) What It Is Java/Telecom Web Services-based platform to control & manage enterprise/carrier network quality Policy enforcement engine controlling access to operators network from 3 rd party apps What It Does Telecom-enable business applications Guarantee customer/partner Quality-of-Service (QoS) with Service Level Agreements (SLA) enforcement Increase network quality by controlling network access, usage and traffic Network traffic routing and throttling Separates application and network interfaces Enhance Partner/Customer Satisfaction with Network Service Quality and Security BEA WebLogic Network Gatekeeper Network Adapters Policy Engine Access Control OA&MPartner Management Billing Telecom Web Services Networks Elements (IMS, SSP, SMSC) Applications (Java, Web Services)

BEA Confidential | 11 BEA WebLogic Network Gatekeeper (WLNG) ACCESS CONTROL LAYER SERVICE PROVIDERS & APPLICATIONS NETWORK ELEMENTS MessagingCall ControlMobility Parlay/OSA GWMMSC SMSC BEA WebLogic Network Gatekeeper Network Adapters Telecom Web Services Policy Engine Access Control OA&M Partner Management Billing Developer Tools Location

BEA Confidential | 12 BEA WLNG in the Legacy Network ACCESS LAYER APPLICATION SERVICES LAYER NETWORK LAYER Wireline WirelessIP Network Protocols (MM7, LIF, SMPP, etc.) Network Protocols (SIP, INAP, CAP, etc.) CORBA Parlay App Server Parlay/OSA Gateway Framework Service Capability Servers SIP HTTP BEA WebLogic Network Gatekeeper BEA WebLogic SIP Server BEA WebLogic Communications Platform CORBA Applications (Java, Web Services)

BEA Confidential | 13 WLNG Product Architecture Charging Service Capabilities User Location User Status MessagingCall Control User Interaction Subscriber Profile Network Plug-Ins MM7 (MMS) SMPP (SMS) LIF/MLP (User Location/ User Status) CORBA (Parlay/Call) SMTP (MMS/ ) POP (MMS/ ) IMAP ( ) Telecom Web Services Policy Engine Rules/SLA Database Rules Engine Access Control Charging & Billing Partner Mgmt CORBA Plug-In Manager CORBA Applications (Java, Web Services) Networks Elements (IMS, SSP, SMSC) CORBA

BEA Confidential | 14 Web Services Interfaces Parlay X Network initiated third party call Third party call SMS Multimedia message Payment User Status Terminal Location Value added APIs for Call Charging Messaging, SMS and MMS User location User status Subscriber profile User interaction, call based and message based

BEA Confidential | 15 Web Services interfaces also exposed through BEA WebLogic Workshop Controls Parlay XValue added APIs

BEA Confidential | 16 Wireline WirelessIP PRM i/f Parlay X - Web Services interface Service Capabilities Application Enablers Network Adapters Enabler Rollout – a phased approach User ProfileMessaging Voice/Call ChargingLocation Interaction Bulk Msg Status

BEA Confidential | 17 Network Connectors Service CapabilitySupported Protocols CallCall control: Parlay 3.3 (OSA rel 4) Multiparty call control: Parlay 3.3 (OSA rel 4) Charging Parlay 3.3 (OSA rel 4) Messaging CIMD2 Ericsson MM7 R2.0 MM7 rel 5 Nokia EAIF SMPP version 3.4 Parlay 3.3 (OSA rel 4) SMS and MMS User InteractionCall user interaction: Parlay 3.3 (OSA rel 4) Generic user interaction: CIMD2 SMPP version 3.4 Parlay 3.3 (OSA rel 4) User Location MLP (LIF) Parlay 3.3 (OSA rel 4) User Status Parlay 3.3 (OSA rel 4)

BEA Confidential | 18 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 19 Policy Based Execution RULE ENGINE Capabilities Network Plug-ins PROVISIONING SLA and SLEE Databases Rule Repository Access 2 2 The PEP provides the Rule Engine with information about the service request Based on the rule and the available data, the rule engine make a decision whether to allow the request or not The decision is then sent back to the PEP 1 1 A service request reaches a PEP in a Capability Module Service request from an application 3 3 The PEP enforces the decision made by the rule engine If the service request was allowed, the execution is continued Othervise, the execution is interrupted and an exception is sent to the application Network External Database Policy Execution Point (PEP) Service Request Data and rule provisioning

BEA Confidential | 20 Network Routing Extendable Web Services Parlay-X Web Services Capabilities Exposed traffic interfaces Web Service FW CORBA Java CORBA MMS-C NETWORK CAPABILITIES OSA GATEWAY Plug -ins Plug-in Manager … SMS-C Routing decision is based on: Matching plug-in type One type per plug-in Matching address plan Each plug-in can support a list of address plans Plug-ins that are severely overloaded are not used Address matched with configured routes Routes are configured using regular expressions (match or best match only) Policy filtering Round robin or weighted selection of plug-in to use SC Manager

BEA Confidential | 21 Service Level Agreements SP Group 2 SP Group 1 SP 1 SP 3 SP 2 APP Group 1 APP Group 2 App 1App 2 App 3App 4App 5App 6 BEA WebLogic Network Gatekeeper Network Adapters Telecom Web Services OSA GWMMSC SMSC Messaging Voice/Call Location … SP Group SLA App Group SLA SP Group Traffic SLA Total Traffic SLA

BEA Confidential | 22 Service Provider- and Application Group SLAs Per Service Provider- and Application Group: Capabilities allowed Start and end date Sub functionality within each allowed capability Maximum traffic allowed towards the WLNG Guaranteed traffic towards the WLNG Maximum number of Call Legs in each call Type of content allowed in messages.... SP Group 2 SP Group 1 SP 1SP 1 SP 3SP 3 SP 2SP 2 APP Group 1 APP Group 2 App 1App 2 App 3App 4App 5App 6 BEA WebLogic Network Gatekeeper Network Adapters Telecom Web Services OSA GW MMSC SMSC Messaging Voice/Call Location … SP Group Access SLA App Group Access SLA SP Group Traffic SLA Total Traffic SLA

BEA Confidential | 23 Service Provider Group Traffic SLAs SP Group 2 SP Group 1 SP 1SP 1 SP 3SP 3 SP 2SP 2 APP Group 1 APP Group 2 App 1App 2 App 3App 4App 5App 6 BEA WebLogic Network Gatekeeper Network Adapters Telecom Web Services OSA GW MMSC SMSC Messaging Voice/Call Location … SP Group Access SLA App Group Access SLA SP Group Traffic SLA Total Traffic SLA Per Service Provider Group: Permitted nodes Start and end date Maximum traffic allowed towards a specific node Maximum send list length towards a specific node...

BEA Confidential | 24 Total Traffic SLA SP Group 2 SP Group 1 SP 1SP 1 SP 3SP 3 SP 2SP 2 APP Group 1 APP Group 2 App 1App 2 App 3App 4App 5App 6 BEA WebLogic Network Gatekeeper Network Adapters Telecom Web Services OSA GW MMSC SMSC Messaging Voice/Call Location … SP Group Access SLA App Group Access SLA SP Group Traffic SLA Total Traffic SLA Controlling interface between WLNG and each network node Start and end date Total maximum traffic allowed towards a specific node from the WLNG Maximum send list length towards a node

BEA Confidential | 25 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 26 PRM Integration OSA GW NETWORK CAPABILITIES SMS-C MMS-C MM7 3 rd party service provider 1 Application 2 1 n 3 rd party service provider 2 Application 2 1 n 3 rd party service provider n Application 2 1 n MM7 node OSA/Parlay SMPP GW SMPP Subscribers Partners Self-Care PRM i/f Parlay X - Web Services interface Service Capabilities Application Enablers Network Adapters Charging & Billing PRM

BEA Confidential | 27 Partner Self-Care Sign upDownload Develop TestRegister applicationMonitor

BEA Confidential | 28 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 29 The Equation In-house development Establish Platform and Tools Plan, Budget, Recruit, Train Develop Application Verify Application Integrate Application Deploy Service Manage Service Bill Service Reward Staff Manage Staff Manage Customers Manage Platform With 3 rd Parties Establish Platform and Tools Build, Leverage Partners Develop Applications Verify Applications Integrate Applications Deploy Services Manage Services Bill Services Reward Partners Manage Partners Manage Customers Manage Platform

BEA Confidential | 30 Business Aspects Accuracy - the basic enablers are EDRs collected in one or multiple nodes Many types of partner business models. From simple pre- paid allotments to flexible revenues share schemes Deliver first, then charge. Annoyance factors. Restrict and verify billing codes – costly to repair. Reconciliation with small partners requires same amount of handling (human resources) as with big partners. If avoided by outsourcing you may loose monitoring and control. Margins are low for established content labels – now pushing for 70% – need to break the hegemony

BEA Confidential | 31 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 32 Leverage Mature Industry Standards Telecom Web Services, SIP, J2EE. 1 Benefit from Unique WLCP Strengths Combined value of Telecom Web Services, Network Access Management & IMS Application Platform. 2 Launch New Services Now! Use BEA WebLogic SIP Server and BEA WebLogic Network Gatekeeper for next-gen service delivery. 3 SUMMARY Monetize 3 rd Party Providers Now! Use BEA WebLogic Network Gatekeeper to securely, and scalably manage 3 rd party network access. 4

BEA Confidential | 33 Agenda Telecom Industry Challenges What is Parlay & Telecom Web Services BEA WebLogic Network Gatekeeper Policy Enforced Network Access Control 3rd Party Partner Relationship Management Flexible Billing & Charging Why BEA WebLogic Network Gatekeeper Key Use Cases

BEA Confidential | 34 Customer Case One Situation Wanted to open up network capabilities for third parties using open interfaces Wanted to standardize the access into their network for third parties, and decided on web services and Parlay X Wanted to start with SMS capability, then add MMS, then call control A fundamental requirement was to protect both network nodes and subscribers Solution Integration in 4 weeks on Parlay Gwy and SMSC Open interfaces provided based on Parlay X High flexibility to protect network and subscribers based on policy rules Business rules tailored according to the requirements of the marketing department Off-the-shelf adapters to plug into existing network infrastructure, subscriber DB

BEA Confidential | 35 Customer Case Two Situation Home-made SDP solution Limited messaging support (except simple SMS) and no billing integration Lacking bulk capacity for SMS and MMS No standard interfaces for third party access No real-time SLA enforcement Marketing requirements were not met by current systems Solution Support for location, bulk messaging and advanced subscriber services based on standard interfaces e.g. Parlay X Support for Parlay X, MM7, SMPP and CIMD2 northbound Support for MM7, SMPP, CIMD2 and SS7 southbound Partner Relationship Management. Integrated with network elements Policy based access control and SLA enforcement

BEA Confidential | 36 Customer Case Three Situation In-house pre-SDP solution with multiple external partners Basic messaging and billing support Lacking single access control layer, multiple stove pipes No real-time SLA enforcement Wanted to launch new breath of services, aggressive timescales Wanted to add new enablers in a phased approach Wanted an open, flexible system with all x-abilities Network agnostic approach Solution Support for location, messaging, charging and advanced subscriber services based on open interfaces Portal for partner self-care and partner relationship management Partner Relationship Management integrated with multiple network elements Network protection with advanced routing mechanisms Policy based real time SLA enforcement and access control

BEA Confidential | 38 Security… Security Provided by WebLogic Network Gatekeeper: Identification and Authentication Web Services using Kerberos type service-token based authentication Authorization and Service Access Web Service sessions are verified against service session restrictions specified in the application instance group SLA Integrity and Confidentiality Secure communications can be achieved using SSL or VPN between firewalls

BEA Confidential | 39 …Security Auditing and Non-Repudiation All successful and unsuccessful access attempts are written to the event log with all transactions being stored as CDRs (Charging Data Records) in the database Network Authentication If the underlying network nodes provide authentication interfaces, the WLNG Plug-ins can authenticate with them Database Security All sensitive data such as usernames, passwords, certificates and private-keys are encrypted before storage in the database The Database is protected by host address, username and password combinations SLEE Service users only have access to the database tables that are related to that particular Service Management Security Usernames and passwords are encrypted before storage in the database

BEA Confidential | 40 WebLogic Communications Platform: Telecom Web Services - Network View OSS Network Element Management BSS Provisioning System Charging Functions VASP or Enterprise SNMP RADIUS DIAMETER (Ro/Rf) LDAP (or XCAP, CAI3G, etc.) MAP Sh/Dh HSS(+SLF)/HLRAAAMass Storage WLCP Border Gateway FTP/SFTP Pr HTTP (SOAP, etc.) SMSCMMSC Wireless Village MPC Parlay/OSA gateway IMS Core and Enablers SIP (ISC) HTTP (Ut) DIAMETER (Sh/Dh) CORBALIF/MLP SMPP MM7 SSP/CSP WLES