Transcript TINA-C Organization (until 1997)

@ Forces
John Evans
BT Angel Centre,
5th Feb. '99
TINA-C Organization (until 1997)
TINA Conference
Sc.Committee
Consortium
Technical
Committee
AD HOC
Teams
Management
Consortium
Steering
Board
Integration
Services
Resources
Validation
RFR/S Process
Review
Board
(RFR/S)
Core Team
Auxiliary
Projects
More than 30 permanent
people in Red Bank (NJ)
(in member
companies)
From 1993 to end 1997
Timeline
Architecture focused
1993
Product focused
1997
Core Team work
Architecture
Issue 1
Revision
Revision
Issue 4
Issue 2
Issue 3
(Architecture issues)
Final
2000
Phase 2
new
process
Validation etc....
Auxiliary
Projects
Telecom’95
Worldwide Demonstrations
The TINA Trial
TINA-C Organization
• Technical leadership
• Liaison among
members and industries
• Administration
FORUM
Board of Directors
Consortium
Administration
Office
TINA
Architecture
Board
Working Groups
• Driving force for assigned
subjects
• Coordinated by TAB
• Approved by Forum
• Cooperate with members,
industries and academies
• All decisions (including Email based decisions with
the time limit)
• One vote per company
• Technical + Strategic
meetings
• Including manufactures
• Advisor role
Special Interest Groups
• Driving force for establishing new directions
• Coordinated by TAB
• Approved by Forum
• Cooperate with members, industries and
academies
TINA-C Members
Alcatel
AT&T
Bellcore,
British Telecom
Broadcom
Cable and Wireless
Cegetel
Center for
Development
Telematics, India
CSELT
Deutsche Telekom
Digital/Tandem
ETRI, Korea
EURESCOM
France Telecom
Fujitsu
FUB, Italy
GPT
Hitachi
HP
IBM
Iona
Korea Telecom
KPN
Lucent
Siemens
Sun Microsystem
Sprint
Stentor
Swisscom
Tadiran Telecom
Tele Danmark
Telia
Telnor
8
Telstra
Telesys Software
Telecom Portugal
TINA Inf. Ind. China
Toshiba
MCI
Mitsubishi
NTT
NEC
Nortel
OKI
University of Chile
Humboldt
University
GMD Fokus
Objectives of new TINA-C



Adoption of TINA architecture and specifications to
industry products
– Seamless services by federating heterogeneous
existing systems/networks
– Modular-based extension or replacement of
existing software infrastructure/systems
Demonstrate the benefits of TINA adoption as
platform for advanced services
Completing some specifications and refinement of
architecture (e.g.reference points)
TINA-C membership type

Full members (with voting right)

Associate members (no voting right)

Plus:
 Membership arrangements for academic
institutions to facilitate research interactions
New TINA-C Structure



A registered corporation (like ATMF, OMG, NMF.)
Filed for Non-Profit Status
Salaried
 Chief Executive Officer :Deb Ghua
([email protected])
 Chief Technology Officer:Hendrik Berndt
([email protected])
Independent Central Office Space
Architecture Overview
TINA
Overall Architecture
Network
Resource
Architecture
Network Resource
Model
Service
Architecture
Session Model
Subscription
Model
Computing
Architecture
DPE
Architecture
Management
Architecture
Configuration
Management
Fault
Management
Relations to standardization
DAVIC
•Architecture
Separations
•Session Concept
ITU-T
SG-10
ATM-F
ITEF W3C
•Third party control
•Object groups
•Stream binding •M4 network model
•ODL
•QoS
•Session Concept
•QoS
•Accounting
•ODL
•CMC
IMA
TINA
SG-15
SG-11
OMG
•NRIM
•Session Concept
•Third party control
•Connection Graphs
NMF
Open Group
•application of
viewpoints
ODP
ODMA
Major Achievements




Huge set of specifications and methodologies (Service
Architecture, Computing Architecture, Resource
Management Architecture): more than 25 deliverables!
TINA-C Worldwide demos: starting at Telecom 95
Four main TINA TRIALS (NTT&Others, Global One,
Safari, P715)
TINA-C awareness worldwide
and
 TINA is now moving from specs to products and
services!
Expected Results (1998+)
A more simple and complete
Architecture
Simplified
Profiles: e.g. for Reference Points
Shortcuts: e.g. for QoS framework
More complete
Reference Points: RtR, 3Pty, LNFed
Service Management Framework
Integrated with more legacy systems
Specifications/ standards for gateways/adaptation
units
Deliverables (1998+)

Simplify:
– Ret, ConS, Tcon
– DPE Architecture, SA, NRA
– Service Component Specifications ,
Network Component Specifications
 Create:
– RtR, 3Pty, Service Management
Specifications, ...
Active Working Groups
 Applications of TINA
 Service Management
 TINA - IN
 Next Generation Mobility
 Service Architecture Reference
Points
 Naming and Addressing Framework
 Compliance Framework
 DPE Architecture
 Security
Possible new Working Groups
– Network Architecture Reference Points needed for evolution of RPs (or NRA)
– TINA and mobile and intelligent Agents
– others
Some WG details: TINA-IN-WG

Goals:
– Business case identification for IN to TINA
migration
 New services, or existing services migration
 Web and IN convergence (service interaction, IN
service customization and management using
Web access)
 IN-CTI convergence
– Application of TINA principles and concepts to IN
evolution
 Map TINA access, usage & communication
sessions to IN
 TINA Triggering & Connection mangmt for IN
 Impact on the design of IN architecture elements
(SCP, IP, ...)
Some WG details: SARP WG

Goals:
– To specify and maintain the reference points in the
scope of Service Architecture
 Inter domain RPs: Ret, RtR, 3Pty (Brk)
 Intra domain RPs: Access/Usage Split
– Update related architecture documents/service
component specs or provide addenda
Some WG details: Mobility WG


Goals:
– to complete TINA so that mobility is supported
intrinsically in the architecture;
– to provide migration paths to TINArize existing
mobile systems
Ongoing Activities:
– Handover support;
– Service Management for UMTS;
– Personal Mobility support;
– Modifications to the Business Model
– DPE support of Terminal Mobility
Some WG details: DPE










Goals: Maintain the TINA DPE Architecture
Provide a focal point for requirements on TINA
middleware
Influence the OMG with these requirements
Influence other (i.e. ITU-T) standards bodies
Ensure interoperability between DPE nodes (Kernel
Transport Network)
Study interworking issues with other distribution
technologies, as far as the middleware level is
concerned (Internet, OSI, TMN ...)
DPE Quality of Service Framework
Scalability and DPE profiling
Fault Tolerance, Mobility Support
Application Engineering support
Some WG details: Service Management
 Focus
–
–
–
–
–
–
on FCAPS
Fault
Configuration
Accounting
Performance ( service quality in TINA)
Security (collaboration with DPE)
Subscription
 Outputs
– The next version of SCS, RP specs.
Some WG details: Naming & Addressing

Goals:
To define a common Naming Framework that
may be applied by the various demonstrations of
The TINA Trial (TTT) whenever they want to
interoperate with another TTT demonstration.

To underline what changes have to be made to
the current "TINA Naming Framework" document,
version 0.2 to make it acceptable as a TINA-C
Baseline.
Some WG details: Application WG
 Goal: To define a minimum and sufficient set of
“proven” specifications to realize a small number
of services
– The specification will be “proven” with (pre-)products
that work and (trial or commercial) services that are
provided to customers/* not just paper exercises nor toy
prototypes */
– Target services include:
 Retail service for digital publishers and/or digital
libraries
– navigation for content selection
– delivery of contents (archived information)
with/without copyright to a large number of
customers with/without network QoS
ITS’98 Sao Paulo, Brazil Hendrik Berndt
08/09/98
CTO TINA-C
116
TINA-C Business Model
Broker
Bkr
Consumer
Bkr
Ret
Bkr
Bkr
3Pty
Retailer
3pty Service
Provider
RtR
TCon
TCon
ConS
ConS
Connectivity
Provider
CSLN
LNFed
Bkr
3Pty
TCon
Acronyms
CO
CORBA
DPE
IDL
IOP
kTN
NCCE
ODP
ODL
OMG
PA
RFR/S
TINA-C
TN
UA
UAP
Computational Objects (Elements of the Computational Model)
Common Object Request Broker Architecture (The OMG Architecture)
Distributed Processing Environment
Interface Description Language OMG Standard
Inter ORB Protocol
Kernel Transport Network (used to support Computational interactions
e.g. for control purposes)
Native Communication and Computing Environment
Open Distributed Processing (ISO Standard)
Object Definition Language (IDL extension to describe TINA objects)
Object Management Group
Provider Agent (Counterpart of UA in the User/provider relationship)
Requests for Refinement and Solutions (TINA-C new process)
Telecommunication Information Networking Architecture (Consortium)
Transport Network (used to support stream interactions e.g. to support
end-user data)
User Agent (Counterpart of PA in the User/provider relationship)
User Application