Telecommunications Platform SIG
Industry Links:
Meetings:
Minutes from Telecom Platfom SIG meetings
Minutes from Telecom Domain Task Force meetings:
Minutes
of the Anaheim meeting, February 2004,
telecom/04-02-01
Minutes
of the London meeting, November 2003,
telecom/03-11-02
Minutes
of the Boston meeting, September 2003,
telecom/03-09-01
Minutes
of the Paris meeting, June 2003, telecom/03-06-01
Minutes
of the Orlando meeting, March 2003, telecom/03-03-05
Minutes
of the Burlingame meeting, January 2003,
telecom/03-01-09
Minutes
of the Arlington meeting, November 2002,
telecom/02-11-02
Minutes
of the Helsinky meeting, September 2002,
telecom/02-09-07
Minutes
of the Orlando meeting, June 2002, telecom/02-06-01
Minutes
of the Yokohama meeting, April 2002,
telecom/02-04-02
Minutes
of the Anaheim meeting, January 2002,
telecom/02-01-03
Minutes
of the Dublin meeting, November 2001,
telecom/01-11-04
Minutes
of the Toronto meeting, September 2001,
telecom/01-09-04
Minutes
of the Danvers meeting, July 2001, telecom/01-07-17
Minutes
of the Paris meeting, April 2001, telecom/01-06-02
Minutes
of the Irvine meeting, February 2001,
telecom/01-03-07
Minutes
of the Orlando meeting, Decembre 2000,
telecom/00-12-23
Minutes
of the Burlingame meeting, September 2000,
telecom/00-10-01
Minutes
of the Oslo meeting, June 2000, telecom/00-06-10
Minutes
of the Denver meeting, March 2000, telecom/00-03-16
Minutes
of the Mesa meeting, January 2000, telecom/00-02-01
Minutes
of the Cambridge meeting, November 1999,
telecom/99-11-07
Presentations:
OMG
technologies in telecom industry - Status and
trends, June 2003, telecom/03-06-04
RFIs, RFPs:
Corba
Management RFI (Status: answers
received 01/04/02; Draft white paper expected April
2004, common work with DMTF and TMF) This Request
for Information (RFI) solicits information on
potential CORBA Management Services for managing
ORBs, CORBA Services and CORBA-based applications in
large scale heterogeneous networks. In particular,
the OMG ORBOS PTF wants to learn requirements (both
generic and domain specific), existing solutions and
related standards.
PIM
and PSM for Software Radio Components (Status:
Revised Submission due 05/04/04; SW radio RFP) This
RFP solicits proposals for a Platform Independent
Model (PIM) and a CORBA Platform Specific Model (PSM)
of radio infrastructure facilities that can be
utilitized in developing waveforms, which promotes
portability of waveforms across Software Defined
Radios (SDR).
Stream
for the CCM (Status: revised submission due:
05/04/04; Joint with Mars RFP). The CORBA Component
Model is a comprehensive component architecture
based on the reliable and well-proven CORBA
middleware. It contains concepts that allow for
multi-interface components, event based
communication, port based configuration and flexible
implementation structures. These concepts are
specified in the CCM metamodel. However, up to now
the CCM metamodel only foresees operational and
event based communication. There are no
possibilities to specify and implement components
communicating by continuous data exchange
(streams). Also the CCM container architecture does
not include any support for streams. This RFP
solicits proposals for an extension of the CCM that
facilitates the modeling, realization and execution
of components which communicate by exchange of
continuous data (streams). In conjunction with
existing OMG specifications, namely EDOC [ptc/02-02-05]
and existing CCM [formal/2002-06-65], this will
result in significant benefits to the CCM user
community especially in the telecom domain, since
many telecom applications consist of components
which exchange audio, video and other data streams.
Defense, medical, and industrial systems in which
continuous sensor or signal data predominates are
other target domains as well. It is the intent of
this RFP to encourage submissions that propose
concepts that are open to automation (i.e.
automation of connection setup, code generation, or
deployment) and will be integrated in the CCM
Component Model, CCM container architecture, and the
component implementation framework (CIF).
QoS
for the CCM (Status: revised submission due:
05/04/04: Mars RFP). The CORBA Component Model
is a comprehensive component architecture based on
the reliable and well-proven CORBA middleware. It
contains concepts that allow for multi-interface
components, event based communication, port based
configuration and flexible implementation
structures. These concepts are specified in the CCM
metamodel. Although the CCM is a major step forward
to support the design and implementation of
component based distributed telecommunication
systems, it has not sufficiently addressed the
non-functional or QoS related aspects of distributed
systems. These aspects are of special importance in
domains like telecommunication or real-time systems.
This RFP solicits proposals for an extension of the
CCM that facilitates the design and realization of
QoS in the context of CORBA Components. Proposals
are sought which enable the definition of flexible
QoS-categories and parameters and the association of
these to elements of CCM models. Furthermore, the
RFP solicits proposals which describe the mechanisms
which are necessary to negotiate, establish and
control QoS contracts in the context of
communication between components. It is the intent
of this RFP to encourage submissions that propose
concepts that are open to automation and will be
integrated in the CCM container architecture.
UML
profile and metamodel for voice-based applications
(Status: LOI dur on 05/04/03, Initial submission due
on 02/08/04, MARS RFP) This RFP addresses the
standardization of dialog models used in voice-based
applications in a platform-independent way. More
precisely, this RFP solicits proposals for the
following: -A MOF metamodel to describe platform
independent concepts to model voice dialogs -A UML
profile to describe the usage of the UML notation
when modeling voice dialogs
Vote Status:
Endorsed white
Papers:
- NGOSS (Next Generation
Operation Support Systems) Information model II
White paper endorsed by the TF, january 2003, telecom/03-01-01,
telecom/03-01-02,
telecom/03-01-03,
telecom/03-01-04
- Roadmap of the
telecom task force white paper endorsed by
the task force V1.0, telecom/01-04-02,
January 2001
- Open Service Market, white paper V1, telecom/00-06-05,
June 2000
- Wireless CORBA, white paper: telecom/98-11-09,
November 1998
- Intelligent Networking , white paper: telecom/96-12-03
, December 1996.
- TMN , white paper: telecom/96-07-01
, May 1996.
Links to adopted specifications
| Specification |
Documents |
Date
of adoption
Status |
| Notification/JMS
Interworking |
V1.0 specs: dtc/03-06-01 |
Adopted 03/03, finalization ongoing,
product on the market |
| PIM
and PSM for SDO |
V1.0 specs: sdo/03-03-01,
IDL: ad/03-03-01,
Rose: ad/03-03-02,
XMI: ad/03-03-03 |
Adopted 03/03, finalization ongoing |
| GIOP
tunnelling over Bluetooth RFC |
V1.1 Specs: dtc/03-10-03,
IDL dtc/03-10-04 |
Adopted 03/03, finalized 11/03, This
specification is now a part of the wireless
specification.RTF is on-going (see wireless
below). O pen source implementation exists |
| Federated
Charging and rating facility |
V1.0 Specs: dtc/03-01-01 |
Adopted 09/02, finalization ongoing |
| Wireless
Access and Terminal Mobility |
V1.1 Specs: dtc/03-10-03,
IDL dtc/03-10-04 |
Adopted 03/00, finalised 09/02, revised
V1.1 11/03. New RTF is on-going. |
| Telecom
Service Access &Subscription |
V1.0 pecs: formal/02-12-01 |
Adopted 06/00, finalized 06/02 |
| CORBA-FTAM/FTP
Interworking |
Specs: telecom/00-02-04 |
Adopted 03/00, finalized 01/02 |
| Management
of Event Domain |
Specs: formal/01-06-03 |
Adopted 01/00, finalized 03/01
products on the market |
| Telecom Log Service V1.1.2 |
V1.1.2 specs: formal/03-07-01
+ IDL: formal/03-07-02 |
Adopted 01/99, finalized
08/99, revised V1.1 29/04/02, products
on the market. |
| CORBA/TMN Interworking |
Specs: telecom/98-10-10,
IDLs: telecom/98-10-11 |
Adopted 11/98, Products on the
market |
| CORBA/TCAP
Interworking |
Specs: telecom/98-10-03
+ FTF final report Dtc/00-02-08 |
Adopted 11/98, finalized
03/00 |
| Notification Service 1.0.1 |
Specs: formal/02-08-04 |
Adopted 04/98, revised
three times v1.1: 10/98, v 1.2: 07/99,
v1.3: 12/00, Products on the Market |
| Control and Management of A/V
Streams |
Final specs: formal/00-01-03 |
Adopted10/97, Revised
10/98. Open source implementation exists |
Working Group:
No working group at the moment.
|
