Telecommunications Information Networking Architecture (TINA)

1. Telecommunications Information Networking Architecture (TINA) Presented by: Sudip Misra E-mail: sudip_misra@yahoo.com Phone#: (613)228-5217

2. Agenda • Background • What is TINA? • Goals of TINA • Applicability of TINA • TINA Architectural Principles • Layered Architecture • Architectural Model

3. Agenda (Contd.) • Computing Architecture • Service Architecture • Network Architecture • Management Architecture • Security Domain in TINA • TINA Compliance • TINA products • Conclusions • References

4. Background • Internet is a key component in the multimedia age. • The intelligence in modern internet lies mainly in the end-systems. • Whereas, the intelligence in traditional telecom systems lies in the network.

5. Background (Contd.) • Modern Internet = More Computational Power • Traditional Telecom Networks = High reliability, security, QoS, etc. • How would it be with the convergence of both?  Versatile Multimedia and Information Services = (High Computational Intelligence) + (High Security, reliability, QoS).

6. What is TINA? • Defines an open and comprehensive architecture, that integrates the two technologies and capitalizes on other recent advances in computer and telecommunications technologies to support the deployment of new multi-service networks that will support multimedia services [12] . • TINA is a consortium of over forty companies, which include, public network operators, telecommunications equipment suppliers, and telecommunications research organizations [6]. • An example of TINA based product is from Starvision

7. Goals of TINA • Aim: Provide a common architecture on which new services can be built. • What problems does it solve?  New service deployment.  Interoperability between systems from different vendors. • 3 Major Goals: 1. To provide versatile multimedia and information services 2. Make it easy to create new services and to manage services and networks 3. Create an open telecommunications and information software component marketplace .

8. Applicability of TINA • The intention of TINA is to apply it to all parts of telecommunication and information systems:  Terminals (computers, etc),  Transport servers (switches, routers, etc),  Service servers (web, etc), and  Management servers (authentication, billing, etc).

9. TINA Architectural Principles • Based on fourprinciples, that ensures interoperability, portability and reusability of software components and independence from specific technologies [1, 12, 13]: 1. Object-Oriented Analysis and Design: Breaks system down into a set of interacting models. 2. Distribution: Helps in breaking service software components into different parts over the network to accommodate traffic characteristics, network load, survivability and customer demand.

10. TINA Architectural Principles (Contd.) 3. Decoupling of software components. This ensures that a change in one component due to a change in technology does not affect other components. 4. Separation of concern between parts of the system: Two major separation of concerns (Figure 1):  Between applications and the environment (i.e. DPE), on which they are run, and  Separation of applications into the service-specific part and the generic management and control part.

11. Layered Architecture TINA is a 4-layered architecture: • Hardware Layer: Processors, memory, communication devices. • Software Layer: Operating Systems, Communications and other support software (NCCE). • DPE layer: Distributed execution of telecommunications applications. • Telecommunications applications layer: Implements capabilities provided by the system. (Figure adapted from [13])

12. Architectural Model • According to the separation of concerns, TINA is divided into the following sub-architectures:  Computing Architecture.  Service Architecture.  Network Architecture.  Management Architecture.

13. Architectural Model (Contd.)

14. Computing Architecture (CA) • Defines object-oriented modeling concepts and the DPE. • CA provides three viewpoints & modeling concepts (VP & M): Information VP&M Computation VP&M  Engineering VP&M.

15. Computing Architecture (Contd.) • Information VP&M:  Describes the following concepts: -- Information objects - information bearing entities. -- Object types - classifications of information objects. -- Relationships between entities. -- Constraints and rules that govern their behavior. • Computational VP&M:  Describes computational objects and their relations  Computational objects are units of programming interacting by communication through interface.

16. Computing Architecture (Contd.) • Engineering VP&M:  Describes the organization of an abstract infrastructure required to support distribution called the DPE (Distributed Processing Environment).  Engineering Modeling Concepts include: -- DPE Kernel - provides support to object-life-cycle control and inter-object communication. -- Kernel Transport Network (KTN) - provides a technology-independent view of the communication facilities provided by the NCCEs of the DPE nodes. -- DPE Services - provide operational I/F to support the run-time execution and communication of objects.

17. Service Architecture • The Service Architecture defines a set of principles for providing services. • Session concepts help in providing service information specification:  Access Session: A user runs it to access a service.  Service Session: Provides an environment for execution of a service.  User Session: activities performed and the resources allocated by one user for one specific service session.  Communication Session: Supports activities needed to support communication between users.

18. Service Architecture: TINA Sessions

19. Service Architecture (Contd.) • Generic Access Information Model. • Access Scenario: 1) First, a terminal is recognized and associated to a network access point. 2) Second, user identified through the appropriated registration procedures, 3) Next, the user is associated to terminal(s), and 4) Eventually, the user can access to a set of executable services or existing sessions.

20. Network Architecture • Generic concepts to describe transport networks in a technology independent way. • Establishment, modification and release of connections. • Defined using ITU-T recommendations: G.803, M3100. • Major Concepts:  Partitioning: into sub-networks and links between them.  Layering: A set of layered networks.

21. Management Architecture • Defines a set of concepts and principles for software systems that manage services, resources, software, and underlying technology. • Management Activities:  Telecommunications Management: Management of telecom services and underlying networks.  Computing Management: Management of computers, platforms, and the DPE on which TINA runs.  Software Management  DPE Management  Computing Environment Management.  Kernel Transport Network Management.

22. Management Architecture (Contd.) • Management in the Service Architecture focuses on the Service Management Layer (SML); • Management in the Network Architecture comprises Network and Network Element Management Layers (NML and EML); • Management in Computing Architecture does not conform with TMN layering

23. Security Domain in TINA • Because of its distributed computing environment, TINA products are vulnerable to security violation. • TINA Security requirements in four areas:  Telecom systems and service.  Management systems.  DPE security and DPE security services.  Security Management (Please see notes for details).

24. TINA Compliance • The compliance to the TINA concepts and principles can broadly be classified to be in either of two types: • External: Any system based on TINA should apply architectural concepts and principles to design, specification and implementation. • Internal: Internal compliance concepts and principles are normally used and applied by TINA consortium and their use for others is entirely optional.

25. TINA Products • Two categories:  Products and Implementations (DPEs, tools, servers, open switches, and so on), e.g., Starvision is a first example.  Service offerings which have (visibly or invisibly) "TINA inside" .

26. Conclusions • TINA proposes solutions for the future evolution of IN. • TINA Service Composition Architecture is helpful for rapid deployment of new services. • TINA security management is a key issue because of greater vulnerability to security violation because of its distributed nature.

27. References [1] W.J. Barr, T. Boyd, Y, Inoue, “The TINA initiative”, IEEE Communications Magazine, Vol. 31, Issue 3, pp. 70-76, 1993.  [2] M. Born, R. Fischer, M. Von Lowis, D. Kruger, C. Ulbricht, “Service Composition in a TINA Environment”, Proceedings of TINA’99, pp. 180-182, 1999.  [3] L. M. Cacares, W.T. Watanabe, C.B. WestPhall, A. Sekkaki, “Development of Prototype based on TINA Accounting and Service Management Architecture”, Proceedings of XXI International Conference of the Chilean Computer Science Society, pp. 50-57, 2001.  [4] F.J. Carrasco, J. Esteve, M. Felipe, J.C. Garcia, “Applying CORBA Technology for the implementation of a TINA service”, Global Telecommunications Perspective, GLOBECOM’96, vol. 1, pp.57-62, 1996.  [5] P. Hellemans, H. Vanderstraeten, J.C. Yelmo, J. Villamor, P. Lago, G. Canal, “TINA Service Architecture: For Specification to Implementation”, Proceedings of TINA’97 Conference, pp. 174-183, 1997.  [6] Y. Inoue, D. Cuha, H. Berndt, “The TINA Consortium”, IEEE Communications Magazine, pp. 130-136, Vol. 36, Issue 9, 1998.  [7] M. Kihl, C. Nyberg, H. Warne, P. Wollinger, “Performance simulation of a TINA Network”, Golobal Telecommunications Conference, GLOBECOM’97, vol. 3, pp.1567-1571, 1997. [8] M. Mampaey, A. Couturier, “Using TINA Concepts for IN evolution”, IEEE Communications Magazine, Vol. 38, Issue 6, pp. 94-99, 2000.  [9] P. Richardson, “Integrating network and operations – A TINA Perspective”, Region 10 International Conference on Technology Enabling Tomorrow: Computers, Communications and Automation towards the 21st Century, pp 207-211, vol. 1, 1992.

28. References (Contd.) [10] C. Smith, “Applying TINA-C service architecture to the intranets and internet”, Proceedings of TINA ’97 Conference, pp. 4-12, 1997. [11] P. Vickers, R. Cole, “The role of TINA in telecomms revolution”, IEE Third Tutorial Seminar on The Intelligent Network - The Next Generation, pp. 4/1-4/4, 1995. [12] The TINA Consortium Web Page, http://www.tinac.com [13] http://hagel.ittc.ukans.edu/projects/tina-c/ [14] www.omg.org/news/about/liaison.htm [15] http://www.objs.com/workshops/ws9801/papers/paper035.html [16] http://www.tid.es/presencia/publicaciones/comsid/ing/articulos/vol71/tinac/tinac.html