ETSI TISPAN NGN Specifications (page 2 of 3)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI EN 383 001
V1.1.1
2006-06
(29 p.)
|
NGN-R1 |
|
Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control (BICC)
Protocol or ISDN User Part (ISUP) |
[ITU-T Recommendation Q.1912.5, modified]
The present document provides the ETSI endorsement of the ITU-T Recommendation Q.1912.5.
ITU-T Recommendation Q.1912.5 defines the signalling interworking between the Bearer Independent Call Control
(BICC) or ISDN User Part (ISUP) protocols and SIP in order to support services that can be commonly supported by
BICC or ISUP and SIP-based network domains.
The present document is applicable to ETSI PSTN/ISDN networks interworking with networks based on an IETF based
SIP/SDP profile as defined in annex C of ITU-T Recommendation Q.1912.5.
In the case where an IMS-based network interworks with the PSTN/ISDN, then the ETSI endorsement of
3GPP TS 29.163,
in either ETSI TS 129 163 and
ETSI ES 283 027
as appropriate to the applicability of each document,
takes precedence.
Formats, codes and procedures marked for national use or as network option are included for informative purposes for
the international interface specification. If these items so marked are supported within a national network and operator's
network, then it is proposed that they are supported in this manner.
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
| Up List
Check
| |
Rapporteur: Jan Lindquist (V1) Carsten Waitzmann (V2) |
|
|
|
|
|
|
|
|
|
|
| | |
| Up List
Check
| |
Rapporteur: Sietse Van der Gaast (V1) Daniela Barcariol (V2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TR 183 013
V1.1.1
2006-05
(22 p.)
|
NGN-R1 |
|
Analysis of relevant 3GPP IMS specifications for use in
TISPAN_NGN Release 1 specifications |
The present document presents the analysis of the impacts on relevant 3GPP IMS specifications when used in the
context of TISPAN NGN R1 and proposes arrangements for their endorsement by TISPAN as part of NGN Release 1.
An early decision of the NGN project was to use the 3GPP defined IP Multimedia Subsystem (IMS) as a starting point
for providing Multimedia service capabilities and supporting Simulation of PSTN/ISDN communication services in the
fixed network. The present document reviews the content of the relevant 3GPP Technical Specifications and identifies
how their endorsement should be achieved to allow for the reuse of IMS in the TISPAN_NGN Release 1 specifications.
The document is structured as follows:
- Clause 4 identifies the process of endorsement.
- Clause 5 presents the analysis of endorsement requirements in the NGN.
- The annexes present outline CRs for specifically identified 3GPP documents.
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TR 183 014
V1.1.1
2005-12
(31 p.)
|
NGN-R1 |
|
PSTN/ISDN Emulation -
Development and Verification of PSTN/ISDN Emulation |
|
The present document presents the results of an analysis of bearer, basic and supplementary services currently provided
in PSTN and ISDN implementations. The purpose of the analysis was to identify further areas of standardization to
ensure that such services can be reliably emulated within the NGN thus enabling network operators to fulfil the
technical regulatory obligations on European ECN providers of Publicly Available Telephone Service. It was assumed
during the analysis that PSTN and ISDN signalling would be presented in the Integrated Services User Part (ISUP) as
defined in EN 300 356-1 and EN 300 356-2 and that signalling within the NGN would be encapsulated in SIP-I
as defined in
ETSI EN 383 001
and ITU-T Recommendation H.248.1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
| Up List
Check
| |
Rapporteur: Wayne Cutler (V1) Jerker Zetterlund (V2) |
|
|
|
|
|
|
|
|
|
|
| | |
| Up List
Check
| |
Rapporteur: Walter Brown (V1) Bruno Chatras (V2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TS 183 022
V1.1.1
2005-06
(8 p.)
|
NGN-R1 |
|
MGC Information Package |
The present document describes an extension to ITU-T Recommendation H.248.1 gateway protocol to enable a Call
Agent/MGC to store data on a MG that can be subsequently retrieved to facilitate MGC recovery action.
The standard H248 audit mechanism permits a MGC to retrieve data from an associated MG in order to re-synchronize
connection data/state between a MGC and MG. In terms of identifying the other end of this connection, the SDP RD
(Remote Descriptor) that is associated with the ephemeral termination enables the other end of the connection to be
identified - albeit not in a format that may be convenient for the MGC to use. In many cases the RD may not enable the
other end to be identified (e.g. some GWs may use different control and media addresses).
In order to achieve a co-ordinated recovery action, whereby both GW connections in a single call/end-end connection
can be torn down in parallel, it is proposed to define a new H248 package to enable the MGC to store a block of data on
a MG which enables the MGC to identify the other end of the connection. The structure of the stored data is understood
only by the MGC and is opaque to the MG. Thus, the MGC is now able, via standard H248 audit mechanisms, to
retrieve the previously stored data block in the event of a MGC failure. The MGC is now able to identify the other end
of the connection (e.g. typically on separate MG) and thus provide a co-ordinated clean-up of the related connections on
the separate MGs. The MGC is at liberty to define the contents of the string in a proprietary manner that is most
convenient for its own usage.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TR 183 025
V2.2.0
2008-06
(71 p.)
|
NGN-R2 |
|
H.248 Non-call related procedures and
management system interaction |
The purpose of the present document is to define guidelines with regard to the interaction of non-call related H.248
procedures and generic network management use cases and vice versa. More specifically, the interaction between the
following is considered:
|
| - |
Control procedures at the H.248 interface.
These are the procedures between Media Gateway Controllers (primary and secondary) and their associated
Media Gateways (primary, and secondary if available). These procedures primarily utilize the H.248
ServiceChange and H.248 Audit procedures.
| |
| - |
Management procedures at the management interface(s) of H.248 systems (i.e. both Media Gateway
Controller & Media Gateway) to perform non call related tasks such as configuration management (start-up,
capability change, maintenance locking) and fault management (failure handling).
|
It is intended that these guidelines are then subsequently used in corresponding H.248 profiles to produce detailed noncall
related procedures. At the current time, the existing set of ETSI H.248 profiles lack any such
detailed procedures.
Specific management systems, architectures and protocols are outside the scope of the present document; only the
general requirements and Use Cases related to the management system shall be discussed.
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI ES 283 026
V1.6.0
2008-04
(32 p.)
|
NGN-R1 |
|
Resource and Admission Control -
Protocol for QoS reservation information exchange between
the Service Policy Decision Function (SPDF) and the
Access-Resource and Admission Control Function (A-RACF)
in the Resource and Protocol specification |
The present document provides the stage 3 specification of the Rq interface. The functional requirements and the
stage 2 specifications of the Rq interface are contained in
ETSI ES 282 001
and
ETSI ES 282 003.
The Rq interface is the
interface between the Service Policy Decision Function (SPDF) and the Access - Resource and Admission Control
Function (A-RACF) and is used for QoS resource reservation information exchange between the SPDF and the
A-RACF. Via the Rq interface the SPDF issues requests for resources in the access network, indicating IP QoS
characteristics. The A-RACF uses the IP QoS information to perform admission control and indicate to the SPDF via
the Rq interface its admission control decisions. Due to the possible business roles in an access environment, the SPDF
may be either in the same domain or in a different domain as the A-RACF.
The present document defines:
-
The information to be exchanged between SPDF and A-RACF over the Rq interface.
-
An Rq interface definition based on the Diameter protocol.
In situations where no generic overload control mechanism is used on the Rq interface, the interface shall only be
capable of supporting a one-to-one relationship between the A-RACF and SPDF (i.e. one SPDF may only contact one
A-RACF, and that A-RACF may only contact that same SPDF). Overload control need not be supported in this
situation due to the fact that it should be possible to traffic engineer the capabilities of the two entities, so that the
capacity of one entity matches the capacity of the other.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI ES 283 030
V1.1.1
2006-07
(11 p.)
|
NGN-R1 |
|
Presence Service Capability -
Protocol Specification |
[3GPP TS 24.141
V7.0.0, modified and
OMA-TS-Presence_SIMPLE-V1_0, modified]
The present document provides the protocol details for the presence service within the IP Multimedia (IM) Core
Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in
ETSI ES 283 003.
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by
ETSI ES 283 003.
The Presence XDMS and Resource List Server (RLS) specific data formats and XCAP application usages are within the
scope of the present document. These are used within the context of the generic XDM capability described in
ETSI TS 183 038.
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing presence
functionality.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TR 183 032
V1.1.1
2006-05
(52 p.)
|
NGN-R1 |
|
Feasibility study into mechanisms for the support of
encapsulated ISUP information in IMS |
|
The present document addresses issues for the support of ISUP information between IMS entities when used in an
NGN, i.e. MGCF to MGCF, MGCF to AS, AS to MGCF, AGCF to AS, and possibly AS to AS.
The present document provides a home for text for incorporation into other deliverables once the documentation
structure has been decided.
A number of potential use cases exist for such a mechanism, e.g. PSTN to PSTN bridging using IMS, support of service
information to AS from MGCF in simulation services, support of the IMS based PSTN/ISDN emulation subsystem, but
it is not in the scope of the present document to provide information relating to use of this mechanism to support such
use cases. Such use of this mechanism will be dealt with by other work items.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI ES 283 034
V1.5.0
2008-04
(27 p.)
|
NGN-R1 |
|
Network Attachment Sub-System (NASS) -
e4 interface based on the DIAMETER protocol |
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and the Resource and Admission Control Subsystem (RACS), based on Diameter.
The present document is applicable to the e4 interface between the Connectivity Session Location and Repository
Function (CLF) and the RACS.
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined
within the present document.
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI ES 283 035
V1.2.1
2007-06
(18 p.)
|
NGN-R1 |
|
Network Attachment Sub-System (NASS) -
e2 interface based on the DIAMETER protocol |
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and service control subsystems or applications of the TISPAN NGN architecture, based on Diameter.
The present document is applicable to the e2 interface between the Connectivity Session Location and Repository
Function (CLF) and an Application Function (AF).
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined
within the present document.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TS 183 043
V1.1.1
2006-05
(68 p.)
|
NGN-R1 |
|
IMS-based PSTN/ISDN Emulation
Stage 3 specification |
The present document defines call control protocols and procedures for use in the IMS-based PSTN/ISDN Emulation
subsystem based on the Media Gateway Control Protocol (MEGACO), the Session Initiation Protocol (SIP), and the
associated Session Description Protocol (SDP).
NOTE: The present document relies on the architectural framework defined in
ETSI TS 182 012
for IMS-based
PES Emulation and may need to be updated once the open issues identified in the present document are
resolved.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TR 183 046
V2.0.0
2008-01
(30 p.)
|
NGN-R2 |
|
SDP Interworking between SIP/SDP and H.248/SDP |
The present document specifically describes the differing SDP usage between SIP and H.248 together with the
implied mapping capability that is performed by the MGC/Call Server.
SDP has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media
requirements of a given session/call/connection. However, the different VoIP control protocols that utilize SDP each
specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between
these variations in the use of SDP and perform the interworking between them. Specifically for this report, the differing
SDP usage between SIP and H.248 shall be described together with the implied mapping capability that is
performed by the MGC/Call Server.
Any network element (e.g. a MGCF) which handles both H.248/SDP signalling and SIP/SDP signalling provides any
necessary interworking between both signalling protocols. Such interworking comprises in general:
• interworking between SIP and H.248 signalling on message and procedural level (out of scope of the present
document); and
• interworking between the two SDP segments (SDP-SDP interworking; the scope of the present document).
The function providing SDP-to-SDP interworking between SIP/SDP and H.248/SDP signalling is, in the present
document, termed a "SDP Mapper".
The SDP Mapper performs SDP-SDP interworking capability to reconcile the different uses of SDP between control
protocols H.248 and SIP. In order to perform this role, the SDP Mapper takes into account i) which parts of SDP are
required to be sent on an interface, and ii) which parts of SDP are received on an interface. For a given session/call,
which use the two different control protocols at each end, some SDP parameters may be transited whilst others may not.
The SDP Mapper ensures that the differing requirements with regard to SDP handling at each end are mutually
satisfied.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
ETSI TS 183 048
V1.4.0
2008-06
(59 p.)
|
NGN-R1 |
| - |
P-CSCF and SPDF using Gq';
|
| - |
IBCF and SPDF using Gq';
|
| - |
SPDF and (C- and I-) BGF using Ia;
|
| - |
SPDF and A-RACF using Rq.
|
In addition, to illustrate the usage of these rules, the present document contains informative signalling flows between
the above-listed entities.
Non IMS AF entities are out of scope of the present document. Thus, the rules for using the Gq', Rq and Ia protocols
and the signalli | | |
