id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
183 032
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study into mechanisms for the support of encapsulated ISUP information in IMS
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183032/01.01.01_60/tr_183032v010101p.pdf
|
The present document addresses issues for the support of ISUP information between IMS entities when used in an NGN, i.e. MGCF to MGCF, MGCF to AS, AS to MGCF, AGCF to AS, and possibly AS to AS. The present document provides a home for text for incorporation into other deliverables once the documentation structure has been decided. A number of potential use cases exist for such a mechanism, e.g. PSTN to PSTN bridging using IMS, support of service information to AS from MGCF in simulation services, support of the IMS based PSTN/ISDN emulation subsystem, but it is not in the scope of the present document to provide information relating to use of this mechanism to support such use cases. Such use of this mechanism will be dealt with by other work items.
|
183 025
|
<empty>
|
TR
|
2.2.0
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183025/02.02.00_60/tr_183025v020200p.pdf
|
The purpose of the present document is to define guidelines with regard to the interaction of non-call related H.248 procedures and generic network management use cases and vice versa. More specifically, the interaction between the following is considered: • Control procedures at the H.248 interface. These are the procedures between Media Gateway Controllers (primary and secondary) and their associated Media Gateways (primary, and secondary if available). These procedures primarily utilize the H.248 ServiceChange and H.248 Audit procedures. • Management procedures at the management interface(s) of H.248 systems (i.e. both Media Gateway Controller and Media Gateway) to perform non call related tasks such as configuration management (start-up, capability change, maintenance locking) and fault management (failure handling). It is intended that these guidelines are then subsequently used in corresponding H.248 profiles to produce detailed non-call related procedures. At the current time, the existing set of ETSI H.248 profiles ( [i.1], [i.2], [i.3] and [i.4]) lack any such detailed procedures. Specific management systems, architectures and protocols are outside the scope of the present document; only the general requirements and Use Cases related to the management system shall be discussed.
|
183 052
|
<empty>
|
TR
|
2.2.0
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183052/02.02.00_60/tr_183052v020200p.pdf
|
The present documents purpose is to develop a solution for interworking problems of REFER based simulation services. This solution shall adjust REFER interworking problems of the Release 1 NGN services ECT and CONF, and shall also take into account Release 2 services. NOTE: The results of the of the TR are included in ETSI TS 183 028 [5] "Common Basic Communication procedures".
|
182 031
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182031/03.01.01_60/tr_182031v030101p.pdf
|
The present document covers a use case analysis for the interaction of the TISPAN Resource and Admission Control Sub-System (RACS) with the Customer Premises Network (CPN), as well as an analysis of required functional entities, reference points and information flows. Furthermore, requirements for interworking with in-home QoS control mechanisms are studied. The study concludes with a recommendation on the way, or ways, how RACS and CPN should interact and interface, i.e. on one or several interworking architecture(s) proposal(s), taking into account security and privacy aspects.
|
182 030
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182030/03.01.01_60/tr_182030v030101p.pdf
|
The present document analyses existing NGN-based IPTV functional architectures (IMS based IPTV, NGN integrated IPTV) and its features. The scope of the present document includes: • comparison of architectural aspects between TISPAN NGN based IPTV and 3GPP MBMS/PSS (IMS based or non-IMS based MBMS/PSS) with aim to consider possible mappings of functionalities or feasibility of scenarios for interworking; • consider IPTV work within other SDOs/Fora with relation to TISPAN NGN based IPTV architecture (e.g. relation with ITU-T IMS/non-IMS based IPTV); • consider the impacts for providing selected TISPAN IPTV services to mobile UE over existing mobile access networks; • consider the impacts to support IPTV interconnection models from TISPAN stage 2 specification.
|
182 026
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182026/03.01.01_60/tr_182026v030101p.pdf
|
The present document identifies TISPAN NGN mobility scenarios and the impact of mobility between access- technology independent networks. The main impact of these scenarios is expected to be on the NASS and RACS architectures, but does not preclude other impacts within the TISPAN NGN architecture. The present document may also recommend a way forward to support these scenarios; however, it may also conclude that no further work in TISPAN is required. The present document is expected to be access-technology independent and as such will require coordination of the TISPAN work with external SDOs and Fora such as 3GPP, ITU-T, ECMA, and the WiMAX Forum.
|
183 069
|
<empty>
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183069/02.01.01_60/tr_183069v020101p.pdf
|
The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN. The present document addresses control plane signalling (usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI specifications, as seen from the perspective of an NGCN site. Advice-of-charge aspects are addressed as far as SIP signalling is concerned. The structure of the present document reflects the historical structure of previous versions of it. All references to ETSI TR 124 969 [i.97] are intended to be to the entire contents of the referenced document, which now forms the contents of the present document, and not to any part which might be implied by any headings within the present document.
|
183 068
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183068/03.01.01_60/tr_183068v030101p.pdf
|
The present document defines guidelines for usage and implementation of border gateways (BGW), based on H.248 profile definitions for controlling such IP-to-IP gateways like ETSI TISPAN "H.248 Ia profile" specifications [i.1], [i.2] and [i.3]. Figure 1 illustrates the architecture assumed in the present document. Figure 1: Scope
|
183 057
|
<empty>
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183057/02.01.01_60/tr_183057v020101p.pdf
|
The purpose of the present document is to analyse the requirements for out-of-band DTMF transport in IMS, to assess the possible technical solutions addressing these requirements, to select a solution and to identify and derive the required changes to the relevant IMS specifications. NOTE: The consequence of the TR will most certainly lead to developing CRs against ETSI TISPAN Release 2 IMS specifications and the corresponding 3GPP specifications.
|
183 056
|
<empty>
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183056/02.01.01_60/tr_183056v020101p.pdf
|
The present document purpose is to investigate new methods for providing overlap sending originating from PSTN Networks and devices. The expectation is that such methods would save on processing that the present method for overlap sending deploys. It is also the aim of this investigation to be fully backward compatible, have no impact upon the SIP signalling protocols, and have a minimal impact upon the existing SIP nodes.
|
182 010
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182010/03.01.01_60/tr_182010v030101p.pdf
|
The present document is an ETSI Technical Report which contains only informative elements. The words "shall" and "must" used in the present document either refer to requirements defined in other documents or propose requirements that could be used later on in a document containing normative provisions such as a Technical Specification or an ETSI Standard. The present document analyses peer-to-peer technologies for content delivery for IPTV services: use cases, requirements, architecture studies and other aspects. The scope of the present document includes: • Use cases and requirements: - Types of peer-to-peer mechanisms: delivery of stored/off-line content; delivery of streaming content. - Application of peer-to-peer mechanisms: deliver content from IPTV Service Provider to Consumer; share User-Generated Content (UGC) between users via the IPTV solution; acquire content from third-party Content Providers by IPTV Service Provider; manage content within the IPTV solution; customer profiling based on traffic characteristics. • Architecture studies: - topology analysis; - super-peer-based solution architectures; - impact on TISPAN IPTV network architecture; - impact on Customer Premises Network architecture. • Other aspects: - network aspects, transport level; - security aspects, risk analysis; - legal aspects; - charging aspects; - indexing aspects ("naming"); - concatenation of peer-to-peer ("NNI"). ETSI ETSI TR 182 010 V3.1.1 (2010-02) 8
|
182 005
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182005/01.01.01_60/tr_182005v010101p.pdf
|
The present document provides guidance concerning information, regarding NGN subscribers, to be stored in the Network. It considers the following "types" of user data: • Network attachment data, to be stored in the NASS functional entities ES 282 004 [3], the Profile Database Function (PDBF) and the Connectivity Session Location and Repository Function (CLF). • Service attachment data (for the IMS subsystem ES 282 007 [4]) to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3 [1]. • Data related to CAMEL support of IMS services to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3.8 [1]. • Data related to Generic Authentication Architecture to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3A [1]. • Subscriber data for I-WLAN domain to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3B [1]. Subscriber data related to the PSTN Emulation subsystem (PES, or IMS based PES) is not considered in the present document. Furthermore the present document provides information whether the information is stored permanently or temporarily in the concerned functional entities.
|
181 020
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Exposing TISPAN NGN Services and Capabilities; Requirements, Technical Approaches and Next Steps
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181020/01.01.01_60/tr_181020v010101p.pdf
|
The present document: • Identifies requirements for flexible and agile service development and deployment for a multi-provider and multivendor environment. • Surveys the technical approaches available (e.g. Web services) to expose the functionalities and identify any possible impacts in the evolution of the TISPAN architecture and management. • Surveys the existing industry efforts in this domain (e.g. TISPAN/NGN (protocols), Parlay/X, OSA, OMA, ITU-T, OASIS, WS-I, W3C, among others) and relationship with management frameworks (e.g. DMTF/TMF) • Identifies next steps.
|
180 000
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/180000_180099/180000/01.01.01_60/tr_180000v010101p.pdf
|
The present document provides a common pool of terminology for use within the TISPAN-NGN project. It is intended that all NGN documents refer to the present document within their definitions clause for their basic terminology. If a specific term also used by the 3GPP is not defined in the present document, then the definition in the 3GPP terminology document [1] shall be valid. The present document contains both definitions and explanations of terms. Explanatory text is intended as purely informational material. The definitions are marked as such and follow the structure: 1) Term to be defined. 2) Definition text. 3) Source of definition (optional). 4) Note(s) (explanatory notes). 5) Editor's notes.
|
182 022
|
Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Architectures for QoS handling
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182022/02.00.00_60/tr_182022v020000p.pdf
|
The present document presents an overall analysis of architectural requirements for QoS reporting and resource monitoring (i.e. QoS handling). This includes analysing management aspects from an architectural perspective (stage 2) as well as taking into account the work on performance and QoS for Next Generation Networks undertaken by STQ. The area of QoS reporting covers detecting the end-to-end QoS experienced by bearer flows, while the area of resource monitoring covers monitoring the topologies and resources of the transport segments controlled by RACS. Resource monitoring includes detecting the actual usage of these resources. The present document provides an informative description of the QoS handling tasks that are to be performed. It further describes how different subsystems, common functions or capabilities, and management systems interact in performing these tasks. Being an informative document providing an overall analysis of QoS handling area it is foreseen to be referenced by the RACS release 2 specification [1] and potentially other specifications impacted by QoS handling, but it only performs a preliminary architectural analysis. New functions or interfaces for QoS Handling will not be part of the normative document of the RACS release 2 specification [1]. The present document does not define or re-define functions or interfaces needed for QoS handling. Instead, such enhancements are expected to be made in normative documents such as the RACS specification, beyond current release.
|
182 017
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service; Architecture and functional description [Endorsement of OMA-AD-PoC-V1]
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182017/01.01.01_60/tr_182017v010101p.pdf
|
The present document defines the architecture for Direct Communication. This architecture is an endorsement of the OMA architecture specifications. TISPAN IMS is based on 3GPP IMS. It shall be possible to: • Deploy TISPAN DC using 3GPP2 MMD as long as the related TISPAN requirements on IMS are considered within 3GPP2 MMD. • Have interworking of TISPAN DC with 3GPP PoC and 3GPP2 PoC services. NOTE: The present document uses the term "NGN" only in the context of TISPAN.
|
182 015
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Next Generation Networks; Architecture for Control of Processing Overload
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182015/01.01.01_60/tr_182015v010101p.pdf
|
The present document describes the architectural principles that are required to provide effective control of processing overload in networks compliant to the TISPAN NGN Architecture. As such it constitutes a discussion of the requirements for the protocols required to support the NGN overload control architecture. The scope is limited to the control of processing overload at NGN processing resources caused by service requests coming from session-based or command-response applications by controlling the rate at which those applications send service requests to an overloaded resource. It does not extend to the overload of transmission bandwidth whether used for the user plane or for the control plane.
|
182 013
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Bearer Control; Stage 2 Requirements
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/182000_182099/182013/01.01.01_60/tr_182013v010101p.pdf
|
The present document identifies a range of issues which occur if Bearer Control Function communicates with each other. The present document is based on concepts developed in ITU-T Q.Sup51: "Signalling Requirements For IP-QoS". The present document covers the part of NCI (Network Control Interface) interface which provides multiple bearer routes between source and destination.
|
183 072
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183072/03.01.01_60/tr_183072v030101p.pdf
|
The present document specifically describes the framework of IP emulation services for PSTN modem call types. The present document provides, inter alia, a description of: • the problem statement; • summary of IP bearer services; • overview of media-type configurations; and • a collection of example network use cases; for PSTN modem calls.
|
183 070
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183070/03.01.01_60/tr_183070v030101p.pdf
|
The present document provides a report on the study of the applicability of the ANCP protocol to the Rr interface between Generic Resource Admission Control Function (x-RACF) instances. Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of ANCP. Where this is not possible, extensions to ANCP are defined within the present document.
|
183 069
|
Network Technologies (NTECH); Business Trunking; NGCN-NGN Interfaces Implementation Guide
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183069/03.00.00_60/tr_183069v030000p.pdf
|
The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN. The present document addresses control plane signalling (usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI specifications, as seen from the perspective of an NGCN site. Advice-of-charge aspects are addressed as far as SIP signalling is concerned. The structure of the present document reflects the historical structure of previous versions of it. All references to ETSI TR 124 969 [i.97] are intended to be to the entire contents of the referenced document, which now forms the contents of the present document, and not to any part which might be implied by any headings within the present document.
|
181 015
|
Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Requirements for Customized Originating and Terminating Multimedia Information Presentation (COMIP/CTMIP) and Customized Originating and Terminating Multimedia Information Filtering (COMIF/CTMIF) Requirements Analysis
|
TR
|
2.0.1
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181015/02.00.01_60/tr_181015v020001p.pdf
|
The study identifies requirements for: • originating and terminating party multimedia information presentation and filtering during session establishment (e.g. name, alias, picture, card, ring, video, etc.); • interoperability. The results of this study will be used as a new service capability defined in a new document or as an update of the document "Service and capability requirements" concerning multimedia information presentation and filtering services.
|
181 011
|
<empty>
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181011/02.00.00_60/tr_181011v020000p.pdf
|
The present document identifies and analyses fixed-mobile convergence scenarios in order to derive requirements and capabilities to support FMC capabilities (e.g. network attachment, roaming, etc.) and the impact to services, e.g. multimedia communication services (e.g. telephony, sms, mms, etc.). It determines the responsible standards body for each requirement/capability and the release in which it is (expected to be) covered. The goals are: • to identify specific access types, and which organization is defining each of them; • to determine requirements and capabilities (taking account of terminal requirements) and to analyse these to determine which are: - within the scope of ETSI TISPAN; - being progressed in other standards bodies; - a priority for TISPAN NGN Release 2; - included in the next release of 3GPP.
|
181 007
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Overview of Messaging Services
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181007/02.01.01_60/tr_181007v020101p.pdf
|
The present document describes some of the different types of messaging (based on TR 122 940 [1]) and provides informative guidance on the areas of application of the Short Message Services and Multi-Media Messaging Services specified by ETSI. The present document does not provide guidance on the services in mobile environments (e.g. GSM). The present document does not specify the services and does not provide service requirements.
|
181 004
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Generic capabilities and their use to develop services
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181004/01.01.01_60/tr_181004v010101p.pdf
|
The present document presents an analysis of existing and new NGN generic capabilities required for the support of services identified in TR 181 003 [1]. The NGN generic capabilities for NGN release 1 (TR 180 001 [2]) and beyond are identified. The purpose of the analysis is to enable ETSI to identify further areas of standardization for NGN generic capabilities. Priority is given to capabilities that enable service interoperability in heterogeneous environments.
|
181 003
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services Capabilities, Requirements and strategic direction for NGN services
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/181000_181099/181003/01.01.01_60/tr_181003v010101p.pdf
|
The present document provides the results of an analysis of the current work and strategic direction of relevant SDOs (ITU-T, FGNGN, IETF, etc.) and other fora (EURESCOM, CJK, ATIS, etc.) in relation to services and network requirements to support ETSI TISPAN. The purpose of this analysis is to ensure synthesis of the current studies on NGN services. The present document enables ETSI to identify strategic directions for standardization of NGN services and service requirements beyond Release 1. A catalogue of existing and proposed service documents is given in annex B. This catalogue does not provide any prioritization.
|
180 003
|
<empty>
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/180000_180099/180003/03.01.01_60/tr_180003v030101p.pdf
|
The present document provides guidance for handling IMS-based NGN national IP interconnection details. Interconnection of NGNs represents a broad area of study including such areas as signalling interconnection, media interconnection, routing, address resolution, security, charging and network management. However, as with most aspects of the NGN, there are many Standards Development Organizations (SDOs) and industry bodies that are working on this topic. As organizations such as ITU-T, 3GPP, GSMA and the i3 Forum do focus on overarching IP interconnection specifications and agreements, a gap on guidelines for the handling of national IP interconnection was identified. The present document is intended to fill this gap for IMS based NGN national IP interconnection in co-relation with the IMS approach of 3GPP.
|
180 001
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1; Release definition
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/180000_180099/180001/01.01.01_60/tr_180001v010101p.pdf
|
The present document provides a description of the content of NGN Release 1 and defines the release through a catalogue of the Release 1 documentation set. The inter-relationships between release 1 documents and the features supported is also provided.. The present document is structured as follows: - clause 4 provides an overview of Next Generation Networks (NGN); - clause 5 describes the NGN Release 1, the Requirements to support Release 1 and outlines the major capabilities that Release 1 will fulfil; - clause 6 defines the content and capabilities of NGN Release 1; - clause 7 introduces the Release 1 plan documentation set. The present document does not provide solutions for the technical issues that are identified therein.
|
133 901
|
Universal Mobile Telecommunications System (UMTS); 3G Security - Criteria for cyptographic Algorithm design process (3G TR 33.901 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/133900_133999/133901/03.00.00_60/tr_133901v030000p.pdf
|
........................................................................................................................................................5
|
127 903
|
Universal Mobile Telecommunications System (UMTS); Discussion of Synchronization Standards (3G TR 27.903 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/127900_127999/127903/03.00.00_60/tr_127903v030000p.pdf
|
........................................................................................................................................................5
|
126 915
|
Universal Mobile Telecommunications System (UMTS); Echo Control For Speech and Multi-Media Services (3G TR 26.915 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/126900_126999/126915/03.00.00_60/tr_126915v030000p.pdf
|
........................................................................................................................................................5
|
126 912
|
Universal Mobile Telecommunications System (UMTS); QoS for Speech and Multimedia Codec; Quantitative performance evaluation of H.324 Annex C over 3G (3G TR 26.912 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/126900_126999/126912/03.00.00_60/tr_126912v030000p.pdf
|
........................................................................................................................................................6
|
125 990
|
Universal Mobile Telecommunications System (UMTS); Vocabulary (3G TR 25.990 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/125900_125999/125990/03.00.00_60/tr_125990v030000p.pdf
|
........................................................................................................................................................5
|
125 941
|
Universal Mobile Telecommunications System (UMTS); TSG RAN WG4 document structure (3G TS 25.941 version 3.1.0 Release 1999)
|
TR
|
3.1.0
|
http://www.etsi.org/deliver/etsi_tr/125900_125999/125941/03.01.00_60/tr_125941v030100p.pdf
|
........................................................................................................................................................4
|
123 972
|
Universal Mobile Telecommunications System (UMTS); Circuit Switched Multimedia Telephony (3G TR 23.972 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/123900_123999/123972/03.00.00_60/tr_123972v030000p.pdf
|
........................................................................................................................................................4
|
123 930
|
Universal Mobile Telecommunications System (UMTS); Iu Principles (3G TR 23.930 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/123900_123999/123930/03.00.00_60/tr_123930v030000p.pdf
|
........................................................................................................................................................5
|
170 012
|
Project MESA; Technical Specification Group - System; System Overview
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/170000_170099/170012/03.01.01_60/tr_170012v030101p.pdf
|
The present document defines a system architecture that is capable of meeting the requirements of next-generation public service and public safety agencies. The present document articulates requirements that are detailed in the Project MESA Statement of Requirements document and captures other elements that encompass the overall user communication landscape.
|
170 003
|
Project MESA; Service Specification Group - Services and Applications; Basic requirements
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/170000_170099/170003/03.01.01_60/tr_170003v030101p.pdf
|
The present document defines the initial basic requirements to be used as a basis for the elaboration of the MESA Statement of Requirements, TS 170 001 [1].
|
170 002
|
Project MESA; Service Specification Group - Services and Applications; Definitions, symbols and abbreviations
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/170000_170099/170002/03.01.01_60/tr_170002v030101p.pdf
|
The present document defines the basic applied terms, symbols and abbreviations as required by Project MESA to produce MESA Specifications and MESA Reports. It is also intended as a guidance document for other external bodies such that misunderstandings can be minimized in situations of liaison and cooperation. The present document is applicable to deliverables produced by Project MESA.
|
134 925
|
Universal Mobile Telecommunications System (UMTS); Specific Absorbtion Rate (SAR) requirements and regulations in different regions (3G TR 34.925 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/134900_134999/134925/03.00.00_60/tr_134925v030000p.pdf
|
........................................................................................................................................................5
|
134 907
|
Universal Mobile Telecommunications System (UMTS); Report on electrical safety requirements and regulations (3G TR 34.907 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/134900_134999/134907/03.00.00_60/tr_134907v030000p.pdf
|
........................................................................................................................................................5
|
133 902
|
Universal Mobile Telecommunications System (UMTS); Formal Analysis of the 3G Authentication Protocol (3G TR 33.902 version 3.1.0 Release 1999)
|
TR
|
3.1.0
|
http://www.etsi.org/deliver/etsi_tr/133900_133999/133902/03.01.00_60/tr_133902v030100p.pdf
|
........................................................................................................................................................5
|
133 901
|
Universal Mobile Telecommunications System (UMTS); 3G Security - Criteria for cyptographic Algorithm design process (3G TR 33.901 version 4.0.0 Release 4)
|
TR
|
4.0.0
|
http://www.etsi.org/deliver/etsi_tr/133900_133999/133901/04.00.00_60/tr_133901v040000p.pdf
|
........................................................................................................................................................5
|
122 975
|
Universal Mobile Telecommunications System (UMTS); Service aspects; Advanced Addressing ; (3G TR 22.975 version 3.1.0 Release 1999)
|
TR
|
3.1.0
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122975/03.01.00_60/tr_122975v030100p.pdf
| |
122 971
|
Universal Mobile Telecommunications System (UMTS); Automatic Establishment of Roaming Relationships (3G TR 22.971 version 3.1.1 Release 1999)
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122971/03.01.01_60/tr_122971v030101p.pdf
| |
122 970
|
Universal Mobile Telecommunications System (UMTS); Service aspects; Virtual Home Environment (VHE) (3G TR 22.970 version 3.0.1 Release 1999)
|
TR
|
3.0.1
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122970/03.00.01_60/tr_122970v030001p.pdf
|
........................................................................................................................................................5
|
122 960
|
Universal Mobile Telecommunications System (UMTS); Mobile multimedia services including mobile Intranet and Internet services (3G TR 22.960 version 3.0.1 Release 1999)
|
TR
|
3.0.1
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122960/03.00.01_60/tr_122960v030001p.pdf
| |
122 945
|
Universal Mobile Telecommunications System (UMTS); Study on provisioning of fax in GSM and UMTS (3G TR 22.945 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122945/03.00.00_60/tr_122945v030000p.pdf
| |
122 925
|
Universal Mobile Telecommunications System (UMTS); Service aspects; Quality of Service and Network Performance (3G TR 22.925 version 3.1.1 Release 1999)
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122925/03.01.01_60/tr_122925v030101p.pdf
| |
122 924
|
Universal Mobile Telecommunications System (UMTS); Service aspects; Charging and Accounting Mechanisms (3G TR 22.924 version 3.1.1 Release 1999)
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122924/03.01.01_60/tr_122924v030101p.pdf
| |
122 907
|
Universal Mobile Telecommunications System (UMTS); Terminal and smart card concepts (3G TR 22.907 version 3.1.3 Release 1999)
|
TR
|
3.1.3
|
http://www.etsi.org/deliver/etsi_tr/122900_122999/122907/03.01.03_60/tr_122907v030103p.pdf
| |
121 978
|
Universal Mobile Telecommunications System (UMTS); Feasibility Technical Report - CAMEL Control of VoIP Services (3G TR 21.978 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/121900_121999/121978/03.00.00_60/tr_121978v030000p.pdf
|
........................................................................................................................................................6
|
121 910
|
Universal Mobile Telecommunications System (UMTS); Multi-mode User Equipment (UE) issues; Categories principles and procedures (3G TR 21.910 version 3.0.0 Release 1999)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/121900_121999/121910/03.00.00_60/tr_121910v030000p.pdf
|
........................................................................................................................................................5
|
119 600
|
Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for trust service status lists providers
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/119600_119699/119600/01.02.01_60/tr_119600v010201p.pdf
|
The present document provides guidance on the selection of standards and their options to organizations wishing to establish a trust service status list, for a particular business implementation context and associated business requirements. The present document describes the business scoping parameters relevant to this area and how the relevant standards and options for this area can be identified given these business scoping parameters. The target audience of the present document includes those potentially requiring support from trust services and in particular trust service status lists. The present document provides an explanation of how related standards can be used to meet the business needs.
|
119 530
|
Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM); Feasibility study: Interoperability profile between ETSI EN 319 532-based REM systems and PReM-based systems
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119500_119599/119530/01.01.01_60/tr_119530v010101p.pdf
|
The present document represents a feasibility study for an interoperability profile between systems based on ETSI EN 319 522 [i.21] / ETSI EN 319 532 [i.22] ERDS/REMS specification and UPU S52-2 PReM specification [i.25].
|
119 520-2
|
Electronic Signatures and Trust Infrastructures (ESI); Framework of ERDS/REM standards; Part 2: Impact of emerging technologies on ERDS/REM Models
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119500_119599/11952002/01.01.01_60/tr_11952002v010101p.pdf
|
The present document aims to study the impact of emerging technologies and models for ERDS/REM provision and assess their impact on the ERDS framework of standards. The approach followed is to: • Monitor emerging ERDS/REM technologies and models that have been identified. The result of this activity is reported in clause 4. • Assess the result of monitoring and identify concrete proposals on ERDS/REM services provision and models. The result of this activity is reported in clause 5 and the impact on the ERDS framework is reflected in ETSI TR 119 520-1 [i.13].
|
119 520-1
|
Electronic Signatures and Trust Infrastructures (ESI); Framework of ERDS/REM standards; Part 1: New (Q)ERDS/(Q)ERDSP standardization rationalized framework as a result of the new components brought by eIDAS2.0
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119500_119599/11952001/01.01.01_60/tr_11952001v010101p.pdf
|
The present document defines the new (Q)ERDS/(Q)ERDSP standardization rationalized framework, identifying the most relevant changes to be performed in the framework currently existing, among which: the incorporation of an ERDS HTTP-based baseline, offering similar features than REM baseline but on HTTP-based protocols; those due to the changes brought by eIDAS 2.0 [i.2] (including new components such as the EU eWallet, and the Electronic Attestations of Attributes); and those ones due to emerging technologies that might have an impact in this field. It also contains recommendations for updating ETSI TR 119 000 [i.4] and ETSI TR 119 001 [i.5]. Finally, the present document identifies the issues that may impact in the policy and security requirements standards.
|
119 500
|
Business Driven Guidance for Trust Application Service Providers
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119500_119599/119500/01.01.01_60/tr_119500v010101p.pdf
|
The present document provides guidance on the use of standards for Trust Application Service Providers (area 5) as identified in the framework for standardization of signatures: overview [i.1]. The present document then describes the Business Scoping Parameters relevant to this area (see clause 6) and how the relevant standards and options for this area can be identified given the Business Scoping Parameters (clause 7). The target audience of the present document includes: 1) Business managers who potentially require support from digital signatures in their business will find here an understandable explanation of how services applying digital signatures standards can be used to meet their business needs. 2) Application architects who will find here material that will guide them throughout the difficult process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to services applying digital signatures, and will gain a better understanding on how to select the appropriate standards to be implemented and/or used. 3) Developers of the systems who will find an understanding of a good part of the ultimate reasons that led the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and to be known in detail for a proper development.
|
119 479-2
|
Electronic Signatures and Trust Infrastructures (ESI); Technological Solutions for the EU Digital Identity Framework; Part 2: EAA Extended Validation Services Framework and Application
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/11947902/01.01.01_60/tr_11947902v010101p.pdf
|
The present document proposes an extended validation mechanism leveraging on the existing OID4VP protocol. Its primary aim is to support the secure and interoperable validation of electronic attestations by identifying standardization needs in the context of the attestation rulebook and attribute catalogues. Key focus areas include: • introduction of attestation refreshing and attestation encryption mechanisms; • description of embedded disclosure policies and support for pricing policies; • further considerations on the extension of attestation metadata structures to include policy-related parameters.
|
119 476
|
Electronic Signatures and Trust Infrastructures (ESI); Analysis of selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/119476/01.02.01_60/tr_119476v010201p.pdf
|
The present document analyses cryptographic schemes for selective disclosure and their potential application for privacy of electronic attestation attributes in line with the expected requirement of the proposed regulation amending Regulation (EU) No 910/2014 (commonly called eIDAS2) [i.86]. NOTE 1: The term selective disclosure is a collective term that may also include various concepts of unlinkability, and predicates such as range proofs, depending on the context of the specific cryptographic scheme. The scope of the present document is primarily to describe selective disclosure and unlinkability properties of each analysed cryptographic scheme. NOTE 2: Range proofs, and more general predicate proofs as well as general-purpose ZKPs are out of scope in the ARF [i.59]. If an analysed cryptographic scheme relies on any of these features, they will be described in the context of that particular cryptographic scheme. The present document aims at providing a comprehensive overview of existing cryptographic schemes for selective disclosure and the formats and protocols associated with these cryptographic schemes. The aim of the present document is first to provide input to ETSI standardization relating to how selective disclosure may be applied to the eIDAS2 (Qualified) Electronic Attribute Attestations ((Q)EAA) and Person Identification Data (PID). More specifically, the present report may serve as input to (Q)EAA issuance policies as being specified in ETSI TS 119 471 [i.80] and (Q)EAA profiles as being specified in ETSI TS 119 472-1 [i.81]. Second, the present document will also analyse the policy requirements for (Q)TSPs and PID providers issuing (Q)EAAs or PIDs with selective disclosure capabilities to EUDI Wallets. Third, the present document analyses how the user of an EUDI Wallet can present selected attributes of a (Q)EAA or PID to relying parties (or (Q)TSPs acting as relying parties). Consequently, the present document can highlight needs that may require future standardization efforts. The present document analyses the concepts of selective disclosure, unlinkability, and predicates (including range proofs) in the following main clauses: • Selective disclosure signature schemes (clause 4): This clause describes the academic research of the cryptographic algorithms and schemes that shape the foundation for selective disclosure signature schemes. • Selective disclosure (Q)EAA formats (clause 5): This clause describes the (Q)EAA formats that have been developed and standardized based on the aforementioned selective disclosure signature schemes. • Selective disclosure protocols and systems (clause 6): This clause describes the complete protocols and /or systems that have been developed and standardized based on the aforementioned selective disclosure signature schemes and (Q)EAA formats. Since the ARF [i.59] specifies the PID to be issued to an EUDI Wallet as ISO mDL [i.140] (with ISO mDL MSO for selective disclosure) or W3C Verifiable Credentials (with SD-JWT for selective disclosure), these formats and protocols are analysed in more detail in clause 7.
|
119 460
|
Electronic Signatures and Infrastructures (ESI); Survey of technologies and regulatory requirements for identity proofing for trust service subjects
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/119460/01.01.01_60/tr_119460v010101p.pdf
|
The present document provides the results of a survey on the technologies, legislations, specifications, guidelines and standards related to or used for identity proofing. Information has been collected as comprehensively as possible, and is analysed in the present document. The aim is to identify trends and select relevant elements for ETSI DTS/ESI-0019461 [i.50] to address both security policy and security requirements for enrolment of Trust Services subjects. The methodology to achieve this goal is presented in clause 4 and is followed by the analysis.
|
119 411-5
|
Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 5: Guidelines for the coexistence of web browser and EU trust controls
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/11941105/01.01.01_60/tr_11941105v010101p.pdf
|
The present document defines two approaches for issuing qualified certificates for website authentication, deploying them to websites, and their consumption by web browsers. Objectives of Approach #1 (i.e. "1-QWAC Approach") 1-QWACs: a) Support coexistence of trust controls based upon meeting requirements from both the Web Browser Vendor within the meaning of Recital 65 of the Regulation (EU) 2024/1183 [i.3] and EU Trusted Lists with ETSI standards aimed at supporting EU trust controls. b) Include requirements for TLS certificates based on CA/Browser Forum Requirements [i.4] and [i.5] as applied in ETSI standards [4]. c) Authenticate the website directly by using the QWAC to establish a TLS connection between the web browser and the server. NOTE: TLS uses encryption to secure data transmitted over a network providing confidentiality, integrity, and authentication. Objectives of Approach #2 (i.e. "2-QWAC with Certificate Binding Validation Approach") 2-QWACs with Certificate Binding Validation: - Support trust controls based upon EU Trusted Lists with ETSI standards aimed at supporting EU trust controls for a QWAC, which is used to bind the identity in the QWAC to the TLS certificate(s) to be used by the web browser to establish a TLS connection between the web browser and the server. - Support trust controls based upon Web Browser Vendor Root Stores for the TLS certificate which is used to establish a TLS connection between the web browser and the server. All approaches: • aim to meet the requirements of Article 45, Article 45a, and Recital 65 of Regulation (EU) 2024/1183 [i.3]; • include requirements of qualified certificates for website authentication as specified in Regulation (EU) 2024/1183 [i.3]; and • enable the display of identity data contained in qualified certificates for website authentication and validated by the EU trust schemes in a user-friendly manner. Clause 4 specifies Trust Service Provider requirements for issuing QWACs. Clause 5 provides website operator guidance for using QWACs. Clause 6 specifies web browser requirements for consuming QWACs.
|
119 411-4
|
Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 4: Checklist supporting audit of TSP against ETSI EN 319 411-1 or ETSI EN 319 411-2
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/11941104/01.02.01_60/tr_11941104v010201p.pdf
|
The present document is a checklist of the policy requirements specific to TSP issuing certificates (as expressed in ETSI EN 319 411-1 [i.2] and ETSI EN 319 411-2 [i.3]) including the generic requirements which are independent of the type of service (as expressed in ETSI EN 319 401 [i.1]). The checklist identifies each requirement associated with each certificate policy, as specified in ETSI EN 319 411-1 [i.2] and ETSI EN 319 411-2 [i.3], and also relates where relevant the requirement to a particular TSP component service. Additional fields are provided to allow TSPs to indicate claimed compliance to a particular requirement and for assessors to indicate the results of an assessment for each requirement. This checklist can be used by the TSP itself to prepare for an assessment of its practices against the referenced documents (i.e. serve as a basis for a self-declaration) and/or by the assessor when conducting the assessment. The present document does not specify how the requirements identified can be assessed by an independent party, including requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE: See ETSI EN 319 403-1 [i.7] for guidance on assessment of TSP's processes and services.
|
119 404
|
Electronic Signatures and Infrastructures (ESI); NIS2 and its impact on eIDAS standards
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/119404/01.01.01_60/tr_119404v010101p.pdf
|
The present document: • outlines the main requirements of NIS2; • analyses the requirements of NIS2 Directive against the existing cybersecurity provisions of ETSI EN 319 401 [i.7] in order to identify areas where additional provisions are needed; • takes into account the use of ISO 27002 general information security controls for cyber security used in support of ETSI EN 319 401 [i.7] including revisions to align with the major reorganisation to ISO 27002 from the 27002:2013 [i.5] to the 27002:2022 [i.6]; • establishes a methodology for aligning other ETSI standards with the NIS2 Directive.
|
119 400
|
Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for trust service providers supporting digital signatures and related services
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/119400/01.01.01_60/tr_119400v010101p.pdf
|
The present document provides guidance on the selection of standards and options for the trust service provider supporting digital signatures and related services (area 4) as identified in ETSI TR 119 000 [i.2]. The present document describes the business scoping parameters relevant to this area (see clause 5) and how the relevant standards and options for this area can be identified given the business scoping parameters (see clause 6). The target audience of the present document includes: 1) Business managers who potentially require support from digital signatures and in particular the provision of related supporting trust services in their business will find here an explanation of how digital signatures standards can be used to meet their business needs. 2) Application architects who will find here material that will guide them throughout the process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to digital signatures and in particular the provision of related supporting trust services. They will gain a better understanding on how to select the appropriate standards to be implemented and/or used. 3) Developers of the systems who will find in the present document an understanding of the main reasons that lead the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and that they need to know in detail for a proper development.
|
119 300
|
Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for cryptographic suites
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/119300_119399/119300/01.02.01_60/tr_119300v010201p.pdf
|
The present document provides business driven guidance on the use of standards for cryptographic suites, and in particular for digital signature creation algorithms. The present document explains the concept of security parameters that helps to choose a proper cryptographic suite for digital signature creation. It also gives an overview how to analyze the business needs and how to select a system that satisfies these needs. The purported audience of the present document is mainly the application designers and implementers. The present document provides recommendations to trust service providers and manufacturers of security devices.
|
119 164-1
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Conformance and Interoperability; Part 1: Overview
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/11916401/01.01.01_60/tr_11916401v010101p.pdf
|
The present document provides an overview of the set of test suites for testing interoperability and conformance of ASiC containers. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of ASiC containers; and b) lists the features of every test suite for testing interoperability and conformance of ASiC containers. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable.
|
119 144-1
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/11914401/01.01.01_60/tr_11914401v010101p.pdf
|
The present document provides an overview of the set of test suites for testing interoperability and conformance of PAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of PAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of PAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable.
|
119 134-1
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/11913401/01.01.01_60/tr_11913401v010101p.pdf
|
The present document provides an overview of the set of test suites for testing interoperability and conformance of XAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of XAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of XAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable.
|
119 124-1
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/11912401/01.01.01_60/tr_11912401v010101p.pdf
|
The present document provides an overview of the set of test suites for testing interoperability and conformance of CAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of CAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of CAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable.
|
119 112
|
Electronic Signatures and Infrastructures (ESI); Most significant differences between AdES/ASiC ENs and previous TSs
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/119112/01.01.01_60/tr_119112v010101p.pdf
|
The present document summarizes: • The most relevant differences between the CAdES digital signatures specified in ETSI EN 319 122-1 [i.2] and ETSI EN 319 122-2 [i.26], and the CAdES signatures specified in ETSI TS 101 733 (V2.2.1) [i.3] and ETSI TS 103 173 (V2.2.1) [i.4]. • The most relevant differences between the PAdES digital signatures specified in ETSI EN 319 142-1 [i.8] and ETSI EN 319 142-2 [i.9], and the PAdES signatures specified in the latest versions of the different parts ETSI TS 102 778 ([i.10] to [i.15]) and ETSI TS 103 172 (V2.2.2) [i.16]. • The most relevant differences between the XAdES digital signatures specified in ETSI EN 319 132-1 [i.1] and ETSI EN 319 132-2 [i.5], and the XAdES signatures specified in ETSI TS 101 903 (V1.4.2) [i.6] and ETSI TS 103 171 (V2.1.1) [i.7]. • The most relevant differences between the ASiC containers specified in ETSI EN 319 162-1 [i.17] and ETSI EN 319 162-2 [i.18] and the ASiC containers specified in ETSI TS 102 918 (V1.3.1) [i.19] and ETSI TS 103 174 (V2.2.1) [i.20].
|
119 100
|
Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for signature creation and validation
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119100_119199/119100/01.01.01_60/tr_119100v010101p.pdf
|
The present document, which addresses area 1 of the Framework [i.1], provides a business driven guided process for implementing generation and validation of digital signatures in business' electronic processes. Starting from a business analysis and risk analysis of the business' electronic processes, stakeholders are guided for making the best choice among the wide offer of standards in order to ensure the best implementation of digital signatures within the addressed application/business electronic processes. The target audience includes enterprise/business process architects, application architects, application developers, and signature policy issuers.
|
119 001
|
Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/119000_119099/119001/01.02.01_60/tr_119001v010201p.pdf
|
The present document provides definitions and abbreviations for use in the ETSI ESI framework for standardization of signatures.
|
119 000
|
Electronic Signatures and Infrastructures (ESI); The framework for standardization of digital signatures and trust services; Overview
|
TR
|
1.3.1
|
http://www.etsi.org/deliver/etsi_tr/119000_119099/119000/01.03.01_60/tr_119000v010301p.pdf
|
The present document describes the general structure for ETSI/CEN digital signature standardization outlining existing and potential standards for such signatures, hereafter referred to as the framework for standardization of signatures. This framework identifies six areas of standardization with a list of existing and potential future standards in each area. NOTE: Each title providing the name of a listed standard in the framework for standardization of signatures includes a hyperlink that leads to download facilities for such a standard, including all its versions, both as TS/TR and/or as EN when applicable.
|
118 568
|
AI enablement to oneM2M (oneM2M TR-0068 version 5.0.1)
|
TR
|
5.0.1
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118568/05.00.01_60/tr_118568v050001p.pdf
|
The present document is analysing existing AI/ML technologies that can be resourced into oneM2M architecture. The present document is also investigating potential AI/ML service use cases that use data collected in the oneM2M system. The study on existing AI/ML technologies and use cases are further analysed in the present document to understand what features are supported and unsupported by the oneM2M system. Based on the result of the present document, it will identify potential requirements and key features to enable AI/ML in the oneM2M system.
|
118 567
|
oneM2M: Study on Management Object migration to SDT (oneM2M TR-0067 version 4.0.0)
|
TR
|
4.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118567/04.00.00_60/tr_118567v040000p.pdf
|
The present document studies the completion of SDT (Smart Device Template) using <flexContainer> resource specializations and the possible migration of the existing device management model using Management Object (<mgmtObj>). The present document is initiated in the context of the Management Object Migration having the following objectives (extract): In Release 4, SDT (Smart Device Template) has been extended to include device management functions in addition to the existing services. This justified extension creates a new way to perform device management compared to the existing Device Management (DM) Common Services Function (CSF) model using <mgmtObj>. In order not to live with 2 solutions for the same purpose, the present document proposes to work on a transition phase allowing implementation using DM <mgmtObj> to migrate towards SDT model. The scope of the present document is to study the Device Management model based on Management Object (<mgmtObj>) model migration towards SDT model. This action plan includes to: 1) Provide a temporary TR with a mapping between <mgmtObj> and the SDT DM <flexContainer>. 2) List in the present document all the specifications and sections that will have to be updated when <mgmtObj> will be replaced by SDT. 3) List in the present document the issues to be resolved by removing the <mgmtObj> after migration and the proposed solutions. 4) Depending on the present document outcomes, decide whether <mgmtObj> should be removed or not in oneM2M Release 4. New tasks may be added during the process if necessary. The present document intends to provide the study as part of the action plan above.
|
118 565
|
oneM2M-SensorThings API interworking (oneM2M TR-0065 version 5.0.0)
|
TR
|
5.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118565/05.00.00_60/tr_118565v050000p.pdf
|
The present document defines an interworking of both standards oneM2M and OGC SensorThings API. The present document is structured as followed: • Introduction and background to OGC-SensorThings API. • Describing interworking scenarios that are relevant but not exclusive for Smart City (there are also examples from other areas and verticals as well). • Technical comparison of oneM2M and OGC/STA. • Describing a technical solution for interworking of both standards; there might be interworking on different level: - opaque data routing; - data model mapping between oneM2M-SDT and OGC. • Developing test cases for interworking between oneM2M and OGC SensorThings API.
|
118 551
|
oneM2M API guide (oneM2M TR-0051 version 2.0.0)
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118551/02.00.00_60/tr_118551v020000p.pdf
|
The present document is a collection of the CRUDN messages used for managing some of the main resources defined in ETSI TS 118 101 [i.2]. It also provides the description and associated flow in basic examples. It aims to use this list as a common sets of APIs to help developers to write applications that can run across different platforms and specific implementations. When an application developer would need to build software code for managing a specific resource, he could have an immediate access to the list of CRUDN message with description and its associated examples of requests to send and its expected responses. The REST API examples are sorted by resource type and CRUDN operations, which allows a quick and easy access to the information.
|
118 546
|
oneM2M: Study on Public Warning Service Enabler (oneM2M TR-0046 v4.0.0 Release 4)
|
TR
|
4.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118546/04.00.00_60/tr_118546v040000p.pdf
|
The present document results of studies on public warning service enabler of oneM2M system. To enable public warning service over oneM2M system, the study includes following technical scope: • Case studies of existing public warning systems. • Use cases and potential requirements. • Architecture analysis for the new use cases and requirements with current oneM2M system. • Abstract data models for public warning services.
|
118 525
|
oneM2M; Application Developer Guide (oneM2M version 1.0.0 Release 1)
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118525/01.00.00_60/tr_118525v010000p.pdf
|
The present document provides a guide for application developers to develop applications using functionalities provided by any oneM2M compliant service platform with thescope of as follows: • Objective of the use case, • The architecture of the use case mapped into an oneM2M service platform, • The execution procedures for implementation of the use case, and • Implementation details of the use case.
|
118 522
|
oneM2M; Continuation & integration of HGI Smart Home activities (oneM2M TR-0022 version 2.0.0)
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118522/02.00.00_60/tr_118522v020000p.pdf
|
The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements. It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M.
|
118 518
|
oneM2M; Industrial Domain Enablement (oneM2M TR-0018 version 2.5.1 Release 2A)
|
TR
|
2.5.1
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118518/02.05.01_60/tr_118518v020501p.pdf
|
The present document collects the use cases of the industrial domain and the requirements needed to support the use cases collectively. In addition it identifies the necessary technical work needed to be addressed while enhancing future oneM2M specifications.
|
118 517
|
oneM2M; Home Domain Abstract Information Model (oneM2M TR-0017 version 2.0.0)
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118517/02.00.00_60/tr_118517v020000p.pdf
|
The present document allows application developers to describe the status of devices as resources on oneM2M-based platform in various ways. Thus different application developers can create different resource trees even when they build the same kinds of applications. Moreover when handling the same kinds of devices from different vendors on M2M platforms, application developers may create disunited resource trees without common information model. In order to solve such issues, the present document intends to provide the common and unified APIs on one M2M platform for the home domain by defining an abstract information model for the home domain devices such as TV, refrigerator, air conditioner, smart meter, and lighting equipment. The definition of the abstract information model will be based on data models that currently exist in the home domain. The home domain abstract information model does not intend to define the interworking function between the oneM2M system and protocols of the data models from which the abstract data model is defined. Also, the present document intends to define how the developed abstract information model for a device could be represented in the CSEs of the oneM2M system.
|
118 516
|
oneM2M; Study of Authorization Architecture for Supporting Heterogeneous Access Control Policies (oneM2M TR-0016 version 2.0.0)
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118516/02.00.00_60/tr_118516v020000p.pdf
|
The present document provides technical solutions for oneM2M authorization architecture, authorization procedures and access control policies. The present document also gives evaluations of these proposed technical solutions. ETSI TS 118 103 [i.2] only defines a high level authorization architecture that describes its major components and general authorization procedure. The objective of the present document is to provide candidate security solutions related to authorization architecture, authorization procedures and access control policies. The present document provides security solutions in the following three aspects: • Detailed design of authorization architecture: This part investigates the interfaces among authorization components (e.g. procedures and parameters), how these components could be distributed in different oneM2M entities (i.e. different CSEs), and how to implement Role Based Access Control (RBAC) and token based access control. • Supporting user specified access control policies: This part investigates how the oneM2M authorization system could be an extensible system that can support user-defined access control mechanisms and/or access control policy languages. • Investigating existing access control policy languages: This part investigates if some standardized access control policy languages could become oneM2M recommended access control policy description languages.
|
118 512
|
oneM2M; End-to-End Security and Group Authentication (oneM2M TR-0012 version 2.0.0)
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118512/02.00.00_60/tr_118512v020000p.pdf
|
The present document provides options and analyses for the security features and mechanisms providing end-to-end security and group authentication for oneM2M. The scope of this technical report includes use cases, threat analyses, high level architecture, generic requirements, available options, evaluation of options, and detailed procedures for executing end-to-end security and group authentication.
|
118 508
|
Analysis of Security Solutions for the oneM2M System
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118508/01.00.00_60/tr_118508v010000p.pdf
|
The scope of the present document is to create a common understanding on security within oneM2M systems. To achieve that, security services are explained, threats analysed and security requirements within oneM2M identified and derived from use cases. In addition the present document discusses how security mechanisms relate to the oneM2M architecture. Suitable security procedures and mechanisms are defined within [i.12].
|
118 506
|
Study of Management Capability Enablement Technologies for Consideration by oneM2M
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118506/01.00.00_60/tr_118506v010000p.pdf
|
The present document describes and collects the state-of-art of the existing technologies on management capability, evaluates if the technologies can match the requirements defined in oneM2M, analyzes how the technologies can leverage the design of the architecture of oneM2M.
|
118 503
|
oneM2M Architecture Part 2: Study for the merging of architectures proposed for consideration by oneM2M
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118503/01.00.00_60/tr_118503v010000p.pdf
|
The present document provides an evaluation of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. Common Functional Entities and Reference Points are identified, as well as critical differences. New functionality will not be considered as part of this study. The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications. The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group.
|
118 502
|
Architecture Part 1: Analysis of the architectures proposed for consideration by oneM2M
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118502/01.00.00_60/tr_118502v010000p.pdf
|
The present document provides an analysis and comparison of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. In addition, architectural work by other non-oneM2M Partner Type 1 organizations is provided for consideration. The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications (TS). The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group.
|
104 112
|
Lawful Interception (LI); Collection of test cases for Lawful Interception and Lawful Disclosure
|
TR
|
1.2.1
|
http://www.etsi.org/deliver/etsi_tr/104100_104199/104112/01.02.01_60/tr_104112v010201p.pdf
|
The present document provides an informative basis for LI and LD related testing procedures, thus giving an international and inter-organizational understanding about applicable tests. By using the present document, communication and examination of tests is simplified by creating an equal understanding and structure of testing, regardless of time and organization. The test cases and test scenario components describe as many use cases as possible.
|
105 178
|
Access, Terminals, Transmission and Multiplexing (ATTM); Comparison of sustainability parameters between internal and external, including "cloud-based", ICT hosting solutions
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/105178/01.01.01_60/tr_105178v010101p.pdf
|
The present document provides methods to enable a comparison of sustainability parameters between both internal and external (including "cloud-based") ICT hosting solutions addressing: • energy consumption; • Green House Gas (GHG) emission; • water consumption; • treatment of electrical and electronic equipment including maintenance at End of Life (EoL). The present document does not address: • technical aspects of whether a given external hosting solution is able to provide a functional replacement of Users ICT needs; • methods of improving resource management within data centres/ICT sites (reference should be made to ETSI EN 305 174-2 [i.8] and ETSI TS 105 174-2 [i.12].
|
105 177
|
Access, Terminals, Transmission and Multiplexing (ATTM); Benefit Analysis of Ethernet and power over coaxial cables - IP Video Surveillance Case Studies
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/105177/01.01.01_60/tr_105177v010101p.pdf
|
The present document reviews the benefit analyses and environmental impact for selected use cases (such as mass transit systems) of using coaxial cables to support both Ethernet and power over coaxial equipment for IP Video Surveillance Systems (VSS) when: a) upgrading existing analogue VSS using legacy coaxial cables as compared with installation of alternative transmission media; and b) building new VSS by installing coaxial cables as compared with other transmission media.
|
105 174-6
|
Integrated broadband cable telecommunication networks (CABLE); Broadband Deployment and Energy Management; Part 6: Cable Access Networks
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/10517406/01.01.01_60/tr_10517406v010101p.pdf
|
The present document describes the cable access network, and progressive network access architectures that reduce the network energy consumption and the metrics required to benchmark the network and its components to support and enable the proper implementation of services, applications and content on an energy efficient infrastructure and describe measures that may improve the energy efficiency of cable access networks. Within the present document: • clause 4 presents the schematic for cable access network infrastructures, the evolution of the network architectures to meet consumer capacity demand and bandwidth growth and the main components of the cable access network energy consuming elements; • clause 5 presents measurement key performance indicators to baseline and measure network energy performance; • clause 6 explains power consumption metrics of the CAN; • clause 7 describes and gives consideration to power metrics of field deployed access network elements; • clause 8 describes the electrical powering of the CAN components and the distributed usage of the electrical power. This clause explains ways to improve the power consumption and benchmarking the HFC CAN plant; • clause 9 considers the calculations to measure the data throughput of a CAN.
|
105 174-5-2
|
Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 2: Office premises (single-tenant)
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740502/01.01.01_60/tr_1051740502v010101p.pdf
|
The present document details measures which may be taken to improve the energy efficiency within office premises (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within office premises (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture.
|
105 174-5-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant)
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740501/01.01.01_60/tr_1051740501v010101p.pdf
|
The present document details measures which may be taken to improve the energy efficiency within homes (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions of terms and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within homes (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture.
|
105 174-4
|
Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 4: Access networks
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/10517404/01.01.01_60/tr_10517404v010101p.pdf
|
The present document details measures which may be taken to improve the energy efficiency the access networks for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Clause 4 of the present document: • identifies the standardization bodies working on interfaces to, cabling within, installation of, and other aspects of the communication infrastructures of, access networks; • outlines some of the principal access network topographies and their differences in respect of energy consumption; • provides strategic analysis of energy consumption trends within access networks; • develops the concept of Key Performance Indicators (KPI), introduced in Part 1 of this multi-part set of documents, to enable consistent monitoring of energy efficiency; • outlines further work needed to ensure the improvement of energy efficiency in communication networks. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of the present document to provide detailed standardized solutions for network architecture.
|
105 174-2-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 2: Network sites; Sub-part 1: Operator sites
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740201/01.01.01_60/tr_1051740201v010101p.pdf
|
The present document details measures which may be taken to improve the energy efficiency within operator's sites for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 introduces operator sites concepts; • clause 5 details the approaches that may be employed to improve energy efficiency within the areas of the operator site containing network telecommunications equipment; • clause 6 details the approaches that may be employed to improve energy efficiency within the areas of the operator site containing information telecommunications equipment. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for network architecture. The present document focuses on energy efficiency. The CO2 footprint is not taken in account in the present document.
|
104 106
|
Publicly Available Specification (PAS); O-RAN Security Threat Modeling and Risk Assessment (O-RAN.WG11.Threat-Modeling.O-R003-v03.00)
|
TR
|
3.0.0
|
http://www.etsi.org/deliver/etsi_tr/104100_104199/104106/03.00.00_60/tr_104106v030000p.pdf
|
The present document describes the O-RAN Security Threat Modeling and Risk Assessment. It identifies assets to be protected, analyses the O-RAN components for vulnerabilities, examines potential threats associated with those vulnerabilities, provides security principles which stakeholders should address when building a secure end-to-end O-RAN system and assesses the risks of the identified threats based on impact and likelihood factors. NOTE: The present document is transformed from a Technical Specification (TS) to a Technical Report (TR) as it does not contain normative requirements. Instead, it is an informative document that serves as a vital resource for understanding the potential risks within O-RAN and defining appropriate requirement/controls to mitigate them effectively.
|
118 501
|
oneM2M Use Case collection
|
TR
|
1.0.0
|
http://www.etsi.org/deliver/etsi_tr/118500_118599/118501/01.00.00_60/tr_118501v010000p.pdf
|
The present document includes a collection of use cases from a variety of M2M industry segments (listed in table 1.1). Each use case may include a description, source, actors, pre-conditions, triggers, normal and alternative flow of sequence of interactions among actors and system, post-conditions, illustrations and potential requirements. The potential requirements provide an initial view of what oneM2M requirements could arise from the Use Case as seen by the contributor. These are intended to help the reader understand the use case's needs. These potential requirements may have been subsequently submitted by the contributor for consideration as candidate oneM2M requirements, which may or may not have been agreed as a oneM2M requirement (often after much editing). As such, there may not be a direct mapping from the potential requirements to agreed oneM2M requirements [i.14]. Table 1.1 Industry Segment oneM2M Use Cases Agriculture Energy Wide area Energy related measurement/ control system for advanced transmission and distribution automation Analytics for oneM2M Smart Meter Reading Environmental Monitoring for Hydro-Power Generation using Satellite M2M Oil and Gas Pipeline Cellular /Satellite Gateway Enterprise Smart building Finance Healthcare M2M Healthcare Gateway Wellness services Secure remote patient care and monitoring Industrial Public Services Street Light Automation Devices, Virtual devices and Things Car/Bicycle Sharing Services Smart parking Information Delivery service in the devastated area Residential Home Energy Management Home Energy Management System Plug-In Electrical Charging Vehicles and power feed in home scenario Real-time Audio/Video Communication Event Triggered Task Execution Semantic Home Control Semantic Device Plug and Play Retail Transportation Vehicle Diagnostic & Maintenance Report Remote Maintenance services Neighbourhood Alerting on Traffic Accident Fleet management service using Digital Tachograph Other Extending the M2M Access Network using Satellites M2M data traffic management by underlying network operator Optimizing connectivity management parameters with mobile networks Optimizing mobility management parameters with mobile networks Sleepy nodes Collection of M2M system data Leveraging Broadcasting/ Multicasting Capability of Underlying Networks Service Provisioning for Equipment with Built-in Device ETSI ETSI TR 118 501 V1.0.0 (2015-05) 12
|
104 225
|
Securing Artificial Intelligence TC (SAI); Privacy aspects of AI/ML systems
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/104200_104299/104225/01.01.01_60/tr_104225v010101p.pdf
|
The present document identifies the role of privacy as one of the components of the Security of AI, and defines measures to protect and preserve privacy in the context of AI that covers both, safeguarding models and protecting data, as well as the role of privacy-sensitive data in AI solutions. It documents and addresses the attacks and their associated remediations where applicable, considering the existence of multiple levels of trust affecting the lifecycle of data. The investigated attack mitigations include Non-AI-Specific (traditional Security/Privacy redresses), AI/ML-specific remedies, proactive remediations ("left of the boom"), and reactive responses to an adversarial activity ("right of the boom").
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.