
Spec
download
| Titles and spec
numbers | Current
version | Releases
| Numbering
scheme |
Change Requests This page contains informal descriptive text only. See master
WID page for further details. 3GPP has
adopted the approach of creating a number of IMS enablers that can be used by a
number of services. The success of this has been demonstrated through the
adoption of the IMS by other standardisation bodies (e.g. TISPAN, OMA, ….).
Various technical IMS specifications provide the ability to sequence invocations
of IP Multimedia Applications or their servers. Being able to statically
sequence handing off session control to individual applications or their servers
is not sufficient. Use cases exist where applying only this static means would
result in an undesirable service experience for the user.
A means is
required in order to identify the correct IP Multimedia Application (or its
server) requested and to coordinate among applications for the following reasons:
§
It is required to identify the correct IP Multimedia Application (server(s))
to link into the call path, if required, in order to provide a consistent &
anticipated user experience.
§
Often interworking requires knowledge of the services being interworked,
as such interworking between an IMS based IP Multimedia Application and a
non-IMS based service may benefit from the identification of the requested
service. Also, a
means is required in order to store the Service Broker identifier sequencing
instructions for application coordination. The
objective of the work item is to enhance functionality for service brokering
found in previous releases.
Published
specifications |
Historical
information |
Work
plan
| TSG
Working methods | Drafting
rules | Delegates
corner|
ASN.1
Feature: IMS Service Brokering enhancements
This work
item enhances existing requirements for the coordination of IP Multimedia
Applications engaged in service delivery.
page maintained by Specifications Manager
last updated
2006-04-03: first issue