id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 248
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
185 013
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Codecs for customer network devices
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/185000_185099/185013/03.01.01_60/tr_185013v030101p.pdf
|
The objective of the present document is to define the set of codecs supported by CNDs for NGN services, on the basis of the service requirements contained in TS 181 005 [i.1] and TS 185 005 [i.4], and with reference to the CNDs architecture defined in TS 185 006 [i.11] (for communication services) and TS 185 009 [i.5] (for IPTV services). Work will address AV/broadcast codecs for IPTV and Conversational codecs for telephony services. It will be fully consistent with the set of codecs identified in TS 181 005 [i.1]. When TS 181 005 [i.1] already specifies a list of codecs for voice services, no new codecs will be added, no codec will be removed nor downgraded in status (mandatory, recommended optional) within this list. For each service (mainly person to person communication and IPTV) work will be focused on defining subset of default/mandatory which is the only way to guarantee interoperability and avoid transcoding a minimum set of codecs to be supported will be defined.
|
185 012
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study of security mechanisms for customer premises networks connected to TISPAN NGN
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/185000_185099/185012/03.01.01_60/tr_185012v030101p.pdf
|
The present document presents the results of a study into the feasibility of providing security mechanisms to be implemented in a Customer Premises Network (CPN) that allow the CPN to comply with the security objectives and requirements of the CPN. The present document identifies the placement of measures in the Customer Network Gateway (CNG) and in the Customer Network Devices (CNDs) that support the end-to-end security architecture of NGN release 3 as defined in TR 180 001 [i.20] (NGN-R3 release definition) and TS 187 003 [i.18] (security architecture). The present document completes task 7 of the TVRA method defined in TS 102 165-1 [i.21] with due account of the remainder of the TVRA for CPNs presented in TR 185 008 [i.13] and TR 187 002 [i.17].
|
185 008
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of security mechanisms for customer networks connected to TISPAN NGN R2
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/185000_185099/185008/02.00.00_60/tr_185008v020000p.pdf
|
The present document present an analysis of the security mechanisms that could be supported in the customer environment (Customer Network Gateway or Customer Devices) with reference to the overall end to end security architecture for the NGN defined by WG7. As examples, these mechanisms can be related to authentication (for connectivity and for services), firewalling and network access/parental control, virus protection, intrusion detection, Anti Spam capabilities. The activity will be performed in close relationship with WG7. The reactions to threats or the protections against threats described in the present document will involve only the CPN, not the external network.
|
185 007
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of protocols for customer networks connected to TISPAN NGN
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/185000_185099/185007/02.00.00_60/tr_185007v020000p.pdf
|
The present document contains informative text for analysing the set of protocols that can be used in the Customer Premises Networks (CPN) on the interfaces defined by stage 2 documents TS 185 003 [8] and TS 185 006 [7] related to service and transport layers. It will constitute a basic document produced by WG5, with a strong collaboration with WG3, to be used as the starting point for future technical specifications on that field.
|
185 004
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); High level customer network architectures
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/185000_185099/185004/01.01.01_60/tr_185004v010101p.pdf
|
The objective of the present document is to analyse the possible architectures for the customer environment, combining different possibilities in terms of elements to be considered. In particular, the analysed architectures will cover the possibility of managing one or more than one entry points from the WAN side, using one or more than one customer gateway, or possibly excluding the adoption of a customer gateway. Different alternatives for Customer Network Gateway ownership will also be examined. The detailed architectures of customer devices and customer network gateways will be addressed in other WIs and will take into account the possible alternatives analysed in the present document. The customer network is intended to support residential or small office scenarios, so that the scope of the document does not include corporate scenarios which are to be covered by other documents.
|
184 012
|
Network Technologies (NTECH); Description of the DNS protocol usage in IP based operators networks
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/184000_184099/184012/01.01.01_60/tr_184012v010101p.pdf
|
The present document describes different use cases for the usage of the DNS protocol (e.g. Service Location, NP/ENUM, address resolution) in IP based operators networks. The DNS base protocol itself is defined in RFC 1035 [i.16]. The present document describes the behaviour and details for DNS protocol usage in IP based operators networks, transport options for DNS messages, DNS protocol behaviour and configuration as well as options to make the usage of the DNS protocol more reliable (e.g. timer characteristics etc.). The use cases described here and options to make the usage of the DNS protocol more reliable are principal ones for network operators and not intended to be exhaustive.
|
184 008
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Infrastructure ENUM Options for a TISPAN IPX
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/184000_184099/184008/02.01.01_60/tr_184008v020101p.pdf
|
The present document provides an overview of some of the relevant options that can be used to implement Infrastructure ENUM (I-ENUM), which in the present document is defined as the use of the technology specified in RFC 3761 [i.1] by the carrier of record to map a telephone number into a URI. That URI then identifies a specific point of interconnection to that communication provider's network that could enable the originating party to establish communication over an IPX to the associated terminating party. An assessment of the options is given and recommendations made in order to provide a secure and reliable implementation of I-ENUM for TISPAN networks to facilitate routeing and interconnection within NGNs.
|
184 007
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Naming/Numbering Address Resolution (NAR)
|
TR
|
2.2.1
|
http://www.etsi.org/deliver/etsi_tr/184000_184099/184007/02.02.01_60/tr_184007v020201p.pdf
|
The present document investigates the need to introduce a Naming/Numbering Address Resolution framework into TISPAN NGN conformant communication networks. To this end the following topics are covered: • Analysis of the consequences of creating a Naming/Numbering Address Resolution framework. • Gap Analysis of current TISPAN NGNs specifications in comparison to existing/emerging solutions of NAR methods. • Identification of items for standardization as a result of the analysis described in the bullet above. Furthermore the present document investigates the Naming/Numbering Address Resolution (NAR) in NGNs and identifies Naming/Numbering Address Resolution (NAR) use cases used in NGN environments.
|
184 005
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Types of numbers used in an NGN environment
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/184000_184099/184005/01.01.01_60/tr_184005v010101p.pdf
|
The present document describes the public identifiers, in the numeric format, used in NGNs: international E.164 numbers, E.164 numbers in the national formats and different types of non-E.164 numbers. It describes the processing of dialled digits to achieve these numbers and the usage of all these kinds of numbers. For E.164 numbers also the processing to a target name in an NGN environment for further name/number to address translation is explained. The processing (treatment) of non-E.164 numbers is FFS but some initial discussion could be found in annex A.
|
184 003
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Portability of telephone numbers between operators for Next Generation Networks (NGNs)
|
TR
|
3.1.1
|
http://www.etsi.org/deliver/etsi_tr/184000_184099/184003/03.01.01_60/tr_184003v030101p.pdf
|
The present document focuses on number portability (NP) for telephone numbers from national numbering plans (NNP) for Next Generation Networks (NGNs). These national numbering plans are based on ITU-T Recommendation E.164 [i.19]. Identifier Portability, i.e. portability of other public identifiers than telephone numbers (e.g. name based SIP URIs or SIP/tel URIs with a specific phone-context) is outside the scope of the present document, but it is recognized that this could be the topic of a future separate study. The present document identifies ways to support portability of telephone numbers (e.g. E.164 numbers) between Service Providers (SP) - so called "service provider portability" (SPP). The term operator in the present document is used instead of Service Provider and the report identifies functionality needed to support the following portability scenarios: • Between NGN operators; • From NGN operators to PSTN/ISDN SPs; • From PSTN/ISDN SPs to NGN operators. NOTE: The types of telephone numbers that are subject to portability is a national matter, and are therefore not addressed in the present document. The support for number portability can be divided in two distinct processes: a) the process of porting a telephone number from one operator to another; and b) the process to establish a call to a telephone number that may be ported. The first process a) would include the actions from: • the request of the telephone number to be ported; • the distribution and storage of NP Data (NPD) that the telephone number is ported from one operator to another operator, and at which time the porting takes effect; • making the necessary NPD available to the data base environment that are accessible in real time from the communication processing systems; • allowing communication establishment to the operator that currently serves the telephone number. The second process b) would include information: • how data bases in the real time environment can be accessed and NPD can be retrieved; • from where the NPD can be retrieved; • how the NPD can be carried and used and transformed to NP Routing Information (NRI) for the establishment of the communication to the current operator. The detailed process of porting a telephone number and storage and distribution of NPD is essentially an administrative process, that may differ very much from country to country. The present document considers mainly the following: • NGN network architecture specific for number portability; • how the NPD obtained from the real time data base environment is used to route sessions, based on NRI, within and between networks. However, some information relating to the process of porting a telephone number is provided in annex A, and how to populate and make NPD and ENUM data available to the real time environment is provided in annexes B and C. Clause 5 gives an high level framework concerning different kind of DBs in the real time and in the non-real time environment of the NGN on different levels (i.e. operator, national and international level). ETSI ETSI TR 184 003 V3.1.1 (2010-06) 6
|
183 072
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Emulation Services for PSTN Modem Calls
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Resource and Admission Control Sub-System (RACS); Rr interface based on the ANCP protocol
|
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.
|
183 069
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Business Trunking; NGCN-NGN Interfaces Implementation Guide
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Guidelines on using Ia H.248 profile for control of Border Gateway Functions (BGF); Border Gateway Guidelines
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on Out-of-band DTMF
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on new methods for Overlap Sending
|
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.
|
183 052
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Solution for REFER interworking problems
|
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".
|
183 050
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Register of assigned protocol numbers and names
|
TR
|
2.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183050/02.01.01_60/tr_183050v020101p.pdf
|
The present document contains the record of assignment of names, numbers and identifiers used in TISPAN protocol specifications, managed by TISPAN, and which are required to be globally unique. In particular, it contains the assignments and sub-structure of ASN.1 Object Identifier trees assigned to TISPAN and the assignments and sub-structure of any URI or URN schemes which TISPAN manages. The present document also contains information on names, numbers and identifiers used in TISPAN protocol specifications, but which are assigned by other authorities. This may include assignments from the IETF, ETSI, W3C, etc. Names, addresses, numbers and identifiers and their associated schemes, used in networks, assigned or managed or monitored by TISPAN Working Group 4 are outside the scope of the present document. All aspects of numbering, addressing and naming of a telecommunications network are outside the scope of the present document.
|
183 050
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Register of assigned protocol numbers and names
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183050/01.01.01_60/tr_183050v010101p.pdf
|
The present document contains the record of assignment of names, numbers and identifiers used in TISPAN protocol specifications, managed by TISPAN, and which are required to be globally unique. In particular, it contains the assignments and sub-structure of ASN.1 Object Identifier trees assigned to TISPAN and the assignments and sub-structure of any URI or URN schemes which TISPAN manages. The present document also contains information on names, numbers and identifiers used in TISPAN protocol specifications, but which are assigned by other authorities. This may include assignments from the IETF, ETSI, W3C, etc. Names, addresses, numbers and identifiers and their associated schemes, used in networks, assigned or managed or monitored by TISPAN Working Group 4 are outside the scope of the present document. All aspects of numbering, addressing and naming of a telecommunications network are outside the scope of the present document.
|
183 046
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); SDP Interworking between Call/Session Control Protocols (SIP/SDP, RTSP/SDP; etc.) and the Gateway Control Protocol (H.248/SDP)
|
TR
|
3.3.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183046/03.03.01_60/tr_183046v030301p.pdf
|
The present document specifically describes the differing SDP usage between SIP [i.2] and H.248 [i.3] together with the implied mapping capability that is performed by the MGC/Call Server. SDP [i.1] has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media requirements of a given session/call/connection. However, the different VoIP control protocols that utilise SDP each specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking between them. SDP [i.1] has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media requirements of a given session/call/connection. However, the different VoIP control protocols that utilize SDP each specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking between them. Specifically for the present document, the differing SDP usage between SIP [i.2] and H.248 [i.3] will be described together with the implied mapping capability that is performed by the MGC/Call Server. Any network element (e.g. a MGCF) which handles both H.248/SDP signalling and SIP/SDP signalling provides any necessary interworking between both signalling protocols (see figure 1). Such interworking comprises in general: • interworking between SIP and H.248 signalling on message and procedural level (out of scope of the present document); and • interworking between the two SDP segments (SDP-SDP interworking; the scope of the present document). The function providing SDP-to-SDP interworking between SIP/SDP and H.248/SDP signalling is, in the present document, termed a "SDP Mapper" (see also clause 3.1). The SDP Mapper performs SDP-SDP interworking capability to reconcile the different uses of SDP between control protocols H.248 and SIP. In order to perform this role, the SDP Mapper takes into account i) which parts of SDP are required to be sent on an interface, and ii) which parts of SDP are received on an interface. For a given session/call, which use the two different control protocols at each end, some SDP parameters may be transited whilst others may not. The SDP Mapper ensures that the differing requirements with regard to SDP handling at each end are mutually satisfied. H.248 Media Gateway (MG or MGW) H.248 Media Gateway Controller (MGC) Network Element handling both H.248/SDP and SIP/SDP Signalling Scope of this Technical Report H.248/SDP Gateway Control Protocol (text encoding mode) SIP e.g. SIP Proxy, SIP User Agent, etc SDP Mapper SIP/SDP SIP-I Session Initiation Protocol Figure 1: Scope ETSI ETSI TR 183 046 V3.3.1 (2009-08) 7
|
183 046
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); SDP Interworking between SIP/SDP and H.248/SDP
|
TR
|
2.0.0
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183046/02.00.00_60/tr_183046v020000p.pdf
|
The present document specifically describes the differing SDP usage between SIP [i.2] and H.248 [i.3] together with the implied mapping capability that is performed by the MGC/Call Server. SDP [i.1] has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media requirements of a given session/call/connection. However, the different VoIP control protocols that utilise SDP each specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking between them. SDP [i.1] has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media requirements of a given session/call/connection. However, the different VoIP control protocols that utilize SDP each specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking between them. Specifically for the present document, the differing SDP usage between SIP [i.2] and H.248 [i.3] will be described together with the implied mapping capability that is performed by the MGC/Call Server. Any network element (e.g. a MGCF) which handles both H.248/SDP signalling and SIP/SDP signalling provides any necessary interworking between both signalling protocols (see figure 1). Such interworking comprises in general: • interworking between SIP and H.248 signalling on message and procedural level (out of scope of the present document); and • interworking between the two SDP segments (SDP-SDP interworking; the scope of the present document). The function providing SDP-to-SDP interworking between SIP/SDP and H.248/SDP signalling is, in the present document, termed a "SDP Mapper" (see also clause 3.1). The SDP Mapper performs SDP-SDP interworking capability to reconcile the different uses of SDP between control protocols H.248 and SIP. In order to perform this role, the SDP Mapper takes into account i) which parts of SDP are required to be sent on an interface, and ii) which parts of SDP are received on an interface. For a given session/call, which use the two different control protocols at each end, some SDP parameters may be transited whilst others may not. The SDP Mapper ensures that the differing requirements with regard to SDP handling at each end are mutually satisfied. H.248 Media Gateway (MG or MGW) H.248 Media Gateway Controller (MGC) Network Element handling both H.248/SDP and SIP/SDP Signalling Scope of this Technical Report H.248/SDP Gateway Control Protocol (text encoding mode) SIP e.g. SIP Proxy, SIP User Agent, etc SDP Mapper SIP/SDP SIP-I Session Initiation Protocol Figure 1: Scope ETSI ETSI TR 183 046 V3.3.1 (2009-08) 7
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-Call Related Procedures and Management System Interaction
|
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 014
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation; Development and Verification of PSTN/ISDN Emulation
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/183000_183099/183014/01.01.01_60/tr_183014v010101p.pdf
|
The present document presents the results of an analysis of bearer, basic and supplementary services currently provided in PSTN and ISDN implementations. The purpose of the analysis was to identify further areas of standardization to ensure that such services can be reliably emulated within the NGN thus enabling network operators to fulfil the technical regulatory obligations on European ECN providers of Publicly Available Telephone Service. It was assumed during the analysis that PSTN and ISDN signalling would be presented in the Integrated Services User Part (ISUP) as defined in EN 300 356-1 [3] and EN 300 356-2 [4] and that signalling within the NGN would be encapsulated in SIP-I as defined in EN 383 001[1] and ITU-T Recommendation H.248.1 [29].
|
182 031
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Remote CPN QoS Control; Study on CPN - RACS Interaction
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN based IPTV mapping or interconnect between IPTV systems
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Impact of mobility for access-technology independent networks in the TISPAN NGN architecture
|
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.
|
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.
|
182 010
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Peer-to-peer for content delivery for IPTV services: analysis of mechanisms and NGN impacts
|
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.
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Fixed Mobile Convergence; Requirements analysis
|
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
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Technical Report on NGN National IP Interconnection
|
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.
|
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.
|
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
|
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
|
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 540
|
Electronic Signatures and Trust Infrastructures (ESI); Standardization requirements for Smart Contracts based on Electronic Ledgers
|
TR
|
1.1.1
|
http://www.etsi.org/deliver/etsi_tr/119500_119599/119540/01.01.01_60/tr_119540v010101p.pdf
|
The present document defines standardization issues for Smart Contracts, as defined in Data Act [i.1], and based on Electronic Ledgers as defined by eIDAS2 [i.2]. It builds on existing and planned standardization and publicly available specifications. It presents a novel and as yet unpublished Chain of Trust, by addressing the role of all involved entities in building, deploying, and executing a Smart Contract computer program on an Electronic Ledger. All the relevant actors, artifacts, hardware, networks and tools, are identified by emphasizing the critical points where governance, safety, security, and identity issues are required. The Chain of Trust will be extensively translated in suitable recommendations in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. The security of Smart Contracts will be significantly compromised by an incomplete validation chain, which exposes users to various risks, including fraud and attacks. NOTE 1: The present document summarizes the results of a scoping study that examines the issues for the application of Smart Contracts, particularly in relation to the European frameworks outlined in the Data Act [i.1] and eIDAS2 [i.2] regulations. The goal is to pinpoint standardization issues for Smart Contracts and Electronic Ledgers in data-sharing computer applications. Additionally, the study considers reports and standards from ETSI ISG PDL (at the time of the publication of the present document conveyed into ETSI TC DATA), ETSI TC ESI, and checks consistency with ISO and CEN documents. NOTE 2: Unless otherwise specified in the present document, the definition of Smart Contracts refers to Regulation (EU) 2023/2854 [i.1] and the definition of Electronic Ledgers, and Qualified Electronic Ledger refer to Regulation (EU) 2022/2065 [i.2]. See Annex C for further details. The present document is structured as follows: • Clause 4 enumerates the regulations, applied standards, EU initiatives and other activities involved for the use of Smart Contracts in Data Sharing Computer Applications. • Clause 5 is the core of the present document. It identifies the entities and their inter-relations for the creation, validation, deployment and use of Smart Contracts in Electronic Ledgers. A Chain of Trust listing the main entities and their relations will be presented and discussed; the Chain of Trust allows to highlight issues that will be focused in the next clause. • Clause 6 lists in a concise way the issues that are translated into formal requirements in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. • Clause 7 concludes. • Annex A presents four figures showing a particular, fine-grained, implementation of the Chain of Trust as presented in Table 1: entities, their relations participating in the design of SC Language, the deployment, and execution of Smart Contracts on a Qualified Electronic Ledger. Other implementations are also possible. • Annex B graphically and informally depicts, the Chain of Trust, as formally described in Table 2. • Annex C gives a comparative overview of definitions in normative and standard documents. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 8
|
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
|
<empty>
|
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-1
|
Electronic Signatures and Trust Infrastructures (ESI); Selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes; Part 1: Feasibility study
|
TR
|
1.3.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/11947601/01.03.01_60/tr_11947601v010301p.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.103]. 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.71]. 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 document may serve as input to (Q)EAA issuance policies as being specified in ETSI TS 119 471 [i.96] and (Q)EAA profiles as being specified in ETSI TS 119 472-1 [i.97]. 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.71] specifies the PID to be issued to an EUDI Wallet as mdoc [i.181] (with 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 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.3.1
|
http://www.etsi.org/deliver/etsi_tr/119400_119499/11941104/01.03.01_60/tr_11941104v010301p.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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.