35.240 - Applications of information technology
ICS 35.240 Details
Applications of information technology
Anwendungen der Informationstechnik
Applications des technologies de l'information
Uporabniške rešitve informacijske tehnike in tehnologije
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.240 - Applications of information technology
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).
This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.
- Standard164 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft140 pagesEnglish languagesale 10% offe-Library read for1 day
RTS/LI-00242-3
- Standard58 pagesEnglish languagesale 15% off
- Technical specification58 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the application of medical waveform format encoding rules (MFER) to describe standard electrocardiography waveforms measured in physiological laboratories, hospital wards, clinics, and primary care medical checkups. It covers electrocardiography such as 12-lead, 15-lead, 18-lead, Cabrera lead, Nehb lead, Frank lead, XYZ lead, and exercise tests that are measured by inspection equipment such as electrocardiographs and patient monitors that are compatible with MFER. Medical waveforms that are not in the scope of this document include Holter ECG, exercise stress ECG, and real-time ECG waveform encoding used for physiological monitors.
- Standard34 pagesEnglish languagesale 15% off
This document defines the application of medical waveform format encoding rules (MFER) to describe long-term electrocardiography waveforms measured in physiological laboratories and health care clinics. It covers electrocardiography such as bipolar 2, 3-lead, 12-lead that are measured by medical equipment such as Holter electrocardiograph and patient physiological monitors that are compatible with MFER documents encoding rules (see ISO 22077-1).
- Standard28 pagesEnglish languagesale 15% off
This document describes a basic role and functional model of the intelligent transport systems (ITS) data aggregation role, which is a basic role of ISO/TR 4445. It provides a paradigm describing: a) a framework for the provision of ITS data aggregation for cooperative ITS service application; b) a description of the concept of a role and functional model for such roles; c) a conceptual architecture between actors involved in the provision/receipt of ITS data aggregation; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures.
- Technical report11 pagesEnglish languagesale 15% off
- Draft11 pagesEnglish languagesale 15% off
- Draft11 pagesEnglish languagesale 15% off
This document specifies security means and procedures for AVPS Type 3 as specified in ISO 23374-1. It focuses on operation interfaces and management interfaces as defined in ISO 23374-1.
- Technical specification44 pagesEnglish languagesale 15% off
- Draft44 pagesEnglish languagesale 15% off
- Draft44 pagesEnglish languagesale 15% off
This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts:
— a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and
— a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema.
This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).
- Draft64 pagesEnglish languagesale 10% offe-Library read for1 day
This standard establishes a normative definition of communication between personal telehealth insulin
pump devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other
ISO/IEEE 11073 standards including existing terminology, information profiles, application profile
standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in
telehealth environments, restricting optionality in base frameworks in favor of interoperability. This
standard defines a common core functionality of personal telehealth insulin pump devices.
In the context of personal health devices (PHDs), an insulin pump is a medical device used for the
administration of insulin in the treatment of diabetes mellitus, also known as continuous subcutaneous
insulin infusion (CSII) therapy. This standard provides the data modeling according to ISO/IEEE 11073-20601 and does not specify the measurement method.
- Draft132 pagesEnglish languagesale 10% offe-Library read for1 day
This technical specification identifies and clarifies lighting properties for digital building design and maintenance. This document provides all the needed properties to design and to describe lighting systems. These properties are intended to be used for mapping between data providers and requesters. The mapping of the identifiers enables the exchange of luminaire and sensing device data within different databases. The unambiguous mapping and description of properties improves the data quality, reduces misinterpretations and the processing time in digital environments. Therefore, the properties listed in this document establish the essential description of lighting systems in BIM systems and databases. The listed properties in this document are used to structure the product data sheet which is complemented with real product information.
- Technical specification61 pagesEnglish languagesale 15% off
- Draft61 pagesEnglish languagesale 15% off
- Draft61 pagesEnglish languagesale 15% off
This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts: — a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and — a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema. This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).
- Standard100 pagesEnglish languagesale 15% off
- Standard109 pagesFrench languagesale 15% off
- Draft76 pagesFrench languagesale 15% off
- Corrigendum1 pageEnglish languagesale 10% offe-Library read for1 day
This document specifies:
— the data elements, structures and relationships between the data elements required for the exchange of information, which uniquely and with certainty identify pharmaceutical dose forms, units of presentation, routes of administration and packaging items (containers, closures and administration devices) related to medicinal products;
— a mechanism for the association of translations of a single concept into different languages, which is an integral part of the information exchange;
— a mechanism for the versioning of the concepts in order to track their evolution;
— rules to help regional authorities to map existing regional terms to the terms created using this document, in a harmonized and meaningful way.
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft34 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62351-3:2023 specifies how to provide confidentiality, integrity protection, and message level authentication for protocols that make use of TCP/IP as a message transport layer and utilize Transport Layer Security when cyber-security is required. This may relate to SCADA and telecontrol protocols, but also to additional protocols if they meet the requirements in this document.
IEC 62351-3 specifies how to secure TCP/IP-based protocols through constraints on the specification of the messages, procedures, and algorithms of Transport Layer Security (TLS) (TLSv1.2 defined in RFC 5246, TLSv1.3 defined in RFC 8446). In the specific clauses, there will be subclauses to note the differences and commonalities in the application depending on the target TLS version. The use and specification of intervening external security devices (e.g., "bump-in-the-wire") are considered out-of-scope.
In contrast to previous editions of this document, this edition is self-contained in terms of completely defining a profile of TLS. Hence, it can be applied directly, without the need to specify further TLS parameters, except the port number, over which the communication will be performed. Therefore, this part can be directly utilized from a referencing standard and can be combined with further security measures on other layers. Providing the profiling of TLS without the need for further specifying TLS parameters allows declaring conformity to the described functionality without the need to involve further IEC 62351 documents.
This document is intended to be referenced as a normative part of other IEC standards that have the need for providing security for their TCP/IP-based protocol exchanges under similar boundary conditions. However, it is up to the individual protocol security initiatives to decide if this document is to be referenced.
The document also defines security events for specific conditions, which support error handling, security audit trails, intrusion detection, and conformance testing. Any action of an organization in response to events to an error condition described in this document are beyond the scope of this document and are expected to be defined by the organization’s security policy.
This document reflects the security requirements of the IEC power systems management protocols. Should other standards bring forward new requirements, this document may need to be revised.
This second edition cancels and replaces the first edition published in 2014, Amendment 1:2018 and Amendment 2:2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Inclusion of the TLSv1.2 related parameter required in IEC 62351-3 Ed.1.2 to be specified by the referencing standard. This comprises the following parameter:
• Mandatory TLSv1.2 cipher suites to be supported.
• Specification of session resumption parameters.
• Specification of session renegotiation parameters.
• Revocation handling using CRL and OCSP.
• Handling of security events.
b) Inclusion of a TLSv1.3 profile to be applicable for the power system domain in a similar way as for TLSv1.2 session.
- Standard52 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a 3rd Party API for the Home and Building HBES Open Communication System.
- Standard124 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft124 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines an additional data concept that may be transferred as the ‘optional additional data ’ part of an eCall MSD, as defined in EN 15722, that may be transferred from a vehicle to a PSAP in the event of a crash or emergency via an eCall communication session.
The purpose of this document is to provide means to notify the PSAP of any limitations to the sending equipment that are endorsed by other standards, but not (immediately) apparent to the receiver. Lack of knowledge about these limitations can hamper the emergency process. This document describes an additional data concept which facilitates the inclusion of information about such limitations in a consistent and usable matter.
This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible.
- Standard18 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft18 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
This document is part of the ISO/IEC 5087 series, which specifies a common data model for cities. This document specifies the foundation level concepts.
- Standard50 pagesEnglish languagesale 15% off
- Draft50 pagesEnglish languagesale 15% off
This document establishes terms and definitions that are useful in the specification, characterization and evaluation of presentation attack detection (PAD) methods. This document does not provide the following: — standardization of specific PAD detection methods; — detailed information about countermeasures (i.e. anti-spoofing mechanisms), algorithms or sensors; — overall system-level security or vulnerability assessment. The attacks to be considered in this document are those that take place at the capture device during the presentation and collection of the biometric characteristics. Any other attacks are considered outside the scope of this document.
- Standard11 pagesEnglish languagesale 15% off
In respect of pan-European eCall (operating requirements defined in EN 16072), this document defines the high-level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a circuit-switched mobile communications network.
NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third-party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and is consistent in respect of the interface to the PSAP. This deliverable makes reference to those provisions but does not duplicate them.
- Draft54 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the fields of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Draft55 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard11 pagesEnglish languagesale 15% off
- Standard13 pagesEnglish languagesale 15% off
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines: — ASN.1 (data) types within the fields of EFC; — ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC. This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Standard49 pagesEnglish languagesale 15% off
This document specifies a common interface by which financial-transaction-card-originated messages can be interchanged between acquirers and card issuers. It specifies message structure and format, including normalized data types. Message, field, value definitions and supporting information are provided by the ISO 8583 maintenance agency (MA). Contact and web page information for the ISO 8583 MA can be found at: https://www.iso.org/maintenance_agencies.html. The method by which messages are transported or settlement takes place is not within the scope of this document. NOTE With the proliferation of technology available to financial institutions to offer services to customers, a range of tokens now exist for identifying account relationships (e.g. financial transaction cards). In order to maintain clarity, this document will continue to use card terminology that applies to tokens and cards, unless the element is specific to tokens or cards, in which case it will be identified as such. However, the actual token numeric issued by a financial institution can be different from the associated card numeric.
- Standard18 pagesEnglish languagesale 15% off
Automated valet parking systems (AVPSs) perform level 4 automated driving of individual or multiple unoccupied vehicles within a prescribed area of a parking facility. This document specifies performance requirements for the operation functions, the environmental conditions within parking facilities where automated vehicle operation is performed, and the test procedures to verify the performance requirements. An AVPS is comprised of physically separated sub-systems distributed among vehicles, facility equipment and user domains. The functionalities of AVPSs are realized by cooperation of these sub-systems, which are, in many cases, provided by different organizations. This document defines the system architecture and the communication interfaces between the sub-systems at the logical level. An AVPS manages its system participants (i.e. AVPS-compliant vehicles and parking facilities) and provides interfaces to other facility users and involved persons (e.g. system operators, facility managers). This document contains requirements for the management functions such as checking compatibility between vehicles and parking facilities, performing remote assistance and recovery when automated driving cannot be performed, and executing operation stop commands in response to the actions of other facility users. AVPSs are intended for use by a service provider upon receiving authority over vehicles from individual service recipients. This document does not include parking automation technologies that are solely based on usage by an individual user. If the vehicle is put into driverless operation directly by the user, this is not considered to be part of the AVPS.
- Standard153 pagesEnglish languagesale 15% off
This document specifies containment requirements for tagged PDF documents that use the PDF 1.7 namespace and the PDF 2.0 namespace. These containment requirements extend, and entirely comply with, the rules and provisions already specified for tagged PDF documents within ISO 32000-2.
- Technical specification40 pagesEnglish languagesale 15% off
- Draft40 pagesEnglish languagesale 15% off
- Draft40 pagesEnglish languagesale 15% off
This document establishes a standard registration and maintenance mechanism for the registration of ISO 19150-4-conformant geographic information service ontologies.
This document makes use of ISO 19135-1 whenever appropriate.
This document does not define semantics operators or rules for ontologies, and does not develop any application ontology.
In relation to ISO 19101-1:2014, 6.2, this document defines and formalizes the following purposes of the ISO geographic information reference model:
— geographic information service components and their behaviour for data processing purposes over the Web; and
— OWL ontologies to cast ISO/TC 211 International Standards to benefit from and support the Semantic Web.
In relation to ISO 19101-1:2014, 8.3, this document addresses the Application:Procedural foundation of the ISO geographic information reference model.
- Draft36 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines rules for ISO 28560-1 data elements to be encoded in radio frequency identification (RFID) tags with a memory structure that is partitioned into four memory banks. This primarily applies to ISO/IEC 18000-63 (previously known as ISO/IEC 18000-6 Type C) operating in the UHF frequency, but not necessarily restricted to this technology. The rules for encoding a subset of data elements taken from the total set of data elements defined in ISO 28560-1 are based on ISO/IEC 15962, which uses an object identifier structure to identify data elements. This document defines the rules for encoding a unique item identifier in a specific memory bank, known as MB 01, taking into account different requirements for privacy. It also defines the rules for encoding other relevant data in a separate memory bank, known as MB 11. Each of these memory banks is addressable using different command set of the appropriate RFID technology. As with other parts of ISO 28560, this document is appropriate for the needs of all types of libraries (including academic, public, corporate, special, and school libraries). This document provides essential standards-based information about RFID in libraries. A source of additional information about implementation issues is provided in Annex A.
- Technical specification54 pagesEnglish languagesale 15% off
- Draft54 pagesEnglish languagesale 15% off
- Draft54 pagesEnglish languagesale 15% off
This document defines a 3rd Party API for the Home and Building HBES Open Communication System.
- Standard124 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft124 pagesEnglish languagesale 10% offe-Library read for1 day
This document addresses a blockchain-based traceability platform for cold chain food which realizes continuous and effective tracking of the cold chain food. The following aspects are included: — it explores issues and considerations for cold chain food traceability, especially during the epidemic outbreak; — it describes scenarios and stakeholders for effective tracking of the cold chain food using the platform; — it describes data elements and processes for the platform; — it presents the platform capabilities such as data tamper resistance, sustainability; — it gives relevant use cases based on the platform.
- Technical report11 pagesEnglish languagesale 15% off
- Draft11 pagesEnglish languagesale 15% off
- Draft11 pagesEnglish languagesale 15% off
This document defines a coverage processing language for server-side extraction, filtering, processing, analytics, and fusion of multi-dimensional geospatial coverages representing, for example, spatio-temporal sensor, image, simulation, or statistics datacubes. Services implementing this language provide access to original or derived sets of coverage information, in forms that are useful for client-side consumption.
This document relies on the ISO 19123-1 abstract coverage model. In this edition, regular and irregular multi-dimensional grids are supported for axes that can carry spatial, temporal or any other semantics. Future editions will additionally support further axis types as well as further coverage types from ISO 19123-1, specifically, point clouds and meshes.
- Draft80 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a conceptual schema for coverages. A coverage is a mapping from a spatial, temporal or spatiotemporal domain to attribute values sharing the same attribute type. A coverage domain consists of a collection of direct positions in a coordinate space that can be defined in terms of spatial and/or temporal dimensions, as well as non-spatiotemporal (in ISO 19111:2019, “parametric”) dimensions. Examples of coverages include point clouds, grids, meshes, triangulated irregular networks, and polygon sets. Coverages are the prevailing data structures in a number of application areas, such as remote sensing, meteorology and mapping of depth, elevation, soil and vegetation. This document defines the coverage concept including the relationship between the domain of a coverage and its associated attribute range. This document defines the characteristics of the domain. The characteristics of the attribute range are not defined in this document, but are defined in implementation standards. Consequently, the standardization target of this document consists of implementation standards, not concrete implementations themselves.
- Draft146 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides requirements and recommendations on all written text so that it is easy to read and understand in any user interface, regardless of its format. This document addresses the process of creation, adaptation and evaluation of written text that is easy to read and understand. This document does not consider devices or transmission mechanisms used to deliver written text. It does not provide language-specific guidance.
- Standard21 pagesEnglish languagesale 15% off
- Standard22 pagesFrench languagesale 15% off
- Draft21 pagesEnglish languagesale 15% off
- Draft21 pagesEnglish languagesale 15% off
This document specifies clinical sequencing information generated by massive parallel sequencing technology for sharing health information via massively parallel sequencing. This document covers the data fields and their metadata from the generation of sequence reads and base calling to variant evaluation and assertion for archiving reproducibility during health information exchange of clinical sequence information. However, the specimen collection, processing and storage, DNA extraction and DNA processing and library preparation, and the generation of test report are not in the scope of this document. This document hence defines the data types, relationship, optionality, cardinalities and bindings of terminology of the data. In essence, this document specifies: — the required data fields and their metadata from generation of sequence reads and base calling to variant evaluation and assertion for sharing clinical genomic sequencing data files generated by massively parallel sequencing technology, as shown in Figure 1; — the sequencing information from human samples using DNA sequencing by massively parallel sequencing technologies for clinical practice.
- Technical specification14 pagesEnglish languagesale 15% off
- Draft14 pagesEnglish languagesale 15% off
- Draft14 pagesEnglish languagesale 15% off
This document establishes a standard registration and maintenance mechanism for the registration of ISO 19150-4-conformant geographic information service ontologies. This document makes use of ISO 19135-1 whenever appropriate. This document does not define semantics operators or rules for ontologies, and does not develop any application ontology. In relation to ISO 19101-1:2014, 6.2, this document defines and formalizes the following purposes of the ISO geographic information reference model: — geographic information service components and their behaviour for data processing purposes over the Web; and — OWL ontologies to cast ISO/TC 211 International Standards to benefit from and support the Semantic Web. In relation to ISO 19101-1:2014, 8.3, this document addresses the Application:Procedural foundation of the ISO geographic information reference model.
- Standard30 pagesEnglish languagesale 15% off
- Standard31 pagesFrench languagesale 15% off
- Draft31 pagesEnglish languagesale 15% off
- Draft38 pagesFrench languagesale 15% off
- Technical specification146 pagesEnglish languagesale 15% off
- Draft146 pagesEnglish languagesale 15% off
- Draft146 pagesEnglish languagesale 15% off
This document defines an additional data concept that can be transferred as the ‘optional additional data’ part of an eCall MSD, as defined in EN 15722, that can be transferred from a vehicle to a PSAP in the event of a crash or emergency via an eCall communication session.
The purpose of this document is to provide means to notify the PSAP of any limitations to the sending equipment that are endorsed by other standards, but not (immediately) apparent to the receiver. Lack of knowledge about these limitations can hamper the emergency process. This document describes an additional data concept which facilitates the inclusion of information about such limitations in a consistent and usable matter.
This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible.
NOTE 1 The communications media protocols and methods for the transmission of the eCall message are not specified in this document.
NOTE 2 Additional data concepts can also be transferred, and it is advised to register any such data concepts using a data registry as defined in EN ISO 24978 [1]. See www.esafetydata.com for an example.
- Standard18 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft18 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the common conventions required for the interchange of specific patient data (demographic, recording conditions ...), ECG signal data and metadata, ECG measurements and ECG annotations, and ECG interpretation results. This document specifies the content and structure of the information which may be interchanged between digital ECG electrocardiographs/devices and computer ECG management systems, as well as other computer or information systems (cloud, etc.) where ECG data can be stored. This document defines the way to describe and encode standard and medium to long-term electrocardiogram waveforms measured in physiological laboratories, hospital wards, clinics and primary care medical check-ups, ambulatory and home care. It covers electrocardiograms such as 12-lead, 15-lead, 18-lead, Cabrera lead, Nehb lead, Frank lead, XYZ lead, Holter ECGs and exercise ECGs that are recorded, measured and analysed by equipment such as electrocardiographs, patient monitors, wearable devices. It also covers intracardiac electrograms recorded by implantable devices as well as the analysis results of ECG analysis and interpretation systems and software that are compatible with SCP-ECG. ECG waveforms and data that are not in the scope of this document include real-time ECG waveform encoding and analysis used for physiological monitors, and intra-cardiac or extra cardiac ECG mapping.
- Standard231 pagesEnglish languagesale 15% off
- Draft232 pagesEnglish languagesale 15% off
The present document contains a stage 1 like description of the interception information in relation to the process of
sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when
Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs
to contain.
Examples of asynchronous messages include email, unified messaging and chat applications.
The definition of handover transport and encoding of HI2 and HI3 is outside the scope of the present document. Refer
to ETSI TS 102 232-1 [3].
The present document is designed to be used where appropriate in conjunction with other deliverables that define the
service specific IRI data formats. The present document aligns with 3GPP TS 33.108 [5], ETSI TS 101 671 [i.3], ETSI
TS 101 331 [1] and ETSI TR 101 944 [i.1].
- Standard57 pagesEnglish languagesale 15% off
- Technical specification57 pagesEnglish languagesale 10% offe-Library read for1 day
This European Standard specifies the data exchange of technical documents such as bill of material, technical drawings and other related technical documents for rolling stock.
- Standard87 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft73 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft73 pagesEnglish languagesale 10% offe-Library read for1 day
The present document contains service-specific details for the handover of the lawfully intercepted PSTN/ISDN
Services (including emulated services such as those defined in ETSI ES 282 002 [i.3]) using packet-based techniques as
defined in ETSI TS 102 232-1 [2].
- Standard13 pagesEnglish languagesale 15% off
- Technical specification13 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session
Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP
MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3].
The present document is consistent with the definition of the Handover Interface, as described in ETSI
TS 102 232-1 [2].
The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and
ETSI TS 101 671 [1].
- Standard28 pagesEnglish languagesale 15% off
- Technical specification28 pagesEnglish languagesale 10% offe-Library read for1 day
The present document contains a stage 1 description of the interception information in relation to the process of binding
a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related
Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain.
The present document includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol
(DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP
address and CC for the intercepted IP packets.
The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present
document. For the handover interface is referred to ETSI TS 102 232-1 [2].
- Standard56 pagesEnglish languagesale 15% off
- Technical specification56 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies an approach for the handover of the lawfully-intercepted information that is defined in
the two standards: 3GPP TS 33.108 [3] and 3GPP TS 33.128 [6]. The present document uses the handover techniques
defined in ETSI TS 102 232-1 [2]. In this way, the present document allows additional services to be delivered through
a common interface.
3GPP TS 33.108
The scope of the present document includes the handover of lawfully-intercepted information from the following parts
of 3GPP TS 33.108 [3]:
• Intercept Related Information (IRI) and the Content of Communication (CC) from the mobile circuit-switched
domain (3GPP TS 33.108 [3], clause 5).
• IRI and CC from the mobile packet-switched domain (3GPP TS 33.108 [3], clause 6).
• IRI and CC from the multi-media domain (3GPP TS 33.108 [3], clause 7).
• IRI and CC from the EPS domain (3GPP TS 33.108 [3], clause 10).
• IRI and CC from the IMS Conference domain (3GPP TS 33.108 [3], clause 11).
• IRI and CC from the IMS-based VoIP domain (3GPP TS 33.108 [3], clause 12).
• IRI from the Proximity Services domain (3GPP TS 33.108 [3], clause 13).
• IRI and CC from the Group Communication System Enablers domain (3GPP TS 33.108 [3], clause 14).
The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [3].
3GPP TS 33.128
The scope of the present document includes the handover of lawfully-intercepted information in accordance with 3GPP TS 33.128 [6].
- Standard19 pagesEnglish languagesale 15% off
- Technical specification19 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks.
The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the
service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI
TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI
TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns
with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI
TS 101 331 [i.9] and ETSI TR 101 944 [i.4].
For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override
or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4].
For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document
and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.
- Standard62 pagesEnglish languagesale 15% off
- Technical specification62 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies Lawful Interception for an Access Provider that has access to layer 2 session
information and that is not required to have layer 3 information. In this case, the focus of Lawful Interception (LI) for IP
Network Access is on the portion of the network, commonly referred to as "layer 2 interception", that facilitates
subscriber access to the Public IP network.
The present document describes the LI at the interception domain of the access network.
The present document contains:
• a stage 1 description of the Lawful Interception service;
• a stage 2 description of the information flows between the functional entities (including the information
elements involved) and triggering events; and
• a stage 3 description of the protocol and procedures to be used in mapping from stage 2 information flows and
elements to Intercept Related Information (IRI) and Content of Communication (CC).
The present document is consistent with the definition of the Handover Interface, as described in ETSI
TS 102 232-1 [2].
NOTE 1: Layer 3 interception is described in ETSI TS 102 232-3 [12].
NOTE 2: Layer 2 interception is not applicable to the PS domain of the GSM/UMTS networks (ETSI
TS 123 060 [15]).
- Standard29 pagesEnglish languagesale 15% off
- Technical specification29 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a data model and encoding rules for the use of radio frequency identification (RFID) tags for items appropriate for the needs of all types of libraries (including national, academic, public, corporate, special, and school libraries). The rules for encoding a subset of data elements taken from the total set of data elements defined in ISO 28560-1 are based on ISO/IEC 15962, which uses an object identifier structure to identify data elements. This document defines the technical characteristics required to encode the data elements defined in ISO 28560-1 according to ISO/IEC 15962. These subsets of data elements can be different on different items in the same library. The encoding rules also enable the optional data to be organized on the RFID tag in any sequence. In addition, the encoding rules provide for flexible encoding of variable length and variable format data. This document provides essential standards-based information about RFID in libraries. A source of additional information about implementation issues is provided in Annex A.
- Standard43 pagesEnglish languagesale 15% off
- Draft43 pagesEnglish languagesale 15% off
- Draft43 pagesEnglish languagesale 15% off
This document specifies an information model representing the quality control of the manufacturing process of traditional Chinese medicinal products by defining a set of domain constraints of sanctioned characteristics, each composed of a relationship. It is applicable to the quality supervision and management of manufacturing process of Chinese materia medica. Japanese KAMPO medicine is outside the scope of this document.
- Technical specification10 pagesEnglish languagesale 15% off
- Draft10 pagesEnglish languagesale 15% off
- Draft10 pagesEnglish languagesale 15% off