hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f48081bd805749985fb8401c02d17713 | 101 495 | 3.2 Symbols | Void. |
f48081bd805749985fb8401c02d17713 | 101 495 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface BWS Broadcast WebSite CA Conditional Access DAB Digital Audio Broadcasting DCP Distribution and Communications Protocol DECT Digital Enhanced Cordless Telecommunications DIQ Digital baseband In-phase and Quadrature DL Dynamic Label DMB Digital Multimedia Broadcasting DRM Digital Radio Mondiale EBU European Broadcasting Union EDI Encapsulation of DAB Interfaces EPG Electronic Programme Guide ETI Ensemble Transport Interface FIC Fast Information Channel FM Frequency Modulation FM-RDS Frequency Modulation - Radio Data System GI Group Information GSM Global System for Mobile communication HE-AAC High Efficiency - Advanced Audio Coding HTML Hyper Text Markup Language IEC International Electrotechnical Committee IP Internet Protocol IPDC Internet Protocol Data Channel ISDN Integrated Services Digital Network JTC Joint Technical Committee LI Logical Interface ETSI ETSI TR 101 495 V2.2.1 (2019-11) 9 Mbit/s Mega (106) bits per second MHz Mega (106) Hertz MOT Multimedia Object Transfer MPEG Moving Pictures Expert Group MSC Main Service Channel MTU Maximum Transfer Unit ODA Open Data Application OFDM Orthogonal Frequency Division Multiplexing OMRI Open Mobile Radio Interface PAD Programme Associated Data PFT Protection, Fragmentation and Transport PI Programme Information PSI/SI Programme Specific Information/Service Information PSSC Personal DAB Service Session Control PSTN Public Switched Telecommunications System RDS Radio Data System RDS-ODA RDS Open Data Application RF Radio Frequency RTP Real-time Transport Protocol SAT Sub-channel Assignment Table SFN Single Frequency Network SI Service Information SPI Service and Programme Information STI Service Transport Interface STI-C Service Transport Interface - Control STI-D Service Transport Interface - Data TDC Transparent Data Channel TMC Traffic Message Channel TPEG Transport Protocol Experts Group XML eXtensible Markup Language |
f48081bd805749985fb8401c02d17713 | 101 495 | 4 Introduction | The DAB system originated as a European funded project known as Eureka 147. The members of the project team decided to standardize the system at ETSI and the system standard was first published in 1995. Since then the system has been modified in various ways and additional standards documents have also been created to facilitate additional features, interoperable equipment interfaces for contribution and distribution networks, additional transport modes, data applications and so on. The present document is designed to provide some background and guidance to those considering using the DAB system so that the appropriate standards documents are consulted. DAB is primarily a system for digital radio and so the coding and modulation is designed to provide reliable mobile reception. This also allows non-audio services to be carried, including mobile video services, traffic data and a host of other applications. DAB is relatively wideband for a broadcast radio system and therefore carries several services, known as a multiplex. However, the multiplex is primarily a feature of the transmission system. One key benefit of digital radio is that it should be easy to use: therefore receiver makers should ensure that the user can understand the way to select services, and this is often best achieved with a flat list. DAB is most widely used as a digital radio transmission system using DAB+ audio coding and text messages carried as dynamic labels. Additional data often accompanies the audio: visuals via the SlideShow application and logos and programme information via the SPI application. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 10 |
f48081bd805749985fb8401c02d17713 | 101 495 | 5 DAB system standards | |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.1 Introduction | The DAB system is built around a core which defines the coding, modulation and transmission system parameters. Surrounding the core, two basic data mechanisms are provided: stream mode and packet mode. Also defined is the signalling channel that allows a receiver to make sense of the content of the multiplex. Audio coding and data transport definitions are provided in separate documents, along with the enumeration of certain signalling parameters and the rules of operation for complex service information features. This scheme is shown in figure 1. Figure 1: Building blocks of the DAB system |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.2 DAB system definition | |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.2.1 DAB system standard | ETSI EN 300 401 [i.1] is the DAB system standard. It was first published in 1995. In 2016 the WorldDAB Technical Committee performed a detailed review of the standard and the way that it had been utilized during its 20 year lifetime. The conclusion of that work was a simplified and revised version of the standard published as V2.1.1 in 2017. It describes the DAB system, designed for delivery of high-quality digital audio programme and data services for mobile, portable and fixed reception from terrestrial transmitters in frequency bands from 30 MHz to 300 MHz. The DAB system is designed to provide spectrum and power efficient techniques in terrestrial transmitter network planning, known as the Single Frequency Network (SFN). ETSI EN 300 401 [i.1] defines the DAB transmission signal. It includes the coding algorithms for multiplexing of audio programmes and data services, channel coding and modulation. Provision is also made for transmission of additional data services which may be programme related or not, within the limit of the total system capacity. ETSI EN 300 401 [i.1] provides information on the system configuration which includes information about the ensembles, services, service components and linking of them. ETSI EN 300 401 [i.1] describes the nominal characteristics of the emitted DAB signal. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 11 |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.2.2 Registered tables | To allow development of additional features and data services without the need to revise the DAB system standard, ETSI TS 101 756 [i.2] contains the enumeration of various parameters. It also contains the enumeration for certain parameters in the MOT standard, ETSI EN 301 234 [i.8]. The tables in ETSI TS 101 756 [i.2] are maintained by the WorldDAB Technical Committee. The procedure for registering a new value in an existing table or the registration of a new table is described in clause 4 of ETSI TS 101 756 [i.2]. Additionally there are annexes containing translations of Programme Type Codes and Announcement Type Codes and the definition of the Latin-based character set and its minimum representation on displays. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.2.3 Rules of implementation | ETSI TS 103 176 [i.3] defines rules of implementation for certain service information features. These rules have been developed to provide a reliable and consistent experience for digital radio listeners; they provide implementation details for how the Fast Information Channel (FIC) signalling is used and how receivers will interpret and behave in response to receiving the FIC signalling. The rules define the requirements for service following, service lists, announcements and text (for both FIC labels and dynamic labels) and these rules need to be followed in order to provide the expected behaviour of the features. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.2.4 Conditional Access | ETSI TS 102 367 [i.4] describes the conditional access system that may be used for DAB service components. It allows for scrambling to be applied to stream mode audio, stream mode data and packet mode data service components. It specifies the framework for signalling and various configurations of content and access control data. It should be noted that CA is optional. CA is not applied to free-to-air radio services carried over DAB. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.3 Audio coding | |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.3.1 Introduction | In the original DAB standard, audio coding was included. Later, with the development of more efficient audio coding methods, the DAB+ audio coding method was introduced and specified in a separate ETSI TS document. With the publication of ETSI EN 300 401 [i.1] (V2.1.1), DAB audio coding was moved into a separate ETSI TS document in order to reflect that all introductions of the DAB system since the availability of DAB+ audio have been implemented using DAB+ audio for radio services and that many existing transmissions have been migrated from DAB audio to DAB+ audio. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.3.2 DAB+ audio | ETSI TS 102 563 [i.5] defines the method to code and transmit audio services using the HE-AAC v2 audio coder. It details the necessary mandatory requirements for decoders, the permitted audio modes and the data protection and encapsulation. This audio coding scheme permits the full use of the PAD channel for carrying dynamic labels and user applications. DAB+ audio is recommended for all audio services as it provides a greater efficiency and enhanced robustness compared to the original DAB audio. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.3.3 DAB audio | ETSI TS 103 466 [i.6] defines the original method for coding audio services, using the MPEG layer 2 audio coder. The content is technically identical to that in ETSI EN 300 401 [i.1] (V1.4.1), except that the unused dual channel mode has been removed. It is provided to ensure continued support for existing broadcasts that use DAB audio, but it is not recommended for new implementations since DAB+ audio provides greater efficiency. However, it should be noted that there are no IPR fees to pay when implementing DAB audio, either for transmission or reception. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 12 |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.3.4 DAB audio testing | ETSI TS 101 757 [i.7] specifies a test procedure for DAB audio and defines test bitstreams which can be used to verify whether bitstreams and decoders meet the requirements as specified in ETSI TS 103 466 [i.6]. These tests can be used for various purposes such as: • manufacturers of encoders, and their customers, can use the tests to verify whether the encoder produces valid bitstreams; • manufacturers of decoders and their customers can use the tests to verify whether the decoder meets the requirements specified in ETSI TS 103 466 [i.6] for the claimed decoder capabilities. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.4 Data transport coding | |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.4.1 Introduction | The DAB system provides two basic mechanisms for data transport - stream mode and packet mode. Building on these basic mechanisms, data transmission generally takes two forms - file based and stream based. The Multimedia Object Transfer (MOT) standard allows broadcasting of file based data. The Transparent Data Channel (TDC) standard allows broadcasting of synchronous and asynchronous streams. Mechanisms have also been provided to allow MPEG-2 transport stream based services to be carried over DAB. The data applications using these data transport provisions are given in clause 7. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.4.2 File transfer - MOT | ETSI EN 301 234 [i.8] describes the MOT protocol which allows broadcasting of various kinds of data using the DAB system. It is tailored to the needs of Multimedia services and the specific constraints given by the broadcasting characteristics of the DAB system. MOT ensures interoperability between different data services and application types as well as equipment from different manufacturers. It allows a flexible utilization of the data channels incorporated in the DAB system, as well as methods to manage and maintain a reliable transmission in a uni-directional broadcast environment. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.4.3 Transparent Data Channel - TDC | ETSI TS 101 759 [i.9], defines the method to deliver synchronous or asynchronous data transparently within a DAB transmission, either in stream mode or packet mode. |
f48081bd805749985fb8401c02d17713 | 101 495 | 5.4.4 MPEG-2 Transport Stream | ETSI TS 102 427 [i.10] specifies how MPEG-2 Transport Stream can be encapsulated within a DAB MSC stream data subchannel, including additional error protection. The error protection mechanism is composed of a Reed-Solomon coder and an interleaver. |
f48081bd805749985fb8401c02d17713 | 101 495 | 6 DAB contribution, distribution and network standards | |
f48081bd805749985fb8401c02d17713 | 101 495 | 6.1 Introduction | These standards provide vendor independent broadcast networking interfaces for contribution and distribution networks. ETSI EN 300 797 [i.11] describes the Service Transport Interface (STI), ETSI EN 300 798 [i.13] describes the digital baseband in-phase and quadrature interface and ETSI ETS 300 799 [i.14] describes the Ensemble Transport Interface (ETI). ETSI TS 102 693 [i.15] provides a mechanism for the encapsulation of STI and ETI compliant data streams for distribution over IP networks. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 13 Ensemble- multiplexer Service Transport- multiplex Audio Data Service Information Service Provider 1 Service Transport- multiplex Audio Data Service Information Service Provider 2 Service Transport- multiplex Audio Data Service Information Service Provider n Service transport- network Ensemble transport- network Transmitter 1 COFDM Encoder Transmitter m COFDM Encoder ETI ETI ETI STI STI STI STI DIQ DIQ Figure 2: Conceptual DAB transmission network and related standards |
f48081bd805749985fb8401c02d17713 | 101 495 | 6.2 Contribution networks - STI | ETSI EN 300 797 [i.11] provides a standardized way of transporting DAB service components, service information and control information in a DAB contribution network. The contribution network connects the studios of the various Service providers to the Ensemble provider's ensemble multiplexer. The STI consists of two parts: the data part, STI-D, which carries data intended for broadcast, and the control part, STI-C, which carries data for control and monitoring purposes and is not intended for broadcast. STI-D is unidirectional in nature, whereas STI-C is bidirectional in nature. ETSI EN 300 797 [i.11] specifies first the logical interface for STI-D and STI-C, and then defines various physical implementations for them. The STI interface is suitable for use on a number of different physical media and telecommunication networks. Provision is made for the inclusion of appropriate error detection and correction and for the management of network transit delay. ETSI TS 101 860 [i.12] defines guidance in implementation and usage of the functionality described in the STI standard ETSI EN 300 797 [i.11]. Subsets of the STI standard are defined in order to make interoperable solutions possible for different suppliers of STI devices. The subsets are called STI Levels. Interoperability is ensured if the STI Logical Interface (LI) and STI Physical Interfaces (STI-PI, X) are the same for entities transporting DAB Service Components, Service Information and control messages in a DAB contribution network. |
f48081bd805749985fb8401c02d17713 | 101 495 | 6.3 Transmission interface - DIQ | ETSI EN 300 798 [i.13] is applicable to DAB channel coding equipment typically located at each of the transmitter sites in a DAB SFN. The norm describes the characteristics of a suitable interface for the connection of the two major elements of the DAB OFDM generator; the baseband processing equipment and the RF modulator. The interface provides an interconnection between a single source (the baseband processor) and a single destination (the RF modulator). The standard does not cover the generation of the digital I/Q baseband signals since this is covered in ETSI EN 300 401 [i.1]. The digital baseband I/Q interface is unidirectional and does not cover the provision of status nor control information in the reverse direction (i.e. from the modulator back to the baseband processing section of the equipment). |
f48081bd805749985fb8401c02d17713 | 101 495 | 6.4 Distribution networks - ETI | ETSI ETS 300 799 [i.14] establishes a method for the distribution of DAB signals between the ensemble multiplexer, and DAB modulation equipment located at the different transmission sites of an SFN. The data flow of the ETI is unidirectional by nature and the standard specifies first the logical interface the ETI, and then defines various physical implementations for it. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 14 The interface is suitable for use on a number of different physical media including standard 2 Mbit/s switched telecommunication networks. Provision is made for the inclusion of appropriate error detection and correction and for the management of network transit delay. Limited capacity is also made available for signalling from the ensemble multiplexer to other equipment in the distribution network. ETSI ETS 300 799 [i.14] does not cover the provision of status nor control information in the reverse direction (i.e. from transmitters back to the Ensemble provider). |
f48081bd805749985fb8401c02d17713 | 101 495 | 6.5 IP encapsulation - EDI | ETSI TS 102 693 [i.15] provides a mechanism for the encapsulation of STI-D (see ETSI EN 300 797 [i.11]) and ETI (see ETSI ETS 300 799 [i.14]) compliant data streams for distribution over IP networks. EDI is based on the existing Distribution and Communications Protocol (DCP - ETSI TS 102 821 [i.16]) and therefore a layered approach relevant to unique IP network designs can be implemented. EDI is designed to distribute STI-D and ETI over varying conditions of IP networks, and ensure the robust delivery of STI-D and ETI compliant data over networks affected by congestion, jitter and limited packet loss. EDI can be configured to operate a re-send function, or re-construct missed packets at the receiver in times of packet loss. Once the EDI Packet has been passed to the DCP stage, Protection, Fragmentation and Transport (PFT) can add a further layer of Reed Solomon block coding and fragmentation if required; this is especially attractive for uni-directional or low Quality of Service (QoS) networks. EDI utilizes open internet standards, and can be configured for operation over uni-directional unicast and multicast UDP/IP, and connection based TCP/IP, including MTU adaptations. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7 Data applications | |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.1 Introduction | As a digital broadcast delivery platform, DAB is able to carry data services that may compliment the radio services or provide independent services. This clause 7 provides a guide to the most relevant data applications. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.2 SlideShow | ETSI TS 101 499 [i.17] describes the techniques required to deliver a sequence of slides which carry information in the form of images. The main use for this user application will be in context with a programme service component. Examples are: news programme items complemented by photos from the reported events and programme items with popular songs accompanied by photographs of the performers or the covers of their issued CDs. Two modes are possible: on simpler devices, the Slide Show Application is service provider driven and does not require any interaction from the end-user of the corresponding service component: each slide appears automatically on the display and will be replaced under the control of the service provider according to the needs of his service. For other devices, a categorized SlideShow may be shown, which allows the user to select groups of images for interactive playback. Hybrid radio provisions are included to allow a seamless experience for users when consuming radio services delivered by DAB or IP or a combination of both. The content may be created once by the service provider for delivery by both mechanisms and manufacturers may implement decoders with many common elements. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.3 Service and Programme Information (SPI) | |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.3.1 Introduction | The Service and Programme Information (SPI) is designed to allow for an enhanced radio experience. It may be implemented at various levels, since it is divided into Service Information (SI), Programme Information (PI) and Group Information (GI). The SPI is applicable to hybrid radio (i.e. broadcast and/or IP delivery) and allows a broadcaster considerable flexibility in the provision of metadata. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 15 |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.3.2 SPI xml | ETSI TS 102 818 [i.18] defines the XML schema data model for the hybrid SPI, covering Digital Audio Broadcasting (DAB), Digital Radio Mondiale (DRM) and RadioDNS. It can be used for transmitting station logos and other service information, programme schedule data and grouping to EPG applications on receivers, and for exchanging such information between broadcasters, network operators and content providers. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.3.3 SPI binary | ETSI TS 102 371 [i.19] describes the process to compress the SPI data for transmission over a DAB transmission channel to reduce the transmitted bit-rate and to profile the data for a range of different receiver capabilities. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.4 Filecasting | ETSI TS 103 177 [i.20] specifies the Filecasting user application which permits the non-linear delivery of multimedia content using DAB. Whilst the main focus is the delivery of audio files over a broadcast network, it is also applicable to other media formats too, such as video files and documents which may contain a mixture of formatted text and graphics, for example in pdf format. Filecasting can be used by broadcasters with existing DAB linear audio services to deliver additional content associated (but not necessarily directly linked) with these audio services. Equally it can be used to create standalone Filecast services. This content could be an entire programme (podcast), additional short-form content relating to a linear radio programme, or news, weather or traffic bulletins. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.5 Text applications | |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.5.1 DL Plus | ETSI TS 102 980 [i.21] describes an extension to the DAB Dynamic Label X-PAD application (see ETSI EN 300 401 [i.1]) to allow listeners to select the kind of textual information they are interested in. For that purpose DL messages are complemented by tags which identify specific content of the DL message by a content type. Users can select the content types of information to be presented; they do not need to read, or even be aware of, the complete stream of DL messages. DL Plus is a backwards compatible extension of the DL feature: the transmitted tags are not visible in the DL message so that listeners with receivers without a DL Plus decoder still view the DL messages as before. For the broadcaster, the additional data rate (for tag transmission) is significantly less than the data rate necessary for text. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.5.2 Journaline® | ETSI TS 102 979 [i.22] describes a text based information service for digital radio, optimized for simple data aggregation and re-use, which is highly efficient in broadcast transmission. It supports the widest range of receiver types, from low-cost solutions with a small text display up to high-end receivers with graphical user interfaces and optional text-to-speech playback. The radio user can access the information provided by the radio station which is comparable to teletext for TV. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.6 DMB | ETSI TS 102 428 [i.23] specifies the user application for video services carried via DAB. It also includes profile definitions for the application. It defines the components of the video services; the content compression, the synchronization mechanism and multiplexing mechanism, allowing video services to be delivered to suitably equipped terminals. ETSI TS 102 428 [i.23] also specifies the way that DMB may be used to deliver radio services, and although such services were envisaged and trialled, this usage has not continued due to the better technical performance of DAB+ audio. The use of DMB for radio services is strongly discouraged. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 16 |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.7 TPEG | ETSI TS 103 551 [i.24] specifies the standardised method to transport TPEG services over DAB. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.8 OMRI | ETSI TS 103 632 [i.41] specifies an Application Programming Interface (API) for the Open Mobile Radio Interface (OMRI) which can be used by application developers to gain access to broadcast radio tuners in consumer electronic devices such as smartphones, tablets and/or other devices, and which allows the execution of program code often referred to as apps. |
f48081bd805749985fb8401c02d17713 | 101 495 | 7.9 Filtered Information Service (FIS) | ETSI TS 103 689 [i.42] specifies the Filtered Information Service (FIS) data application that allows service providers to deliver information to groups of receivers with configurable filters, for example, text language, model number, date of registration, etc. The XML framework and transport specification are defined. |
f48081bd805749985fb8401c02d17713 | 101 495 | 8 Receiver specifications | |
f48081bd805749985fb8401c02d17713 | 101 495 | 8.1 Introduction | The DAB standards originally specified only the process to generate the signal on the air, but as the implementation has rolled out, it became clear that aspects of receiver behaviour needed to be specified. Almost all the DAB standards include provisions to specify the correct interpretation of the signalling provided in a received DAB ensemble without being prescriptive about how the implementation is made. |
f48081bd805749985fb8401c02d17713 | 101 495 | 8.2 Minimum requirements | ETSI TS 103 461 [i.25] describes the minimum requirements for digital radios, both domestic and in-vehicle, and the necessary test methods that lead to compliance with the requirements. It may be used as the technical basis for a Digital Radio Certification Mark scheme. A Digital Radio Certification Mark is designed to be used on product packaging and provides an easily recognized mark to correspond to public information campaigns on the necessary requirements for consumers to make a switch to digital radio. Manufacturers are, of course, free to include additional features or increased performance compared to the minimum requirements specified. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9 Historical DAB specifications | |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.1 Introduction | The DAB system has been developed extensively during its lifetime and many ideas were considered and standardised but later were superceded or otherwise found to be of limited value. For completeness, this clause 9 describes those documents since they are still publically available. However, implementations according to these specifications are largely historical and limited to trial and experimental broadcasts and equipment. The specifications in this clause 9 have been marked as "Historical" in the ETSI Work Programme. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.2 Guidelines for Implementation and Operation | ETSI TR 101 496 [i.26] was developed by the Eureka Project 147 as the major companion document to ETSI EN 300 401 [i.1]. ETSI TR 101 496 [i.26] was developed in three parts, covering: Outline and Features; System Features; and Broadcast Network, giving considerable detail and explanations to help to implement DAB systems and develop conformant equipment. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 17 ETSI TR 101 496 [i.26] is now of only historical interest, since it corresponds to ETSI EN 300 401(V1.3.3) [i.1] published in 2001, and so does not reflect the current status and should not be used to understand the present requirements of DAB equipment and services. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.3 Rules of operation for MOT | ETSI TR 101 497 [i.27] provides guidance on the use of V1.1.1 and V1.2.1 of the MOT specification [i.8]. It is not relevant to V2.1.1 and later versions of the MOT specification [i.8]. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.4 Broadcast Web Site | ETSI TS 101 498 [i.28] describes the Broadcast Web Site application which gives the opportunity to use HTML as a content format to support information services. This concept allows a service provider to deliver an entire web site to a receiver using only the broadcast channel of DAB and without the need for any form of return channel. The idea was considered to be of interest when published, but the widespread availability of mobile IP connectivity, and the necessity for a back-channel for most web based services has rendered the BWS obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.5 Service planning | ETSI TR 101 758 [i.29] describes the general principles for deriving the necessary field strength and compatible receiver sensitivity for satisfactory operation of a DAB system. It has not been maintained, since such planning guidance is more generally provided by regulatory authorities, often referencing the work of the European Broadcasting Union (EBU). 9.6 Java™ ETSI TS 101 993 [i.30] specifies a DAB related API for Java. This API enables the download of Java programs via DAB and the control of their execution. Additionally, it provides an interface to the functionality of DAB. A DAB extension to the Java API has been designed to provide the software framework for designing, implementing and executing portable applications specifically targeted to the DAB system. The DAB Java Framework is divided in three basic modules or packages: a DAB specific extension of the Java API, a runtime support for the DAB applications execution environment, and a DAB I/O package for signalling the DAB Java extension over the DAB signal. The idea was considered to be of interest when published, but the widespread availability of mobile IP connectivity, and the necessity for a back-channel for most web based services has rendered DAB Java obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.7 TMC | ETSI TS 102 368 [i.31], developed by the TMC Forum in collaboration with the WorldDAB Forum, describes the mapping required to deliver TMC data via DAB transmission. However, the development and deployment of TPEG, which includes the encapsulation of TMC services, has rendered this specification obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.8 Voice applications | ETSI TS 102 632 [i.32] builds upon the BWS specification by providing the capabilities to allow a voice interface. This is especially useful to some mobility cases where the user is doing other things while using the system such as driving a car or crossing the street. The specification, like BWS, is now obsolete. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 18 |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.9 Middleware | ETSI TS 102 635 [i.33] establishes a standard for a platform-independent environment, where executable applications can be signalled and transferred to a receiver via a broadcasting network and executed on the receiver. It does not suppose the exclusive use of a specific broadcast network but defines the commonly-required specifications among diverse broadcast networks. It includes the definitions of basic data formats, protocols to deliver data, to signal downloadable applications and to download them, ways to denote resources on broadcast networks, and detailed interfaces among receiver platform, broadcast and communication networks, and the applications. This is specified in part 1 of [i.33]. In order to apply the present document to a target broadcast network, it is required to map abstract interfaces to concrete entities of the network and to add additional definitions specific to the network. This is specified in part 2 for DAB. Similar to the reasons for the demise of DAB Java, the Middleware specification is now obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.10 Intellitext | ETSI TS 102 652 [i.34] describes an extension to the DAB Dynamic Label X-PAD application (see ETSI EN 300 401 [i.1]) to enable hierarchical-menu-driven text services on a compatible receiver. The data is compiled into a simple Teletext-like database of information which the user of any DAB radio equipped with this application can browse on demand. Intellitext messages are a special form of DL messages, formatted in such a way that receivers not supporting Intellitext will continue to function normally. The Intellitext system provides a means for broadcasters to control the lifetime and basic formatting of broadcast information, while the display of information is user-driven. Intellitext was used on-air for some years and implemented in some receivers. However, the specification is now unused and obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.11 IPDC services | ETSI TS 102 978 [i.35] specifies the transport of IPDC services using the MSC stream mode of DAB (ETSI EN 300 401 [i.1]) including additional error protection (ETSI TS 102 427 [i.10]). IPDC services, e.g. audio and video services, are packetized and synchronized using RTP and appropriate RTP payload format specifications. For efficiency, some appropriate restrictions to MPEG-2 TS and an efficient transmission method for PSI/SI and SAT sections are specified. ETSI TS 102 978 [i.35] also specifies methods of macro and micro time slicing for power-efficient transmission of IPDC Services in DAB systems. The methods for sub-channel synchronization and data arrangement are specified. The development of IPDC services has generally required the use of a back-channel. This specification is now obsolete. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.12 Mobile internet | |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.12.1 IP tunnelling | ETSI ES 201 735 [i.36], developed by the Eureka Project 147, describes how to transport Internet Protocol (IP) datagrams in a Digital Audio Broadcasting (DAB) packet mode service component, a technique described as "IP tunnelling". The use of IP tunnelling provides DAB with a mechanism for the adaptation of Internet services to DAB and is also a key component for DAB services using two-way interaction with personal DAB. The use of IP tunnelling enables the use of IP as a common network layer protocol, end-to-end, for DAB data services. IP tunnelling through DAB is unidirectional. The tunnel is created from the packet mode encoder on the transmitting side, to the packet mode decoder on the receiving side, of the DAB system. The idea was considered to be of interest when published, but the widespread availability of mobile IP connectivity, and the necessity for a back-channel for most web based services has rendered IP tunnelling, and the associated protocols and interaction channel specifications obsolete. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 19 |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.12.2 Protocols | ETSI ES 201 736 [i.37], developed by the Eureka Project 147, describes the protocol stacks to be used for the different types of services that are defined, as local interactive, one-way interactive and two-way interactive service. The specification also defines a protocol PSSC (Personal DAB Service Session Control) which allows the set up of personal DAB service sessions and functionalities like handover between DAB cells, etc. It also defines the message format to be used and allows for further future extensions. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.12.3 Interaction channel | ETSI ES 201 737 [i.38], developed by the Eureka Project 147, describes the Interaction Channels through Global System for Mobile communication (GSM), the Public Switched Telecommunications System (PSTN), Integrated Services Digital Network (ISDN), Digital Enhanced Cordless Telecommunications (DECT). It describes low level network management and basically references relevant telecommunication standards and describes how the implementation of low level interaction is handled. |
f48081bd805749985fb8401c02d17713 | 101 495 | 9.13 RDS linkage | ETSI EN 301 700 [i.39] describes a standard method for signalling DAB service information to a receiver tuned to a FM-RDS service using the RDS Open Data Application (RDS-ODA) system, as specified in the RDS standard, IEC 62106 [i.40]. Since some DAB services are simulcasts of existing FM services, usually with RDS, it is possible for receivers able to receive both DAB and FM services to present the listener with the DAB service, but it can fall back to the FM service outside the DAB coverage area. DAB provides the signalling, through the service following information in the Fast Information Channel, to enable a receiver to find the equivalent service on FM. ETSI EN 301 700 [i.39] describes the characteristics of an RDS-ODA for providing frequency information for DAB ensembles. Additionally the ODA can signal various Service Information attributes of DAB services thus allowing a receiver to find an equivalent DAB service. Despite the validity of this approach, RDS only receivers have no use of the data that could be signalled using ETSI EN 301 700 [i.39], and DAB/RDS receivers have access to all the information they require from the DAB tuner. Therefore this specification has not been implemented and it is now obsolete. ETSI ETSI TR 101 495 V2.2.1 (2019-11) 20 History Document history V1.1.1 November 2000 Publication V1.2.1 January 2005 Publication V1.3.1 January 2006 Publication V1.4.1 March 2012 Publication V2.1.1 August 2017 Publication V2.2.1 November 2019 Publication |
6eaea832393614ad197614f6c14112b5 | 101 365 | 1 Scope | The purpose of the present document is to analyse the threats due to IN interworking between IN structured network operators and/or service providers using CS2 and CS3. A set of technical requirements will be established in a following document. The present document analyses the attacks which could occur in the interworking relationships, the present document principally considers CS2 and will focus mainly on security problems linked to the use of SCF-SDF, SCF-SCF and SDF-SDF interfaces. These IN interfaces could be either the target of the attack or the means to perform the attack. The present document follows the successive steps: - listing vulnerabilities for IN architecture to the use of SCF-SDF, SCF-SCF and SDF-SDF interfaces; - description of threats (Intentional or accidental) and their impact; - determination of the likelihood of the attack based on the motivation of the attacker; - production of a risk assessment. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] ETR 339: "Intelligent Network; IN interconnect business requirements". [2] ITU-T Recommendation Q.1221: "Introduction to Intelligent network Capability Set 2". [3] ITU-T Recommendation Q.1224: "Intelligent Network Distributed Functional Plane for Capability Set 2". [4] ITU-T Recommendation Q.1228: "Intelligent Network Interface Capability Set 2". [5] ETR 332: "Security techniques Advisory Group (STAG); Security requirements capture". [6] ETR 232: "Security techniques Advisory Group (STAG); Glossary of security terminology". [7] ETR 083: "Universal Personal Telecommunication (UPT); General UPT security architecture". |
6eaea832393614ad197614f6c14112b5 | 101 365 | 3 Definitions and abbreviations | |
6eaea832393614ad197614f6c14112b5 | 101 365 | 3.1 Definitions | For the purposes of the present document, the following definitions apply: masquerade (« spoofing »): The pretence of an entity to be a different entity. This may be a basis for other threats like unauthorized access or forgery. ETSI TR 101 365 V1.1.1 (1998-07) 6 unauthorized access: An entity attempts to access data in violation to the security policy in force. eavesdropping: A breach of confidentiality by monitoring communication. loss or corruption of information: The integrity of data (transferred) is compromised by unauthorized deletion, insertion, modification, reordering, replay or delay. replay of information: The repetition of previously valid commands and responses with the intention of corrupting service or causing an overload. repudiation: Denial by one of the entities involved in a communication of having participated in all or part of the communication. forgery: An entity fabricates information and claims that such information was received from another entity or sent to another entity. denial of service: The prevention of authorised access to resources or the delaying of time critical operations. unauthorized activity: An attacker performs activities for which he has no permission or which are in contradiction of an interconnect agreement. The definitions of the other security terms used in this document can be found in [6]. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CS2 Capability Set 2 CS3 Capability Set 3 CCF Call Control Function CCAF Call Control Access Function IN Intelligent Network IP Intelligent Peripheral INAP Intelligent Network Application Part ISUP ISDN User Part ITU International Telecommunications Union IWF InterWorking Function OS Operation System OSF Operation System Function SCF Service Control Function SCP Service Control Point SDF Service Data Function SDP Service Data Point SMP Service Management Point SMAP Service Management Access Point SRF Specialized Resource Function SCEP Service Creation Environment Point SSF Service Switching Function SSCP Service Switching Control Point SS7 Signalling System number 7 TMN Telecommunication Management Network |
6eaea832393614ad197614f6c14112b5 | 101 365 | 4 Introduction | As stated in the principles of Intelligent Network of ITU-T Recommendation Q.1201. "The term Intelligent Network (IN) is used to describe an architectural concept which is intended to be applicable to all telecommunication networks. IN aims to ease the introduction of new services based on a greater flexibility and new capacities". ETSI TR 101 365 V1.1.1 (1998-07) 7 With the introduction of Capability set 2 (CS2) which permits interconnection of IN networks, proprietary security solutions are not sufficient due to the lack of interoperability. Moreover the definition of interfaces for interworking between IN-structured networks require new security solutions. Compared to the single network problem the security issues are changed and made more demanding. These objectives require an adequate level of security to meet the requirements specified in [1]. A threat analysis according to the principles established by TC Security in [5] is therefore needed. Such a threat analysis is the main goal of the present document. 5 Security requirements for interconnected networks, as derived from business requirements ETR 339 [1] lists business requirements and security aspects as seen from the objectives of customers, operators, economic entities and legislative entities. Security requirements applicable to the IN interfaces between functional entities have been extracted from the business requirements and aggregated. The following high level security requirements, applicable to interconnected networks, were identified: - availability and reliability of IN interconnections; - confidentiality (related to certain service data and personal data); - integrity of data (especially related to charging and billing information); - accountability of service operations; - quick recovery from security and integrity failures. A successful implementation of the security objectives and the management of the mechanisms are also highly dependent on close co-operation and agreements between operators. Co-ordination of security policies is required. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 6 System description | To analyse security problems for IN interconnect, the three following diagrams have been studied. These diagrams are based on reference model to be found in [2], [3] and [4]. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 6.1 Basic block diagram | Two networks A and B may use some bidirectional interconnection arrangement to carry the information flows between them. An intruder may try to attack this interconnection arrangement. ETSI TR 101 365 V1.1.1 (1998-07) 8 Intruder control information (INAP) circuit and related signalling (ISUP,etc) Network or service provider A Network or service provider B interconnection arrangement Management Network Management Network IN entities IN entities Signalling network signalling network Figure 1: Principle 7 networks interconnection |
6eaea832393614ad197614f6c14112b5 | 101 365 | 6.2 Block diagram at the functional level | When two networks communicate to each other, the system description at the functional level can be shown as follows: SRF SDF SCF SSF CCF CCAF SDF SCF SSF CCF Network operator or service provider A Network operator or service provider B IN entities Interconnect IN interface Management interface Intruder Internal Management OSF Interconnecting Arrangement OSF SMF SMF other interface SRF Figure 2: Functional level of network interconnection NOTE : a) The OSF-OSF relates to the TMN. b) A network operator or service provider need not employ all entities shown. ETSI TR 101 365 V1.1.1 (1998-07) 9 |
6eaea832393614ad197614f6c14112b5 | 101 365 | 6.3 Block diagram at the physical level | When two networks communicate with each other, the system description at the physical level can be shown as follows: The following diagram describes a possible physical representation, (all entities shown need not be used in a specific network). Network A Network B terminal terminal IP IP SCP SCP SDP SDP SMP SMP SMAP SMAP SCEP SCEP SSP/SSCP SSP/SSCP Intruder Intruder INAP signalling signalling SS7 ISUP Figure 3: Physical level of network interconnection |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7 Threat analysis | |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.1 On vulnerabilities Threats and Intruders | The standardisation of the architecture concept of IN leads to a distribution of information (data, logic) over different entities defined in the distributed plane of IN conceptual model. This distribution introduces new vulnerabilities on the communication between entities. The vulnerabilities on communication are similar within networks and between networks but the threats and the way to reduce them are different. Generally, between two systems linked by a communication medium, the vulnerabilities are sorted in different families: - vulnerabilities on communication path; - vulnerabilities of connected « applications » running on the systems; - vulnerabilities in network layer implementation; - vulnerabilities of the operating system used in the system; - vulnerabilities due to historical, legislative and management constraints; - vulnerabilities linked to imperfection and tolerance. In the present document, only the first three families are analysed. In practical application the other vulnerabilities should be taken into account. ETSI TR 101 365 V1.1.1 (1998-07) 10 The principal threats considered are: - masquerade (« spoofing »); - unauthorized access; - eavesdropping; - loss of information; - corruption of information; - forgery; - repudiation; - denial of service; - replay of information; - unauthorized activity. The above mentioned threats can be put into effect by different types of intruders. Such intruders can be separated in the following main categories: - external intruders; - intruders within an organisation (unfaithful servants); - accidental intruders (for instance due to lack of technical knowledge). The external intruders are likely to be motivated by the opportunity to gain something for their own purpose and/or cause problems for the organisation being attacked. Internal intruders are likely to have personal motives, or act as agents for other organisations. The third category need not be a malicious intruder, but may act as one due to incompetent or careless behaviour. In the new liberalised environment, many new entrants without previous experience in telecommunications can be foreseen. Consequently, this area should also be addressed in a comprehensive threat analysis. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2 List of threats | In the following, the threats mentioned above are described, and possible attack methods are considered. The resulting impact is given. For information, some countermeasures are mentioned, however they will be studied in detail in a following document. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.1 Masquerade (« spoofing ») | Description Masquerade is the pretence of one entity to be a different entity. There are different forms of masquerade attacks such as an interleaving attack which is a masquerade which involves the use of information derived from one or more ongoing or previous authentication exchanges. In order to perform such an attack, the first step will typically consist in obtaining access data through some means and then using it to obtain irregular access. Possible Attack Methods - tapping onto a link when a genuine entity has already established an interconnecting session on that link; - let one entity on the interconnecting link falsely take on the identity of an other entity which it may or may not otherwise legitimately represent. ETSI TR 101 365 V1.1.1 (1998-07) 11 Impact - reduction in quality of service provided; - loss of confidence in the system; - reporting of spurious faults; - the suppression of genuine fault reports; - generation of false data; - service being illegally obtained causing loss of privacy; - denial of service to the genuine entity; - loss of information which could degrade the quality of service provided, lead to incorrect fraud handling and lead to a loss of confidence in the system; - loss of revenue; - inability to prevent fraud; - loss of confidentiality. Possible countermeasures - entity authentication; - message authentication; - access control to authentication data; - encryption; - physical protection. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.2 Unauthorized access | Description An attacker gains access to a system or application to which he/she does not have the required permission. Possible Attack Methods - exploiting system weaknesses; - misconfiguring equipment; - masquerading as an entity with higher access permission. Impact - loss of confidentiality; - loss or corruption of information; - forgery; - denial of service; - theft of service. ETSI TR 101 365 V1.1.1 (1998-07) 12 Possible countermeasures - well defined access control; - authentication; - security policy; - properly controlled configuration. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.3 Eavesdropping | Description Unauthorised listening in to communications, resulting in a breach of confidentiality. Possible Attack Methods - using protocol or routing tools to redirect traffic to another network; - attaching a protocol analyser to any accessible link; - use of a device for eavesdropping and compromising switches used for the communication; - illegal use of lawful interception facilities. Impact - loss of confidentiality of customer data; - loss or confidentiality of service information data; - loss of confidentiality of managemant information; - loss of confidentiality of charging information; loss of confidentiality of authentication data. Possible Countermeasures - encryption of transmitted information; - access control to transmission medium; - physical protection; - specific network configuration to reduce vulnerabilities. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.4 Loss of information | Description The destruction of information which may be stored or in transit along a path of communication. Possible Attack Methods - incorrect routing and addressing of messages; - introducing severe message delays; - various forms of blocking or interruptions preventing access or communication; - unauthorized deletion of data; - system or equipment failures with subsequent loss of data. ETSI TR 101 365 V1.1.1 (1998-07) 13 Impact As a result, different types of data may be lost e.g. protocol and handling information, service data (charging data, call records), customer data (profiles) and general system data. The robustness of the protocols and system implementation will decide to what extent the lost information can be recovered quickly via mechanisms such as retransmission, rerouting, back up etc. The impact on service operation will depend on what kind of data is lost, and whether this data can be recovered or not. Some examples of possible consequences of losing sensitive information without instant recovery are: - reduced reliability and QoS due to disruption of services; - reduced availability due to denial of service; - complete loss of service; - reduced quality of statistics and surveillance data for management purposes; - reduced security level due to disruption of security procedures (access control, authentication, logging etc.); - reduced trust, reputation and market share; - reduced income due to loss of charging records (if carried over IN interfaces). Possible countermeasures - secure access control; - protection of addressing and routing labels; - comprehensive data recovery features; - sequence control of messages; - checked acknowledgement of messages. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.5 Corruption of Information | Description The compromise of data integrity by unauthorized insertion, modification or reordering. Possible attack methods - modifying transmitted information; - modifying stored information, e.g. by masquerading or bypassing access control. Impact - incorrect routing and addressing of messages; - various forms of interruption preventing access or communication; - unauthorized modification of information; - denial of service; - incorrect billing; - loss of trust; - loss of customers. Possible Countermeasures - secure numbering of messages in combination with message integrity checks; ETSI TR 101 365 V1.1.1 (1998-07) 14 - security alarming; - secure access control; - Message Authentication Code; - digital signature. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.6 Forgery | Description An entity fabricates information and claims that such information was received from another entity or sent to another entity. Possible Attack Methods - Fraudulent charging by a network operator (resulting in charging of events that did not exist or the wrong amount) can occur. This malevolent network operator can be the originating network one of the transit networks or the destination network. - A network operator can also fabricate false messages involving other entities and then claim that such requests were received from another entity or sent to another entity. The communicating network will have to deal with those requests without be paid for that later on. Impact - loss of revenue; - loss of trust; - technical breakdown; - possible extra costs for the network operators and/or users. Possible countermeasures - strong agreements between operators, discouraging irregular behaviour; - audit; - mutually agreed security policies; - authentication mechanisms; - digital signature. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.7 Repudiation | Description One or more users involved in a communication deny participation, a critical threat for electronic financial transactions (billing) and electronic contractual agreements. Possible attack methods - denial of transmission; - denial of receipt; - denial of having accessed data in a database; - denial of having modified data in a database. Impact ETSI TR 101 365 V1.1.1 (1998-07) 15 - loss of revenue; - loss of trust; - loss of customers. Possible countermeasures - digital signature; - cryptosystems using Trusted Third Party; - independent audit; - strong agreements between operators, discouraging irregular behaviour. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.8 Denial of service | Description An entity fails to deliver its service or prevents other entities from delivering their services. Possible Attack Methods - interfering with signalling; - modifying stored information; - deliberate congestion; - removing resources from service; - physical destruction of equipment; - misconfiguration of a component; - interfering with cryptosystems. Impact - inability to perform desired functions; - service failure; - degradation of service; - loss of income; - loss of reputation; - loss of customers. Possible countermeasures - message authentication code; - digital signature; - physical protection; - access control; - security alarms; - automatic event handling; - event monitoring. ETSI TR 101 365 V1.1.1 (1998-07) 16 |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.9 Replay of information | Description The repetition of previously transmitted information. The intention may be to corrupt service, causing overload or disruption. Possible Attack Methods - replay with modification of security procedures (e.g sequence number change); - replay of a message (protocol data, system data, user data, etc…). Impact - overload; - overcharging; - loss of revenue; - loss of trust; - loss of customers; - corruption of service; - denial of service; - masquerade. Possible countermeasures - message authentication code in combination with sequence numbers and/or time stamps; - digital signature; - event monitoring. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.2.10 Unauthorized activity | Description An attacker performs activities for which he has no permission or which are in contradiction of an interconnect agreement. Possible Attack Methods - exploiting system weaknesses; - misconfiguring equipment. Impact - false service; - disruption of service; - denial of service. Possible countermeasures - event monitoring; - authorisation; - security policy; ETSI TR 101 365 V1.1.1 (1998-07) 17 - configuration control. |
6eaea832393614ad197614f6c14112b5 | 101 365 | 7.3 Risk analysis | The following table gives an evaluation of the main attack scenarios identified .For each attack scenario the likelihood and the impact have been evaluated in order to get the risk assessment of the attack method according to the method described in [5]. For the risk assessment the occurrence likelihood of threats is estimated from low to high. The meaning of the likelihood estimation of a particular threat is explained as follows: Table 1: Likelihood L Low According to up-to-date knowledge, a possible attacker needs to solve strong tech- nical difficulties to state the threat, or the motivation for an attacker is very low. M Medium The technical requirements necessary to state this threat are not too high and seem to be solvable without big effort; furthermore, there must be a reasonable motivation for an attacker to perform the threat. H High There are no sufficient mechanisms installed to counteract this threat, and the motivation for an attacker is quite high. The impact of a threat is also estimated from low to high. The meaning of the impact evaluation is explained as follows: Table 2: Impact L for "low impact" The concerned party is not harmed very strongly; the possible damage is low. M for "medium impact" The threat addresses the interests of providers / subscribers and cannot be neglected. H for "high impact" A basis of business is threatened and severe damage might occur in this context. The risk assessment is derived from the likelihood and the impact according to table 3: Table 3: Derivation of the risk assessment Likelihood Impact Risk assessment L L L M L L H L M L M L M M M H M H L H M M H H H H H The risk assessment of a threat is then derived and estimated from low to high. The meaning of the risk assessment is explained as follows: ETSI TR 101 365 V1.1.1 (1998-07) 18 Table 4: Risk L for "minor risk" Minor risks arise, if either no essential assets are concerned, or the respective attack is unlikely. Threats causing minor risks have no primary need for countermeasures. M for "major risk" Major risks are represented by threats on relevant assets which are likely to occur, even if their impact is less fatal. Major risks should be handled seriously and should be minimised as soon as possible. H for "critical risk" Critical risks arise, when the primary interests of the providers / subscribers are threatened and when a potential attacker's effort to harm these interests is not high. Critical risks must be minimised with highest priority. ETSI TR 101 365 V1.1.1 (1998-07) 19 Table 5: Risk Assessment Attack scenario Threat Reference Motivation Likelihood Im-pact Risk Assess ment 1 Masquerading as a SCP in order to reduce or disable network capabilities 7.2.1 sabotage, financial L H M 2 Masquerading as a SDP 7.2.1 financial (number portability case), breach of confidence, sabotage L H M 3 Masquerade as a SCP to pervert network service. 7.2.1 malice ; destroy reputation ; financial L H M 4 Abuse of access privileges via an SCP or SDP against/to an SCP or SDP 7.2.2 financial, sabotage M H H 5 Subversion of OSF (e.g. insider attack leading to control over IN entities) 7.2.2 7.2.6 financial, commercial, revenge, espionage, denial of service, masquerading H H H 6 Eavesdropping on a SDP-SDP interconnection in order to get customer information 7.2.3 financial, gathering intelligence, Interesting information can be : location, authentication information, privacy, billing information, management information M H H 7 Eavesdropping on an SCP-SDP relationship 7.2.3 financial ; commercial ; espionage; personal espionage ; breach of privacy H H H 8 An SCP deletes/modifies information (user data, system data, charging data) in an SDP 7.2.4 7.2.5 destroy reputation ; financial. This could also happen accidentally M H H 9 Generation, deletion or modification of charging information in transit (assuming that IN entities may be used for charging in future) 7.2.4 7.2.5 financial, destruction of reputation H H H 10 Disruption of maintenance state by modification of transmitted data 7.2.5 sabotage, destruction of reputation L M L 11 Disruption of the distribution of service logic from the SMP/OS towards an SCP or an IP 7.2.5 sabotage, destruction of reputation, commercial M H H 12 Modification of routing information 7.2.5 commercial, espionage M H H 13 An SCP delivers incorrect routing information 7.2.5 7.2.6 financial, commercial, destruction of reputation. This could also happen accidentally M H H 14 An SCP sends wrong charging information to another network (assuming that IN entities may be used for charging in future) 7.2.6 financial This could also happen accidentally M H H 15 Generation of false traffic for purposes of fraud a) to gather interconnect charges for premium rate service fraud other value added service fraud 7.2.6 7.2.9 financial, commercial H H H 16 An operator denies that his SCP has sent or received charging information 7.2.7 financial, commercial M M M 17 An SCP or SDP is made unavailable (e.g. by message flooding) 7.2.8 denial of service, sabotage destruction of reputation, denial of service obligation, commercial advantage. This could also happen accidentally M H H 18 Running a rogue service by a network against an other network 7.2.10 financial, This could also happen accidentally M H H ETSI TR 101 365 V1.1.1 (1998-07) 20 Table 6: Risk assessment evaluation 19 Data trawling against an SDF, within an SCP or SDP 7.2.10 financial, espionage (personal and commercial information), marketing intelligence M H H ETSI TR 101 365 V1.1.1 (1998-07) 21 History Document history V1.1.1 July 1998 Publication ISBN 2-7437-2409-9 Dépôt légal : Juillet 1998 |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 1 Scope | The present document contains detailed guidelines to be used in association with ETSI TS 101 674-2 [2]. It provides additional details for a "Framework Solution" for Network Management (NM) to support interconnections between European ATM network management platforms utilized for the provision of (semi-) permanent Virtual Path and Virtual Channel connections. It addresses NM requirements, processes and interface specifications. The Framework for Inter-operator Processes and Interface Specifications covers all NM functional areas where network interoperability and agreements are needed to support ATM interconnection services. The information contained in the present document is restricted to a level of functionality which is considered to be practicable for an initial phase of implementation, - i.e. a "Phase 1" specification. The present document identifies working details that need to be agreed between operators to establish interconnect services. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] ETSI TS 101 674-1: "Technical Framework for the provision of interoperable ATM services; Part 1: NNI-Interface User and Control plane specification (including network functions and service aspects) Phase 1". [2] ETSI TS 101 674-2: "Technical Framework for the Provision of Interoperable ATM Services; Part 2: Network Management (X-Interface) Specification for Phase 1 Implementation". [3] EURESCOM P813 Deliverable 3: "Broadband Service Operator Interconnect Handbook". [4] ETSI ETS 300 298-1: "Broadband Integrated Services Digital Network (B-ISDN); Asynchronous Transfer Mode (ATM); Part 1: B-ISDN ATM functional characteristics [ITU-T Recommendation I.150 (1995)]". [5] ETSI ETS 300 298-2: "Broadband Integrated Services Digital Network (B-ISDN); Asynchronous Transfer Mode (ATM); Part 2: B-ISDN ATM layer specification [ITU-T Recommendation I.361 (1995)]". [6] ETSI EN 300 820-1: "Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 1: Configuration Management". [7] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network". [8] EURESCOM P408 Pan-European TMN - Experiments and Field Trial Support Deliverable 6: "Specifications of the Xcoop Interface for ATM Network Management: (Tests specified in D6 Volume 4 Annex 3: Laboratory Methods and Abstract test suites for validation of the Xcoop interface". [9] EURESCOM P612 Deliverable 2, Volume 2 (1998): "TMN X-interface Specifications for Trouble Ticketing". ETSI ETSI TR 101 477 V1.1.1 (2000-06) 13 [10] ETSI EN 300 820-2: "Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: alarm management". [11] EURESCOM Project P811 Deliverable 1 (1999): "Reference Framework for OSS Interconnection". [12] ITU-T Recommendation I.371 (1996): "Traffic control and congestion control in B-ISDN". [13] ITU-T Recommendation M.1400 (1997): "Designations for International Networks", including Amendment 1. [14] ATM Forum Traffic Management Specification, version 4.1, 1999. [15] EURESCOM Project P707: General information in Deliverables 2 and 3. [16] EURESCOM P813 Deliverable 4: "Requirements for network management of switched ATM services and IP VPN Quality of service". [17] ITU-T Recommendation X.700 (1992): "Management Framework For Open Systems Interconnection (OSI) For CCITT Applications". [18] ITU-T Recommendation I.751 (1996): "Asynchronous transfer mode management of the network element view". [19] ETSI ETS 300 469 (1998): "Broadband Integrated Services Digital Network (B-ISDN); Asynchronous Transfer Mode (ATM); Management of the network element view [ITU-T Recommendation I.751 (1996)]". [20] ITU-T Recommendation X.721 (1992): "Information technology – Open Systems Interconnection – Structure of management information: Definition of management information". [21] ITU-T Recommendation M.3100 (1992): "Generic network information model". [22] ETSI ES 200 653: "Telecommunications Management Network (TMN); Network level generic class library". [23] ITU-T Recommendation I.630 (1998): "ATM protection switching". [24] "Towards Resilient Networks and Services" (undated), P. Georgatsos and Y. T'Joens, from Guideline NIG-G5 of the NIG Chain (taken from the EU ACTS projects). [25] EURESCOM P612 Deliverable 1, Volume 3, Annex B (1997): "Harmonised rRequirements for trouble ticketing". [26] ITU-T Recommendation M.1530 (1992): "Network maintenance information". [27] ITU-T Recommendation M.3208.1 (1997): "TMN management services for dedicated and reconfigurable circuits network: Leased circuit services". [28] ITU-T Recommendation X.790 (1995): "Trouble management function for ITU-T applications". [29] ITU-T Recommendation M.1540 (1994): "Exchange of information for planned outages of transmission systems". [30] ITU-T Recommendation M.1550 (1992): "Escalation procedure". [31] ITU-T Recommendation M.1560 (1992): "Escalation procedure for international leased circuits". [32] ETSI EN 300 820-3: "Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 3: VP Performance management ". ETSI ETSI TR 101 477 V1.1.1 (2000-06) 14 [33] EURESCOM Project P708, Deliverable 2 (1999): "Xcoop Specification for ATM VP Performance Management". [34] EURESCOM Project P708 Deliverable 1, Part 1: "Usage Measurements for Accounting Management – The Xcoop Interface". Also Deliverable 3 (1999): "Specification of accounting Management for the Xcoop Interface". [35] ITU-T Recommendation D.224: "Charging and Accounting Principles for ATM/B-ISDN". [36] EURESCOM Project P710: General reference to all Deliverables. [37] EURESCOM Project P708, PIR7.3 version 1 (1999). [38] EURESCOM Project P708 Deliverable 5 (1999): "Proposed enhancements to ETSI standards (EN 300 820-1 and EN 300 820-2)". [39] OMG CORBA 2.2/IIOP Specification (1998). Available at: http://www.omg.org/library/c2indx.html and: ftp://ftp.omg.org/pub/docs/formal/98-07-01.pdf. [40] ETSI TS 101 675-1: "Technical Framework for the Provision of Interoperable ATM Services; Network-Network Interface (NNI) User and Control Plane Specification". (Including Network Functions and Service Aspects) Phase 2". [41] ETSI TR 101 673 (V1.1): "Technical Framework for the Provision of Interoperable ATM Services; Overview". [42] Void. [43] ITU-T Recommendation E.191 (1996): "B-ISDN numbering and addressing". [44] ITU-T Recommendation E.164 (1997): "The international public telecommunications numbering plan". [45] ITU-T Recommendation D.170 (1998): "Monthly telephone and telex accounts". [46] ITU-T Recommendation D.285 (1996): "Guiding principles for charging and accounting for intelligent network supported services". [47] ITU-T Recommendation D.232 (1997): "Specific tariff and accounting principles applicable to ISDN supplementary services". [48] ITU-T Recommendation D.230 (1995): "General charging and accounting principles for supplementary services associated with international telecommunication services provided over the Integrated Services Digital Network (ISDN)". [49] ITU-T Recommendation D.225 (1997): "Charging and accounting principles to be applied to frame relay data transmission service". [50] ITU-T Recommendation D.212 (1996): "Charging and accounting principles for the use of Signalling System No. 7". [51] ITU-T Recommendation D.211 (1998): "International accounting for the use of the signal transfer point and/or signalling point for relay in Signalling System No. 7". [52] ITU-T Recommendation D.210 (1994): "General charging and accounting principles for international telecommunication services provided over the Integrated Services Digital Network (ISDN)". [53] IETF RFC 2078 (1997): "Generic Security Service Application Program Interface, Version 2" - J. Linn. [54] ITU-T Recommendation E.735 (1997): "Framework for traffic control and dimensioning in B-ISDN". [55] ITU-T Recommendation G.805 (1995): "Generic functional architecture of transport networks". ETSI ETSI TR 101 477 V1.1.1 (2000-06) 15 [56] ITU-T Recommendation I.356 (1996): "B-ISDN ATM layer cell transfer performance". [57] ITU-T Recommendation I.357 (1996): "B-ISDN semi-permanent connection availability". [58] ITU-T Recommendation I.610 (1995): "B-ISDN operation and maintenance principles and functions". [59] ITU-T Recommendation M.1510 (1992): "Exchange of contact point information for the maintenance of international services and the international network". [60] ITU-T Recommendation M.1520 (1992): "Standardized information exchange between Administrations". [61] ITU-T Recommendation M.1535 (1996): "Principles for maintenance information to be exchanged at customer contact point (MICC)". [62] ITU-T Recommendation M.3010 (1992): "Principles for a Telecommunications management network". [63] ITU-T Recommendation M.3100 (1995): "Generic network information model", including Corrigendum 1. [64] Void. [65] ITU-T Recommendation M.3400 (1997): "TMN management functions". [66] ITU-T Recommendation O.191 (1997): "Equipment to measure the Cell Transfer Performance of ATM connections". [67] ITU-T Recommendation Q.813 (1998): "Security Transformations Application Service Element for Remote Operations Service Element (STASE-ROSE)". [68] ITU-T Recommendation Q.822 (1994): "Stage 1, Stage 2 and Stage 3 Description for the Q3 interface - Performance management". [69] ITU-T Recommendation X.741 (1995): "Information technology - Open Systems Interconnection - Systems management: Objects and attributes for access control". |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 3 Definitions and abbreviations | |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: ATM Access Point: means by which a subnetwork offers external interfaces to other subnetworks. It is associated with an end point of an IPPL ATM Gateway: represents an ATM access point in one subnetwork, which is associated with an ATM access point in another subnetwork for the purpose of topological interconnection Connection: ATM cell transport entity which is capable of transferring information transparently between connection points. A connection defines the association between the connection points and the connection points delimit the connection Connection Admission Control: set of actions taken by the network at the connection set up phase (or during connection re-negotiation phase) in order to establish whether a virtual channel connection or a virtual path connection can be accepted or rejected Data Communications Network (DCN): dedicated network used to interconnect operators' network management platforms supporting automated X.easi interface processes. (The DCN may be configured as a "closed user group" among these operator's management platforms.) ETSI ETSI TR 101 477 V1.1.1 (2000-06) 16 Inter-PNO Physical Link (IPPL): represents a physical link that offers bi-directional transmission capabilities and connects two subnetworks. Each InterPNOPhysicalLink is terminated by two ATM Access Points which are in charge of emitting failures related to the link or to the access point itself. An IPPL can be realized by any transmission capability (SDH, PDH etc.) Link: "topological component" which describes the fixed relationship between a "sub-network" and another "sub- network" or "access group". It is defined by an access point on one subnetwork, which is associated with an access point on another subnetwork NNI.easi interface: network to network interface in the User and Control Planes, specified in TS 101 674-1 [1] Q-interface: non-specified interface used in a generic sense in the present document to mean any competent means by which an operator manages its internal network technology Subnetwork: "topological component" used to effect routing and management. It describes the potential for "sub- network connections" across the "sub-network". It can be partitioned into interconnected "subnetworks" and "links". Each "subnetwork" in turn can be partitioned into smaller "sub-networks" and "links" and so on. A "subnetwork" may be contained within one physical node. In the present document this partition is not used Subnetwork connection: Subnetwork Connection is capable of transferring information transparently across a subnetwork. It is delimited by connection termination points at the boundary of the subnetwork and represents the association between these connection points. It can be a VP or a VC connection Trouble Ticket: report used to exchange information about the resolution of faults, degradations or provisioning problems between operators. Refer also to ITU-T Recommendation X.790 [28] for a definition of Trouble Management and Trouble Reporting Virtual Channel Connection: ATM cell transport entity formed by a series of connections between the end-points. A Virtual Channel Connection is contained in a Virtual Path Connection. However, over the management interface, this containment need not always be visible Virtual Path Connection: ATM cell transport entity formed by a series of connections between the end-points. A Virtual Path Connection can contain one or more Virtual Channel Connections. However, over the management interface, this containment need not always be visible |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AACC Association Access Control Component ABR Available Bit Rate ABT-DT ATM Block Transfer capability with Delayed Transmission ABT-IT ATM Block Transfer capability with Immediate Transmission ACSE Association Control Service Element AE Application Entity AESA ATM Forum End System Addresses AM Accounting Management API Application Programming Interface AR Availability Ratio ASN.1 Abstract Syntax Notation.1 ASP ATM Service Provider ATC ATM Transfer Capability ATM Asynchronous Transfer Mode ATM-CP ATM Connectivity Provider ATMF ATM Forum ATM-SP ATM Service Provider BW Bandwidth CAC Connection (or Call) Admission Control CANCAN ACTS project, Contract Negotiation and Charging in ATM CBR Constant Bit Rate CCR Chargeable Cell Rate ETSI ETSI TR 101 477 V1.1.1 (2000-06) 17 CDR Connection Detail Record CDV Cell Delay Variation CDV(T) Cell Delay Variation (Tolerance) CER Cell Error Rate CLP Cell Loss Priority CLR Cell Loss Ratio CM Configuration Management CMIP Common Management Information Protocol CMISE Common Management Information Service Element CMR Cell Misinsertion Ratio CORBA Common Object Request Broker Architecture CPE Customer Premises Equipment CPN Customer Private Network CTD Cell Transfer Delay CUG Closed User Group DBR Deterministic Bit Rate DCE Data Communication Equipment DCN Data Communications Network DN Distinguished Name EASI (or easi) ETSI project ATM Services Interoperability EDI Electronic Data Interchange EN European Norm ETNO European Public Telecommunications Network Operators' Association EURESCOM European Institute for Research and Strategic Studies in Telecommunications FM Fault Management FTAM File Transfer, Access and Management GDMO Guidelines for the Definition of Managed Objects GIOP General Inter-ORB Protocol GOM Generic Object Model GoS Grade of Service GSS Generic Security Services GSSC Generic Security Services Component IETF Internet Engineering Task Force IIOP Internet Inter-ORB Protocol IN Intelligent Network IOC Inter-Operator/International Operations Centre IOU Inter-operator Operations Unit IP Internet Protocol IPPL Inter-PNO Physical Link IPsec Internet Protocol security ISA Interconnect Service Establishment ISD Interconnect Service Definition ISDN Integrated Services Digital Network ISO Interconnect Service Operation ITU-T International Telecommunications Union, Telecommunications Standardization Sector JAMES Joint ATM Experiment on European Services LAN Local Area Network LC Link Connection MAE Management Application Entity MBR Maximum Burst Rate MBS Maximum Burst Size MCR Minimum Cell Rate METRAN Managed European Transmission Network MF Management Function MO Managed Object MoU Memorandum of Understanding MSC Management Service Component MTBO Mean Time Between Outages MTP Medium Term Planning NE Network Element ETSI ETSI TR 101 477 V1.1.1 (2000-06) 18 NM Network Management NMF Network Management Forum (now the Telemanagement Forum TMF) NNI Network to Network Interface NNI.easi Network to Network Interface to ETSI Project EASI specification given in [1] NPC Network Parameter Control NRT (or nRT) Non Real Time NSAP Network Service Access point OA Operations Agreement OAM Operations and Maintenance OCPT Operational Contact and Procedural Template OMG Object Management Group OMT Object Modelling Technique ORB Object Request Broker OS Operations System OSE Operational Support Entities, ("manual" interface) OSI Open Systems Interconnection OSS Operations Support System PA Process Administrator PCP Process Control Point PCR Peak Cell Rate PDH Plesiochronous Digital Hierarchy PM Performance Management PNO Providing Network Operator POI Point of Interconnect PSAP Permanent Service Access point PSTN Public Switched Telephone Network PVC Permanent Virtual Channel PVCCTP Permanent Virtual Channel Connection Termination Point PVP Permanent Virtual Path PVPCTP Permanent Virtual Path Connection Termination Point QoS Quality of Service RFS Request For Service ROSE Remote Operations Service Element RT Real Time SALC Security Audit Log Component SBR Statistical Bit Rate SCC Security Control Component SCR Sustainable Cell Rate SDH Synchronous Digital Hierarchy SDL Specification and Description Language SECBR Severely Errored Cell Block Ratio SES Severely Errored Second SH Security Handler SIA Standard Interconnect Agreement SMC Service Management Centre SMDS Switched Multi-megabit Data Service SNC Subnetwork Connection SNMP Simple Network Management Protocol SP Service Provider SPC Signalling Point Code SS7 Signalling System No. 7 STASE-ROSE Secure Transformation Application Service Element – Remote Operations Service Element STM-1 Synchronous Transport Module – 1 STP Signal Transfer Point SVC Switched Virtual Channel TCP/IP Transfer Control Protocol/Internet Protocol TMN Telecommunications Management Network T-PNO Transit-PNO UBR Unspecified Bit Rate UNI User to Network Interface ETSI ETSI TR 101 477 V1.1.1 (2000-06) 19 UPC Usage Parameter Control VA-SP Value Added Service Provider VBR Variable Bit Rate +(rt = real time or nrt = non-real time) VC Virtual Channel VCC Virtual Channel Connection VCCC Virtual Channel Cross Connect VCI Virtual Channel Identifier VCL Virtual Channel Link VP Virtual Path VPC Virtual Path Connection VPCC Virtual Path Cross Connect VPCTP Virtual Path Connection Termination Point VPI Virtual Path Identifier VPN Virtual Private Network VPTTP Virtual Path Trail Termination Point X.easi NM interface being specified in the present document X.user NM interface between PNO and VA-SP or other consumer Xcoop X.easi (as named in other cooperative X-interface specification projects) X-interface TMN network management interface XML eXtensible Markup Language |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 4 General introduction | |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 4.1 Overview | The present document provides a "Framework Solution" in the form of guidelines to network management specifications and to supporting multi-lateral documentation for the practical achievement of inter-operability between European ATM networks, and between their associated management platforms, or Operations Support Systems (OSSs). It specifically acts as a detailed set of "Guidelines" to TS 101 674-2 [2]. It covers the processes and functions for the efficient management of interconnected ATM networks which align with technical specifications (for the user, control and network management planes respectively) being developed by the ETSI EASI project [1], [2]. Available network management standards for ATM services focus on the automation of operational processes. The present document also examines pre-service processes that are necessary between co-operating operators to establish the interconnection of their ATM networks prior to operational use. Operational NM interfaces should be specified in the context of these pre-service processes to ensure efficient and cost effective ATM-based service provision from the points of view of operators and customers alike. These pre-service interconnection processes take a great deal longer time to complete, than in-service connection provisioning, using the automated network management functions described later. The provision of interconnected ATM services has to be considered within the current European trading environment. This is characterized by a liberalization process that has been initiated by the EU. The exact stage of liberalization in each EU member state varies and different regulations are in place concerning the issue of licences to operate telecommunication networks. For this reason, the Business Model, proposed in the present document, separates the provision of network services - such as ATM connections - from value added service provision, since in some EU states this distinction is an important part of the regulatory environment. ETSI ETSI TR 101 477 V1.1.1 (2000-06) 20 4.2 Relationship of the present document to other ETSI and EURESCOM documents The present document is part of a set of documents from ETSI and EURESCOM in relation to the specifications for Phase 1. Figure 1 shows the relationship of the present document to the others: The present document TR 101 477 ETSI TS 101 674-2 NNI Network Management Plane ETSI TS 101 674-1 NNI User and Control Plane ATM X-interfaces specifications EN 300 820-1 /-2 /-3/… Broadband Service operator interconnect Handbook EURESCOM P813 D3 Describes what must be agreed bilaterally between operators Figure 1: Relationship of the present document to other EURESCOM and ETSI documents The combination of TS 101 674-1 [1] and TS 101 674-2 [2] provides the full technical specification for the Network to Network Interface covering the User, Control and Management Planes. The present document provides guidelines to the application of [2], the specification of the NNI for Network Management Plane and in doing so, references other applicable standards such as the EN 300 820-1 [6] for the X-Interface. In addition to these specifications and guidelines there is a need to document and agree some aspects of the interface, particularly operational aspects, on a bilateral basis. The Operator's Handbook [3] provides the overview and checklist for the aspects that have to be agreed bilaterally. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 4.3 Structure and organization of the present document | The scope and content of the present document, together with the relationship to the principal ETSI Phase 1 specification documents, is summarized in figure 2. ETSI ETSI TR 101 477 V1.1.1 (2000-06) 21 Requirements for interconnected ATM Network Management incl. Business Model, Technical Principles and Interconnect Policies Scope (and contents) of this document to provide guidelines for TS 101 674-2 [2] The proposed solution: EASI Specification of interconnected ATM Networks and Services Interconnected ATM Management Processes Specification of Automated or Manual ATM Management Interfaces Specification of the proposed solution for interconnected ATM network management & processes Annexes F - N include (short-form titles): TMN Management Principles Manual and Automated Interfaces Performance management issues Charging management issues Standards basis for accounting management Fax forms used for JAMES processes Star and Cascade Model values Pre-selection of carriers and policy rules General issues, gaps and dependencies Defined in TS 101 674-1 [1] Annexes A - E include (short-form titles) Interconnect processes for PVP, PVC Proposals for management identifier schemes Proposals for PVC managed resources Further details on security processes Further details on traffic and capacity ETSI Specification of ATM VP/VC Management Defined in EN 300 820-1 [6] Figure 2: Derivation of the proposed Network Management Solution The initial step is to develop the requirements for interconnected ATM network Management. These are based upon an assessment of the requirements arising from [1], and also general requirements that are captured in the form of a Business Model and interconnect policies. These are captured in clauses 6 and 7. These requirements are used to determine the ATM Interconnect Management processes for both Pre-Service and In-Service process areas. These are covered in clauses 8 and 9. For those processes where automated interfaces are required the present document develops solutions. The emphasis in Phase 1 is placed on the in-service inter-operator network management interface, "X.easi". This is introduced in subclause 5.4 and specifically addressed in clause 9. The solutions are mainly based upon references to Standards. A potential limitation to the solution derivation model shown in figure 2 is that there is no indication of what part of the standards is mandatory and what part is optional or how the model can be extended (e.g. by the use of "conditional packages"). Where possible, these aspects are described in various text clauses in the present document. A NM "solution" for interconnected ATM services would be deficient without a description of (i) a data model for supporting inter-operator processes and (ii) implementation and testing issues. Clauses 10 and 11 respectively provide information and requirements in these two areas. In addition to the clauses listed above, which comprise the main part of the present document, a series of annexes have been developed. The annexes A - E provide significant additional details in the following areas: (A) Management processes for provisioning and repairing PVP and PVC connections (B) Management identifier schemes (C) proposals for extensions of PVP to PVC managed resources (D) security processes and (E) traffic and capacity management processes. Annexes A - E should be regarded as an integral part of the description of the NM solution for operators interested in implementation and operation of the management interface described in the present document. Annexes F to N are not an integral part of the Phase 1 solution but may be regarded as relevant and useful background information. NOTE: Concerning annex C above, the term "extension of PVP to PVC managed resources" is used, because the PVP model is described in an existing standard, whereas the PVC part is new. ETSI ETSI TR 101 477 V1.1.1 (2000-06) 22 |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5 Technical principles for ATM interconnection services | |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.1 Overview | The requirements and solutions for ATM Management and Operations Support Systems are driven from an understanding of the ATM interconnect services offered between operators. Clause 5 addresses the interconnect services from both the ATM Bearer and Management Plane perspectives. More specifically, clause 5 describes the technical principles identified with ATM interconnection services. This includes ATM bearer capabilities, ATM interconnect services definition, "X.easi" nomenclature definition, a description of the network management parameters, the TMN and related technology basis for the NM specification, definitions of manual and automated interfaces and the requirements for the NM (X.easi) interface. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.2 ATM bearer capabilities | The present document is concerned with the following two types of ATM bearer capabilities which may require inter-operator processes for end-to-end management. Permanent Virtual Circuit Service Permanent Virtual Circuits are pre-configured logical connections between two ATM systems. They may of either the Virtual Path or Virtual Channel type. Switched Virtual Circuit Service Switched Virtual Circuits are logical ATM connections established via signalling. They will usually be of the Virtual Channel type. The ATM bearer capability distinguishes two types of connections (whether permanent or switched): Virtual Channel (VC) and Virtual Path (VP). Individual ATM connections between two adjacent ATM systems are referred to as VC Link Connections and VP Link Connections. The VP (or VC) Link may therefore be defined as the entity which connects two subnetworks where the VP (or VC) identifier is terminated or translated. End-to-end connections are referred to as Virtual Channel Connections (VCCs) and Virtual Path Connections (VPCs). All connections should be associated with a defined Quality of Service (QoS) and defined ATM Transfer Capability (ATC), - refer to subclause 5.3. A single ATM physical interface will support multiple VPCs, each of which will contain multiple VCCs. Implementing VPCs aids the manageability of the ATM network. Traffic management, rerouting and possibly switching may be based on these VPCs. The concepts of VPs, VCs and underlying physical links are depicted in figure 3 from the point of view of a single physical interface. Each such entity will have a unique identifier ascribed to it for operational purposes (which is not elaborated here). Physical layer connection VP VP VC VC VC VC Figure 3: Virtual Paths and Virtual Channels within the physical layer The ATM bearer capabilities are aligned with the technical capabilities required by [1], which are listed in the following bullets: • The transmission level. Transmission should be possible using virtual path connections (VPCs) or virtual channel connections (VCCs). ETSI ETSI TR 101 477 V1.1.1 (2000-06) 23 • The connection type. Connections can be permanent or semi-permanent. It should be possible to extend the specification to switched (on demand) connections, if required (Refer to comments in the bullets of subclause 9.1.3 for further comments about management requirements for switched services.). Permanent/semi-permanent virtual connections are to be supported on virtual path connection level and on virtual channel connection level. (For Phase 1, switched virtual connections should only supported on a virtual channel connection level.) Permanent/semi-permanent virtual channel connections (and switched virtual channel connections, if required) should be transported in different virtual path connections. • The connection configuration. Connections can, in principle, be point-to-point or point-to-multipoint. In Phase 1, support of point-to-multipoint connections is not required. • The direction of transmission. Transmission can be unidirectional (i.e. without any reverse information transport) or bi-directional. When bi-directional, transmission can be symmetric or asymmetric. At the NNI.easi interfaces, all modes of transmission, as defined in ETS 300 298-1 [4] and ETS 300 298-2 [5] should be supported. • The quality of service (QoS). The QoS classes required to be supported are defined in table 5.2 of [1]. • The ATM transfer capability (ATC). The ATCs required to be supported are defined in table 5.2 of [1]. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.3 Definition of ATM interconnect services | The provisioning of ATM end-to-end services across multiple interconnected ATM networks requires definition of the interconnect services. In the present document the ATM interconnect service is defined as "the capability to provide ATM connectivity across a particular network". The ATM interconnect service distinguishes two components: (1) the ATM interconnect transport service (defined by the User and Control Plane); (2) the ATM interconnect management service (defined by the Management Plane). The scope of both (1) and (2) needs to be agreed between interconnecting operators as part of the Interconnect Service Definition process described later in clause 7. The ATM interconnect service can be offered as: (i) Originating Carrier Service (i.e. a connection service from an A Endpoint to an adjacent operator's network); (ii) Transit Carrier Service (i.e. a connection service from an adjacent operator's network to the network of another adjacent operator, across their own network). Destination Carrier Service (i.e. a connection service between an adjacent operator's network and a Z Endpoint). The destination carrier service may be associated with the terminating connectivity provider described in clause 6. The present document is principally concerned with the ATM interconnect management service (2) whereas (1) is described in [1]. The interconnect management service involves establishment, maintenance and release of subnetwork connections amongst two or more administrative domains, as well all associated processes in order to meet a customer service requirement. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.4 "X.easi" Definition | In the present document the term "X.easi" has been chosen to reference all proposed network management functions between operators, covering both automated real-time and manual capabilities for the "ATM interconnect service operation processes". This term is a placeholder description which is expected to be strongly related to the established ITU-T TMN "X interface". The use of the term "X.easi", at this stage, avoids the need to be prescriptive about whether such interfaces are completely manual or automated, or some hybrid. ETSI ETSI TR 101 477 V1.1.1 (2000-06) 24 |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.5 Network management parameters | Figure 4 shows the concepts, resources and "planes" which may be considered in the context of the provision of ATM services which span two or more operator's network domains. Some terms are defined later in the present document. The part shown above the heavy line "p" represents the network management plane which is required to manage ATM networks and services defined in [1]. In order to define the scope for the Phase 1 specification, the X.easi interface is specifically restricted to management of the operational processes (as described in clause 9). The pre-service processes, described in clauses 7 and 8, are necessary inter-operator bi-lateral and multi-lateral activities associated with the provision of ATM interconnection services but are not within the definition of the X.easi management interface for the Phase 1 specification. (Q-interface) (Q-interface) (Q-interface) X.easi ATM Gateway ATM Gateway ATM Gateway ATM Gateway ATM Gateway NNI.easi X.easi UNI CPN/ CPE UNI CPN/ CPE UNI CPN/ CPE Legend: ATM Network ‘C’ ATM Network ‘A’ ATM Network ‘B’ Operations Support System (Operator ‘A’) Operations Support System (Operator ‘B’) Operations Support System (Operator ‘C’) ATM Network Management Plane (Scope of this document, except definition of the Q-interface) ATM Network User & Control Plane (Specification in ETSI TS 101 674-1. Out of the scope of this document) ATM Network ‘A’ Facilities and customer connections ATM Network ‘B’ Facilities and customer connections ATM Network ‘C’ Facilities and customer connections X.easi Network Management interface between operators’ Operations Support Systems CPN/CPE Customer Private Network / Customer Premises Equipment NNI.easi Network-to-Network Interface (specified in [1]) UNI User-to-Network Interface (specification not specified) (Q-interface) Management interface to the network technology in each operator domain This is proprietary to each operator and not defined or specified in this document. NOTE The ‘I’ and ‘A’ operators may be one and the same organisation. ‘p’ NNI.easi Operations Support System (Operator ‘I’ initiator) X.easi Figure 4: Concepts, resources and planes for ATM networks and services Figure 4 shows the general case of an initiating operator (I) in addition to the originating operator (A), by comparison with the NM description in the equivalent figure in [1]. Operator (I) is included in the network management specification in order to align with the European standard [6]. In many cases, the "I" and "A" operators may be one and the same organization (as assumed in [1]) but may equally well be different organizations. As the end to end connections are established across multiple subnetworks, the Operation Support systems of the A, B and C operators are responsible for, originating connections, transit connections and terminating connections ETSI ETSI TR 101 477 V1.1.1 (2000-06) 25 respectively and the I operator is responsible for arranging the end to end connection between A Endpoint and Z Endpoint, that is, the connections of direct interest to the end customer(s). Furthermore, operators I, A, B and C in figure 4 map onto the I-CP, A-CP, T-CP and Z-CP roles defined in the Business Model (figure 5), described in subclause 6.3. It may be presumed that many interconnecting operators would wish to act in any of the I, A, B or C roles shown in figure 4, according to the configuration of any given PVP or PVC connection and would wish to provide management services such as PVP/PVC establish, release, reconfigure, modify [6] etc in relation to any of these four roles. The management services, defined in relation to each of the four roles, are required to support PVP, PVC etc services provided by the interconnected ATM networks plane. The specification of the interconnected ATM networks plane (the part shown below the heavy line "p" in figure 4), is defined in [1], except for the User-to-Network interface (UNI). Interactions with entities such as "Value Added Service Providers" are not shown in figure 4 but described later in association with the interconnect business model and figure 5. 5.6 TMN and Technology basis for the X.easi interface specification |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.6.1 The TMN basis for the interface specification | The proposal for the network management interface specification, identified as "X.easi" in the present document, is based upon the ITU-T Telecommunications Management Network (TMN) Architecture and principles, derived from ITU-T Recommendation M.3010 [7]. The concept behind a TMN is to provide an organized architecture to achieve the interconnection between various types of operators for the exchange of management information, using an agreed architecture with standardized interfaces including protocols and messages. One such interface is the TMN X-interface. This is derived from the "x reference point" described in [7] and is pertinent for the establishment, maintenance and release of ATM Virtual Path (VP) and Virtual Channel (VC) connections which span several operator's ATM domains. The term "X.easi", is derived from these concepts. Some additional detail on TMN concepts is provided in annex F. TMN architecture also defines the Q-interface, derived from the q reference point in [7] and other standards. Simplistically, this interface is operator-internal. It is between an operator's OSS and its network technology, including switches. These interfaces are essential but are the responsibility of each operator and its technology supplier and, as such, are outside the scope of the present document. For efficient ATM interconnection, it must be presumed that suitable Q-like interfaces are available to operate in association with the relevant X.easi interfaces. (Refer also to the architecture and associated comments in figure 4.) The present document recognizes that some operator's operations support systems (OSSs) are manual and this factor influences the technical capabilities of the X.easi interface. The concepts of manual and automated TMN management interfaces are described in subclause 5.6.2. |
87adb3a5a1f0cae643a14a295fd5465b | 101 477 | 5.6.2 The technology basis for the interface specification | The "automated" interface specifications, described in clause 9 and elsewhere, are based on the presumed use of a CMIP and GDMO based implementation of the interface. The practical use of such technology has been demonstrated in other EURESCOM projects [8], [9]. The present document aims to provide a management interface specification which may or may not rely on the use of a CMIP and GDMO implementation. In other words, the specifications and principles described in the present document should be applicable to any suitable technology basis, although the descriptions have the established basis of CMIP/GDMO in mind. CMIP/GDMO should therefore be considered as a reasonable example of the technology solution but not necessarily the sole choice. Many of the concepts of network management, for the "ATM interconnect service operation processes" described later (specifically with figure 8), are associated with the deployment and use of "X.easi" interfaces which are: "Manual", "Fully-automated", or "Semi-automated". Subclauses 5.6.2.1 and 5.6.2.2 describe the use of these terms. ETSI ETSI TR 101 477 V1.1.1 (2000-06) 26 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.