Technology Trials: Experience & Findings

© eircom

Brendan Kearns

Eircom, bkearns@eircom.ie

Wednesday 24th November

ETSI IMS Implementation Workshop

Contents of the Presentation

© eircom

Trials should find platforms / vendors that can be configured to support products that are relevant to

the current marketplace and are aligned with company strategy

© eircom

company strategy

Powerpoint cannot take us all the way

Deploy Relevant Products

Engineer CreatesProduct

The way it was The way it is

© eircom

CustomerHad Little Choice

But to Buy

Customer Choice Leads to Survival of the Most

Relevant Service

Difficult For Operator to Determine In Advance

Relevance of a Product

Trials Play A Part

Product Development & Trials

General drift of technology & customer expectations

Vendors & Operators Drive New Standards

vendors realise standards & pitch to operators

Commercial strategy informs CTO technology strategy

CTO evaluate technology platforms

© eircom

Operators enter RFP process

Operator choose vendor

Operator deploys new platform

Operator deploy new products

CTO evaluate technology platforms

Proof of Concept, Demonstration, Product Development

Commercial Pilot

Scope - Success Factors - People

Trial of the Platform

Hands On Experience

Prove Platform & Fit

Operator or Vendor Lab

Trial of the Product

Create Product in Lab

Platform Configuration

Tech Service Description

Commercial Pilot

Provisioning / Charging

Operating Fault Procedures

Deployment Procedures

Technology Strategy ValidatedTeam Capable of Evaluation

Tech Product DescriptionAugment Business Case

Validate Deployment StrategyValidate Processes

© eircom

Team Capable of Evaluation Augment Business Case Validate ProcessesPeople Training

Responsible for setting the architecture, picking the vendor and proving the platform

Network Architect

Could be company staff for a technology trial, friendly customers or paying customers for a commercial pilot.

Trialists

Responsible for configuring the platform to realise product and to add on provisioning, charging,

capabilities to build complete end to end product.

Product Development

Our ability to innovate is enhanced by working with external groups who bring another perspective.

Trial Partners

Responsible for operating and Maintaining the Product.

Operations

Responsible for picking trialists, structure of feedback, analysis of feedback, concluding on

the likely takup of the product.

Customer Insight

Case Study: Add if Required

© eircom

Eircom NGIN Tender

NGIN Case StudySummary

• Platform & Vendor Evaluation

• Hands On JAIN SLEE

• Demonstration of New Capabilities• Single JAIN SLEE Application triggered by Multiple Access Networks

• Integration With Web API’s

• Proof of Concept

© eircom

• Proof of Concept• Converged Application “Mobile Anywhere”

• Voice Call – IM – Calender Integration

• Voice Call – IM – Google Maps Integration

NGIN Case StudyWhat Was Done

Mgmt LAN

Provisioning / Cust. Care

NGINWeb Control

SOAP / XMLWeb 2.0 Applications

Buddy FinderPersonalised Call Back Network

Applications

INAP

SIP

© eircom

CAMEL

‘NGIN’ integrated to fixed, mobile and IMS plus Web 2.0

SSP

PSTN

Mobile

IMS / VoIP

Eircom / Meteor Live networks

Laboratory

INAP

NGIN Case StudyOutcome

• Commercial engagement from beginning

• Strong fundamental business case

• Demonstrations augmented business case

• Platform now in deployment

© eircom

Case Study

© eircom

Eircom RCS Trial

RCS Case Study: Objectives

© eircom

Address

BookPresence

Messaging Media

Share

Community & Social Networks Aggregator

[API Integration]

RCS Case StudyWhat Was Done

App Servers

Web Gateway

FB / G Integration

© eircom

IMS

MobileRCS

Client

RCS Web Client

RCS / Facebook

RCS / Google

3 Access Networks: RAN, Internet & Corporate WAN

BroadbandRCS

Client

Initial Filter Criteria

SBC

IP Firewalling

Client Config

Client XML

Client Rebuild

RAN

RCS Case Study: Team Cannot Configure Some elements

App Servers: Configured by IMS Vendor

Web Gateway: Configured by IMS Vendor

FaceBook / Google Integration: by Feedhenry & Solames

Could be configured by the team

Could not be configured

by the team:

© eircom

Initial Filter Criteria: Configured by ALU & Edited by eircom

SBC: Configured by ACME & Edited by eircom

IP Firewalling: Configured by other eircom groups

Client Config: 1st stop to resolve incompatibilities

Client XML: 2nd stop to resolve client incompatibilities

Client Rebuild

RAN: Configured by eircom but some functions not accessible

by the team: under

control of external

resources.This can

create delay.

Case Study: CommentsRich Communication Suite

• Some Technical Findings• IMS: Stable and Ready For Deployment

• Acceptance Testing: Manual test case implementation is cumbersome

• Client Side: Primacy of the User Interface

• Mobile and Broadband clients from the same vendor preferable

• Server Side: Layer 3/4 firewalling and session border control implementation should be combined

• Deployment Capability: Sweep of the technology makes this Technically Challenging

© eircom

Conclusion

© eircom

General Observations From Working on Trials

• Get Support & Participation from Commercial Colleagues

• Trial split into topics each with one person responsible

• Identify what cannot be configured by team members

• Innovation comes from 3rd parties

• Trial description document becomes the final report

Some General Conclusions

© eircom

• Formulate efficient testing strategy to include IOT with 3rd parties

• Demonstrations should have “WOW” factor

• Short high profile trials are more efficient

• Results of user trial is the dominant perspective on the full trial

• Align timing with market

Q&A

© eircom

Brendan Kearns

bkearns@eircom.ie