ETSI TISPAN NGN Specifications (page 3 of 3)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
ETSI TS 184 002
|
|
Identifiers (IDs) for NGN |
|
The present document provides an overview of the identifiers used within 3GPP which are considered applicable to
NGN. It is intended that the information contained in the present document are not referred to any specific TISPAN
Releases, and it shall be used as the basis for defining additional identifiers and related parameters to facilitate the
implementation of TISPAN NGN standards.
|
|
|
| |
| Up List |
Rapporteur: Hanns Juergen Schwarzbauer |
|
|
|
|
|
|
|
|
| |
|
ETSI EG 284 004
|
|
Incorporating Universal Communications Identifier (UCI)
support into the specification of
Next Generation Networks (NGN) |
The present document identifies approaches to incorporating UCI capabilities as defined in EG 202 067 and
EG 203 072 into ETSI's TISPAN NGN. The present document provides a review and assessment as to what extent
existing standards, specifications and guidelines support elements of a UCI implementation and how, if necessary, they
should be adapted in order to more fully support complete UCI implementation. The analysis presented is not restricted
to only those standards and specifications developed in TISPAN but also covers the work of other bodies (whose work
is already being incorporated to the NGN):
|
| - |
a review of the work done by Liberty Alliance in this area is provided in annex C;
| |
| - |
a review of the existing TISPAN NGN capabilities to provide a UCI presence service is provided in annex B;
and
| |
| - |
a review of SIP capabilities in this area is provided in annex A.
|
An outline abstract model of UCI showing use-cases, architecture and information flows is given in clause 5 and an
analysis of how existing NGN protocols and capabilities support them is given in clause 6. The abstract model shows
how the UCI elements are carried and how they may be presented across the NGN.
The present document provides, in clause 11, a model showing how UCI exists in the context of other developing
standards work at ETSI and how they fit to the existing NGN model.
|
|
|
| |
| Up List |
Rapporteur: Michael Pluke |
|
|
|
|
|
|
|
|
| |
|
ETSI TR 184 005
|
|
Types of numbers used in an NGN environment |
The present document describes the public identifiers, in the numeric format, used in NGNs: international E.164
numbers, E.164 numbers in the national formats and different types of non-E.164 numbers.
It describes the processing of dialled digits to achieve these numbers and the usage of all these kinds of numbers. For
E.164 numbers also the processing to a target name in an NGN environment for further name/number to address
translation is explained. The processing (treatment) of non-E.164 numbers is FFS but some initial discussion could be
found in annex A.
|
|
|
| |
| Up List |
Rapporteur: Joakim Stralmark |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 184 006
|
|
Interconnection and Routeing requirements related to Numbering and Naming for NGNs;
NAR Interconnect |
The present document analyzes the issues concerned with interconnection and routeing in NGN and their implications
and requirements for numbering, naming and addressing and related resolution functionalities.
Several different interconnection scenarios are considered, based on TISPAN "NGN Functional Architecture",
although not all require the use of all architectural functions. The role of the transit network has also been considered in
order to evaluate the knowledge of numbers/names served by different operators and related requirements for routing
purposes.
Some scenarios may require the availability of infrastructure systems for numbering/naming resolutions, such as
infrastructure ENUM, or other database based system for route resolution, and may require coordinated provision by
involved operators.
The present document focuses on calls routed between subscribers identified by E.164 numbers, coded through either
tel URI and SIP URI formats. It also applies only to the transfer of calls across interconnection points between the home
network of the A-Party and the home network of the B-Party. It does not consider in detail interconnections needed to
support roaming scenarios. A further issue of the present document will consider interconnect scenarios related to
roaming.
The present document is relevant not just to IMS but to any NGN SIP-based interconnection.
|
|
|
| |
| Up List |
Rapporteur: Francesco Silletta |
|
|
|
|
|
|
|
|
| |
|
ETSI TR 184 007
|
|
Naming/Numbering Address Resolution (NAR) |
The present document investigates the need to introduce a Naming/Numbering Address Resolution framework into
TISPAN NGN conformant communication networks. To this end the following topics are covered:
|
| - |
Analysis of the consequences of creating a Naming/Numbering Address Resolution framework.
| |
| - |
Gap Analysis of current TISPAN NGNs specifications in comparison to existing/emerging solutions of NAR
methods.
| |
| - |
Identification of items for standardization as a result of the analysis described in the bullet above.
|
Furthermore the present document investigates the Naming/Numbering Address Resolution (NAR) in NGNs and
identifies Naming/Numbering Address Resolution (NAR) use cases used in NGN environments.
|
|
|
| |
| Up List |
Rapporteur: Frank Mildner |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Oskar van Deventer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Didier Becam |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 185 003
|
|
Customer Network Gateway Architecture and Reference Points |
The present document provides an overview of Customer Network Gateway (CNG) functional architecture and
reference points and the way it interacts with an NGN, as described in ETSI TISPAN Release 1 and Release 2 standards
(see ES 282 001).
The present document describes architectural building blocks to be included in the CNG to support the interworking
with an NGN, both at the transfer, transport and service layers. It also defines the reference points between the CNG
internal architectural blocks involved and a CND.
The WG5 does not address the layer 1 issues, as such studies refer to the AT&TM Group.
|
|
|
| |
| Up List |
Rapporteur: Bastien Lamer |
|
|
|
|
|
|
|
|
| |
|
ETSI TR 185 004
|
|
High level customer network architectures |
The objective of the present document is to analyse the possible architectures for the customer environment, combining
different possibilities in terms of elements to be considered. In particular, the analysed architectures will cover the
possibility of managing one or more than one entry points from the WAN side, using one or more than one customer
gateway, or possibly excluding the adoption of a customer gateway. Different alternatives for Customer Network
Gateway ownership will also be examined. The detailed architectures of customer devices and customer network
gateways will be addressed in other WIs and will take into account the possible alternatives analysed in the present
document.
The customer network is intended to support residential or small office scenarios, so that the scope of the document
does not include corporate scenarios which are to be covered by other documents.
|
|
|
| |
| Up List |
Rapporteur: Radu Suciu |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Milan Erbes |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 185 006
|
|
Customer Devices architecture and interfaces and Reference Points |
The present document defines the stage 2 Customer Network Devices (CND) specifications, including architectural
building blocks to be included in the Customer Network Devices to support the interworking with control plane NGN
architecture, both for the transport layers (NASS, RACS) and for the service layer. The present document will also
define the reference points between the NGN architectural blocks involved and the corresponding CNDs functions here
defined (for the cases in what the CNG will be transparent for the service and control planes point of view), as well as
between the Customer Network Devices and the CNG when appropriate. The present document will perform, as first
step, a categorization of the different user equipment with reference to the type of service supported and the different
levels of implementation of the related functionalities.
Please note that in relation to the Customer Network Devices for IPTV usage the present document will cover only the
classification step and will not provide any detail about the architecture and reference points. The IPTV CND are
specified in TS 185 009.
|
|
|
| |
| Up List |
Rapporteur: Fabrizio Verroca |
|
|
|
|
|
|
|
|
| |
|
ETSI TR 185 007
|
|
Analysis of protocols for customer networks connected to TISPAN NGN |
|
The present document contains informative text for analysing the set of protocols that can be used in the Customer
Premises Networks (CPN) on the interfaces defined by stage 2 documents TS 185 003 and TS 185 006 related to
service and transport layers. It will constitute a basic document produced by WG5, with a strong collaboration with
WG3, to be used as the starting point for future technical specifications on that field
|
|
|
| |
| Up List |
Rapporteur: Fabrizio Verroca |
|
|
|
|
|
|
|
|
| |
|
ETSI TR 185 008
|
|
Analysis of security mechanisms for customer networks connected to TISPAN NGN R2 |
The present document present an analysis of the security mechanisms that could be supported in the customer
environment (Customer Network Gateway or Customer Devices) with reference to the overall end to end security
architecture for the NGN defined by WG7. As examples, these mechanisms can be related to authentication (for
connectivity and for services), firewalling and network access/parental control, virus protection, intrusion detection,
Anti Spam capabilities. The activity will be performed in close relationship with WG7.
The reactions to threats or the protections against threats described in the present document will involve only the CPN,
not the external network.
|
|
|
| |
| Up List |
Rapporteur: Christophe Dubois |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 185 009
|
|
Architecture and reference points of a customer network device for IMS based IPTV services |
The present document defines the stage 2 Customer Network Devices for IPTV services (IPTV-CND) specifications; It
is therefore addressing the overall architecture of the customer network device (CND) enabling the IPTV service
consumption. The architectural definition is covering both transport and service layer related functionalities. The
reference points between the CND and the Customer Network Gateway (CNG) are also part of the specifications.
The 2 solutions elaborated specified in
ETSI TS 182 027 and
ETSI TS 182 028 are IMS based IPTV and IPTV Dedicated
Subsystem solutions but only the IMS based IPTV solution is considered in the present document.
|
|
|
| |
| Up List |
Rapporteur: Denis Mischler |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Axel Rennoch |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Michael Gläser |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 005-1
|
|
Terminating Identification Presentation (TIP) and
Terminating Identification Restriction (TIR) -
Part 1: Protocol Implementation
Conformance Statement (PICS) |
The present document specifies the Protocol implementation conformance statement (PICS) for the
Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) NGN Basic Service,
ETSI TS 183 008.
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP
Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
The TIP service provides the originating party with the possibility to receive a trusted (network-provided) identity of the
terminating party, and is applicable to all session-based services of the NGN.
The OIR service enables the terminating party to prevent presentation of any network-provided identity to the
originating party, and is applicable to all session-based services of the NGN.
|
|
|
| |
| Up List |
Rapporteur: Gerhard Ott |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Axel Rennoch |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 006-1
|
|
Originating Identification Presentation (OIP) and
Originating Identification Restriction (OIR) -
Part 1: Protocol Implementation
Conformance Statement (PICS) |
The present document specifies the Protocol implementation conformance statement (PICS) for the Originating
Identification Presentation (OIP) and Originating Identification Restriction (OIR) NGN Basic Service,
ETSI TS 183 007.
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP
Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
The OIP service provides the terminating party with the possibility to receive a trusted (network-provided) identity of
the originating party, and is applicable to all session-based services of the NGN.
The OIR service enables the originating party to prevent presentation of any network-provided identity to the
terminating party, and is applicable to all session-based services of the NGN.
|
|
|
| |
| Up List |
Rapporteur: Gerhard Ott |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Axel Rennoch |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 007-1
|
|
Communication HOLD (CH) -
Part 1: Protocol Implementation
Conformance Statement (PICS) |
|
The present document specifies the Protocol implementation conformance statement (PICS) for the Communication
Hold service (HOLD) NGN Basic Service,
ETSI TS 183 010.
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP
Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
The Communication Hold supplementary service enables a user to suspend the media stream(s) of an established IP
multimedia session, and resume the media stream(s) at a later time.
|
|
|
| |
| Up List |
Rapporteur: Gerhard Ott |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 007-2
|
|
Communication HOLD (CH) -
Part 2: Test Suite Structure and Test Purposes (TSS&TP) |
|
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP of the Communication Hold
service, based on stage one and two of the ISDN HOLD supplementary services.
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP
Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
|
|
| |
| Up List |
Rapporteur: Martin Brand |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Rapporteur: Axel Rennoch |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 008-1
|
|
IMS/NGN Performance Benchmark
Part 1: Core Concepts |
The present document is for an initial, revision 1.0, release of an IMS/TISPAN NGN performance benchmark. The
metrics measured and reported are for performance of this subsystem under a communications application load.
The benchmark is defined for the IMS network as a whole, as well as for several subsystems of an IMS network. The
benchmark is designed so that nodes composing a subsystem can also be benchmarked alone.
This multi-part deliverable consists of three parts document is in three parts. The present document contains overall
benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking
scenarios.
TS 186 008-2 contains the IMS and ETSI TISPAN SUT subsystem configurations, the specific benchmarking
use-cases and scenarios, along with scenario specific metrics and design objectives. It also defines the SUT
configuration parameters. This part also contains any required extensions to the overall descriptions present in the
present document, if necessary for the specific scenario.
TS 186 008-3 defines an initial benchmark test through the specification of a traffic set, traffic-time profile and
benchmark test procedure.
|
|
|
| |
| Up List |
Rapporteur: Olivier Jacques |
|
|
|
|
|
|
|
|
| |
|
ETSI TS 186 008-2
|
|
IMS/NGN Performance Benchmark
Part 2: Subsystem Configurations and Benchmarks |
The present document is for an initial, revision 1.0, release of an IMS/NGN performance benchmark. The metrics
measured and reported are for performance of this subsystem under a communications application load.
The benchmark is defined for the IMS/NGN network as a whole, as well as for several subsystems of an IMS/NGN
network. The benchmark is designed so that nodes composing a subsystem can also be benchmarked alone.
This multi-part deliverable consists of three parts. TS 186 008-1 contains overall benchmark descriptions,
architectures, processes, and information models that are common to all specific benchmarking scenarios.
The present document is Part 2 of the IMS Benchmark definition and contains the IMS and ETSI TISPAN SUT
subsystem configurations, the specific benchmarking use-cases and scenarios, along with scenario specific metrics and
design objectives. It also defines the SUT configuration parameters. The present document also contains any required
extensions to the overall descriptions present in TS 186 008-1, if necessary for the specific scenario. This present
document also includes an attachment containing any required data or code files.
TS 186 008-3 defines an initial benchmark test through the specification of a traffic set, traffic-time profile, and
benchmark test procedure.
The current architecture and scenarios defined for IMS/NGN Benchmark in the present document include:
|
| - |
Control plane of the IMS/NGN architecture.
| |
| - |
Registration/De-Registration use-case.
| |
| - |
Session setup/teardown use-case.
| |
| - |
Page mode messaging use-case.
|
|
|
|
| |
| Up List |
Rapporteur: Olivier Jacques |
|
|
|
|
|
|
|
|
|
|
