200 likes | 319 Views
fmc services and billing. agenda. TILAB and its role in italian context choices available for fixed, mobile and integrated operators the best position various routes to full fixed-mobile convergence trends, initiatives... service layer as a key point
E N D
agenda • TILAB and its role in italian context • choices available for fixed, mobile and integrated operators • the best position • various routes to full fixed-mobile convergence • trends, initiatives... • service layer as a key point • new services to be invented and deployed • which is the best choice? • management & billing • consequences • requirements • opportunities • legacy and new architectures BUT from the services perspective... not from the point of view of an expert on billing...
Italian market trends (excerpt from: M.Tronchetti Provera, Meeting with the Financial Community 2005 )
Different roles for a TLC Operator • Fixed operator • defensive position • vs traffic erosion and substitution • leverage on indoor services, BB and VAS • Mobile operator • current aggressive/expansive position • risk of saturation for GSM? • 3G ? • Fixed AND mobile operator • advantages of both operators • trends of the market • savings & optimisations BEST POSITION...
The Telecom Italia Network Model(excerpt from: S. Pileri, Piattaforme abilitanti ed evoluzione della Rete – Notiziario Tecnico Telecom Italia, #1, 2004, pg11-19) Cost Efficiency Focus Service Mgmt Platform Voice Voice & Video Telephony Services Optical Packet Backbone Wired Access Data Data Communication Services Wireless Access Video Content Delivery Services Revenue Generation Focus
Different convergences • service execution/delivery • SDP • web services • OSA... • service creation • fast prototyping • test and trial approach • shorter time to market • terminal • multiradio terminals • fixed/mobile network indipendence • network control • IMS • SIP • management/logistic • single billing • unified customer care/complaints • operations & maintenance • informative services... etc (UMA,FMCA) (TISPAN, 3GPP) SERVICE LAYER
TI convergent services portfolio 2007(excerpt from: M.Tronchetti Provera, Meeting with the Financial Community 2005 )
Another view about convergent services many families: • voice (VoIP, VoWLAN etc) • video/multimedia • SWIS • combinational • SMS activated • personal communication • mobile office • security based • localisation/context awareness • .... • BUT THESE ARE ONLY FEW EXAMPLES... • for each family which is the best implementation? • how to choose most interesting features without a crystall ball? • how to fast prototype and test ? • ...
SCE as a key tool • for fastening development/ simulation/ deployment/ provisioning phases • for controlling the whole service life cycle • for separating service and execution/network layers: bigger indipendence from vendors
STARSLEE & STARSCE: the TILAB tools • developed by TILAB on the base of StarSIP, the Telecom Italia reference SIP platform • used by all the research project in TILAB involved in innnovative next generation services creation and trials Service Creation Environment
Some convergent features... • from the point of view of the customer it should be fine to have: • one brand • one catalogue • one contact point for • buying • complaining • signalling problems • changing some configuration • ... • one bill • ex-post “cross” billing • pre-paid tools • one authentication method CONSEQUENCE NEW REQUIREMENTS IN PARTICULAR FOR BILLING PROCEDURES/ ARCHITECTURES
BUT from the operational point of view... • all the traditional FCAPS functional area have to be involved by convergence: • fault • provisioning • accounting • performance/QoS • security CUSTOMER NEEDS OPERATOR SAVINGS AND OPERATIONAL OPTIMISATION
Savings expected from convergence optimisation...(excerpt from: M.Tronchetti Provera, Meeting with the Financial Community 2005 )
Some additional requirements in the next generation services area... • flexibility in the set up of new services metaphors • application to person • person to person • rich messaging • session based services • fixed-mobile roaming • contents • ... • real time QoS delivery vs real time billing • flexible billing policies (not only flat policies) • pre-paid policy vs subscription • event based billing • content based vs volume based • horizontal platform vs vertical platforms • independence between CDR production and (legacy?) billing systems • ... ...each point can be seen as an opportunity or as a threat...
... And a question... • which are the real products/services to be sold by the TLC operator? • the connectivity (bandwidth/time/bits...) • with QoS • with the knowledge of what is transmitted (attention to p2p!!!) • the contents • some security items (authentication as a product?) • brokerage of the services for third parties • value added and classical services/applications (usual role) • The answer is: probably everything... and now... • But is the BSS architecture adequate to those purposes?
Some conclusions and suggestions... • legacy systems to be taken into account • flexibility and openness as key attributes for the BSS • avoid vertical solutions and prefer horizontal platforms • pre-paid lesson from mobile experience to be exploited in the convergent arena • OSS architectures to be reviewed on the basis of a deep operational processes revision • opportunities of using convergent billing for selling “other” stuff in addition to the traditional items • if an opportunity is not exploited it can become a threat....