|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI EN 383 001
|
|
Interworking between SIP and
BICC
Protocol or ISUP |
The present document provides the ETSI endorsement of the ITU-T Recommendation Q.1912.5.
ITU-T 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 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 3GPP TS 29.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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 013
|
|
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
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 022
|
|
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 TS 183 025
|
|
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 and 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
non-call 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
|
|
Protocol for QoS reservation information exchange between
the SPDF and the
Access-RACF (A-RACF) |
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 TS 183 026
|
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 TR 183 032
|
|
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
|
|
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
|
|
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 036
|
|
ISDN/SIP interworking - Protocol specification |
|
This TS specifies the, stage 3, Protocol Description of the signalling interworking between ISDN
DSS1 protocol and SIP based on the concatenation of ES 283 027, ES 283 003 with
EN 300 899-1.
The concatenation method describes only the SIP/ISDN parameter mapping without ISUP procedures. In addition direct inter-working not supported by this concatenation of these existing inter-working documents will be described.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI ES 283 039-2
|
|
NGN Congestion and Overload Control -
Part 2: Core GOCAP and NOCA Entity Behaviours |
|
The present document describes the core features of the NGN Overload Control Architecture (NOCA) and the Generic
Overload Control Application Protocol (GOCAP). While it is usual for the architectural components to be specified
separately from the protocols that are used to communicate between them, the performance requirements of overload
controls are such that the coupling between architecture, protocol and implementation is very strong. This means that
the present document specifies the architecture, entity behaviours and protocol for the core NOCA/GOCAP together.
The way GOCAP and the NOCA entities are deployed to control traffic that uses a specific application protocol is
profiled via additional small shim specifications.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI ES 283 039-3
|
|
NGN Overload Control Architecture -
Part 3: Overload and Congestion Control for H.248 MG/MGC |
|
The present document describes an extension to H.248.1 gateway protocol to enable a robust overload control
mechanism to be implemented between Access media GateWays (AGWs) and their associated Media Gateway
Controllers (MGCs). This proposal is intended to provide a resolution to a specific known NGN architectural issue that
needs to be resolved within the NGN release 1 time frame. The proposal is targeted at reference 1 and is independent of
the H248 core protocol version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 043
|
|
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 TS 183 045
|
|
Direct Communication Service Capability - SIP Protocol Specification |
The present document provides the ETSI TISPAN endorsement of, OMA-TS-PoC_ControlPlane-V1,
OMA-TS-PoC_UserPlane-V1, and OMA-TS-PoC_XDM-V1 in line with the requirements of TISPAN NGN.
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing Direct
Communication functionality.
TISPAN IMS is based on 3GPP IMS. It shall be possible to:
|
| - |
deploy TISPAN DC using 3GPP2 MMD as long as the related TISPAN requirements on IMS are considered
within 3GPP2 MMD;
| |
| - |
have interworking of TISPAN DC with 3GPP PoC and 3GPP2 PoC services.
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 046
|
|
SDP Interworking between Call/Session Control Protocols (SIP/SDP, RTSP/SDP; etc.) and the Gateway Control Protocol (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
|
|
RACS Stage 3 Signalling Flows |
The present document specifies normative rules for how to use the Gq', Rq, Ia and Re protocols (TS 183 017,
ES 283 026, ES 283 018, and TS 183 060) as of TISPAN release 2. These rules apply to the interface between:
|
| - |
P-CSCF and SPDF using Gq';
| |
| - |
IBCF and SPDF using Gq';
| |
| - |
SPDF and (C- and I-) BGF using Ia;
| |
| - |
SPDF and x-RACF using Rq;
| |
| - |
x-RACF and RCEF using Re.
|
In addition, to illustrate the usage of these rules, the present document contains informative signalling flows between
the above-listed entities.
The present document covers both IMS and non-IMS AFs, and both conversational services such as telephony and
non-conversational services such as IPTV.
For IPTV, both unicast and multicast are covered, as well as the push and pull models for interactions with the
ECF/EFF. Conversational multicast services and the usage of pull for conversational services is out of the scope for the
present document.
The following specific topics are covered in the present document;
|
| - |
policy enforcement in the RCEF;
| |
| - |
error handling over Ia;
| |
| - |
transcoding in the I/C-BGF;
| |
| - |
reservations requests in overbooking mode;
| |
| - |
address latching for hosted NAPT/NAPT-PT traversal.
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI ES 283 049
|
|
H.248 Profile for controlling Trunking Media Gateways (TMG) |
The present document provides the ETSI TISPAN endorsement of the
3GPP TS 29.332 "3rd Generation Partnership
Project; Technical Specification Group Core Network and Terminals; Media Gateway Control Function (MGCF) - IM
Media Gateway; Mn Interface (Release 7)".
The present document provides the necessary adaptations to the above specification, in order to comply with the
requirements of TISPAN NGN Release 2.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 050
|
|
Register of assigned protocol numbers and names |
The present document contains the record of assignment of names, numbers and identifiers used in TISPAN protocol
specifications, managed by TISPAN, and which are required to be globally unique. In particular, it contains the
assignments and sub-structure of ASN.1 Object Identifier trees assigned to TISPAN and the assignments and
sub-structure of any URI or URN schemes which TISPAN manages.
The present document also contains information on names, numbers and identifiers used in TISPAN protocol
specifications, but which are assigned by other authorities. This may include assignments from the IETF, ETSI, W3C,
etc.
Names, addresses, numbers and identifiers and their associated schemes, used in networks, assigned or managed or
monitored by TISPAN Working Group 4 are outside the scope of the present document. All aspects of numbering,
addressing and naming of a telecommunications network are outside the scope of the present document.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 052
|
|
Solution for REFER interworking problems |
|
The present documents purpose is to develop a solution for interworking problems of REFER based simulation services.
This solution shall adjust REFER interworking problems of the Release 1 NGN services ECT and CONF, and shall also
take into account Release 2 services.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 056
|
|
Feasibility study on new methods for Overlap Sending |
|
The present document purpose is to investigate new methods for providing overlap sending originating from PSTN
Networks and devices. The expectation is that such methods would save on processing that the present method for
overlap sending deploys. It is also the aim of this investigation to be fully backward compatible, have no impact upon
the SIP signalling protocols, and have a minimal impact upon the existing SIP nodes.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 057
|
|
Feasibility study on Out-of-Band DTMF |
The purpose of the present document is to analyse the requirements for out-of-band DTMF transport in IMS, to assess
the possible technical solutions addressing these requirements, to select a solution and to identify and derive the
required changes to the relevant IMS specifications.
|
| NOTE: |
The consequence of the TR will most certainly lead to developing CRs against ETSI TISPAN Release 2
IMS specifications and the corresponding 3GPP specifications.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 059-1
|
|
NASS - a2 interface based on the DIAMETER protocol |
The present document is applicable to the a2 interface between the Connectivity Session Location and Repository
Function (CLF) and the Network Access Configuration Function (NACF).
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 060
|
|
Resource and Admission Control Subsystem (RACS) -
Re interface based on the DIAMETER protocol |
The present document defines a specification based on DIAMETER for use at the Re Reference Point between the
TISPAN NGN Access-Resource Admission Control Function (A-RACF) and the Resource Control Enforcement
Function (RCEF).
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 063
|
|
IMS-based IPTV stage 3 specification |
The present document describes the Procedures on the Functional Entities and Call Flows for the protocols and their
possible enhancements to support IPTV services based on the architecture and stage 2 information flows described in
TS 182 027.
The possible enhancements of protocols will define the scope of new or enhanced protocol specifications.
Besides, the interaction with other Simulation Service will be considered.
|
| NOTE: |
The present document relies on the architectural framework defined in TS 182 027 for IMS-based
IPTV Stage 2 and may need to be updated once the open issues identified in the present document are
resolved.
|
The present document is applicable to:
|
| - |
the interface between the User Equipment (UE) and the Call Session Control Function (CSCF);
| |
| - |
the interface between the S-CSCF and IPTV Service Control Functions (SCF);
| |
| - |
the interface between the S-CSCF and IPTV Service Discovery Functions (SDF);
| |
| - |
the interface between the S-CSCF and the Media Control Functions (MCF);
| |
| - |
the interface between the User Equipment (UE) and IPTV Service Selection Functions(SSF);
| |
| - |
the interface between the User Equipment (UE) and Elementary Control Functions (ECF)/Elementary
Forwarding Functions (EFF);
| |
| - |
the interface between the User Equipment (UE) and IPTV Service Control Functions (SCF).
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 064
|
|
Dedicated IPTV subsystem stage 3 specification |
The present document provides the stage 3 description of the dedicated IPTV subsystem based on the architecture and
stage 2 information flows described in ETSI TS 182 028.
The protocol enhancements will form the scope of new or enhanced protocol specifications.
The interaction with other NGN subsystems such as PES, IMS and RACS will be considered.
The current release is applicable to:
|
| - |
the interface between the User Equipment (UE) and the SD&S;
| |
| - |
the interface between the User Equipment (UE) and Customer facing IPTV Applications (CF-IPTV-Apps);
| |
| - |
the interface between the User Equipment (UE) and IPTV Control (IPTV-C);
| |
| - |
the interface between the User Equipment (UE) and Media Control Functions (MCF);
| |
| - |
the interface between the User Equipment (UE) and Media Delivery Functions (MDF);
| |
| - |
the interface between the Customer facing IPTV Applications (CF-IPTV-Apps) and IPTV Control (IPTV-C);
| |
| - |
the interface for access to IPTV User Data Function (IPTV UDF);
| |
| - |
the interface between the IPTV Control (IPTV-C) and Media Control Functions (MCF);
| |
| - |
the interface for access to NGN User Data Access Function (NGN UDAF).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 066
|
|
Network Attachment Sub-System (NASS) - a4 interface based on the DIAMETER protocol |
The present document defines a protocol applicable to the a4 interface between the User Access Authorization
Function (UAAF) and the Connectivity session Location and repository Function (CLF), based on the Diameter
protocol.
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 TR 183 069
|
|
Business Trunking -
NGCN-NGN Interfaces Implementation Guide |
The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications
and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN.
The present document addresses control plane signalling (usage of SIP and SDP protocols, required SIP headers) as
well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport
protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI TISPAN specifications, as seen
from the perspective of an NGCN site.
Advice-of-charge aspects are addressed as far as SIP signalling is concerned.
The present document is based on TS 24 229 Release 7 as modified by ES 283 003 Release 2.
NOTE: Some errors corrected in TS 24 229 Release 8 and 9 are already taken into account in the present
document.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TR 183 070
|
|
RACS - Rr interface based on the ANCP protocol |
The present document provides a report on the study of the applicability of the ANCP (Access Node Control Protocol) protocol to the Rr interface
between Generic Resource Admission Control Function (x-RACF) instances.
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 ANCP. Where this is not possible, extensions to ANCP are defined within the
present document.
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 183 071
|
|
RACS - Rr interface based on the DIAMETER protocol |
The present document defines a specification applicable to the Rr interface between Generic Resource Admission
Control Function (x-RACF) instances, based on the Diameter protocol. Other alternative protocols which may also be
used for this interface such as ANCP are not specified in the present document.
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
