id stringlengths 7 13 | title stringlengths 26 396 | type stringclasses 2
values | version stringclasses 152
values | url stringlengths 90 98 | scope stringlengths 0 9.03k |
|---|---|---|---|---|---|
102 163 | Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Profile Implementation Guide | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102163/01.01.01_60/tr_102163v010101p.pdf | The present document describes the Profile mechanism of HIPERLAN/2 [1]. |
102 164 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Emergency Location Protocols [OMA-TS-MLP-V3_2-20051124-C] | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102164/01.03.01_60/ts_102164v010301p.pdf | The present document specifies the protocol that is used by the local emergency operator to obtain the location information that is registered on the operator location server, see figure 1. It endorses and defines a profile of the OMA specification OMA-TS-MLP-V3_2-20051124-C [1] that are applicable to the emergency location information services. NOTE: The LI Forum has been affiliated and its work subsumed into the OMA; the LIF TS 101 Specification has been succeeded by OMA-TS-MLP-V3_2. |
102 165-1 | Cyber Security (CYBER); Methods and protocols; Part 1: Method and pro forma for Threat, Vulnerability, Risk Analysis (TVRA) | TS | 5.3.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10216501/05.03.01_60/ts_10216501v050301p.pdf | The present document defines a method primarily for use in undertaking an analysis of the threats, risks and vulnerabilities of an Information and Communications Technology (ICT) system to identify applicable countermeasures. NOTE 1: The method described has been tailored to apply to pre-production but can be applied to production devices with due attention given to possibility that the application of countermeasures may be unachievable for a re-design strategy. NOTE 2: The method described in the present document builds from the Common Criteria for security assurance and evaluation defined in [i.27], [i.28], [i.29] and may be used to form part of the documentation set for the Target Of Evaluation as specified in ETSI ES 202 382 [i.24]. |
102 165-2 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Methods and protocols; Part 2: Protocol Framework Definition; Security Counter Measures | TS | 4.2.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10216502/04.02.01_60/ts_10216502v040201p.pdf | The present document defines by means of an information model and functional entity behavioural model, the security countermeasures for the ICT in general and where examples are shown they are shown with respect to the NGN. Countermeasures are grouped by their key feature, i.e. Authentication, Integrity. The Unified Modelling Language (UML) is used to model the countermeasures as a semi-formal tool with verification and simulation capabilities deployed during development. NOTE: This is in accordance with the goals of the eEurope project under objective Good practices (COM(2002) 263 page 18). The countermeasures defined in the present document have been identified from an analysis of the NGN presented in TS 102 165-1 [10] and in TR 187 002 [9] as those most likely to be required for mitigation of risk in the NGN. The deployment of the countermeasures in the NGN is extrapolated from TR 187 002 [9] and defined in this document. The present document is intended for designers of security countermeasures. NOTE: The definition of cryptographic algorithms is not provided by this document but the invocation of algorithms in protocol sequences is shown. The specific use of IPsec [11] in ESP mode [12], including IKEv2 [18] and is reviewed in annex B of this document as a specific stage 3 implementation of the stage 1 and stage 2 capabilities. The authentication countermeasures outlined as structural and behavioural patterns in the present document cover the following scenarios: • Source authentication as defined for IPsec ESP. • NASS-IMS bundled authentication including mechanisms for NASS authentication. • Early IMS authentication (by reference to TR 133 978 [20]). |
102 165-3 | Cyber Security (CYBER); Methods and Protocols for Security; Part 3: Vulnerability Assessment extension for TVRA | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10216503/01.01.01_60/ts_10216503v010101p.pdf | The present document defines the application of the Common Criteria Vulnerability Assessment class defined in Common Criteria part 3 [1] alongside the ETSI TVRA method defined in ETSI TS 102 165-1 [2]. |
102 166 | Corporate telecommunication Networks (CN); Signalling interworking between QSIG and SIP; Basic services | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102166/01.02.01_60/ts_102166v010201p.pdf | The present document specifies signalling interworking between QSIG and the Session Initiation Protocol (SIP) in support of basic services within a corporate telecommunication network (CN) (also known as enterprise network). QSIG is a signalling protocol that operates between Private Integrated Services eXchanges (PINX) within a Private Integrated Services Network (PISN). A PISN provides circuit-switched basic services and supplementary services to its users. QSIG is specified in Ecma Standards; in particular, [2] (call control in support of basic services), [3] (generic functional protocol for the support of supplementary services), and a number of standards specifying individual supplementary services. NOTE: The name QSIG was derived from the fact that it is used for signalling at the Q reference point. The Q reference point is a point of demarcation between two PINXs. SIP is an application-layer protocol for establishing, terminating, and modifying multimedia sessions. It is typically carried over IP [15] and [16]. Telephone calls are considered a type of multimedia session where just audio is exchanged. SIP is defined in [10]. As the support of telephony within corporate networks evolves from circuit-switched technology to Internet technology, the two technologies will coexist in many networks for a period, perhaps several years. Therefore, there is a need to be able to establish, modify, and terminate sessions involving a participant in the SIP network and a participant in the QSIG network. Such calls are supported by gateways that perform interworking between SIP and QSIG. The present document specifies SIP-QSIG signalling interworking for basic services that provide a bi-directional transfer capability for speech, DTMF, facsimile, and modem media between a PISN employing QSIG and a corporate IP network employing SIP. Other aspects of interworking, e.g. the use of RTP and SDP, will differ according to the type of media concerned and are outside the scope of the present document. Call-related and call-independent signalling in support of supplementary services is outside the scope of the present document, but support for certain supplementary services (e.g. call transfer, call diversion) could be the subject of future work. Interworking between QSIG and SIP permits a call originating at a user of a PISN to terminate at a user of a corporate IP network, or a call originating at a user of a corporate IP network to terminate at a user of a PISN. Interworking between a PISN employing QSIG and a public IP network employing SIP is outside the scope of the present document. However, the functionality specified in the present document is in principle applicable to such a scenario when deployed in conjunction with other relevant functionality (e.g. number translation, security functions, etc.). The present document is applicable to any interworking unit that can act as a gateway between a PISN employing QSIG and a corporate IP network employing SIP. |
102 168 | Electromagnetic compatibility and Radio spectrum Matters (ERM); VHF air-ground Data Link (VDL) Mode 4 radio equipment; Study report on Galileo local component | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102168/01.01.01_60/tr_102168v010101p.pdf | |
102 169-1 | Services and Protocols for Advanced Networks (SPAN); Network Integration Testing between H.323, ISDN and PSTN; Part 1: Test Suite Structure and Test purposes (TSS&TP) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10216901/01.01.01_60/ts_10216901v010101p.pdf | The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for Network Integration Testing (NIT) to verify the overall compatibility of ITU-T Recommendation H.323 [3], ISDN and non-ISDN (PSTN) over the national or international ISUP between networks. The TSS&TP specification covers the procedures described in ITU-T Recommendation H.323 [3] , ITU-T Recommendation H.225.0 [4] as specified in TS 101 883 [1] and ITU-T Recommendation Q.931 [5]". All test purposes are written with reference to ITU-T Recommendation H.246 annex C [10] which implies the following test architecture: SUT H.323 ISUP ISDN mapping H.323->ISUP H.246 annex C mapping ISUP->ISDN (Q.699) H.323 terminal ISDN terminal H.323-ISDN inter-working testing architecture via ISUP Two mapping functions are involved. They are specified in ITU-T Recommendation H.246 annex C [10] (H.323-ISUP) and ITU-T Recommendation Q.699 [23] (ISDN-ISUP). |
102 171 | Using ECMA-323 (CSTA XML) in a Voice Browser Environment | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102171/01.01.01_60/tr_102171v010101p.pdf | Services for Computer Supported Telecommunications Applications are defined by Standard ECMA-269 and the XML Protocol for those services is defined by Standard ECMA-323. In many cases, applications require only a small subset of the features standardized in CSTA. In a voice browser environment, processing speech (not call control) is usually the major focus of the application. For example, from a CSTA feature perspective, an application may simply need to answer an incoming call and then later clear it. As these speech-centric applications evolve they can use additional, more advanced, features standardized by CSTA that are provided by CSTA-conformant communications platforms. Since ECMA-269 and ECMA-323 are relatively large standards (combined over 1100 pages), it is a challenge for application developers without prior knowledge of the CSTA standards to know where to find basic concepts that they need to understand in order to implement basic CSTA features. The present document illustrates how ECMA-323 can be used in a Voice Browser environment. These concepts illustrated in the present document can be applied to any Voice Browser environment that provides an XML-based read/write messaging interface (i.e. CSTA Service Boundary) that supports asynchronous events from a CSTA conformant communication platform. SALT enabled browsers that implement a ECMA-323 interface for call control using the SALT smex mechanism is an example of a browser with this capability. Throughout the present document the term "ECMA-323 enabled voice browser" is used, in a generic sense, to refer to browser implementation that support a CSTA conformant ECMA-323 interface. Examples are provided that show how ECMA-323 can be used in several different environments such as SALT-enabled browsers and CCXML. |
102 172 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Minimum requirements for interoperability of ENUM implementations | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102172/01.02.01_60/ts_102172v010201p.pdf | The present document contains general guidance on (User) ENUM implementations as defined in RFC 3761 [16] and in TS 102 051 [2] "ENUM Administration in Europe" and the specification for: • The format, contents and meaning of the information in the NAPTR records that are held by the ENUM Tier 2 Nameserver providers and accessible by DNS. • The ways in which ENUM client software should interpret and act upon information obtained from NAPTR records. The present document is intended to enable interoperability between ENUM implementations that are organized in different countries. This interoperability enables: • The same ENUM client software to work with NAPTR records generated by different national implementations and this in turn will enable applications that use ENUM to access details of ENUM subscribers in more than one country without additional modifications. • Organizations to function as ENUM Registrars and ENUM Tier 2 Nameserver Provider in more than one national implementation. The present document will therefore add economies of scope to the ENUM implementations that will benefit ENUM subscribers, providers, application service providers and ENUM users. The present document is Version 2 of the Technical Specification (TS) and incorporates already some results obtained from trials performed in some countries. It may serve therefore with some caution also as a basis for first commercial deployments, keeping in mind that still not all enumservices are available as IETF RFCs and registered with IANA, The intention is to review the present document based on the experience gained from future implementations and if necessary. |
101 946-1 | Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Message Service (SMS); Profile requirement list and profile specific Implementation Conformance Statement (ICS) proforma; Part 1: Portable radio Termination (PT) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/101900_101999/10194601/01.01.01_60/ts_10194601v010101p.pdf | The present document provides the profile requirement list and profile-specific Implementation Conformance Statement (profile ICS) proforma for the Digital Enhanced Cordless Telecommunications (DECT) Low Rate Messaging Service (LRMS) including Short Message Service (SMS) at the Portable radio Termination (PT) as defined in EN 300 757 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [11]. The supplier of an implementation which is claimed to conform to EN 300 757 [1] is required: • in the case of Low Rate Messaging Service (LRMS) to: - complete a copy of the Protocol Implementation Conformance Statement (PICS) proforma EN 300 476, parts 1 [5], 2 [6], 3 [7] and 7 [8] and with the replacements from the annex A of the present document; - complete a copy of the profile-specific ICS proforma provided in the annex B of the present document. • in the case of Short Message Service (SMS) to: - complete a copy of the Protocol Implementation Conformance Statement (PICS) proforma EN 300 476, parts 1 [5], 2 [6], 3 [7] and 7 [8] with the replacements from the annex C of the present document; - complete a copy of the profile-specific ICS proforma provided in the annex D of the present document. |
102 175 | PowerLine Telecommunications (PLT); Channel characterization and measurement methods | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102175/01.01.01_60/tr_102175v010101p.pdf | The present document applies to measurements of the symmetry behaviour and the attenuation in Low Voltage Distribution Networks (LVDN) within premises. It also covers measurements for magnetic near fields within and in close vicinity of premises resulting from feeding HF-signals into LVDN. The measurements are intended for the measurement campaign of the ETSI Specialist Task Force (STF) 222, which investigates HF characteristics of LVDN relevant for the operation of PLT-systems as well as the hidden node aspect. |
102 177 | Broadband Radio Access Networks (BRAN); HiperMAN; Physical (PHY) layer | TS | 1.5.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102177/01.05.01_60/ts_102177v010501p.pdf | The present document specifies the HiperMAN air interface with the specification layer 1 (physical layer), which can be used to provide Fixed applications, in frequencies below 11 GHz, and Nomadic and converged Fixed-Nomadic applications, in frequencies below 6 GHz. The present document follows the ISO-OSI model. HiperMAN is confined only to the radio subsystems consisting of the Physical (PHY) layer and the DLC layer - which are both core network independent - and the core network specific convergence sub-layer. For managing radio resources and connection control, the Data Link Control (DLC) protocol is applied, which uses the transmission services of the DLC layer. Convergence layers above the DLC layer handle the inter-working with layers at the top of the radio sub-system. The scope of the present document is as follows: • It gives a description of the physical layer for HiperMAN systems. • It specifies the transmission scheme in order to allow interoperability between equipment developed by different manufacturers. This is achieved by describing scrambling, channel coding, modulation, framing, control mechanisms, and power control to assist in radio resource management. • It does cover the receiver and transmitter performance requirements which are specific for HiperMAN systems. • Some information clauses and annexes describe parameters and system models to assist in preparing conformance, interoperability and coexistence specifications. |
102 178 | Broadband Radio Access Networks (BRAN); HiperMAN; Data Link Control (DLC) layer | TS | 1.5.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102178/01.05.01_60/ts_102178v010501p.pdf | The present document defines the Data Link Control (DLC) of HiperMAN to support PMP and optionally Mesh network topologies. The present document provides the DLC functions required for Fixed applications, in frequencies below 11 GHz, and Nomadic and converged Fixed-Nomadic applications, in frequencies below 6 GHz. |
102 179 | Digital Enhanced Cordless Telecommunications (DECT); AT command interface; High-level description | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102179/01.01.01_60/tr_102179v010101p.pdf | The present document specifies a profile of AT commands and recommends that this profile be used for controlling PT and FT functions. |
102 180 | Emergency Communications (EMTEL); Basis of requirements for communication of individuals with authorities/organizations in case of distress (Emergency call handling) | TR | 1.5.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102180/01.05.01_60/tr_102180v010501p.pdf | The present document gives an overview of the requirements for communication from individuals to authorities and organizations in all types of emergencies. It collects operational and organizational requirements as a basis for a common 112 service, including location information (E112). Although many of the requirements collected from network operators, service providers (e.g. emergency response organizations) and users relate to national public policies and regulation, there are a number of service and technical aspects which are better dealt with on the European level to ensure harmonized access and services over Europe and effectiveness by user increased awareness by using standardized solutions. The essence of an emergency call is to establish a direct and real time means of conversation between the calling party and an officer, in a Public Safety Answering Point, in charge of bringing assistance or organizing response. However, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as transmission of data to extend the information made available to the PSAP's agent or to facilitate access of people suffering disabilities or impairments. The present document also collects already established requirements for EMTEL and gives guidance on how to find the standardization work published or ongoing. The present document also identifies the areas needing particular attention from the experts and refers to identified documents in preparation in SDOs (Standard Development Organizations). The present document outlines the basis for technical, operational, organizational or regulatory requirements. The present document is primarily applicable to ETSI technical bodies for the defining of services and specifying technical solutions. Requirements for emergency calls of a private nature (e.g. vehicle/road assistance) and directed to an emergency service provider not being an emergency service provider recognized by a government are not covered by the present document. It is anticipated that the present document will be maintained, by taking in line with developments at regulatory level and more specifically within the CoCom (Communication Committee for the Electronic Communications Directives) at the European Commission (EC) level. |
102 181 | Emergency Communications (EMTEL); Requirements for communication between authorities/organizations during emergencies | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102181/01.03.01_60/ts_102181v010301p.pdf | The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies. |
102 182 | Emergency Communications (EMTEL); Requirements for communications from authorities/organizations to individuals, groups or the general public during emergencies | TS | 1.5.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102182/01.05.01_60/ts_102182v010501p.pdf | The present document gives an overview of the requirements for communication from authorities/organizations to citizens in all types of emergencies. It collects operational and organizational requirements as a basis for a common notification service, including targeting of the area to be notified. Although many of the requirements relate to national public policies and regulation, there are a number of service and technical aspects which are better dealt with on the European level to ensure harmonized access and services over Europe and service effectiveness through increased user awareness by using standardized solutions. The present document also collects already established requirements for notification and gives guidance on how to find the standardization work published or ongoing. The document identifies the areas needing particular attention from the experts and refers to identified documents in preparation in SDOs. The present document is a collection of technical requirements and recommendations. The present document is applicable to ETSI technical bodies for defining of services and specifying technical solutions. It is clear that the present document will not present a solution for every scenario. |
102 183 | Digital Enhanced Cordless Telecommunications (DECT); Conformance testing on DECT equipment | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102183/01.02.01_60/tr_102183v010201p.pdf | The present document attempts to provide an introduction in DECT testing. It gives a general overview on the DECT system, an introduction on testing and DECT testing in particular. It further shows how an ETSI customer can use the DECT test standards. The present document contains an abstract of the DECT standard, the ISO/IEC 9646 [56] to [62] standard and the resulting issues from applying the requirements and techniques of ISO/IEC 9646 on the DECT protocol stack, together with a set of examples derived from the currently available test specification material from the Test suites for different DECT layers. The present document is not an overall description of DECT system concepts for which reference should be made to the relevant DECT standard documents, neither a guidance in testing methodology and framework, for which reference should be made to ISO/IEC 9646 documents. It is outside the scope of the present document to define specific equipment or particular implementation of such a product intended to realize the considered ATSs for DECT testing. |
102 185 | Digital Enhanced Cordless Telecommunications (DECT); Data Services Profile (DSP); Profile overview | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102185/01.02.01_60/tr_102185v010201p.pdf | The present document describes the objectives, structure and content of the Digital European Cordless Telecommunications (DECT) Data Services Profiles (DSPs), which define a set of profile standards for systems conforming to the DECT standard. They are a family of profile standards which build upon, and extend, each other, aimed at the general connection of terminals offering non-voice services between themselves or to other communications network, both public and private, via a DECT Fixed Part (FP). The present document also describes possible user scenarios in wireless mobile computing. These scenarios have formed the guidelines of the DECT DSPs. |
102 187 | Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia; Overview of BSM families | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102187/01.01.01_60/tr_102187v010101p.pdf | The present document has been produced by ETSI Technical Committee Satellite Earth stations and Systems (TC SES). It provides the definitions of the Family Names of Broadband Satellite Multimedia (BSM). |
102 188-1 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 1: General description | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218801/01.01.02_60/ts_10218801v010102p.pdf | The present document is an introduction to the physical layer specification for the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It consists of a general description of the organization of the physical layer with reference to the parts of this multi-part deliverable where each function is specified in more detail. |
102 188-2 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 2: Frame structure | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218802/01.01.02_60/ts_10218802v010102p.pdf | The present document defines the frame structure used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes frame, time slot, and burst structure definition. |
102 188-3 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 3: Channel coding | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218803/01.01.02_60/ts_10218803v010102p.pdf | The present document defines the channel coding structure used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes code block, scrambling, outer forward error correction encoding, interleaving, and inner forward error correction encoding process definition. |
102 188-4 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 4: Modulation | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218804/01.01.02_60/ts_10218804v010102p.pdf | The present document defines the modulation used within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. It includes the various modulation formats that are required for different physical channel types. It also defines the concept of the transmission burst and the mapping of modulated symbols to the burst, and describes the required transmit filtering in general terms. |
102 188-5 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 5: Radio transmission and reception | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218805/01.01.02_60/ts_10218805v010102p.pdf | The present document defines the Radio Frequency (RF) requirements for the Satellite Terminal (ST) transceiver of the Regenerative Satellite Mesh - A (RSM-A); Air interface operating in the Fixed Satellite System (FSS) allocations at Ka-band as follows: • ST reception is in the Fixed Satellite Service (FSS) frequency ranges from 17,70 GHz to 19,70 GHz and from 19,70 GHz to 20,20 GHz; • ST transmission is in the frequency ranges allocated to FSS from 27,50 GHz to 29,50 GHz and from 29,50 GHz to 30,00 GHz. Requirements are defined for two categories of parameters: • those that are required to provide compatibility between the radio channels, connected either to separate or common antennas, that are used in the system. This category also includes parameters providing compatibility with existing systems in the same or adjacent frequency bands; • those that define the transmission quality of the system. These requirements apply to all types of ST that transmit a single modulated carrier, including STs with an antenna diameter greater than 1,8 m (or equivalent corresponding aperture). The technical requirements of the present document apply under the environmental profile for operation of the equipment, which shall be declared by the manufacturer. The equipment shall comply with all the technical requirements of the present document at all times when operating within the boundary limits of the declared operational environmental profile. The environmental profile for operation of the equipment shall include the ranges of humidity, temperature and supply voltage. |
102 188-6 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 6: Radio link control | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218806/01.01.02_60/ts_10218806v010102p.pdf | The present document presents the requirements for synchronizing timing and frequency between the ST and the satellite network within the SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. |
102 188-7 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 7: Synchronization | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218807/01.01.02_60/ts_10218807v010102p.pdf | The present document presents the requirements for synchronizing timing and frequency between the ST and the satellite network within the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. |
102 189-1 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 1: General description | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218901/01.01.02_60/ts_10218901v010102p.pdf | The present document is an introduction to the SMAC/SLC layer specification for the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. In particular it contains the description of the overall network and SMAC/SLC protocol architecture of the BSM Regenerative Satellite Mesh - A (RSM-A) air interface as seen from the ST. It also describes the various interfaces between the ST and other network elements and the relation between the layers in the ST logical protocol architecture as are discussed in the present document as well as the interactions with other layers in the BSM Regenerative Satellite Mesh - A (RSM-A) protocol architecture. |
102 189-2 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 2: Satellite Medium Access Control and Satellite Link Control detailed specification | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218902/01.01.02_60/ts_10218902v010102p.pdf | The present document is the detailed specification of the SMAC/SLC layer protocol for the TC-SES BSM Regenerative Satellite Mesh - A (RSM-A) air interface family. In particular, it contains SMAC and SLC procedures, messages and message formats. |
102 189-3 | Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 3: ST-SAM Interface specification | TS | 1.1.2 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10218903/01.01.02_60/ts_10218903v010102p.pdf | The present document defines the communication interface between a TC-SES BSM Regenerative Satellite Mesh-A (RSM-A) air interface compliant Satellite Terminal (ST) and the Security Access Module (SAM). It specifies the communication medium and the protocols for communication. The present document describes how packets, received at the ST from the Network Operations Control Centre (NOCC), are routed to the SAM, how messages created originally by the ST are routed to the SAM, how message from the SAM are routed via the ST to the NOCC and how messages from the SAM are consumption by the ST. |
102 190 | Near Field Communication (NFC) IP-1; Interface and Protocol (NFCIP-1) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/102190/01.01.01_60/ts_102190v010101p.pdf | The present document defines communication modes for Near Field Communication Interface and Protocol (NFCIP-1) using inductive coupled devices operating at the centre frequency of 13,56 MHz for interconnection of computer peripherals. It also defines both the Active and the Passive communication modes of Near Field Communication Interface and Protocol (NFCIP-1) to realize a communication network using Near Field Communication devices for networked products and also for consumer equipment. The present document specifies, in particular, modulation schemes, codings, transfer speeds, and frame format of the RF interface, as well as initialization schemes and conditions required for data collision control during initialization. Furthermore, the present document defines a transport protocol including protocol activation and data exchange methods. Information interchange between systems also requires, at a minimum, agreement between the interchange parties upon the interchange codes and the data structure. |
102 192-1 | Electromagnetic compatibility and Radio spectrum Matters (ERM); International Technical Characteristics and Test Methods; Part 1: Wireless/Radio Microphones in the 25 MHz to 3 GHz Frequency Range | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10219201/01.01.01_60/ts_10219201v010101p.pdf | The present document covers the minimum characteristics considered necessary in order to make the best use of the available frequencies. It does not necessarily include all the characteristics that may be required by a user, nor does it necessarily represent the optimum performance achievable. The present document applies to equipment operating on radio frequencies between 25 MHz and 3 GHz, using analogue, digital and hybrid (using both analogue and digital modulation) The present document does not apply to radio microphones or in ear monitoring equipment employing Time Division Multiple Access (TDMA), modulation. Additional standards or specifications may be required for equipment intended to interface to the Public Switched Telephone Network (PSTN). This facility may be submitted to regulatory conditions. The present document may be used by accredited test laboratories or manufacturers for testing of the equipment. The performance of the equipment submitted for testing should be representative of the performance of the corresponding production models. The maximum power recommended for equipment covered by the present document is 50mW mean power national regulations on maximum power output will apply. The types of equipment covered by the present document are as follows: - professional hand held radio microphones; - professional body worn radio microphones; - in ear monitoring systems; - consumer radio microphones; - tour guide systems; - aids for the handicapped (assistive technology). NOTE: Test methods within the present document are applicable for equipment with a maximum of 250 mW (mean power). |
102 192-2 | Electromagnetic compatibility and Radio spectrum Matters (ERM); International Technical Characteristics and Test Methods; Part 2: Cordless audio and Consumer radio microphones in the 25 MHz to 3 GHz Frequency Range | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10219202/01.01.01_60/ts_10219202v010101p.pdf | The present document covers the minimum characteristics considered necessary in order to make the best use of the available frequencies. It does not necessarily include all the characteristics that may be required by a user, nor does it necessarily represent the optimum performance achievable. The present document applies to cordless audio and in ear monitoring equipment using either 300 kHz bandwidth analogue modulation or 300 kHz, 600 kHz or 1 200 kHz digital modulation. The frequency bands for this equipment may differ from country to country as specified in their national regulations. All equipment is intended to be used with integral antennas. The present document does not apply to broadband modulation such as spread spectrum techniques. Consumer audio equipment intended for audio and voice operating below 50 MHz and using narrow band modulation are excluded from the present document. Electromagnetic Compatibility (EMC) requirements are covered by the present document in annex A. The types of equipment covered by the present document are examples as follows: - cordless headphones; - cordless loudspeakers; - consumer radio microphones; - in-ear monitoring; - in-vehicle cordless; - personal cordless; - broadband multi channel audio systems. |
102 193 | Fixed Radio Systems; Point-to-point and Point-to-multipoint equipments; Aspects regarding P-P and P-MP digital radio equipment with ATM and IP interfaces carrying native ATM or IP over ATM payloads | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102193/01.01.01_60/tr_102193v010101p.pdf | |
102 197 | Services and Protocols for Advanced Networks (SPAN); Preliminary analysis of EMTEL and Local Emergency Service requirements for IP networks and Next Generation Networks | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102197/01.01.01_60/tr_102197v010101p.pdf | The present document gives a preliminary analysis of technical requirements for the support of EMTEL and location services for emergency and priority services within the PSTN/ISDN/IP signalling transport services in Europe, to progress toward the enhancement signalling transport protocol standards documentation. |
102 198 | Services and Protocols for Advanced Networks (SPAN); Preliminary analysis of migration to the Internet NGN | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102198/01.01.01_60/tr_102198v010101p.pdf | The present document is an analysis of technical requirements for the support and deployment of Telecommunication Services in Europe using IPv6, to progress toward the enhancement of signalling transport protocol standards. The aims are to evaluate the requirements for standardization, existing standards, and to identify standardization gaps with respect to recommendations made by the Communication "Next Generation Internet priorities for action in migrating to the new Internet Protocol Ipv6" [COM(2002) 96 final] (reference [COM 96]). |
102 199 | Services and Protocols for Advanced Networks (SPAN); Preliminary analysis on Broadband multimedia services | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102199/01.01.01_60/tr_102199v010101p.pdf | The present document analyses technical requirements for the support and deployment of Broadband Multimedia Services in Europe. It evaluates the requirements for standardization, identifies existing standards and standardization gaps with respect to the technology for Broadband Multimedia Services. |
102 200 | Methods for Testing and Specification (MTS); UMTS Testing Methodology | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102200/01.01.01_60/tr_102200v010101p.pdf | The present document describes UMTS Network Integration Testing (NIT) methodology and TSS&TP. |
102 202 | Human Factors (HF); Human Factors of work in call centres | TR | 1.1.2 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102202/01.01.02_60/tr_102202v010102p.pdf | The present document reviews the human factors issues of those centres where business is conducted via the telephone whilst simultaneously using Display Screen Equipment (DSE) and gives guidance on the design of the tasks and of the working environment. It classifies such call centres to facilitate the identification of specific tasks, functions and supporting equipment. It reports a number of studies into the call centre working environment and consultations with stakeholders. Guidance is given in the context of current legislation and developing technologies. Human factors problems associated with call centre work are highlighted, and where appropriate, examples of best practice are given to illustrate how they may be avoided. The present document is applicable to call centres of various types such as help lines and telemarketing. It does not deal with issues related either to surveillance centres or to sex lines. It does not deal with web based contact centres. Recommendations in the present document are limited to real time voice based services although the implications of changing technology are noted. Although personal health considerations are included in the present document, safety issues are outside its scope. |
102 203 | Mobile Commerce (M-COMM); Mobile Signatures; Business and Functional Requirements | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102203/01.01.01_60/tr_102203v010101p.pdf | The present document ("TR") considers the business and functional requirements for a MOBILE SIGNATURE SERVICE. The present document is intended to guide the drafting of the following ETSI Technical Specifications (TS) concerning interfaces, security provisions and interoperability of mobile signatures service solutions. • Technical Specification: TS 102 204 - Mobile Signature Web Service Interfaces • Technical Specification: TS 102 206 - Security Requirements for Mobile Signature Systems • Technical Specification: TS 102 207 - Roaming of Mobile Signature Service Transactions Together, the present document and the TSs will allow the design and implementation of interoperable mobile signature service solutions. As such, the present document defines business and functional requirements for mobile signature service solutions that leverage smartcards (including the GSM SIM-CARD) and cryptographic techniques (including asymmetric cryptography used in public key infrastructure - PKI) to facilitate the deployment of electronic signature solutions. The mobile signature service is considered suitable for the administration and management of all aspects relating to: • Advising and guiding citizens about the use of mobile signature. • Acquiring mobile signature capability. • Managing citizen identity (including Data protection and individual privacy). • Processing of signature requests from application providers (and providing responses). • Maintaining signature transaction records for the citizen. • Managing all aspects of signature lifecycle (e.g. validity, expiry, revocation). • Supporting service administration and maintenance activities. In defining the Webservice, the present document makes reference to interactions between different parties and to the end user experience of a mobile signature service at the mobile device. This is done to illustrate concepts and facilitate definition of business and functional requirements for the Webservice - only. Readers are referred to other sources of information as indicated in the "References" clause regarding definitions and specifications for these topics. |
102 204 | Mobile Commerce (M-COMM); Mobile Signature Service; Web Service Interface | TS | 1.1.4 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102204/01.01.04_60/ts_102204v010104p.pdf | The present document specifies the Mobile Signature Service as a Web Service: MOBILE SIGNATURE WEB SERVICE. From the business and functional requirements of TR 102 203 [12], the present document identifies the methods that must be provided by a Mobile Signature Web Service Provider. The present document specifies the data structures and messaging models related to these methods thanks to XML Schema and WSDL. Documentations about these technologies can be found in clause 2. The complete MSS XML Schema is provided in Annex A. A SOAP 1.2 binding is proposed as the mandatory protocol binding. The corresponding WSDL 1.1 description document of such a web service is specified. In defining the Web service, the present document makes reference to interactions between different parties and to the end user experience of a mobile signature service at the mobile device. This is done to illustrate concepts and facilitate definition of the Web service - only. Readers are referred to other sources of information as indicated in clause 2 regarding definitions and specifications for these topics. Structure of the present document: • Scope: a description of the goals and objectives of the present document. • Document Administration: an explanation of the structure, definitions, symbols and abbreviations used in the present document. • Introduction to mobile signature: positions the Mobile Signature project and EC funding etc leading to overview of why mobile signature has a way to accelerate deployment of electronic signatures as originally envisaged by the EU Directive. • Mobile Signature Service Functions: this section describes the high-level functionalities provided by a Mobile Signature Service Provider. • Mobile Signature Web Service: the Mobile Signature Service is specified as a Web Service in this section. • Message Formats: the XML messages exchanged between an Application Provider and a Mobile Signature Service Provider are presented. • Auxiliary XML Data Types: the messages presented in the previous chapter are based upon the XML data types specified here. • Communication Protocol Binding: the protocol binding for the Mobile Signature Service is specified as SOAP 1.2 over HTTP. • Web Service - Security and Privacy Considerations: Security and Privacy considerations with respect to the Mobile Signature Service are presented. ETSI ETSI TS 102 204 V1.1.4 (2003-08) 8 |
102 111-1 | Services and Protocols for Advanced Networks (SPAN); Network Integration Testing between General Packet Radio Service (GPRS) and Internet Protocol (IP) Networks; Part 1: Test Suite Strucutre and Test Purposes (TSS&TP) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/10211101/01.01.01_60/ts_10211101v010101p.pdf | The present document specifies the Test Suite Structure and Test Purposes for Network Integration Testing to verify the overall compatibility between GPRS (UMTS, GSM Phase 2+) and IP Networks. The objective is to verify the level of international or national end-to-end support of GPRS services. |
102 206 | Mobile Commerce (M-COMM); Mobile Signature Service; Security Framework | TR | 1.1.3 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102206/01.01.03_60/tr_102206v010103p.pdf | The Mobile Signature Service is a service provided by a Mobile Signature Service Provider (MSSP) to a Signer and an Application Provider (AP). Because a Mobile Signature is a "universal method for using a mobile device to confirm the intention of a citizen to proceed with a transaction" (see TR 102 203 [18]), the Mobile Signature Service becomes a crucial security element within the architecture of the Application Provider itself. In the case of transactions (e.g. financial) that rely on a Mobile Signature, the issue of liability may be raised. Both parties, i.e. the enduser and the Application Provider are willing to protect themselves from fraudulent behaviours between each other, or even from hackers, thanks to the Mobile Signature. Without a wide and common understanding of the security considerations for Mobile Signatures by all parties (e.g. the Signer, the Application Provider etc.), it will be quite difficult for MSSPs to build commercial agreements with those parties. In this respect, it is essential for all the stakeholders to identify the level of security, a MSSP may, should, or must provide. This is the purpose of the present document. The concept of Mobile Signatures has also to be linked with the current work of EESSI on electronic signatures taking into account the specificities of the mobile environment. TR 102 203 [18] explain that a Mobile Signature is an electronic signature that goes mobile. The present document clarifies the meaning of this sentence in the context of the security requirements of the European Directive. |
102 209 | Telecommunications and Internet converged Services and Protocols for Advancing Networks (TISPAN); Telecommunication Equipment Identification | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102209/01.02.01_60/ts_102209v010201p.pdf | The present document provides the information for the identification of telecommunication equipment. The present document focuses on both manufacturers and PNOs' needs when exchanging information. This information can be used either externally or internally. Based on an analysis of the results of a survey TR 102 214 [2], the present document identifies the data elements which are considered to be necessary and sufficient to identify equipment. In addition to that, the present document provides associated information which is found useful to be exchanged between manufacturers and PNOs. The format of the Equipment Identity is out of scope of the present document. |
102 210 | Broadband Radio Access Networks (BRAN); HIPERMAN; System profiles | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102210/01.02.01_60/ts_102210v010201p.pdf | The present document specifies the HiperMAN system profiles. System profiles provide recommended implementations of HiperMAN compliant systems. Compliance with the HiperMAN specification does not require compliance with the present document. |
102 214 | Services and Protocols for Advanced Networks (SPAN); Result of the PNOs and Equipment Manufacturers questionnaires for identification of Equipment Unit | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102214/01.01.01_60/tr_102214v010101p.pdf | The present document is the result of a survey which was conducted in the fourth quarter of 2002 to evaluate and list the information needed by the PNOs and Manufacturers regarding Equipment Identification. |
102 215 | Electromagnetic compatibility and Radio spectrum Matters (ERM); Recommended approach, and possible limits for measurement uncertainty for the measurement of radiated electromagnetic fields above 1 GHz | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102215/01.03.01_60/tr_102215v010301p.pdf | The present document presents an evaluation of maximum acceptable measurement uncertainty for Radio Frequency (RF) electromagnetic field (emf) measurements above the frequency one gigahertz (1 GHz) for inclusion within ETSI harmonized standards and radio product standards used for compliance testing. The recommended maximum acceptable measurement uncertainty is given for the following measurement parameters: • radiated RF power; • radiated spurious emissions; and • EMC radiated emissions. The maximum frequency recommendations are based upon current capabilities of measurement equipment at May 2003 and the ability to calculate measurement uncertainty from traceable calibration certificates. Frequencies above the recommended maximum frequency for each method of measurement are for further study. A recommendation is given on how to apply the laboratory calculated measurement uncertainty to a measured parameter and to assess the quality of the measurement against a defined limit given in a standard. The present document contains the results of many discussions held with test equipment manufacturers, test laboratories, administrations, trade associations, societies, and members of the GRSC, all who have an interest in measurement uncertainty above 1 GHz. In determining the maximum acceptable measurement uncertainty, particular account has been taken of current methods of measurement already identified in ETSI standards. However where there is an inconsistency, or uncertainties that have not previously been taken into account in the uncertainty budgets, these are clearly identified in the relevant clauses. Whilst an analysis has been carried out on safety related measurements by ETSI, the responsibility for standards rests with CENELEC. The present document will include any recommendations from CENELEC TC 106X related to radiated measurements in a future edition. Fixed link microwave methods of measurement do not use radiated measurements only conducted measurements (excepting EMC testing). Therefore they are considered outside the scope of the present document. However, as new technologies with integral antennas are being developed, this may be reviewed in a future edition. Satellite equipment is outside the scope of the present document, however, this may be reviewed in a future edition. The measurement uncertainty for conducted measurements is outside the scope of the present document. The use of a test jig for radiated RF measurements of integral antenna radio equipment is outside the scope of the present document. Annex A contains historical examples of the application of shared risk within ETSI standards. Annex B contains examples of measurement uncertainty calculations, some of which are still under development. Annex C is reserved for data files to be used in the calculation of radio parameter measurement uncertainties. Annex D contains a list of all relevant contributions to radiated measurement uncertainty extracted from TR 102 273-1-2 [4]. ETSI ETSI TR 102 215 V1.3.1 (2004-11) 8 |
102 216 | Smart Cards; Vocabulary for Secure Element Technologies specifications | TR | 5.1.0 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102216/05.01.00_60/tr_102216v050100p.pdf | The purpose of the present document is to identify specialist technical terms used within the Secure Element Technologies (SET) project for the purposes of writing technical documents. The motivations for this are: • to ensure that editors use terminology that is consistent across specifications; • to provide a reader with convenient reference for technical terms that are used across multiple documents; • to prevent inconsistent use of terminology across documents. The present document is a collection of terms, definitions, abbreviations and acronyms related to the baseline documents defining SET objectives and systems framework. The present document provides a tool for further work on SET technical documentation and facilitates their understanding. The terms, definitions and abbreviations as given in the present document are either imported from existing documentation (SET, 3GPP, ETSI, ISO/IEC or elsewhere) or newly created by smart card experts whenever the need for precise vocabulary was identified. The following types of terms and acronyms are not included in the present document: • terms and acronyms generally used in computer science, information technology and cryptography; • terms and acronyms from specific application domains such as mobile telephony and banking; • terms and acronyms defined and used solely within a specific SET specification to facilitate readability. But such terms and acronyms may be included if they are frequently used in the SET specifications and a common, precise definition of the term or acronym would aid the interpretation and implementation of the specifications. |
102 219 | Methods for Testing and Specification (MTS); The IDL to TTCN-3 Mapping | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102219/01.01.01_60/ts_102219v010101p.pdf | The present document defines the mapping rules for CORBA IDL (as defined in chapter 3 in [4]) to TTCN-3 (as defined in ES 201 873-1 [1]) to enable testing of CORBA-based systems. The principles of mapping CORBA IDL to TTCN-3 can be also used for the mapping of interface specification languages of other object-/component-based technologies. The specification of other mappings is outside the scope of the present document. |
102 220 | Access and Terminals (AT); Technical Specification: Delivery of Cable based services across a home access to the devices in the home | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102220/01.01.01_60/ts_102220v010101p.pdf | The present document describes the technology interface requirements that all appropriate home-networking technologies can use for access to the cable network. The present document spans the description of service data types, requirements for system performance, QoS support, network-based management and local network management. It addresses networks that are installed in residences and used for the transport of information encoded in a digital format. The main emphasis is on IP-based networks. However, some aspects also apply to the primary distribution of digital media (digital video and audio information) over cable networks. |
102 221 | Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 18) | TS | 18.3.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102221/18.03.00_60/ts_102221v180300p.pdf | The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3 [11]; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. Starting from Release 17, the UICC may support Logical Secure Element interfaces, which allows it to host multiple logical secure elements. A special form of such a Logical Secure Element (LSE) is a logical UICC. Where required, the lower layers which represent the features common to all LSEs are denoted as LSE base. The applicability of the clauses in the present document to either the LSE base or to the logical UICC is given in the introduction of each affected clause. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document. |
102 222 | Integrated Circuit Cards (ICC); Administrative commands for telecommunications applications (Release 17) | TS | 17.1.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102222/17.01.00_60/ts_102222v170100p.pdf | The present document defines functions and syntax of a set of administrative commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2] series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1]. For a UICC supporting logical secure elements as defined in ETSI TS 102 221 [5], the provisions of the present specification apply to the logical UICC. The present document does not cover the internal implementation within the UICC and/or the external equipment. |
102 223 | Smart Cards; Card Application Toolkit (CAT) (Release 18) | TS | 18.2.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/18.02.00_60/ts_102223v180200p.pdf | The present document defines the interface between the UICC and the terminal, and mandatory terminal procedures, specifically for "NAA Card Application Toolkit". The Card Application Toolkit (CAT) is a set of generic commands and procedures for use by the ICC, irrespective of the access technology of the network. Within the scope of the present document, the UICC refers here to an ICC which supports at least one application in order to access a network. This application is called here Network Access Application (NAA). The ICC is considered as a platform, which is either based on ETSI TS 102 221 [1] or ETSI TS 102 600 [38], here called "3G platform" or ETSI TS 151 011 [8], here called "2G platform". NAA can be: • a USIM application, as defined in ETSI TS 131 102 [6], which can reside only on a 3G platform; • a SIM application, as defined in ETSI TS 151 011 [8], which can reside either on a 3G or a 2G platform; • a TSIM application, as defined in ETSI TS 100 812 [i.2], which can reside only on a 3G platform; • a ISIM application, as defined in ETSI TS 131 103 [36], which can reside only on a 3G platform; • a CSIM application, as defined in 3GPP2 C.S0065-B [53]; • an R-UIM application, as defined in 3GPP2 C.S0023-D [i.4]; or • other applications residing on a 3G platform or a 2G platform. Specifying the interface is to ensure interoperability between an ICC and a terminal independently of the respective manufacturers and operators. The present document specifies as well mechanisms in order to expand the generic set of commands and procedures by access technology specific ones. The present document defines: • the commands; • the application protocol; • the mandatory requirements on the ICC and terminal for each procedure. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the ICC or the terminal are only specified where these reflect over the interface. The present document does not specify any of the security algorithms that may be used. |
102 224 | Smart Cards; Security mechanisms for UICC based Applications Functional requirements (Release 18) | TS | 18.0.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102224/18.00.00_60/ts_102224v180000p.pdf | The present document provides standardized security mechanisms in conjunction with the Card Application Toolkit for the interface between a Network Entity and a UICC. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in ETSI TS 102 225 [1]. Within the scope of the present document, the UICC refers here to an ICC which support at least one application in order to access a cellular network. The ICC is considered as a platform, which is based on ETSI TS 102 221 [4]. |
102 207 | Mobile Commerce (M-COMM); Mobile Signature Service; Specifications for Roaming in Mobile Signature Services | TS | 1.1.3 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102207/01.01.03_60/ts_102207v010103p.pdf | Basically, an Application Provider should be able to get a Mobile Signature from any enduser, even if the Application Provider and the enduser have not contracted a commercial relationship with the same Mobile Signature Service Provider. Otherwise, an Application Provider would have to build commercial terms with as many MSSPs as possible, and this might be a cost burden. This means that a Mobile Signature transaction issued by an Application Provider should be able to reach the appropriate Mobile Signature Service Provider, and this should be transparent for the Application Provider and the enduser. This is the concept of Mobile Signature Roaming. The present document specifies technical interfaces over SOAP and HTTP for architectures that facilitate the roaming of mobile signature messages between the enduser and an Application Provider, and facilitate the building of an open model. These standardized interfaces must allow: • many-to-many relationships between stakeholders, relying parties and customers; • both centralized or decentralized approach so that endusers and Application Providers are able to establish multiple trusted relationships; • a minimized number of intermediaries between an enduser and an Application Provider; • a common understanding between the Mobile Signature Service Provider and the Application Provider of the security involved in a mobile signature process; • keep track of the path taken by the roaming transaction; • a dispute resolution policy between Application Provider, Enduser, Home MSSP, Acquiring Entity and all the intermediaries involved in the roaming of the transaction. |
102 226 | Smart Cards; Remote APDU structure for UICC based applications (Release 19) | TS | 19.0.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102226/19.00.00_60/ts_102226v190000p.pdf | The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225 [1]. It specifies the APDU format for remote management. Furthermore the present document specifies: • A set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221 [2]. • A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specification [4], its Amendments and Configuration documents. |
102 228 | Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Technology Mapping; Implementation of TIPHON architecture using BICC | TS | 4.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102228/04.01.01_60/ts_102228v040101p.pdf | The present document defines the mapping to the BICC CS2 protocols necessary to implement the TIPHON protocol framework as described in TS 101 882 [2]. The present document is applicable to equipment performing the roles of terminal, and Gateway, and also to entities within the IP network that are necessary to support the four scenarios of TIPHON Release 3. Where the text indicates the status of a requirement (i.e. as strict command or prohibition, as authorizations leaving freedom, or as a capability or possibility), this may modify the nature of a requirement within a referenced standard used to provide the capability. |
102 229 | Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interface Protocol Requirements Definition; Aggregate Bearer Load Control - H.248 Package | TS | 4.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102229/04.01.01_60/ts_102229v040101p.pdf | The present document defines the aggregate load control information flows which are part of the N2 and N3 reference points network architecture as described in TS 101 882 release 4 [1]. The present document is supporting only provisioned aggregate bearer functionality. Mixing of different bearer capabilities of PSTN/ISDN service over the same aggregate bearer is supported. The aggregate bearer is provisioned with a single set of QoS parameters. |
102 230 | Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 10) | TS | 10.2.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/10.02.00_60/ts_102230v100200p.pdf | The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures. |
102 230-1 | Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 17) | TS | 17.3.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/17.03.00_60/ts_10223001v170300p.pdf | The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures. |
102 230-2 | Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 17) | TS | 17.4.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/17.04.00_60/ts_10223002v170400p.pdf | The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document. |
102 232-1 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery | TS | 3.36.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223201/03.36.01_60/ts_10223201v033601p.pdf | The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document: • specifies the modular approach used for specifying IP based handover interfaces; • specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively; • specifies protocols for the transfer of IRI and CC across the handover interfaces; • specifies protocol profiles for the handover interface. The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply. |
102 232-2 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services | TS | 3.16.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223202/03.16.01_60/ts_10223202v031601p.pdf | The present document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include email, unified messaging and chat applications. The definition of handover transport and encoding of HI2 and HI3 is outside the scope of the present document. Refer to ETSI TS 102 232-1 [3]. The present document is designed to be used where appropriate in conjunction with other deliverables that define the service specific IRI data formats. The present document aligns with 3GPP TS 33.108 [5], ETSI TS 101 671 [i.3], ETSI TS 101 331 [1] and ETSI TR 101 944 [i.1]. |
102 232-3 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services | TS | 3.16.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223203/03.16.01_60/ts_10223203v031601p.pdf | The present document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The present document includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets. The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1 [2]. |
102 232-4 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services | TS | 3.8.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223204/03.08.01_60/ts_10223204v030801p.pdf | The present document specifies Lawful Interception for an Access Provider that has access to layer 2 session information and that is not required to have layer 3 information. In this case, the focus of Lawful Interception (LI) for IP Network Access is on the portion of the network, commonly referred to as "layer 2 interception", that facilitates subscriber access to the Public IP network. The present document describes the LI at the interception domain of the access network. The present document contains: • a stage 1 description of the Lawful Interception service; • a stage 2 description of the information flows between the functional entities (including the information elements involved) and triggering events; and • a stage 3 description of the protocol and procedures to be used in mapping from stage 2 information flows and elements to Intercept Related Information (IRI) and Content of Communication (CC). The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. NOTE 1: Layer 3 interception is described in ETSI TS 102 232-3 [12]. NOTE 2: Layer 2 interception is not applicable to the PS domain of the GSM/UMTS networks (3GPP TS 23.060 [15]). |
102 232-5 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services | TS | 3.22.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223205/03.22.01_60/ts_10223205v032201p.pdf | The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3]. The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [1]. |
102 232-6 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services | TS | 3.5.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223206/03.05.01_60/ts_10223206v030501p.pdf | The present document contains service-specific details for the handover of the lawfully intercepted PSTN/ISDN Services (including emulated services such as those defined in ETSI ES 282 002 [i.3]) using packet-based techniques as defined in ETSI TS 102 232-1 [2]. |
102 232-7 | Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services | TS | 3.13.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223207/03.13.01_60/ts_10223207v031301p.pdf | Introduction The present document specifies an approach for the handover of the lawfully-intercepted information that is defined in the two standards: 3GPP TS 33.108 [3] and 3GPP TS 33.128 [6]. The present document uses the handover techniques defined in ETSI TS 102 232-1 [2]. In this way, the present document allows additional services to be delivered through a common interface. 3GPP TS 33.108 The scope of the present document includes the handover of lawfully-intercepted information from the following parts of 3GPP TS 33.108 [3]: • Intercept Related Information (IRI) and the Content of Communication (CC) from the mobile circuit-switched domain (3GPP TS 33.108 [3], clause 5). • IRI and CC from the mobile packet-switched domain (3GPP TS 33.108 [3], clause 6). • IRI and CC from the multi-media domain (3GPP TS 33.108 [3], clause 7). • IRI and CC from the EPS domain (3GPP TS 33.108 [3], clause 10). • IRI and CC from the IMS Conference domain (3GPP TS 33.108 [3], clause 11). • IRI and CC from the IMS-based VoIP domain (3GPP TS 33.108 [3], clause 12). • IRI from the Proximity Services domain (3GPP TS 33.108 [3], clause 13). • IRI and CC from the Group Communication System Enablers domain (3GPP TS 33.108 [3], clause 14). The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [3]. 3GPP TS 33.128 The scope of the present document includes the handover of lawfully-intercepted information in accordance with 3GPP TS 33.128 [6]. |
102 235 | Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Pre-normative Study for IPv6 Testing | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102235/01.01.01_60/tr_102235v010101p.pdf | The present document defines the scope of an IPv6 test specification programme that supports the "IPv6 Ready" certification programme, the European Commission's IPv6 deployment goals and priorities, and ETSI's own needs for IPv6 testing. Analyses, justifications, and supporting documentation are included. The testing programme is closely associated with the eEurope 2005 action plan. This plan asks the European standardization organizations to propose a 3-year work plan (for 2003, 2004, and 2005) to support new priorities, some of which concern IPv6 testing. Thus, the testing programme is composed of short and medium-term plans (from 2003 through 2005) using resources from eEurope 2005 and ETSI members' voluntary and funded contributions. The present document also contains proposals to request 2003 funding via the eEurope 2005 action plan. |
102 237-1 | Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing | TS | 4.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223701/04.01.01_60/ts_10223701v040101p.pdf | The present document, "A generic approach to interoperability testing", gives general guidance on the specification and execution of interoperability tests for communication systems in Next Generation Networks (NGN). It provides a framework within which interoperability test specifications for a wide range of product types can be developed. The guidelines are expressed as recommendations rather than strict rules and leave enough freedom to allow test specifiers to adopt and adapt processes to suit each particular project while still ensuring that test specifications accurately reflect the requirements of the base standards and can be executed consistently across a range of configurations. Interoperability testing is the structured and formal testing of functions supported remotely by two or more items of equipment communicating by means of standardized protocols. It is not the detailed verification of protocol requirements specified in a conformance test suite, neither is it the less formal development testing often associated with plug-fest and interop events (frequently referred to as "bake-offs"). Although some consideration is given within the methodology to the operating and reporting aspects of interoperability testing, the primary focus of the present document is on the specification of interoperability testing architectures, test plans and test suites. |
102 237-2 | Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 2: H.323-SIP interoperability test scenarios to support multimedia communications in NGN environments | TS | 4.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10223702/04.01.01_60/ts_10223702v040101p.pdf | The present document describes an H.323-SIP Interoperability Test Suite focusing on test cases for functionality that include protocol interworking. It is based on the documents TS 101 883 [11] (H.323 Profile) and TS 101 884 [12] (SIP Profile) of TIPHON Release 3. |
102 035 | Digital Video Broadcasting (DVB); Implementation Guidelines of the DVB Simulcrypt Standard | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102000_102099/102035/01.01.01_60/tr_102035v010101p.pdf | The present document provides implementation guidelines for the use and implementation of the DVB Simulcrypt standard. It first tries to draw attention to the technical questions that need to be answered in setting up a DVB Simulcrypt head- end. It also provides guidelines which are intended to be highly recommended rules and as such, aims to facilitate the efficient and reliable implementation of the Simulcrypt model and of its interfaces. The rules apply to broadcasters, network operators as well as manufacturers. Clause 4 "Architecture" presents the DVB Simulcrypt Architecture Model as described in TS 103 197 [6]. Clause 5 "Compliance between version 1 and version 2 of the standard" explains how to support compliance between both versions 1 and 2 of ECMG and EMMG/PDG protocols. Clause 6 "ECMGSCS Protocol" fulfils the ECMG protocol description mainly by giving the state diagram. Clause 7 "EMMG/PDGMUX protocol" fulfils the EMMG/PDG protocol description by giving the state diagram and by clarifying the bandwidth concept, UDP behaviour and datagram packetization rules. Clause 8 "C(P)SIG(P)SIG" describes profiles for adapting the C(P)SIG protocol implementation to real and simple needs. Clause 9 "SIMF based protocols - Role of NMS" allows for reducing the use of the MIB for monitoring only. Clause 10 "Error management" clarifies error management in DVB Simulcrypt protocols. Clause 11 "Redundancy management" sums up uniqueness aspects of protocol parameters and describes basic redundancy policies for functions of the DVB Simulcrypt architecture model. The present document uses the terminology defined in TS 103 197 [6] and should be read in conjunction with that document. ETSI ETSI TR 102 035 V1.1.1 (2002-04) 7 |
102 241 | Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 18) | TS | 18.1.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/18.01.00_60/ts_102241v180100p.pdf | The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers. |
102 242 | Smart Cards; Terminal - card interface; Considerations on robustness improvements | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102242/03.00.00_60/tr_102242v030000p.pdf | The present document describes: • the failure mechanisms that could potentially generate major operating issues between the terminal and the card; • the countermeasures that should be applied within the current specifications; • the enhancements that may further increase the interface robustness. |
102 243-1 | Fixed Radio Systems; Representative values for transmitter power and antenna gain to support inter- and intra-compatibility and sharing analysis; Part 1: Digital point-to-point systems | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/10224301/01.02.01_60/tr_10224301v010201p.pdf | The present document summarizes, in relation to the various frequency bands and sub-system types given in the multipart EN 302 217 [i.2] to [.i.7], information in relation to current practical bounds coming from technology and deployment practice about: • Typical-maximum TX power (see note). • Typical-maximum antenna size and gain. • Exceptional antenna size and gain. NOTE: This should not be intended as the power delivered by equipment currently on the market; it indicates the level that is reasonably achievable by FS technology in each band and might be rendered available standing suitable market opportunities justifying the cost/benefit trade off. Antenna gain is also related to its expected typical antenna size, which nowadays, for its ambient impact, is another important factor limiting, in practice, most of FS deployments. The above values are here reported here due to a lack of any ECC harmonized regulations. In the event that such ECC regulations would come into force, it would supersede any less restrictive information given in the present document. In the band 57 GHz to 64 GHz CEPT promotes an uncoordinated or simplified use of the band as outlined in ECC Recommendation (09)01 [i.9]. Also in the band 64 GHz to 66 GHz ECC Recommendation (05)02 [i.10] provides for simplified channel arrangement suitable for simplified regulatory approach (e.g. light licensing/notification). In the bands 71 GHz to 76 GHz and 81 GHz to 86 GHz ECC Recommendation (05)07 [i.11] provides flexible arrangements suitable for both simplified regulatory approach (e.g. light licensing/notification) or conventional coordination; CEPT administrations would freely select the approach best fitting their policy for the bands. |
102 250-1 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 1: Assessment of Quality of Service | TS | 2.3.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225001/02.03.01_60/ts_10225001v020301p.pdf | The present document serves as a generic umbrella document for the further documents part 2 to part 8 of this series. It gives an overview over the topics addressed by these documents and enables the reader to work with the documents in the intended way. It is important to understand that the complete series of documents focuses on Quality of Service which stands for the objective discussion of quality measures from a rather technical perspective. Based on existing quality standards and further definitions, a complete picture of Quality of Service as seen from a user's point of view is drawn. Wherever possible, existing ITU-T or ETSI definitions are referenced. If ITU-T or ETSI definitions do not exist or are considered as too generic, a more service and mobile network specific definition is made. The present document comprises the theoretical backgrounds to understand terms like "Quality of Service", "Network Performance" and "Quality of Experience". Their meaning and interrelation are discussed by taking different QoS models into account. |
102 250-2 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 2: Definition of Quality of Service parameters and their computation | TS | 2.7.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225002/02.07.01_60/ts_10225002v020701p.pdf | The present document defines QoS parameters and their computation for popular services in mobile networks. The harmonized definitions given in the present document are considered as the prerequisite for the comparison of QoS measurements and their results. It is assumed that the end user can handle his mobile terminal and the services he wants to use (operability is not evaluated). The computation of specific QoS parameters may vary depending on the respective mobile network, e.g. GSM or 3GPP specified 3G system. In this case a respective notification is provided. Other standardization bodies may request an approved document containing specific QoS parameters to be used as reference in their documents. Therefore, the present document may contain incomplete QoS parameter definitions, e.g. giving a description but missing technical trigger points. Such points are marked as "tbd" (to be defined) and will be updated as soon as possible. |
102 250-3 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 3: Typical procedures for Quality of Service measurement equipment | TS | 2.4.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225003/02.04.01_60/ts_10225003v020401p.pdf | The present document describes typical procedures used for QoS measurements on mobile communication networks, along with settings and parameters for such measurements. Where possible, existing ITU-T or ETSI definitions are referenced. In some cases ITU-T or ETSI definitions do not exist or are considered too generic, then a more service and mobile network specific definition is chosen. |
102 250-4 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 4: Requirements for Quality of Service measurement equipment | TS | 2.3.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225004/02.03.01_60/ts_10225004v020301p.pdf | The present document defines the minimum requirements of QoS measurement equipment for digital wireless networks in the way that the values and trigger-points needed to compute the QoS parameter as defined in ETSI TS 102 250-2 [3] can be measured following the procedures defined in ETSI TS 102 250-3 [4]. Test-equipment fulfilling the specified minimum requirements, will allow performing the proposed measurements in a reliable and reproducible way. |
102 250-5 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 5: Definition of typical measurement profiles | TS | 2.5.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225005/02.05.01_60/ts_10225005v020501p.pdf | The present document specifies test profiles which are required to enable benchmarking of different mobile networks both within and outside national boundaries. It is necessary to have these profiles so that when a specific set of tests is carried out then users are comparing "like for like" performance. All timeouts (as part of the profiles) given in the present document are examples from proven experience. It should be noted that most timeouts given in the present document do, with respect to failure ratios as defined in ETSI TS 102 250-2 [1], have a direct impact on measurement results. A timeout value might for example directly relate to the stop trigger point in the sense of the timeout reached event being the point in time where a certain state has not been reached. |
102 250-6 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 6: Post processing and statistical methods | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225006/01.03.01_60/ts_10225006v010301p.pdf | The present document describes definitions and procedures to be used for statistical calculations which are related to Quality of Service (QoS) measurements done by serving probing systems in mobile communications networks, especially GSM and 3G networks. Network performance measurements and their related post-processing are only marginally covered in the present document. |
102 250-7 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 7: Network based Quality of Service measurements | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/10225007/01.02.01_60/ts_10225007v010201p.pdf | The present document specifies how the quality of service parameters, listed in ETSI TS 102 250-2 [1], should be used for measurements done inside a network, in contrary to measurements done in the end-point with a test tool. A test tool can be either stationary or a drive test tool. The measurements of the QoS parameters according to the present document should be done using standardized interfaces and protocols. This is done to ensure that all measurements in a multi-vendor network can be compared. |
102 250-8-1 | Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 8: Formalized definition of Quality of Service parameters and their computation; Sub-part 1: General aspects and terminology | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/1022500801/01.01.01_60/ts_1022500801v010101p.pdf | The present document defines a consistent terminology for the formalized definition of quality of service (QoS) parameters and their computation. In doing so, it carefully distinguishes between measurable quantities and associated statistical aggregation formulas. For frequently used types of quantities and aggregations, generic symbols and calculation formulas are specified. For a large class of QoS parameters, which are basically determined by the observation of events, the present document specifies a methodology for constructing definitions in two stages, using the concept of abstract events and their representation by technical events at well-defined points of observation. In addition, a framework is presented which indicates how QoS parameters may be derived in a generic way via sub- dividing the usage of a service into meaningful sub-transactions, called "phases". |
102 251 | Speech Processing, Transmission and Quality Aspects (STQ); Anonymous Test Report from 2nd Speech Quality Test Event 2002 | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102251/01.01.01_60/tr_102251v010101p.pdf | The present document contains the anonymous Test Report from the 2nd Speech Quality Test Event 2002. |
102 252 | Digital Video Broadcasting (DVB); Guidelines for implementation and use of the control channel for SMATV/MATV distribution systems | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102252/01.01.01_60/tr_102252v010101p.pdf | The present document provides the first guidance to manufacturers, network operators and service providers on equipment design for the use of the Control Channel for SMATV/MATV systems, whose baseline specification is given in TS 101 964 [1]. The Control Channel for SMATV/MATV distribution systems is intended to provide remote control of the head-end device from the user's terminal through a set of commands in a closed in-building environment for the delivery of broadcast services. Furthermore, the Control Channel allows each single user of the building to autonomously decide on the possibility of receiving digital broadcasting services through the community installation, without the need of authorisation from the other users. So the user connected via the in-building cable network can access the broadcast services, satellite and terrestrial, as in the case of "individual reception". The Control Channel protocol is based on DiSEqC [2] to maintain compatibility with existing products and has the further advantage of being sufficiently flexible to allow for future extensions, if and when needed. The structure of the Control Channel message ensures a robust transmission mechanism. SMATV/MATV distribution systems, as described in EN 300 473 [3], represent a solution widely adopted for in- building delivery of DVB signals (both satellite and terrestrial) through collective installations. The adoption of the Control Channel specification, which has been defined in accordance with the commercial requirements given in DVB-TM 2342 (see bibliography), offers an alternative cost-effective solution to the current implementation of SMATV/MATV systems, especially for the case of small and medium size installations, allowing the delivery of DVB TSs/multiplexes without the constraints of the limited bandwidth available in the installation. The technical specification of the Control Channel system (see TS 101 964 [1]) describes the message structure and the set of commands and coding used for remote controlling the Head-end of the SMATV/MATV distribution system. The specification covers both the approaches adopted for the delivery of satellite signals as identified in EN 300 473 [3], i.e. transmodulation from QPSK to QAM (System A) and direct distribution in QPSK after frequency conversion (System B), as well as the remote control of other head-end devices for broadcast services. The specification also takes into account the requirements from EN 301 790 [4] in order to achieve the best commonality and ensure the minimum functionality required for operating via the SMATV systems the satellite interactive terminals. Although primarily focused on SMATV systems for delivery of satellite DVB services, the Control Channel shall also be applicable to MATV systems currently used for terrestrial broadcasting services via VHF/UHF and microwave. The Physical layers of the Control Channel system, described in clauses A.1 and A.2 of TS 101 964 [1], allow for a general use of the Control Channel in the whole range of SMATV/MATV distribution systems, having different topologies and characteristics. The transmission protocol providing the communication link between the user's terminal and the head-end device makes use of the same commands and coding for both physical layers. Furthermore, since the Control Channel capacity is shared among all the user terminals, a "multiaccess" approach is adopted in order to guarantee adequate access time to the selected service. The solution presented in clause A.1 of TS 101 964 [1], which is based on the use of a 22 kHz bus, is suitable for the case of small SMATV/MATV installations using d.c. coupled elements. The solution presented in clause A.2 of TS 101 964 [1], which is based on the use of an RF bus in a frequency range above 10 MHz, provides the capability to pass through community installations using inductive components. So, this second solution potentially allows for a transparent introduction of the Control Channel in most existing SMATV/MATV systems. The present document gives details on the technical parameters and guidelines for system implementation, and provides an evaluation of the performance of the multiaccess schemes adopted for the 22 kHz bus and the RF Control Channel bus, as well as a better knowledge of the features and possibilities offered by the Control Channel protocol . FLEXIMATV Project IST-2000-28695 has been devoted to develop technological solutions based on the DVB control channel specification, aiming at consolidating that European standard, introducing any necessary enhancements and producing clear guidelines on the best practices for implementing DVB control channel systems. These contributions have been included in the present document. Consequently, FLEXIMATV has been aimed at the consolidation of a mature standard supported and endorsed by the analysis and studies, development of industrial solutions, confirmation of suitable performances through appropriate tests in laboratory and in real installations. ETSI ETSI TR 102 252 V1.1.1 (2003-10) 7 |
102 253 | Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access (MCA) Profile Standard | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102253/01.01.01_60/ts_102253v010101p.pdf | The present document specifies the combination of base standards, together with the selection of appropriate options and parameter values, necessary to specify how QSIG / PSS1 can be used for Message Centre Access (MCA) procedures. The present document identifies the necessary or optional employment of particular functions, procedures and services for: • a Calling User to deposit messages for a Served User at a Message Centre; • a Served User to monitor the Served User's Mailbox for new messages; • a Served User to browse through the messages saved in the Served User's Mailbox; • a Served User to retrieve the messages saved in the Served User's Mailbox; and • a Served User to get connected to the Originator of a message or any other destination. |
102 254 | Private Integrated Services Network (PISN); Specification, functional model and information flows; Message Centre Monitoring and Mailbox Identification supplementary service | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102254/01.01.01_60/ts_102254v010101p.pdf | The present document specifies supplementary service Message Centre Monitoring/Mailbox Identification (SS- MCM/MID), which is related, but not limited, to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ECMA-142 [2]. The supplementary service MCM enables a Served User to get informed by a Message Centre about the status and status changes of messages stored in that Served Users Mailbox. The supplementary service MID enables a Message Centre to identify a specific mailbox of a Served User in case that the Served User has more than one Mailbox within the Message Centre. In addition SS-MID enables a Served User to authenticate himself/herself at a specific Mailbox located within the Message Centre. Service specifications are produced in three stages, according to the method described in ETS 300 387 [1]. The present document contains the stage 1 and stage 2 specifications of SS-MCM/MID. The stage 1 specification (see clauses 6 and 7) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (see clauses 8 and 9) specifies the functional entities involved in the supplementary service and the information flows between them. |
102 255 | Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Message Centre Monitoring and Mailbox Identification supplementary service | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102255/01.01.01_60/ts_102255v010101p.pdf | The present document specifies the signalling protocol for the support of the Message Centre Monitoring supplementary service (SS-MCM) as well as the Mailbox Identification supplementary service (SS-MID) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). The supplementary service MCM enables a Served User to get informed by a Message Centre about the status and status changes of messages stored in that Served Users Mailbox. The supplementary service MID enables a Message Centre to identify a specific mailbox of a Served User in case the Served User has more than one mailbox within the Message Centre. In addition SS-MID enables a Served User to authenticate himself/herself at a specific mailbox located within the Messages Centre. The Q reference point is defined in ECMA-133 [1]. Service specifications are produced in three stages and according to the method specified in ETS 300 387 [9]. The present document contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ECMA-346 [8]. The signalling protocol for SS-MCM and SS-MID uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165 [4]. The present document also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between SS-MCM as well as SS-MID and other supplementary services and ANFs. NOTE: Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications. |
102 256 | Private Integrated Services Network (PISN); Specification, functional model and information flows; Make Call Request supplementary service | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102256/01.01.01_60/ts_102256v010101p.pdf | The present document specifies Supplementary Service Make Call Request (SS-MCR), which is related, but not limited, to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ECMA-142 [2]. The supplementary service MCR enables a Requesting User to request a Co-operating User to establish a new Requested Call to a Destination User. This new Requested Call between the Co-operating and Destination User can be either a Basic call or call independent signalling connection. Service specifications are produced in three stages, according to the method described in ETS 300 387 [4]. The present document contains the stage 1 and stage 2 specifications of SS-MCR. The stage 1 specification (clause 6) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (clause 7) specifies the functional entities involved in the supplementary service and the information flows between them. |
102 257 | Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Make Call Request supplementary service | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102257/01.01.01_60/ts_102257v010101p.pdf | The present document specifies the signalling protocol for the support of the Supplementary Service Make Call Request (SS-MCR) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). Supplementary service MCR enables a Requesting User to request a Co-operating User to establish a new Requested Call to a Destination User. This new Requested Call between the Co-operating and Destination User can be either a Basic call or a Call Independent Signalling Connection. The Q reference point is defined in ECMA-133 [1]. Service specifications are produced in three stages and according to the method specified in ETS 300 387 [6]. The present document contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ECMA-343 [4]. The signalling protocol for SS-MCR operates on top of the signalling protocol for basic circuit switched call control, as specified in ECMA-143 [2], and uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165 [3]. The present document also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between SS-MCR and other supplementary services and ANFs. The present document is applicable to PINXs, which can interconnect to form a PISN. |
102 258 | PowerLine Telecommunications (PLT); LCL review and statistical analysis | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102258/01.01.01_60/tr_102258v010101p.pdf | The present document presents the results from LCL measurements performed in Germany, The Netherlands and Spain. It investigates the distribution of the LCL values in respect to the frequency and to the national LVDN-particularities (wiring technology, earthing etc.). |
102 259 | PowerLine Telecommunications (PLT); EMI review and statistical analysis | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102259/01.01.01_60/tr_102259v010101p.pdf | The present document presents the results from EMI measurements performed in Germany, the Netherlands and Spain. It investigates the distribution of the EMI values in respect to the frequency and to the national LVDN-particularities (wiring technology, earthing, etc.). |
102 260 | Electromagnetic compatibility and Radio spectrum Matters (ERM); Code Division Multiple Access Public Access Mobile Radio (CDMA-PAMR); System reference document | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102260/01.01.01_60/tr_102260v010101p.pdf | This System Reference Document has been produced following a request from CEPT working group FM to ETSI and under the MoU between ETSI and CEPT. The objective of the present document is to consider services, business and technical aspects of a CDMA system for PAMR operation in the following bands: • 410 MHz to 420 MHz/420 MHz to 430 MHz; • 450 MHz to 460 MHz/460 MHz to 470 MHz; • 870 MHz to 876 MHz/915 MHz to 921 MHz. This PAMR system is based on CDMA-1X technology, which employs direct sequence spread spectrum code division multiple access technology and a bandwidth of 1 MHz to 25 MHz, with added proprietary functions to support PAMR functions. For convenience, this technology is described in the present document as CDMA-PAMR; however, it should be noted that this does not exclude the possibility of other PAMR systems based on CDMA being proposed in the future. The SRDoc analyses possible consequences of using CDMA-1X technology for PAMR operation, taking into account the number of potential operators in order to ensure competition and current PAMR services offered already in the relevant bands. The following information is included in the annexes to the present document: Annex A: Detailed market information; Annex B: Technical information; Annex C: Expected compatibility issues. |
102 261 | Open Network Services and Architecture (ONSA); Abstract architecture and reference points definition; Mapping of functional architectures and requirements for NGN | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102261/01.01.01_60/ts_102261v010101p.pdf | The present document is an analysis of the mapping of concrete functional architectures as defined in UMTS IMS and MSF to the TIPHON release 3.0 call control architecture. Whilst developing a generic NGN reference model, reference points and the requirements for protocols and interfaces for interconnection are identified. The objective of the present document is to verify implementation oriented architectures against the Release 3 architecture, as developed in EP TIPHON TS 101 314 [6]. This will highlight if there are incompatibilities between the architectures. This study will use the framework for interconnection reference points as defined by ITU-T SG13 in ITU-T Recommendation Y.140 [50]. Ideally, the generic reference model defines a reference architecture, which is technology independent. A functional architecture for NGN study approaches this subject by considering a decomposed call control reference model and collecting functional entities into a simplified logical structure, and referencing possible implementations. |
102 263 | Electromagnetic compatibility and Radio spectrum Matters (ERM); Road Transport and Traffic Telematics (RTTT); Radio equipment to be used in the 77 GHz to 81 GHz band; System Reference Document for automotive collision warning Short Range Radar | TR | 1.1.2 | http://www.etsi.org/deliver/etsi_tr/102200_102299/102263/01.01.02_60/tr_102263v010102p.pdf | The present document applies to Short Range Devices (SRD) in the field of Short Range Radars (SRR) operating at a frequency band in the 79 GHz range (within 77 GHz to 81 GHz) for exterior automotive applications for vehicle environmental sensing. It covers integrated transceivers and separate transmit/receive modules: • transmitters operating in range from 77 GHz to 81 GHz with peak power levels ranging up to 55 dBm; • receivers operating in the range from 77 GHz to 81 GHz. The present document applies to low power motion and distance monitoring radars for automotive applications, operating on radio frequencies in the 77 GHz to 81 GHz band, with mean power densities of up to 23,5 dBm. The remaining elements of the present document concentrate on the technical matters that are required to assist ECC/CEPT working groups FM and SE. |
102 265 | Digital Enhanced Cordless Telecommunications (DECT); DECT access to IP networks | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102265/01.02.01_60/ts_102265v010201p.pdf | The present document specifies additional requirements for DECT Internet Protocol (IP) applications including networking aspects, Voice over IP (VoIP) and other multimedia exchange over IP, mobility and quality of service properties. It provides an end system, i.e. termination of IP into the DECT Fixed Termination (FT). NOTE: Transparent IP packet service is described in EN 301 649 [16], DPRS standard. |
102 148-1-3 | Broadband Radio Access Networks (BRAN); HIPERACCESS; Conformance testing for the Packet based Convergence Layer; Part 1: Common part; Sub-part 3: Abstract Test Suite (ATS) | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/102100_102199/1021480103/01.02.01_60/ts_1021480103v010201p.pdf | The present document contains the Abstract Test Suite (ATS) to test the TS 102 117-1 [1]. The objective of the present document is to provide a basis for conformance tests for BRAN HIPERACCESS equipment giving a high probability of air interface inter-operability between different manufacturers' BRAN HIPERACCESS equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [4] and ISO/IEC 9646-2 [5]) as well as the ETSI rules for conformance testing (ETS 300 406 [3]) are used as a basis for the test methodology. - Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS. - Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the AT side ATS. - Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the AP side ATS. - Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of the AT side ATS. - Annex E provides the Protocol Conformance Test Report (PCTR) Proforma of the AP side ATS. |
102 267 | Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 18) | TS | 18.0.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/18.00.00_60/ts_102267v180000p.pdf | The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow. |
102 268 | Smart Cards; Test specification for the UICC Application Programming Interface (API) for Java Card(TM) (Release 7) | TS | 7.3.0 | http://www.etsi.org/deliver/etsi_ts/102200_102299/102268/07.03.00_60/ts_102268v070300p.pdf | The present document covers the minimum characteristics considered necessary in order to provide compliance to ETSI TS 102 241 [9]. It describes the technical characteristics and methods for testing the UICC API for Java CardTM (ETSI TS 102 241 [9]) implemented in a UICC Platform. It specifies the following parts: • test applicability; • test environment description; • tests format; • test area reference; • conformance requirements; • test area files; • test coverage; • test procedure; • a description of the associated testing tools that is used. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.