|
Reasons for the question
The desire to support existing network services and their enhancements, and
the desire to introduce multimedia - multiparty network services, employing
multiple bearer transport technologies, will require the specification of
network based bearer transport technology independent call control signalling
protocols which support both fixed and mobile network applications.
Because of the desire of the network service providers to physically
distribute network intelligence, therefore, physical separation of the
functionality of network nodes is being studied in external user implementation
forums. Presently these forums are studying the physical separation of call
control function and bearer control functions, and the physical separation of
bearer control functions from switch control and port control functions. The
specification of the network based bearer transport technology independent call
control signalling protocols will be required to apply the concept of physical
separation of call control functions and bearer transport control functions. In
order that the call control functions are independent of bearer transport
technology being controlled by the bearer transport control functions, the
interaction between the call control functions and the bearer transport control
function must be bearer technology independent.
Question
What new protocol recommendations and what enhancements to existing protocol
recommendations are required to support the evolution of bearer transport
independent signalling protocols?
Task objectives
The major focus of this question is to develop bearer transport independent
call control protocol recommendations to be used to support both fixed and
mobile network based services. The task objectives for the question are:
1) Develop the signalling protocol recommendations for the internal
network, call control to call control-signalling applications covered by the
requirements from the question responsible for the Signalling requirements
for the support of Bearer Independent Call Control Applications.
2) Develop the signalling protocol recommendations for the call control
to bearer transport control signalling protocols covered by the requirements
from the question responsible for the Signalling requirements for the
support of Bearer Independent Call Control Applications.
3) Develop the signalling protocol recommendations for extension of
technology based bearer control signalling protocols (excluding Q.AAL2, DSS
2 and B-ISUP, which are in other questions) that may be required in order to
support bearer independent call control applications covered by the
requirements from the question responsible for the Signalling requirements
for the support of Bearer Independent Call Control Applications.
4) Develop the signalling protocol interworking recommendations between
the Bearer Independent Call Control and monolithic environments.
5) Produce the necessary information for Protocol Implementation
Conformance Statements (PICS) with the support of the testing question
(Question P), if required. To assist the test generation the extensive
usage of formal description techniques (e.g. SDL, ASN.1) is encouraged.
Estimated Completion: Ongoing.
The outputs of this question will be recorded as ITU-T recommendations. For
task items 1, 2, 3, and 4, completion dates will be set by requirements
from the question responsible for the Signalling requirements for the support of
Bearer Independent Call Control Applications.
Relationships
The development of these recommendations will require close coordination
activities with:
- Requirements from the question responsible for the Signalling
requirements for the support of Bearer Independent Call Control
Applications.
- Bearer control signalling protocol questions (e.g. H.323, etc.).
- Device control signalling protocol questions (e.g. H.248, etc.).
- Signalling transport protocol questions.
- Integrated call and bearer protocol questions (e.g. DSS 1, DSS 2,
ISUP, B-ISUP, H.323).
|
