Extensible Transport Framework Telecom use case

1
Extensible Transport FrameworkTelecom use case

• One ORB does not fit all telecom needs
• Embedded, real-time, generic, cheap (free), ...
• A telecom framework is composed of several
  inter-operating ORBs.
• E.g. Network management is an end to end problem
• Requirements for large amount of transport
  protocols
• depending to the context, hardware QoS,
  acceptable application requirements, legacy
  protocols
• Requirement for specific, proprietary, private
  transport protocol
• product added value, security, ...

2
One ORB does not fit all telecom needs

• Embedded
• Generic
• Free
• Open Source

• Real-time

3
A telecom frameworkSeveral inter-operable ORBs
End to end solution
4
Public and wide spread protocol needs

• For particular telecom architecture or technology
• telecom architecture SS7/SCCP, B-ISDN, GSM/UMTS,
  Internet
• technology ATM, IP, Frame relay, ADSL/XDSL
• Specific protocols for application context
  dependent
• Reliability
• ALF/UDP (Connection oriented UDP with ack),
• SCTP/UDP (SS7 reliability on IP)
• Efficiency
• VIA (max use of bandwidth)
• Alternative to the RFP
  Standardise theses protocols?

5
Specific or private/proprietary protocol needs

• Protocol specific to an hardware context
• Ethernet level
• Optic level (WDM)
• Private protocols for added value
• Private Network protocols
• Legacy systems
• Specific product hardware
• Non public protocol for security reasons
• non public algorithms

6
Extensible Transport Framework

• Large amount of protocols
• Specific non public protocol
• Money In some cases, need for inexpensive
  protocols
• to sell millions of product units
• Need for standardisation