33.030 - Telecommunication services. Applications
ICS 33.030 Details
Telecommunication services. Applications
Telekommunikationsdienste. Telekommunikationsanwendungen
Services de telecommunications. Applications
Telekomunikacijske uporabniške rešitve
General Information
The scope of this Recommendation | International Standard is to define guidelines supporting the implementation of
information security controls in telecommunications organizations.
The adoption of this Recommendation | International Standard will allow telecommunications organizations to meet
baseline information security management requirements of confidentiality, integrity, availability and any other relevant
security property.
- Standard41 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft37 pagesEnglish languagesale 10% offe-Library read for1 day
The present document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision
of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the
Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is
usually mandatory for the operation of any telecommunication service.
Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI
TS 101 331 [1].
Step 2 describes the derived network functions and the general architecture (or functional model) and is published in
ETSI ES 201 158 [2].
The present document specifies:
• the generic flow of information as well as the procedures and information elements, which are applicable to
any future telecommunication network or service;
• the network/service specific protocols relating to the provision of lawful interception at the Handover Interface
(HI), for the following networks/services:
- switched circuit; and
- packet data.
The technologies covered in the present document are: GSM, TETRA, GPRS, ISDN, PSTN, fixed NGN (including
PSTN/ISDN emulation) and fixed IMS PSTN simulation.
NOTE: As new networks and/or services are developed, the present document will be expanded as the relevant
standards become available.
- Standard128 pagesEnglish languagesale 15% off
- Standard128 pagesEnglish languagesale 15% off
- Standardization document128 pagesEnglish languagesale 10% offe-Library read for1 day
The present document describes the protocol specifications for emergency service caller location determination and
transport architecture as specified in ETSI ES 203 178 [1].
- Standard39 pagesEnglish languagesale 15% off
- Standard39 pagesEnglish languagesale 15% off
- Standardization document39 pagesEnglish languagesale 10% offe-Library read for1 day
In the current competitive world, Quality of Service (QoS) is becoming, jointly with cost, a key indicator in selling and
buying telecommunications services. At the same time, technology and liberalization trends are raising new types of
concerns unknown with the Plain Old Telephony Services (POTS) using switched connections provided by a single
monopoly supplier.
Nowadays, there are several standards describing QoS measurements but the questions of which indicators are to be
monitored and which values they should meet are still open. The present document proposes a methodology for the
identification of indicators relevant to the users that can be used either to monitor the QoS of Telecom services used by
the private customers or for a Service Level Agreement (SLA) between a business customer and a supplier of
Telecommunications services such as that proposed in ETSI EG 202 009-3 [i.22]. This part 3 gives guidelines on how
to express explicit user's QoS requirements, prioritize the indicators, establish a preferred value for each of these
indicators, while ETSI EG 202 009-2 [i.21] proposes QoS indicators for each service and each step of the Customer
Relationship Course.
The present document was written to make available to the providers and users of any kind of telecom services (legacy
network based or IP network based services) a common basis for mutual understanding about quality of service. It aims
to assist users in identifying rationally their QoS requirements in terms of Service Level Objectives (SLO), helping the
providers to better meet them for their mutual benefit.
- Standard49 pagesEnglish languagesale 15% off
- Standard49 pagesEnglish languagesale 15% off
- Guide49 pagesEnglish languagesale 10% offe-Library read for1 day
Considering TS 102 650 and architectures from other standardisation organisations a single functional architecture to support European requirements on emergency caller location determination and transport needs to be developed in particular for the case where VoIP service provider and one or several network operators - all serving the customer in the establishment of an emergency call - are independent enterprises needing to co-operate to determine the location of the (nomadic) caller. The architecture shall identify all necessary interfaces, which are needed to fulfil the requirements outlined in EC Mandate M/493, and provide a basis for possible protocols to be used on those interfaces. Environmental aspect comments: 1) The establishment of emergency calls and the provision of location information about the caller shall not be hampered by high service or network loads or partial service or network outages. (2) The location information shall be provided to the PSAP in a manner that it is easily associated with the respective incoming voice call. (3) Location related information accurate enough to allow routing of the call must be constrained to those entities that require it in order to deliver the call to the correct PSAP. (4) Accurate location information shall be obtained from at least a trustworthy source. A CPE may not be considered trustworthy. User /Consumer Aspects comments: 1) The location should be determined as fast as possible. (2) Should the location determination fail for any reason, the emergency call is still to be setup without delay. (3) The access to and the provision of location information shall be strictly limited to emergency calls only. (4) The architecture shall not be based on location information provided by an entity controlled by the user. Security Aspects (1) The access to location information shall be strictly limited to cases of an emergency call. (2) Location information sufficiently detailed to dispatch personnel and resources shall only be provided to the PSAP handling the emergency call.
- Standard48 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard48 pagesEnglish languagesale 15% off
- Standard48 pagesEnglish languagesale 15% off
- Standard42 pagesEnglish languagesale 15% off
The present document specifies the functional accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement in a form that is suitable for use in public procurement within Europe. The present document might be useful for other purposes such as procurement in the private sector. The present document is intended to be used as the basis for an accessible ICT procurement toolkit. The present document will primarily be useful for public procurers to identify the requirements for their purchases, and also for manufacturers to employ it within their design, build and quality control procedures. The present document contains the necessary functional requirements and provides a reference document such that if procedures are followed by different actors, the results of testing are similar and the interpretation of those results is clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of detail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results. The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable:
• when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions are not available;
• during those parts of start-up, shutdown, and other state transitions that can be completed without user interaction.
NOTE 1: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so.
NOTE 2: Compliance issues are covered in normative clause C.1.
- Standard138 pagesEnglish languagesale 10% offe-Library read for1 day
This deliverable illustrates how CSTA XML (ECMA-323) can be used in a Voice Browser Environment.
- Technical report35 pagesEnglish languagesale 10% offe-Library read for1 day
Services and events reports supported by Computer Supported telecommunications Applications, Phase III are defined in this standard.
- Technical specification4 pagesEnglish languagesale 10% offe-Library read for1 day
This standard specifies an XML protocol for the services described in ECMA-269, Services for Computer Supported Telecommunications Applications (CSTA) Phase III
- Technical specification4 pagesEnglish languagesale 10% offe-Library read for1 day
Revision of ES 201 671 to support IP-based and other new telecommunications technologies.
- Standardization document103 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft39 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft39 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the functional accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement in a form that is suitable for use in public procurement within Europe. The present document is intended to be used with Web based technologies, non-web technologies and hybrids that use both. It covers both software and hardware as well as services. It is intended for use by both providers and procurers, but it is expected that it will also be of use to many others as well.
The relationship between the present document and the essential requirements of Directive 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies is given in Annex A.
The present document contains the necessary functional requirements and provides a reference document such that if procedures are followed by different actors, the results of testing are similar and the interpretation of those results is clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of detail compliant with ISO/IEC 17007:2009, so that conformance testing can give conclusive results.
- Standard181 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the functional accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement in a form that is suitable for use in public procurement within Europe. The present document might be useful for other purposes such as procurement in the private sector.
The present document is intended to be used as the basis for an accessible ICT procurement toolkit. The present document will primarily be useful for public procurers to identify the requirements for their purchases, and also for manufacturers to employ it within their design, build and quality control procedures.
The present document contains the necessary functional requirements and provides a reference document such that if procedures are followed by different actors, the results of testing are similar and the interpretation of those results is clear.
The test descriptions and evaluation methodology included in the present document are elaborated to a level of detail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results.
The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable:
- when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions are not available;
- during those parts of start-up, shutdown, and other state transitions that can be completed without user interaction.
NOTE 1: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so.
NOTE 2: Compliance issues are covered in normative clause C.1.
- Standard134 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the functional accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement in a form that is suitable for use in public procurement within Europe. The present document might be useful for other purposes such as procurement in the private sector. The present document is intended to be used as the basis for an accessible ICT procurement toolkit. The present document will primarily be useful for public procurers to identify the requirements for their purchases, and also for manufacturers to employ it within their design, build and quality control procedures. The present document contains the necessary functional requirements and provides a reference document such that if procedures are followed by different actors, the results of testing are similar and the interpretation of those results is clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of detail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results. The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable: - when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions are not available; - during those parts of start-up, shutdown, and other state transitions that can be completed without user interaction. NOTE 1: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so. NOTE 2: Compliance issues are covered in normative clause C.1.
- Standard134 pagesEnglish languagesale 10% offe-Library read for1 day