services for ngn 34td081 paul sijben [email protected]
TRANSCRIPT
2 (C) 2003 Paul Sijben, [email protected]
NGN Services
• Goal:commercial interoperable telecom services
• Observation– Flashy websites make no money– Incumbents are hesitant to become “mere”
bit transporters
• Which services can be provided to make profit?
• What is needed to do so?
3 (C) 2003 Paul Sijben, [email protected]
Which services?
Transport Services
ConnectivityServices
ApplicationServices
•Services provide higher margin but high risk of failure.•Transport provide lower margin but more reliable volume
Volume
Small
Large
Risk & Margin
Low
High
4 (C) 2003 Paul Sijben, [email protected]
Transport services
• Transport flows for media and signalling• QoS aware
– it can be delivered when needed– QoS parameters requested by application
• Services that require QoS do so end-to-end– Public transport services support QoS– Home/enterprise network support QoS
• Access control• Usage reporting facility• Location reporting facility• Mostly standardized
– Free for all in the home & enterprise
5 (C) 2003 Paul Sijben, [email protected]
Connectivity Services
• Plain multimedia sessions between users at terminals– Telephony call is a simple type of a
multimedia session
• Media may encompass – Narrowband audio– Broadband audio– Messaging– Shared applications
• Fairly Standardized
6 (C) 2003 Paul Sijben, [email protected]
Application Services
• User mobility• Conferencing• Instant messaging• E-commerce• Video on Demand• Location aware services
• Not effectively standardized– Unique services to attract users– Created for potentially small groups
7 (C) 2003 Paul Sijben, [email protected]
Services Scenario
• John is an end-user
• John’s company provides John with communication services under identities [email protected], and +31 1234567890
• John has a contract with TurtleTelecom for his personal communication under identity +31 9876543210
8 (C) 2003 Paul Sijben, [email protected]
John’s telecom dashboard
Hi John, please enter your password for access to your services **********
9 (C) 2003 Paul Sijben, [email protected]
John’s telecom dashboard
CallsPersonal:
3 new voicemail, 1 new video messageBusiness:
10 new voicemail , 3 video messages
MessagingPersonal: 4 unread emails, 2 short messagesBusiness: 22 unread emails, 1 short message
PresencePersonal: 3 friends on-lineBusiness: 0 team members on-line
Wallet
Web
Media
10 (C) 2003 Paul Sijben, [email protected]
Scenario
• John checks his messages. • There is a message from Jane in
Engineering about the project they are working on
• John places a phone (audio) call to Jane expecting it will be a short call
• The situation is more complicated and they add a video link to the call so they can communicate better
• Jane feels the need to draw something for John and to conference in Fred and Alice
11 (C) 2003 Paul Sijben, [email protected]
This is NOW
• Multi-service Terminal • ONE network connection• Terminal integrates view on multiple
accounts• Service provider creates new services
Terminal is service agnostic
• Terminal can be built TODAY• Public network is not up to it
– Customer premises network usually neither but has bandwidth in abundance
12 (C) 2003 Paul Sijben, [email protected]
Conclusion• Flashy services are built out of “dull” components• TISPAN should create benchmark flashy service
descriptions– No need to implement all of them!– Will show us which base components are needed– Describe service aspects end-to-end
• Enable service construction– Cheaply build new services from base deployment– Standards required for use and interconnection of all supported
services. • Vertical: Transport & Connectivity• Horizontal: Transport, Connectivity, Application
– Service capabilities provide the right granularity• Note:Not all capabilities may need to be provided to all parties at the
same price
• Do not stifle innovation, do not standardize too much!