D4.1 Online Repository of existing standards and
Transcription
D4.1 Online Repository of existing standards and
AALIANCE2 D4.1 Online Repository of Standards - Snapshot Project acronym: AALIANCE2 Project title: Next Generation European Ambient Assisted Living Innovation Alliance Grant agreement no.: 288705 Starting date: 1st November 2011 Ending date: 31st October 2013 D4.1 Online Repository of existing standards and certifications in AAL and related areas for the R&D community – snapshot WP related to the Deliverable: WP4 Nature O Dissemination Level PU Version V1.0 Author(s): Lars Rölker-Denker, Marco Eichelberg (OFFIS) Filippo Cavallo, Michela Aquilano (SSSA) John Barry (Tunstall) Harald Klaus (Deutsche Telekom AG) Michael Obach (Tecnalia) Maude Luhern (AGE Platform) Gerard van Glabbeek (ZuidZorg) Project Partners Contributing OFFIS, SSSA, Tun, DT, Tec, AGE, Zui Contractual Date of Delivery 12/2012 Actual Date of Delivery 12/2012 V1.0 2013-01-15 Page 1 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Document History Version Date Type of editing Editorial V0.1 2012-12-31 Initial list of standards online All partners V0.2 2013-01-07 Document draft Lars Rölker-Denker V0.3 2013-01-14 All reviews done. Snapshot created All partners; Lars Rölker-Denker V1.0 2013-01-15 Final document Lars Rölker-Denker Additional editors OFFIS: Axel Helmer, Illia Kadachevitch, Myriam Lipprandt, Frerk Müller, Michael Onken, Enno-Edzard Steen, Andreas Thiel SSSA: Laura Fiorini, Alessandra Moschetti Tecnalia: Ander Izquierdo Valdueza Deliverable Summary Deliverable D4.1 provides an overview of current standards in technology related to Ambient Assisted Living (AAL). This report is a snapshot copy dated 2013-01-14 of the Wiki-based online repository in which this information is maintained. This report will be used as a basis for the 1st workshop on standards and certification in AAL. The work on standardisation in AALIANCE has shown that there are gaps in the standardisation landscape in specific domains related to AAL. As a first step AALIANCE2 collected relevant European and international standards and regulations in the field of AAL. This work partly is based on former national activities such as the Interoperability working group of the German BMBF / VDE Innovation Partnership AAL conducted by the WP4 leader OFFIS. The next step in AALIANCE2 WP4 will be the 1 st workshop on standards and certification in AAL. The online repository will be made available to all workshops participants in order to perform a detailed external review of the collection of standards. The workshop itself will aim at the discussion on future needs in terms of new standards, certification programmes and organisational structures for promoting interoperability in the AAL sector. Afterwards the final collection of standards will be made available to the community. A feedback channel will be established to allow for comments and contributions. V1.0 2013-01-15 Page 2 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Table of Contents 1.Networks and Buses........................................................................................5 1.1.Physical Networks.....................................................................................5 1.1.1General cabling systems.....................................................................5 1.1.2Power line Communication (PLC)......................................................14 1.2.Human Body Communication.................................................................25 1.3.Home Automation Field Buses................................................................27 1.3.1Fieldbuses In General........................................................................27 1.3.2Cable-based Home Automation Field Buses......................................36 1.3.3Wireless Home Automation Field Buses............................................55 1.4.Wireless Protocols for Mobile Applications..............................................61 1.5.(Wireless) Personal Area Networks.........................................................76 1.5.1Bluetooth .........................................................................................80 1.5.2ZigBee...............................................................................................83 2.Communication Protocols..............................................................................88 2.1.1General Purpose Protocols................................................................91 2.1.2Ad-hoc Networks.............................................................................131 2.1.3Medical Devices..............................................................................133 2.1.4Home Appliances............................................................................147 2.1.5Smart Metering...............................................................................156 3.File Formats and Persistent Data Structures...............................................171 3.1.General Purpose...................................................................................171 3.1.1Image formats.................................................................................171 3.1.2Video formats..................................................................................176 3.1.3Audio formats..................................................................................195 3.1.4Document formats..........................................................................204 3.1.5Other structured formats................................................................213 3.2.Medical ................................................................................................214 3.2.1ECG File Formats.............................................................................222 3.3.Character Sets......................................................................................224 4.Terminologies and Semantics......................................................................232 4.1.Languages for Knowledge Representation...........................................232 4.2.Electrotechnical Terminology...............................................................237 4.3.Medical Terminology.............................................................................240 4.4.Home Automation Terminology............................................................255 4.5.Building Information Modelling.............................................................259 5.Runtime Environments................................................................................279 6.Integration Profiles......................................................................................291 7.Software Infrastructure for AAL...................................................................294 7.1.Agent-based Systems...........................................................................295 7.2.Service Oriented Architectures.............................................................299 7.3.Event Driven Architectures...................................................................304 7.4.Universal Remote Console (URC)..........................................................306 8.Personal Health Records..............................................................................309 V1.0 2013-01-15 Page 3 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 9.Sensors & Actuators....................................................................................336 9.1.Safety ..................................................................................................337 9.2.Safety for non-industrial robots............................................................362 9.3.Electromagnetic compatibility..............................................................363 10.User Interfaces..........................................................................................382 11.Specifications and standards for operator models....................................402 11.1.Quality management systems in general...........................................402 11.2.Quality management on the health sector.........................................408 11.3.Quality management systems for AAL................................................413 11.4.Standards for quality and risk management of medical devices........415 11.5.Other relevant standards and certifications.......................................418 11.5.1Quality management facility management...................................418 11.5.2Other.............................................................................................419 12.Health Informatics.....................................................................................420 13.Localization................................................................................................436 13.1.Localization and Navigation................................................................436 13.2.Interoperability of location-based applications and services..............441 14.Privacy and Security..................................................................................447 14.1.Data protection specifications............................................................447 14.2.Alarm systems....................................................................................458 15.Ambient Intelligence..................................................................................466 16.Robots/ Robotics........................................................................................480 17.Smart Home..............................................................................................488 V1.0 2013-01-15 Page 4 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 1. Networks and Buses 1.1. Physical Networks 1.1.1 General cabling systems EN 50173 Profile Reference Name Categories ICS Abstract EN 50173 EN 50173: Information technology - Generic cabling systems Networks and Buses; Physical Networks; General cabling systems; EN 33.040.50 - Lines, connections and circuits Structured cabling is building or campus telecommunications cabling infrastructure that consists of a number of standardized smaller elements (hence structured) called subsystems. EN 50173 describes specifications for these generic cabling systems. Current Version see Standard Parts below Other editions AAL Relevance As AAL homes may contain structured cabling systems or may be part of larger structured cabling systems EN 50173 is an essential standard. Available from see Standard Parts below Standard Parts Standard EN 50173-1:2011 EN 50173-2:2007 EN 50173-3:2007 EN 50173-4:2007 EN 50173-4:2007/A2:2012 EN 50173-5:2007 EN 50173-5:2007/A2:2012 prEN 50173-6:2012 V1.0 Title Information technology - Generic cabling systems - Part 1: General requirements Information technology - Generic cabling systems - Part 2: Office premises Information technology - Generic cabling systems - Part 3: Industrial premises Information technology - Generic cabling systems - Part 4: Homes Information technology - Generic cabling systems - Part 4: Homes Information technology - Generic cabling systems - Part 5: Data centres Information technology - Generic cabling systems - Part 5: Data centres Information technology - Generic cabling systems - Part 6: 2013-01-15 Page 5 of 490 AALIANCE2 CLC/TR 50173-99-3:2012 D4.1 Online Repository of Standards - Snapshot Distributed building services Information technology - Generic cabling systems - Part 99-3: Home cabling infrastructures up to 50 m in length to support simultaneous and non simultaneous provision of applications Description EN 50173-1:2011 specifies: • a) the structure and configuration of the backbone cabling subsystems of generic cabling systems within the types of premises defined by the other standards in the EN 50173 series; • b) channel performance requirements in support of the standards in the EN 50173 series; • c) link performance requirements in support of the standards in the EN 50173 series; • d) backbone cabling reference implementations in support of the standards in the EN 50173 series; • e) component performance requirements in support of the standards in the EN 50173 series. EN 50173-4:2007 specifies a generic cabling for three groups of applications in homes: Information and Communications Technologies (ICT), Broadcast and Communications Technologies (BCT), and Commands, Controls and Communications in Buildings (CCCB). It is intended to guide installations in new buildings or refurbishments, and also applies where cabling is installed to support only one or two of the three application groups listed above. A generic cabling infrastructure is specified based upon balanced cabling and / or coaxial cabling. ICT channels specified in this standard include optical fibre, but the wider use of fibre optical cabling in a home is for further study. The three groups of applications may also be supported by different types of cabling, which may be subject to other standards. For example, ISO/IEC 11801 specifies generic cabling for ICT applications in general for the office environment. While the cabling structure and reference implementations are matched to the home environment in this standard, the channel performances specified for ICT are identical to those specified in ISO/IEC 11801. Because this standard is designed to cover the three major groups, the cabling system may be installed prior to the selection of specific applications. The home may contain one or more buildings (e.g. farm) or may be within a building which contains more than one home (e.g. one home in a multi-dwelling building). The campus or backbone cabling connecting individual homes is built according to the relevant standard (for instance ISO/IEC 11801, IEC 60728). Generic cabling realised according to this standard: a) allows deployment of a wide range of applications without changes to the fixed cabling infrastructure; b) provides a platform to support moves, adds and changes of connectivity. This standard provides users with an application-independent generic cabling for applications run in homes, and a flexible cabling scheme such that changes are both easy and economical; it provides building professionals (for example, architects) with guidance for accommodating cabling before specific requirements are known, i.e. in the initial planning either for construction or refurbishment; and gives users, designers, and manufacturers of application-specific cabling systems advice on interfacing. It specifies relevant requirements for suppliers of V1.0 2013-01-15 Page 6 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot cabling components and installers of cabling, and a distribution system for service providers' services. It supports current products and provides a basis for future product development in home electronic systems. This draft Technical Report CLC/TR 50173-99-3:2012 describes a grading system applicable to telecommunications cabling within homes which provides a range of implementation solutions to support both non-simultaneous and simultaneous provision of applications incorporating: • a) a cabling structure in accordance with, but less complex than that of, EN 50173-4 and with defined connecting hardware pin assignment for certain applications; • b) components meeting or exceeding the requirements of EN 50173-4; • c) shorter cabling channels than those specified in EN 50173-4. prEN 50173-6:2012 specifies generic cabling that supports a wide range of communication services within premises that comprise single or multiple buildings on a campus, many of which require the use of remote powered devices including telecommunications, energy management, environmental control, personnel management, personal information and alarms. The distribution of these services is provided to locations (e.g. for wireless access points, remote powered devices and building management systems) other than those specified in premises-specific standards in EN 50173 series by means of either: • a) an overlay structure and configuration to that specified within EN 50173 series or • b) a stand-alone structure and configuration. It covers balanced cabling and optical fibre cabling. This European Standard is based upon and references the requirements of EN 50173-1, and in addition specifies implementation options. [Source: CENELEC] External links • http://en.wikipedia.org/w/index.php?title=Structured_cabling&oldid=515644545 : information on Structured Cabling more ISO/IEC 11801 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEC 11801 ISO/IEC 11801:2002: Information technology – Generic cabling for customer premises Networks and Buses; Physical Networks; General cabling systems; ISO; IEC 35.200: Interface and interconnection equipment ISO/IEC 11801 specifies general-purpose telecommunication cabling systems (structured cabling) that are suitable for a wide range of applications (analogue and ISDN telephony, various data 2013-01-15 Page 7 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot communication standards, building control systems, factory automation). (from Wikipedia) Current Version 2002 Other editions ISO/IEC 11801:2002/Cor 1:2002 ISO/IEC 11801:2002/Amd 2:2010/Cor 1:2010 ISO/IEC 11801:2002/Amd 1:2008/Cor 1:2008 ISO/IEC 11801:2002/Amd 1:2008 ISO/IEC 11801:2002/Amd 2:2010 ISO/IEC 11801:2002/Cor 2:2002 ISO/IEC 11801:2002/Cor 3:2008 AAL Relevance This standard specifies general-purpose telecommunication cabling systems, which maybe useful in larger living quarters. Available from http://www.iso.org/iso/catalogue_detail?csnumber=36491 Description International standard ISO/IEC 11801 specifies general-purpose telecommunication cabling systems (structured cabling) that are suitable for a wide range of applications (analogue and ISDN telephony, various data communication standards, building control systems, factory automation). It covers both balanced copper cabling and optical fibre cabling. The standard was designed for use within commercial premises that may consist of either a single building or of multiple buildings on a campus. It was optimized for premises that span up to 3 km, up to 1 km² office space, with between 50 and 50,000 persons, but can also be applied for installations outside this range. A corresponding standard for small-office/home-office (SOHO) environments is ISO/IEC 15018, which also covers 1.2 GHz links for cable and satellite TV applications. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=ISO/IEC_11801&oldid=502652669 • http://www.iso.org/iso/catalogue_detail?csnumber=36491 ISO/IEC 14543 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEC 14543 Information technology – Home electronic system (HES) architecture Networks and Buses; Physical Networks; General cabling systems; ISO; IEC; 35.240.99: IT applications in other fields 35.200: Interface and interconnection equipment Home Electronic System (HES) standards describe the architecture of home control systems including communication and interoperability aspects. This International Standard specifies the general features as 2013-01-15 Page 8 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot well as the basic functional structure of an HES. Three different classes of HES are defined. Class 1 has transport capabilities for telecontrol applications only. Class 2 includes Class 1, but also supports switched medium bandwidth data channels. Class 3 includes Classes 1 and 2 and in addition supports high bandwidth switched data channels. (from ISO) Current Version see Standard Parts below Other editions EN 50090 AAL Relevance This standard specifies Home Electronic Systems (HES) for home control systems which may be used in AAL scenarios for communication and interoperability. Available from see Standard Parts below Standard Parts Standard ISO/IEC 14543-2-1:2006 ISO/IEC 14543-3-1:2006 ISO/IEC 14543-3-2:2006 ISO/IEC 14543-3-3:2007 ISO/IEC 14543-3-4:2007 ISO/IEC 14543-3-5:2007 ISO/IEC 14543-3-6:2007 ISO/IEC 14543-3-7:2007 ISO/IEC 14543-3-10:2012 V1.0 Title Information technology - Home Electronic Systems (HES) Architecture – Part 2-1: Introduction and device modularity Information technology – Home Electronic Systems (HES) Architecture – Part 3-1: Communication layers – Application layer for network based control of HES Class 1 Information technology – Home Electronic Systems (HES) Architecture – Part 3-2: Communication layers – Transport, network and general parts of data link layer for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-3: User process for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-4: System management – Management procedures for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-5: Media and media dependent layers – Power line for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-6: Media and media dependent layers – Network based on HES Class 1, twisted pair Information technology – Home electronic system (HES) architecture – Part 3-7: Media and media dependent layers – Radio frequency for network based control of HES Class 1 Information technology – Home Electronic Systems (HES) – Part 3-10: Wireless Short-Packet (WSP) protocol optimized for energy harvesting – Architecture and lower layer protocols 2013-01-15 Page 9 of 490 AALIANCE2 ISO/IEC TR 14543-4:2002 ISO/IEC 14543-4-1:2008 ISO/IEC 14543-4-2:2008 ISO/IEC 14543-5-1:2010 ISO/IEC 14543-5-3:2012 ISO/IEC 14543-5-4:2010 ISO/IEC 14543-5-5:2012 ISO/IEC 14543-5-6:2012 ISO/IEC 14543-5-21:2012 ISO/IEC 14543-5-22:2010 D4.1 Online Repository of Standards - Snapshot Information technology – Home Electronic System (HES) architecture – Part 4: Home and building automation in a mixed-use building Information technology – Home electronic system (HES) architecture – Part 4-1: Communication layers – Application layer for network enhanced control devices of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 4-2: Communication layers – Transport, network and general parts of data link layer for network enhanced control devices of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 5-1: Intelligent grouping and resource sharing for Class 2 and Class 3 – Core protocol Information technology – Home electronic system (HES) architecture – Part 5-3: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Basic application Information technology – Home electronic system (HES) architecture – Part 5-4: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Device validation Information technology – Home electronic system (HES) architecture – Part 5-5: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Device type Information technology – Home electronic system (HES) architecture – Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Part 5-6: Service type Information technology – Home electronic system (HES) architecture – Part 5-21: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Application profile – AV profile Information technology – Home electronic system (HES) architecture – Part 5-22: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Application profile – File profile Description Various electrically controlled devices are used in homes and similar environments for many different applications. Examples of such applications are: lighting, heating, food preparation, washing, energy management, water control, fire alarms, blinds control, different forms of security control and entertainment (audio and video). An overview of such applications is given in the “Catalogue of Applications of the HES” (see Informative reference). When several such devices are able to interwork via a common internal network (in this document called a home network), the resulting total system is called a home control system. When a home control system follows all the specifications in the ISO/IEC HES Standards, it is called a Home Electronic System (HES). V1.0 2013-01-15 Page 10 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Three different classes of HES are defined. Class 1 has transport capabilities for telecontrol applications only. Class 2 includes Class 1, but also supports switched medium bandwidth data channels. Class 3 includes Classes 1 and 2 and in addition supports high bandwidth switched data channels. A home network may be based on one or more different media (for example power line, balanced cables, infra-red or radio) and may also be connected to outside networks (for example telephone, cable television, power and alarm networks). An implementation of the Home Electronic System will typically be assembled by a consumer, one application at a time, starting from single applications like lighting control, security control or audio and video control, to develop eventually into an integrated multiapplication system. The cost of adding an application depends on whether rewiring of the house is needed or whether existing cables and prefitted ducts can be used. Hence the HES standards and supplementary technical reports will also give guidance to architects and builders as well as to users on how to share such resources. Lifetime and innovation cycles vary between one device and another and between devices and networks. To make it possible to add and to change existing devices as well as to enlarge and to upgrade the home network keeping the existing devices, several stable interfaces, the Universal Interface (UI) and the Process Interfaces (PIs) are defined between the home network and the devices. The PIs are meant for simple devices not requiring the full implementation of the HES application protocol. By using these interfaces a manufacturer can design a device both to meet his specific marketing objectives and to give the option to integrate that special device into a multi-application Home Electronic System. This added value allows the user to take advantage of synergy between different applications. To allow manufacturers to implement cheaper devices/network combinations, an HES conformance type B is defined. In this case a device connects directly to the medium without showing the UI or a PI. These devices will, however, be medium dependent and do not have the advantages of devices with full HES conformance (type A conformance where the devices include the Universal Interface). [Source: ISO/IEC TR 14543-1, withdrawn Technical Report] External links • http://webstore.iec.ch/p-preview/info_isoiec14543-1%7Bed1.0%7Den.pdf Technical Report, but still good introduction) (Withdrawn ISO/IEC 14763 Profile Reference Name Categories ICS V1.0 ISO/IEC 14763 ISO/IEC 14763: Information technology - Implementation and operation of customer premises cabling Networks and Buses; Physical Networks; General cabling systems; ISO; IEC 35.200: Interface and interconnection equipment 2013-01-15 Page 11 of 490 AALIANCE2 Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot ISO/IEC 14763-2:2012(E) specifies requirements for the planning, installation and operation of cabling and cabling infrastructures (including cabling, pathways, spaces, earthing and bonding) in support of generic cabling standards and associated documents. see Standard Parts below As AAL scenarios need cabling systems ISO/IEC 14763 offers needed requirements for all steps of the implementation process. see Standard Parts below Standard Parts Standard ISO/IEC 14763-2 ed1.0 Title Information technology - Implementation and operation of customer premises cabling - Part 2: Planning and installation ISO/IEC/TR 14763-2-1 ed1.0 Information technology - Implementation and operation of customer premises cabling - Part 2-1: Planning and installation - Identifiers within administration systems ISO/IEC 14763-3 ed1.1 Consol. Information technology - Implementation and operation with am1 of customer premises cabling - Part 3: Testing of optical fibre cabling Description ISO/IEC 14763-2:2012(E) specifies requirements for the planning, installation and operation of cabling and cabling infrastructures (including cabling, pathways, spaces, earthing and bonding) in support of generic cabling standards and associated documents. The following aspects are addressed: • specification of the installation, • quality assurance, • installation planning, • installation practice, • documentation, • administration, • testing, • inspection, • operation, • maintenance and repair. The requirements of Clauses 5 to 14 of this standard are premises-independent and may be amended by the requirements of premises-specific Annexes. This first edition supersedes Clauses 11 and 12 of ISO/IEC 11801, published in 2002, replaces ISO/IEC V1.0 2013-01-15 Page 12 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 14763-1, published in 1999, its Amendment 1 (2004), ISO/IEC TR 14763-2, published in 2000, ISO/IEC 18010, published in 2002, and its Amendment 1 (2005) and constitutes a technical revision. It includes the following significant technical changes with respect to the previous edition: In addition to the supersession of parts of earlier standards and the incorporation of other standards, this standard provides much greater detail in all aspects of planning and installation with respect to ISO/IEC/TR 14763-2 and provides clearly differentiated and directed requirements and recommendations. ISO/IEC 14763-2-1:2011(E) contains requirements and recommendations for identification of cabling infrastructure elements to support ISO/IEC 14763-2 and equivalent standards. The symbols and object codes specified in this Technical Report are primarily based on IEC 81346 1 and IEC 81346-2. ISO/IEC 14763-3:2006+A1:2011 specifies systems and methods for the inspection and testing of optical fibre cabling designed in accordance with ISO/IEC 11801 or equivalent standards. The test methods refer to existing standards-based procedures where they exist. It replaces ISO/IEC TR 14763-3, first edition, published in 2000, and constitutes a technical revision. It incorporates innovations and recent developments including guidance in the proper use of uni-directional and bi-directional OTDR testing, the three-jumper method as default test method, fibre end-face inspection and criteria for scratches, return loss values for SC and non-SC connectors and the normative use of reference connectors. However, the most substantial change is the application of the 2 parameters which are used to determine the two repeatable multimode launch conditions “modal power distribution and “coupled power ratio. This consolidated version of ISO/IEC 14763-3 consists of the first edition (2006) and its amendment 1 (2009). It bears the edition number 1.1. The technical content is therefore identical to the base edition and its amendment and has been prepared for user convenience. A vertical line in the margin shows where the base publication has been modified by amendment 1. Additions and deletions are displayed in red, with deletions being struck through. This consolidated version consists of the first edition (2006) and its amendment 1 (2009). Therefore, no need to order amendment in addition to this publication. [Source: ISO] ISO/IEC 15018 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEC 15018 ISO/IEC 15018:2004: Information technology – Generic cabling for homes Networks and Buses; Physical Networks; General cabling systems; ISO; IEC 35.200: Interface and interconnection equipment ISO/IEC 15018:2004 is a corresponding standard for smalloffice/home-office (SOHO) environments to ISO/IEC 11801, which also 2013-01-15 Page 13 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot covers 1.2 GHz links for cable and satellite TV applications. 2004 ISO/IEC 15018:2004/Amd 1:2009 http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=37860 Description ISO/IEC 15018:2004 specifies a generic cabling for three groups of applications in homes: Information and Communications Technologies (ICT), Broadcast and Communications Technologies (BCT), and Commands, Controls and Communications in Buildings (CCCB). It is intended to guide installations in new buildings or refurbishments, and also applies where cabling is installed to support only one or two of the three application groups listed above. A generic cabling infrastructure is specified based upon balanced cabling and / or coaxial cabling. ICT channels specified in this standard include optical fibre, but the wider use of fibre optical cabling in a home is for further study. The three groups of applications may also be supported by different types of cabling, which may be subject to other International Standards. For example, ISO/IE cabling for ICT applications in general for the office environment. While the cabling structure and reference implementations are matched to the home environment in ISO/IEC 15018:2004, the channel performances specified for ICT are identical to those specified in ISO/IEC 11801. [Source: ISO] External links • http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=37860 1.1.2 Power line Communication (PLC) EN 50065 Profile Reference Name Categories ICS Abstract V1.0 EN 50065 EN 50065: Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz Networks and Buses; Physical Networks; Power line Communication; EN 33.040.30 - Switching and signalling systems This standard applies to electrical equipment using signals in the frequency range 3 kHz to 148,5 kHz to transmit information on low voltage electrical systems, either on the public electricity distribution network or within installations in consumers’ premises. EN 50065 offers five frequency bands (sorted by frequency in ascending order): unlabelled (3 to 9 kHz), A (9 to 95 kHz), B (95 to 125 kHz), C (125 to 140 kHz) and D (140 to 148,5 kHz). The first two are reserved for 2013-01-15 Page 14 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot applications by electricity suppliers, the others are available for private communication applications within the house. Under ideal conditions data transfer rates of 300 kbit/s are achievable. For higher date transfer rates one frequency band from 1,6 MHz to 13 MHz can be used indoor and from 15 MHz to 30 MHz outdoor.(from Standard Act) Current Version see Standard Parts below Other editions AAL Relevance Frequency bands from B to D maybe used for connecting of and communicating between AAL devices depended on power supply via sockets. Available from see Standard Parts below Standard Parts Standard EN 50065-1:2011 EN 50065-2-1:2003 EN 50065-21:2003/A1:2005 EN 50065-2-2:2003 EN 50065-22:2003/A1:2005 EN 50065-2-3:2003 EN 50065-23:2003/A1:2005 V1.0 Title Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 1: General requirements, frequency bands and electromagnetic disturbances Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-1: Immunity requirements for mains communications equipment and systems operating in the range of frequencies 95 kHz to 148,5 kHz and intended for use in residential, commercial and light industrial environments Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-1: Immunity requirements for mains communications equipment and systems operating in the range of frequencies 95 kHz to 148,5 kHz and intended for use in residential, commercial and light industrial environments Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-2: Immunity requirements for mains communications equipment and systems operating in the range of frequencies 95 kHz to 148,5 kHz and intended for use in industrial environments Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-2: Immunity requirements for mains communications equipment and systems operating in the range of frequencies 95 kHz to 148,5 kHz and intended for use in industrial environments Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-3: Immunity requirements for mains communications equipment and systems operating in the range of frequencies 3 kHz to 95 kHz and intended for use by electricity suppliers and distributors Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 2-3: Immunity requirements for mains communications equipment and systems operating in the 2013-01-15 Page 15 of 490 AALIANCE2 EN 50065-4-1:2001 EN 50065-4-2:2001 EN 50065-42:2001/A1:2003 EN 50065-42:2001/A2:2005 EN 50065-4-3:2003 EN 50065-4-4:2003 EN 50065-4-5:2003 EN 50065-4-6:2004 EN 50065-4-7:2005 EN 50065-7:2001 D4.1 Online Repository of Standards - Snapshot range of frequencies 3 kHz to 95 kHz and intended for use by electricity suppliers and distributors Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 4-1: Low voltage decoupling filters - Generic specification Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz and 1,6 MHz to 30 MHz - Part 4-2: Low voltage decoupling filters - Safety requirements Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz and 1,6 MHz to 30 MHz - Part 4-2: Low voltage decoupling filters - Safety requirements Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz and 1,6 MHz to 30 MHz - Part 4-2: Low voltage decoupling filters - Safety requirements Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 4-3: Low voltage decoupling filter Incoming filter Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 4-4: Low voltage decoupling filter Impedance filter Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 4-5: Low voltage decoupling filter Segmentation filter Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 4-6: Low voltage decoupling filters - Phase coupler Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz and 1,6 MHz to 30 MHz - Part 4-7: Portable low voltage decoupling filters - Safety requirements Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz - Part 7: Equipment impedance Description This standard applies to electrical equipment using signals in the frequency range 3 kHz to 148,5 kHz to transmit information on low voltage electrical systems, either on the public electricity distribution network or within installations in consumers’ premises. It specifies the frequency bands allocated to the different applications, limits for the terminal output voltage in the operating band and limits for conducted and radiated disturbance. It also gives the methods of measurement. It does not specify the modulation methods, the coding methods or functional features (except those for the prevention of mutual interference). Environmental requirements and tests are not included. NOTE 1 Compliance with this standard does not imply permission to establish communication with locations outside the consumer’s installation or with other consumers through the public electricity distribution network where this would not otherwise be allowed. The object of the standard is to limit mutual influence between transmission V1.0 2013-01-15 Page 16 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot equipment in electrical installations and between such equipment and other equipment. In addition this standard is intended to limit interference caused by signal transmission equipment to sensitive electronic equipment. However, complete freedom from such interference cannot be assured. NOTE 2 Designers should consider signalling systems in conformance with this standard when determining immunity for electrical equipment. [Source: CENELEC] EN 50412 Profile Reference Name EN 50412 EN 50412: Power line communication apparatus and systems used in low-voltage installations in the frequency range 1,6 MHz to 30 MHz Categories Networks and Buses; Physical Networks; Power line communication; EN ICS 33.120.20 - Wires and symmetrical cables 97.120 - Automatic controls for household use Abstract EN 50412 describes requirements for apparatus and systems using power line communication, especially to avoid/reduce interferences between different devices. Current Version see Standard Parts below Other editions AAL Relevance As AAL devices may be using power line communication EN 50412 should be considered to avoid/ reduce interferences with other devices. Available from see Standard Parts below Standard Parts Standard CLC/TR 50412-1:2007 EN 50412-2-1:2005 prEN 50412-4:2012 Title Power line communication apparatus and systems used in lowvoltage installations in the frequency range 1,6 MHz to 30 MHz - Part 1: General Power line communication apparatus and systems used in lowvoltage installations in the frequency range 1,6 MHz to 30 MHz - Part 2-1: Residential, commercial and industrial environment Immunity requirements Power line communication apparatus and systems used in lowvoltage installations in the frequency range 1,6 MHz to 30 MHz - Part 4: Low rate wide band services (LRWBS) operating between 2 MHz and 4 MHz - Channel allocations Description This European Standard applies to electrical equipment using signals in the [2-4 MHz] V1.0 2013-01-15 Page 17 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot frequency range to transmit information on low voltage electrical systems/networks within installations in consumers’ premises for residential, commercial and light industrial environments. The purpose of this European Standard is to describe a mechanism to limit mutual interferences between equipments operating in the [2-4 MHz] frequency band and to specify the way systems share the same band. It does not specify the signal modulation methods nor the coding methods or functional features (except those preventing mutual interference in the same band). Applications complying with this coexistence standard may offer low rate (lower than 1 Mb/s) services in home and building automation, street lighting control. This European Standard covers typical applications such as energy efficiency, real-time displays of metering information, general command and control, home automation. This European Standard does not cover high rate communication (higher than 1 Mb/s) applications such as Video or Internet networking. This European Standard does not cover Output Voltage Levels. [Source: CENELEC] Homeplug Profile Reference Name Categories Homeplug Homeplug (HomePlug Powerline Alliance) Networks and Buses; Physical Networks; Power line communication; HomePlug; Communication Network; Home Appliances; IEEE ICS Abstract HomePlug is an industry Alliance comprised of industry leaders at each level of the value chain - from Technology to Services & Content. The Alliance's mission is to enable and promote rapid availability, adoption and implementation of cost effective, interoperable and standardsbased home power line networks and products. HomePlug is the family name for various power line communications specifications that support networking over existing home electrical wiring. Baseline technology for IEEE 1901 Current Version HomePlug 1.0, HomePlug AV2, HomePlug Green PHY, HomePlug Access BPL Other editions IEEE 1901-2010: Standard for Broadband over Power Line Networks: Medium Access Control and Physical Layer Specifications AAL Relevance Homeplug maybe used for connecting of and communicating between AAL devices depended on power supply via sockets. Available from https://www.homeplug.org/home/ Description The HomePlug Powerline Alliance is a trade association of electronics manufacturers, service providers, and retailers that establishes standards for, and tests members' devices for compliance to, the various power line communication technologies known as HomePlug. V1.0 2013-01-15 Page 18 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot The alliance developed standards for applications such as in-home distribution of TV, gaming and Internet access. It also developed a specification for smart power meters and in-home communications between electric systems and appliances. HomePlug is the family name for various power line communications specifications that support networking over existing home electrical wiring. Several specifications exist under the HomePlug moniker, with each offering unique performance capabilities and coexistence or compatibility with other HomePlug specifications. HomePlug 1.0 The first HomePlug specification, HomePlug 1.0, provides a peak PHY-rate of 14 Mbit/s. It was first introduced in June, 2001 and has since been replaced by HomePlug AV. On May 28, 2008 Telecommunications Industry Association (TIA) incorporated HomePlug 1.0 powerline technology into the newly published TIA-1113 international standard. TIA-1113 defines modem operations on user-premises electrical wiring. The new standard is the world's first multi-megabit power line communications standard approved by an American National Standards Institute (ANSI)-accredited organization. HomePlug 1.0 Turbo adapters comply with the HomePlug 1.0 specification but employ a faster, proprietary mode that increases the peak PHY-rate to 85 Mbit/s. HomePlug AV The HomePlug AV specification, which was introduced in August 2005, provides sufficient bandwidth for applications such as HDTV and VoIP. HomePlug AV offers a peak data rate of 200 Mbs at the physical layer, and about 80 Mbs at the MAC layer. HomePlug AV devices are required to coexist, and optionally to interoperate, with HomePlug 1.0 devices. Utilizing adaptive modulation on up to 1155 OFDM sub-carriers, turbo convolution codes for error correction, two-level MAC framing with ARQ, and other techniques, HomePlug AV can achieve near the theoretical maximum bandwidth across a given transmission path. For security reasons, the specification includes key distribution techniques and the use of 128 bit AES encryption. Furthermore, the specification's adaptive techniques present inherent obstacles to eavesdropping and cyber attacks. Some Qualcomm Atheros-based adapters comply with the HomePlug AV specification but employ a proprietary extension that increases the PHY-rate to 500 Mbit/s primarily by using a wider spectrum. HomePlug AV2 The HomePlug AV2 specification was introduced in January 2012, it is interoperable with HomePlug AV and HomePlug GreenPHY devices and is IEEE 1901 standard compliant. It features gigabit-class PHY-rate, support for MIMO PHY, repeating functionalities and power saving modes. HomePlug Green PHY The HomePlug Green PHY specification is a subset of HomePlug AV that is intended for use in the smart grid. It has peak rates of 10 Mbit/s and is designed to go into smart meters and smaller appliances such as HVAC thermostats, home appliances and plug-in electric vehicles so that data can be shared over a home network and with the power utility. High capacity broadband is not needed for such applications; the most important requirements are low power and cost, reliable communication, and compact size. V1.0 2013-01-15 Page 19 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot GreenPHY uses up to 75% less energy than AV.[11] The HomePlug Powerline Alliance worked with utilities and meter manufacturers to develop this 690-page specification. HomePlug Green PHY devices are required to be fully interoperable with devices based on HomePlug AV, HomePlug AV2 and IEEE 1901 specification. HomePlug Access BPL Access Broadband Power Line (BPL) refers to a to-the-home broadband access technology. The HomePlug Alliance formed the HomePlug Access BPL Working Group, whose first charter was to develop the Market Requirements Document (MRD) for a HomePlug Access BPL specification. The Alliance made an open invitation to the BPL industry to participate in the development of or provide input for consideration in the MRD. After several months of collaboration between utilities, ISPs and other BPL industry groups, the MRD was completed in June 2005. HomePlug's work on the Access BPL was subsequently contributed and merged into the IEEE 1901 standard. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/HomePlug_Powerline_Alliance • http://en.wikipedia.org/wiki/HomePlug ISO/IEC DIS 15118 Profile Reference Name ISO/IEC DIS 15118 ISO/IEC DIS 15118: Road vehicles – Vehicle to grid Communication Interface (HomePlug Green PHY) Categories Networks and Buses; Physical Networks; Power line Communication; HomePlug; ISO; IEC; Road vehicles; ICS 43.120: Electric road vehicles Abstract ISO/IEC DIS 15118 describes a communication interface between vehicles and power grid. Current Version see Standard Parts below Other editions AAL Relevance As AAL is expanding from home technology to “everywhere” technology, integration of (electric) vehicles may be useful (localisation, emergency calls). Available from see Standard Parts below Standard Parts Standard ISO/DIS 15118-1 ISO/IEC DIS 15118-2 V1.0 Title Road vehicles – Vehicle to grid communication interface – Part 1: General information and use-case definition Road vehicles – Vehicle to grid communication interface – Part 2: Network and application protocol requirements 2013-01-15 Page 20 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/DIS 15118-3 Road vehicles – Vehicle to grid Communication Interface – Part 3: Physical and data link layer requirements Road vehicles – Vehicle to grid communication interface – Part 4: Network and application protocol conformance test Road vehicles – Vehicle to grid communication interface – Part 5: Physical layer and data link layer conformance test ISO/NP 15118-4 ISO/NP 15118-5 Description The HomePlug Green PHY (HomePlug GP) Specification is a result of an intense standards development effort between leaders in the utility industry and the Green PHY Technical Working Group within the HomePlug Alliance. Developed as a low-cost, low-power adaption of the proven HomePlug AV Specification, HomePlug GP also is compliant with the IEEE P1901-2010TM Standard for Power Line Networks (IEEE1901), HomePlug AV 1.1, and HomePlug AV2. In addition, HomePlug GP will benefit from the huge eco-system of existing HomePlug AV technology solutions and an established third-party and tools for certifying universal interoperability between HomePlug and IEEE P1901 devices. Recently Green PHY has been updated to version Green PHY 1.1 which includes features for the Electric Vehicle (EV) industry including EV to Electric Vehicle Supply Equipment (EVSE) DC battery charging communications, and advanced power management features. [Source: HomePlug] External links • http://www.homeplug.org/tech/homeplug_gp • http://www.homeplug.org/tech/whitepapers/HomePlug_Green_PHY_whitepaper_121003 .pdf • http://www.homeplug.org/tech/whitepapers/HomePlug_GreenPHY_Overview.pdf ITU G.hn Profile Reference Name Categories ICS Abstract V1.0 ITU G.hn ITU (International Telecommunication Union) G.hn Networks and Buses; Physical Networks; Power line Communication; HomePNA; G.hn is the common name for a home network technology family of standards developed under the International Telecommunication Union's Telecommunication Standardization sector (the ITU-T) and promoted by the HomeGrid Forum and several other organizations. The G.hn specification defines networking over power lines, phone lines and coaxial cables with data rates up to 1 Gbit/s. Some 2013-01-15 Page 21 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot recommendations (ITU term for standard) are based on HomePNA. (from Wikipedia) see Standard Parts below ITU G.hn maybe used for connecting of and communicating between AAL devices depended on (already available) power lines and phone lines. see Standard Parts below Standard Parts Standard G.9951 G.9952 G.9953 G.9954 (02/05) G.9954 (01/07) G.9960 G.9961 G.9963 G.9972 G.9970 Title HomePNA 2.0 HomePNA 3.0 HomePNA 3.1 G.hn/HomeGrid G.hn-mimo G.cx G.hnta Description G.hn is a specification for existing-wire home networking. It is a complementary counterpart to Wi-Fi. G.hn targets gigabit per second data rates and operation over three types of legacy home wires: telephone wiring, coaxial cables and power lines. A single G.hn semiconductor device is able to network over any of the supported home wire types. Some benefits of a multi-wire standard are lower equipment development costs and lower deployment costs for service providers (by allowing customer self-install). The majority of devices in which G.hn may become embedded (such as televisions, settop boxes, residential gateways, personal computers or network-attached storage devices) will be AC-powered, so configurations that have at least one power line networking interface are likely to become the most common. This will also facilitate integration with home control and demand side management applications for AC-powered appliances. The ITU-T extended the technology with multiple input, multiple output (MIMO) technology to increase data rates and signalling distance. The work on MIMO for G.hn at ITU-T is under the G.9963 standard. By developing dual mode devices, G.hn proponents believe it can provide an evolution path from other wired home networking technologies such as Multimedia over Coax Alliance (MoCA), HomePNA 3.1 over coax and phone wires (already an ITU standard G.9954), and HomePlug AV, Universal Powerline Association (UPA) and HD-PLC over power line. In February 2009 the key promoters of two of these interfaces united behind the latest version of the standard. G.hn specifies a single Physical Layer based on fast Fourier transform (FFT) orthogonal V1.0 2013-01-15 Page 22 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot frequency-division multiplexing (OFDM) modulation and low-density parity-check code (LDPC) forward error correction (FEC) code. G.hn includes the capability to notch specific frequency bands to avoid interference with amateur radio bands and other licensed radio services. G.hn includes mechanisms to avoid interference with legacy home networking technologies and also with other wireline systems such as VDSL2 or other types of DSL used to access the home. OFDM systems split the transmitted signal into multiple orthogonal sub-carriers. In G.hn each one of the sub-carriers is modulated using QAM. The maximum QAM constellation supported by G.hn is 4096-QAM (12-bit QAM). The G.hn Media Access Control is based on a time division multiple access (TDMA) architecture, in which a “domain master” schedules Transmission Opportunities (TXOPs) that can be used by one or more devices in the “domain”. There are two types of TXOPs: • Contention-Free Transmission Opportunities (CFTXOP), which have a fixed duration and are allocated to a specific pair of transmitter and receiver. CFTXOP are used for implementing TDMA Channel Access for specific applications that require quality of service (QoS) guarantees. • Shared Transmission Opportunities (STXOP), which are shared among multiple devices in the network. STXOP are divided into Time Slots (TS). There are two types of TS: • Contention-Free Time Slots (CFTS), which are used for implementing “implicit” token passing Channel Access. In G.hn, a series of consecutive CFTS is allocated to a number of devices. The allocation is performed by the “domain master” and broadcast to all nodes in the network. There are pre-defined rules that specify which device can transmit after another device has finished using the channel. As all devices know “who is next”, there is no need to explicitly send a “token” between devices. The process of “passing the token” is implicit and ensures that there are no collisions during Channel access. • Contention-Based Time Slots (CBTS), which are used for implementing CSMA/CARP Channel Access. In general, CSMA systems cannot completely avoid collisions, so CBTS are only useful for applications that do not have strict Quality of Service requirements. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=G.hn&oldid=520440574 • http://en.wikipedia.org/w/index.php?title=HomePNA&oldid=518173587 UPB Profile Reference Name Categories V1.0 UPB UPB: Universal powerline bus Networks and Buses; Physical Networks; Power line communication / 2013-01-15 Page 23 of 490 AALIANCE2 ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot HomePlug; 91.140.50 Energy (Including electric energy meters in buildings, emergency electrical supplies, etc. ) Universal powerline bus (or UPB) is a protocol for communication among devices used for home automation. It uses power line wiring for signalling and control. Version 1.4 04/16/07 As AAL devices may be using power line communication UPB is a possible technical solution. http://pulseworx.com/downloads/upb/UPBDescriptionv1.4.pdf Description UPB was developed by PCS Powerline Systems of Northridge, California and released in 1999. Based on the concept of the ubiquitous X10 standard, UPB has an improved transmission rate and higher reliability. While X10 without speciality firewalls has a reported reliability of 70-80%, UPB reportedly has a reliability of more than 99%. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=Universal_powerline_bus&oldid=526173025 • http://pulseworx.com/UPB_.htm X10 Profile Reference Name Categories ICS Abstract X10 X10 Networks and Buses; Physical Networks; Power Line Communication X10 is an international and open industry standard for communication among electronic devices used for home automation (domotics). It primarily uses power line wiring for signalling and control, where the signals involve brief radio frequency bursts representing digital information. A wireless radio based protocol transport is also defined. Current Version Other editions AAL Relevance As AAL devices may be using power line communication X10 is a possible technical solution. Available from - V1.0 2013-01-15 Page 24 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description Household electrical wiring (the same which powers lights and appliances) is used to send digital data between X10 devices. This digital data is encoded onto a 120 kHz carrier which is transmitted as bursts during the relatively quiet zero crossings of the 50 or 60 Hz AC alternating current waveform. One bit is transmitted at each zero crossing. The digital data consists of an address and a command sent from a controller to a controlled device. More advanced controllers can also query equally advanced devices to respond with their status. This status may be as simple as “off” or “on”, or the current dimming level, or even the temperature or other sensor reading. Devices usually plug into the wall where a lamp, television, or other household appliance plugs in; however some built-in controllers are also available for wall switches and ceiling fixtures. The relatively high-frequency carrier frequency carrying the signal cannot pass through a power transformer or across the phases of a multiphase system. For split phase systems, the signal can be passively coupled from phase-to-phase using a passive capacitor, but for three phase systems or where the capacitor provides insufficient coupling, an active X10 repeater can be used. To allow signals to be coupled across phases and still match each phase's zero crossing point, each bit is transmitted three times in each half cycle, offset by 1/6 cycle. It may also be desirable to block X10 signals from leaving the local area so, for example, the X10 controls in one house do not interfere with the X10 controls in a neighbouring house. In this situation, inductive filters can be used to attenuate the X10 signals coming into or going out of the local area. [Source: Wikipedia] External links • ftp://ftp.x10.com/pub/manuals/technicalnote.pdf • http://en.wikipedia.org/w/index.php?title=X10_%28industry_standard %29&oldid=527765643 1.2. Human Body Communication IEC 62779 Profile Reference Name Categories ICS Abstract V1.0 IEC 62779 IEC 62779: Semiconductor devices - Semiconductor interface for human body communication Networks and Buses; Human Body Communication; Robots/ Robotics Human Body Communication (HBC) is a communication technology which utilizes the human body as a means of propagation for the transfer of data at very short range. 2013-01-15 Page 25 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios may contain wearable sensors HBC can be used for data transmission to base stations, stationary actors and other stationary devices. Available from see Standard Parts below Standard Parts Standard IEC 62779-1 Ed.1 IEC 62779-2 Ed.1 Title Semiconductor devices - Semiconductor interface for human body communication - Part 1: General requirements Semiconductor devices - Semiconductor interface for human body communication - Part 2: Characterization of interfacing performances Description Human Body Communication is often described as “the last metre for future communications”: a small distance which holds a myriad of potential future services. The main motivations which push interest towards this technology are basically two: first of all the fact that H.B.C. functions can be used in “hands free” mode, meaning that all you have to do is touch certain objects which have to be enabled or inhibited; for that to happen all the user has to do is wear, in a jacket or trouser pocket, a small gadget, which contains specific qualification codes which propagate on the human body. The second factor is the minuscule energy usage of the technology, in the order of a millionth of a watt, which means there is no biological impact on the user and great operational autonomy of the worn gadget’s battery. The definition of HBC reflects the different technologies which are implemented, each one with its own strengths and weaknesses. The electromagnetic mode is a technology which seems to have found the best balance between cost and performance. What the electromagnetic mode is, is a radio transmitter, of incredibly low power (in the order of one millionth of a watt), which through an appropriately named Skintenna propagates its signal along the surface of the human body so that it doesn’t escape into the surrounding environment. [Source: Telecomitalia.com] External links • http://www.telecomitalia.com/tit/en/innovation/hot-topics/scenarios/Human-BodyCommunication.html V1.0 2013-01-15 Page 26 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 1.3. Home Automation Field Buses 1.3.1 Fieldbuses In General IEC 61158 Profile Reference Name Categories IEC 61158 IEC 61158: Industrial communication networks - Fieldbus specifications Networks and Buses; Home Automation Field Buses; Fieldbuses In General ICS 25.040: Industrial automation systems 25.040.40: Industrial process measurement and control 35.100: Open systems interconnection (OSI) 35.100.20: Data link layer 35.100.70: Application layer 35.110: Networking (including local area networks (LAN), metropolitan area networks (MAN), wide area networks (WAN), etc.) 35.240.50: IT applications in industry (including design automation) Abstract This series of standards defines for the physical, data link and application layer different protocol types for fieldbuses and Ethernet based networks. Current Version see Standard Parts below Other editions AAL Relevance Originally an industry relevant standard IEC 61158 contains basic concepts relevant to AAL like different layers and protocols, fieldbuses and networks based on Ethernet Available from see Standard Parts below Standard Parts Standard IEC/TR 61158-1 ed3.0 IEC 61158-2 ed5.0 IEC 61158-3-1 ed1.0 IEC 61158-3-2 ed1.0 IEC 61158-3-3 ed1.0 IEC 61158-3-4 ed1.0 V1.0 Title Industrial communication networks - Fieldbus specifications Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series Industrial communication networks - Fieldbus specifications Part 2: Physical layer specification and service definition Industrial communication networks - Fieldbus specifications Part 3-1: Data-link layer service definition - Type 1 elements Industrial communication networks - Fieldbus specifications Part 3-2: Data-link layer service definition - Type 2 elements Industrial communication networks - Fieldbus specifications Part 3-3: Data-link layer service definition - Type 3 elements Industrial communication networks - Fieldbus specifications 2013-01-15 Page 27 of 490 AALIANCE2 IEC 61158-3-7 ed1.0 IEC 61158-3-8 ed1.0 IEC 61158-3-11 ed1.0 IEC 61158-3-12 ed2.0 IEC 61158-3-13 ed1.0 IEC 61158-3-14 ed2.0 IEC 61158-3-16 ed1.0 IEC 61158-3-17 ed1.0 IEC 61158-3-18 ed1.0 IEC 61158-3-19 ed2.0 IEC 61158-3-21 ed1.0 IEC 61158-3-22 ed1.0 IEC 61158-4-1 ed1.0 IEC 61158-4-2 ed2.0 IEC 61158-4-3 ed2.0 IEC 61158-4-4 ed1.0 V1.0 D4.1 Online Repository of Standards - Snapshot Part 3-4: Data-link layer service definition - Type 4 elements Industrial communication networks - Fieldbus specifications Part 3-7: Data-link layer service definition - Type 7 elements Industrial communication networks - Fieldbus specifications Part 3-8: Data-link layer service definition - Type 8 elements Industrial communication networks - Fieldbus specifications Part 3-11: Data-link layer service definition - Type 11 elements Industrial communication networks - Fieldbus specifications Part 3-12: Data-link layer service definition - Type 12 elements Industrial communication networks - Fieldbus specifications Part 3-13: Data-link layer service definition - Type 13 elements Industrial communication networks - Fieldbus specifications Part 3-14: Data-link layer service definition - Type 14 elements Industrial communication networks - Fieldbus specifications Part 3-16: Data-link layer service definition - Type 16 elements Industrial communication networks - Fieldbus specifications Part 3-17: Data-link layer service definition - Type 17 elements Industrial communication networks - Fieldbus specifications Part 3-18: Data-link layer service definition - Type 18 elements Industrial communication networks - Fieldbus specifications Part 3-19: Data-link layer service definition - Type 19 elements Industrial communication networks - Fieldbus specifications Part 3-21: Data-link layer service definition - Type 21 elements Industrial communication networks - Fieldbus specifications Part 3-22: Data-link layer service definition - Type 22 elements Industrial communication networks - Fieldbus specifications Part 4-1: Data-link layer protocol specification - Type 1 elements Industrial communication networks - Fieldbus specifications Part 4-2: Application layer protocol specification - Type 2 elements Industrial communication networks - Fieldbus specifications Part 4-3: Data-link layer protocol specification - Type 3 elements Industrial communication networks - Fieldbus specifications 2013-01-15 Page 28 of 490 AALIANCE2 IEC 61158-4-7 ed1.0 IEC 61158-4-8 ed1.0 IEC 61158-4-11 ed2.0 IEC 61158-4-12 ed2.0 IEC 61158-4-13 ed1.0 IEC 61158-4-14 ed2.0 IEC 61158-4-16 ed1.0 IEC 61158-4-17 ed1.0 IEC 61158-4-18 ed2.0 IEC 61158-4-19 ed2.0 IEC 61158-4-21 ed1.0 IEC 61158-4-22 ed1.0 IEC 61158-5-2 ed2.0 IEC 61158-5-3 ed2.0 IEC 61158-5-4 ed1.0 V1.0 D4.1 Online Repository of Standards - Snapshot Part 4-4: Data-link layer protocol specification - Type 4 elements Industrial communication networks - Fieldbus specifications Part 4-7: Data-link layer protocol specification - Type 7 elements Industrial communication networks - Fieldbus specifications Part 4-8: Data-link layer protocol specification - Type 8 elements Industrial communication networks - Fieldbus specifications Part 4-11: Data-link layer protocol specification - Type 11 elements Industrial communication networks - Fieldbus specifications Part 4-12: Data-link layer protocol specification - Type 12 elements Industrial communication networks - Fieldbus specifications Part 4-13: Data-link layer protocol specification - Type 13 elements Industrial communication networks - Fieldbus specifications Part 4-14: Data-link layer protocol specification - Type 14 elements Industrial communication networks - Fieldbus specifications Part 4-16: Data-link layer protocol specification - Type 16 elements Industrial communication networks - Fieldbus specifications Part 4-17: Data-link layer protocol specification - Type 17 elements Industrial communication networks - Fieldbus specifications Part 4-18: Data-link layer protocol specification - Type 18 elements Industrial communication networks - Fieldbus specifications Part 4-19: Data-link layer protocol specification - Type 19 elements Industrial communication networks - Fieldbus specifications Part 4-21: Data-link layer protocol specification - Type 21 elements Industrial communication networks - Fielbus specifications Part 4-22: Data-link layer protocol specification - Type 22 elements Industrial communication networks - Fieldbus specifications Part 5-2: Application layer service definition - Type 2 elements Industrial communication networks - Fieldbus specifications Part 5-3: Application layer service definition - Type 3 elements Industrial communication networks - Fieldbus specifications 2013-01-15 Page 29 of 490 AALIANCE2 IEC 61158-5-5 ed1.0 IEC 61158-5-7 ed1.0 IEC 61158-5-8 ed1.0 IEC 61158-5-9 ed1.0 IEC 61158-5-10 ed2.0 IEC 61158-5-11 ed1.0 IEC 61158-5-12 ed2.0 IEC 61158-5-13 ed1.0 IEC 61158-5-14 ed2.0 IEC 61158-5-15 ed2.0 IEC 61158-5-16 ed1.0 IEC 61158-5-17 ed1.0 IEC 61158-5-18 ed2.0 IEC 61158-5-19 ed2.0 IEC 61158-5-20 ed2.0 V1.0 D4.1 Online Repository of Standards - Snapshot Part 5-4: Application layer service definition - Type 4 elements Industrial communication networks - Fieldbus specifications Part 5-5: Application layer service definition - Type 5 elements Industrial communication networks - Fieldbus specifications Part 5-7: Application layer service definition - Type 7 elements Industrial communication networks - Fieldbus specifications Part 5-8: Application layer service definition - Type 8 elements Industrial communication networks - Fieldbus specifications Part 5-9: Application layer service definition - Type 9 elements Industrial communication networks - Fieldbus specifications Part 5-10: Application layer service definition - Type 10 elements Industrial communication networks - Fieldbus specifications Part 5-11: Application layer service definition - Type 11 elements Industrial communication networks - Fieldbus specifications Part 5-12: Application layer service definition - Type 12 elements Industrial communication networks - Fieldbus specifications Part 5-13: Application layer service definition - Type 13 elements Industrial communication networks - Fieldbus specifications Part 5-14: Application layer service definition - Type 14 elements Industrial communication networks - Fieldbus specifications Part 5-15: Application layer service definition - Type 15 elements Industrial communication networks - Fieldbus specifications Part 5-16: Application layer service definition - Type 16 elements Industrial communication networks - Fieldbus specifications Part 5-17: Application layer service definition - Type 17 elements Industrial communication networks - Fieldbus specifications Part 5-18: Application layer service definition - Type 18 elements Industrial communication networks - Fieldbus specifications Part 5-19: Application layer service definition - Type 19 elements Industrial communication networks - Fieldbus specifications 2013-01-15 Page 30 of 490 AALIANCE2 IEC 61158-5-21 ed1.0 IEC 61158-5-22 ed1.0 IEC 61158-6-2 ed2.0 IEC 61158-6-3 ed2.0 IEC 61158-6-4 ed1.0 IEC 61158-6-5 ed1.0 IEC 61158-6-7 ed1.0 IEC 61158-6-8 ed1.0 IEC 61158-6-9 ed2.0 IEC 61158-6-10 ed2.0 IEC 61158-6-11 ed1.0 IEC 61158-6-12 ed2.0 IEC 61158-6-13 ed1.0 IEC 61158-6-14 ed2.0 IEC 61158-6-15 ed2.0 V1.0 D4.1 Online Repository of Standards - Snapshot Part 5-20: Application layer service definition - Type 20 elements Industrial communication networks - Fieldbus specifications Part 5-21: Application layer service definition - Type 21 elements Industrial communication networks - Fieldbus specifications Part 5-22: Application layer service definition - Type 22 elements Industrial communication networks - Fieldbus specifications Part 6-2: Application layer protocol specification - Type 2 elements Industrial communication networks - Fieldbus specifications Part 6-3: Application layer protocol specification - Type 3 elements Industrial communication networks - Fieldbus specifications Part 6-4: Application layer protocol specification - Type 4 elements Industrial communication networks - Fieldbus specifications Part 6-5: Application layer protocol specification - Type 5 elements Industrial communication networks - Fieldbus specifications Part 6-7: Application layer protocol specification - Type 7 elements Industrial communication networks - Fieldbus specifications Part 6-8: Application layer protocol specification - Type 8 elements Industrial communication networks - Fieldbus specifications Part 6-9: Application layer protocol specification - Type 9 elements Industrial communication networks - Fieldbus specifications Part 6-10: Application layer protocol specification - Type 10 elements Industrial communication networks - Fieldbus specifications Part 6-11: Application layer protocol specification - Type 11 elements Industrial communication networks - Fieldbus specifications Part 6-12: Application layer protocol specification - Type 12 elements Industrial communication networks - Fieldbus specifications Part 6-13: Application layer protocol specification - Type 13 elements Industrial communication networks - Fieldbus specifications Part 6-14: Application layer protocol specification - Type 14 elements Industrial communication networks - Fieldbus specifications 2013-01-15 Page 31 of 490 AALIANCE2 IEC 61158-6-16 ed1.0 IEC 61158-6-17 ed1.0 IEC 61158-6-18 ed2.0 IEC 61158-6-19 ed2.0 IEC 61158-6-20 ed2.0 IEC 61158-6-21 ed1.0 IEC 61158-6-22 ed1.0 D4.1 Online Repository of Standards - Snapshot Part 6-15: Application layer protocol specification - Type 15 elements Industrial communication networks - Fieldbus specifications Part 6-16: Application layer protocol specification - Type 16 elements Industrial communication networks - Fieldbus specifications Part 6-17: Application layer protocol specification - Type 17 elements Industrial communication networks - Fieldbus specifications Part 6-18: Application layer protocol specification - Type 18 elements Industrial communication networks - Fieldbus specifications Part 6-19: Application layer protocol specification - Type 19 elements Industrial communication networks - Fieldbus specifications Part 6-20: Application layer protocol specification - Type 20 elements Industrial communication networks - Fieldbus specifications Part 6-21: Application layer protocol specification - Type 21 elements Industrial communication networks - Fieldbus specifications Part 6-22: Application layer protocol specification - Type 22 elements Description This series of standards defines for the physical, data link and application layer different protocol types for fieldbuses and Ethernet based networks. PROFIBUS is type 3 and PROFINET type 10. IEC 61158-1:2010 presents an overview and guidance for the IEC 61158 series by: • explaining the structure and content of the IEC 61158 series; • relating the structure of the IEC 61158 series to the ISO/IEC 7498 OSI Basic Reference Model; • showing the logical structure of the IEC 61784 series; • showing how to use parts of the IEC 61158 series in combination with the IEC 61784 series; • providing explanations of some aspects of the IEC 61158 series that are common to the parts of the IEC 61158-5 series. [Source: IEC] External links • http://en.wikipedia.org/w/index.php?title=Fieldbus&oldid=526316322 V1.0 2013-01-15 Page 32 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IEC 61784 Profile Reference Name Categories ICS Abstract IEC 61784 IEC 61784: Industrial communication networks - Profiles Networks and Buses; Home Automation Field Buses; Fieldbuses in general 25.040.40: Industrial process measurement and control 35.100.05: Multilayer applications (including International Standardized Profiles) 35.100.20: Data link layer 35.240.50: IT applications in industry (including design automation) This standard contains several Communication Profile Families (CPF), which specify one or more communication profiles see Standard Parts below Current Version Other editions AAL Relevance Originally an industry relevant standard IEC 61784 contains communication profiles which may be also relevant to AAL. Available from see Standard Parts below Standard Parts Standard IEC 61784-1 ed3.0 IEC 61784-2 ed2.0 IEC 61784-3 ed2.0 IEC 61784-3-1 ed2.0 IEC 61784-3-2 ed2.0 IEC 61784-3-3 ed2.0 IEC 61784-3-6 ed2.0 IEC 61784-3-8 ed1.0 IEC 61784-3-12 ed1.0 IEC 61784-3-13 ed1.0 V1.0 Title Industrial communication networks - Profiles - Part 1: Fieldbus profiles Industrial communication networks - Profiles - Part 2: Additional fieldbus profiles for real-time networks based on ISO/IEC 8802-3 Industrial communication networks - Profiles - Part 3: Functional safety fieldbuses - General rules and profile definitions Industrial communication networks - Profiles - Part 3-1: Functional safety fieldbuses - Additional specifications for CPF 1 Industrial communication networks - Profiles - Part 3-2: Functional safety fieldbuses - Additional specifications for CPF 2 Industrial communication networks - Profiles - Part 3-3: Functional safety fieldbuses - Additional specifications for CPF 3 Industrial communication networks - Profiles - Part 3-6: Functional safety fieldbuses - Additional specifications for CPF 6 Industrial communication networks - Profiles - Part 3-8: Functional safety fieldbuses - Additional specifications for CPF 8 Industrial communication networks - Profiles - Part 3-12: Functional safety fieldbuses - Additional specifications for CPF 12 Industrial communication networks - Profiles - Part 3-13: 2013-01-15 Page 33 of 490 AALIANCE2 IEC 61784-3-14 ed1.0 IEC 61784-3-18 ed1.0 IEC 61784-5-2 ed2.0 IEC 61784-5-3 ed2.0 IEC 61784-5-4 ed1.0 IEC 61784-5-6 ed2.0 IEC 61784-5-10 ed2.0 IEC 61784-5-11 ed2.0 IEC 61784-5-12 ed1.0 IEC 61784-5-14 ed1.0 IEC 61784-5-15 ed1.0 D4.1 Online Repository of Standards - Snapshot Functional safety fieldbuses - Additional specifications for CPF 13 Industrial communication networks - Profiles - Part 3-14: Functional safety fieldbuses - Additional specifications for CPF 14 Industrial communication networks - Profiles - Part 3-18: Functional safety fieldbuses - Additional specifications for CPF 18 Industrial communication networks - Profiles - Part 5-2: Installation of fieldbuses - Installation profiles for CPF 2 Industrial communication networks - Profiles - Part 5-3: Installation of fieldbuses - Installation profiles for CPF 3 Industrial communication networks - Profiles - Part 5-4: Installation of fieldbuses - Installation profiles for CPF 4 Industrial communication networks - Profiles - Part 5-6: Installation of fieldbuses - Installation profiles for CPF 6 Industrial communication networks - Profiles - Part 5-10: Installation of fieldbuses - Installation profiles for CPF 10 Industrial communication networks - Profiles - Part 5-11: Installation de fieldbuses - Installation profiles for CPF 11 Industrial communication networks - Profiles - Part 5-12: Installation of fieldbuses - Installation profiles for CPF 12 Industrial communication networks - Profiles - Part 5-14: Installation of fieldbuses - Installation profiles for CPF 14 Industrial communication networks - Profiles - Part 5-15: Installation of fieldbuses - Installation profiles for CPF 15 Description This standard contains several Communication Profile Families (CPF), which specify one or more communication profiles. Such profiles identify, in a strict sense, protocol subsets of the IEC 61158 series via protocol specific communication profiles. The PROFIBUS and PROFINET are always in the CPF 3 section. IEC 61784-1:2010 defines a set of protocol specific communication profiles based primarily on the IEC 61158 series, to be used in the design of devices involved in communications in factory manufacturing and process control. Each profile selects specifications for the communications protocol stack at a device. It contains a minimal set of required services at the application layer and specification of options in intermediate layers defined through references. If no application layer is included, then a minimal set of required services at the Data-link layer is specified. The appropriate references to the protocol specific types are given in each communication profile family or associated profiles. This third edition cancels and replaces the second edition published in 2007. This edition constitutes a technical revision. The main changes with respect to the previous edition are: • update of the dated references to the IEC 61158 series, to IEC 61784-2, to the IEC 61784-3 series, to the IEC 61784-5 series and to IEC 61918 throughout the document; V1.0 2013-01-15 Page 34 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • update of the titles of the referenced documents and references if needed; • update of selection tables for CPF 1, CPF 2, CPF 5 and CPF 8. This bilingual version published in 2011-12, corresponds to the English version published in 2010-07. IEC 61784-2:2010 specifies performance indicators supporting classification schemes for Real-Time Ethernet (RTE) requirements; profiles and related network components based on ISO/IEC 8802-3, IEC 61158 series, and IEC 61784-1; RTE solutions that are able to run in parallel with ISO/IEC 8802-3-based applications. These communication profiles are called Real-Time Ethernet communication profiles. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with respect to the previous edition are: • update of the dated references to the IEC 61158 series, to IEC 61784-1, to the IEC 61784-3 series, to the IEC 61784-5 series and to IEC 61918 throughout the document; • update of selection tables for CPF 2, CPF 3, CPF 11 and CPF 14; • addition of a new profile CP 11/2 in 12.3; • addition of a new profile CP 14/3 in subclause 15.5; • addition of a new Communication Profile Family - CPF 17; • new subclause 3.3.12 (CPF 17 symbols); • new Clause 18 for CPF 17 with one profile; • addition of a new Communication Profile Family - CPF 18; • new subclause 3.3.13 (CPF 18 symbols); • new Clause 19 for CPF 18 with one profile; • specification changes for CPF3; • update of the requirements for all conformance classes; • added precise timing requirements for IP; • updated timing requirements for IO devices; • added precise timing requirements for PTCP; • increasing the amount of synchronized devices in line; • integrating the fast start-up as additional feature. This bilingual version published in 2011-12, corresponds to the English version published in 2010-07. IEC 61784-3:2010 explains some common principles than can be used in the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of IEC 61508 series for functional safety. These principles can be used in various industrial applications such as process control, manufacturing automation and machinery. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with V1.0 2013-01-15 Page 35 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot respect to the previous edition are: • clarifications and additional explanations for requirements, updated references; • updates of definitions and requirements in relation with the new edition of IEC 61508; • addition of a new informative Annex D providing an assessment guideline; • updates in parts for CPF 1, CPF 2, CPF 3, CPF 6 (details provided in the parts); • addition of new parts for CPF 8, CPF 12, CPF 13, CPF 14; • in CPF parts, addition of an annex to provide information about test laboratories for testing and validating conformance of FSCP products. This bilingual version published in 2011-12, corresponds to the English version published in 2010-07. [Source: IEC] External links • http://en.wikipedia.org/wiki/Fieldbus 1.3.2 Cable-based Home Automation Field Buses DigitalSTROM Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from DigitalSTROM DigitalSTROM Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses DigitalSTROM connects electrical devices in a network across the power line and therefore supports features for automatic control. Key feature is a digitalSTROM screw joint implemented in an electrical device as well as the control module with the integrated ditigalSTROMchip. AAL scenarios may use digitalSTROM system components for implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. http://www.digitalstrom.com/ Description digitalSTROM communicates by using the power line which allows an installation of the V1.0 2013-01-15 Page 36 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot system without any new cables. This allows easy retrofitting in existing buildings. The digitalSTROM chip integrated into an electrical device is a slave device. The information to be sent from the chip is modulated on the sinusoidal power line voltage by increasing the effective power on the line for a few micro seconds. Every bus subscriber has its own global unique ID the so called dSID or digitalSTROM ID. This ID is preset by the vendor and not changeable. Every slave gets its own local address by the master in a method similar to DHCP. This address will be used for communication by the slave. For every power line on digtalSTROM master is needed to collect the information from all slaves connected to its power line. This master is placed in the fuse box. digitalSTROM devices are acting as actors and sensors. They are capable of measuring the power line as well as switching or diming the connected devices. External links • http://www.aizo.com/en/ EN 14908 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN 14908 EN 14908: European building automation standard (LON) Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses 35.240.99: IT applications in other fields 35.200: Interface and interconnection equipment The Local Operating Network (LON) is a standard based on field bus principles. It was designed to be a none vertical decentralized bus system for automation features. Within a LON devices are connected and communicate through a bus protocol. Devices connected to this bus are called nodes and are divided into sensors, actors and controllers. see Standard Parts below AAL scenarios may use LON system components for implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. see Standard Parts below Standard Parts Standard ISO/IEC 14908-1:2012 ISO/IEC 14908-2:2012 ISO/IEC 14908-3:2012 V1.0 Title Information technology – Control network protocol – Part 1: Protocol stack Information technology – Control network protocol – Part 2: Twisted pair communication Information technology – Control network protocol – Part 3: 2013-01-15 Page 37 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14908-4:2012 Power line channel specification Information technology – Control network protocol – Part 4: IP communication Description The hardware of LON is based on three 8Bit-processors placed on a chip called Neuron. The first CPU is the media-access-CPU which is capable of controlling the physical connection to the LON network. The second CPU is the network-CPU which codes and decodes the network messages sent and retrieved. The last CPU is the application-CPU containing the application software of the user which represents the “intelligence” of the node. Every Neuron-chip has its own globally unique 48Bit ID (the Neuron-ID) which allows identification of the node within the LON. The communication protocol of this field bus is called LON talk. It defines the layers two to seven of the ISO-OSI reference model. For the physical layer (layer one) are several transceivers such as radio, fibre optic or power line available. From the logical point of view the nodes are communicating by using communication objects which are called Network Variables (NV). To allow communication between several vendors Standard Network Variable Types (SNVT) are defined. A temperature for example is defined as SNVT_temp_p. External links • http://en.wikipedia.org/wiki/Local_Operating_Network EN 50090 Profile Reference Name Categories ICS EN 50090 EN 50090: Home and Building Electronic Systems (HBES) (KNX, former EIB) Network and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses; KNX; EIB 97.120: Automatic controls for household use Abstract EN 50090 is a standard containing technical rules for Home and Building Electronic Systems (HBES). One of the most famous systems developed following EN50090 is KNX/EIB Current Version see Standard Parts below Other editions ISO/IEC 14543 AAL Relevance AAL scenarios may use KNX system components for implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. Available from see Standard Parts below V1.0 2013-01-15 Page 38 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Safety aspects Standard EN 50090-2-2:1996 EN 50090-2-2:1996/A1:2002 EN 50090-2-2:1996/A2:2007 EN 50090-2-3:2005 Title Home and Building Electronic Systems (HBES) - Part 22: System overview - General technical requirements Home and Building Electronic Systems (HBES) - Part 22: System overview - General technical requirements Home and Building Electronic Systems (HBES) - Part 22: System overview - General technical requirements Home and Building Electronic Systems (HBES) - Part 23: System overview - General functional safety requirements for products intended to be integrated in HBES Conformity assessment Standard EN 50090-8:2000 Title Home and Building Electronic Systems (HBES) - Part 8: Conformity assessment of products Cabling Standard EN 50090-9-1:2004 CLC/TR 50090-9-2:2007 Title Home and Building Electronic Systems (HBES) - Part 91: Installation requirements - Generic cabling for HBES Class 1 Twisted Pair Home and Building Electronic Systems (HBES) - Part 92: Installation requirements - Inspection and testing of HBES installation Open Communication System Standard EN 50090-1:2011 EN 50090-3-1:1994 EN 50090-3-2:2004 EN 50090-3-2:2004 EN 50090-3-3:2009 EN 50090-4-1:2004 V1.0 Title Home and Building Electronic Systems (HBES) - Part 1: Standardization structure Home and Building Electronic Systems (HBES) - Part 31: Aspects of application - Introduction to the application structure Home and Building Electronic Systems (HBES) - Part 32: Aspects of application - User process for HBES Class 1 Home and Building Electronic Systems (HBES) - Part 32: Aspects of application - User process for HBES Class 1 Home and Building Electronic Systems (HBES) - Part 33: Aspects of application - HBES Interworking model and common HBES data types Home and Building Electronic Systems (HBES) - Part 41: Media independent layers - Application layer for 2013-01-15 Page 39 of 490 AALIANCE2 EN 50090-4-2:2004 EN 50090-4-3:2007 EN 50090-5-1:2005 EN 50090-5-2:2004 EN 50090-5-3:2006 EN 50090-7-1:2004 D4.1 Online Repository of Standards - Snapshot HBES Class 1 Home and Building Electronic Systems (HBES) - Part 42: Media independent layers - Transport layer, network layer and general parts of data link layer for HBES Class 1 Home and Building Electronic Systems (HBES) - Part 43: Media independent layers - Communication over IP Home and Building Electronic Systems (HBES) - Part 51: Media and media dependent layers - Power line for HBES Class 1 Home and Building Electronic Systems (HBES) - Part 52: Media and media dependent layers - Network based on HBES Class 1, Twisted Pair Home and Building Electronic Systems (HBES) - Part 53: Media and media dependent layers - Radio frequency Home and Building Electronic Systems (HBES) - Part 71: System management - Management procedures Description KNX is a standardized (EN 50090, ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BâtiBUS, and the European Installation Bus (EIB or Instabus). The KNX standard is administered by the KNX Association. The standard is based on the communication stack of EIB but enlarged with the physical layers, configuration modes and application experience of BatiBUS and EHS. KNX defines several physical communication medias: • Twisted pair wiring (inherited from the BatiBUS and EIB Instabus standards) • Power line networking (inherited from EIB and EHS - similar to that used by X10) • Radio (KNX-RF) • Infrared • Ethernet (also known as EIBnet/IP or KNXnet/IP) KNX is designed to be independent of any particular hardware platform. A KNX Device Network can be controlled by anything from an 8-bit microcontroller to a PC, according to the needs of a particular implementation. The most common form of installation is over twisted pair medium. EN 50090 is gradually replaced by EN 50491 but still the basis for KNX. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/KNX_%28standard%29 V1.0 2013-01-15 Page 40 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 50491 Profile Reference Name EN 50491 EN 50491: General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Categories Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses; EN; HBES; Building Automation; BACS; Sensors & Actuators; Safety ICS 97.120 - Automatic controls for household use Abstract The EN 50491 series of standards is entitled “General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS)” and contains requirements for HBES devices including environmental performance, safety, functional safety, EMC, and desing, planning and installation. The EN 50491 series is in the process of replacing the existing EN 50090 series of standards entitled “Home and Building Electronic Systems (HBES)” covering the areas system overview, aspects of application, media independent layers, media and media dependent layers, interfaces, system management, conformity assessment of products and installation requirements. [source: etsi.org] Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios often will use HBES and BACS EN 50491 is an essential standard. Available from see Standard Parts below Standard Parts Standard prEN 50491-1:201X EN 50491-2:2010 EN 50491-3:2009 EN 50491-4-1:2012 V1.0 Title General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 1: General requirements General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 2: Environmental conditions General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 3: Electrical safety requirements General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 4-1: General functional safety requirements for products intended to be integrated in Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) 2013-01-15 Page 41 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 50491-5-1:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-1: EMC requirements, conditions and test set-up prEN 50491-5-2 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-2: EMC requirements for HBES/BACS (Class A) used in residential, commercial and light industry environment EN 50491-5-2:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-2: EMC requirements for HBES/BACS used in residential, commercial and light industry environment EN 50491-5-3:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-3: EMC requirements for HBES/BACS used in industry environment prEN 50491-6-1:2011 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 6-1: HBES installations - Installation and planning CLC/TR 50491-6General requirements for Home and Building Electronic Systems 3:2011 (HBES) and Building Automation and Control Systems (BACS) Part 6-3: HBES installations - Assessment and definition of levels prEN 50491-11 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 11: Smart metering - Application specification - Home display prEN 50491-12 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 12: Smart grid - Application specification - Interface and framework for customer Description EN 50491-3:2009 provides the electrical safety requirements for all devices connected to HBES/BACS. This European Standard is applicable to – operator stations and other human system interface devices, – devices for management functions, – control devices, automation stations and application specific controllers, – field devices, – cabling and interconnection of devices. This European Standard covers the following requirements and compliance criteria: – protection from hazards in the device; – protection from overvoltages on the network; – protection from touch current; – protection from hazards caused by different type of circuits; – protection of the communication wiring from overheating caused by excessive current. EN 50491-4-1:2012 sets the requirements for functional safety for HBES/BACS products and systems, a multi-application bus system where the functions are decentralised, distributed and linked through a common communication process. The requirements may also apply to the distributed functions of any equipment connected in a home or building control system if no specific functional safety standard exists for this equipment or system. The functional safety requirements of this European Standard apply together with the relevant product standard for the device if any. This European Standard is part of the EN V1.0 2013-01-15 Page 42 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 50491 series of standards. This European Standard does not provide functional safety requirements for safety-related systems. EN 50491-5-1:2010 sets the minimum level of EMC performance for HBES/BACS products intended to be connected to an HBES/BACS system. A set of devices connected to perform a stand alone application is not considered to be an HBES/BACS system and therefore are outside the scope of this European Standard. This European Standard provides the general performance requirements and test setups for EMC for all products connected to HBES/BACS. This connection can be wired (e.g. communication cable, power line) or wireless (e.g. radiofrequency, infrared). This European Standard is applicable (but not limited) to – operator stations and other human system interface devices, – devices for management functions, – control devices, automation stations and application specific controllers, – field devices and their interfaces, – cabling and interconnection of devices, – dedicated devices for engineering and commissioning tools for HBES/BACS CLC/TR 50491-6-3:2011 establishes the general rules for assessing HBES installations, according to its complexity and energy performance. This Technical Report applies to – household HBES installation, from and up to the connection point with the utility (i.e. electricity, telecommunications, tele-service, water, gas, security and similar), – HBES installations that include applications related to automation and integrated control of electrical and/or electronic devices, – the networks used for the HBES interconnection regardless of the transmission media used for their communications, – new HBES installations, retrofitting and enlargement of existing installations. [Source: CENELEC] External links • http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740501/01.01.01_60/tr_1051740 501v010101p.pdf EN 62386 Profile Reference Name Categories EN 62386 EN 62386: Digital addressable lighting interface (DALI) Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses; EN ICS 29.140: Lamps and related equipment 29.140.50: Lighting installation systems (including supply track systems) 29.140.99: Other standards related to lamps Abstract 62386 is a technical standard for network-based systems that controls lighting in buildings (from Wikipedia) Current Version see Standard Parts below Other editions AAL Relevance AAL scenarios may use DALI system components for implementing V1.0 2013-01-15 Page 43 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot certain features. TThis can be for example switching the lights on in case of emergency. Available from see Standard Parts below Standard Parts Standard IEC 62386-101 ed1.0 IEC 62386-102 ed1.0 IEC 62386-201 ed1.0 IEC 62386-202 ed1.0 IEC 62386-203 ed1.0 IEC 62386-204 ed1.0 IEC 62386-205 ed1.0 IEC 62386-206 ed1.0 IEC 62386-207 ed1.0 IEC 62386-208 ed1.0 IEC 62386-209 ed1.0 IEC 62386-210 ed1.0 Title Digital addressable lighting interface - Part 101: General requirements - System Digital addressable lighting interface - Part 102: General requirements - Control gear Digital addressable lighting interface - Part 201: Particular requirements for control gear - Fluorescent lamps (device type 0) Digital addressable lighting interface - Part 202: Particular requirements for control gear - Self-contained emergency lighting (device type 1) Digital addressable lighting interface - Part 203: Particular requirements for control gear - Discharge lamps (excluding fluorescent lamps) (device type 2) Digital addressable lighting interface - Part 204: Particular requirements for control gear - Low voltage halogen lamps (device type 3) Digital addressable lighting interface - Part 205: Particular requirements for control gear - Supply voltage controller for incandescent lamps (device type 4) Digital addressable lighting interface - Part 206: Particular requirements for control gear - Conversion from digital signal into d.c. voltage (device type 5) Digital addressable lighting interface - Part 207: Particular requirements for control gear - LED modules (device type 6) Digital addressable lighting interface - Part 208: Particular requirements for control gear - Switching function (device type 7) Digital addressable lighting interface - Part 209: Particular requirements for control gear - Colour control (device type 8) Digital addressable lighting interface - Part 210: Particular requirements for control gear - Sequencer (device type 9) Description Every device implementing the DALI-interface is controllable by is DALI-address. By using a DALI-gateway the status of every DALI-device can be read and set. To every DALI device in one DALI segment up to 16 groups can be added to allow synchronous controlling of several devices. Next to this up to 16 “moods” (predefined levels of intensity) can be set and stored to every device. DALI can be used as a single standalone system with up to 64 devices or as a subsystem by a DALI gateway connecting several subsystems. V1.0 2013-01-15 Page 44 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot DALI uses a serial asynchronous data protocol with a bandwidth of 1200 Bit/s at a voltage of 16V. The standard does not define the lines, plugs or connector blocks. Lines can be used in star, lined up or tree topologies. Not allowed is a circular topology. The maximum of line length is defined at 300m. A terminating resistor is not needed. External links • http://en.wikipedia.org/w/index.php? title=Digital_Addressable_Lighting_Interface&oldid=528463054 • DALI-AG's technical overview of DALI EN ISO 16484 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN ISO 16484 EN ISO 16484: Building automation and control systems (BACnet) Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses 35.240.99: IT applications in other fields (including e-learning) 91.040.01: Buildings in general The international Norm ISO 16484 is regarding Building automation and control systems (BACS) see Standard Parts below AAL scenarios may use BACnet system components for implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. see Standard Parts below Standard Parts Standard ISO 16484-1:2010 ISO 16484-2:2004 ISO 16484-3:2005 ISO 16484-5:2007 ISO 16484-6:2005 Title Building automation and control systems (BACS) – Part 1: Project specification and implementation Building automation and control systems (BACS) – Part 2: Hardware Building automation and control systems (BACS) – Part 3: Functions Building automation and control systems – Part 5: Data communication protocol Building automation and control systems (BACS) – Part 6: Data communication conformance Description The international Norm ISO 16484 is regarding Building automation and control systems V1.0 2013-01-15 Page 45 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot (BACS). It consists of 5 parts. ISO 16484-1:2010 specifies guiding principles for project design and implementation and for the integration of other systems into the building automation and control systems (BACS). ISO 16484-2:2004 specifies the requirements for the hardware to perform the tasks within a building automation and control system (BACS). It provides the terms, definitions and abbreviations for the understanding of ISO 16484-2 and ISO 16484-3. ISO 16484-2:2004 relates only to physical items/devices, i.e. devices for management functions, operator stations and other human system interface devices; controllers, automation stations and application specific controllers; field devices and their interfaces; cabling and interconnection of devices; engineering and commissioning tools. ISO 16484-3:2005 specifies the requirements for the overall functionality and engineering services to achieve building automation and control systems. It defines terms, which shall be used for specifications and it gives guidelines for the functional documentation of project/application specific systems. It provides a sample template for documentation of plant/application specific functions, called BACS points list. ISO 16484-5:2007 defines data communication services and protocols for computer equipment used for monitoring and control of heating, ventilation, air-conditioning and refrigeration (HVAC&R) and other building systems. It defines, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings. ISO 16484-6:2009 defines a standard method for verifying that an implementation of the BACnet protocol provides each capability claimed in its Protocol Implementation Conformance Statement (PICS) in conformance with the BACnet standard. [Source: ISO] External links • http://de.wikipedia.org/wiki/ISO_16484 • http://www.big-eu.org/ ISO/IEC 15045 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEC 15045 ISO/IEC 15045: Information technology – Home Electronic System (HES) gateway Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses; ISO; IEC; 35.200: Interface and interconnection equipment 35.240.99: IT applications in other fields (including e-learning) The Residential Gateway (RG) is a device of the Home Electronic System (HES) that connects home network domains to network 2013-01-15 Page 46 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot domains outside the house Current Version see Standard Parts below Other editions AAL Relevance AAL scenarios may use ISO/IEC 15045 based system components for implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. Available from see Standard Parts below Standard Parts Standard ISO/IEC 15045-1:2004 ISO/IEC 15045-2:2012 Title Information technology – Home Electronic System (HES) gateway – Part 1: A residential gateway model for HES Information technology – Home Electronic System (HES) gateway – Part 2: Modularity and protocol Description The Residential Gateway (RG) is a device of the Home Electronic System (HES) that connects home network domains to network domains outside the house. It supports communications among devices within the premises, and among systems, service providers, operators and users outside the premises. The RG enables service and content providers to deliver services such as entertainment, video and broadband digital streams, monitoring for health care, security and occupancy, home appliance control and preventive maintenance, remote metering, and energy management. The RG specified by this standard does not imply the use of any particular protocol such as IP and it is recognised that many forms of the RG will exist using many types of data such as analogue video and broadband digital streams. ISO/IEC 15045-2:2012(E) specifies a gateway architecture that provides an interconnection between one or more Wide Area Networks (WANs) and one or more Home Area Networks (HANs). It is not needed for a “simple gateway” linking one WAN to one HAN where there is no intention of future expansion. It applies to a “distributed gateway,” and is also referred to in ISO/IEC 15045-1 as the Complex Modular Gateway. Also, it specifies how separate gateways in a single house can interoperate to provide coordinated functions. [Source: ISO] ISO/IEC 14543 Profile Reference Name Categories ICS V1.0 ISO/IEC 14543 Information technology – Home electronic system (HES) architecture Networks and Buses; Physical Networks; General cabling systems; ISO; IEC; 35.240.99: IT applications in other fields 2013-01-15 Page 47 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 35.200: Interface and interconnection equipment Abstract Home Electronic System (HES) standards describe the architecture of home control systems including communication and interoperability aspects. This International Standard specifies the general features as well as the basic functional structure of an HES. Three different classes of HES are defined. Class 1 has transport capabilities for telecontrol applications only. Class 2 includes Class 1, but also supports switched medium bandwidth data channels. Class 3 includes Classes 1 and 2 and in addition supports high bandwidth switched data channels. (from ISO) Current Version see Standard Parts below Other editions EN 50090 AAL Relevance This standard specifies Home Electronic Systems (HES) for home control systems which may be used in AAL scenarios for communication and interoperability. Available from see Standard Parts below Standard Parts Standard ISO/IEC 14543-2-1:2006 ISO/IEC 14543-3-1:2006 ISO/IEC 14543-3-2:2006 ISO/IEC 14543-3-3:2007 ISO/IEC 14543-3-4:2007 ISO/IEC 14543-3-5:2007 ISO/IEC 14543-3-6:2007 ISO/IEC 14543-3-7:2007 ISO/IEC 14543-3-10:2012 V1.0 Title Information technology - Home Electronic Systems (HES) Architecture – Part 2-1: Introduction and device modularity Information technology – Home Electronic Systems (HES) Architecture – Part 3-1: Communication layers – Application layer for network based control of HES Class 1 Information technology – Home Electronic Systems (HES) Architecture – Part 3-2: Communication layers – Transport, network and general parts of data link layer for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-3: User process for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-4: System management – Management procedures for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-5: Media and media dependent layers – Power line for network based control of HES Class 1 Information technology – Home electronic system (HES) architecture – Part 3-6: Media and media dependent layers – Network based on HES Class 1, twisted pair Information technology – Home electronic system (HES) architecture – Part 3-7: Media and media dependent layers – Radio frequency for network based control of HES Class 1 Information technology – Home Electronic Systems (HES) – Part 3-10: Wireless Short-Packet (WSP) protocol optimized 2013-01-15 Page 48 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot for energy harvesting – Architecture and lower layer protocols ISO/IEC TR 14543-4:2002 Information technology – Home Electronic System (HES) architecture – Part 4: Home and building automation in a mixed-use building ISO/IEC 14543-4-1:2008 Information technology – Home electronic system (HES) architecture – Part 4-1: Communication layers – Application layer for network enhanced control devices of HES Class 1 ISO/IEC 14543-4-2:2008 Information technology – Home electronic system (HES) architecture – Part 4-2: Communication layers – Transport, network and general parts of data link layer for network enhanced control devices of HES Class 1 ISO/IEC 14543-5-1:2010 Information technology – Home electronic system (HES) architecture – Part 5-1: Intelligent grouping and resource sharing for Class 2 and Class 3 – Core protocol ISO/IEC 14543-5-3:2012 Information technology – Home electronic system (HES) architecture – Part 5-3: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Basic application ISO/IEC 14543-5-4:2010 Information technology – Home electronic system (HES) architecture – Part 5-4: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Device validation ISO/IEC 14543-5-5:2012 Information technology – Home electronic system (HES) architecture – Part 5-5: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Device type ISO/IEC 14543-5-6:2012 Information technology – Home electronic system (HES) architecture – Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Part 5-6: Service type ISO/IEC 14543-5-21:2012 Information technology – Home electronic system (HES) architecture – Part 5-21: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Application profile – AV profile ISO/IEC 14543-5-22:2010 Information technology – Home electronic system (HES) architecture – Part 5-22: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Application profile – File profile Description Various electrically controlled devices are used in homes and similar environments for many different applications. Examples of such applications are: lighting, heating, food preparation, washing, energy management, water control, fire alarms, blinds control, different forms of security control and entertainment (audio and video). An overview of such applications is given in the “Catalogue of Applications of the HES” (see Informative reference). When several such devices are able to interwork via a common internal network (in this document called a home network), the resulting total system is called a home control system. When a home control system follows all the specifications in the ISO/IEC HES V1.0 2013-01-15 Page 49 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standards, it is called a Home Electronic System (HES). Three different classes of HES are defined. Class 1 has transport capabilities for telecontrol applications only. Class 2 includes Class 1, but also supports switched medium bandwidth data channels. Class 3 includes Classes 1 and 2 and in addition supports high bandwidth switched data channels. A home network may be based on one or more different media (for example power line, balanced cables, infrared or radio) and may also be connected to outside networks (for example telephone, cable television, power and alarm networks). An implementation of the Home Electronic System will typically be assembled by a consumer, one application at a time, starting from single applications like lighting control, security control or audio and video control, to develop eventually into an integrated multiapplication system. The cost of adding an application depends on whether rewiring of the house is needed or whether existing cables and prefitted ducts can be used. Hence the HES standards and supplementary technical reports will also give guidance to architects and builders as well as to users on how to share such resources. Lifetime and innovation cycles vary between one device and another and between devices and networks. To make it possible to add and to change existing devices as well as to enlarge and to upgrade the home network keeping the existing devices, several stable interfaces, the Universal Interface (UI) and the Process Interfaces (PIs) are defined between the home network and the devices. The PIs are meant for simple devices not requiring the full implementation of the HES application protocol. By using these interfaces a manufacturer can design a device both to meet his specific marketing objectives and to give the option to integrate that special device into a multi-application Home Electronic System. This added value allows the user to take advantage of synergy between different applications. To allow manufacturers to implement cheaper devices/network combinations, an HES conformance type B is defined. In this case a device connects directly to the medium without showing the UI or a PI. These devices will, however, be medium dependent and do not have the advantages of devices with full HES conformance (type A conformance where the devices include the Universal Interface). [Source: ISO/IEC TR 14543-1, withdrawn Technical Report] External links • http://webstore.iec.ch/p-preview/info_isoiec14543-1%7Bed1.0%7Den.pdf Technical Report, but still good introduction) (Withdrawn ISO/IEC 15067-3 Profile Reference Name V1.0 ISO/IEC 15067-3 ISO/IEC 15067-3:2012 Information technology – Home electronic system (HES) application model – Part 3: Model of a demand-response energy management system for HES 2013-01-15 Page 50 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses ICS Abstract ISO/IEC 15067-3:2012(E) specifies an energy management model for programs that manage the consumer demand for electricity using a method known as “demand response” Current Version Other editions AAL Relevance ISO/IEC 15067 - 3 describes an energy management model, this is very relevant for AAL Available from http://www.iso.org/iso/catalogue_detail.htm?csnumber=55596 Description ISO/IEC 15067-3:2012(E) specifies an energy management model for programs that manage the consumer demand for electricity using a method known as “demand response”. Three types of demand response are specified in this standard: direct control, local control and distributed control. It replaces ISO/IEC TR 15067-3, first edition, published in 2000, and constitutes a technical revision. It includes the following significant technical changes with respect to the previous edition: • the demand response options have been expanded; • distributed energy resources such as local generation and storage have been included; • the terminology for demand response has been aligned with smart grid. [Source: ISO] ISO/IEC CD 29104 Profile Reference Name ISO/IEC CD 29104 ISO/IEC CD 29104: Information technology – Centralized Management Protocol (CMP) for Ubiquitous Home Network Services Categories Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses ICS 35.110: Networking (including local area networks (LAN), metropolitan area networks (MAN), wide area networks (WAN), etc.) 35.200: Interface and interconnection equipment 35.240.99: IT applications in other fields (including e-learning) Abstract The goal of ISO/IEC CD 29104 is to provide a standardized interface between Home Network Management Server (HOMS) and Residential Gateway installed in multiple premises, wherein companies providing a network or a service through the standardized residential gateways can manage various residential gateways through HOMS. Current Version see Standard Parts below V1.0 2013-01-15 Page 51 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance Thus AAL scenarios may include external services CMP offers an approach to integrate the services into the Home Network. Available from see Standard Parts below Standard Parts Standard ISO/IEC CD 29104-1 ISO/IEC CD 29104-2 ISO/IEC CD 29104-3 Title Information technology – Centralized Management Protocol (CMP) for ubiquitous home network services – Part 1: Remote management of residential gateways Information technology - Centralized Management Protocol (CMP) for Ubiquitous Home Network Services – Part 2: Remote Management of Application Servers Information technology - Centralized Management Protocol (CMP) for Ubiquitous Home Network Services – Part 3: Remote Management of User Terminals Description Home Network is an information infrastructure that connects all the home appliances and the server groups located outside the home (See ISO/IEC 15045-1) and thus can provide Home Automation services, Care services, Security services, Entertainment services, Telemetry services, and more. These services can be described as follows: • Home Automation Services provide control and monitoring of all the home appliances; • Care Services provide Health Care services and Pet Care services; • Security Services provide safe life at home by using security door, security windows, and Web cameras. • Entertainment Services provide the residents of the home with joyful life by using Audio, TV, PC, etc.; • Telemetry Services provide Automatic Meter Reading (AMR) services including the current and statistical usages of electricity, gas, and water consumptions. These services provide the residents of the networked homes with chances of living safe, convenient, and rich life. Because of these features of home network services, the home network is spread all over the world as time goes by. It is important to note, however, that, as the number of home network subscribers increases, those home network services may not be available when a networked home appliance is out of order. Moreover, servers located in the Web may not allow immediate trouble shooting of home appliances as well as real-time software upgrade. For these reasons a standardized architecture for centralized home network management servers is needed. Figure 1 shows the home network infrastructure specified by ISO/IEC 29104 series that allows the home network users to entertain and manage the various home network services that are provided in real time. These services are still available even when the users are outside of the home by using Web-PC or mobile terminals. Home Network Management Server (HOMS) is the server located in the Web that can provide the capability of controlling the networked home V1.0 2013-01-15 Page 52 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot appliances as well as software upgrade of Residential Gateway (RG) devices in real time, as shown in Figure 1. Figure 1 – CMP architecture based on HOMS The CMP architecture defines a centralized server, called the Home Network Management Server (HOMS), to process residential gateway registration requests and event messages using HOMS, as illustrated in Figure 1. HOMS communicates with each residential gateway, application server, and user interface agent via three protocols specified in the CMP standard: • CMP Part 1 specifies an interface protocol called HOMS Residential Gateway Interface Protocol (HRIP) between the HOMS and a residential gateway. The residential gateway provides the connection between an external access network and an internal home network so that HOMS can send requests and receive operation messages. • CMP Part 2 specifies an interface protocol called HOMS Application Server Interface Protocol (HAIP) between HOMS and Application Servers. • CMP Part 3 specifies a third interface protocol called HOMS Users Interface Protocol (HUIP) between HOMS and Users Application Clients (user interfaces). The CMP architecture that is needed for providing various home network services consists of HOMS, Residential Gateway (RG), Networked Home Devices, Application Servers located in the Web and User Application Clients. Some functionalities of these equipments are described as follows: • HOMS • User Web/WAP Page Process • Remote Control Server: Process Interfaced with Residential Gateways • User DB Management Process • Security Process • O&M (Operation and Management) • Residential Gateway • A gateway that can control all the networked appliances in the home • Networked Home Devices V1.0 2013-01-15 Page 53 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Controllable home appliances networked all together including RG • Application Service Server for the provisioning of various services • ASP Server • SMS Server • LBS Server • Trouble Shooting Server • Local ISP Server • User Application Client Group • Application Management Client • Application User Client The goal of this standard is to provide a standardized interface between HOMS and Residential Gateway installed in multiple premises, wherein companies providing a network or a service through the standardized residential gateways can manage various residential gateways through HOMS. Device manufacturers who develop residential gateways conforming to this standard will be able to manage various residential gateways without the need for changes in management application S/W. This will result in the reduction of cost required for device development. Further, a service provider and a network provider can directly install various services desired by service users through the residential gateway owned by the service user by using the standard interface provided by the residential gateway. While the CMP based on SOAP (see ISO/IEC 29363) describes a home device remote control interface by using a Web Service Description Language (WSDL) as specified in ISO/IEC 25437, the remote management scheme of multiple RGs and home appliances networked in the premises can be generic by adopting Remote Procedure Call (RPC) methods as specified in Broadband Forum TR-069. The RPC method-based remote management mechanism is good for providing scalability in the sense that direct remote management of end user devices by the remote management system is possible. On the other hand, the remote management mechanism based on the HRIP proxied by the standardized RG is also a good approach that can provide a level of degree of freedom in implementing the Residential Gateways with extra parameters to be specified in this specification. These additional parameters of Residential Gateways are defined in Annex C of TR-069. The CMP includes remote management and control of home networked devices via cellular phones or any user terminals, which is considered as most distinguishing among others. Some of the use cases are presented, and the ubiquitous home network services shall be implemented in such a way that they are given to customers in real time wherever they locate. • Home security/control service: Digital appliances and devices including door lock, window, and gas valves are monitored and controlled. If there are any urgent events, they are notified to home owners on the move as well as at home via cellular phones. In addition, monitoring camera can send the image of living room for the event checkout. V1.0 2013-01-15 Page 54 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Care service: The services like health-care, pet care are offered, and the status of the elderly people or pets can be monitored by other family members regardless of their position and time. • Shop security/control service: The similar services for homes are applied to shops. • Entertainment service: The independent service providers can provide the users with elearning and VOD services through PCs and cellular phones. • Telemetry service: The automatic meter readings of electricity, gas and tap water are provided for cost-saving and accounting purposes. Home network server and RGs perform several categories of functions using CMP to support the customer use cases presented above. The CMP protocol is also used for the purpose of O&M of the services and devices. As can be seen from the use cases of CMP in the area of Home Network services, the intent of this standard is to control home networking devices including residential gateways as well as to manage services delivery in order to provide telephone operators with a new business model as a potential growth engine. Therefore, the CMP standard will be a good technology to be used when Telecommunication Companies, System Operators, and Network Operators want to open a new home network market by applying the capability of controlling and managing home appliances, residential gateways, and application servers via any type of user terminals including cellular phones. [Source: from SC25 document, see external link] External links • http://hes-standards.org/doc/SC25_WG1_N1388.doc 1.3.3 Wireless Home Automation Field Buses ISO/IEC 14543-3-10:2012 (EnOcean) Profile Reference Name Categories ICS Abstract V1.0 ISO/IEC 14543-3-10:2012 ISO/IEC 14543-3-10:2012: Information technology – Home Electronic Systems (HES) – Part 3-10: Wireless Short-Packet (WSP) protocol optimized for energy harvesting – Architecture and lower layer protocols (EnOcean) Networks and Buses; Home Automation Field Buses; Wireless Home Automation Field Buses 35.240.99: IT applications in other fields 35.200: Interface and interconnection equipment The EnOcean technology is an energy harvesting wireless technology used primarily in building automation systems; but is also applied to other applications in industry, transportation, logistics and smart homes. 2013-01-15 Page 55 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version 2012 Other editions AAL Relevance As most AAL technologies are intended to be retrofittable ISO/IEC 14543-3-10:2012 (EnOcean) offers wireless and energy harvesting solutions. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=59865 Description ISO/IEC 14543-3-10:2012(E) specifies a wireless protocol for low-powered devices such as energy harvested devices in a home environment. This wireless protocol is specifically designed to keep the energy consumption of such sensors and switches extremely low. The WSP protocol system consists of two and optionally three types of components that are specified in this standard. These are the transmitter, the receiver and optionally the repeater. Repeaters are needed when the transmitter and the receiver are located in such a way that no good direct communication between them can be established. [Source: ISO] Modules based on EnOcean technology combine micro energy converters with ultra low power electronics and enable wireless communications between batteryless wireless sensors, switches, controllers and gateways. In March 2012, the EnOcean wireless standard was ratified as the international standard ISO/IEC 14543-3-10, which is optimized for wireless solutions with ultra-low power consumption and energy harvesting.[1] The standard covers the OSI (Open Systems Interconnection) layers 1-3 which are the physical, data link and networking layers. The energy harvesting wireless modules are manufactured and marketed by the company EnOcean which is based in Oberhaching, Germany. EnOcean offers its technology and licenses for the patented features within the EnOcean Alliance framework. [Source: Wikipedia] External links • http://www.enocean.com/en/home/ • http://en.wikipedia.org/w/index.php?title=EnOcean&oldid=521847641 ISO/IEC 18000-7:2004 (DASH7) Profile Reference Name Categories ICS V1.0 ISO/IEC 18000-7:2004 ISO/IEC 18000-7:2004: Information technology – Radio frequency identification for item management – Part 7: Parameters for active air interface communications at 433 MHz (DASH7) Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses 35.040: Character sets and information coding (including coding of 2013-01-15 Page 56 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot audio, picture, multimedia and hypermedia information, IT security techniques, encryption, bar coding, electronic signatures, etc.) Abstract DASH7 is an open source wireless sensor networking standard for wireless sensor networking, which operates in the 433 MHz unlicensed ISM band. Current Version Other editions AAL Relevance DASH7 can be important to several AAL scenarios allowing wireless identification of a person or object and therefore also location. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=37978 Description ISO/IEC 18000-7:2004 defines the air interface for radio-frequency identification (RFID) devices operating as an active RF Tag in the 433 MHz band used in item management applications. Its purpose is to provide a common technical specification for RFID devices that may be used by ISO committees developing RFID application standards. This standard is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. ISO/IEC 180007:2004 defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum power, spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and where appropriate operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. ISO/IEC 180007:2004 further defines the communications protocol used in the air interface. [Source: ISO] External links • http://www.dash7.org/ INSTEON Profile Reference Name Categories INSTEON INSTEON Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses ICS Abstract INSTEON uses both radio frequency signals and the home's existing electrical wiring to talk to each other Current Version Other editions AAL Relevance AAL scenarios may use INSTEON system components for V1.0 2013-01-15 Page 57 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot implementing certain features. This can be for example a decision support system based on activity recognition derived by the usage of electrical devices. Available from http://www.insteon.net/ Description INSTEON uses both radio frequency signals and the home's existing electrical wiring to talk to each other. Every message is confirmed as it is received, and if any errors are detected, the message is automatically resent. Unlike most other mesh networks, INSTEON's “mesh” network has every device acting as a repeater – receiving and sending every message to all other devices on the network. So instead of stressing the network by adding more INSTEON devices, you actually strengthen it. Other mesh networks use router tables, and only those products involved in routing the signal act as repeaters – creating a less reliable network. One command is sent to all devices simultaneously for instant, elegant scene control. With no central controller or networking setup required, setting up your INSTEON network is a simple plug and tap to link one INSTEON product to another. Specifications: Network Topology • Dual band (RF and Power line) • Peer-to-peer • Mesh topology • Unsupervised (no routing tables) Protocol • Simulcast hopping for instant scenes • Statelink messages for backwards and forwards compatibility • All devices are two-way repeaters • Hop counts optimized for every device to device connection • Valid hop counts 0,1,2 and 3 • Error detection • Automatic Error correction Device Installation • Plug-in • Wire-in • Battery operated Security V1.0 2013-01-15 Page 58 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Tap-tap physical possession • Encrypted message payload Frequencies • Power line: 131KHz • RF (US): 915KHz • RF (Europe): 868KHz • RF (Australia, New Zealand): 921KHz Capacities • Maximum devices per network: 16,777,216 • Maximum devices per scene: Limited only memory • Maximum scenes per device: 256 Patents: INSTEON is protected under US and international patents issued and pending • Australia: 2009251115, 2009233636, 2009233635, 2005317202 • Brazil: pending • Canada: pending • China:101917215 • Europe: pending • Hong Kong:1146984 • India: pending • Israel: pending • Japan: 5114206 • Korea: 10-0910994, 10-0910993, 10-0910992 • Malaysia: pending • Mexico: 298433 • New Zealand: 556068 • Singapore: 133643 • Taiwan: I311419 • Thailand: pending • USA: 8081649, 7345998, 6970072, others pending [Source: insteon.net] External links http://en.wikipedia.org/wiki/Insteon V1.0 2013-01-15 Page 59 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ITU-T G.9959 (Z-Wave) Profile Reference Name ITU-T G.9959 ITU-T G.9959: Short range narrow-band digital radiocommunication transceivers - PHY and MAC layer specifications (Z-Wave) Categories Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses ICS Abstract Z-Wave is a wireless communications protocol designed for home automation, specifically to remotely control applications in residential and light commercial environments. The technology uses a low-power RF radio embedded or retrofitted into home electronics devices and systems, such as lighting, home access control, entertainment systems and household appliances. [Source: Wikipedia] Current Version Other editions AAL Relevance AAL scenarios may use wireless communication for home automation like Z-Wave as technical basis. Available from http://www.itu.int/rec/T-REC-G.9959/en Description Z-Wave communicates using a low-power wireless technology designed specifically for remote control applications. The Z-Wave wireless protocol is optimized for reliable, lowlatency communication of small data packets, unlike Wi-Fi and other IEEE 802.11-based wireless LAN systems that are designed primarily for high-bandwidth data flow. Z-Wave operates in the sub-gigahertz frequency range, around 900 MHz. This band competes with some cordless telephones and other consumer electronics devices, but avoids interference with Wi-Fi and other systems that operate on the crowded 2.4 GHz band. ZWave is designed to be easily embedded in consumer electronics products, including battery operated devices such as remote controls, smoke alarms and security sensors. ZWave was developed by a Danish startup called Zen-Sys that was acquired by Sigma Designs in 2008. Z-Wave is currently supported by over 160 manufacturers worldwide and appears in a broad range of consumer products in the U.S., Europe and Asia. The standard itself is not open and is available only to Sigma-Designs customers under non-disclosure agreement. All these product share the Z-Wave transceiver chip that is supplied by Sigma Designs and Mitsumi. Some Z-Wave product vendors have embraced the open source and hobbyist communities. Z-Wave is a proprietary wireless protocol oriented to the residential control and automation market. Conceptually, Z-Wave is intended to provide a simple yet reliable method to wirelessly control lights and appliances in your house. To meet these design parameters, Zensys's or Sigma Designs Z-Wave package includes a chip with a low data rate that V1.0 2013-01-15 Page 60 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot offers reliable data delivery along with simplicity and flexibility. Z-Wave works in industrial, scientific, and medical (ISM) band on the single frequency using frequency-shift keying (FSK) radio. The throughput is 40Kb/sec (9.6Kb/sec using old chips) and suitable for control and sensor applications. Each Z-Wave network may include up to 232 nodes and consists of two sets of nodes: controllers and slave devices. Nodes may be configured to retransmit the message in order to guarantee connectivity in multipath environment of residential house. Average communication distance between two nodes is 100 feet, and with message ability to hop up to four times between nodes, it gives enough coverage for most residential houses. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=Z-Wave&oldid=529142165 1.4. Wireless Protocols for Mobile Applications CoAP Profile Reference Name Categories ICS Abstract CoAP CoAP: Constrained Application Protocol Networks and Buses; Wireless Protocols for Mobile Applications; Constrained Application Protocol (CoAP) is a software protocol intended to be used in very simple electronics devices that allows them to communicate interactively over the Internet. It is particularly targeted for small low power sensors, switches, valves and similar components that need to be controlled or supervised remotely, through standard Internet networks. (from Wikipedia) Current Version Other editions AAL Relevance As AAL scenarios will use small low power devices such as sensors CoAP is a suitable protocol. Available from https://datatracker.ietf.org/doc/draft-ietf-core-coap/?include_text=1 Description The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as 6LoWPAN often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as V1.0 2013-01-15 Page 61 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP easily interfaces with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead and simplicity for constrained environments. [Source: IETF] External links • https://datatracker.ietf.org/doc/draft-ietf-core-coap/ • http://en.wikipedia.org/w/index.php? title=Constrained_Application_Protocol&oldid=522683310 DECT Profile Reference Name Categories ICS Abstract DECT DECT: Digital Enhanced Cordless Telecommunications Networks and Buses; Wireless Protocols for Mobile Applications; Digital Enhanced Cordless Telecommunications (Digital European Cordless Telecommunications), usually known by the acronym DECT, is a digital communication standard, which is primarily used for creating cordless phone systems but also for data transmission. Current Version see Standard Parts below Other editions ETSI EN 300 175 AAL Relevance As DECT devices, especially cordless telephones, are quite common AAL scenarios may use these technologies. Available from see Standard Parts below Standard Parts Standard ETSI EN 300 175-1 V2.2.1 (2008-11) ETSI EN 300 175-2 V2.2.1 (2008-11) ETSI EN 300 175-3 V2.2.1 (2008-11) ETSI EN 300 175-4 V2.2.1 (2008-11) V1.0 Title Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 1: Overview Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 2: Physical Layer (PHL) Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 3: Medium Access Control (MAC) layer Digital Enhanced Cordless Telecommunications 2013-01-15 Page 62 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ETSI EN 300 175-5 V2.2.1 (2008-11) ETSI EN 300 175-6 V2.2.1 (2008-11) ETSI EN 300 175-7 V2.2.1 (2008-11) ETSI EN 300 175-8 V2.2.1 (2009-02) (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK) layer Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 6: Identities and addressing Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security features Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 8: Speech and audio coding and transmission Description Digital Enhanced Cordless Telecommunications (DECT™) is the ETSI standard for shortrange cordless communications, which can be adapted for many applications and can be used over unlicensed frequency allocations world-wide. DECT™ is suited to voice (including PSTN and VoIP telephony), data and networking applications with a range up to 500 metres. DECT™ dominates the cordless residential market and the enterprise PABX (Private Automatic Branch eXchange) market. DECT™ is also used in the Wireless Local Loop to replace copper in the 'last mile' for user premises. [Source: ETSI] External links • http://www.etsi.org/technologies-clusters/technologies/dect? highlight=YToxOntpOjA7czo0OiJkZWN0Ijt9 • http://en.wikipedia.org/w/index.php? title=Digital_Enhanced_Cordless_Telecommunications&oldid=526271236 IEEE 802.11x (WLAN) Profile Reference Name Categories ICS V1.0 IEEE 802.11x IEEE 802.11x (WLAN): IEEE Standard for Information technology– Telecommunications and information exchange between systems Local and metropolitan area networks–Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Networks and Buses; Wireless Protocols for Mobile Applications; 35.110: Networking 2013-01-15 Page 63 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract IEEE 802.11 is a set of standards for implementing wireless local area network (WLAN) computer communication in the 2.4, 3.6 and 5 GHz frequency bands. They are created and maintained by the IEEE LAN/MAN Standards Committee (IEEE 802). The base version of the standard was released in 1997 and has had subsequent amendments. These standards provide the basis for wireless network products using the Wi-Fi brand. [Source: Wikipedia] Current Version see Standard Parts below Other editions ISO/IEC/IEEE 8802-11:2012: Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN medium access control (MAC) and physical layer (PHY) specifications AAL Relevance As most AAL scenarios will use WLAN components, IEEE 802.11x should be taken into account. Available from see Standard Parts below Standard Parts Standard IEEE 802.11-2012 IEEE 802.11aa-2012 IEEE 802.11ad-2012 IEEE 802.11ae-2012 IEEE 802.11u-2011 V1.0 Title 802.11-2012 - IEEE Standard for Information technology– Telecommunications and information exchange between systems Local and metropolitan area networks–Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications 802.11aa-2012 - IEEE Standard for Information technology– Telecommunications and information exchange between systems Local and metropolitan area networks–Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 2: MAC Enhancements for Robust Audio Video Streaming 802.11ad-2012 - IEEE Approved Draft Standard for LAN Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band 802.11ae-2012 - IEEE Standard for Information technology– Telecommunications and information exchange between systems–Local and metropolitan area networks–Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 1: Prioritization of Management Frames 802.11u-2011 - IEEE Standard for Information TechnologyTelecommunications and information exchange between systems-Local and Metropolitan networks-specific requirementsPart II: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 9: Interworking 2013-01-15 Page 64 of 490 AALIANCE2 IEEE ISO/IEC 880211:2005/AMD4 IEEE ISO/IEC 880211:1999/AMD5 IEEE ISO/IEC 880211:2005/AMD6 IEEE 8802-11-2012 D4.1 Online Repository of Standards - Snapshot with External Networks 8802-11:2005/AMD4-2006 - IEEE ISO/IEC 8802-11:2005/AMD4 [IEEE Std 802.11g-2003] Information technology– Local and metropolitan area networks– Part 11: Wireless LAN Medium Access Control (Mac) and Physical Layer (PHY) Specifications– Amendment 4: Further Higher Data Rate Extension in the 2.4 GHz Band 8802-11:2005/AMD5-2006 - IEEE ISO/IEC 8802-11:1999/AMD5 (E) [IEEE Std 802.11h-2003] Information technology– Local and metropolitan area networks– Part 11: Amendment 5: Spectrum and Transmit Power Management Extensions in the 5 GHz band in Europe 8802-11:2005/AMD6-2006 - IEEE ISO/IEC 8802-11:2005/AMD6, Information technology - Telecommunications and information exchange between systems- Local and metropolitan area networks- Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control(MAC) Security Enhancements 8802-11-2012 - IEEE Information technology– Telecommunications and information exchange between systems Local and metropolitan area networks–Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Description The 802.11 family consist of a series of half-duplex over-the-air modulation techniques that use the same basic protocol. The most popular are those defined by the 802.11b and 802.11g protocols, which are amendments to the original standard. 802.11-1997 was the first wireless networking standard, but 802.11b was the first widely accepted one, followed by 802.11g and 802.11n. 802.11n is a new multi-streaming modulation technique. Other standards in the family (c–f, h, j) are service amendments and extensions or corrections to the previous specifications. 802.11b and 802.11g use the 2.4 GHz ISM band, operating in the United States under Part 15 of the US Federal Communications Commission Rules and Regulations. Because of this choice of frequency band, 802.11b and g equipment may occasionally suffer interference from microwave ovens, cordless telephones and Bluetooth devices. 802.11b and 802.11g control their interference and susceptibility to interference by using directsequence spread spectrum (DSSS) and orthogonal frequency-division multiplexing (OFDM) signalling methods, respectively. 802.11a uses the 5 GHz U-NII band, which, for much of the world, offers at least 23 non-overlapping channels rather than the 2.4 GHz ISM frequency band, where adjacent channels overlap. Better or worse performance with higher or lower frequencies (channels) may be realized, depending on the environment. The segment of the radio frequency spectrum used by 802.11 varies between countries. In the US, 802.11a and 802.11g devices may be operated without a license, as allowed in Part 15 of the FCC Rules and Regulations. Frequencies used by channels one through six V1.0 2013-01-15 Page 65 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot of 802.11b and 802.11g fall within the 2.4 GHz amateur radio band. Licensed amateur radio operators may operate 802.11b/g devices under Part 97 of the FCC Rules and Regulations, allowing increased power output but not commercial content or encryption. [Source: Wikipedia] External links • http://grouper.ieee.org/groups/802/11/ • http://en.wikipedia.org/w/index.php?title=IEEE_802.11&oldid=527582658 IPv6 Profile Reference Name Categories ICS Abstract IPv6 IPv6: Internet Protocol Version 6 IETF IPv6 (Internet Protocol version 6) is the latest revision of the Internet Protocol (IP), the primary communications protocol upon which the entire Internet is built. It is intended to replace the older IPv4, which is still employed for the vast majority of Internet traffic as of 2012. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 running out of addresses. [Source: Wikipedia] Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios may contain (many small) devices (i.e. sensors, actors) connected to the Internet IPv6 is inevitable. Available from see Standard Parts below Standard Parts Standard RFC 2460 RFC 4291 RFC 4861 RFC 4862 Title Internet Protocol, Version 6 (IPv6) Specification IP Version 6 Addressing Architecture Neighbour Discovery for IP version 6 (IPv6) IPv6 Stateless Address Autoconfiguration Description Each device on the Internet, such as a computer or mobile telephone, must be assigned an IP address, a number with a certain number of binary digits (each presented by one bit), in order to communicate with other devices. With the ever-increasing number of new devices being connected to the Internet, there is a need for more addresses than IPv4 can accommodate. IPv6 uses 128-bit addresses, allowing for 2128, or approximately 3.4×1038 addresses — more than 7.9×1028 times as many as IPv4, which uses 32-bit addresses. V1.0 2013-01-15 Page 66 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IPv4 allows for only 4,294,967,296 unique addresses worldwide (or fewer than one address per person alive in 2012), but IPv6 allows for around 4.8×1028 addresses per person — a number unlikely to ever run out. However, this means the two protocols are not compatible, complicating the transition to IPv6. IPv6 addresses, as commonly displayed to users, consist of eight groups of four hexadecimal digits separated by colons, for example 2001:0db8:85a3:0042:1000:8a2e:0370:7334. The deployment of IPv6 is accelerating, with a symbolic World IPv6 Launch having taken place on 6 June 2012, in which major internet service providers, especially in countries that had been lagging in IPv6 adoption, deployed IPv6 addresses to portions of their users. Data from Arbor Networks showed a peak of 0.2% of Internet traffic on IPv6 during the launch. As of late November 2012, IPv6 traffic share was reported to be approaching 1%. [Source: Wikipedia] External links • http://datatracker.ietf.org/wg/ipv6/charter/ • http://en.wikipedia.org/w/index.php?title=IPv6&oldid=528973653 ISO/IEC 14443 Profile Reference Name ISO/IEC 14443 ISO/IEC 14443: Identification cards – Contactless integrated circuit cards – Proximity cards Categories Networks and Buses; Wireless Protocols for Mobile Applications; ISO; IEC ICS 35.240.15: Identification cards and related devices Abstract ISO/IEC 14443 Identification cards – Contactless integrated circuit cards – Proximity cards is an international standard that defines proximity cards used for identification, and the transmission protocols for communicating with it. Current Version see Standard Parts below Other editions AAL Relevance As some AAL scenarios may contain access control scenarios either for residents and their families or for professionals (carers, service providers) identification cards are one possible technical solution. In this case ISO/IEC 14443 should be taken into account. Available from see Standard Parts below Standard Parts Standard ISO/IEC 14443-1:2008 ISO/IEC 14443-2:2010 V1.0 Title Identification cards – Contactless integrated circuit cards – Proximity cards – Part 1: Physical characteristics Identification cards – Contactless integrated circuit cards – 2013-01-15 Page 67 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14443-3:2011 ISO/IEC 14443-4:2008 Proximity cards – Part 2: Radio frequency power and signal interface Identification cards – Contactless integrated circuit cards – Proximity cards – Part 3: Initialization and anticollision Identification cards – Contactless integrated circuit cards – Proximity cards – Part 4: Transmission protocol Description ISO/IEC 14443-1:2008 defines the physical characteristics of PICCs, commonly known as proximity cards. It is to be used in conjunction with other parts of ISO/IEC 14443. ISO/IEC 14443-2:2010 specifies the characteristics of the fields to be provided for power and bi-directional communication between proximity coupling devices (PCDs) and proximity cards or objects (PICCs). It does not specify the means of generating coupling fields, nor the means of compliance with electromagnetic radiation and human exposure regulations, which can vary according to country. ISO/IEC 14443-3:2011 describes: • polling for proximity cards or objects (PICCs) entering the field of a proximity coupling device (PCD); • the byte format, the frames and timing used during the initial phase of communication between PCDs and PICCs; • the initial Request and Answer to Request command content; • methods to detect and communicate with one PICC among several PICCs (anticollision); • other parameters required to initialize communications between a PICC and PCD; • optional means to ease and speed up the selection of one PICC among several PICCs based on application criteria. ISO/IEC 14443 is one of a series of International Standards describing the parameters for identification cards as defined in ISO/IEC 7810, and the use of such cards for international interchange. ISO/IEC 14443-4:2008 specifies a half-duplex block transmission protocol featuring the special needs of a contactless environment and defines the activation and deactivation sequence of the protocol. [Source: ISO] External links • http://en.wikipedia.org/wiki/ISO/IEC_14443 ISO/IEC 18000 (RFID) Profile Reference Name V1.0 ISO/IEC 18000 ISO/IEC 18000: Information technology – Radio frequency identification for item management (RFID) 2013-01-15 Page 68 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories Networks and Buses; Wireless Protocols for Mobile Applications; ISO; IEC ICS 35.040: Character sets and information coding Abstract Radio-frequency identification (RFID) is the use of a wireless noncontact system that uses radio-frequency electromagnetic fields to transfer data from a tag attached to an object, for the purposes of automatic identification and tracking. Current Version see Standard Parts below Other editions The usage of RFID in specific domains is regulated in additional standards. AAL Relevance As AAL scenarios may have to identify and track different kind of items in a certain area (inside a flat), RFID is one possible technical solution. Available from see Standard Parts below Standard Parts Standard ISO/IEC 18000-1:2008 ISO/IEC 18000-2:2009 ISO/IEC 18000-3:2010 ISO/IEC 18000-4:2008 ISO/IEC 18000-6:2010 ISO/IEC 18000-61:2012 ISO/IEC 18000-62:2012 ISO/IEC 18000-64:2012 ISO/IEC 18000-7:2009 V1.0 Title Information technology – Radio frequency identification for item management – Part 1: Reference architecture and definition of parameters to be standardized Information technology – Radio frequency identification for item management – Part 2: Parameters for air interface communications below 135 kHz Information technology – Radio frequency identification for item management – Part 3: Parameters for air interface communications at 13,56 MHz Information technology – Radio frequency identification for item management – Part 4: Parameters for air interface communications at 2,45 GHz Information technology – Radio frequency identification for item management – Part 6: Parameters for air interface communications at 860 MHz to 960 MHz Information technology – Radio frequency identification for item management – Part 61: Parameters for air interface communications at 860 MHz to 960 MHz Type A Information technology – Radio frequency identification for item management – Part 62: Parameters for air interface communications at 860 MHz to 960 MHz Type B Information technology – Radio frequency identification for item management – Part 64: Parameters for air interface communications at 860 MHz to 960 MHz Type D Information technology – Radio frequency identification for item management – Part 7: Parameters for active air interface communications at 433 MHz 2013-01-15 Page 69 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description ISO/IEC 18000-1:2008 defines the generic architecture concepts in which item identification may commonly be required within the logistics and supply chain and defines the parameters that need to be determined in any standardized air interface definition in the subsequent parts of ISO/IEC 18000. The subsequent parts of ISO/IEC 18000 provide the specific values for definition of the air interface parameters for a particular frequency/type of air interface from which compliance (or non-compliance) with ISO/IEC 18000-1:2008 can be established. ISO/IEC 18000-1:2008 also provides a description of example conceptual architectures in which these air interfaces are often to be utilized. ISO/IEC 18000-1:2008 limits its scope to transactions and data exchanges across the air interface at reference point delta. The means of generating and managing such transactions, other than a requirement to achieve the transactional performance determined within ISO/IEC 18000-1:2008, are outside the scope of ISO/IEC 18000-1:2008, as is the definition or specification of any supporting hardware, firmware, software or associated equipment. Standardization of other reference points is outside the scope of ISO/IEC 18000-1:2008. ISO/IEC 18000-1:2008 is an enabling standard which supports and promotes several RFID implementations without making conclusions about the relative technical merits of any available option for any possible application. ISO/IEC 18000-1:2008 also provides reference information in respect of patents that have been declared to the developers of ISO/IEC 18000 as pertinent and provides reference addresses in respect of regulations under which ISO/IEC 18000 must operate. ISO/IEC 18000-2:2009 defines the air interface for radio frequency identification (RFID) devices operating below 135 kHz. The purpose of ISO/IEC 18000-2:2009 is to provide a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. ISO/IEC 18000-2:2009 is intended to allow for compatibility and to encourage inter-operability of products in the international marketplace. ISO/IEC 18000-2:2009 defines the physical layer used for communication between the interrogator and the tag and further defines the communications protocol used in the air interface. Two types of tag are defined by ISO/IEC 18000-2:2009: Type A and Type B, which differ only by their physical layer. Both support the same inventory (anti-collision) and protocol. Type A tags are permanently powered by the interrogator, including during the tag-tointerrogator transmission, and operate at 125 kHz. Type B tags are powered by the interrogator, except during the tag-to-interrogator transmission, and operate at 125 kHz or 134,2 kHz. ISO/IEC 18000-3:2010 has 3 MODES of operation, intended to address different applications. The detailed technical differences between the modes are shown in parameter tables. ISO/IEC 18000-3:2010 provides physical layer, collision management system and protocol V1.0 2013-01-15 Page 70 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot values for RFID systems for item identification operating at 13,56 MHz in accordance with the requirements of ISO/IEC 18000-1. It provides definitions for systems for each MODE determined in ISO/IEC 18000-3:2010. It defines three non-interfering MODES. The MODES are not interoperable. The MODES, whilst not interoperable, are non-interfering. ISO/IEC 18000-4:2008 is one of a series of International Standards and Technical Reports developed for the identification of items (Item Management) using radio frequency identification (RFID) technology. ISO/IEC 18000-4:2008 defines the 2,45 GHz protocols that support ISO/IEC 18000-1. Each of the specific physical/data link configurations is defined in a separate sub-clause. The configuration descriptions include a Physical Layer and a Data Link Layer. ISO/IEC 18000-4:2008 defines the air interface for radio frequency identification (RFID) devices operating in the 2,45 GHz Industrial, Scientific, and Medical (ISM) band used in item management applications. ISO/IEC 18000-4:2008 provides a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. ISO/IEC 18000-4:2008 is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. ISO/IEC 18000-4:2008 defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum equivalent isotropically radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and where appropriate operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. ISO/IEC 18000-4:2008 further defines the communications protocol used in the air interface. ISO/IEC 18000-4:2008 contains two modes. The first is a passive tag operating as an interrogator talks first while the second is a battery assisted tag operating as a tag talks first. The detailed technical differences between the modes are shown in the parameter tables. ISO/IEC 18000-6:2010 defines the air interface for radio frequency identification (RFID) devices operating in the 860 MHz to 960 MHz Industrial, Scientific, and Medical (ISM) band used in item management applications. It provides a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. ISO/IEC 18000-6:2010 is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. It defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum effective isotropic radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. It further defines the communications protocol used in the air interface. ISO/IEC 18000-6:2010 specifies the physical and logical requirements for a passiveV1.0 2013-01-15 Page 71 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot backscatter, Interrogator-Talks-First (ITF) or tag-talks-only-after-listening (TOTAL) RFID system. The system comprises Interrogators, and tags, also known as labels. An Interrogator receives information from a tag by transmitting a continuous-wave (CW) RF signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the Interrogator. The system is ITF, meaning that a tag modulates its antenna reflection coefficient with an information signal only after being directed to do so by an Interrogator, or TOTAL, meaning that a tag modulates its antenna reflection coefficient with an information signal upon entering an Interrogator's field after first listening for Interrogator modulation in order to determine if the system is ITF or not. In detail, ISO/IEC 18000-6:2010 contains one mode with four types. The detailed technical differences between the four types are shown in the associated parameter tables. Types A, B and C are ITF. Type A uses Pulse-Interval Encoding (PIE) in the forward link and an adaptive ALOHA collision-arbitration algorithm. Type B uses Manchester in the forward link and an adaptive binary-tree collision-arbitration algorithm. Type C uses PIE in the forward link and a random slotted collision-arbitration algorithm. Type D is TOTAL based on Pulse Position Encoding or Miller M=2 encoded subcarrier. ISO/IEC 18000-6:2010 specifies • physical interactions (the signalling layer of the communication link) between Interrogators and tags, • Interrogator and tag operating procedures and commands, • the collision arbitration scheme used to identify a specific tag in a multiple-tag environment. ISO/IEC 18000-61:2012 defines the air interface for radio frequency identification (RFID) devices operating in the 860 MHz to 960 MHz Industrial, Scientific, and Medical (ISM) band used in item management applications. It provides a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. It is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. It defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum effective isotropic radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. It further defines the communications protocol used in the air interface. ISO/IEC 18000-61:2012 specifies the physical and logical requirements for a passivebackscatter, Interrogator-Talks-First (ITF) systems. The system comprises Interrogators, also known as readers, and tags, also known as labels. An Interrogator receives information from a tag by transmitting a continuous-wave (CW) RF signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the Interrogator. The system is ITF, meaning that a tag modulates V1.0 2013-01-15 Page 72 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot its antenna reflection coefficient with an information signal only after being directed to do so by an Interrogator. ISO/IEC 18000-61:2012 contains Type A. Type A is ITF. Type A uses Pulse-Interval Encoding (PIE) in the forward link and an adaptive ALOHA collision-arbitration algorithm. ISO/IEC 18000-61:2012 specifies • physical interactions (the signalling layer of the communication link) between Interrogators and tags, • Interrogator and tag operating procedures and commands, • the collision arbitration scheme used to identify a specific tag in a multiple-tag environment. ISO/IEC 18000-62:2012 defines the air interface for radio frequency identification (RFID) devices operating in the 860 MHz to 960 MHz Industrial, Scientific, and Medical (ISM) band used in item management applications. It provides a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. It is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. It defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum effective isotropic radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. It further defines the communications protocol used in the air interface. ISO/IEC 18000-62:2012 specifies the physical and logical requirements for a passivebackscatter, Interrogator-Talks-First (ITF) systems. The system comprises Interrogators, also known as readers, and tags, also known as labels. An Interrogator receives information from a tag by transmitting a continuous-wave (CW) RF signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the Interrogator. The system is ITF, meaning that a tag modulates its antenna reflection coefficient with an information signal only after being directed to do so by an Interrogator. ISO/IEC 18000-62:2012 contains Type B. Type B uses Manchester in the forward link and an adaptive binary-tree collisionarbitration algorithm. ISO/IEC 18000-62:2012 specifies • physical interactions (the signalling layer of the communication link) between Interrogators and tags, • Interrogator and tag operating procedures and commands, • the collision arbitration scheme used to identify a specific tag in a multiple-tag V1.0 2013-01-15 Page 73 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot environment. ISO/IEC 18000-64:2012 defines the air interface for radio frequency identification (RFID) devices operating in the 860 MHz to 960 MHz Industrial, Scientific, and Medical (ISM) band used in item management applications. It provides a common technical specification for RFID devices that can be used by ISO committees developing RFID application standards. It is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. It defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum effective isotropic radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. It further defines the communications protocol used in the air interface. ISO/IEC 18000-64:2012 specifies the physical and logical requirements for a passivebackscatter, Tag Only Talks After Listening (TOTAL) RFID system. The system comprises Interrogators, also known as readers, and tags, also known as labels. An Interrogator receives information from a tag by transmitting a continuous-wave (CW) RF signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the Interrogator. The system is TOTAL, meaning that a tag modulates its antenna reflection coefficient with an information signal upon entering an Interrogator's field after first listening for Interrogator modulation in order to determine if the system is ITF or not. ISO/IEC 18000-64:2012 contains Type D. Type D is TOTAL based on Pulse Position Encoding or Miller M=2 encoded subcarrier. ISO/IEC 18000-64:2012 specifies • physical interactions (the signalling layer of the communication link) between Interrogators and tags, • Interrogator and tag operating procedures, • the collision arbitration scheme used to identify a specific tag in a multiple-tag environment. ISO/IEC 18000-7:2009 defines the air interface for radio frequency identification (RFID) devices operating as an active RF tag in the 433 MHz band used in item management applications. It provides a common technical specification for RFID devices that can be used by ISO technical committees developing RFID application standards. ISO/IEC 18000-7:2009 is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. ISO/IEC 180007:2009 defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum power, spurious emissions, modulation, duty cycle, data coding, bit V1.0 2013-01-15 Page 74 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. ISO/IEC 180007:2009 further defines the communications protocol used in the air interface. [Source: ISO] NFC: Near Field Communication Profile Reference Name Categories NFC NFC: Near Field Communication Networks and Buses; Wireless Protocols for Mobile Applications; ISO; IEC ICS 35.100.20: Data link layer 35.100.10: Physical layer Abstract Near field communication (NFC) is a set of standards for smartphones and similar devices to establish radio communication with each other by touching them together or bringing them into close proximity, usually no more than a few centimetres Present and anticipated applications include contactless transactions, data exchange, and simplified setup of more complex communications such as Wi-Fi. Communication is also possible between an NFC device and an unpowered NFC chip, called a “tag”. [Source: Wikipedia] Current Version see Standard Parts below Other editions Standard ECMA-340 for ISO/IEC 18092: Near Field Communication Interface and Protocol (NFCIP-1) Standard ECMA-352 for ISO/IEC 21481:2012: Near Field Communication Interface and Protocol -2 (NFCIP-2) AAL Relevance As AAL scenarios may contain mobile devices with the need for contactless data transmission to other (mobile and stationary) devices, NFC is one possible technical solution. Available from see Standard Parts below Standard Parts Standard ISO/IEC 18092:2004 ISO/IEC 21481:2012 Title Information technology – Telecommunications and information exchange between systems – Near Field Communication – Interface and Protocol (NFCIP-1) Information technology – Telecommunications and information exchange between systems – Near Field Communication Interface and Protocol -2 (NFCIP-2) Description ISO/IEC 18092:2004 defines communication modes for Near Field Communication Interface and Protocol (NFCIP-1) using inductive coupled devices operating at the centre V1.0 2013-01-15 Page 75 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot frequency of 13,56 MHz for interconnection of computer peripherals. It also defines both the Active and the Passive communication modes of NFCIP-1 to realize a communication network using Near Field Communication devices for networked products and also for consumer equipment. This International Standard specifies, in particular, modulation schemes, codings, transfer speeds and frame format of the RF interface, as well as initialization schemes and conditions required for data collision control during initialization. Furthermore, this International Standard defines a transport protocol including protocol activation and data exchange methods. ISO/IEC 21481 specifies the communication mode selection mechanism, designed not to disturb any ongoing communication at 13,56 MHz, for devices implementing ISO/IEC 18092 and the reader functionality for integrated circuit cards compliant with ISO/IEC 14443 or ISO/IEC 15693. ISO/IEC 21481 requires implementations to enter the selected communication mode as specified in the respective International Standard. The communication mode specifications, however, are outside the scope of this NFCIP-2 International Standard. [Source: ISO] [Source: ecma-international.org] External links • http://en.wikipedia.org/w/index.php?title=Near_field_communication&oldid=527787123 • http://www.ecma-international.org • http://www.iso.org/iso/home.html 1.5. (Wireless) Personal Area Networks IEEE 802.15.4 Profile Reference Name Categories ICS Abstract V1.0 IEEE 802.15.4 IEEE 802.15.4: IEEE Standard for Local and metropolitan area networks–Part 15.4: Low-Rate Wireless Personal Area Networks (Basis for ZigBee,ISA100.11a, WirelessHART, MiWi) Networks and Buses; Wireless Personal Area Network; IEEE; ZigBee IEEE 802.15.4 is a standard which specifies the physical layer and media access control for low-rate wireless personal area networks (LRWPANs). It is maintained by the IEEE 802.15 working group. It is the basis for the ZigBee, ISA100.11a, WirelessHART, and MiWi specifications, each of which further extends the standard by developing the upper layers which are not defined in IEEE 802.15.4. Alternatively, it can be used with 6LoWPAN and standard Internet protocols to build a wireless embedded Internet. [Source: Wikipedia] 2013-01-15 Page 76 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version 2011 Other editions AAL Relevance IEEE 802.15.4 is the basis for many wireless sensor networks used in AAL scenarios. Available from http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf Description IEEE standard 802.15.4 intends to offer the fundamental lower network layers of a type of wireless personal area network (WPAN) which focuses on low-cost, low-speed ubiquitous communication between devices (in contrast with other, more end-user oriented approaches, such as Wi-Fi). The emphasis is on very low cost communication of nearby devices with little to no underlying infrastructure, intending to exploit this to lower power consumption even more. The basic framework conceives a 10-meter communications range with a transfer rate of 250 kbit/s. Trade-offs are possible to favour more radically embedded devices with even lower power requirements, through the definition of not one, but several physical layers. Lower transfer rates of 20 and 40 kbit/s were initially defined, with the 100 kbit/s rate being added in the current revision. Even lower rates can be considered with the resulting effect on power consumption. As already mentioned, the main identifying feature of IEEE 802.15.4 among WPANs is the importance of achieving extremely low manufacturing and operation costs and technological simplicity, without sacrificing flexibility or generality. Important features include real-time suitability by reservation of guaranteed time slots, collision avoidance through CSMA/CA and integrated support for secure communications. Devices also include power management functions such as link quality and energy detection. IEEE 802.15.4-conformant devices may use one of three possible frequency bands for operation. [Source: Wikipedia] External links • http://www.ieee802.org/15/pub/TG4.html • http://en.wikipedia.org/w/index.php?title=IEEE_802.15.4&oldid=527494689 • http://en.wikipedia.org/w/index.php?title=Personal_area_network&oldid=522004127 6LoWPAN Profile Reference Name Categories ICS V1.0 6LoWPAN 6LoWPAN: IPv6 for Wireless Personal Area Networks Networks and Buses; Wireless Personal Area Network; 2013-01-15 Page 77 of 490 AALIANCE2 Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot 6LoWPAN is a communication protocol for small and smallest devices with limited processing capabilities. 6LowPAN enables these devices to participate in the Internet of Things. [Source: Wikipedia] see Standard Parts below As AAL scenarios may contain small devices with limited processing capabilities and Internet access may be necessary 6LoWPAN should be taken into account. see Standard Parts below Standard Parts Standard RFC 4919 RFC 4944 RFC 6282 RFC 6775 Title IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals Transmission of IPv6 Packets over IEEE 802.15.4 Networks Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks Neighbour Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) Description The 6LoWPAN group has defined encapsulation and header compression mechanisms that allow IPv6 packets to be sent to and received from over IEEE 802.15.4 based networks. IPv4 and IPv6 are the work horses for data delivery for local-area networks, metropolitan area networks, and wide-area networks such as the Internet. Likewise, IEEE 802.15.4 devices provide sensing communication-ability in the wireless domain. The inherent natures of the two networks though, is different. The target for IP networking for low-power radio communication are the applications that need wireless internet connectivity at lower data rates for devices with very limited form factor. Examples could include, but are not limited to: automation and entertainment applications in home, office and factory environments. The header compression mechanisms standardized in RFC4944 can be used to provide header compression of IPv6 packets over such networks. IPv6 is also in use on the Smart Grid enabling smart meters and other devices to build a micro mesh network before sending the data back to the billing system using the IPv6 backbone. Some of these networks run over IEEE 802.15.4 radios, and therefore use the header compression and fragmentation as specified by RFC4944. [Source: Wikipedia] External links • http://datatracker.ietf.org/wg/6lowpan/charter/ • http://6lowpan.tzi.org/FrontPage?action=show&redirect=StartSeite • http://en.wikipedia.org/w/index.php?title=6LoWPAN&oldid=522650931 V1.0 2013-01-15 Page 78 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot MiWi Profile Reference Name Categories ICS Abstract MiWi MiWi Networks and Buses; Wireless Personal Area Network; IEEE; ZigBee MiWi and MiWi P2P are proprietary wireless protocols designed by Microchip Technology that uses small, low-power digital radios based on the IEEE 802.15.4 standard for wireless personal area networks (WPANs). It is designed for low data transmission rates and short distance, cost constrained networks, such as industrial monitoring and control, home and building automation, remote control, low-power wireless sensors, lighting control and automated meter reading. [Source: Wikipedia] Current Version Other editions AAL Relevance MiWi can be used for setting up wireless sensor networks which may be needed in AAL scenarios. Available from http://www.microchip.com/stellent/idcplg? IdcService=SS_GET_PAGE&nodeId=1824&appnote=en520606 http://www.microchip.com/stellent/idcplg? IdcService=SS_GET_PAGE&nodeId=1824&appnote=en536181 Description Microchip has released two application notes which present technical information on MiWi. These are not primarily protocol specifications and more than half of these documents are focused on implementing the MiWi protocol on Microchip microcontrollers. As of 2009, interoperable third party implementations have not appeared. Unless they do, it will not be clear if those specifications are complete or accurate enough to serve roles other than supporting Microchip's code or being one more proprietary example of a lightweight WPAN stack. Many developers trying to use WPAN technologies have observed that ZigBee seems undesirably complex. Accordingly, there exists a technical niche for a simpler protocols, of which MiWi is a proprietary example. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=MiWi&oldid=529269757 V1.0 2013-01-15 Page 79 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 1.5.1 Bluetooth IEEE 802.15.1 Profile Reference Name Categories ICS Abstract IEEE 802.15.1 IEEE 802.15.1 (Bluetooth) Networks and Buses; Wireless Personal Area Network; Bluetooth Bluetooth is a wireless technology standard for exchanging data over short distances (using short-wavelength radio transmissions in the ISM band from 2400–2480 MHz) from fixed and mobile devices, creating personal area networks (PANs) with high levels of security. Created by telecom vendor Ericsson in 1994, it was originally conceived as a wireless alternative to RS-232 data cables. It can connect several devices, overcoming problems of synchronization. [Source: Wikipedia] Current Version Other editions AAL Relevance Many AAL scenarios contain (mobile) devices (headsets, wearable sensors) connected to other devices (stationary, mobile). Here Bluetooth can be useful. Available from http://ieee802.org/15/Bluetooth/index.html Description Bluetooth uses a radio technology called frequency-hopping spread spectrum, which chops up the data being sent and transmits chunks of it on up to 79 bands (1 MHz each; centred from 2402 to 2480 MHz) in the range 2,400–2,483.5 MHz (allowing for guard bands). This range is in the globally unlicensed Industrial, Scientific and Medical (ISM) 2.4 GHz short-range radio frequency band. It usually performs 800 hops per second, with Adaptive Frequency-Hopping (AFH) enabled. A master Bluetooth device can communicate with a maximum of seven devices in a piconet (an ad-hoc computer network using Bluetooth technology), though not all devices reach this maximum. The devices can switch roles, by agreement, and the slave can become the master (for example, a headset initiating a connection to a phone will necessarily begin as master, as initiator of the connection; but may subsequently prefer to be slave). To use Bluetooth wireless technology, a device has to be able to interpret certain Bluetooth profiles, which are definitions of possible applications and specify general behaviours that Bluetooth enabled devices use to communicate with other Bluetooth devices. These profiles include settings to parametrize and to control the communication from start. Adherence to profiles saves the time for transmitting the parameters anew before the bi-directional link becomes effective. There are a wide range of Bluetooth profiles that describe many different types of applications or use cases for devices. [Source: Wikipedia] V1.0 2013-01-15 Page 80 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.ieee802.org/15/pub/TG1.html • http://www.bluetooth.com/Pages/Bluetooth-Home.aspx • https://www.bluetooth.org/apps/content/ • http://en.wikipedia.org/w/index.php?title=Bluetooth&oldid=528277290 BT-LE Profile Reference Name Categories ICS Abstract BT-LE BT-LE: Bluetooth Low Energy Networks and Buses; Wireless Personal Area Networks; Bluetooth Bluetooth low energy (BT-LE) is a feature of Bluetooth 4.0 wireless radio technology, aimed at new, principally low-power and low-latency, applications for wireless devices within a short range (up to 50 metres / 160 feet). This facilitates a wide range of applications and smaller form factor devices in the healthcare, fitness, security and home entertainment industries. [Source: Wikipedia] Current Version Other editions AAL Relevance BT-LE may be used for long-term monitoring scenarios in AAL scenarios. Available from https://www.bluetooth.org/Technical/Specifications/adopted.htm Description Devices using Bluetooth low energy wireless technology are expected to consume a fraction of the power of Classic Bluetooth enabled products for Bluetooth communication. In many cases, products will be able to operate more than a year on a button cell battery without recharging. It will allow sensors such as thermometers to operate continuously, communicating intermittently with other devices such as a mobile phone. This may increase the concerns for privacy, as when the remote, low power, continuously on, sensor would be present in devices with BT-LE. Several chip suppliers have released Bluetooth low energy chips. Some of these offered chip designs include the entire protocol suite implementation, others allow for special implementing strategies. Some of these chip designs allow for dynamic change of protocol suite even outside the Bluetooth technology/Bluetooth low energy standard, others are just tailored for one protocol suite. Those offering products include Broadcom, CSR, EM Microelectronic, Nordic Semiconductor, and Texas Instruments. [Source: Wikipedia] V1.0 2013-01-15 Page 81 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://en.wikipedia.org/w/index.php?title=Bluetooth_low_energy&oldid=528071146 HDP Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from HDP HDP: Bluetooth Health Device Profile Networks and Buses; Wireless Personal Area Networks; Bluetooth Profile designed to facilitate transmission and reception of Medical Device data. A Bluetooth profile is a specification regarding an aspect of Bluetooth-based wireless communication between devices. In order to use Bluetooth technology, a device must be compatible with the subset of Bluetooth profiles necessary to use the desired services. [Source: Wikipedia] As AAL scenarios can contain (mobile) medical devices Bluetooth HDP is one possibility to connect these devices with other (stationary and mobile) devices (like base stations, personal health records). https://www.bluetooth.org/docman/handlers/downloaddoc.ashx? doc_id=225927 Description The Bluetooth Health Device Profile defines the underlying wireless connection and protocol. It operates in conjunction with the ISO/IEEE 11073-20601 Personal Health Data Exchange Protocol and associated 11073-104xx device specialization specifications (where xx represents a specific document number) to provide application level interoperability for a wide variety of personal health devices. The purpose of HDP is to support a long and growing list of proposed applications for mobile, in-home, in-clinic and in-hospital uses. For example, in a clinical setting, Bluetooth transceivers using HDP may transmit waveforms from portable patient monitoring devices (Sources) such as ECG monitors and blood oximeters to fixed monitoring stations (Sinks) located within the clinic. Exemplary home use applications include those in which the Sources might be pulse oximeters, glucose meters, weight scales, thermometers, or blood pressure monitors, and in which the Sink might be a cell phone, a PDA, telehealth station, or a personal computer. In such applications, the Sink might serve not only to display the data locally, but also to forward that data to a remote server for further sharing (as with the user's physician) and archiving. [Source: HEALTH DEVICE PROFILE Implementation Guidance Whitepaper] V1.0 2013-01-15 Page 82 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=225927 1.5.2 ZigBee ZigBee Profile Reference Name Categories ZigBee ZigBee Networks and Buses; (Wireless) Personal Area Networks; Communication Protocols; Medical Devices; ICS Abstract ZigBee is a specification for a suite of high level communication protocols using small, low-power digital radios based on an IEEE 802 standard for personal area networks. ZigBee devices are often used in mesh network form to transmit data over longer distances, passing data through intermediate devices to reach more distant ones. This allows ZigBee networks to be formed ad-hoc, with no centralized control or high-power transmitter/receiver able to reach all of the devices. Any ZigBee device can be tasked with running the network. [Source: Wikipedia] Current Version Other editions AAL Relevance ZigBee can be used for setting up wireless sensor networks which may be needed in AAL scenarios. Available from http://www.zigbee.org/Specifications/ZigBee/Overview.aspx Description ZigBee is targeted at applications that require a low data rate, long battery life, and secure networking. ZigBee has a defined rate of 250 kbit/s, best suited for periodic or intermittent data or a single signal transmission from a sensor or input device. Applications include wireless light switches, electrical meters with in-home-displays, traffic management systems, and other consumer and industrial equipment that requires short-range wireless transfer of data at relatively low rates. The technology defined by the ZigBee specification is intended to be simpler and less expensive than other WPANs, such as Bluetooth. The name refers to the waggle dance of honey bees after their return to the beehive. ZigBee is a low-cost, low-power, wireless mesh network standard. The low cost allows the technology to be widely deployed in wireless control and monitoring applications. Low power-usage allows longer life with smaller batteries. Mesh networking provides high reliability and more extensive range. ZigBee chip vendors typically sell integrated radios and microcontrollers with between 60 KB and 256 KB flash memory. ZigBee operates in the industrial, scientific and medical (ISM) radio bands; 868 MHz in V1.0 2013-01-15 Page 83 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Europe, 915 MHz in the USA and Australia and 2.4 GHz in most jurisdictions worldwide. Data transmission rates vary from 20 to 900 kilobits/second. The ZigBee network layer natively supports both star and tree typical networks, and generic mesh networks. Every network must have one coordinator device, tasked with its creation, the control of its parameters and basic maintenance. Within star networks, the coordinator must be the central node. Both trees and meshes allows the use of ZigBee routers to extend communication at the network level. ZigBee builds upon the physical layer and medium access control defined in IEEE standard 802.15.4 (2003 version) for low-rate WPANs. The specification goes on to complete the standard by adding four main components: network layer, application layer, ZigBee device objects (ZDOs) and manufacturer-defined application objects which allow for customization and favour total integration. Besides adding two high-level network layers to the underlying structure, the most significant improvement is the introduction of ZDOs. These are responsible for a number of tasks, which include keeping of device roles, management of requests to join a network, device discovery and security. ZigBee is not intended to support power line networking but to interface with it at least for smart metering and smart appliance purposes. Because ZigBee nodes can go from sleep to active mode in 30 ms or less, the latency can be low and devices can be responsive, particularly compared to Bluetooth wake-up delays, which are typically around three seconds. Because ZigBee nodes can sleep most of the time, average power consumption can be low, resulting in long battery life. [Source: Wikipedia] External links • http://www.zigbee.org/Home.aspx • http://en.wikipedia.org/w/index.php?title=ZigBee&oldid=529423988 ZigBee Home Automation Profile Reference Name Categories ZigBee Home Automation ZigBee Home Automation Networks and Buses; Communication Protocols; General Purpose Protocols; ZigBee ICS Abstract ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management and security, as well as the expandability to connect with other ZigBee networks Current Version Other editions V1.0 2013-01-15 Page 84 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance As AAL scenarios may use wireless sensor networks for home automation ZigBee Home Automation may be useful. Available from http://zigbee.org/Standards/ZigBeeHomeAutomation/Overview.aspx Description ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management and security, as well as the expandability to connect with other ZigBee networks. Smarter homes allow consumers to save money, be more environmentally aware, feel more secure and enjoy a variety of conveniences that make homes easier and less expensive to maintain. ZigBee Home Automation supports a diverse ecosystem of service providers and product manufacturers as they invent products necessary to create smart homes. These products are ideal for new construction, do-it-yourself and retrofit markets, and are easy to use, maintain and install. All ZigBee Home Automation products are ZigBee Certified to perform regardless of manufacturer, allowing anyone to purchase with confidence. Numerous innovative companies have contributed their expertise to this standard, including Phillips, Control4 and Texas Instruments. ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management, and security as well as expand to connect with other ZigBee networks. Smarter homes allow consumers to save money, be more environmentally aware, feel more secure and enjoy a variety of conveniences that make homes easier and less expensive to maintain. All ZigBee Home Automation products are ZigBee Certified to perform regardless of manufacturer, allowing anyone to purchase with confidence. These products are ideal for new construction, do-it-yourself and retrofit markets and are easy to use, maintain and install. ZigBee Health Care Profile Reference Name Categories ZigBee Health Care ZigBee Health Care Network and Buses; (Wireless) Personal Area Network; Communication Protocols; Medical Devices; ZigBee ICS Abstract ZigBee Health Care offers a global standard for interoperable products enabling secure and reliable monitoring and management of noncritical, low-acuity healthcare services targeted at chronic disease, ageing independence and general health, wellness and fitness. [Source: ZigBee.org] Current Version Other editions V1.0 2013-01-15 Page 85 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance ZigBee Health care’s specification provides standard interfaces and device descriptions to allow inter-operability among ZigBee devices produced by various manufacturers of health care products. Available from http://www.zigbee.org/Standards/ZigBeeHealthCare/Overview.aspx Description ZigBee Health Care offers a global standard for interoperable products enabling secure and reliable monitoring and management of non-critical, low-acuity healthcare services targeted at chronic disease, ageing independence and general health, wellness and fitness. These easy-to-use products facilitate independence, plus overall health, wellness and fitness awareness. A variety of these products even offer an innovative connection with health care professionals like doctors and nurses, allowing them to monitor your health even while you're at home. All ZigBee Health Care products are ZigBee Certified to perform regardless of manufacturer, allowing everyone to purchase with confidence. These products are ideal for personal, medical personnel, gymnasiums or hospital/recovery centre use. [Source: ZigBee.org] External links • http://www.zigbee.org/Standards/ZigBeeHealthCare/Overview.aspx ZigBee SE Profile Reference Name Categories ICS Abstract ZigBee SE ZigBee SE: ZigBee Smart Energy Communications Protocols; Smart Metering; ZigBee ZigBee Smart Energy is the world's leading standard for interoperable products that monitor, control, inform and automate the delivery and use of energy and water. It helps create greener homes by giving consumers the information and automation needed to easily reduce their consumption and save money, too. Current Version 1.1, Version 2.0 is currently under development Other editions AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from http://www.zigbee.org/Standards/ZigBeeSmartEnergy/Overview.aspx Description ZigBee Smart Energy is the world's leading standard for interoperable products that monitor, control, inform and automate the delivery and use of energy and water. It helps V1.0 2013-01-15 Page 86 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot create greener homes by giving consumers the information and automation needed to easily reduce their consumption and save money, too. ZigBee Smart Energy version 1.1, the newest version for product development, adds several important features including dynamic pricing enhancements, tunnelling of other protocols, prepayment features, over-the-air updates and guaranteed backwards compatibility with certified ZigBee Smart Energy products version 1.0. This standard supports the diverse needs of a global ecosystem of utilities, product manufacturers and government groups as they plan to meet future energy and water needs. All ZigBee Smart Energy products are ZigBee Certified to perform regardless of manufacturer, allowing utilities and consumers to purchase with confidence. Every product needed to implement a robust ZigBee Smart Energy home area network (HAN) is available. These products make it easy for utilities and governments to deploy smart grid solutions that are secure, easy to install and consumer-friendly. Some of the world's leading utilities, energy service providers, product manufacturers and technology companies are supporting the development of ZigBee Smart Energy. Several other standards groups are also involved with extending the reach of ZigBee Smart Energy to more homes around the world. Smart Energy Profile version 2.0 is currently under development in cooperation with a number of other standards development groups. It will offer IP-based control for advanced metering infrastructure and home area networks. This version will not replace ZigBee Smart Energy version 1, rather it will offer utilities and energy service providers another choice when creating their advanced metering infrastructure and home area networks (HANs). In addition to all the services and devices found in ZigBee Smart Energy version 1, version 2.0 will feature control of plug-in electric vehicle (PEV) charging, installation, configuration and firmware download for HAN devices, prepay services, user information and messaging, load control, demand response and common information and application profile interfaces for wired and wireless HANs. V1.0 2013-01-15 Page 87 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 2. Communication Protocols TCP/IP Profile Reference Name Categories ICS Abstract TCP/IP TCP/IP: Transmission Control Protocol/Internet Protocol Communication Protocols; IETF 35.110 - Networking TCP/IP (Transmission Control Protocol/Internet Protocol) is the basic communication language or protocol of the Internet Current Version see Standard Parts below Other editions AAL Relevance base protocol for many higher-level protocols Available from see Standard Parts below Standard Parts Standard RFC 791 RFC 793 RFC 1122 RFC 2460 RFC 2474 RFC 3168 RFC 3260 RFC 4301 RFC 4379 RFC 5095 RFC 5462 RFC 5722 RFC 5871 RFC 5884 RFC 6040 RFC 6093 RFC 6298 RFC 6424 V1.0 Title Internet Protocol (V4) Transmission Control Protocol Requirements for Internet Hosts – Communication Layers Internet Protocol, Version 6 (IPv6) Specification Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers The Addition of Explicit Congestion Notification (ECN) to IP New Terminology and Clarifications for Diffserv Security Architecture for the Internet Protocol Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures Deprecation of Type 0 Routing Headers in IPv6 Multiprotocol Label Switching (MPLS) Label Stack Entry: “EXP” Field Renamed to “Traffic Class” Field Handling of Overlapping IPv6 Fragments IANA Allocation Guidelines for the IPv6 Routing Header Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs) Tunnelling of Explicit Congestion Notification On the Implementation of the TCP Urgent Mechanism Computing TCP's Retransmission Timer Mechanism for Performing Label Switched Path Ping (LSP Ping) over 2013-01-15 Page 88 of 490 AALIANCE2 RFC 6426 RFC 6437 RFC 6528 RFC 6564 RFC 6633 D4.1 Online Repository of Standards - Snapshot MPLS Tunnels MPLS On-Demand Connectivity Verification and Route Tracing IPv6 Flow Label Specification Defending against Sequence Number Attacks A Uniform Format for IPv6 Extension Headers Deprecation of ICMP Source Quench Messages Description TCP/IP (Transmission Control Protocol/Internet Protocol) is the basic communication language or protocol of the Internet. It can also be used as a communications protocol in a private network (either an intranet or an extranet). When you are set up with direct access to the Internet, your computer is provided with a copy of the TCP/IP program just as every other computer that you may send messages to or get information from also has a copy of TCP/IP. TCP/IP is a two-layer protocol. The higher layer, Transmission Control Protocol, manages the assembling of a message or file into smaller packets that are transmitted over the Internet and received by a TCP layer that reassembles the packets into the original message. The lower layer, Internet Protocol, handles the address part of each packet so that it gets to the right destination. Each gateway computer on the network checks this address to see where to forward the message. Even though some packets from the same message are routed differently than others, they'll be reassembled at the destination. TCP/IP uses the client/server model of communication in which a computer user (a client) requests and is provided a service (such as sending a Web page) by another computer (a server) in the network. TCP/IP communication is primarily point-to-point, meaning each communication is from one point (or host computer) in the network to another point or host computer. TCP/IP and the higher-level applications that use it are collectively said to be “stateless” because each client request is considered a new request unrelated to any previous one (unlike ordinary phone conversations that require a dedicated connection for the call duration). Being stateless frees network paths so that everyone can use them continuously. (Note that the TCP layer itself is not stateless as far as any one message is concerned. Its connection remains in place until all packets in a message have been received.) External links • http://searchnetworking.techtarget.com/definition/TCP-IP • http://technet.microsoft.com/it-it/library/cc737968(v=ws.10).aspx • http://en.wikipedia.org/wiki/Transmission_Control_Protocol • http://en.wikipedia.org/wiki/Internet_Protocol • http://en.wikipedia.org/wiki/IPv6 V1.0 2013-01-15 Page 89 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot UDP Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from RFC 768 UDP - User Data Protocol Communication Protocols; IETF 35.110 - Networking UDP is a network protocol the offers a datagram mode of packetswitched computer communication in the environment of an interconnected set of computer networks. see Standard Parts below base protocol for many higher-level protocols such as UPnP see Standard Parts below Standard Parts Standard RFC 768 RFC 3828 RFC 3948 RFC 4113 RFC 5405 RFC 5426 Title User Datagram Protocol The Lightweight User Datagram Protocol (UDP-LITE) UDP Encapsulation of IPsec ESP Packets Management Information Base for the UDP Unicast UDP Usage Guidelines for Application Design Transmission of SysLog messages over UDP Description UDP stands for “User Datagram Protocol.” It is part of the TCP/IP suite of protocols used for data transferring. UDP is a known as a “stateless” protocol, meaning it doesn't acknowledge that the packets being sent have been received. For this reason, the UDP protocol is typically used for streaming media. While you might see skips in video or hear some fuzz in audio clips, UDP transmission prevents the playback from stopping completely. External links • http://www.techterms.com/definition/udp • http://www.javvin.com/protocolUDP.html • http://en.wikipedia.org/wiki/User_Datagram_Protocol V1.0 2013-01-15 Page 90 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 2.1.1 General Purpose Protocols File Transfer BEEP Profile Reference Name Categories RFC 3080 The Blocks Extensible Exchange Protocol Core (BEEP) Communication Protocols; General Purpose Protocols; File Transfer; IETF ICS 35.110 - Networking Abstract BEEP is a generic application protocol kernel for connection-oriented, asynchronous interactions Current Version Other editions AAL Relevance can be used for the exchange of information between components of an AAL system Available from http://tools.ietf.org/html/rfc3080 Description BEEP is a framework for creating network application protocols. It includes an application protocol kernel for connection-oriented asynchronous interactions. BEEP is intended to abstract-out the common features that have traditionally been duplicated in each protocol implementation. BEEP typically runs on top of TCP and allows the exchange of messages called 'frames'. Unlike HTTP (and similar protocols), either end of the connection can send a frame at any time, and 'questions' and 'replies' can be interleaved easily. BEEP also includes facilities for encryption and authentication, and is highly extensible. [Source: Wikipedia] External links • http://www.beepcore.org/ • http://en.wikipedia.org/wiki/BEEP FTP Profile Reference Name Categories V1.0 RFC 959 File Transfer Protocol (FTP) Communication Protocols; General Purpose Protocols; File Transfer; IETF 2013-01-15 Page 91 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract 35.110 - Networking FTP is a standard protocol to transmit the files from one host to another one Current Version Other editions AAL Relevance May be used to exchange data between components of an AAL system, in particular over WAN/Internet Available from http://tools.ietf.org/html/rfc959 Standard Parts Standard RFC 959 RFC 2228 RFC 2640 RFC 2773 RFC 3659 RFC 5797 Title File Transfer Protocol (FTP) FTP Security Extensions Internationalization of the File Transfer Protocol FTP Encryption using KEA and SKIPJACK Extensions to FTP FTP Command and Extension Registry Description FTP is a standard protocol to transmit the file from an host to another one. The objectives of FTP are 1) to promote sharing of files (computer programs and/or data), 2) to encourage indirect or implicit (via programs) use of remote computers, 3) to shield a user from variations in file storage systems among hosts, and 4) to transfer data reliably and efficiently. FTP, though usable directly by a user at a terminal, is designed mainly for use by programs. External links • http://en.wikipedia.org/wiki/FTP HTTP Profile Reference Name Categories ICS Abstract V1.0 HTTP HTTP: Hypertext Transfer Protocol Communications Protocols; General Purpose Protocol; File Transfer; Streaming; IETF The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. It is a generic, stateless, objectoriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods (commands). 2013-01-15 Page 92 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot see Standard Parts below HTTP has been in use by the World-Wide Web global information see Standard Parts below Standard Parts Standard RFC2616 Hypertext Transfer Protocol RFC6585 Additional HTTP Status Codes Title Description The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers [47]. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. External links • http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol IMAP4 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from RFC 3501 IMAP4: Internet Message Access Protocol - Version 4rev1 Communication Protocols; General Purpose Protocols; File Transfer; IETF 35.110 - Networking IMAP is a method of accessing electronic mail or bulletin board messages that are kept on a (possibly shared) mail server see Standard Parts below Can be used for the exchange of information between components of an AAL system http://tools.ietf.org/html/rfc3501 Standard Parts Standard RFC 3501 RFC 1731 V1.0 Title Internet Message Access Protocol - Version 4rev1 IMAP4 Authentication Mechanisms 2013-01-15 Page 93 of 490 AALIANCE2 RFC 2061 RFC 4466 RFC 4469 RFC 4551 RFC 5032 RFC 5182 RFC 5738 RFC 6186 D4.1 Online Repository of Standards - Snapshot IMAP4 COMPATIBILITY WITH IMAP2BIS Collected Extensions to IMAP4 ABNF Internet Message Access Protocol (IMAP) CATENATE Extension IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization WITHIN Search Extension to the IMAP Protocol IMAP Extension for Referencing the Last SEARCH Result IMAP Support for UTF-8 Use of SRV Records for Locating Email Submission/Access Services Description IMAP stands for Internet Message Access Protocol. It is a method of accessing electronic mail or bulletin board messages that are kept on a (possibly shared) mail server. In other words, it permits a “client” email program to access remote message stores as if they were local. For example, email stored on an IMAP server can be manipulated from a desktop computer at home, a workstation at the office, and a notebook computer while travelling, without the need to transfer messages or files back and forth between these computers. Key goals for IMAP include: 1. Be fully compatible with Internet messaging standards, e.g. MIME. 2. Allow message access and management from more than one computer. 3. Allow access without reliance on less efficient file access protocols. 4. Provide support for “online”, “offline”, and “disconnected” access modes 5. Support for concurrent access to shared mailboxes 6. Client software needs no knowledge about the server's file store format. External links • http://en.wikipedia.org/wiki/IMAP • http://networking.ringofsaturn.com/Protocols/imap.php POP3 Profile Reference Name Categories RFC 1939 POP3: Post Office Protocol – Version 3 Communication Protocols; General Purpose Protocols; File Transfer; IETF ICS 35.110 - Networking Abstract POP3 is a protocol that permits to download e-mails from a mail server, and enables the offline mail consultation. Current Version see Standard Parts below V1.0 2013-01-15 Page 94 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance can be used for the exchange of information between components of an AAL system Available from http://tools.ietf.org/html/rfc1939 Standard Parts Standard RFC 1939 RFC 1957 RFC 2449 RFC 6186 Title Post Office Protocol - Version 3 Some Observations on Implementations of the Post Office Protocol (POP3) POP3 Extension Mechanism Use of SRV Records for Locating Email Submission/Access Services Description The Post Office Protocol (POP) works best when one has only a single computer, since it was designed to support “offline” message access, wherein messages are downloaded and then deleted from the mail server. This mode of access is not compatible with access from multiple computers since it tends to sprinkle messages across all of the computers used for mail access. Thus, unless all of those machines share a common file system, the offline mode of access that POP was designed to support effectively ties the user to one computer for message storage and manipulation. External links • http://en.wikipedia.org/wiki/Post_Office_Protocol SMTP Profile Reference Name Categories RFC 5321 SMTP: Simple Mail Transfer Protocol Communication Protocols; General Purpose Protocols; File Transfer; IETF ICS 35.110 - Networking Abstract SMTP is a protocol for reliable and efficient transfer of e-mails Current Version Other editions AAL Relevance can be used for the exchange of information between components of an AAL system Available from http://tools.ietf.org/html/rfc5321 Description SMTP is the Internet protocol used to transfer electronic mail between computers, much like HTTP is the Internet protocol used to transfer web pages between computers. V1.0 2013-01-15 Page 95 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Mail servers use SMTP to send and receive mail messages, while client applications normally use SMTP only to send message and receive messages using a different protocol, such as POP3 or IMAP4. External links • http://utcc.utoronto.ca/usg/technotes/smtp-intro.html • http://en.wikipedia.org/wiki/SMTP SSH Profile Reference Name Categories RFC 4251 SSH: Secure Shell Communication Protocols, General Purpose Protocols, File Transfer; IETF ICS 35.110 - Networking Abstract Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network Current Version 2 Other editions AAL Relevance Allow a secure login over an insecure network, e.g. for maintenance purposes or file transfer Available from http://tools.ietf.org/html/rfc4251 Description Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network. It consists of three major components: • The Transport Layer Protocol [SSH-TRANS] provides server authentication, confidentiality, and integrity. It may optionally also provide compression. The transport layer will typically be run over a TCP/IP connection, but might also be used on top of any other reliable data stream. • The User Authentication Protocol [SSH-USERAUTH] authenticates the client-side user to the server. It runs over the transport layer protocol. • The Connection Protocol [SSH-CONNECT] multiplexes the encrypted tunnel into several logical channels. It runs over the user authentication protocol. The client sends a service request once a secure transport layer connection has been established. A second service request is sent after user authentication is complete. This allows new protocols to be defined and coexist with the protocols listed above. The connection protocol provides channels that can be used for a wide range of purposes. Standard methods are provided for setting up secure interactive shell sessions and for forwarding (“tunnelling”) arbitrary TCP/IP ports and X11 connections. V1.0 2013-01-15 Page 96 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://en.wikipedia.org/wiki/Secure_Shell TFTP Profile Reference Name Categories RFC 1350 Trivial File Transfer Protocol (TFTP) Communication Protocols; General Purpose Protocols; File Transfer; IETF ICS 35.110 - Networking Abstract TFTP is a simple protocol that permits the transmission of configuration or initial program files at boot time and is supported by some network boards for remote boot functionality Current Version see Standard Parts below Other editions AAL Relevance can be used to transfer configuration or boot files at the startup of AAL system components running their own operating systems Available from http://tools.ietf.org/html/rfc1350 Standard Parts Standard RFC 1350 RFC 1785 RFC 2347 RFC 2348 RFC 2349 Title The TFTP protocol TFTP Option Negotiation Analysis TFTP Option Extension TFTP Blocksize Option TFTP Timeout Interval and Transfer Size Options Description TFTP is a simple file transfer protocol that is primarily used for an automated transfer of configuration or boot files between machines in a local environment, i.e. remote boot of systems that do not have any data storage services. It is an element of the Preboot Execution Environment (PXE) network boot protocol, where it is implemented in the firmware ROM / NVRAM of the host's network card. TFTP provides no authentication and is, therefore, unsuitable for use over Internet connections. External links • http://en.wikipedia.org/wiki/TFTP V1.0 2013-01-15 Page 97 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot SFTP Profile Reference Name Categories SFTP SSH File Transfer Protocol Communications Protocols; General Purpose Protocol; File Transfer; IETF ICS 35.110 - Networking Abstract The SSH File Transfer Protocol provides secure (encrypted) file transfer over any reliable data stream. Current Version 6 Other editions AAL Relevance can be used for the exchange of information between components of an AAL system Available from http://tools.ietf.org/html/draft-ietf-secsh-filexfer-13 Description SFTP is a part of the Secure Shell (SSH) protocol suite and offers an FTP-like functionality over encrypted SSH connections, i.e. offering confidentiality and integrity of transmission and authentication of the sending and receiving system or user. The protocol has only Internet Draft status but is widely used in practice. External links • http://en.wikipedia.org/wiki/SSH_file_transfer_protocol TLS Profile Reference Name Categories RFC 5276 Transport Layer Security (TLS) Communication Protocols; General Purpose Protocols; File Transfer; IETF ICS 35.110 - Networking Abstract TLS is a cryptographic protocol that enables secure point-to-point communication over unsecure networks such as the Internet Current Version 1.2 Other editions AAL Relevance can be used for a secure exchange of information between components of an AAL system, in particular over Internet connections Available from http://tools.ietf.org/html/rfc3501 V1.0 2013-01-15 Page 98 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard RFC 5276 RFC 5746 RFC 5878 RFC 6176 Title The Transport Layer Security (TLS) Protocol Version 1.2 Transport Layer Security (TLS) Renegotiation Indication Extension Transport Layer Security (TLS) Authorization Extensions Prohibiting Secure Sockets Layer (SSL) Version 2.0 Description The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping,tampering, or message forgery. The goals of TLS Protocol, in order of their priority, are: 1. Cryptographic security: TLS should be used to establish a secure connection between two parties. 2. Interoperability: Independent programmers should be able to develop applications utilizing TLS that will then be able to successfully exchange cryptographic parameters without knowledge of one another's code. 3. Extensibility: TLS seeks to provide a framework into which new public key and bulk encryption methods can be incorporated as necessary. This will also accomplish two sub-goals: to prevent the need to create a new protocol (and risking the introduction of possible new weaknesses) and to avoid the need to implement an entire new security library. 4. Relative efficiency: Cryptographic operations tend to be highly CPU intensive, particularly public key operations. For this reason, the TLS protocol has incorporated an optional session caching scheme to reduce the number of connections that need to be established from scratch. Additionally, care has been taken to reduce network activity. External links • http://en.wikipedia.org/wiki/Transport_Layer_Security Control DPWS Profile Reference Name Categories ICS Abstract V1.0 OASIS DPWS DPWS: Devices Profile for Web Services Communication Protocol, General Purpose Protocol, Control; Communication Protocol, Ad-hoc networks; Runtime Environment 35.110 - Networking DPWS is a web-service protocol for communication between different devices. 2013-01-15 Page 99 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version 1.1 Other editions AAL Relevance DPWS can be used to implement service calls between different components of an AAL system, partly implemented in resource-limited embedded devices Available from http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01 Description The Devices Profile for Web Services (DPWS) is also sometimes called Web Services for Devices (WSD). A PC or other device can detect DPWS-enabled devices on a network, then discover and invoke the Web service functionality each device provides. DPWS has been developed with implementation on resource-limited embedded devices in mind. In Web Services terms, a “profile” is a set of guidelines for how to use Web Services technologies for a given purpose. The Web Services standards allow implementers to choose from a variety of message representations, text encodings, transport protocols, and other options, some of which are not mutually interoperable. By constraining these decisions, profiles ensure that implementations conforming to the profile will work well together. DPWS provides the following functionality between compatible devices: • Discovering DPWS-capable devices on the network and the services they offer • Sending messages to DPWS-capable devices and receiving replies • Describing a Web service by providing a WSDL file • Interacting with a service using its description • Subscribing to and receiving events from a Web service Devices can be DPWS clients (invoking services on devices), servers (providing services), or both. External links • http://msdn.microsoft.com/en-us/library/dd170125.aspx • http://en.wikipedia.org/wiki/DPWS SIP Profile Reference Name Categories ICS Abstract V1.0 RFC 3261 SIP: Session Initiation Protocol Communication Protocol; General Purpose Protocols; Control; IETF 35.110 - Networking SIP is an application-layer control (signalling) protocol for creating, modifying, and terminating sessions with one or more participants. 2013-01-15 Page 100 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. Current Version see Standard Parts below Other editions AAL Relevance enables Teleconference, Multimedia, Messages etc. Available from see Standard Parts below Standard Parts Standard RFC 3261 RFC 3842 RFC 2976 RFC 3428 RFC 2848 RFC 3262 RFC 3903 RFC 3515 RFC 2848 RFC 3311 RFC 3265 RFC 2976 RFC 3050 RFC 3087 RFC 3261 RFC 3262 RFC 3263 RFC 3264 RFC 3265 RFC 3311 RFC 3312 RFC 3313 RFC 3319 RFC 3323 RFC 3324 RFC 3325 V1.0 Title SIP: Session Initiation Protocol SIP Message Waiting Indication SIP Method Info SIP Method Message The PINT Service Protocol: extensions to SIP and SDP for IP Access to Telephone Call Service SIP Method pack SIP Method Publish SIP Method Refer SIP Method Subscribe and Unsubscribe SIP method Update SIP Specific Event Notification The SIP INFO Method Common Gateway Interface for SIP Control of Service Context using SIP Request-URI SIP: Session Initiation Protocol (Main SIP RFC) Reliability of Provisional Responses in the Session Initiation Protocol (SIP) Session Initiation Protocol (SIP): Locating SIP Servers An Offer/Answer Model with the Session Description Protocol (SDP) Session Initiation Protocol (SIP)-Specific Event Notification The Session Initiation Protocol (SIP) UPDATE Method Integration of Resource Management and Session Initiation Protocol (SIP) Private Session Initiation Protocol (SIP) Extensions for Media Authorization Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers A Privacy Mechanism for the Session Initiation Protocol (SIP) Short Term Requirements for Network Asserted Identity Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks 2013-01-15 Page 101 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot RFC 3326 RFC 3319 The Reason Header Field for the Session Initiation Protocol (SIP) Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts Security Mechanism Agreement for the Session Initiation Protocol (SIP) Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers Grouping of Media Lines in the Session Description Protocol (SDP) Internet Media Type message/sipfrag Session Initiation Protocol (SIP) Extension for Instant Messaging The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signalling Compression (SigComp) Compressing the Session Initiation Protocol (SIP) Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) Refer Method Mapping of Media Streams to Resource Reservation Flows The tel URI for Telephone Numbers Number Portability Parameters for the “tel” URI RFC 3327 RFC 3329 RFC 3361 RFC 3388 RFC 3420 RFC 3428 RFC 3485 RFC 3486 RFC 3487 RFC 3515 RFC 3524 RFC 3966 RFC 4964 Description Session Initiation Protocol (SIP) is an application-layer control (signalling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. SIP invitations used to create sessions carry session descriptions that allow participants to agree on a set of compatible media types. SIP makes use of elements called proxy servers to help route requests to the user's current location, authenticate and authorize users for services, implement provider call-routing policies, and provide features to users. SIP also provides a registration function that allows users to upload their current locations for use by proxy servers. SIP runs on top of several different transport protocols. External links • http://www.voip-info.org/wiki/view/SIP • http://en.wikipedia.org/wiki/Session_Initiation_Protocol UPnP Profile Reference Name V1.0 UPnP UPnP: Universal Plug and Play 2013-01-15 Page 102 of 490 AALIANCE2 Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot Communication Protocols; General Purpose; Control; Ad-hoc networks; Runtime Environment; ISO; IEC 35.200: Interface and interconnection equipment Universal Plug and Play (UPnP) is a set of networking protocols that allows networked devices, such as personal computers, printers, Internet gateways,Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment. 1.0 Help to create a network of interconnected devices ISO/IEC 29341-1:2011 Description ISO/IEC 29341-1:2011(E) Information technology – UPnP Device Architecture – Part 1: UPnP Device Architecture Version 1.0 Defines UPnP technology which describes an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, and PCs of all form factors. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces, or attached to the Internet. UPnP technology provides a distributed, open networking architecture that leverages TCP/IP and the Web technologies to enable seamless proximity networking in addition to control and data transfer among networked devices. The UPnP Device Architecture (UDA) is designed to support zeroconfiguration, “invisible” networking, and automatic discovery for a breadth of device categories from a wide range of vendors. A device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. Finally, a device can leave a network smoothly and automatically without leaving any unwanted state behind. The technologies leveraged in the UPnP architecture include Internet protocols such as IP, TCP, UDP, HTTP, and XML. Like the Internet, contracts are based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. This International Standard replaces ISO/IEC 29341-1, first edition, published in 2008, and constitutes a technical revision. External links • http://en.wikipedia.org/wiki/Upnp Addressing SSDP Profile Reference Name V1.0 SSDP SSDP: Simple Service Discovery Protocol 2013-01-15 Page 103 of 490 AALIANCE2 Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot Communication Protocols; General Purpose protocols; Addressing; IETF SSDP provides a mechanism where by network clients, with little or no static configuration, can discover network services. SSDP accomplishes this by providing for multicast discovery support as well as server based notification and discovery routing. 1.0 dynamic discovery and invocation of services https://tools.ietf.org/html/draft-cai-ssdp-v1-03 Description The Simple Service Discovery Protocol (SSDP) is a network protocol based on the Internet Protocol Suite for advertisement and discovery of network services and presence information. It accomplishes this without assistance of server-based configuration mechanisms, such as the Dynamic Host Configuration Protocol (DHCP) or the Domain Name System (DNS), and without special static configuration of a network host. SSDP is the basis of the discovery protocol of Universal Plug and Play and is intended for use in residential or small office environments. It was formally described in an IETF Internet draft by Microsoft and Hewlett-Packard in 1999. Although the IETF proposal has since expired, SSDP was incorporated into the UPnP protocol stack, and a description of the final implementation is included in UPnP standards documents. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Zeroconf Profile Reference Name Zeroconf Zeroconf: Zero Configuration Networking (also Automatic Private IP Addressing; APIPA or Auto-IP) Categories Communication Protocols; General Purpose protocols; Addressing; IETF ICS 35.110 - Networking Abstract Zero configuration networking (Zeroconf) is a set of techniques that automatically creates a usable Internet Protocol (IP) network without manual operator intervention or special configuration servers. Current Version Other editions AAL Relevance auto-configuration of AAL systems components V1.0 2013-01-15 Page 104 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from http://www.zeroconf.org/ Standard Parts Standard RFC 3927 RFC 4862 RFC 5227 http://files.zeroconf.org/draft-ietfzeroconf-reqts-12.txt http://files.zeroconf.org/draft-ietfzeroconf-host-prof-01.txt http://files.zeroconf.org/draft-ietfzeroconf-zmaap-02.txt http://files.zeroconf.org/draft-ietfzeroconf-zmaap-api-00.txt Title Dynamic Configuration of IPv4 Link-Local Addresses IPv6 Stateless Address Autoconfiguration IPv4 Address Conflict Detection Requirements for Automatic Configuration of IP Hosts Zeroconf Host Profile Applicability Statement Zeroconf Multicast Address Allocation Protocol (ZMAAP) An API for the Zeroconf Multicast Address Allocation Protocol (ZMAAP) Description Zero configuration networking (Zeroconf) is a set of techniques that automatically creates a usable Internet Protocol (IP) network without manual operator intervention or special configuration servers. Zero configuration networking allows devices such as computers and printers to connect to a network automatically. Without Zeroconf, a network administrator must set up services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), or configure each computer's network settings manually, which may be difficult and time-consuming. Zeroconf is built on three core technologies: • Assignment of numeric network addresses for networked devices • Automatic resolution and distribution of computer hostnames • Automatic location of network services, such as printing devices The IETF Zeroconf Working Group was chartered September 1999 and held its first official meeting at the 46th IETF in Washington, D.C., in November 1999. By the time the Working Group completed its work on Dynamic Configuration of IPv4 Link-Local Addresses and wrapped up in July 2003, IPv4LL was implemented and shipping in Mac OS (9 & X), Microsoft Windows (98, ME, 2000, XP, 2003), in every network printer from every major printer vendor, and in many assorted network devices from a variety of vendors. IPv4LL is available for Linux and for embedded operating systems. If you're making a networked device today, there's no excuse not to include IPv4 Link-Local Addressing. The specification for IPv4 Link-Local Addressing is complete (RFC3927), but the work to improve network ease-of-use (Zero Configuration Networking) continues. That means making it possible to take two laptop computers, and connect them with a crossover Ethernet cable, and have them communicate usefully using IP, without needing a man in a white lab coat to set it all up for you. Zeroconf is not limited to networks with just two hosts, but as we scale up our technologies to larger networks, we always have to be sure we haven't forgotten the two-devices (and no DHCP server) case. V1.0 2013-01-15 Page 105 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot [Source: www.zeroconf.org] External links • http://www.zeroconf.org/ • http://en.wikipedia.org/wiki/Zero_configuration_networking Management DHCP Profile Reference Name Categories DHCP DHCP: Dynamic Host Configuration Protocol Communication Protocols; General Purpose Protocol; Management; IETF ICS Abstract The Dynamic Host Configuration Protocol (DHCP)provides a framework for passing configuration information to hosts on a TCP/IP network Current Version Other editions AAL Relevance It enables an automatically configuration of devices Available from http://tools.ietf.org/html/rfc2132 Description In telecommunications and informatics the Dynamic Host Configuration Protocol (DHCP) is a network protocol (dynamic IP) that allows devices or terminals (host) of a certain local area to receive the configuration necessary to establish a connection and operate on a wider network based on Internet Protocol (IP), in order to prevent duplicate addresses. Each address have to be unique External links • http://en.wikipedia.org/wiki/Dhcp DNS Profile Reference Name Categories V1.0 DNS DNS: Domain Name System Communication Protocols; General Purpose Protocol; Management; IETF 2013-01-15 Page 106 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract The goal of domain names is to provide a mechanism for naming resources in such a way that the names are usable in different hosts, networks,protocol families, internet, and administrative organizations. Current Version see Standard Parts below Other editions AAL Relevance The access to computer over the internet using names instead of numbers Available from see Standard Parts below Standard Parts Standard RFC 1034 RFC 1035 Title DOMAIN NAMES - CONCEPTS AND FACILITIES DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION Description DNS protocol is utilized to identify servers by their IP addresses and aliases given their registered name. The request is usually simple, including just the name of the server. The response however is usually very complex because it contains all the addresses and aliases that the server might have. Because of this a compression algorithm is utilized in all cases to reduce the number of redundant data and the size of the datagrams. UDP is utilized to send and receive DNS requests. External links • http://en.wikipedia.org/wiki/Domain_Name_System DDNS Profile Reference Name Categories DDNS(DynDNS) DDNS - Dynamic Domain Name System Communication Protocols; General Purpose Protocol; Management; IETF ICS Abstract Dynamic DNS or DDNS is a method of updating, in real time, a Domain Name System (DNS) to point to a changing IP address on the Internet. This is used to provide a persistent domain name for a resource that may change location on the network. Current Version Other editions AAL Relevance DDNS is a protocol to assign an IP addresses to each computer or devices which are connected to a network and DDNS is a system that addresses the problem of rapid updates, could be useful when there V1.0 2013-01-15 Page 107 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot are some domains which change position inside the network. Available from http://tools.ietf.org/html/rfc2136 Description Dynamic DNS or DDNS is a method of updating, in real time, a Domain Name System (DNS) to point to a changing IP address on the Internet. This is used to provide a persistent domain name for a resource that may change location on the network. There are two very different mechanisms the term is used to describe. At the administration levels of the internet, “dynamic DNS updating” refers to systems that are used to update traditional DNS records without manual editing. These mechanisms are explained in RFC 2136 and use the TSIG mechanism to provide security. The second sort of DDNS is a particular type of DNS server that allows lightweight and immediate updates to its local database, often using a web-based form. These are used by individuals and small systems. External links • http://en.wikipedia.org/wiki/Ddns NAT-PMP Profile Reference Name NAT-PMP NAT-PMP: NAT Port Mapping Protocol (NAT: Network Address Translation) Categories Communication Protocol; General Purpose Protocol; Management; IETF ICS Abstract the NAT Port Mapping Protocol promoted by Apple computer and integrated in recent AirPort wireless routers/access points and in Mac OS X is an alternative to the much less elegant UPnP IGD (Internet Gateway Device) specification. Current Version Other editions AAL Relevance It’s a protocol for the automatic configuration port Available from http://tools.ietf.org/html/draft-cheshire-nat-pmp-03 Description The NAT Port Mapping Protocol promoted by Apple computer and integrated in recent AirPort wireless routers/access points and in Mac OS X is an alternative to the much less elegant UPnP IGD (Internet Gateway Device) specification. NAT-PMP is part of the Bonjour protocol specifications. Below is the description of the protocol as found in the internet draft (i.e. RFC draft) first published by Apple Computer in September 2005, and last updated in 2008. All the versions are available on IEFT web site : tools.ietf.org/html/draft-cheshire-nat-pmp-03. It is designed to work on small NATed LANs : V1.0 2013-01-15 Page 108 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot A domestic network with one wireless router and a few devices with private IP addresses, as defined in RFC1918. In NAT-PMP, the service is provided by the default gateway of the network which is the router connecting the private network to the outside world. The clients send their request in the form of UDP packets to the port 5351 of the default gateway. So there is no need for a discovery process as it is the case within the UPnP IGD specification. External links • http://en.wikipedia.org/wiki/NAT-PMP UPnP Profile Reference Name Categories UPnP UPnP: Universal Plug and Play Communication Protocols; General Purpose; Control; Ad-hoc networks; Runtime Environment; ISO; IEC ICS 35.200: Interface and interconnection equipment Abstract Universal Plug and Play (UPnP) is a set of networking protocols that allows networked devices, such as personal computers, printers, Internet gateways,Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment. Current Version 1.0 Other editions AAL Relevance Help to create a network of interconnected devices Available from ISO/IEC 29341-1:2011 Description ISO/IEC 29341-1:2011(E) Information technology – UPnP Device Architecture – Part 1: UPnP Device Architecture Version 1.0 Defines UPnP technology which describes an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, and PCs of all form factors. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces, or attached to the Internet. UPnP technology provides a distributed, open networking architecture that leverages TCP/IP and the Web technologies to enable seamless proximity networking in addition to control and data transfer among networked devices. The UPnP Device Architecture (UDA) is designed to support zeroconfiguration, “invisible” networking, and automatic discovery for a breadth of device categories from a wide range of vendors. A device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. Finally, a device can leave a network smoothly and automatically without leaving any unwanted state behind. The technologies leveraged in the UPnP architecture include Internet protocols such as IP, TCP, UDP, HTTP, and XML. Like the Internet, V1.0 2013-01-15 Page 109 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot contracts are based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. This International Standard replaces ISO/IEC 29341-1, first edition, published in 2008, and constitutes a technical revision. External links • http://en.wikipedia.org/wiki/Upnp OMA DM Profile Reference Name Categories ICS Abstract OMA DM OMA DM: OMA - Device Management (Open Mobile Alliance) Communication Protocols; General Purpose Protocol; Management OMA DM help the user to device management, device diagnostic, update , software installation and other application Current Version 1.1.2 Other editions AAL Relevance OMA DM could be helpful in various scenario, for instance: say a device resets accidentally and the user has no idea how to reconfigure it. If your device management server contains the required information and can reset the device for the user, it saves both time and cost. Available from http://www.ibm.com/developerworks/wireless/library/wi-oma/ Description The Open Mobile Alliance (OMA) was formed in June 2002 by nearly 200 companies that play important roles in the mobile industry's value chain. The alliance focuses on developing interoperable mobile service enablers, and becomes the focal point in device management by consolidating several organizations into OMA, including SyncML Initiatives and WAP Forum. SyncML DM, which was one of SyncML's main specifications, has evolved into OMA DM. OMA's Device Management Working Group is in charge of the revision and publication of OMA Device Management. OMA DM has the approved enabler, version 1.1.2, and is currently working on the candidate enabler, version 1.2. OMA DM 1.2 contains the Enabler Release Definition for OMA DM, along with eight technical specifications and two supporting files. Enabler Release Definition mainly defines the scope of OMA DM, and the server and client requirements to conform to OMA DM. Technical specifications consist of three parts: data models, protocol and mechanism, and policy. In the following section, we discuss in detail data models, protocols, and mechanisms intermixing with version 1.2 policy concepts. In the end, device management aims to achieve these important function requirements: • Bootstrap provisioning, remote maintenance, and reporting of configuration data to a device • Device diagnostics and fault management V1.0 2013-01-15 Page 110 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Application and non-application software installation, update, and management External links • http://en.wikipedia.org/wiki/OMA_DM SNMP Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from SNMP SNMP: Simple Network Management Protocol Communication Protocol; General purpose protocol; Management; IETF Simple Network Management Protocol (SNMP) is one of the standard operations and maintenance protocols for the Internet. Its task is the configuration, management, and supervision of a network device. 3 Management of the network device see Standard Parts below Standard Parts Standard RFC3410 RFC3411 RFC3412 RFC3413 RFC3414 RFC3415 RFC3416 RFC3417 RFC3584 RFC3826 RFC5343 RFC5590 RFC5591 V1.0 Title Introduction and Applicability Statements for Internet Standard Management Framework An Architecture for Describing SNMP Management Frameworks Message Processing and Dispatching SNMP Applications User-based Security Model View-based Access Control Model Version 2 of the Protocol Operations for the Simple Network Management Protocol Transport Mappings Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model Simple Network Management Protocol (SNMP) Context EngineID Discovery Transport Subsystem for the Simple Network Management Protocol (SNMP) Transport Security Model for the Simple Network Management Protocol 2013-01-15 Page 111 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot RFC5593 (SNMP) Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) Description The Simple Network Management Protocol (SNMP) is by far the dominant protocol in network management. This Protocol (SNMP) was designed to be an easily implementable, basic network management tool that could be used to meet network management needs. It is named Simple Network Management Protocol as it is really easy to understand. A key reason for its widespread acceptance, besides being the chief Internet standard for network management, is its relative simplicity. There are different versions of SNMP, such as SNMP V1, SNMP V2c, and SNMP V3. Implementing SNMP management in a networked device is far more straightforward than most other standard or non-standard approaches to network management. Despite that, SNMP application development has not been as simple as one would like it to be. It has required significant effort to develop management applications to manage a variety of networked devices to be managed. This situation is now changing for the better, as more SNMP tools become available. With improved tools, SNMP is poised to deliver end-to-end management for all areas of the growing inter-networking industry. Thus SNMP has become the dominant standardized network management scheme in use today. The SNMP set of standards provides a framework for the definition of management information along with a protocol for the exchange of that information. The SNMP model assumes the existence of Managers and Agents. External links • http://www.webnms.com/cagent/help/technology_used/c_snmp_overview.html • http://www.snmp.com/protocol/snmp_rfcs.shtml • http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol CWMP Profile Reference Name CWMP CWMP - Customer Premises Equipment (CPE) Wan Management Protocol Categories Communication Protocols; General Purpose Protocols; Management ICS Abstract The basic idea behind CWMP is computer-aided management and configuration of Customer Premises Equipment (CPE). The CWMP protocol helps you to reduce costs for management and support of your devices. The CWMP can be divided into several sub-protocols Current Version see Standard Parts below V1.0 2013-01-15 Page 112 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance Through these protocols heterogeneous devices are put in contact with each other in order to enable the communication. Available from see Standard Parts below Standard Parts Standard TR-069 TR-106 TR-098 TR-104 TR-135 TR-140 TR-111 Title describes the main concept of configuration, management and monitoring via CWMP; the RPC method scope for CPE as well as for ACS and the transport mechanisms (HTTP/HTTPS) of RPC calls between ACS and CPE) describes the generic design of a data model (parameter stack) for a device specific data model for Internet Gateway Devices, like Routers, Modems, etc. specific data model for Voice-over-IP (VoIP) devices specific data model for IP-TV Set-Top-Boxes (STB) specific data model for (Network Attached) File Storage Devices (NAS) describes a way to configure devices located behind a CWMP-enabled NAT gateway Description The basic idea behind CWMP is computer-aided management and configuration of Customer Premises Equipment (CPE). The CWMP protocol helps you to reduce costs for management and support of your devices. It's main purposes are: • Configuration of devices • Monitoring and diagnostic of devices • Firmware upgrade management • These tasks are accomplished by Remote Procedure Calls (RPC) between an AutoConfiguration Server (ACS) and a CPE. As transport protocol for the RPC calls HTTP (HTTPS) is being used. Typical situations in which you may want to make use of CWMP are: • Automated initial configuration of CPE, as soon as a customer plugs in a device • Assisted configuration of a device on any kind of error • Re-Configuration or factory resetting of a device in case of an urgent problem • Rebooting a device • Upgrading the firmware of a device (or a whole bunch of devices) The CWMP can be divided into several sub-protocols. The main subprotocol are reported into the table. These protocols are the standard for remote configuration of devices in the market of DLS broadband V1.0 2013-01-15 Page 113 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.axiros.com/knowledge-base/faqs-on-device-mgmt/cpe-wan-managementprotocol-tr-069.html?no_cache=1 • http://en.wikipedia.org/wiki/Cwmp LDAP Profile Reference Name Categories LDAP LDAP: Lightweight Directory Access Protocol Communication Protocol; General Purpose protocol; Management; Other; IETF ICS Abstract The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Current Version 3 Other editions AAL Relevance Standard protocol that allows access to data info of users connected to a network Available from see Standard Parts below Standard Parts Standard RFC2251 RFC4150 RFC4511 RFC4512 RFC4513 RFC4514 RFC4515 RFC4516 RFC4517 RFC4518 V1.0 Title Lightweight Directory Access Protocol (v3) Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map Lightweight Directory Access Protocol (LDAP): The Protocol Lightweight Directory Access Protocol (LDAP): Directory Information Model Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanism Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation 2013-01-15 Page 114 of 490 AALIANCE2 RFC4519 D4.1 Online Repository of Standards - Snapshot Lightweight Directory Access Protocol (LDAP): Schema for User Applications Description The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. Key aspects of LDAP are: • Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead. • Many protocol data elements are encoding as ordinary strings (e.g., Distinguished Names). • A lightweight BER encoding is used to encode all protocol elements. SysLog Profile Reference Name Categories SysLog SysLog: System Log Communication Protocol; General Purpose Protocols; Management; IETF ICS Abstract the syslog protocol is a standard for data logging, which is used to convey event notification messages. It is used much more in Unix System than in Windows Current Version see Standard Parts below Other editions AAL Relevance Can Log and Storage easily data from various type of devices. Available from see Standard Parts below Standard Parts Standard RFC3164 RFC5424 Title The BSD syslog Protocol The SysLog Protocol Description Since the beginning, life has relied upon the transmission of messages. For the self-aware organic unit, these messages can relay many different things. The messages may signal danger, the presence of food or the other necessities of life, and many other things. In many cases, these messages are informative to other units and require no V1.0 2013-01-15 Page 115 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot acknowledgement. As people interacted and created processes, this same principle was applied to societal communications. As an example, severe weather warnings may be delivered through any number of channels - a siren blowing, warnings delivered over television and radio stations, and even through the use of flags on ships. The expectation is that people hearing or seeing these warnings would realize their significance and take appropriate action. In most cases, no responding acknowledgement of receipt of the warning is required or even desired. Along these same lines, operating systems, processes and applications were written to send messages of their own status, or messages to indicate that certain events had occurred. These event messages generally had local significance to the machine operators. As the operating systems, processes and applications grew ever more complex, systems were devised to categorize and log these diverse messages and allow the operations staff to more quickly differentiate the notifications of problems from simple status messages. The syslog process was one such system that has been widely accepted in many operating systems. Flexibility was designed into this process so the operations staff have the ability to configure the destination of messages sent from the processes running on the device. In one dimension, the events that were received by the syslog process could be logged to different files and also displayed on the console of the device. In another dimension, the syslog process could be configured to forward the messages across a network to the syslog process on another machine. The syslog process had to be built network-aware for some modicum of scalability since it was known that the operators of multiple systems would not have the time to access each system to review the messages logged there. The syslog process running on the remote devices could therefore be configured to either add the message to a file, or to subsequently forward it to another machine. In its most simplistic terms, the syslog protocol provides a transport to allow a machine to send event notification messages across IP networks to event message collectors - also known as syslog servers. Since each process, application and operating system was written somewhat independently, there is little uniformity to the content of syslog messages. For this reason, no assumption is made upon the formatting or contents of the messages. The protocol is simply designed to transport these event messages. In all cases, there is one device that originates the message. The syslog process on that machine may send the message to a collector. No acknowledgement of the receipt is made. One of the fundamental tenets of the syslog protocol and process is its simplicity. No stringent coordination is required between the transmitters and the receivers. Indeed, the transmission of syslog messages may be started on a device without a receiver being configured, or even actually physically present. Conversely, many devices will most likely be able to receive messages without explicit configuration or definitions. This simplicity has greatly aided the acceptance and deployment of syslog. External links • http://en.wikipedia.org/wiki/Syslog V1.0 2013-01-15 Page 116 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot File System AFP Profile Reference Name Categories ICS Abstract AFP AFP: Apple Filing Protocol Communication Protocol; General Purpose protocol; File System The Apple Filing Protocol (AFP) allows users of multiple computers to share files easily and efficiently over a network. Current Version 3 Other editions AAL Relevance AFP commands can be issued directly by the local computer, or translated from the local computer's command language. The algorithms convert the commands into actions. Available from https://developer.apple.com/library/mac/#documentation/networking/co nceptual/afp/Introduction/Introduction.html Description The Apple Filing Protocol (AFP), formerly AppleTalk Filing Protocol, is a proprietary network protocol that offers file services for Mac OS X and original Mac OS. In Mac OS X, AFP is one of several file services supported including Server Message Block (SMB), Network File System (NFS), File Transfer Protocol (FTP), and WebDAV. AFP currently supports Unicode file names, POSIX and access control list permissions, resource forks, named extended attributes, and advanced file locking. In Mac OS 9 and earlier, AFP was the primary protocol for file services. External links • http://en.wikipedia.org/wiki/Apple_Filing_Protocol NFS Profile Reference Name Categories ICS Abstract V1.0 NFS NFS: Network File System Communication Protocol; General Purpose Protocols; File System; IETF NFS allowing a user on a client computer to access files over a network in a manner similar to how local storage is accessed. It is usually used on Unix system, but it is often use also in windows system. 2013-01-15 Page 117 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version 4 Other editions AAL Relevance NFS allowing a server to share file, directory and file system with a client which have made the request Available from http://www.rfc-editor.org/rfc/rfc3530.txt Description The operation of NFS is defined in the form of three main components that can be viewed as logically residing at each of the three OSI model layers corresponding to the TCP/IP application layer (see Figure 253). These components are: • Remote Procedure Call (RPC): RPC is a generic session layer service used to implement client/server internetworking functionality. It extends the notion of a program calling a local procedure on a particular host computer, to the calling of a procedure on a remote device across a network. • External Data Representation (XDR): XDR is a descriptive language that allows data types to be defined in a consistent manner. XDR conceptually resides at the presentation layer; its universal representations allow data to be exchanged using NFS between computers that may use very different internal methods of storing data. • NFS Procedures and Operations: The actual functionality of NFS is implemented in the form of procedures and operations that conceptually function at layer seven of the OSI model. These procedures specify particular tasks to be carried out on files over the network, using XDR to represent data and RPC to carry the commands across an internetwork. These three key “subprotocols” if you will, comprise the bulk of the NFS protocol. Each is described in more detail in a separate topic of this section on NFS. The NFS version 4 protocol is a further revision of the NFS protocol defined already by versions 2 [RFC1094] and 3 [RFC1813]. It retains the essential characteristics of previous versions: design for easy recovery, independent of transport protocols, operating systems and filesystems, simplicity, and good performance. The NFS version 4 revision has the following goals: • Improved access and good performance on the Internet. The protocol is designed to transit firewalls easily, perform well where latency is high and bandwidth is low, and scale to very large numbers of clients per server. • Strong security with negotiation built into the protocol. • Good cross-platform interoperability. The protocol features a filesystem model that provides a useful, common set of features that does not unduly favour one filesystem or operating system over another. • Designed for protocol extensions. The protocol is designed to accept standard extensions that do not compromise backward compatibility. External links http://en.wikipedia.org/wiki/Network_File_System V1.0 2013-01-15 Page 118 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot SMB Profile Reference Name Categories SMB SMB: Server Message Block Communication Protocols; General Purpose Protocols; File System; Printing ICS Abstract SMB, which stands for Server Message Block, is a protocol for sharing files, printers, serial ports, and communications abstractions such as named pipes and mailslots between computers. Commonly used on Windows systems. Current Version 3.0 Other editions AAL Relevance SMB uses client-server approach. It is optimized for local network, but it could be used also for internet applications. It could be useful in case of communication between two nodes of the network. Available from http://msdn.microsoft.com/en-us/library/cc246482.aspx Description Stands for “Server Message Block.” SMB is a network protocol used by Windows-based computers that allows systems within the same network to share files. It allows computers connected to the same network or domain to access files from other local computers as easily as if they were on the computer's local hard drive. Not only does SMB allow computers to share files, but it also enables computers to share printers and even serial ports from other computers within the network. For example, a computer connected to a Windows network could print a document on a printer connected to another computer on the network, as long as both machines support the SMB protocol. Though SMB was originally developed for Windows, it can also be used by other platforms, including Unix and Mac OS X, using a software implementation called Samba. By using Samba instructions, Mac, Windows, and Unix computers can share the same files, folders, and printers. This is great for those Windows-based office networks where there is a graphic designer who refuses to use anything but a Mac and a tech guy who does everything on his Linux machine. External links • http://www.samba.org/cifs/docs/what-is-smb.html • http://msdn.microsoft.com/en-us/library/cc212363.aspx • http://msdn.microsoft.com/en-us/library/cc212614.aspx • http://en.wikipedia.org/wiki/Server_Message_Block V1.0 2013-01-15 Page 119 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot WebDAV Profile Reference Name Categories WebDAV WebDAV: Web-based Distributed Authoring and Versioning Communication Protocol; General Purpose Protocols; File System; IETF ICS Abstract Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance) Current Version see Standard Parts below Other editions AAL Relevance WebDAV protocol makes the Web a readable and writeable medium. It provides a framework for users to create, change and move documents on a server. Available from see Standard Parts below Standard Parts Standard RFC3253 RFC4918 RFC5397 Title Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) WebDAV Current Principal Extension Description The WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the complexity of clients that are capable of interoperating with a variety of versioning repository managers, to facilitate widespread deployment of applications capable of utilizing the WebDAV Versioning services. WebDAV versioning includes automatic versioning for versioning-unaware clients, version history management, workspace management, baseline management, activity management, and URL namespace versioning. External links • http://en.wikipedia.org/wiki/Webdav V1.0 2013-01-15 Page 120 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot DCE/DFS Profile Reference Name DCE/DFS DCE/RPC : Distributed Computing Environment / Distribuited File System Categories Communication protocol; General Purpose Protocol; File System ICS Abstract DCE/RPC is a protocol dedicate to remote files share, it is commonly used into distributed computing environment Current Version Other editions AAL Relevance This protocol is very fast even if the connection between two different devices is slow. Available from http://www.opengroup.org/dce/ Description The Distributed Computing Environment (DCE) is a software system developed in the early 1990s by a consortium that included Apollo Computer (later part of Hewlett-Packard), IBM, Digital Equipment Corporation, and others. The DCE supplies a framework and toolkit for developing client/server applications. The framework includes a remote procedure call (RPC) mechanism known as DCE/RPC, a naming (directory) service, a time service, an authentication service and a distributed file system (DFS) known as DCE/DFS. DCE was a big step in direction to standardisation of architectures, which were manufacturer dependent before. Transforming the concept in software for different platforms has been given up after a short period. Similar to the OSI model DCE was not granted success, the underlying concepts however prevailed. External links • http://en.wikipedia.org/wiki/Distributed_Computing_Environment Streaming AirPlay Profile Reference Name Categories ICS Abstract V1.0 AirPlay AirPlay Communication Protocol; General Purpose Protocol; Streaming AirPlay is a proprietary protocol developed by Apple. Allowing the possibility to share among devices connected on the same Home network wireless multimedia streaming of video, music and photo. 2013-01-15 Page 121 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot Multimedia streaming could be accessible from different devices http://nto.github.com/AirPlay.html Description AirPlay is a family of protocols implemented by Apple to view various types of media content on the Apple TV from any iOS device or iTunes. “iOS device” refers to an iPhone, iPod touch or iPad. The following scenarios are supported by AirPlay: • Display photos and slideshows from an iOS device. • Stream audio from an iOS device or iTunes. • Display videos from an iOS device or iTunes. • Show the screen content from an iOS device or OS X Mountain Lion. This is called AirPlay Mirroring. It requires hardware capable of encoding live video without taking too much CPU, so it is only available on iPhone 4S, iPad 2, the new iPad, and Macs with Sandy Bridge CPUs. Audio streaming is also supported from an iOS device or iTunes to an AirPort Express base station or a 3rd party AirPlay-enabled audio device. Initially this was called AirTunes, but it was later renamed to AirPlay when Apple added video support for the Apple TV. External links • http://en.wikipedia.org/wiki/AirPlay HTTP Profile Reference Name Categories HTTP HTTP: Hypertext Transfer Protocol Communications Protocols; General Purpose Protocol; File Transfer; Streaming; IETF ICS Abstract The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. It is a generic, stateless, objectoriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods (commands). Current Version see Standard Parts below Other editions AAL Relevance HTTP has been in use by the World-Wide Web global information Available from see Standard Parts below V1.0 2013-01-15 Page 122 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard RFC2616 RFC6585 Title Hypertext Transfer Protocol Additional HTTP Status Codes Description The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers [47]. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. External links • http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol RTP Profile Reference Name Categories ICS Abstract RTP RTP: Real-Time Transport Protocol Communication Protocols; General Purpose Protocols; Control; IETF RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services Current Version see Standard Parts below Other editions AAL Relevance Enables delivering audio and video over IP networks. Available from see Standard Parts below Standard Parts Standard RFC3550 RFC3551 STD 64 STD 65 Title RTP: A transport Protocol for Real-Time Applications RTP Profile for Audio and Video Conferences with Minimal Control RTP: A Transport Protocol for Real-Time Applications RTP Profile for Audio and Video Conferences with Minimal Control Description RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network V1.0 2013-01-15 Page 123 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot services. It’s based on UDP protocol. RTP does not address resource reservation and does not guarantee quality-of-service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. External links • http://en.wikipedia.org/wiki/Real-time_Transport_Protocol RTSP Profile Reference Name Categories ICS Abstract RTSP RTSP: RealTime Streaming Protocol Communication Protocols; General Purpose Protocols; Control; IETF RTSP is a protocol for control over the delivery of data with real-time properties Current Version Other editions AAL Relevance RTSP manage the streaming session of multimedia file from a server to client Available from http://tools.ietf.org/html/rfc2326 Description The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This protocol is intended to control multiple data delivery sessions, provide a means for choosing delivery channels such as UDP, multicast UDP and TCP, and provide a means for choosing delivery mechanisms based upon RTP External links • http://en.wikipedia.org/wiki/Rtsp RTMP Profile Reference Name V1.0 RTMP RTMP: Real Time Messaging Protocol 2013-01-15 Page 124 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories ICS Abstract Communication Protocol; General Purpose Protocols; Streaming The Real-Time Messaging Protocol (RTMP) was designed for highperformance transmission of audio, video, and data between Adobe Flash Platform technologies, including Adobe Flash Player and Adobe AIR. RTMP is now available as an open specification to create products and technology that enable delivery of video, audio, and data in the open AMF, SWF, FLV, and F4V formats compatible with Adobe Flash Player. Current Version 1.0 Other editions AAL Relevance Allowing the internet transmission of multimedia files. Available from http://www.adobe.com/devnet/rtmp.html Description Real Time Messaging Protocol (RTMP) was initially a proprietary protocol developed by Macromedia for streaming audio, video and data over the Internet, between a Flash player and a server. Macromedia is now owned by Adobe, which has released an incomplete version of the specification of the protocol for public use. RTMP is a TCP-based protocol which maintains persistent connections and allows lowlatency communication. To deliver streams smoothly and transmit as much information as possible, it splits streams into fragments and their size is negotiated dynamically between the client and server while sometimes it is kept unchanged: the default fragment sizes are 64-bytes for audio data, and 128 bytes for video data and most other data types. Fragments from different streams may then be interleaved, and multiplexed over a single connection. With longer data chunks the protocol thus carries only a one-byte header per fragment, so incurring very little overhead. However, in practice individual fragments are not typically interleaved. Instead, the interleaving and multiplexing is done at the packet level, with RTMP packets across several different active channels being interleaved in such a way as to ensure that each channel meets its bandwidth, latency, and other qualityof-service requirements. Packets interleaved in this fashion are treated as indivisible, and are not interleaved on the fragment level. External links • http://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol Printing CUPS Profile Reference Name Categories V1.0 CUPS CUPS: Common Unix Printing System Communication Protocol; General Purpose Protocol; Printing 2013-01-15 Page 125 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract CUPS is the standards-based, open source printing system developed by Apple Inc. for OS® X and other UNIX®-like operating systems. CUPS is the software you use to print from applications like the web browser you are using to read this page. It converts the page descriptions produced by your application (put a paragraph here, draw a line there, and so forth) into something your printer can understand and then sends the information to the printer for printing. Current Version 1.6.1 Other editions AAL Relevance Server PC printing the request of the client PC using CUPS protocol Available from http://www.cups.org/ Description CUPS is the software you use to print from applications like the web browser you are using to read this page. It converts the page descriptions produced by your application (put a paragraph here, draw a line there, and so forth) into something your printer can understand and then sends the information to the printer for printing. Now, since every printer manufacturer does things differently, printing can be very complicated. CUPS does its best to hide this from you and your application so that you can concentrate on printing and less on how to print. Generally, the only time you need to know anything about your printer is when you use it for the first time, and even then CUPS can often figure things out on its own The first time you print to a printer, CUPS creates a queue to keep track of the current status of the printer (everything OK, out of paper, etc.) and any pages you have printed. Most of the time the queue points to a printer connected directly to your computer via a USB port, however it can also point to a printer on your network, a printer on the Internet, or multiple printers depending on the configuration. Regardless of where the queue points, it will look like any other printer to you and your applications. Every time you print something, CUPS creates a job which contains the queue you are sending the print to, the name of the document you are printing, and the page descriptions. Job are numbered (queue-1, queue-2, and so forth) so you can monitor the job as it is printed or cancel it if you see a mistake. When CUPS gets a job for printing, it determines the best programs (filters, printer drivers, port monitors, and backends) to convert the pages into a printable format and then runs them to actually print the job. When the print job is completely printed, CUPS removes the job from the queue and moves on to any other jobs you have submitted. You can also be notified when the job is finished, or if there are any errors during printing, in several different ways. External links • http://en.wikipedia.org/wiki/Common_Unix_Printing_System IPP Profile Reference V1.0 IPP 2013-01-15 Page 126 of 490 AALIANCE2 Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot IPP: Internet Printing Protocol Communication Protocols; General Purpose Protocols; Printing; IETF IPP is a system based on a standard that allows printing from any remote PC to any accessible printer see Standard Parts below It enables the printing over internet connections see Standard Parts below Standard Parts Standard RFC3998 RFC3996 RFC3995 Title Internet Printing Protocol (IPP): Job and Printer Administrative Operations Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications Internet Printing Protocol (IPP):Event Notifications and Subscriptions Description The internet Printing Protocol (IPP) in an application level protocol that can be used for distributed printing using internet tools and technologies. IPP version 1.1 (RFC 2911, RFC 2910) focuses on end user functionality, with a few administrative operations included. This document defines additional OPTIONAL end user, operator, and administrator operations used to control Jobs and Printers. The IPP will be used to accommodate these four functions: • Allow a user to find out about a printer's capabilities • Allow a user to submit print jobs to a printer • Allow a user to find out the status of a printer or a print job • Allow a user to cancel a previously submitted job External links • http://en.wikipedia.org/wiki/Internet_Printing_Protocol SMB Profile Reference Name Categories ICS V1.0 SMB SMB: Server Message Block Communication Protocols; General Purpose Protocols; File System; Printing 2013-01-15 Page 127 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract SMB, which stands for Server Message Block, is a protocol for sharing files, printers, serial ports, and communications abstractions such as named pipes and mailslots between computers. Commonly used on Windows systems. Current Version 3.0 Other editions AAL Relevance SMB uses client-server approach. It is optimized for local network, but it could be used also for internet applications. It could be useful in case of communication between two nodes of the network. Available from http://msdn.microsoft.com/en-us/library/cc246482.aspx Description Stands for “Server Message Block.” SMB is a network protocol used by Windows-based computers that allows systems within the same network to share files. It allows computers connected to the same network or domain to access files from other local computers as easily as if they were on the computer's local hard drive. Not only does SMB allow computers to share files, but it also enables computers to share printers and even serial ports from other computers within the network. For example, a computer connected to a Windows network could print a document on a printer connected to another computer on the network, as long as both machines support the SMB protocol. Though SMB was originally developed for Windows, it can also be used by other platforms, including Unix and Mac OS X, using a software implementation called Samba. By using Samba instructions, Mac, Windows, and Unix computers can share the same files, folders, and printers. This is great for those Windows-based office networks where there is a graphic designer who refuses to use anything but a Mac and a tech guy who does everything on his Linux machine. External links • http://www.samba.org/cifs/docs/what-is-smb.html • http://msdn.microsoft.com/en-us/library/cc212363.aspx • http://msdn.microsoft.com/en-us/library/cc212614.aspx • http://en.wikipedia.org/wiki/Server_Message_Block Other CalDAV Profile Reference Name Categories ICS Abstract V1.0 CalDAV CalDAV Communications Protocols; General Purpose Protocol; Other; IETF CalDAV is an extensions to the Web Distributed Authoring and 2013-01-15 Page 128 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. Current Version Other editions AAL Relevance CalDAV is a diffuse protocol to share the agenda. A possible scenario in AAL context is that an entire family could synchronize their own agenda with elderly’s agenda in order to know if there are medicines, doctor or other relevant appointment. Available from http://www.ietf.org/rfc/rfc4791.txt Standard Parts Standard RFC 4791 Title Calendaring Extension to WebDAV (CalDAV) Description The following text is taken from wikipedia Calendaring Extensions to WebDAV, or CalDAV, is an Internet standard allowing a client to access scheduling information on a remote server. It extends WebDAV (HTTP-based protocol for data manipulation) specification and uses iCalendar format for the data. The protocol is defined by RFC 4791. It allows multiple client access to the same information thus allowing cooperative planning and information sharing. Many server and client applications support the protocol. The architecture of CalDAV (partially inherited from the underlying specifications) organizes the data (events, tasks, free-busy info, notes) in directories (collections), where multiple items (resources) reside. The resources and collections can be accessed by one or more users, using standard HTTP and DAV semantics to detect conflicting changes, or to provide locking. For access control the concept of ACLs are used, so each operation (view, edit, delete etc.) can be denied or granted per user. Therefore the specification requires that CalDAV servers must support “WebDAV Access Control Protocol” (RFC 3744). The calendar resources must use iCalendar format, which allows the server to understand and process the data. Parsing the iCalendar items is necessary, because the server has to support a number of calendaring-specific operations such as doing free-busy time reports and expansion of recurring events. With this functionality, a user may synchronize his or her own calendar to a CalDAV server, and share it among multiple devices or with other users. The protocol also supports non-personal calendars, such as calendars for sites or organizations. • CalDAV Port(s) 80, 443 • RFC(s) RFC 4791 • OSI layer Application External links • CalDav (Wikipedia) V1.0 2013-01-15 Page 129 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot LDAP Profile Reference Name Categories LDAP LDAP: Lightweight Directory Access Protocol Communication Protocol; General Purpose protocol; Management; Other; IETF ICS Abstract The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Current Version 3 Other editions AAL Relevance Standard protocol that allows access to datainfo of users connected to a network Available from see Standard Parts below Standard Parts Standard RFC2251 RFC4150 RFC4511 RFC4512 RFC4513 RFC4514 RFC4515 RFC4516 RFC4517 RFC4518 RFC4519 Title Lightweight Directory Access Protocol (v3) Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map Lightweight Directory Access Protocol (LDAP): The Protocol Lightweight Directory Access Protocol (LDAP): Directory Information Model Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanism Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation Lightweight Directory Access Protocol (LDAP): Schema for User Applications Description The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol V1.0 2013-01-15 Page 130 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. Key aspects of LDAP are: • Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead. • Many protocol data elements are encoding as ordinary strings (e.g., Distinguished Names). • A lightweight BER encoding is used to encode all protocol elements. 2.1.2 Ad-hoc Networks DPWS Profile Reference Name Categories OASIS DPWS DPWS: Devices Profile for Web Services Communication Protocol, General Purpose Protocol, Control; Communication Protocol, Ad-hoc networks; Runtime Environment ICS 35.110 - Networking Abstract DPWS is a web-service protocol for communication between different devices. Current Version 1.1 Other editions AAL Relevance DPWS can be used to implement service calls between different components of an AAL system, partly implemented in resource-limited embedded devices Available from http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01 Description The Devices Profile for Web Services (DPWS) is also sometimes called Web Services for Devices (WSD). A PC or other device can detect DPWS-enabled devices on a network, then discover and invoke the Web service functionality each device provides. DPWS has been developed with implementation on resource-limited embedded devices in mind. In Web Services terms, a “profile” is a set of guidelines for how to use Web Services technologies for a given purpose. The Web Services standards allow implementers to choose from a variety of message representations, text encodings, transport protocols, and other options, some of which are not mutually interoperable. By constraining these decisions, profiles ensure that implementations conforming to the profile will work well together. DPWS provides the following functionality between compatible devices: V1.0 2013-01-15 Page 131 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Discovering DPWS-capable devices on the network and the services they offer • Sending messages to DPWS-capable devices and receiving replies • Describing a Web service by providing a WSDL file • Interacting with a service using its description • Subscribing to and receiving events from a Web service Devices can be DPWS clients (invoking services on devices), servers (providing services), or both. External links • http://msdn.microsoft.com/en-us/library/dd170125.aspx • http://en.wikipedia.org/wiki/DPWS UPnP Profile Reference Name Categories UPnP UPnP: Universal Plug and Play Communication Protocols; General Purpose; Control; Ad-hoc networks; Runtime Environment; ISO; IEC ICS 35.200: Interface and interconnection equipment Abstract Universal Plug and Play (UPnP) is a set of networking protocols that allows networked devices, such as personal computers, printers, Internet gateways,Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment. Current Version 1.0 Other editions AAL Relevance Help to create a network of interconnected devices Available from ISO/IEC 29341-1:2011 Description ISO/IEC 29341-1:2011(E) Information technology – UPnP Device Architecture – Part 1: UPnP Device Architecture Version 1.0 Defines UPnP technology which describes an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, and PCs of all form factors. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces, or attached to the Internet. UPnP technology provides a distributed, open networking architecture that leverages TCP/IP and the Web technologies to enable seamless proximity networking in addition to control and data transfer among networked devices. The UPnP Device Architecture (UDA) is designed to support zeroconfiguration, “invisible” networking, and automatic discovery for a breadth of device V1.0 2013-01-15 Page 132 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot categories from a wide range of vendors. A device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. Finally, a device can leave a network smoothly and automatically without leaving any unwanted state behind. The technologies leveraged in the UPnP architecture include Internet protocols such as IP, TCP, UDP, HTTP, and XML. Like the Internet, contracts are based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. This International Standard replaces ISO/IEC 29341-1, first edition, published in 2008, and constitutes a technical revision. External links • http://en.wikipedia.org/wiki/Upnp 2.1.3 Medical Devices BlueRobin Profile Reference Name Categories ICS Abstract BlueRobin BlueRobin Communication Protocols; Medical Devices It’s a proprietary protocol developed by BM wireless LTd & Co.KG. The target of the BlueRobinTM protocol is to provide low data rates for wireless body area sensor networks and team monitoring systems at ultra-low power consumption combined with high reliability and low hardware costs. Current Version Other editions AAL Relevance It’s a low power wireless device. For instance it could be used for radio transmission of data from body sensors Available from Description Main Use Cases and Effective Data Rate The target of the BlueRobinTM protocol is to provide low data rates for wireless body area sensor networks and team monitoring systems at ultra-low power consumption combined with high reliability and low hardware costs. The effective data rate is selectable from 8 bits up to 256 bits per data packet with an interval between packet transmissions in the range of 500 ms up to 1 second. Current Consumption The transmitter and receiver current consumption is small enough to enable the realisation of body area systems consisting of a receiver and up to 3 transmitters that can be V1.0 2013-01-15 Page 133 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot operated with standard CR2032 batteries for more than 2 years¹. Following conditions apply: • Transmission distance at least 3 meters • System usage rate is one hour / day Reliability To reduce hardware costs and current consumption as much as possible the protocol is based on a unidirectional transmission, however for applications sensitive to data loss a bidirectional acknowledgement system including a smart packet collision avoidance method is available. To enhance data reliability in case of a unidirectional system redundant transmission including a patented packet collision minimization method is provided. If a sensor needs to be controlled and configured from the receiver side an optional messaging system allows sending data to the sensor. This feature causes a slightly increased current consumption on the sensor side. It also allows to switch sensors on and off from the receiver side in a very power efficient way. When using this messaging system, transceiver chips have to be used on both sides. Unique Serial Numbers and Type Specifiers To allow unique identification of transmitters, a type specifier and a serial number (also called transmitter ID) is assigned to every module. The type specifier is used to determine the kind of data a module delivers and therefore the way it has to be interpreted (i.e. speed data, heart rate data …). The serial number is unique for every transmitter. Both type specifier and serial number are contained in every data packet that is transmitted. External links http://www.bmwireless.com/index.php/bluerobin_bmwireless.html DICOM Profile Reference Name Categories DICOM DICOM: Digital Imaging and Communications in Medicine Communication Protocols; Medical Devices; File Formats and Persistent Data Structures; General Purpose; Medical; ISO ICS 35.240.80: IT applications in health care technology Abstract DICOM defines criteria for communication, visualization, archiving and printing of biomedical information Current Version http://medical.nema.org/ (there may be daily changes) Other editions ISO 12052:2006: Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management AAL Relevance DICOM is a public standard, so it achieves a great diffusion among medical devices. This involves a greater exchange of information V1.0 2013-01-15 Page 134 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from http://medical.nema.org/standard.html http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=43218 Description DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting information in medical imaging. It includes a file format definition and a network communications protocol. The communication protocol is an application protocol that uses TCP/IP to communicate between systems. DICOM files can be exchanged between two entities that are capable of receiving image and patient data in DICOM format. The National Electrical Manufacturers Association (NEMA) holds the copyright to this standard.[1] It was developed by the DICOM Standards Committee, whose members[2] are also partly members of NEMA.[3] DICOM enables the integration of scanners, servers, workstations, printers, and network hardware from multiple manufacturers into a picture archiving and communication system (PACS). The different devices come with DICOM conformance statements which clearly state which DICOM classes they support. DICOM has been widely adopted by hospitals and is making inroads in smaller applications like dentists' and doctors' offices. DICOM is known as NEMA standard PS3, and as ISO standard 12052:2006 “Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management”. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/DICOM EDIFACT Profile Reference Name EDIFACT EDIFACT: United Nations Electronic Data Interchange For Administration, Commerce and Transport Categories Communication Protocols; Medical Devices; ISO ICS 35.240.60: IT applications in transport and trade Abstract EDIFACT is the recognised international standard for EDI trading in a wide range of commercial and non-commercial sectors. Current Version Other editions AAL Relevance Available from http://www.iso.org/iso/catalogue_detail?csnumber=35033 Standard Parts Standard V1.0 Title 2013-01-15 Page 135 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO 9735-2:2002 Electronic data interchange for administration, commerce and transport (EDIFACT) – Application level syntax rules (Syntax version number: 4, Syntax release number: 1) – Part 2: Syntax rules specific to batch EDI Description EDIFACT is the recognised international standard for EDI trading in a wide range of commercial and non-commercial sectors. Its established applications are in store-andforward “batch” communication of transaction messages of many kinds. EDIFACT begins with an underlying syntax, which is an ISO standard . Within that syntax, there are directories of data elements, composite data elements, segments, and messages; and there are conventions for placing messages in an “envelope” which identifies the sender and receiver and other attributes of a transmission. EDIFACT itself does not define the medium by which the message is sent, or the protocols which are used in any particular form of communication. The standards are completely neutral in this respect - they define messages and their contents: nothing else. EDIFACT is an enabling standard which provides a great deal of flexibility - some might say too much - for individual application requirements to be accommodated. For this reason, very precise application guidelines are needed in addition to the basic standards. For book and serials trading, from publishers, through wholesalers, booksellers and subscription agents, to libraries, Editor is the agency which develops and maintains those guidelines. External links http://www.edifactor.com/standard_edi.php HL7 Profile Reference Name Categories HL7 HL7: Health Level Seven Communication Protocols; Medical Devices; ISO; Personal Health Records ICS Abstract HL7 provides standards for interoperability that improve care delivery, optimize workflow, reduce ambiguity and enhance knowledge transfer among all of our stakeholders, including healthcare providers, government agencies, the vendor community, fellow standardisation bodies and patients. Current Version see Standard Parts below Other editions AAL Relevance HL7 defines standard for different area of health care in order to define an unambiguous communications protocol Available from http://www.hl7.org/about/FAQs/index.cfm?ref=nav http://www.hl7.org/implement/standards/product_matrix.cfm?ref=nav V1.0 2013-01-15 Page 136 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts following are reported the HL7's standard published by ISO Standard ISO/HL7 21731:2006 ISO/HL7 27932:2009 ISO/HL7 10781:2009 ISO/HL7 279531:2011 ISO/HL7 27931:2009 Title Data Exchange Standards – HL7 Clinical Document Architecture, Release 2 Health informatics – HL7 version 3 – Reference information model – Release 1 Electronic Health Record-System Functional Model, Release 1.1 Health informatics – Individual case safety reports (ICSRs) in pharmacovigilance – Part 1: Framework for adverse event reporting Data Exchange Standards – Health Level Seven Version 2.5 – An application protocol for electronic data exchange in healthcare environments ISO/TS 15000Electronic business eXtensible Markup Language (ebXML) – Part 2: 2:2004 Message service specification (ebMS) ISO/TS 11073EHealth informatics – Medical waveform format – Part 92001: Encoding 92001:2007 rules ISO 13606Health informatics – Electronic health record communication – Part 3: 3:2009 Reference archetypes and term lists ISO 21090:2011 Health informatics – Harmonized data types for information interchange Description Health Level Seven International is one of several American National Standards Institute (ANSI) -accredited Standards Developing Organizations (SDOs) operating in the healthcare arena. Most SDOs produce standards (sometimes called specifications or protocols) for a particular healthcare domain such as pharmacy, medical devices, imaging or insurance (claims processing) transactions. Health Level Seven's domain is clinical and administrative data. HL7 and its members provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information. These standards define how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world. External links • http://www.hl7.org/ • http://en.wikipedia.org/wiki/Health_Level_7 V1.0 2013-01-15 Page 137 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IHE XDM Profile Reference Name Categories ICS Abstract IHE XDM IHE XDM: Cross-Enterprise Media Interchange Communication Protocols; Medical Devices; Personal Health Records Cross-Enterprise Document Media Interchange (XDM) provides document interchange using a common file and directory structure over several standard media. This permits the patient to use physical media to carry medical documents. This also permits the use of person-toperson email to convey medical documents. (from wiki.ihe.net, see external link) Current Version Current Technical Framework - Revision 9.0 Other editions AAL Relevance Exchanging of medical documents can be very useful is AAL systems. Available from http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description This Supplement introduces a new IHE Integration Profile that facilitates interchange across health enterprises of electronic patient related medical documents, using media or email. This Integration Profile, referred to as XDM (for Cross-Enterprise Document Media Interchange), complements the existing XDS Integration Profile by providing for the use of XDS defined formats and metadata in a simpler environment: • Transfer of documents and related metadata over CD-R and USB memory devices • Transfer of documents and related metadata over email using a ZIP attachment It focuses on providing a standards-based specification for managing the interchange of documents that healthcare enterprises (anywhere from a private physician to a clinic to an acute care in-patient facility) have decided to explicitly exchange documents using media between the patient and the patient’s care providers, or between care providers. This enables better interoperability between Electronic Health Records (EHRs) and Personal Health Records (PHRs), as a natural complement to the IHE ITI XDS Integration Profile (for cross-enterprise document sharing). [Source: ihe.net, see external link] External links http://wiki.ihe.net/index.php?title=Cross-enterprise_Document_Media_Interchange http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Supplement_XDM_TI_2006 _08_15.pdf V1.0 2013-01-15 Page 138 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IHE XDR Profile Reference Name Categories ICS Abstract IHE XDR IHE XDR: Cross-Enterprise Document Reliable Interchange Communications Protocols; Medical Devices; Personal Health Records Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories. [Source: from wiki.ihe.net, see external link] Current Version Other editions AAL Relevance XDR provides a reliable and automatic transfer of documents and metadata for one patient between EHR systems even in the absence of an XDS infrastructure. Available from http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description XDR provides a reliable and automatic transfer of documents and metadata for one patient between EHR systems even in the absence of an XDS infrastructure. XDR supports the reuse of the Provide and Register Set transaction-b with Web-Services as transport. Transfer is direct from source to recipient, no repository or registry actors are involved. XDR is document format agnostic, supporting the same document content as XDS and XDM. Document content is described in XDS Document Content Profiles. Examples are XDS-MS, XD-LAB, XPHR, and XDS-SD. XDR defines no new metadata or message formats. It leverages XDS metadata with emphasis on patient identification, document identification, description, and relationships. [Source: wiki.ihe.net, see external link] External links http://wiki.ihe.net/index.php?title=Cross-enterprise_Document_Reliable_Interchange IHE XDS Profile Reference Name Categories ICS V1.0 IHE XDS IHE XDS: Cross-Enterprise Document Sharing Communication Protocols; Medical Devices; Personal Health Records 2013-01-15 Page 139 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract Cross-Enterprise Document Sharing (XDS) facilitates the registration, distribution and access across health enterprises of patient electronic health records. [Source: wiki.ihe.net, see external link] Current Version Technical Framework version 9.0 Other editions AAL Relevance XDS providing a standards-based specification for managing the sharing of documents between any healthcare enterprise Available from http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility and personal health record systems. This is managed through federated document repositories and a document registry to create a longitudinal record of information about a patient within a given clinical affinity domain. These are distinct entities with separate responsibilities: • A Document Repository is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests. • A Document Registry is responsible for storing information about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored. In addition to these features the figure of document administrator has been inserted. The Document Administrator actor supports metadata update by issuing the Update Document, Set transaction and Delete Document Set transaction to the Document Registry actor. Facilitates management of the Electronic Health Record • facilitates the registration, distribution and access across health enterprises of patient electronic health records. • focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility. [Source: from wiki.ihe.net] External links • http://wiki.ihe.net/index.php?title=Cross-Enterprise_Document_Sharing IHE XUA Profile Reference V1.0 IHE XUA 2013-01-15 Page 140 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name Categories ICS Abstract IHE XUA: Integrating the Healthcare Cross Enterprise User Assertion Communication Protocol; Medical Devices Cross-Enterprise User Assertion Profile (XUA) - provides a means to communicate claims about the identity of an authenticated principal (user, application, system…) in transactions that cross enterprise boundaries Current Version Other editions AAL Relevance Assistance to sites in implementing security and confidentiality policies Available from http://www.ihe.net/ Description With the growth of communications between organizations there is a strong need to provide user identity, role assignment, and other claims about the context of the communication. These transactions are happening between different organizations that are otherwise competitors, and thus not likely that they will be able to agree on a centralized user identity system like EUA. This communications between organizations is the space that the Cross-Enterprise User Assertion (XUA) profile fills by using Federated Identity. Cross-Enterprise User Assertion Profile (XUA) - provides a means to communicate claims about the identity of an authenticated principal (user, application, system…) in transactions that cross enterprise boundaries. To provide accountability in these cross-enterprise transactions there is a need to identify the requesting principal in a way that enables the receiver to make access decisions and generate the proper audit entries. The XUA Profile supports enterprises that have chosen to have their own user directory with their own unique method of authenticating the users, as well as others that may have chosen to use a third party to perform the authentication Assistance to sites in implementing security and confidentiality policies There are transactions defined by IHE that cross enterprise boundaries and are web-services based on ITI TF-2:Appendix V. The existing IHE profiles for an authenticated user identity (IHE Enterprise User Authentication Profile [EUA]) are not intended to function in crossenterprise transactions. In a cross-enterprise environment it is more likely that the transactions will be going between two enterprises that maintain their own independent user directories (IHE Personnel White Pages [PWP]). This type of requirement is the focus of the Identity Federation standards. Identity Federation has received much attention by the security and the platforms industry. Identity Federation is agnostic to the type of user directory; it allows for a centralized user directory, but also supports the more powerful federation of user directories. External links • http://wiki.ihe.net/index.php?title=Cross-Enterprise_User_Assertion_ (XUA) • http://healthcaresecprivacy.blogspot.it/2011/05/ihe-privacy-and-security-profilescross.html V1.0 2013-01-15 Page 141 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IHE XCA Profile Reference Name Categories ICS Abstract IHE XCA IHE XCA: Integrating the Healthcare Cross Community Access Communications Protocols; Medical Devices The Cross-Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities Current Version Other editions AAL Relevance Available from http://www.ihe.net/ Description The Cross-Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism. Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc. A community is identifiable by a globally unique id called the homeCommunityId. Membership of a facility/enterprise in one community does not preclude it from being a member in another community. Such communities may be XDS Affinity Domains which define document sharing using the XDS profile or any other communities, no matter what their internal sharing structure. External links http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_XCA_Rev2-1_TI_201008-10.pdf#page=14 ISO/IEEE 11073 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEEE 11073 ISO/IEEE 11073: Health informatics - Medical / health device communication standards Communication Protocols; Medical Devices; Personal Health Records; Terminologies and Semantics; Medical Terminology; ISO; IEEE 35.240.80: IT applications in health care technology CEN ISO/IEEE 11073 Health informatics - Medical / health device communication standards enable communication between medical, health care and wellness devices and with external computer systems. They provide automatic and detailed electronic data capture of client2013-01-15 Page 142 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot related and vital signs information, and of device operational data. Current Version see Standard Parts below Other editions AAL Relevance This is the standard for data communications between health devices Available from see Standard Parts below Standard Parts Standard ISO/IEEE 1107320101:2004 ISO/IEEE 1107310408:2010 ISO/IEEE 1107310415:2010 ISO/IEEE 1107310471:2010 ISO/IEEE 1107310407:2010 ISO/IEEE 1107310404:2010 ISO/IEEE 1107310417:2010 ISO/IEEE 1107330200:2004 ISO/IEEE 1107330300:2004 ISO/IEEE 1107310201:2004 ISO/IEEE 1107310101:2004 ISO 1107391064:2009 ISO/IEEE 1107320601:2010 ISO 1107390101:2008 ISO/TS 1107392001:2007 ISO/IEEE FDIS 11073-10406 ISO/IEEE DIS 11073-10417 V1.0 Title Health informatics – Point-of-care medical device communication – Part 20101: Application profiles – Base standard Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale Health informatics – Personal health device communication – Part 10471: Device specialization - Independent living activity hub Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter Health informatics – Point-of-care medical device communication – Part 30200: Transport profile – Cable connected Health informatics – Point-of-care medical device communication – Part 30300: Transport profile – Infrared wireless Health informatics – Point-of-care medical device communication – Part 10201: Domain information model Health informatics – Point-of-care medical device communication – Part 10101: Nomenclature Health informatics – Standard communication protocol – Part 91064: Computer-assisted electrocardiography Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol Health informatics – Point-of-care medical device communication – Part 90101: Analytical instruments – Point-of-care test Health informatics – Medical waveform format – Part 92001: Encoding rules Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG) Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter 2013-01-15 Page 143 of 490 AALIANCE2 ISO/IEEE DIS 11073-10418 ISO/IEEE FDIS 11073-10420 ISO/IEEE FDIS 11073-10421 ISO/IEEE FDIS 11073-10472 ISO/IEEE FDIS 11073-30400 D4.1 Online Repository of Standards - Snapshot Health informatics – Personal health device communication – Part 10418: Device specialization–International Normalized Ratio (INR) monitor Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyser Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow) Health Informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor Health informatics – Point-of-care medical device communication – Part 30400: Interface profile – Cabled Ethernet Description 5. Provide real-time plug-and-play interoperability for citizen-related medical, healthcare and wellness devices; 6. Facilitate efficient exchange of care device data, acquired at the point-of-care, in all care environments. • “Real-time” means that data from multiple devices can be retrieved, time correlated, and displayed or processed in fractions of a second. • “Plug-and-play” means that all a user has to do is make the connection – the systems automatically detect, configure, and communicate without any other human interaction. • “Efficient exchange of care device data” means that information that is captured at the point-of-care (e.g., personal vital signs data) can be archived, retrieved, and processed by many different types of applications without extensive software and equipment support, and without needless loss of information. The standards are targeted at personal health and fitness devices (such as glucose monitors, pulse oximeters, weighing scales, medication dispensers and activity monitors) and at continuing and acute care devices (such as pulse oximeters, ventilators and infusion pumps). They comprise a family of standards that can be layered together to provide connectivity optimized for the specific devices being interfaced. There are four main partitions to the standards: • Device data, including a nomenclature, or terminology, optimized for vital signs information representation based on an object-oriented data model, and device • General application services (e.g., polled vs. “event driven” services); • Internetworking and gateway standards (e.g., an observation reporting interface from CEN ISO/IEEE 11073-based messaging and data representation to HL7 or DICOM); • Transports (e.g., cable connected or wireless). [Source: Wikipedia] V1.0 2013-01-15 Page 144 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • ISO/IEEE11073 (Wikipedia) xDT Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from xDT xDT Communication Protocols; Medical Devices; File Formats and Persistent Data Structures; General Purpose; Medical; Germany 35.240.80: IT applications in health care technology xDT is a family of message formats used in the German ambulatory healthcare sector to exchange reimbursement data, medical summaries, device data and lab data See below xDT is currently the only format most IT systems in doctors' private practices in Germany can read and write, thus offering an import/export interface for medical AAL data http://www.kbv.de/ita/4287.html Standard Parts Standard BDT 3.0:2012 KVDT 4.18:2012 LDT 4.19:2012 GDT 3.0:2012 Title Datensatzbeschreibung BDT [Data set definition BDT (treatment data transfer)] Datensatzbeschreibung KVDT [Data set definition KVDT (Association of SHI Physicians data transfer)] Datensatzbeschreibung LDT (Labordatenträger) [Data set definition LDT (laboratory record carrier)] Anbindung von medizinischen Messgeräten (Gerätedatenträger) [Connection of medical measurement devices (device record carrier)] Description The xDT standard is a family of communication formats (file/message formats) for the information exchange in the ambulatory health sector in Germany. xDT was initiated in the 1980s by the Association of Statutory Health Insurance Physicians and has become a national standard that is used in practice management information systems. The Federal Association of SHI Physicians (KBV) is responsible for the observance of the standard. There are strict testing and certification requirements. xDT started with the ADT standard for reimbursement data (meanwhile superseded by KVDT). Further specifications based on the same data structure followed, such BDT (treatment data), GDT (device data) and LDT (laboratory data). xDT messages are essentially text files. A message consists of several “records”, while V1.0 2013-01-15 Page 145 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot each record consists of one or more “fields”, each field being encoded as one line of text. Each line starts with a three-digit number indicating the length of the line (including the carriage return/line feed), immediately followed by four digits indicating the field ID, followed by the value. The standard precisely defines the permitted sequence of fields for each record type, including optionality, possible repetitions, sub-fields etc. German umlaut characters are encoded either according to DIN 66003:1974, IBM Code Page 437 or ISO 8859-1/15. External links • http://de.wikipedia.org/wiki/XDT (in German language) • http://www.kbv.de/ita/4274.html (in German language) ZigBee Health Care Profile Reference Name Categories ZigBee Health Care ZigBee Health Care Network and Buses; (Wireless) Personal Area Network; Communication Protocols; Medical Devices; ZigBee ICS Abstract ZigBee Health Care offers a global standard for interoperable products enabling secure and reliable monitoring and management of noncritical, low-acuity healthcare services targeted at chronic disease, ageing independence and general health, wellness and fitness. [Source: ZigBee.org] Current Version Other editions AAL Relevance ZigBee Health care’s specification provides standard interfaces and device descriptions to allow inter-operability among ZigBee devices produced by various manufacturers of health care products. Available from http://www.zigbee.org/Standards/ZigBeeHealthCare/Overview. aspx Description ZigBee Health Care offers a global standard for interoperable products enabling secure and reliable monitoring and management of non-critical, low-acuity healthcare services targeted at chronic disease, ageing independence and general health, wellness and fitness. These easy-to-use products facilitate independence, plus overall health, wellness and fitness awareness. A variety of these products even offer an innovative connection with health care professionals like doctors and nurses, allowing them to monitor your health even while you're at home. All ZigBee Health Care products are ZigBee Certified to perform regardless of manufacturer, allowing everyone to purchase with confidence. These products are ideal for V1.0 2013-01-15 Page 146 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot personal, medical personnel, gymnasiums or hospital/recovery centre use. [Source: ZigBee.org] External links • http://www.zigbee.org/Standards/ZigBeeHealthCare/Overview.aspx 2.1.4 Home Appliances HomePNA Profile Reference Name HomePNA HomePNA Alliance (formerly the Home Phoneline Networking Alliance, also known as HPNA) Categories Communication Protocols; Home Appliances; ITU ICS Abstract HomePNA is an alliance of leading technology companies working to promote the adoption of a high performance existing-wire home networking standard for applications such as triple-play service deployments. HomePBNA is approved by the ITU. Current Version see Standard Parts below Other editions AAL Relevance HomePNA maybe used for connecting of and communicating between AAL devices depended on (already available) power lines and phone lines. Available from see Standard Parts below Standard Parts Standard G.9951 G.9952 G.9953 G.9954 (02/05) G.9954 (01/07) Title HomePNA 2.0 HomePNA 3.0 HomePNA 3.1 Description The HomePNA™ Alliance is a community of leading technology companies, original equipment manufacturers (OEMs) and service providers working together to develop, promote and support home networking solutions based on internationally recognized, open and interoperable HomePNA standards. The Alliance supports development and deployment of products designed to meet the needs of consumers and to address service providers' demands for carrier-grade performance to enable the distribution of triple-play services, such as IPTV, Voice over IP (VoIP) and Internet data in the home over existing V1.0 2013-01-15 Page 147 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot telephone wires and coax cables. The technology enables telecommunication service providers to meet - and drive - the growing consumer demand for affordable, high-speed and easy-to-use home entertainment networks. HomePNA's goal is to drive the adoption and shipments of HomePNA technology worldwide: • Develop leading-edge multimedia home networking technology that operates over multiple types of existing home wiring for the worldwide market • Cooperate with other industry groups to deliver easy-to-use complete access/home networking solutions • Lower development and deployment costs with easy-to-use member-only community Web-based communication tools • Drive market interest and awareness by promoting HomePNA's feature-rich technology and market success to the press and analysts • Promote member products at tradeshow HomePNA booths • Provide opportunities for members to promote their products through HomePNA newsletters, success stories and blog • Increase customer satisfaction through the member-product logo interoperability and certification program • Lower product development and deployment costs with a one-stop Web resource for finding certified HomePNA products and technology External links • http://www.homepna.org • http://en.wikipedia.org/w/index.php?title=HomePNA&oldid=529355682 CHAIN Profile Reference Name Categories ICS Abstract CHAIN CHAIN: CECED Home Appliances Interoperating Network Communication Protocols; Home Appliances; EN; CENELEC 97.120 - Automatic controls for household use CHAIN (Ceced Home Appliances Interoperating Network), defines the protocol for connecting appliances in a single multibrand system designed for control and automation of key services in a home: e.g., remote control of appliance operation, energy or load management, remote diagnostics and automatic maintenance support to appliances, downloading and updating of data, programs, and services from the Web. Current Version see Standard Parts below Other editions EN 50523 V1.0 2013-01-15 Page 148 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance CHAIN addresses the interoperability of an “Intelligent home”, that has an overlap to the domain of AAL. Available from see Standard Parts below Standard Parts Standard EN50523-1:2009 EN50523-2:2009 Title Household appliances interworking - Part 1: Functional specification Household appliances interworking - Part 2: Data structures Description CECED Members have decided that each actor should stop searching individually for the killer application and that there is a need for creating a pre-competitive platform. We have developed a solution, C.H.A.I.N. (Ceced Home Appliances Interoperating Network), allowing appliances from different manufacturers to inter-work, independently from the bus protocol technology and the proprietary control system embedded in the appliance. C.H.A.I.N. is the quality mark ensuring compatibility of the appliances. C.H.A.I.N. is open to other application clusters of automation in the home, facilitating the way to an “intelligent home”. The new platform, called Chain (Ceced Home Appliances Interoperating Network), defines the protocol for connecting appliances in a single multibrand system designed for control and automation of key services in a home: e.g., remote control of appliance operation, energy or load management, remote diagnostics and automatic maintenance support to appliances, downloading and updating of data, programs, and services from the Web. Products complying with the protocol will receive a special certification, to be agreed with the leading international associations which develop and maintain open communications protocols on home automation. Such a certification is a guarantee to the customer that the product is compliant with the common standard, while fully delivering its performances within the home automation system. External links • http://www.ceced.eu/IFEDE/easnet.dll/GetDoc?APPL=1&DAT_IM=20B945 • http://www.ceced.eudata.be/ICECED/easnet.dll/GetDoc?APPL=1&DAT_IM=031980 DLNA Profile Reference Name Categories ICS Abstract V1.0 DLNA DLNA: Digital Living Network Alliance Communication Protocols; Home Appliances The Digital Living Network Alliance (DLNA) is a non-profit collaborative trade organization established by Sony in June 2003, that is responsible for defining interoperability guidelines to enable sharing of 2013-01-15 Page 149 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot digital media such as music, photos and videos between consumer devices such as computers, TVs, printers, cameras, cell phones, and other multimedia devices Suitable for AAL applications with the focus on multimedia http://www.dlna.org Description Digital Living Network Alliance (DLNA) is helping put an end to that frustration. A collaboration of the world’s leading consumer electronics, PC and mobile companies, DLNA has created design guidelines for a new generation of DLNA Certified products that can work together — no matter the brand. In the DLNA defined future, you’ll buy DLNA Certified products that help you share and enjoy your digital content where and when you want, at home or on the road, by yourself or among friends. The goal of DLNA is to enable end-to-end interoperability among the digital devices storing, playing and sharing digital content on your digital network. So far that includes DLNA Certified products in twelve different DLNA device classes in three categories. The DLNA Certified Device Classes are separated as follows: Home Network Devices: • Digital Media Server (DMS): These devices store content and make it available to networked digital media players (DMP) and digital media renderers (DMR). Examples include PCs and network-attached storage (NAS) devices. • Digital Media Player (DMP): These devices find content on digital media servers (DMS) and provide playback and rendering capabilities. Examples include TVs, stereos and home theatres, wireless monitors and game consoles. • Digital Media Renderer (DMR): These devices play content received from a digital media controller (DMC), which will find content from a digital media server (DMS). Examples include TVs, audio/video receivers, video displays and remote speakers for music. • Digital Media Controller (DMC): These devices find content on digital media servers (DMS) and play it on digital media renderers (DMR). Examples include Internet tablets, Wi-Fi enabled digital cameras and personal digital assistants (PDAs). • Digital Media Printer (DMPr): These devices provide printing services to the DLNA home network. Generally, digital media players (DMP) and digital media controllers (DMC) with print capability can print to DMPr. Examples include networked photo printers and networked all-in-one printers Mobile Handheld Devices: • Mobile Digital Media Server (M-DMS): These wireless devices store content and make it available to wired/wireless networked mobile digital media players (M-DMP), digital media renderers (DMR) and digital media printers (DMPr). Examples include mobile phones and portable music players. • Mobile Digital Media Player (M-DMP): These wireless devices find and play content on a digital media server (DMS) or mobile digital media server (M-DMS). Examples include mobile phones and mobile media tablets designed for viewing multimedia content. V1.0 2013-01-15 Page 150 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Mobile Digital Media Uploader (M-DMU): These wireless devices send (upload) content to a digital media server (DMS) or mobile digital media server (M-DMS). Examples include digital cameras and mobile phones. • Mobile Digital Media Downloader (M-DMD): These wireless devices find and store (download) content from a digital media server (DMS) or mobile digital media server (MDMS). Examples include portable music players and mobile phones. • Mobile Digital Media Controller (M-DMC): These wireless devices find content on a digital media server (DMS) or mobile digital media server (M-DMS) and send it to digital media renderers (DMR). Examples include personal digital assistants (PDAs) and mobile phones. Home Infrastructure Devices: • Mobile Network Connectivity Function (M-NCF): These devices provide a bridge between mobile handheld device network connectivity and home network connectivity. • Media Interoperability Unit (MIU):These devices provide content transformation between required media formats for home network and mobile handheld devices. External links • DLNA • DLNA (Wikipedia) ISO/IEC 18012 Profile Reference Name ISO/IEC 18012 Information technology – Home Electronic System – Guidelines for product interoperability Categories Communication Protocols; Home Appliances; ISO; IEEE ICS 35.240.99: IT applications in other fields, 35.200: Interface and interconnection equipment Abstract ISO/IEC 18012-1:2004 defines the components of interoperability for the purpose of providing a framework within which subsequent parts of the standard will be drafted. ISO/IEC 18012-2:2012(E) specifies a taxonomy and application interoperability model for the interoperability of products in the area of home systems. Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios may use home devices from different companies and have the demand for interoperability this standard is relevant. Available from see Standard Parts below V1.0 2013-01-15 Page 151 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard ISO/IEC 18012-1:2004 ISO/IEC 18012-2:2012 Title Information technology – Home Electronic System – Guidelines for product interoperability – Part 1: Introduction Information technology – Home Electronic System – Guidelines for product interoperability – Part 2: Taxonomy and application interoperability model Description ISO/IEC 18012-1:2004 specifies requirements for product interoperability in the area of home and building automation systems, with sufficient detail needed to design interoperable Home Electronic System products. The widespread development of many national standard and proprietary networks within and to the home has necessitated a standard for interoperability among home system applications and products from multiple manufacturers. Where widely varying devices need to interoperate, it is desirable that they do so seamlessly to present a single, uniform network and hence to deliver a variety of applications. Examples of such applications are lighting control, environmental control, audio/video equipment control and home security. Although a single uniform home control system would simplify operations, this standard recognises that multiple different networks may co-exist in the same house, and therefore applies to devices connected to a single home control system or to different home control systems. It ensures that, where applications on the same or dissimilar networks co-exist within premises and are required to interoperate, they will do so in a safe, reliable, predictable and consistent manner. It specifies requirements to assure that devices from multiple manufacturers work together to provide a specific application; a specific device could also be used for multiple applications. Interoperability requirements are given with respect to safety, addressing, applications, transport of information, management, and setup of devices/elements within home networks - static and/or dynamic binding between objects. This part defines the components of interoperability for the purpose of providing a framework within which subsequent parts of the standard will be drafted. This part applies to components within networks, between networks and located within dissimilar networks, as well as to devices located at the junction of dissimilar networks. ISO/IEC 18012-2:2012(E) specifies a taxonomy and application interoperability model for the interoperability of products in the area of home systems. It also specifies an interoperability framework to allow products from multiple manufacturers to work together in order to provide a specific application. It describes a application process that exists above the OSI reference model (ISO/IEC 7498-1) stack, with sufficient detail needed to establish interoperable applications in this domain. It is applicable to: single implementation home electronic system networks, connected devices and applications, multiple implementation home electronic system networks, connected devices and applications, automatically configured devices, manually configured devices and manually configured groups/clusters of devices. [Source: ISO] V1.0 2013-01-15 Page 152 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ZigBee Home Automation Profile Reference Name Categories ZigBee Home Automation ZigBee Home Automation Networks and Buses; Communication Protocols; General Purpose Protocols; ZigBee ICS Abstract ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management and security, as well as the expandability to connect with other ZigBee networks Current Version Other editions AAL Relevance As AAL scenarios may use wireless sensor networks for home automation ZigBee Home Automation may be useful. Available from http://zigbee.org/Standards/ZigBeeHomeAutomation/Overview.aspx Description ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management and security, as well as the expandability to connect with other ZigBee networks. Smarter homes allow consumers to save money, be more environmentally aware, feel more secure and enjoy a variety of conveniences that make homes easier and less expensive to maintain. ZigBee Home Automation supports a diverse ecosystem of service providers and product manufacturers as they invent products necessary to create smart homes. These products are ideal for new construction, do-it-yourself and retrofit markets, and are easy to use, maintain and install. All ZigBee Home Automation products are ZigBee Certified to perform regardless of manufacturer, allowing anyone to purchase with confidence. Numerous innovative companies have contributed their expertise to this standard, including Phillips, Control4 and Texas Instruments. ZigBee Home Automation offers a global standard for interoperable products enabling smart homes that can control appliances, lighting, environment, energy management, and security as well as expand to connect with other ZigBee networks. Smarter homes allow consumers to save money, be more environmentally aware, feel more secure and enjoy a variety of conveniences that make homes easier and less expensive to maintain. All ZigBee Home Automation products are ZigBee Certified to perform regardless of manufacturer, allowing anyone to purchase with confidence. These products are ideal for new construction, do-it-yourself and retrofit markets and are easy to use, maintain and install. V1.0 2013-01-15 Page 153 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Homeplug Profile Reference Name Categories Homeplug Homeplug (HomePlug Powerline Alliance) Networks and Buses; Physical Networks; Power line Communication; HomePlug; Communication Network; Home Appliances; IEEE ICS Abstract HomePlug is an industry Alliance comprised of industry leaders at each level of the value chain - from Technology to Services & Content. The Alliance's mission is to enable and promote rapid availability, adoption and implementation of cost effective, interoperable and standardsbased home power line networks and products. HomePlug is the family name for various power line communications specifications that support networking over existing home electrical wiring. Baseline technology for IEEE 1901 Current Version HomePlug 1.0, HomePlug AV2, HomePlug Green PHY, HomePlug Access BPL Other editions IEEE 1901-2010: Standard for Broadband over Power Line Networks: Medium Access Control and Physical Layer Specifications AAL Relevance Homeplug maybe used for connecting of and communicating between AAL devices depended on power supply via sockets. Available from https://www.homeplug.org/home/ Description The HomePlug Powerline Alliance is a trade association of electronics manufacturers, service providers, and retailers that establishes standards for, and tests members' devices for compliance to, the various power line communication technologies known as HomePlug. The alliance developed standards for applications such as in-home distribution of TV, gaming and Internet access. It also developed a specification for smart power meters and in-home communications between electric systems and appliances. HomePlug is the family name for various power line communications specifications that support networking over existing home electrical wiring. Several specifications exist under the HomePlug moniker, with each offering unique performance capabilities and coexistence or compatibility with other HomePlug specifications. HomePlug 1.0 The first HomePlug specification, HomePlug 1.0, provides a peak PHY-rate of 14 Mbit/s. It was first introduced in June, 2001 and has since been replaced by HomePlug AV. On May 28, 2008 Telecommunications Industry Association (TIA) incorporated HomePlug 1.0 power line technology into the newly published TIA-1113 international standard. TIA-1113 defines modem operations on user-premises electrical wiring. The new standard is the world's first multi-megabit power line communications standard approved by an American National Standards Institute (ANSI)-accredited organization. V1.0 2013-01-15 Page 154 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot HomePlug 1.0 Turbo adapters comply with the HomePlug 1.0 specification but employ a faster, proprietary mode that increases the peak PHY-rate to 85 Mbit/s. HomePlug AV The HomePlug AV specification, which was introduced in August 2005, provides sufficient bandwidth for applications such as HDTV and VoIP. HomePlug AV offers a peak data rate of 200 Mbs at the physical layer, and about 80 Mbs at the MAC layer. HomePlug AV devices are required to coexist, and optionally to interoperate, with HomePlug 1.0 devices. Utilizing adaptive modulation on up to 1155 OFDM sub-carriers, turbo convolution codes for error correction, two-level MAC framing with ARQ, and other techniques, HomePlug AV can achieve near the theoretical maximum bandwidth across a given transmission path. For security reasons, the specification includes key distribution techniques and the use of 128 bit AES encryption. Furthermore, the specification's adaptive techniques present inherent obstacles to eavesdropping and cyber attacks. Some Qualcomm Atheros-based adapters comply with the HomePlug AV specification but employ a proprietary extension that increases the PHY-rate to 500 Mbit/s primarily by using a wider spectrum. HomePlug AV2 The HomePlug AV2 specification was introduced in January 2012, it is interoperable with HomePlug AV and HomePlug GreenPHY devices and is IEEE 1901 standard compliant. It features gigabit-class PHY-rate, support for MIMO PHY, repeating functionalities and power saving modes. HomePlug Green PHY The HomePlug Green PHY specification is a subset of HomePlug AV that is intended for use in the smart grid. It has peak rates of 10 Mbit/s and is designed to go into smart meters and smaller appliances such as HVAC thermostats, home appliances and plug-in electric vehicles so that data can be shared over a home network and with the power utility. High capacity broadband is not needed for such applications; the most important requirements are low power and cost, reliable communication, and compact size. GreenPHY uses up to 75% less energy than AV.[11] The HomePlug Powerline Alliance worked with utilities and meter manufacturers to develop this 690-page specification. HomePlug Green PHY devices are required to be fully interoperable with devices based on HomePlug AV, HomePlug AV2 and IEEE 1901 specification. HomePlug Access BPL Access Broadband Power Line (BPL) refers to a to-the-home broadband access technology. The HomePlug Alliance formed the HomePlug Access BPL Working Group, whose first charter was to develop the Market Requirements Document (MRD) for a HomePlug Access BPL specification. The Alliance made an open invitation to the BPL industry to participate in the development of or provide input for consideration in the MRD. After several months of collaboration between utilities, ISPs and other BPL industry groups, the MRD was completed in June 2005. HomePlug's work on the Access BPL was subsequently contributed and merged into the IEEE 1901 standard. [Source: Wikipedia] V1.0 2013-01-15 Page 155 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://en.wikipedia.org/wiki/HomePlug_Powerline_Alliance • http://en.wikipedia.org/wiki/HomePlug 2.1.5 Smart Metering BSI-TR-03109 Profile Reference Name Categories ICS Abstract BSI-TR-03109 BSI-TR-03109: Technical Guideline BSI TR-03109 SMART ENERGY Communications Protocols; Smart Metering; Germany To ensure interoperability between the different components in a metering system, some requirements of protection of the safety profile shall be adopted and complied. These requirements are specified in this technical guide for the safe use of smart metering systems Current Version 0.5 Other editions AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from https://www.bsi.bund.de/ContentBSI/Publikationen/TechnischeRichtlini en/tr03109/index_htm.html Standard Parts Standard BSI-TR-03109 Title [ENTWURF] Technische Richtlinie BSI TR- 03109 SMART ENERGY Description The Technical Guideline (TR) of the Federal Office for Information Security (BSI), entitled “Technical Guidelines SMART ENERGY” describes the requirements for functionality, interoperability and security, the need to comply with the components in the context of smart metering, as well as the requirements to examine these properties. EEBus Profile Reference Name Categories ICS V1.0 EEBus EEBus Communication Protocols; Smart Metering - 2013-01-15 Page 156 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract The EEBus describes a technology for comprehensive networking of devices and load management between power suppliers, grid operators and end users. For this, it abstracts many existing protocols in a consistent IPv6/XML format. Furthermore, it defines mechanisms for automatic load management. [Source: from eebus.org] Current Version Other editions AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from Description In the commercial and residential areas, devices of different manufacturers, with different field bus or interface protocols are usually used instead of complex “single source” systems. Furthermore, the devices are often installed or replaced at different times. The EEBus is a middle-ware to support integration of the heterogeneous device infrastructures distributed throughout the building. The EEBus is a kind of interpreter between the protocols of the different devices and technologies, ensuring up-to-date, smooth, transparent and secure communication between the power supply and the smart consumer. Individual links between the data points of such protocols on a user level cannot solve this task. The missing rules (defined, e.g. in standards) would in this case always enable only proprietary – i.e. not generally valid and not expansible - implementation. The EEBus as an integration platform generates this possibility for general application and thus the transparency and structure for device couplings. Therefore, the respective bodies consider mapping between the different protocols in standardisation as well. The EEbus has only a single adapter for every connected protocol type. Ideally, implementation of the EEBus should not require any changes to the device field buses to be integrated due to the parallel standardisation efforts. Additionally, the EEBus creates a consistent abstraction of energy characteristics of various devices across the different field buses. It warrants complete transaction safety of load management in spite of different message and communications protocols at the device interfaces. Only a single, standardised EEBus interface in XML format is visible from the outside, i.e. from the power supply to the consumer. Only this enables transmission of incentive values between the power supplier and consumer and reconciliation of consumption and demand between the parties involved. On the inside (machine-consumer), the EEBus expands established interface standards by necessary signal and control functions for communication in a smart grid. Exchange or supplementation of end devices is easy because new devices can be “connected” with their standardised interfaces. The parallel standardisation efforts of the EEBus thus enable a solution concept comprehensively based on standards. [Source: from eebus.org] V1.0 2013-01-15 Page 157 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.eebus.org/en/initiative-eebus-ev/ • http://de.wikipedia.org/wiki/EEBus (German Wikipedia page) EMAN Profile Reference Name Categories ICS Abstract EMAN EMAN: Energy Management Communication Protocols; Smart Metering; IETF The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices. Current Version draft Other editions AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from Description The focus of the Energy Management (EMAN) framework is energy monitoring and management of energy objects. The scope of devices considered are network equipment and its components, and devices connected directly or indirectly to the network. The EMAN framework enables monitoring (heterogeneous devices to report their energy consumption) and, if permissible, control. There are multiple scenarios where this is desirable, particularly considering the increased importance of limiting consumption of finite energy resources and reducing operational expenses. The EMAN framework describes how energy information can be retrieved from IP-enabled devices using Simple Network Management Protocol (SNMP), specifically, Management Information Base (MIBs) for SNMP. [Source: IETF] External links • http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/ EN 13757 Profile Reference Name V1.0 EN 13757 EN 13757: Communication systems for meters and remote reading of meters (M-Bus) 2013-01-15 Page 158 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories Networks and Buses; Cables and Physical Networks; Power line Communication; EN; M-Bus; OMS; Open Metering System; CEN; IEC; ICS 91.140.50 Energy (Including electric energy meters in buildings, emergency electrical supplies, etc. ) Abstract M-Bus (Meter-Bus) is a European standard (EN 13757-2 physical and link layer, EN 13757-3 application layer) for the remote reading of gas or electricity meters. M-Bus is also usable for other types of consumption meters. The M-Bus interface is made for communication on two wire, making it very cost effective. A radio variant of M-Bus (Wireless M-Bus) is also specified in EN 13757-4. [Source: Wikipedia] Current Version see Standard Parts below Other editions IEC 62056 AAL Relevance As some AAL business models use smart meters to access the customer's home, this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 13757-1:2003 EN 13757-2:2004 EN 13757-3:2004 EN 13757-4:2005 EN 13757-5:2008 EN 13757-6:2008 Title Communication systems for meters and remote reading of meters Part 1: Data exchange Communication systems for meters and remote reading of meters Part 2: Physical and link layer Communication systems for meters and remote reading of meters Part 3: Dedicated application layer Communication systems for meters and remote reading of meters Part 4: Wireless meter readout (Radio meter reading for operation in the 868 MHz to 870 MHz SRD band) Communication systems for meters and remote reading of meters Part 5: Wireless relaying Communication systems for meters and remote reading of meters Part 6: Local Bus Description The DLMS/COSEM standard suite (IEC 62056 / EN 13757-1) is the most widely accepted international standard for utility meter data exchange. This global acceptance is clearly demonstrated by the continued fast growth of the membership of the DLMS User Association and by the number of meter types certified to be DLMS / COSEM compliant. M-Bus (Meter-Bus) is a European standard for the remote reading of gas or electricity meters. M-Bus is also usable for other types of consumption meters. The M-Bus interface is made for communication on two wire, making it very cost effective. A radio variant of MBus (Wireless M-Bus) is also specified. The Open Metering System OMS stands for a manufacturer and utilities independent standardization for Meter-Bus based communication between utility meters (electricity, gas, water, district heat, heat cost allocators) and systems in the field of Smart meter. On the side of meter manufacturers there were mainly the members of the technical associations in Germany FIGAWA V1.0 2013-01-15 Page 159 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot (German Association for Gas and Water) and ZVEI (German Electrical and Electronics Industry Association), but also several other internationally operating companies joined to create a bundle of common definitions and specifications based on the European MeterBus standard (EN 13757) as well as the Dutch NTA 8130. The outcoming results were entered in the European standardization organization and is currently being discussed as an adoption or extension of EN 13757 (available in early 2013). The OMS specification documents are written in English and available to the public for free. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=Meter-Bus&oldid=506923869 • http://en.wikipedia.org/w/index.php?title=Open_Metering_System&oldid=508742369 • http://www.oms-group.org/en_index.html • http://www.oms-group.org/en_downloads.html EN 62056 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from V1.0 IEC 62056 IEC 62056: Electricity Metering Data Exchange - The DLMS/COSEM Suite Networks and Buses; Cables and Physical Networks; Power line communication / HomePlug; EN; Communications Protocols, Smart Metering; IEC 35.100 Open systems interconnection (OSI) 17.220.20 Measurement of electrical and magnetic quantities (Including measuring instruments, instrument transformers and Electric energy meters in buildings) 91.140.50 Electricity supply systems (Including electric energy meters in buildings, emergency electrical supplies, etc.) IEC62056 is a set of standards for Electricity metering – Data exchange for meter reading, tariff and load control by International Electrotechnical Commission. The IEC62056 standards are the International Standard versions of the DLMS/COSEM specification. [Source: Wikipedia] see Standard Parts below As some AAL business models use smart metering to access the customer's home, this standard is relevant. see Standard Parts below 2013-01-15 Page 160 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard IEC 62056-21 ed1.0 Title Electricity metering - Data exchange for meter reading, tariff and load control - Part 21: Direct local data exchange IEC 62056-31 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 31: Use of local area networks on twisted pair with carrier signalling IEC/TS 62056-41 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 41: Data exchange using wide area networks: Public switched telephone network (PSTN) with LINK+ protocol IEC 62056-42 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange IEC 62056-46 ed1.1 Electricity metering - Data exchange for meter reading, tariff Consol. with am1 and load control - Part 46: Data link layer using HDLC protocol IEC 62056-46 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 46: Data link layer using HDLC protocol IEC 62056-46-am1 ed1.0 Amendment 1 - Electricity metering - Data exchange for meter reading, tariff and load control - Part 46: Data link layer using HDLC protocol IEC 62056-47 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 47: COSEM transport layers for IPv4 networks IEC/TS 62056-51 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 51: Application layer protocols IEC/TS 62056-52 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 52: Communication protocols management distribution line message specification (DLMS) server IEC 62056-53 ed2.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 53: COSEM application layer IEC 62056-61 ed2.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 61: Object identification system (OBIS) IEC 62056-62 ed2.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 62: Interface classes IEC/TR 62051-1 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Glossary of terms - Part 1: Terms related to data exchange with metering equipment using DLMS/COSEM Description Part 21: Describes hardware and protocol specifications for local meter data exchange. In such systems, a hand-held unit (HHU) or a unit with equivalent functions is connected to a tariff device or a group of devices. V1.0 2013-01-15 Page 161 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Part 31: Describes two new architectures for local bus data exchange with stations either energized or not. For non-energized stations, the bus supplies energy for data exchange. Part 42: Specifies the physical layer services and protocols within the Companion Specification for Energy Metering (COSEM) three-layer connection oriented profile for asynchronous data communication. Part 46: Specifies the data link layer for connection-oriented, HDLC-based, asynchronous communication profile. Part 47: Specifies the transport layers for COSEM communication profiles for use on IPv4 networks. These communication profiles contain a connection-less and a connectionoriented transport layer, providing OSI-style services to the service user COSEM application layer. The connection-less transport layer is based on the Internet standard User Datagram Protocol. The connection-oriented transport layer is based on the Internet standard Transmission Control Protocol. Part 53: Specifies the COSEM application layer in terms of structure, services and protocols for COSEM clients and servers, and defines how to use the COSEM application layer in various communication profiles. It defines services for establishing and releasing application associations, and data communication services for accessing the methods and attributes of COSEM interface objects, defined in IEC 62056-62, using either logical name (LN) or short name (SN) referencing. Part 61: defines the identification codes (ID-codes) for commonly used data items in electricity metering equipment. This part of IEC 62056 specifies the overall structure of the identification system and the mapping of all data items to their identification codes. Part 62: specifies a model of a meter as it is seen through its communication interface(s). Generic building blocks are defined using object-oriented methods, in the form of interface classes to model meters from simple up to very complex functionality. External links • http://en.wikipedia.org/w/index.php?title=IEC_62056&oldid=513252367 • http://www.cenelec.eu/dyn/www/f? p=104:110:1530940690107308::::FSP_ORG_ID,FSP_PROJECT,FSP_LANG_ID:63,70 74,25 IEC 61334 Profile Reference Name Categories ICS V1.0 IEC 61334 IEC 61334: Distribution automation using distribution line carrier systems Communication Protocols; Smart Metering; IEC 29.240.20: Power transmission and distribution lines 33.200: Telecontrol. Telemetering ( including Supervising, Control and Data Acquisition System (SCADA)) 2013-01-15 Page 162 of 490 AALIANCE2 Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot IEC 61334 is a standard for low-speed reliable power line communications by electricity meters, water meters and SCADA. It is also known as S-FSK, for “spread frequency shift keying” and was formerly known as IEC 1334 before IEC's most recent renumbering. It is actually a series of standards describing the researched physical environment of power lines, a well-adapted physical layer, a workable low-power media access layer, and a management interface. Related standards use the robust physical layer (e.g. IP over S-FSK), but not the higher layers. [Source: Wikipedia] see Standard Parts below As some AAL business models use smart metering to access the customer's home, this standard is relevant. see Standard Parts below Standard Parts Standard IEC/TR 61334-1-1 ed1.0 IEC/TR 61334-1-2 ed1.0 IEC/TR 61334-1-4 ed1.0 IEC 61334-3-1 ed1.0 IEC 61334-3-21 ed1.0 IEC 61334-3-22 ed1.0 IEC 61334-4-1 ed1.0 IEC 61334-4-32 ed1.0 IEC 61334-4-33 ed1.0 IEC 61334-4-41 ed1.0 V1.0 Title Distribution automation using distribution line carrier systems - Part 1: General considerations - Section 1: Distribution automation system architecture Distribution automation using distribution line carrier systems - Part 1-2: General considerations - Guide for specification Distribution automation using distribution line carrier systems - Part 1: General considerations - Section 4: Identification of data transmission parameters concerning medium and lowvoltage distribution mains Distribution automation using distribution line carrier systems - Part 3-1: Mains signalling requirements - Frequency bands and output levels Distribution automation using distribution line carrier systems - Part 3: Mains signalling requirements - Section 21: MV phase-to-phase isolated capacitive coupling device Distribution automation using distribution line carrier systems - Part 3-22: Mains signalling requirements - MV phase-toearth and screen-to-earth intrusive coupling devices Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 1: Reference model of the communication system Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 32: Data link layer - Logical link control (LLC) Distribution automation using distribution line carrier systems - Part 4-33: Data communication protocols - Data link layer Connection oriented protocol Distribution automation using distribution line carrier systems 2013-01-15 Page 163 of 490 AALIANCE2 IEC 61334-4-42 ed1.0 IEC 61334-4-61 ed1.0 IEC 61334-4-511 ed1.0 IEC 61334-4-512 ed1.0 IEC 61334-5-1 ed2.0 IEC/TS 61334-5-2 ed1.0 IEC/TS 61334-5-3 ed1.0 IEC/TS 61334-5-4 ed1.0 IEC/TS 61334-5-5 ed1.0 IEC 61334-6 ed1.0 D4.1 Online Repository of Standards - Snapshot - Part 4: Data communication protocols - Section 41: Application protocol - Distribution line message specification Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 42: Application protocols - Application layer Distribution automation using distribution line carrier systems - Part 4-61: Data communication protocols - Network layer Connectionless protocol Distribution automation using distribution line carrier systems - Part 4-511: Data communication protocols - Systems management - CIASE protocol Distribution automation using distribution line carrier systems - Part 4-512: Data communication protocols - System management using profile 61334-5-1 - Management Information Base (MIB) Distribution automation using distribution line carrier systems - Part 5-1: Lower layer profiles - The spread frequency shift keying (S-FSK) profile Distribution automation using distribution line carrier systems - Part 5-2: Lower layer profiles - Frequency shift keying (FSK) profile Distribution automation using distribution line carrier systems - Part 5-3: Lower-layer profiles - Spread spectrum adaptive wideband (SS-AW) profile Distribution automation using distribution line carrier systems - Part 5-4: Lower layer profiles - Multi-carrier modulation (MCM) profile Distribution automation using distribution line carrier systems - Part 5-5: Lower layer profiles - Spread spectrum - fast frequency hopping (SS-FFH) profile Distribution automation using distribution line carrier systems - Part 6: A-XDR encoding rule Description The physical layer synchronizes a small packet of tones to the zero-crossing of the power line's voltage. The tones are chosen by utilities, not specified in the standard. Tones are usually between 20 kHz and 100 kHz, and should be separated by at least 10 kHz to prevent cross talk. One tone is chosen for mark (i.e. a binary 1), and the other for space (i.e. 0). The standard permits each zero-crossing to convey 1, 2, 4 or 8 bits, with decreased sensitivity to timing as the number of bits increases. In multiphase power lines, a separate signal might be sent on each phase to speed up the transmission. The standard's low speed is caused by the limited number of bits per power line cycle. The high reliability comes from its reliable timing system (i.e. zero crossing), high signal to noise ratio (frequencies are chosen to avoid common power line noise), lack of intermodulation distortion, and adaptive signal detection. V1.0 2013-01-15 Page 164 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot The most significant bits are sent first, unlike a conventional serial port. The data from zero crossings should be collected into 8-bit bytes. Each byte is collected into 42-byte packets. The first four bytes of each packet are a preamble to measure the channel's current condition. This is followed by 38 bytes of data, and 3 byte-times of silence. The physical layer is adaptive. The silence and the preamble allow the receiver's signal processing to measure the channel's noise ratios. Depending on the signal to noise ratios, the bits can be recovered from the difference between the power of the mark and space tones, the power of the mark tones only, or the space tones only. The system should be able to adjust the receiving method on each 42-byte packet. The bytes from the low-layer packets are reformed into bytes for the higher layers. The higher link-layer strongly resembles HDLC, except with a novel feature that allows selected stations to retransmit messages. The management interface layer provides remote control of a station's protocol layers, including diagnostics and configuration. For example, it lets a central controller read a unit's signal to noise ratios, and set the bit that enables a station to retransmit weak stations. The protocol layers are designed to integrate with any application layer, but the presence of a management interface suggests a design targeted to DLMS/COSEM, a widely-used EU standard for the application layer of meters and SCADA. DLMS/COSEM requires a management interface. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=IEC_61334&oldid=526148662 IEC 62056 Profile Reference Name Categories ICS Abstract V1.0 IEC 62056 IEC 62056: Electricity Metering Data Exchange - The DLMS/COSEM Suite Networks and Buses; Cables and Physical Networks; Power line Communication; IEC 17.220.20: Measurement of electrical and magnetic quantities (Including measuring instruments, instrument transformers and Electric energy meters in buildings) 35.100: Open systems interconnection (OSI) 91.140.50: Electricity supply systems (Including electric energy meters in buildings, emergency electrical supplies, etc.) The DLMS/COSEM standard suite (IEC 62056 / EN 13757-1) is the most widely accepted international standard for utility meter data exchange. This global acceptance is clearly demonstrated by the continued fast growth of the membership of the DLMS User Association and by the number of meter types certified to be DLMS / COSEM compliant. IEC62056 is a set of standards for Electricity 2013-01-15 Page 165 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot metering – Data exchange for meter reading, tariff and load control by International Electrotechnical Commission. The IEC62056 standards are the International Standard versions of the DLMS/COSEM specification. [Source: Wikipedia] Current Version see Standard Parts below Other editions EN 13757 AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from see Standard Parts below Standard Parts Standard IEC 62056-21 ed1.0 Title Electricity metering - Data exchange for meter reading, tariff and load control - Part 21: Direct local data exchange IEC 62056-31 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 31: Use of local area networks on twisted pair with carrier signalling IEC/TS 62056-41 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 41: Data exchange using wide area networks: Public switched telephone network (PSTN) with LINK+ protocol IEC 62056-42 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange IEC 62056-46 ed1.1 Electricity metering - Data exchange for meter reading, tariff Consol. with am1 and load control - Part 46: Data link layer using HDLC protocol IEC 62056-46 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 46: Data link layer using HDLC protocol IEC 62056-46-am1 ed1.0 Amendment 1 - Electricity metering - Data exchange for meter reading, tariff and load control - Part 46: Data link layer using HDLC protocol IEC 62056-47 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 47: COSEM transport layers for IPv4 networks IEC/TS 62056-51 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 51: Application layer protocols IEC/TS 62056-52 ed1.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 52: Communication protocols management distribution line message specification (DLMS) server IEC 62056-53 ed2.0 Electricity metering - Data exchange for meter reading, tariff and load control - Part 53: COSEM application layer IEC 62056-61 ed2.0 Electricity metering - Data exchange for meter reading, tariff V1.0 2013-01-15 Page 166 of 490 AALIANCE2 IEC 62056-62 ed2.0 IEC/TR 62051-1 ed1.0 D4.1 Online Repository of Standards - Snapshot and load control - Part 61: Object identification system (OBIS) Electricity metering - Data exchange for meter reading, tariff and load control - Part 62: Interface classes Electricity metering - Data exchange for meter reading, tariff and load control - Glossary of terms - Part 1: Terms related to data exchange with metering equipment using DLMS/COSEM Description IEC62056 is a set of standards for Electricity metering – Data exchange for meter reading, tariff and load control by International Electrotechnical Commission. The IEC62056 standards are the International Standard versions of the DLMS/COSEM specification. DLMS or Device Language Message Specification (originally Distribution Line Message Specification), is the suite of standards developed and maintained by the DLMS User Association and has been co-opted by the IEC TC13 WG14 into the IEC 62056 series of standards. The DLMS User Association has established a D Type liaison with IEC TC13 WG14 responsible for international standards for meter data exchange and establishing the IEC 62056 series. In this role, the DLMS UA provides maintenance, registration and conformance testing services for IEC 62056 DLMS/COSEM. COSEM or Companion Specification for Energy Metering, includes a set of specifications that defines the Transport and Application Layers of the DLMS protocol. The DLMS User Association defines the protocols into a set of four specification documents namely Green Book, Yellow Book, Blue Book and White Book. The Blue book describes the COSEM meter object model and the object identification system, the Green book describes the Architecture and Protocols, the Yellow book treats all the questions concerning conformance testing, the White book contains the glossary of terms. If a product conforms to DLMS Yellow Book then it automatically implies conformance to IEC62056 set of standards. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=IEC_62056&oldid=513252367 SML Profile Reference Name Categories ICS Abstract SML SML: Smart Message Language Communication Protocols; Smart Metering; Germany; VDE; Smart Message Language is a communication protocol for electricity meters developed in Germany for measurement data exchange and firmware upgrades. Current Version 1.03 (from 2008-11-12) Other editions V1.0 2013-01-15 Page 167 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance As some AAL business models use smart meters to access the customer's home, this standard is relevant. Available from http://www.vde.com/de/fnn/arbeitsgebiete/messwesen/Sym2/Infomateri al/Documents/SML_081112_103.pdf Description Smart Message Language is used for SyM2, eHZ and EDL21 meters. A SML message is specified as SML-request, SML-response or a combination of both. External links • http://de.wikipedia.org/w/index.php?title=Smart_Message_Language&oldid=104385877 (in German) SyM2 Profile Reference Name Categories ICS Abstract SyM2 SyM2: Synchronous Modular Meter Communication Protocols; Smart Metering: Germany; VDE SYM2 is the synonym for Synchronous Modular Meter, a modular and non monolithic concept for electricity meters with clocked registration periods. Current Version Other editions AAL Relevance As some AAL business models use smart meters to access the customer's home, this standard is relevant. Available from http://www.vde.com/de/fnn/arbeitsgebiete/messwesen/Sym2/Infomateri al/documents/sym2_ph_103_091006_eng.pdf Description The general specification for “Synchronous Modular Meters” (SyM²”) serves to provide development engineers at the meter manufacturers and the staff dealing with invoicing metering equipment at network operators, metering point operators and vendors with a harmonised working document for load profile meters featuring a clocked registration period. The goals of the SyM² have been defined as follows under the paramount consideration of cost reduction in operations management: • Modularised device concept with mounted or integrated function units and a standardised interface, • And thus installation of only those elements specifically required on site plus continual easy adaptation to new developments. • Use of meter readings in place of increments / power mean values, V1.0 2013-01-15 Page 168 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • dispensing with the maximum metering mechanism, • dispensing with integrated tariff control, • reducing the influence of the device clock by changing to a seconds index, • separation into a compulsory-calibration register and additional modules not subject to compulsory calibration for upgrading transparency by returning to simple measured values, • reducing the complexity of the individual modules, • firmware download utilising the concepts of the WE External links • http://sit.sit.fraunhofer.de/smv/publications/download/sd4rces_2011.pdf ZigBee SE Profile Reference Name Categories ICS Abstract ZigBee SE ZigBee SE: ZigBee Smart Energy Communications Protocols; Smart Metering; ZigBee ZigBee Smart Energy is the world's leading standard for interoperable products that monitor, control, inform and automate the delivery and use of energy and water. It helps create greener homes by giving consumers the information and automation needed to easily reduce their consumption and save money, too. Current Version 1.1, Version 2.0 is currently under development Other editions AAL Relevance As some AAL business models use smart metering to access the customer's home, this standard is relevant. Available from http://www.zigbee.org/Standards/ZigBeeSmartEnergy/Overview.aspx Description ZigBee Smart Energy is the world's leading standard for interoperable products that monitor, control, inform and automate the delivery and use of energy and water. It helps create greener homes by giving consumers the information and automation needed to easily reduce their consumption and save money, too. ZigBee Smart Energy version 1.1, the newest version for product development, adds several important features including dynamic pricing enhancements, tunnelling of other protocols, prepayment features, over-the-air updates and guaranteed backwards compatibility with certified ZigBee Smart Energy products version 1.0. This standard supports the diverse needs of a global ecosystem of utilities, product manufacturers and government groups as they plan to meet future energy and water V1.0 2013-01-15 Page 169 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot needs. All ZigBee Smart Energy products are ZigBee Certified to perform regardless of manufacturer, allowing utilities and consumers to purchase with confidence. Every product needed to implement a robust ZigBee Smart Energy home area network (HAN) is available. These products make it easy for utilities and governments to deploy smart grid solutions that are secure, easy to install and consumer-friendly. Some of the world's leading utilities, energy service providers, product manufacturers and technology companies are supporting the development of ZigBee Smart Energy. Several other standards groups are also involved with extending the reach of ZigBee Smart Energy to more homes around the world. Smart Energy Profile version 2.0 is currently under development in cooperation with a number of other standards development groups. It will offer IP-based control for advanced metering infrastructure and home area networks. This version will not replace ZigBee Smart Energy version 1, rather it will offer utilities and energy service providers another choice when creating their advanced metering infrastructure and home area networks (HANs). In addition to all the services and devices found in ZigBee Smart Energy version 1, version 2.0 will feature control of plug-in electric vehicle (PEV) charging, installation, configuration and firmware download for HAN devices, prepay services, user information and messaging, load control, demand response and common information and application profile interfaces for wired and wireless HANs. V1.0 2013-01-15 Page 170 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 3. File Formats and Persistent Data Structures Note: Many file formats and audio/video encodings not covered here are described in the Wikipedia lists of file formats and codecs. 3.1. General Purpose • Codecs • List of file name extensions 3.1.1 Image formats BMP Profile Reference Name Categories BMP BMP: Windows Bitmap File Formats and Persistent Data Structures; General Purpose; Image formats ICS Abstract The BMP file extension is commonly used for Bitmap files - standard, non-compressed bit-mapped graphics format used in the Windows. Current Version Other editions AAL Relevance Popular image format, may be used in AAL scenarios. Available from Description Bitmap images, also called raster images, use a grid (the bitmap or raster) of small squares known as pixels to represent images. Each pixel is assigned a specific location and colour value. Windows bitmap files are stored in a device-independent bitmap (DIB) format that allows Windows to display the bitmap on any type of display device. The term “device independent” means that the bitmap specifies pixel colour in a form independent of the method used by a display to represent colour The default filename extension of a Windows DIB file is .BMP. Each bitmap file contains a bitmap-file header, a bitmapinformation header, a colour table, and an array of bytes that defines the bitmap bits. External links • http://en.wikipedia.org/wiki/BMP_file_format (good format description) V1.0 2013-01-15 Page 171 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • http://www.digicamsoft.com/bmp/bmp.html • http://www.file-extensions.org/bmp-file-extension GIF Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from Graphics Interchange Format [GIF] GIF: Graphics Interchange Format File Formats and Persistent Data Structures; General Purpose; Image formats Image format that supports supports up to 8 bits per pixel, allowing a single image to reference a palette of up to 256 distinct colours GIF 1987 Popular image format, may be used in AAL scenarios. http://www.w3.org/Graphics/GIF/spec-gif87.txt Description The format supports up to 8 bits per pixel thus allowing a single image to reference a palette of up to 256 distinct colours The colours are chosen from the 24-bit RGB colour space. It also supports animations and allows a separate palette of 256 colours for each frame. The colour limitation makes the GIF format unsuitable for reproducing colour photographs and other images with continuous colour, but it is well-suited for simpler images such as graphics or logos with solid areas of colour GIFs are suitable for sharpedged line art (such as logos) with a limited number of colours This takes advantage of the format's lossless compression, which favours flat areas of uniform colour with well defined edges. GIFs can be used to store low-colour sprite data for games. GIFs can be used for small animations and low-resolution film clips. In view of the general limitation on the GIF image palette to 256 colours, it is not usually used as a format for digital photography. External links • http://www.w3.org/Graphics/GIF/spec-gif87.txt • http://www.file-extensions.org/gif-file-extension • http://en.wikipedia.org/w/index.php?title=Graphics_Interchange_Format JPEG Profile Reference Name V1.0 JPEG JPEG (Joint Photographic Experts Group) 2013-01-15 Page 172 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories File Formats and Persistent Data Structures; General Purpose; Image formats ICS 35.040: Character sets and information coding Abstract JPEG is a lossy image compression algorithm that significantly reduces the file size of the original image at the cost of quality. The higher the compression ratio the lower the quality of the .jpg file. Current Version see Standard Parts below Other editions T.81 (09/92) T.83 (11/94) T.84 (07/96) T.86 (06/98) T.871 (05/11) ISO/IEC JTC1 - ISO TC97 WG8 AAL Relevance Popular image format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 10918-1:1994 ISO/IEC 109181:1994/Cor 1:2005 ISO/IEC 10918-2:1995 Title Information technology – Digital compression and coding of continuous-tone still images: Requirements and guidelines Patent information update Information technology – Digital compression and coding of continuous-tone still images: Compliance testing ISO/IEC 10918-3:1997 Information technology – Digital compression and coding of continuous-tone still images: Extensions ISO/IEC 10918Provisions to allow registration of new compression types and 3:1997/Amd 1:1999 versions in the SPIFF header ISO/IEC 10918-4:1999 Information technology – Digital compression and coding of continuous-tone still images: Registration of JPEG profiles, SPIFF profiles, SPIFF tags, SPIFF colour spaces, APPn markers, SPIFF compression types and Registration Authorities (REGAUT) All(?) parts also freely available from the ITU: http://www.itu.int/ITUT/studygroups/com16/jpeg1x/index.html Description JPEG is based on a 24-bit colour palette and supports 16.7 million colours However it is a lossy compression format, which means that it drops information that is compressed out. Compression ratios may range from 10:1 to 20:1 and most graphic application programs (such as Adobe Photoshop) allow you to choose the compression rate. The degree of compression can be adjusted, allowing a selectable tradeoff between storage size and image quality. The JPEG file format is best suited for digital photographs, where the typical compressional rate with very low quality loss is around 10:1. External links • http://www.file-extensions.org/jpg-file-extension V1.0 2013-01-15 Page 173 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • http://en.wikipedia.org/wiki/JPEG#The_JPEG_standard PNG Profile Reference Name Categories PNG PNG: Portable Network Graphics File Formats and Persistent Data Structures; General Purpose; Image formats; W3C ICS 35.140: Computer graphics Abstract PNG is a bitmap graphics format similar to GIF, that uses image compression mainly for web purposes. Current Version ISO/IEC 15948:2004 Other editions W3C Recommendation on 1st October, 1996 updated to a second edition incorporating all errata on 10 November 2003. AAL Relevance Popular image format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 15948:2004 Title Information technology – Computer graphics and image processing – Portable Network Graphics (PNG): Functional specification Description Portable Network Graphics (PNG) is a bitmapped image format that employs lossless data compression. PNG is a lossless format with 16.7 million colours, index colour, grayscale, true colour, transparency and also is streamable, which makes it superior to GIF. The format was approved as a standard by the WWW consortium (W3C) to replace GIF, because GIF is using a patented data compression algorithm called LZW. In contrast, PNG is completely patent- and license-free. Originally only Netscape Navigator and Microsoft Internet Explorer supported PNG file format, but today every web browser can read the format correctly. External links • http://www.w3.org/Graphics/PNG/ • http://en.wikipedia.org/wiki/Portable_Network_Graphics • http://www.file-extensions.org/png-file-extension V1.0 2013-01-15 Page 174 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot RAW Profile Reference Name Categories RAW RAW File Formats and Persistent Data Structures; General Purpose; Image formats ICS Abstract A camera raw image file contains minimally processed data from the image sensor of either a digital camera, image scanner, or motion picture film scanner. Current Version Other editions AAL Relevance AAL optical sensor devices produce RAW data Available from Description Raw files are so named because they are not yet processed and therefore are not ready to be printed or edited with a bitmap graphics editor. Raw image files are sometimes called digital negatives, as they fulfil the same role as negatives in film photography: that is, the negative is not directly usable as an image, but has all of the information needed to create an image External links • http://en.wikipedia.org/wiki/Raw_image_format TIFF Profile Reference Name Categories TIFF TIFF: Tagged Image File Format File Formats and Persistent Data Structures; General Purpose; Image formats; ISO; IETF ICS 37.040.99: Other standards related to photography; 35.240.30: IT applications in information, documentation and publishing; 37.100.99:Other standards related to graphic technology; Abstract TIFF is a file format for storing images. It is one of the most widely supported lossless (does not lose information during compression) file formats for storing bit-mapped images. Current Version see Standard Parts below Other editions RFC 2306 (TIFF-F Facsimile); RFC 3949 (TIFF-FX Internet Fax); V1.0 2013-01-15 Page 175 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot TIFF Revision 6.0 Final — June 3, 1992 AAL Relevance Popular image format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO 12234-2:2001 ISO/AWI 12234-2 (under development) ISO 12639:2004 ISO 12639:2004/Amd 1:2007 Title Electronic still-picture imaging – Removable memory – Part 2: TIFF/EP image data format Graphic technology – Prepress digital data exchange – Tag image file format for image technology (TIFF/IT); Use of JBIG2-Amd2 compression in TIFF/IT Description TIFF is a flexible, adaptable file format for handling images and data within a single file, by including the header tags (size, definition, image-data arrangement, applied image compression) defining the image's geometry. For example, a TIFF file can be a container holding compressed (lossy) JPEG and (lossless) PackBits compressed images. The ability to store image data in a lossless format makes a TIFF file a useful image archive, because, unlike standard JPEG files, a TIFF file using lossless compression (or none) may be edited and re-saved without losing image quality. This is not the case when using the TIFF as a container holding compressed JPEG. Other TIFF options are layers and pages. External links • http://en.wikipedia.org/wiki/Tagged_Image_File_Format • http://tools.ietf.org/html/rfc2306 • http://tools.ietf.org/html/rfc3949 • http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf 3.1.2 Video formats AVI Profile Reference Name Categories ICS Abstract V1.0 AVI AVI: Audio Video Interleave File Formats and Persistent Data Structures; General Purpose; Video formats AVI is a multimedia container format introduced by Microsoft as part of its Video for Windows technology. AVI files can contain both audio and 2013-01-15 Page 176 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot video data in a file container that allows synchronous audio-with-video playback. Current Version Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from Description AVI is a derivative of the Resource Interchange File Format (RIFF), which divides a file's data into blocks, or “chunks.” Each “chunk” is identified by a FourCC tag. An AVI file takes the form of a single chunk in a RIFF formatted file, which is then subdivided into two mandatory “chunks” and one optional “chunk”. By way of the RIFF format, the audio-visual data contained in the “movie” chunk can be encoded or decoded by software called a codec, which is an abbreviation for (en)coder/decoder. Upon creation of the file, the codec translates between raw data and the (compressed) data format used inside the chunk. An AVI file may carry audio/visual data inside the chunks in virtually any compression scheme, including Full Frame (Uncompressed), Intel Real Time (Indeo), Cinepak, Motion JPEG, Editable MPEG, VDOWave, ClearVideo / RealVideo, QPEG, and MPEG-4 Video. External links • http://en.wikipedia.org/wiki/Audio_Video_Interleave • http://www.file-extensions.org/avi-file-extension FLV Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from FLV FLV: Flash Video File Formats and Persistent Data Structures; General Purpose; Video formats Flash Video is a container file format used to deliver video over the Internet using Adobe Flash Player versions 6–11. Flash Video content may also be embedded within SWF files. There are two different video file formats known as Flash Video: FLV and F4V. Popular video format, may be used in AAL scenarios. - Description The audio and video data within FLV files are encoded in the same manner as they are within SWF files. The latter F4V file format is based on the ISO base media file format and V1.0 2013-01-15 Page 177 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot is starting with Flash Player 9 update 3. Both formats are supported in Adobe Flash Player and currently developed by Adobe Systems. Flash Video has been accepted as the default online video format by many sites. Flash Video is viewable on most operating systems via the Adobe Flash Player and web browser plug-in or one of several third-party programs. Apple's iOS devices do not support the Flash Player plug-in and so require other delivery methods such as provided by the Adobe Flash Media Server. Supported media types in FLV file format: Video: On2 VP6, Sorenson Spark (Sorenson H.263), Screen video, H.264; Audio: MP3, ADPCM, Linear PCM, Nellymoser, Speex, AAC, G.711 (reserved for internal use). External links • http://en.wikipedia.org/wiki/Flash_Video • http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flv/pdfs/vi deo_file_format_spec_v10.pdf H.264 Profile Reference Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding [H.264][MPEG4-AVC] Name H.264/MPEG-4 AVC/ ISO/IEC 14496-10 Categories File Formats and Persistent Data Structures; General Purpose; Video formats ICS 35.040: Character sets and information coding Abstract H.264/MPEG-4 Part 10 or AVC (Advanced Video Coding) is a standard for video compression, and is currently one of the most commonly used formats for the recording, compression, and distribution of high definition video. Current Version ISO/IEC 14496-10:2012 Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.h tm?csnumber=61490 Description H.264/MPEG-4 AVC is a block-oriented motion-compensation-based codec standard developed by the ITU-T Video Coding Experts Group (VCEG) together with the International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) joint working group, the Moving Picture Experts Group (MPEG). The product of this partnership effort is known as the Joint Video Team (JVT). The ITU-T H.264 standard and the ISO/IEC MPEG-4 AVC standard (formally, ISO/IEC 14496-10 – MPEG-4 Part 10, Advanced Video Coding) are jointly maintained so that they have identical technical content. V1.0 2013-01-15 Page 178 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot H.264 is perhaps best known as being one of the codec standards for Blu-ray Discs; all Blu-ray Disc players must be able to decode H.264. It is also widely used by streaming internet sources, such as videos from Vimeo, YouTube, and the iTunes Store, web software such as the Adobe Flash Player and Microsoft Silverlight, and also various HDTV broadcasts over terrestrial (ATSC, ISDB-T, DVB-T or DVB-T2), cable (DVB-C) and satellite (DVB-S and DVB-S2). The ISO/IEC 14496-10:2012 specifies advanced video coding for the coding of audiovisual objects. It was developed in response to a growing need for higher compression of moving pictures for various applications such as digital storage media, television broadcasting, Internet streaming, and real-time audiovisual communication. ISO/IEC 14496-10:2012 specifies a coded video representation syntax and an associated decoding process that are suitable for use in a wide variety of applications and network environments. This standard includes the specification of advanced video coding (AVC) and associated extensions to enable scalable video coding (SVC) and multiview video coding (MVC). External links • http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC MPEG-1 Profile Reference Name Categories MPEG-1 MPEG-1/ ISO/IEC 11172 File Formats and Persistent Data Structures; General Purpose; Video formats ICS 35.040: Character sets and information coding Abstract MPEG-1 is a standard for lossy compression of video and audio. It is designed to compress VHS-quality raw digital video and CD audio down to 1.5 Mbit/s (26:1 and 6:1 compression ratios respectively) without excessive quality loss. The MPEG-1 standard is published as ISO/IEC 11172. Current Version see Standard Parts below Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 11172-1:1993 ISO/IEC 11172-1:1993/Cor 1:1996 ISO/IEC 11172-1:1993/Cor 2:1999 ISO/IEC 11172-2:1993 ISO/IEC 11172-2:1993/Cor 1:1996 V1.0 Title Information technology – Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s – Part 1: Systems Information technology – Coding of moving pictures and associated audio for digital storage 2013-01-15 Page 179 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 11172-2:1993/Cor 2:1999 ISO/IEC 11172-2:1993/Cor 3:2003 ISO/IEC 11172-2:1993/Cor 4:2006 ISO/IEC 11172-3:1993 ISO/IEC 11172-3:1993/Cor 1:1996 media at up to about 1,5 Mbit/s – Part 2: Video Information technology – Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s – Part 3: Audio ISO/IEC 11172-4:1995 Information technology – Coding of moving ISO/IEC 11172-4:1995/Cor 1:2007 pictures and associated audio for digital storage media at up to about 1,5 Mbit/s – Part 4: Compliance testing ISO/IEC TR 11172-5:1998 Information technology – Coding of moving ISO/IEC TR 11172-5:1998/Cor 1:2007 pictures and associated audio for digital storage media at up to about 1,5 Mbit/s – Part 5: Software simulation Description This International Standard is published in four parts. Part 1 - Systems - specifies the system coding layer of the standard. It defines a multiplexed structure for combining audio and video data and means of representing the timing information needed to replay synchronized sequences in real-time. Part 2 - video - specifies the coded representation of video data and the decoding process required to reconstruct pictures. Part 3 - audio specifies the coded representation of audio data and the decoding process required to reconstruct audio. Part 4 - compliance testing - specifies procedures to determine characteristics of coded bitstreams and to test compliance of bitstreams and decoders with the requirements specified in Parts 1, 2 and 3. MPEG-2 Profile Reference Name Categories MPEG-2 MPEG-2 File Formats and Persistent Data Structures; General Purpose; Video formats ICS 35.040: Character sets and information coding Abstract MPEG-2 is a standard for “the generic coding of moving pictures and associated audio information”. It describes a combination of lossy video compression and lossy audio data compression methods which permit storage and transmission of movies using currently available storage media and transmission bandwidth. Current Version ISO/IEC 13818 Other editions see Standard Parts below AAL Relevance Popular video format, may be used in AAL scenarios. Available from see Standard Parts below V1.0 2013-01-15 Page 180 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard ISO/IEC 13818-1:2007 ISO/IEC 13818-1:2007/Amd 1:2007 ISO/IEC 13818-1:2007/Amd 2:2008 ISO/IEC 13818-1:2007/Amd 3:2009 ISO/IEC 13818-1:2007/Amd 3:2009/Cor 1:2011 ISO/IEC 13818-1:2007/Amd 4:2009 ISO/IEC 13818-1:2007/Amd 5:2011 ISO/IEC 13818-1:2007/Amd 6:2011 ISO/IEC 13818-1:2007/Cor 1:2008 ISO/IEC 13818-1:2007/Cor 2:2009 ISO/IEC 13818-1:2007/Cor 3:2011 Title Information technology – Generic coding of moving pictures and associated audio information: Systems Transport of MPEG-4 streaming text and MPEG-4 lossless audio over MPEG-2 systems Carriage of auxiliary video data Transport of scalable video over Rec. ITU-T H.222.0 - ISO/IEC 13818-1 - ISO/IEC 13818-2:2000 ISO/IEC 13818-2:2000/Amd 1:2001 ISO/IEC 13818-2:2000/Amd 2:2007 ISO/IEC 13818-2:2000/Amd 3:2010 ISO/IEC 13818-2:2000/Cor 1:2002 ISO/IEC 13818-2:2000/Cor 2:2007 Information technology – Generic coding of moving pictures and associated audio information: Video Content description data Support for colour spaces New level for 1080@50p/60p - ISO/IEC 13818-3:1998 Information technology – Generic coding of moving pictures and associated audio information – Part 3: Audio Information technology – Generic coding of moving pictures and associated audio information – Part 4: Conformance testing MPEG-2 IPMP conformance testing Additional audio conformance test sequences - ISO/IEC 13818-4:2004 ISO/IEC 13818-4:2004/Amd 1:2005 ISO/IEC 13818-4:2004/Amd 2:2005 ISO/IEC 13818-4:2004/Amd 2:2005/Cor 1:2007 ISO/IEC 13818-4:2004/Amd 2:2005/Cor 2:2009 ISO/IEC 13818-4:2004/Amd 3:2009 V1.0 2013-01-15 Transport of multiview video over Rec. ITU-T H.222.0 - ISO/IEC 13818-1 Transport of JPEG 2000 Part 1 (ITU-T Rec T.800 - ISO/IEC 15444-1) video over ITU-T Rec H.222.0 - ISO/IEC 13818-1 Extension to AVC video descriptor and signalling of operation points for MVC Corrections concerning VBV buffer size, semantics of splice_type and removal rate from transport buffer for ITU-T H.264 ISO/IEC 14496-10 advanced video coding Page 181 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 13818-4:2004/Cor 1:2007 ISO/IEC 13818-4:2004/Cor 2:2011 ISO/IEC 13818-4:2004/Cor 3:2012 - ISO/IEC TR 13818-5:2005 Information technology – Generic coding of moving pictures and associated audio information – Part 5: Software simulation Information technology – Generic coding of moving pictures and associated audio information – Part 6: Extensions for DSMCC Additions to support data broadcasting Additions to support synchronized download services, opportunistic data services and resource announcement in broadcast and interactive services Transport buffer model in support of synchronized user-to-network download protocol - ISO/IEC 13818-6:1998 ISO/IEC 13818-6:1998/Amd 1:2000 ISO/IEC 13818-6:1998/Amd 1:2000/Cor 1:2002 ISO/IEC 13818-6:1998/Amd 2:2000 ISO/IEC 13818-6:1998/Amd 3:2001 ISO/IEC 13818-6:1998/Cor 1:1999 ISO/IEC 13818-6:1998/Cor 2:2002 Level for 1080@50p/60p conformance testing - ISO/IEC 13818-7:2006 ISO/IEC 13818-7:2006/Amd 1:2007 ISO/IEC 13818-7:2006/Cor 1:2009 ISO/IEC 13818-7:2006/Cor 2:2010 Information technology – Generic coding of moving pictures and associated audio information – Part 7: Advanced Audio Coding (AAC) Transport of MPEG Surround in AAC - ISO/IEC 13818-9:1996 Information technology – Generic coding of moving pictures and associated audio information – Part 9: Extension for real time interface for systems decoders Information technology – Generic coding of moving pictures and associated audio information – Part 10: Conformance extensions for Digital Storage Media Command and Control (DSM-CC) Information technology – Generic coding of moving pictures and associated audio information – Part 11: IPMP on MPEG-2 ISO/IEC 13818-10:1999 ISO/IEC 13818-11:2004 V1.0 2013-01-15 Page 182 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot systems Description MPEG-2 is widely used as the format of digital television signals that are broadcast by terrestrial (over-the-air), cable, and direct broadcast satellite TV systems. It also specifies the format of movies and other programs that are distributed on DVD and similar discs. TV stations, TV receivers, DVD players, and other equipment are often designed to this standard. MPEG-2 was the second of several standards developed by the Moving Pictures Expert Group (MPEG) and is an international standard (ISO/IEC 13818). MPEG-4 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from MPEG-4 MPEG-4/ ISO/IEC-14496 File Formats and Persistent Data Structures; General Purpose; Video formats 35.040: Character sets and information coding MPEG-4 is a method of defining compression of audio and visual (AV) digital data. Uses of MPEG-4 include compression of AV data for web (streaming media) and CD distribution, voice (telephone, videophone) and broadcast television applications. see Standard Parts below Popular video format, may be used in AAL scenarios. see Standard Parts below Standard Parts Standard ISO/IEC 14496-1:2010 ISO/IEC 14496-1:2010/Amd 1:2010 Title Information technology – Coding of audiovisual objects – Part 1: Systems Usage of LASeR in MPEG-4 systems and Registration Authority for MPEG-4 descriptors ISO/IEC 14496-2:2004 ISO/IEC 14496-2:2004/Amd 1:2004 ISO/IEC 14496-2:2004/Amd 2:2005 ISO/IEC 14496-2:2004/Amd 3:2007 ISO/IEC 14496-2:2004/Amd 3:2007/Cor 1:2008 ISO/IEC 14496-2:2004/Amd 4:2008 ISO/IEC 14496-2:2004/Amd 5:2009 ISO/IEC 14496-2:2004/Cor 1:2004 Information technology – Coding of audiovisual objects – Part 2: Visual Error resilient simple scalable profile New Levels for Simple Profile Support for colour spaces Simple profile level 6 Simple studio profile levels 5 and 6 - V1.0 2013-01-15 Page 183 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14496-2:2004/Cor 2:2007 ISO/IEC 14496-2:2004/Cor 3:2008 ISO/IEC 14496-2:2004/Cor 4:2010 - ISO/IEC 14496-3:2009 ISO/IEC 14496-3:2009/Amd 1:2009 ISO/IEC 14496-3:2009/Amd 2:2010 ISO/IEC 14496-3:2009/Amd 3:2012 ISO/IEC 14496-3:2009/Cor 1:2009 ISO/IEC 14496-3:2009/Cor 2:2011 ISO/IEC 14496-3:2009/Cor 3:2012 ISO/IEC 14496-3:2009/Cor 4:2012 Information technology – Coding of audiovisual objects – Part 3: Audio HD-AAC profile ALS simple profile and transport of SAOC Transport of unified speech and audio coding (USAC) - ISO/IEC 14496-4:2004 ISO/IEC 14496-4:2004/Amd 1:2005 ISO/IEC 14496-4:2004/Amd 1:2005/Cor 1:2005 ISO/IEC 14496-4:2004/Amd 1:2005/Cor 2:2008 ISO/IEC 14496-4:2004/Amd 2:2005 ISO/IEC 14496-4:2004/Amd 3:2005 ISO/IEC 14496-4:2004/Amd 4:2005 ISO/IEC 14496-4:2004/Amd 5:2005 ISO/IEC 14496-4:2004/Amd 6:2005 ISO/IEC 14496-4:2004/Amd 6:2005/Cor 1:2007 ISO/IEC 14496-4:2004/Amd 9:2006 ISO/IEC 14496-4:2004/Amd 9:2006/Cor 1:2007 ISO/IEC 14496-4:2004/Amd 9:2006/Cor 2:2012 ISO/IEC 14496-4:2004/Amd 10:2005 ISO/IEC 14496-4:2004/Amd 17:2007 ISO/IEC 14496-4:2004/Amd 23:2008 ISO/IEC 14496-4:2004/Amd 24:2008 ISO/IEC 14496-4:2004/Amd 25:2008 ISO/IEC 14496-4:2004/Amd 26:2008 ISO/IEC 14496-4:2004/Amd 27:2008 ISO/IEC 14496-4:2004/Amd 28:2008 ISO/IEC 14496-4:2004/Amd 29:2008 ISO/IEC 14496-4:2004/Amd 30:2009 ISO/IEC 14496-4:2004/Amd 31:2009 ISO/IEC 14496-4:2004/Amd 35:2009 ISO/IEC 14496-4:2004/Amd 37:2009 ISO/IEC 14496-4:2004/Amd 38:2010 ISO/IEC 14496-4:2004/Amd 38:2010/Cor Information technology – Coding of audiovisual objects – Part 4: Conformance testing Conformance testing for MPEG-4 MPEG-4 conformance extensions for XMT and media nodes Visual new levels and tools IPMPX conformance extensions Conformance extensions for error-resilient simple scalable profile Advanced Video Coding conformance AVC fidelity range extensions conformance Conformance extensions for simple profile levels 4a and 5 Advanced text and 2D graphics conformance Synthesized texture conformance Synthesized texture conformance File format conformance LASeR and SAF conformance Conformance levels and bitstreams for Open Font Format LASeR and SAF extensions conformance Conformance extensions for simple profile level 6 Symbolic Music Representation conformance Conformance testing for new profiles for professional applications V1.0 2013-01-15 Page 184 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 1:2012 ISO/IEC 14496-4:2004/Amd 40:2011 ISO/IEC 14496-4:2004/Cor 1:2005 ISO/IEC 14496-4:2004/Cor 2:2007 ISO/IEC 14496-4:2004/Cor 4:2008 ISO/IEC 14496-4:2004/Cor 7:2010 Conformance testing for SVC profiles Simple studio profile levels 5 and 6 conformance testing Additional file format conformance Conformance testing for Multiview Video Coding ExtendedCore2D conformance - ISO/IEC 14496-5:2001 ISO/IEC 14496-5:2001/Amd 1:2002 ISO/IEC 14496-5:2001/Amd 1:2002/Cor 1:2008 ISO/IEC 14496-5:2001/Amd 2:2003 ISO/IEC 14496-5:2001/Amd 3:2003 ISO/IEC 14496-5:2001/Amd 4:2004 ISO/IEC 14496-5:2001/Amd 5:2004 ISO/IEC 14496-5:2001/Amd 5:2004/Cor 1:2011 ISO/IEC 14496-5:2001/Amd 6:2005 ISO/IEC 14496-5:2001/Amd 6:2005/Cor 1:2006 ISO/IEC 14496-5:2001/Amd 7:2005 ISO/IEC 14496-5:2001/Amd 8:2006 ISO/IEC 14496-5:2001/Amd 9:2007 ISO/IEC 14496-5:2001/Amd 10:2007 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 1:2008 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 2:2008 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 3:2009 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 4:2010 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 5:2011 ISO/IEC 14496-5:2001/Amd 10:2007/Cor 6:2012 ISO/IEC 14496-5:2001/Amd 11:2007 ISO/IEC 14496-5:2001/Amd 12:2007 ISO/IEC 14496-5:2001/Amd 13:2008 ISO/IEC 14496-5:2001/Amd 14:2009 ISO/IEC 14496-5:2001/Amd 14:2009/Cor 1:2010 Information technology – Coding of audiovisual objects – Part 5: Reference software Reference software for MPEG-4 MPEG-4 reference software extensions for XMT and media nodes Visual new level and tools IPMPX reference software extensions Reference software extensions for error resilient simple scalable profile Advanced Video Coding (AVC) and High Efficiency Advanced Audio Coding (HE AAC) reference software AFX reference software extensions AVC fidelity range extensions reference software Morphing & Textures reference software SSC, DST, ALS and SLS reference software V1.0 2013-01-15 MPEG-J GFX Reference software Updated file format reference software Geometry and shadow reference software Open Font Format reference software Reference software for Multiview Video Coding Symbolic Music Representation reference Page 185 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14496-5:2001/Amd 15:2010 ISO/IEC 14496-5:2001/Amd 16:2008 ISO/IEC 14496-5:2001/Amd 17:2008 ISO/IEC 14496-5:2001/Amd 18:2008 ISO/IEC 14496-5:2001/Amd 19:2009 ISO/IEC 14496-5:2001/Amd 20:2009 ISO/IEC 14496-5:2001/Amd 21:2009 ISO/IEC 14496-5:2001/Amd 22:2009 ISO/IEC 14496-5:2001/Amd 23:2010 ISO/IEC 14496-5:2001/Amd 24:2009 ISO/IEC 14496-5:2001/Amd 24:2009/Cor 1:2012 ISO/IEC 14496-5:2001/Amd 25:2009 ISO/IEC 14496-5:2001/Amd 26:2011 ISO/IEC 14496-5:2001/Amd 27:2011 ISO/IEC 14496-5:2001/Amd 28:2011 ISO/IEC 14496-5:2001/Amd 29:2011 ISO/IEC 14496-5:2001/Amd 30:2011 ISO/IEC 14496-5:2001/Amd 31:2012 software Reference software for LASeR and SAF Reference software for new profiles for professional applications Reference software for Scalable Video Coding MPEG-1 and -2 on MPEG-4 reference software and BSAC extensions Frame-based Animated Mesh Compression reference software Reference software for 3D Graphics Compression Model (3DGCM) Synthesized texture reference software Reference software for AAC-ELD Reference software for scene partitioning Reference software for scalable complexity 3D mesh coding in 3DG compression model Scalable complexity 3D mesh coding reference software Reference software for LASeR adaptation tools Reference software for LASeR presentation and modification of structured information (PMSI) tools ExtendedCore2D reference software Reference software for efficient representation of 3D meshes with multiple attributes ISO/IEC 14496-6:2000 Information technology – Coding of audiovisual objects – Part 6: Delivery Multimedia Integration Framework (DMIF) Information technology – Coding of audiovisual objects – Part 7: Optimized reference software for coding of audio-visual objects Information technology – Coding of audiovisual objects – Part 8: Carriage of ISO/IEC 14496 contents over IP networks Information technology – Coding of audiovisual objects – Part 9: Reference hardware description Information technology – Coding of audiovisual objects – Part 10: Advanced Video Coding Information technology – Coding of audiovisual objects – Part 11: Scene description ISO/IEC TR 14496-7:2004 ISO/IEC 14496-8:2004 ISO/IEC TR 14496-9:2009 ISO/IEC 14496-10:2012 ISO/IEC 14496-11:2005 ISO/IEC 14496-11:2005/Amd 5:2007 V1.0 2013-01-15 Page 186 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14496-11:2005/Amd 6:2009 ISO/IEC 14496-11:2005/Amd 7:2010 ISO/IEC 14496-11:2005/Cor 5:2008 ISO/IEC 14496-11:2005/Cor 6:2007 and application engine Support for Symbolic Music Notation ExtendedCore2D profile - ISO/IEC 14496-12:2012 Information technology – Coding of audiovisual objects – Part 12: ISO base media file format Information technology – Coding of audiovisual objects – Part 13: Intellectual Property Management and Protection (IPMP) extensions Information technology – Coding of audiovisual objects – Part 14: MP4 file format Handling of MPEG-4 audio enhancement layers - ISO/IEC 14496-13:2004 ISO/IEC 14496-14:2003 ISO/IEC 14496-14:2003/Amd 1:2010 ISO/IEC 14496-14:2003/Cor 1:2006 ISO/IEC 14496-15:2010 ISO/IEC 14496-15:2010/Amd 1:2011 ISO/IEC 14496-15:2010/Cor 1:2011 ISO/IEC 14496-15:2010/Cor 2:2012 Information technology – Coding of audiovisual objects – Part 15: Advanced Video Coding (AVC) file format Sub-track definitions - ISO/IEC 14496-16:2011 ISO/IEC 14496-16:2011/Amd 1:2011 Information technology – Coding of audiovisual objects – Part 16: Animation Framework eXtension (AFX) Efficient representation of 3D meshes with multiple attributes Information technology – Coding of audiovisual objects – Part 17: Streaming text format Information technology – Coding of audiovisual objects – Part 18: Font compression and streaming - ISO/IEC 14496-17:2006 ISO/IEC 14496-18:2004 ISO/IEC 14496-18:2004/Cor 1:2007 ISO/IEC 14496-19:2004 ISO/IEC 14496-20:2008 ISO/IEC 14496-20:2008/Amd 1:2009 ISO/IEC 14496-20:2008/Amd 2:2010 V1.0 2013-01-15 Information technology - Coding of audiovisual objects – Part 19: Synthesized texture stream Information technology – Coding of audiovisual objects – Part 20: Lightweight Application Scene Representation (LASeR) Page 187 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 14496-20:2008/Amd 3:2010 ISO/IEC 14496-20:2008/Cor 1:2010 and Simple Aggregation Format (SAF) Extensions to support SVGT1.2 Technology for scene adaptation Presentation and Modification of Structured Information (PMSI) - ISO/IEC 14496-21:2006 ISO/IEC 14496-21:2006/Cor 1:2007 Information technology – Coding of audiovisual objects – Part 21: MPEG-J Graphics Framework eXtensions (GFX) - ISO/IEC 14496-22:2009 ISO/IEC 14496-22:2009/Amd 1:2010 ISO/IEC 14496-22:2009/Amd 2:2012 ISO/IEC 14496-22:2009/Cor 1:2010 Information technology – Coding of audiovisual objects – Part 22: Open Font Format Support for many-to-one range mappings Additional script and language tags - ISO/IEC 14496-23:2008 Information technology – Coding of audiovisual objects – Part 23: Symbolic Music Representation Information technology – Coding of audiovisual objects – Part 23: Symbolic Music Representation Information technology – Coding of audiovisual objects – Part 25: 3D Graphics Compression Model Information technology – Coding of audiovisual objects – Part 26: Audio conformance BSAC conformance for broadcasting - ISO/IEC TR 14496-24:2008 ISO/IEC 14496-25:2011 ISO/IEC 14496-26:2010 ISO/IEC 14496-26:2010/Amd 2:2010 ISO/IEC 14496-26:2010/Cor 2:2011 ISO/IEC 14496-26:2010/Cor 3:2011 ISO/IEC 14496-26:2010/Cor 4:2011 ISO/IEC 14496-26:2010/Cor 5:2012 ISO/IEC 14496-27:2009 ISO/IEC 14496-27:2009/Amd 2:2011 ISO/IEC 14496-27:2009/Amd 3:2011 ISO/IEC 14496-27:2009/Amd 4:2012 Information technology – Coding of audiovisual objects – Part 27: 3D Graphics conformance Scalable complexity 3D mesh coding conformance Scalable complexity 3D mesh coding conformance in 3DGCM Conformance for efficient representation of 3D meshes with multiple attributes ISO/IEC 14496-28:2012 Information technology – Coding of audio- V1.0 2013-01-15 Page 188 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot visual objects – Part 28: Composite font representation Description MPEG-4 absorbs many of the features of MPEG-1 and MPEG-2 and other related standards, adding new features such as (extended) VRML support for 3D rendering, object-oriented composite files (including audio, video and VRML objects), support for externally specified Digital Rights Management and various types of interactivity. AAC (Advanced Audio Coding) was standardized as an adjunct to MPEG-2 (as Part 7) before MPEG-4 was issued. The ISO/IEC 14496 (MPEG-4) series has been developed by MPEG (Motion Picture Experts Group) and defines the set of technologies for compression, encoding and delivery of complex audio-visual scenes composed of different media objects: • video objects (natural or synthetic video); • audio objects; • still images; • text and vector graphics; • computer-animated images. MPEG-4 provides a standardized way to: • represent the content of audio-visual objects; • describe the composition of these objects in compound media scenes; • encode, multiplex and synchronize the data associated with the media objects; • transport the media presentation over different channels; • interact with the audio-visual scene at the receiver's end. The key parts to be aware of are MPEG-4 part 2 (including Advanced Simple Profile, used by codecs such as DivX, Xvid, Nero Digital and 3ivx and by QuickTime 6) and MPEG-4 part 10 (MPEG-4 AVC/H.264 or Advanced Video Coding, used by the x264 encoder, by Nero Digital AVC, by QuickTime 7, and by high-definition video media like Blu-ray Disc). External links http://en.wikipedia.org/wiki/MPEG-4 MPEG-7 Profile Reference Name Categories V1.0 MPEG-7 MPEG-7 File Formats and Persistent Data Structures; General Purpose; Video 2013-01-15 Page 189 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot formats ICS 35.040: Character sets and information coding Abstract MPEG-7 is intended to provide complementary functionality to the previous MPEG standards, representing information about the content, not the content itself Current Version see Standard Parts below Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 15938-1:2002 ISO/IEC 15938-1:2002/Amd 1:2005 ISO/IEC 15938-1:2002/Amd 1:2005/Cor 1:2005 ISO/IEC 15938-1:2002/Amd 2:2006 ISO/IEC 15938-1:2002/Cor 1:2004 ISO/IEC 15938-1:2002/Cor 2:2005 ISO/IEC 15938-2:2002 ISO/IEC 15938-3:2002 ISO/IEC 15938-3:2002/Amd 1:2004 ISO/IEC 15938-3:2002/Amd 1:2004/Cor 1:2005 ISO/IEC 15938-3:2002/Amd 1:2004/Cor 2:2007 ISO/IEC 15938-3:2002/Amd 2:2006 ISO/IEC 15938-3:2002/Amd 2:2006/Cor 1:2007 ISO/IEC 15938-3:2002/Amd 3:2009 ISO/IEC 15938-3:2002/Amd 4:2010 ISO/IEC 15938-3:2002/Cor 1:2004 ISO/IEC 15938-4:2002 ISO/IEC 15938-4:2002/Amd 1:2004 ISO/IEC 15938-4:2002/Amd 2:2006 ISO/IEC 15938-5:2003 ISO/IEC 15938-5:2003/Amd 1:2004 ISO/IEC 15938-5:2003/Amd 2:2005 ISO/IEC 15938-5:2003/Amd 3:2008 ISO/IEC 15938-5:2003/Amd 4:2012 ISO/IEC 15938-5:2003/Cor 1:2004 V1.0 2013-01-15 Title Information technology – Multimedia content description interface – Part 1: Systems Systems extensions Fast access extension Information technology – Multimedia content description interface – Part 2: Description definition language Information technology – Multimedia content description interface – Part 3: Visual Visual extensions Perceptual 3D Shape Descriptor Image signature tools Video signature tools - Information technology – Multimedia content description interface – Part 4: Audio Audio extensions High-level descriptors Information technology – Multimedia content description interface – Part 5: Multimedia description schemes Multimedia description schemes extensions Multimedia description schemes user preference extensions Improvements to geographic descriptor Page 190 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 15938-6:2003 ISO/IEC 15938-6:2003/Amd 1:2006 ISO/IEC 15938-6:2003/Amd 1:2006/Cor 1:2007 ISO/IEC 15938-6:2003/Amd 2:2007 ISO/IEC 15938-6:2003/Amd 3:2010 ISO/IEC 15938-6:2003/Amd 4:2011 ISO/IEC 15938-7:2003 ISO/IEC 15938-7:2003/Amd 1:2005 ISO/IEC 15938-7:2003/Amd 2:2007 ISO/IEC 15938-7:2003/Amd 3:2007 ISO/IEC 15938-7:2003/Amd 4:2008 ISO/IEC 15938-7:2003/Amd 5:2010 ISO/IEC 15938-7:2003/Amd 6:2011 ISO/IEC TR 15938-8:2002 ISO/IEC TR 15938-8:2002/Amd 1:2004 ISO/IEC TR 15938-8:2002/Amd 2:2006 ISO/IEC TR 15938-8:2002/Amd 3:2007 ISO/IEC TR 15938-8:2002/Amd 4:2009 ISO/IEC TR 15938-8:2002/Amd 5:2010 ISO/IEC TR 15938-8:2002/Amd 6:2011 ISO/IEC TR 15938-8:2002/Cor 1:2005 ISO/IEC 15938-9:2005 ISO/IEC 15938-9:2005/Amd 1:2012 ISO/IEC 15938-10:2005 V1.0 2013-01-15 Social metadata Information technology – Multimedia content description interface – Part 6: Reference software Reference software extensions Reference software of perceptual 3D shape descriptor Reference software for image signature tools Reference software for video signature tools Information technology – Multimedia content description interface – Part 7: Conformance testing Conformance extensions Fast access extensions conformance Conformance testing of perceptual 3D shape descriptor Improvements to geographic descriptor conformance Conformance testing for image signature tools Conformance testing for video signature tools Information technology – Multimedia content description interface – Part 8: Extraction and use of MPEG-7 descriptions Extensions of extraction and use of MPEG-7 descriptions Extraction and use of MPEG-7 perceptual 3D shape descriptor Technologies for digital photo management using MPEG-7 visual tools Extraction of audio features from compressed formats Extraction and matching of image signature tools Extraction and matching of video signature tools Information technology – Multimedia content description interface – Part 9: Profiles and levels Extensions to profiles and levels Information technology - Multimedia content Page 191 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 15938-10:2005/Cor 1:2007 ISO/IEC TR 15938-11:2005 ISO/IEC TR 15938-11:2005/Amd 1:2012 ISO/IEC 15938-12:2012 description interface – Part 10: Schema definition Information technology – Multimedia content description Interface – Part 11: MPEG-7 profile schemas Audiovisual description profile (AVDP) schema Information technology – Multimedia content description interface – Part 12: Query format Description MPEG-7 is a multimedia content description standard. It was standardized in ISO/IEC 15938 (Multimedia content description interface).[1][2][3][4] This description will be associated with the content itself, to allow fast and efficient searching for material that is of interest to the user. MPEG-7 is formally called Multimedia Content Description Interface. Thus, it is not a standard which deals with the actual encoding of moving pictures and audio, like MPEG-1, MPEG-2 and MPEG-4. It uses XML to store metadata, and can be attached to timecode in order to tag particular events, or synchronise lyrics to a song, for example. [source: wikipedia] External links • http://en.wikipedia.org/wiki/MPEG-7 Quicktime Profile Reference Name Categories Quicktime Quicktime File Formats and Persistent Data Structures; General Purpose; Video formats ICS Abstract QuickTime is an extensible multimedia framework developed by Apple Inc., capable of handling various formats of digital video, picture, sound, panoramic images, and interactivity. Current Version Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from http://www.apple.com/uk/quicktime/ Description It is available free of charge for both Mac OS X and Windows operating systems. There V1.0 2013-01-15 Page 192 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot are some other free player applications that rely on the QuickTime framework, providing features not available in the basic QuickTime Player. It supports different files types and codecs natively. The QuickTime File Format (QTFF) is designed to accommodate the many kinds of data that need to be stored in order to work with digital multimedia. The QTFF is an ideal format for the exchange of digital media between devices, applications, and operating systems, because it can be used to describe almost any media structure. The file format is objectoriented, consisting of a flexible collection of objects that is easily parsed and easily expanded. Unknown objects can simply be ignored or skipped, allowing considerable forward compatibility as new object types are introduced. External links • http://en.wikipedia.org/wiki/QuickTime • https://developer.apple.com/library/mac/#documentation/QuickTime/QTFF/QTFFPreface /qtffPreface.html RealVideo Profile Reference Name Categories RealVideo RealVideo File Formats and Persistent Data Structures; General Purpose; Video formats ICS Abstract RealVideo is a suite of proprietary video compression formats developed by RealNetworks – the specific format changes with the version. RealVideo is supported on many platforms, including Windows, Mac, Linux, Solaris, and several mobile phones. Current Version Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from Description RealVideo can be played from a RealMedia file or streamed over the network using the Real Time Streaming Protocol (RTSP), a standard protocol for streaming media developed by the IETF. To facilitate real-time streaming, RealVideo (and RealAudio) normally uses constant bit rate encoding, so that the same amount of data is sent over the network each second. Recently, RealNetworks has introduced a variable bit rate form called RealMedia Variable Bitrate (RMVB). This allows for better video quality, however this format is less suited for streaming because it is difficult to predict how much network capacity a certain video stream will need. Video with fast motion or rapidly changing scenes will require a higher bit rate. If the bit rate of a video stream increases significantly, it may exceed the speed at V1.0 2013-01-15 Page 193 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot which data can be transmitted over the network, leading to an interruption in the video. External links • http://en.wikipedia.org/wiki/RealVideo WMV Profile Reference Name Categories WMV WMV: Windows Media Video File Formats and Persistent Data Structures; General Purpose; Video formats ICS Abstract Windows Media Video (WMV) is a video compression format for several proprietary codecs developed by Microsoft. Current Version see Standard Parts below Other editions AAL Relevance Popular video format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ST 421:2006 ST 421-A1:2006 ST 421-A2:2011 Title VC-1 Compressed Video Bitstream Format and Decoding Process VC-1 Compressed Video Bitstream Format and Decoding Process — Amendment 1 VC-1 Compressed Video Bitstream Format and Decoding Process — Amendment 2 Description A WMV file is in most circumstances encapsulated in the Advanced Systems Format (ASF) container format. The file extension .WMV typically describes ASF files that use Windows Media Video codecs. The audio codec used in conjunction with Windows Media Video is typically some version of Windows Media Audio, or in rarer cases, the deprecated Sipro ACELP.net audio codec. Microsoft recommends that ASF files containing nonWindows Media codecs use the generic .ASF file extension. ST 421:2006 (better known as VC-1) defines the bitstream syntax and semantics for compressed video data in VC-1 format, and specifies constraints that are required for conformant bitstreams. It also describes the complete process required to decode the bitstream. The compression algorithm is not specified in this standard. External links • http://en.wikipedia.org/wiki/Windows_Media_Video • https://www.smpte.org/ V1.0 2013-01-15 Page 194 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 3.1.3 Audio formats AAC Profile Reference Name Categories ISO/IEC 14496-3:2009 [AAC] Information technology – Coding of audio-visual objects – Part 3: Audio File Formats and Persistent Data Structures; General Purpose; Audio formats ICS 35.040: Character sets and information coding Abstract Advanced Audio Coding (AAC) is a standardized, lossy compression and encoding scheme for digital audio. Designed to be the successor of the MP3 format, AAC generally achieves better sound quality than MP3 at similar bit rates. Current Version see Standard Parts below Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 14496 – 3 ISO/IEC 14496-3:2009/Amd 1:2009 ISO/IEC 14496-3:2009/Amd 2:2010 ISO/IEC 14496-3:2009/Amd 3:2012 ISO/IEC 14496-3:2009/Cor 1:2009 ISO/IEC 14496-3:2009/Cor 2:2011 ISO/IEC 14496-3:2009/Cor 3:2012 ISO/IEC 14496-3:2009/Cor 4:2012 Title Information technology – Coding of audiovisual objects – Part 3: Audio HD-AAC profile and MPEG Surround signalling ALS simple profile and transport of SAOC Transport of unified speech and audio coding (USAC) - Description AAC supports inclusion of 48 full-bandwidth (up to 96 kHz) audio channels in one stream plus 16 low frequency effects (LFE, limited to 120 Hz) channels, up to 16 “coupling” or dialogue channels, and up to 16 data streams. The quality for stereo is satisfactory to modest requirements at 96 kbit/s in joint stereo mode; however, Hi-Fi transparency demands data rates of at least 128 kbit/s (VBR). The MPEG-2 audio tests showed that AAC meets the requirements referred to as “transparent” for the ITU at 128 kbit/s for stereo, and 320 kbit/s for 5.1 audio. AAC is also the default or standard audio format for YouTube, iPhone, iPod, iPad, Nintendo DSi, iTunes, DivX Plus Web Player and PlayStation 3. It is supported on PlayStation Vita, Wii (with the Photo Channel 1.1 update installed), Sony Walkman MP3 series and later, Sony Ericsson; Nokia, Android, BlackBerry, and webOS-based mobile V1.0 2013-01-15 Page 195 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot phones, with the use of a converter. AAC has also seen some adoption on in-dash car audio especially on high-end units such as the Pioneer AVIC series. External links • http://en.wikipedia.org/wiki/Advanced_Audio_Coding GSM Profile Reference Name Categories Global System for Mobile Communications [GSM] GSM: Global System for Mobile Communications File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract GSM is a standard set developed by the European Telecommunications Standards Institute (ETSI) to describe protocols for second generation (2G) digital cellular networks used by mobile phones. Current Version see Standard Parts below Other editions AAL Relevance Many AAL applications and services using mobile terminals are based on the GSM standards set. Available from see Standard Parts below Standard Parts Standard http://www.3gpp.org/ftp/Specs/htmlinfo/45001.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45002.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45003.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45004.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45005.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45008.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45009.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45010.htm http://www.3gpp.org/ftp/Specs/htmlV1.0 2013-01-15 Title TS 45.001: Physical layer on the radio path; General description TS 45.002: Multiplexing and multiple access on the radio path TS 45.003: Channel coding TS 45.004: Modulation TS 45.005: Radio transmission and reception TS 45.008: Radio subsystem link control TS 45.009: Link adaptation TS 45.010: Radio subsystem synchronization TS 45.015: Release independent Downlink Page 196 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot info/45015.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45022.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45050.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45056.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45811.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45860.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45902.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45903.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45912.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45913.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45914.htm http://www.3gpp.org/ftp/Specs/htmlinfo/45926.htm • TS: Technical Specification Advanced Receiver Performance (DARP); Implementation guidelines TS 45.022: Radio link management in hierarchical networks TR 45.050: Background for Radio Frequency (RF) requirements TS 45.056: GSM Cordless Telephony System (CTS), Phase 1; CTS-FP Radio subsystem TR 45.811: Uplink - Time Difference Of Arrival (U-TDOA) in GSM and GPRS TR 45.860: Signal Precoding Enhancements for EGPRS2 DL TS 45.902: Flexible Layer One (FLO) TR 45.903: Feasibility study on Single Antenna Interference Cancellation (SAIC) for GSM networks TR 45.912: Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN) TR 45.913: Optimized transmit pulse shape for downlink Enhanced General Packet Radio Service (EGPRS2-B) TR 45.914: Circuit switched voice capacity evolution for GSM/EDGE Radio Access Network (GERAN) TR 45.926: Potential solutions for energysaving for GSM/EDGE radio access BTS • TR: Technical Report Description GSM is a cellular network, which means that cell phones connect to it by searching for cells in the immediate vicinity. The GSM standard was developed as a replacement for first generation (1G) analogue cellular networks, and originally described a digital, circuit switched network optimized for full duplex voice telephony. This was expanded over time to include data communications, first by circuit switched transport, then packet data transport via GPRS (General Packet Radio Services) and EDGE (Enhanced Data rates for GSM Evolution or EGPRS). Further improvements were made when the 3GPP developed third generation (3G) UMTS standards followed by fourth generation (4G) LTE Advanced standards. GSM is a cellular network, which means that cell phones connect to it by searching for cells in the immediate V1.0 2013-01-15 Page 197 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot vicinity. There are five different cell sizes in a GSM network—macro, micro, pico, femto and umbrella cells. The coverage area of each cell varies according to the implementation environment. GSM has used a variety of voice codecs to squeeze 3.1 kHz audio into between 6.5 and 13 kbit/s. Originally, two codecs, named after the types of data channel they were allocated, were used, called Half Rate (6.5 kbit/s) and Full Rate (13 kbit/s). These used a system based upon linear predictive coding (LPC). GSM was further enhanced in 1997 with the Enhanced Full Rate codec, a 12.2 kbit/s codec that uses a full rate channel. Finally, with the development of UMTS, EFR was refactored into a variable-rate codec called AMR-Narrowband, which is high quality and robust against interference when used on full rate channels, or less robust but still relatively high quality when used in good radio conditions on half-rate channels. GSM networks operate in a number of different carrier frequency ranges (separated into GSM frequency ranges for 2G and UMTS frequency bands for 3G), with most 2G GSM networks operating in the 900 MHz or 1800 MHz bands. Where these bands were already allocated, the 850 MHz and 1900 MHz bands were used instead (for example in Canada and the United States). In rare cases the 400 and 450 MHz frequency bands are assigned in some countries because they were previously used for first-generation systems. External links • http://en.wikipedia.org/wiki/GSM • http://www.etsi.org/index.php/technologies-clusters/technologies/mobile/gsm • http://www.3gpp.org/ftp/Specs/html-info/45-series.htm ISDN Profile Reference Name Categories ISDN ISDN: Integrated Services Digital Network File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract ISDN is a set of communication standards for simultaneous digital transmission of voice, video, data, and other network services over the traditional circuits of the public switched telephone network. Current Version Other editions AAL Relevance Popular telephone connection, may be used for audio signal (and data) transmitting Available from http://www.itu.int/rec/T-REC-I/e V1.0 2013-01-15 Page 198 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts All parts available and described here: http://www.itu.int/rec/T-REC-I/e Description The key feature of ISDN is that it integrates speech and data on the same lines, adding features that were not available in the classic telephone system. There are several kinds of access interfaces to ISDN defined as Basic Rate Interface (BRI), Primary Rate Interface (PRI) and Broadband ISDN (B-ISDN). ISDN is a circuit-switched telephone network system, which also provides access to packet switched networks, designed to allow digital transmission of voice and data over ordinary telephone copper wires, resulting in potentially better voice quality than an analogue phone can provide. External links • http://en.wikipedia.org/wiki/Integrated_Services_Digital_Network MIDI Profile Reference Name Categories MIDI MIDI: Musical Instrument Digital Interface File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract MIDI is an electronic musical instrument industry specification that enables a wide variety of digital musical instruments, computers and other related devices to connect and communicate with one another. Current Version Complete MIDI 1.0 Detailed Specification Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from http://www.midi.org/techspecs/index.php Description It is a set of standard commands that allows electronic musical instruments, performance controllers, computers and related devices to communicate, as well as a hardware standard that guarantees compatibility between them. MIDI equipment captures note events and adjustments to controls such as knobs and buttons, encodes them as digital messages, and sends these messages to other devices where they control sound generation and other features. This data can be recorded into a hardware or software device called a sequencer, which can be used to edit the data and to play it back at a later time. Complete MIDI 1.0 Detailed Specification containing the basic MIDI Protocol (1983-1996), including Time Code (MTC), Show Control (MSC), Machine Control (MMC), and more. V1.0 2013-01-15 Page 199 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://en.wikipedia.org/wiki/MIDI MP3 Profile Reference Name Categories MP3 MP3: MPEG-1 Audio Layer 3 File Formats and Persistent Data Structures; General Purpose; Audio formats ICS 35.040: Character sets and information coding Abstract MP3 is a patented encoding format for digital audio which uses a form of lossy data compression. It is a common audio format for consumer audio storage, as well as a de facto standard of digital audio compression for the transfer and playback of music on most digital audio players. Current Version see Standard Parts below Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 13818-3:1998 ISO/IEC 11172-3:1993 Title Information technology – Generic coding of moving pictures and associated audio information – Part 3: Audio Information technology – Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s – Part 3: Audio Description The use in MP3 of a lossy compression algorithm is designed to greatly reduce the amount of data required to represent the audio recording and still sound like a faithful reproduction of the original uncompressed audio for most listeners. An MP3 file that is created using the setting of 128 kbit/s will result in a file that is about 1/11 the size of the CD file created from the original audio source. An MP3 file can also be constructed at higher or lower bit rates, with higher or lower resulting quality. The compression works by reducing accuracy of certain parts of sound that are considered to be beyond the auditory resolution ability of most people External links • http://en.wikipedia.org/wiki/MP3 V1.0 2013-01-15 Page 200 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot RealAudio Profile Reference Name Categories RealAudio RealAudio File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract RealAudio is a proprietary audio format developed by RealNetworks. It uses a variety of audio codecs, ranging from low-bitrate formats that can be used over dial-up modems, to high-fidelity formats for music. It can also be used as a streaming audio format, that is played at the same time as it is downloaded. Current Version Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from http://de.real.com/realplayer/ Description RealAudio files were originally identified by a filename extension of .ra (for Real Audio). The official player for RealMedia content is RealNetworks' RealPlayer SP, currently at version 14, and is available for various platforms in binary form. RealAudio was developed as a streaming media format, meaning that it can be played while it is downloaded. It is possible to stream RealAudio using HTTP. In this case, the RealAudio file is retrieved similarly to a normal web page, but playback begins as soon as the first part is received and continues while the rest of the file is downloaded. Using HTTP streaming works best with pre-recorded files so some alternative protocols have been developed which work better for live broadcasts. RealAudio files are compressed using several different audio codecs. Each codec is identified by a four character code. External links • http://en.wikipedia.org/wiki/RealAudio RIFF WAVE Profile Reference Name Categories ICS Abstract V1.0 RIFF WAVE RIFF WAVE: Resource Interchange File Format WAVE File Formats and Persistent Data Structures; General Purpose; Audio formats WAVE, (or more commonly known as WAV due to its file name extension) is a Microsoft and IBM audio file format standard for storing 2013-01-15 Page 201 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot an audio bitstream on PCs. Current Version Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from Description It is an application of the Resource Interchange File Format (RIFF) bitstream format method for storing data in “chunks”. It is the main format used on Windows systems for raw and typically uncompressed audio. The usual bitstream encoding is the linear pulsecode modulation (LPCM) format. Though a WAV file can hold compressed audio, the most common WAV format contains uncompressed audio in the linear pulse code modulation (LPCM) format. The WAV format supports compressed audio, using, on Windows, the Audio Compression Manager. Any ACM codec can be used to compress a WAV file. External links • http://en.wikipedia.org/wiki/WAV • http://en.wikipedia.org/wiki/Resource_Interchange_File_Format Vorbis Profile Reference Name Categories Vorbis Vorbis (Ogg Vorbis) File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract Vorbis is a free software / open source project headed by the Xiph.Org Foundation (formerly Xiphophorus company). The project produces an audio format specification and software implementation (codec) for lossy audio compression. Vorbis is most commonly used in conjunction with the Ogg container format and it is therefore often referred to as Ogg Vorbis. Current Version Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from http://www.vorbis.com Description Ogg Vorbis is roughly comparable to other formats used to store and play digital music, such as MP3, VQF, AAC, and other digital audio formats. It is different from these other formats because it is completely free, open, and unpatented. Vorbis had been shown to perform significantly better than many other lossy audio formats in the past in that it V1.0 2013-01-15 Page 202 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot produced smaller files at equivalent or higher quality while retaining computational complexity comparable to other MDCT formats such as AAC or Windows Media Audio. Vorbis files can compress to a smaller file size and still sound fine. However, there have not been many significant tests run in recent years. External links • http://en.wikipedia.org/wiki/Vorbis WMA Profile Reference Name Categories WMA WMA: Windows Media Audio File Formats and Persistent Data Structures; General Purpose; Audio formats ICS Abstract Windows Media Audio (WMA) is an audio data compression technology developed by Microsoft. The name can be used to refer to its audio file format or its audio codecs. It is a proprietary technology that forms part of the Windows Media framework. Current Version Windows Media Audio 10 Other editions AAL Relevance Popular audio format, may be used in AAL scenarios. Available from http://msdn.microsoft.com/enus/library/ff819508(v=VS.85).aspx#WindowsMediaAudio9Voice Description WMA consists of four distinct codecs. The original WMA codec, known simply as WMA, was conceived as a competitor to the popular MP3 and RealAudio codecs. WMA Pro, a newer and more advanced codec, supports multichannel and high resolution audio. A lossless codec, WMA Lossless, compresses audio data without loss of audio fidelity (the regular WMA format is lossy). WMA Voice, targeted at voice content, applies compression using a range of low bit rates. External links • http://en.wikipedia.org/wiki/Windows_Media_Audio V1.0 2013-01-15 Page 203 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 3.1.4 Document formats E-Mail Profile Reference Name Categories E-Mail E-Mail File Formats and Persistent Data Structures; General Purpose; Documents formats; IETF ICS Abstract E-mail is a method of exchanging digital messages from an author to one or more recipients. Modern email operates across the Internet or other computer networks. Current Version see Standard Parts below Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard Request for Comments: 5322 Request for Comments: 5321 Request for Comments: 2045 Request for Comments: 2046 Request for Comments: 2047 Request for Comments: 2048 Request for Comments: 2049 Title Internet Message Format Simple Mail Transfer Protocol Multipurpose Internet Mail Extensions(MIME) Part One: Format of Internet Message Bodies Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header for Non-ASCII Text Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Description Some early email systems required that the author and the recipient both be online at the same time, in common with instant messaging. Today's email systems are based on a store-and-forward model. Email servers accept, forward, deliver and store messages. Neither the users nor their computers are required to be online simultaneously; they need connect only briefly, typically to an email server, for as long as it takes to send or receive messages. External links • http://en.wikipedia.org/wiki/Email V1.0 2013-01-15 Page 204 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot HTML Profile Reference Name Categories HTML HTML: Hypertext Markup Language File Formats and Persistent Data Structures; General Purpose; Documents formats; ISO; IEC ICS 35.240.30: IT applications in information, documentation and publishing Abstract HyperText Markup Language (HTML) is the main markup language for displaying web pages and other information that can be displayed in a web browser. Current Version HTML5 Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO 8879:1986 ISO/IEC 15445:2000 Title Information processing – Text and office systems – Standard Generalized Markup Language (SGML) Information technology – Document description and processing languages – HyperText Markup Language (HTML) Description HTML gives authors the means to: • Publish online documents with headings, text, tables, lists, photos, etc. • Retrieve online information via hypertext links, at the click of a button. • Design forms for conducting transactions with remote services, for use in searching for information, making reservations, ordering products, etc. • Include spread-sheets, video clips, sound clips, and other applications directly in their documents. External links • http://www.w3.org/standards/webdesign/htmlcss • http://en.wikipedia.org/wiki/HTML iCalendar Profile Reference V1.0 iCalendar 2013-01-15 Page 205 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name Categories iCalendar File Formats and Persistent Data Structures; General Purpose; Documents formats; IETF ICS Abstract iCalendar is a computer file format which allows Internet users to send meeting requests and tasks to other Internet users, via email, or sharing files with an extension of .ics. Current Version see Standard Parts below Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard Request for Comments: 3283 Request for Comments: 6638 Request for Comments: 6047 Title Guide to Internet Calendaring Scheduling Extensions to CalDAV iCalendar Message-Based Interoperability Protocol (iMIP) Description Recipients of the iCalendar data file (with supporting software, such as an email client or calendar application) can respond to the sender easily or counter-propose another meeting date/time. The top-level element in iCalendar is the Calendaring and Scheduling Core Object, a collection of calendar and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be grouped together. External links • http://en.wikipedia.org/wiki/ICalendar Microsoft Excel Profile Reference Name Categories Microsoft Excel Microsoft Excel File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract Microsoft Excel is a non-free commercial spreadsheet application written and distributed by Microsoft for Microsoft Windows and Mac OS X. Current Version 2010 for Microsoft Windows ((version 14) included in Office 2010) and 2011 for Mac OS X V1.0 2013-01-15 Page 206 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://office.microsoft.com/en-us/excel http://www.microsoft.com/mac/excel Description Microsoft Excel features calculation, graphing tools, pivot tables, and a macro programming language called Visual Basic for Applications. Microsoft Excel has the basic features of all spreadsheets, using a grid of cells arranged in numbered rows and letternamed columns to organize data manipulations like arithmetic operations. It has a battery of supplied functions to answer statistical, engineering and financial needs. In addition, it can display data as line graphs, histograms and charts, and with a very limited threedimensional graphical display. It allows sectioning of data to view its dependencies on various factors for different perspectives (using pivot tables and the scenario manager). It has a programming aspect, Visual Basic for Applications, allowing the user to employ a wide variety of numerical methods. Filename extension: .xls, (.xlsx, .xlsm, .xlsb - Excel 2007) External links • http://en.wikipedia.org/wiki/Microsoft_Excel Microsoft Word Profile Reference Name Categories Microsoft Word Microsoft Word File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract Microsoft Word is a proprietary word processor designed by Microsoft. Current Version Microsoft Office Word 2010 for Windows and Microsoft Office Word 2011 for Mac Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://office.microsoft.com/en-us/word/ Description Microsoft Word is a word processing program that allows users to create professional documents such as resumes, letters, fax cover sheets, reports, legal documents, brochures, manuals and more. It is an efficient tool for students, business owners and even working individuals to have on their computers. Microsoft Word has tools to format fonts, add clipart, add page numbers, and create tables and headers. There is even an “office assistant” cartoon that can sit in the background to guide you through the creation of your document or answer any questions that you might have. Microsoft Word's native V1.0 2013-01-15 Page 207 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot file formats are denoted either by a .doc or .docx file extension. Microsoft does not guarantee the correct display of the document on different workstations, even if the two workstations use the same version of Microsoft Word, primarily due to page layout depending on the current printer. This means it is possible the document the recipient sees might not be exactly the same as the document the sender sees. External links • http://en.wikipedia.org/wiki/Microsoft_Word • http://office.microsoft.com/en-us/word/ OpenDocument Profile Reference Name Categories OpenDocument OpenDocument File Formats and Persistent Data Structures; General Purpose; Documents formats; ISO; IEC ICS Abstract OD is an XML-based file format for spreadsheets, charts, presentations and word processing documents. Current Version see Standard Parts below Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from see Standard Parts below Standard Parts Standard ISO/IEC 26300:2006 ISO/IEC 26300:2006/Amd 1:2012 ISO/IEC 26300:2006/Cor 1:2010 ISO/IEC 26300:2006/Cor 2:2011 OASIS Committee Specification OpenDocument 1.0 OpenDocument 1.1 OpenDocument 1.2 ISO/IEC ISP 15124-1:1998 V1.0 Title Information technology – Open Document Format for Office Applications (OpenDocument) v1.0 Open Document Format for Office Applications (OpenDocument) v1.1. Open Document Format for Office Applications (OpenDocument) v1.1 OASIS Standard, 1 Feb 2007 Open Document Format for Office Applications (OpenDocument) Version 1.2 Information technology – International Standardized Profile FOD126 – Open Document Format: Image Applications – Enhanced document structure – Character, raster graphics, 2013-01-15 Page 208 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC TR 29166:2011 ISO/IEC 29500-1:2012 ISO/IEC 29500-2:2012 ISO/IEC 29500-3:2012 ISO/IEC 29500-4:2012 ISO/IEC 29500-4:2008/Cor 1:2010 and geometric graphics content architecture – Part 1: Document Application Profile (DAP) Information technology – Document description and processing languages – Guidelines for translation between ISO/IEC 26300 and ISO/IEC 29500 document formats Information technology – Document description and processing languages – Office Open XML File Formats – Part 1: Fundamentals and Markup Language Reference Information technology – Document description and processing languages – Office Open XML File Formats – Part 2: Open Packaging Conventions Information technology – Document description and processing languages – Office Open XML File Formats – Part 3: Markup Compatibility and Extensibility Information technology – Document description and processing languages – Office Open XML File Formats – Part 4: Transitional Migration Features - Description The most common filename extensions used for OpenDocument documents are: • .odt and .fodt for word processing (text) documents • .ods and .fods for spreadsheets • .odp and .fodp for presentations • .odb for databases • .odg and .fodg for graphics • .odf for formulae, mathematical equations External links • http://en.wikipedia.org/wiki/OpenDocument PDF Profile Reference Name Categories V1.0 PDF PDF: Portable Document Format File Formats and Persistent Data Structures; General Purpose; Documents formats; ISO 2013-01-15 Page 209 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS 37.100.99: Other standards related to graphic technology; 35.240.30: IT applications in information, documentation and publishing Abstract The pdf file enable users to exchange and view electronic documents easily independently of the environment in which they were created. Current Version Extension Level 8 (2011) Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://www.adobe.com/products/acrobat/adobepdf.html Standard Parts Standard ISO 32000-1:2008 ISO 19005-1:2005 ISO 19005-1:2005/Cor 1:2007 ISO 19005-1:2005/Cor 2:2011 ISO 19005-2:2011 ISO 19005-3:2012 Title Document management – Portable document format – Part 1: PDF 1.7 Document management – Electronic document file format for long-term preservation – Part 1: Use of PDF 1.4 (PDF/A-1) Document management – Electronic document file format for long-term preservation – Part 2: Use of ISO 32000-1 (PDF/A-2) Document management – Electronic document file format for long-term preservation – Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A3) Description PDF relies on the same imaging model as the PostScript® page description language to describe text and graphics in a device-independent and resolution-independent manner. To improve performance for interactive viewing, PDF defines a more structured format than that used by most PostScript language programs. PDF also includes objects, such as annotations and hypertext links, that are not part of the page itself but are useful for interactive viewing and document interchange. External links • http://www.adobe.com/pdf/ • http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_17.pdf • http://en.wikipedia.org/wiki/Portable_Document_Format V1.0 2013-01-15 Page 210 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot PostScript Profile Reference Name Categories PostScript PostScript File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract Postscript is a programming language that describes the appearance of a printed page. It was developed by Adobe in 1985 and has become an industry standard for printing and imaging. Current Version PostScript 3 Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://www.adobe.com/products/postscript/ Description The primary application of PostScript Language is to describe the appearance of text, graphical shapes, and sampled images on printed or displayed pages, according to the Adobe imaging model. A program in this language can communicate a description of a document from a composition system to a printing system or control the appearance of text and graphics on a display. The description is high-level and device-independent. External links • http://partners.adobe.com/public/developer/en/ps/PLRM.pdf • http://www.adobe.com/products/postscript/pdfs/ps3datasheet.pdf • http://en.wikipedia.org/wiki/PostScript#PostScript_3 RSS Profile Reference Name Categories RSS RSS: Really Simple Syndication File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format. An RSS document (which is called a “feed”, “web feed” or “channel”) includes full or summarized text, plus metadata such as publishing dates and authorship. Current Version RSS 2.0 V1.0 2013-01-15 Page 211 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://www.rssboard.org/rss-specification Description RSS feeds benefit publishers by letting them syndicate content automatically. A standardized XML file format allows the information to be published once and viewed by many different programs. They benefit readers who want to subscribe to timely updates from favourite websites or to aggregate feeds from many sites into one place. As RSS files are essentially XML formatted plain text, the RSS file itself is relatively easily read both by automated processes and by humans alike. External links • http://en.wikipedia.org/wiki/RSS • http://www.rssboard.org/rss-specification RTF Profile Reference Name Categories RTF RTF: Rich Text Format File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract Rich Text Format is a proprietary file format that many word processing programs understand; it is often used when a document is created in one word processing program but is expected to be edited in another word processing program. Unlike a basic text file, an RTF file can include information such as text style, size, and colour Current Version RTF 1.9.1 Other editions AAL Relevance Popular document format, may be used in AAL scenarios. Available from http://www.microsoft.com/en-us/download/details.aspx?id=10725 Standard Parts Standard Rich Text Format (RTF) Specification, version 1.9.1 Title - Description The Rich Text Format (often abbreviated RTF) is a proprietary document file format with published specification developed by Microsoft Corporation since 1987 for Microsoft products and for cross-platform document interchange. V1.0 2013-01-15 Page 212 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Most word processors are able to read and write some versions of RTF. There are several different revisions of RTF specification and portability of files will depend on what version of RTF is being used. RTF specifications are changed and published with major Microsoft Word and Office versions. It should not be confused with enriched text (mimetype “text/enriched” of RFC 1896) or its predecessor Rich Text (mimetype “text/richtext” of RFC 1341 and 1521); nor with IBM's RFT-DCA (Revisable Format Text-Document Content Architecture) which are completely different specifications. [source: wikipedia] External links • http://www.microsoft.com/en-us/download/details.aspx?id=10725 • http://en.wikipedia.org/wiki/Rich_Text_Format 3.1.5 Other structured formats SMIL Profile Reference Name Categories SMIL SMIL: Synchronized Multimedia Integration Language File Formats and Persistent Data Structures; General Purpose; Documents formats ICS Abstract The Synchronized Multimedia Integration Language enables simple authoring of interactive audiovisual presentations. Current Version see Standard Parts below Other editions AAL Relevance As many AAL-Applications using different modalities for user interaction, this standard may be relevant. Available from see Standard Parts below Standard Parts Standard W3C Recommendation : Synchronized Multimedia Integration Language (SMIL 3.0) Synchronized Multimedia Integration Language (SMIL) 1.0 Specification Title Description SMIL is typically used for “rich media”/multimedia presentations which integrate streaming audio and video with images, text or any other media type. SMIL is an easy-to-learn V1.0 2013-01-15 Page 213 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot HTML-like language, and many SMIL presentations are written using a simple text-editor. A SMIL document is similar in structure to an HTML document in that they are typically divided between an optional <head> section and a required <body> section. External links • http://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language#SMIL_3.0 3.2. Medical CCD Profile Reference Name Categories CCD CCD: Continuity of Care Document Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract The Continuity of Care Document (CCD) specification is an XML-based markup standard intended to specify the encoding, structure and semantics of a patient summary clinical document for exchange. Current Version Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://hl7book.net/index.php?title=CDA Description The Continuity of Care Document (CCD) summarizes the most important health data of a patient. The Document was developed on the basis of the contents of the CCR but uses the structure of a CDA-Document. It is represented in XML. The CCD specification is a constraint on the HL7 Clinical Document Architecture (CDA) standard. The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part is based on the HL7 Reference Information Model (RIM) and provides a framework for referring to concepts from coding systems, such as the SNOMED or the LOINC. The patient summary contains a core data set of the most relevant administrative, demographic, and clinical information facts about a patient's healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another practitioner, system, or setting to support the continuity of care. Its primary use case is to provide a snapshot in time containing the pertinent clinical, demographic, and administrative data for a specific patient. V1.0 2013-01-15 Page 214 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot The CCD specification contains U.S. specific requirements; its use is therefore limited to the U.S. The U.S. Healthcare Information Technology Standards Panel has selected the CCD as one of its standards. CCDs are quickly becoming one of the most ubiquitous and thorough means of transferring health data on patients as each can contain vast amounts of data based on the standard format, in a relatively easy to use and portable file. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Continuity_of_Care_Document CCR Profile Reference Name Categories CCR CCR: Continuity of Care Record Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract Continuity of Care Record (CCR) is a health record standard specification developed jointly by ASTM International, the Massachusetts Medical Society (MMS), the Healthcare Information and Management Systems Society (HIMSS), the American Academy of Family Physicians (AAFP), the American Academy of Pediatrics (AAP), and other health informatics vendors. Current Version Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://www.astm.org/Standards/E2369.htm Description The Continuity of Care Document (CCR) summarizes the most important health data of a patient. It was developed with the support of different medical committees under the lead of the American Society for Testing and Materials (ASTM). The CCR is represented in XML and uses terminology systems like SNOMED and ICD to enable a semantic interoperability. CCR-Header (administrative data), CCR-Body (the actual content) and the CCR-Footer. The CCR standard is a patient health summary standard. It is a way to create flexible documents that contain the most relevant and timely core health information about a patient, and to send these electronically from one caregiver to another. It contains various sections such as patient demographics, insurance information, diagnoses and problem list, medications, allergies and care plan. These represent a “snapshot” of a patient's health data that can be useful or possibly lifesaving, if available at the time of clinical encounter. The ASTM CCR standard is designed[opinion] to permit easy creation by a physician V1.0 2013-01-15 Page 215 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot using an electronic health record (EHR) system at the end of an encounter. Because it is expressed in the standard data interchange language known as XML, a CCR can potentially be created, read, and interpreted by any EHR or EMR software application. A CCR can also be exported to other formats, such as PDF or Office Open XML (Microsoft Word 2007 format). The Continuity of Care Document (CCD) is an HL7 CDA implementation of the Continuity of Care Record (CCR). A CCR document can generally be converted into CCD using Extensible Stylesheet Language Transformations (XSLT), but it is not always possible to perform the inverse transformation, since some CCD features are not supported in CCR. HITSP provides reference information that demonstrates how CCD and CCR (as HITSP C32) are embedded in CDA. Although the CCR and CCD standards could continue to coexist, with CCR providing for basic information requests and CCD servicing more detailed requests, the newer CCD standard might eventually completely supplant CCR. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Continuity_of_Care_Record CDA Profile Reference Name Categories CDA CDA: HL7 Clinical Document Architecture Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. Current Version Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://hl7book.net/index.php?title=CDA Description The Clinical Document Architecture (CDA) is a standard for the generic representation of health related documents. CDA is uses so called templates, specifying the concrete data items for a specific use case. CDA is part of the HL7 version 3 standard family and was accepted as ISO standard. CDA documents are represented in XML and consist of three levels. The first level is only human readable free text. The second level contains structured headings, which are machine interpretable. A CDA document on level three V1.0 2013-01-15 Page 216 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot have to be complete machine interpretable. The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. CDA is part of the HL7 version 3 standard. Akin to other parts of the HL7 version 3 standard it was developed using the HL7 Development Framework (HDF) and it is based on the HL7 Reference Information Model (RIM) and the HL7 Version 3 Data Types. CDA documents are persistent in nature. The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part relies on coding systems (such as from SNOMED and LOINC) to represent concepts. CDA Release 2 has been adopted as an ISO standard, ISO/HL7 27932:2009. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Clinical_Document_Architecture DICOM Profile Reference Name Categories DICOM DICOM: Digital Imaging and Communications in Medicine Communication Protocols; Medical Devices; File Formats and Persistent Data Structures; General Purpose; Medical; ISO ICS 35.240.80: IT applications in health care technology Abstract DICOM defines criteria for communication, visualization, archiving and printing of biomedical information Current Version http://medical.nema.org/ (there may be daily changes) Other editions ISO 12052:2006: Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management AAL Relevance DICOM is a public standard, so it achieves a great diffusion among medical devices. This involves a greater exchange of information Available from http://medical.nema.org/standard.html http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=43218 Description DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting information in medical imaging. It includes a file format definition and a network communications protocol. The communication protocol is an V1.0 2013-01-15 Page 217 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot application protocol that uses TCP/IP to communicate between systems. DICOM files can be exchanged between two entities that are capable of receiving image and patient data in DICOM format. The National Electrical Manufacturers Association (NEMA) holds the copyright to this standard.[1] It was developed by the DICOM Standards Committee, whose members[2] are also partly members of NEMA.[3] DICOM enables the integration of scanners, servers, workstations, printers, and network hardware from multiple manufacturers into a picture archiving and communication system (PACS). The different devices come with DICOM conformance statements which clearly state which DICOM classes they support. DICOM has been widely adopted by hospitals and is making inroads in smaller applications like dentists' and doctors' offices. DICOM is known as NEMA standard PS3, and as ISO standard 12052:2006 “Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management”. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/DICOM ePflegebericht Profile Reference Name Categories ePflegebericht ePflegebericht Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract CDA-based document in German care context. Current Version Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://www.hl7.de/publikationen/techdok.php Description The ePflegebericht (electronic care report) is a CDA –based document that is currently under development by the German Hochschule Osnabrück. The document consists of a header with administrative data and a body, which holds the actual content (like diagnoses, care targets and so on). The document is intended to share information between different institutions, which participate in the care process of a patient. V1.0 2013-01-15 Page 218 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/EN 13606 Profile Reference Name Categories ISO/EN 13606 ISO/EN 13606: Electronic Health Record Communication (EHRcom) Health informatics; Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical; ISO; EN ICS 35.240.80: IT applications in health care technology Abstract The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). Current Version see Standard Parts below Other editions AAL Relevance This standard is relevant to PHRs, EHRs and thereby to AAL. Available from see Standard Parts below Standard Parts Standard ISO 13606-1:2007 ISO 13606-2:2007 ISO 13606-3:2008 ISO/TS 13606-4:2007 ISO 13606-5:2010 Title Health informatics - Electronic health record communication Part 1: Reference model Health informatics - Electronic health record communication Part 2: Archetypes interchange specification Health informatics - Electronic health record communication Part 3: Reference archetypes and term lists Health informatics - Electronic health record communication Part 4: Security Health informatics - Electronic health record communication Part 5: Interface specification (ISO 13606-5:2010) Description The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). This is to support the interoperability of systems and components that need to communicate (access, transfer, add or modify) EHR data via electronic messages or as distributed objects: • preserving the original clinical meaning intended by the author; • reflecting the confidentiality of that data as intended by the author and patient. The name of this European Standard suggests that it is not intended to specify the internal architecture or database design of EHR systems or components, but the scope includes the use of an 'object'. This implies that the 'objects' can be stored, retrieved and exchanged. It is explicitly not intended to prescribe the kinds of clinical applications that V1.0 2013-01-15 Page 219 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot might request or contribute EHR data in particular settings, domains or specialities. For this reason, the information model proposed here is called the EHR Extract, and might be used to define a message, an XML document or schema, or an object interface. The information model in this European Standard is an ISO RM-ODP Information Viewpoint of the EHR Extract. This European Standard considers the EHR to be the persistent longitudinal and potentially multi-enterprise or multi-national record of health and care provision relating to a single subject of care (the patient), created and stored in one or more physical systems in order to inform the subject’s future health care and to provide a medico-legal record of care that has been provided. Whilst an EHR service or system will need to interact with many other services or systems providing terminology, medical knowledge, guidelines, workflow, security, persons registries, billing etc. this European Standard has only touched on those areas if some persistent trace of such interactions is required in the EHR itself, and requires specific features in the reference model to allow their communication. This European Standard may offer a practical and useful contribution to the design of EHR systems but will primarily be realised as a common set of external interfaces or messages built on otherwise heterogeneous clinical systems. The openEHR Framework is the basis of this new Electronic Health Record Communication Standard (EN 13606) [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/EN_13606 PHMR Profile Reference Name Categories PHMR PHMR: Personal Health Monitoring Report File Formats and Persistent Data Structures; General Purpose; Medical; Personal Health Records ICS Abstract The PHMR carries personal healthcare monitoring information. The information is transmitted as notes and as raw data. Current Version HL7 Implementation Guide for CDA Release 2 - Personal Healthcare Monitoring Report Other editions AAL Relevance This standard is used by the Continua Alliance to collect an share information that is acquired in the users home and is thereby relevant to AAL. Available from http://www.hl7.org/implement/standards/product_brief.cfm? product_id=33 Description The purpose of this document is to describe constraints on the CDA Header and Body V1.0 2013-01-15 Page 220 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot elements for Personal Healthcare Monitoring Report (PHMR) documents mostly containing analysed and raw information of data generated by personal healthcare monitoring devices such as glucometers, BP cuffs, thermometers, weight scales, etc. The PHMR carries personal healthcare monitoring information. The information may have multiple characteristics, including representation of: • Measurements captured by devices • Notes, summaries, and other kinds of narrative information • Graphs that may be added by intermediary devices that represent trends of users’ health [Source: HL7] VHitG Profile Reference Name Categories VHitG VHitG: VHitG Medical report Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract Current Version Other editions AAL Relevance As this standard is relevant to Electronic and Personal Health Records and communication in the healthcare system, it is relevant for the data storage and communication in the field of AAL. Available from http://www.bvitg.de/arztbrief.html Description The initiative was founded in May 2005 through the bvitg. The target of this standard is the exchange of a structured document in a medical context. The document contains information for the discharge or referral of a patient and is intended to be read by professionals in the medical domain. XPHR Profile Reference Name Categories ICS V1.0 XPHR XPHR: Exchange of Personal Health Record Content Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical - 2013-01-15 Page 221 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract This profile describes the content and format of summary information extracted from a PHR System for import into an EHR System, and visa versa. Current Version 8.0 Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant to data storage and communication in the field of AAL. Available from http://www.ihe.net/ Description Exchange of Personal Health Record Content (XPHR) was defined by the IHE to enable the exchange of important personal health data of a patient between electronic health record systems in the professional domain and personal health record systems in the home domain. XPHR is based on CDA and represented in XML. External links • http://wiki.ihe.net/index.php?title=Exchange_of_Personal_Health_Record_Content 3.2.1 ECG File Formats SCP-ECG Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from SCP-ECG SCP-ECG: Standard Communication Protocol for Electrocardiography File Formats and Persistent Data Structures; General Purpose; Medical 35.240.80 - IT applications in health care technology SCP-ECG, which stands for Standard communications protocol for computer assisted electrocardiography, is a standard for ECG traces, annotations, and metadata, that specifies the interchange format and a messaging procedure for ECG cart-to-host communication and for retrieval of SCP-ECG records from the host to the ECG cart. ISO 11073-91064:2009 EN 1064:2005+A1:2007 ANSI/AAMI standard EC71:2001 As AAL-Applications may store or transmit ECG data, this standard is relevant to AAL. see Standard Parts below Standard Parts Standard ISO 11073-91064:2009 V1.0 Title Health informatics – Standard communication protocol – Part 91064: Computer-assisted 2013-01-15 Page 222 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 1064:2005 ANSI/AAMI standard EC71:2001 electrocardiography Health informatics - Standard communication protocol - Computer-assisted electrocardiography Standard communications protocol for computer assisted electrocardiography Description SCP-ECG is a standard that specifies the interchange format and a messaging procedure for ECG cart-to-host communication and for retrieval of SCP-ECG records from the host (to the ECG cart). aECG Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from aECG aECG: HL7 Annotated ECG File Formats and Persistent Data Structures; General Purpose; Medical HL7 aECG (the HL7 Annotated Electrocardiogram) is a standard medical record data format for storing and retrieving electrocardiogram data for a patient. Like other HL7 formats, it is XML based. HL7 aECG Implementation Guide As AAL-Applications may store or transmit ECG data, this standard is relevant to AAL. http://www.hl7.org/documentcenter/public_temp_9393650A-1C23BA17-0CC532316EA63978/wg/rcrim/annecg/aECG%20Implementation %20Guide%202005-03-21%20final%203.pdf Description The Annotated ECG (aECG) HL7 standard was created in response to the FDA’s digital ECG initiative. The FDA initiative required ECG waveforms and annotations submitted to the FDA to have a standard format for the data, so it was created a standard to meet the FDA requirements, the HL7 aECG Implementation Guide. External links • http://www.openecg.net/tutorial1/How_To_Implement_SCP.pdf EDF Profile Reference V1.0 EDF 2013-01-15 Page 223 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name Categories ICS Abstract EDF: European Data Format File Formats and Persistent Data Structures; General Purpose; Medical European Data Format is a standard file format designed for exchange and storage of medical time series. Current Version Other editions AAL Relevance As many AAL-Applications store time series data, this standard may be relevant. Available from Description Internally it includes a header and one or more data records. The header contains some general information (patient identification, start time…) and technical specs of each signal (calibration, sampling rate, filtering, …), coded as ASCII characters. The data records contain samples as little-endian 16-bit integers. EDF is a popular format for polysomnography (PSG) recordings. External links • http://en.wikipedia.org/wiki/European_Data_Format • http://www.edfplus.info/ 3.3. Character Sets ASCII Profile Reference Name ASCII ASCII: American Standard Code for Information Interchange; ISO 646 “Information Processing – ISO 7-bit coded character set for information interchange” Categories File Formats and Persistent Data Structures; General Purpose; Character Sets ICS 35.040: Character sets and information coding Abstract Specifies a set of 128 control and graphic characters such as letters, digits and symbols with their coded representation. Applies to alphabets of the Latin script. Current Version Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from - V1.0 2013-01-15 Page 224 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard ISO/IEC 646:1991 Title Information technology – ISO 7-bit coded character set for information interchange Description The American Standard Code for Information Interchange is a character-encoding scheme originally based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that use text. Most modern characterencoding schemes are based on ASCII, though they support many additional characters. External links • http://en.wikipedia.org/wiki/Ascii Codepage Windows-1252 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from Codepage Windows-1252 Codepage Windows-1252 File Formats and Persistent Data Structures; General Purpose; Character Sets 35.040: Character sets and information coding Windows-1252 or CP-1252 is a character encoding of the Latin alphabet, used by default in the legacy components of Microsoft Windows in English and some other Western languages. It is one version within the group of Windows code pages. ISO/IEC 8859 is a joint ISO and IEC series of standards for 8-bit character encodings. ISO/IEC 8859-1 Popular character set, may be used in AAL applications. http://www.iso.org/iso/catalogue_detail.htm?csnumber=28245 Description This encoding is a superset of ISO 8859-1, but differs from the IANA's ISO-8859-1 by using displayable characters rather than control characters in the 80 to 9F (hex) range. It is known to Windows by the code page number 1252, and by the IANA-approved name “Windows-1252”. This code page also contains all the printable characters that are in ISO 8859-15 (though some are mapped to different code points). It is very common to mislabel Windows-1252 text with the charset label ISO-8859-1. A common result was that all the quotes and apostrophes (produced by “smart quotes” in Microsoft software) were replaced with question marks or boxes on non-Windows operating systems, making text difficult to read. Most modern web browsers and e-mail clients treat the MIME charset ISO-8859-1 as Windows-1252 in order to accommodate V1.0 2013-01-15 Page 225 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot such mislabelling This is now standard behaviour in the draft HTML 5 specification, which requires that documents advertised as ISO-8859-1 actually be parsed with the Windows1252 encoding. Historically, the phrase “ANSI Code Page” (ACP) is used in Windows to refer to various code pages considered as native. The intention was that most of these would be ANSI standards such as ISO-8859-1. Even though Windows-1252 was the first and by far most popular code page named so in Microsoft Windows parlance, the code page has never been an ANSI standard. Microsoft-affiliated bloggers now state that “The term ANSI as used to signify Windows code pages is a historical reference, but is nowadays a misnomer that continues to persist in the Windows community.” [source: Wikipedia] External links • http://en.wikipedia.org/wiki/Windows-1252 Codepage 437 Profile Reference Name Categories Codepage 437 Codepage 437 File Formats and Persistent Data Structures; General Purpose; Character Sets ICS Abstract Code page 437 also known as CP 437, OEM 437, PC-8, MS-DOS Latin US is the character set of the original IBM PC (personal computer), or MS-DOS. Current Version Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from Description In a strict sense, this character set was not conceived as a code page—it was simply the graphical glyph repertoire available in the 9 by 14 pixels-per-character font of the IBM Monochrome Display Adapter (MDA) and the 8 by 8 pixels-per-character font of the Colour Graphics Adapter (CGA) cards used with the original IBM PC. The ROM of the IBM Enhanced Graphics Adapter (EGA) contains an additional 8 by 14 pixels-per-character version and the VGA adapter expanded the character cell to 9 by 16 for compatibility with the finer VGA resolution. In the 21st century, this character set remains the primary font in the core of any EGA and VGA-compatible graphics card—that is, the text you can see on screen when a PC reboots, before any other font can be loaded from a storage medium, is rendered with this “Code Page”. “437” is the default hardware Code Page for PC hardware sold in the United States (US) and Western Europe; systems that are available for purchase in Eastern European, Arabic, and Asian countries may differ. V1.0 2013-01-15 Page 226 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot [source: Wikipedia] External links • http://en.wikipedia.org/wiki/Code_page_437 Codepage 850 Profile Reference Name Categories Codepage 850 Codepage 850 File Formats and Persistent Data Structures; General Purpose; Character Sets ICS Abstract Code page 850 (also known as CP 850, IBM 00850, OEM 850, MSDOS Latin 1) is a code page used under MS-DOS in Western Europe. It is the code page commonly used by the version of MS-DOS underlying Windows ME. It is also sometimes used on English DOS systems, although code page 437 is generally the default on those. Current Version Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from Description Code page 850 differs from code page 437 in that many of the box drawing characters, Greek letters, and various symbols were replaced with additional Latin letters with diacritics, thus greatly improving support for Western European languages (all characters from ISO 8859-1 are included). External links • http://en.wikipedia.org/wiki/Code_page_850 ISO 2022 Profile Reference Name Categories ICS Abstract V1.0 ISO 2022 ISO 2022: Information technology – Character code structure and extension techniques File Formats and Persistent Data Structures; General Purpose; Character Sets; ISO; IEC 35.040: Character sets and information coding Specifies the structure of 8-bit codes and 7-bit codes which provide for 2013-01-15 Page 227 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot the coding of character sets. The codes specified here are designed to be used for data that is processed sequentially in a forward direction. Use of these codes in strings of data which are processed in some other way, or which are included in data formatted for fixed-length record processing, may have undesirable results or may require additional special treatment to ensure correct interpretation. [source: Wikipedia] Current Version Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from Standard Parts Standard ISO/IEC 2022:1994 Title Information technology – Character code structure and extension techniques Description Many of the character sets included as ISO/IEC 2022 encodings are 'double byte' encodings where two bytes correspond to a single character. This makes ISO-2022 a variable width encoding. But a specific implementation does not have to implement all of the standard; the conformance level and the supported character sets are defined by the implementation. [source: Wikipedia] External links • http://en.wikipedia.org/wiki/ISO/IEC_2022 ISO 8859 Profile Reference Name Categories ISO 8859 ISO 8859: 8-bit single-byte coded graphic character sets File Formats and Persistent Data Structures; General Purpose; Character Sets; ISO; IEC ICS 35.040 Character sets and information coding Abstract ISO/IEC 8859 is a joint ISO and IEC series of standards for 8-bit character encodings. The series of standards consists of numbered parts, such as ISO/IEC 8859-1, ISO/IEC 8859-2, etc. There are 15 parts, excluding the abandoned ISO/IEC 8859-12. The ISO working group maintaining this series of standards has been disbanded. [source: Wikipedia] Current Version see Standard Parts below V1.0 2013-01-15 Page 228 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from see Standard Parts below Standard Parts Standard ISO/IEC 8859-1:1998 ISO/IEC 8859-2:1999 ISO/IEC 8859-3:1999 ISO/IEC 8859-4:1998 ISO/IEC 8859-5:1999 ISO/IEC 8859-6:1999 ISO/IEC 8859-7:2003 ISO/IEC 8859-8:1999 ISO/IEC 8859-9:1999 ISO/IEC 8859-10:1998 ISO/IEC 8859-11:2001 ISO/IEC 8859-13:1998 ISO/IEC 8859-14:1998 ISO/IEC 8859-15:1999 ISO/IEC 8859-16:2001 Title Information technology – 8-bit single-byte coded graphic character sets – Part 1: Latin alphabet No. 1 Information technology – 8-bit single-byte coded graphic character sets – Part 2: Latin alphabet No. 2 Information technology – 8-bit single-byte coded graphic character sets – Part 3: Latin alphabet No. 3 Information technology – 8-bit single-byte coded graphic character sets – Part 4: Latin alphabet No. 4 Information technology – 8-bit single-byte coded graphic character sets – Part 5: Latin/Cyrillic alphabet Information technology – 8-bit single-byte coded graphic character sets – Part 6: Latin/Arabic alphabet Information technology – 8-bit single-byte coded graphic character sets – Part 7: Latin/Greek alphabet Information technology – 8-bit single-byte coded graphic character sets – Part 8: Latin/Hebrew alphabet Information technology – 8-bit single-byte coded graphic character sets – Part 9: Latin alphabet No. 5 Information technology – 8-bit single-byte coded graphic character sets – Part 10: Latin alphabet No. 6 Information technology – 8-bit single-byte coded graphic character sets – Part 11: Latin/Thai alphabet Information technology – 8-bit single-byte coded graphic character sets – Part 13: Latin alphabet No. 7 Information technology – 8-bit single-byte coded graphic character sets – Part 14: Latin alphabet No. 8 (Celtic) Information technology – 8-bit single-byte coded graphic character sets – Part 15: Latin alphabet No. 9 Information technology – 8-bit single-byte coded graphic character sets – Part 16: Latin alphabet No. 10 Description While the bit patterns of the 95 printable ASCII characters are sufficient to exchange information in modern English, most other languages that use Latin-derived alphabets need additional symbols not covered by ASCII, such as ß (German), ñ (Spanish), å (Swedish and other Nordic languages) and ő (Hungarian). ISO/IEC 8859 sought to remedy this problem by utilizing the eighth bit in an 8-bit byte to allow positions for another 96 printable characters. Early encodings were limited to 7 bits because of restrictions of some V1.0 2013-01-15 Page 229 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot data transmission protocols, and partially for historical reasons. However, more characters were needed than could fit in a single 8-bit character encoding, so several mappings were developed, including at least ten suitable for various Latin-derived alphabets. The ISO/IEC 8859-n encodings only contain printable characters, and were designed to be used in conjunction with control characters mapped to the unassigned bytes. To this end a series of encodings registered with the IANA add the C0 control set (control characters mapped to bytes 0 to 31) from ISO 646 and the C1 control set (control characters mapped to bytes 128 to 159) from ISO 6429, resulting in full 8-bit character maps with most, if not all, bytes assigned. These sets have ISO-8859-n as their preferred MIME name or, in cases where a preferred MIME name isn't specified, their canonical name. Many people use the terms ISO/IEC 8859-n and ISO-8859-n interchangeably. ISO/IEC 8859-11 did not get such a charset assigned, presumably because it was almost identical to TIS 620. [source: Wikipedia] External links http://en.wikipedia.org/wiki/ISO/IEC_8859 Teletext Profile Reference Name Categories Teletext Teletext; ETS 300 706 – Enhanced Teletext specification File Formats and Persistent Data Structures; General Purpose; Character Sets; ETSI ICS 33020 Abstract This European Telecommunication Standard (ETS) defines the application of CCIR Teletext System B to CCIR 625 Line 50 field Television Systems B, D, G, H, I, K and L. The System is optimised for broadcast media using cable, terrestrial and satellite transmission and the associated service and product environment. Reliable reception of data is ensured, since there is a good match between the service area defined for vision and sound reception and that provided for Teletext data broadcasting Current Version ETS 300 706 Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from http://www.etsi.org/deliver/etsi_i_ets/300700_300799/300706/01_60/et s_300706e01p.pdf Description Teletext data packets are normally grouped together to form “pages” of information, although some have a “stand-alone” function. The range of presentation and application features are arranged to be downward compatible. This permits initial services to be defined and existing services to be upgraded, without rendering obsolete equipment V1.0 2013-01-15 Page 230 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot already in the field. External links • http://en.wikipedia.org/wiki/Teletext Unicode Profile Reference Name Unicode Unicode (ISO/IEC 10646:2012: Information technology – Universal Coded Character Set (UCS)) Categories File Formats and Persistent Data Structures; General Purpose; Character Sets; ISO; IEC ICS 35040 Abstract ISO/IEC 10646:2012 specifies the Universal Character Set (UCS). It is applicable to the representation, transmission, interchange, processing, storage, input and presentation of the written form of the languages of the world as well as additional symbols. It covers 110 181 characters from the world's scripts. Current Version 2012 Other editions AAL Relevance Popular character set, may be used in AAL applications. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=56921 Description Unicode is a computing industry standard for the consistent encoding, representation and handling of text expressed in most of the world's writing systems. Developed in conjunction with the Universal Character Set standard and published in book form as The Unicode Standard, the latest version of Unicode contains a repertoire of more than 110,000 characters covering 100 scripts. The standard consists in a set of code charts for visual reference, an encoding methodology and set of standard character encodings, a set of reference data computer files, and a number of related items, such as character properties, rules for normalization, decomposition, collation, rendering, and bidirectional display order (for the correct display of text containing both right-to-left scripts, such as Arabic and Hebrew, and left-to-right scripts). As of September 2012, the most recent version is Unicode 6.2. External links • http://en.wikipedia.org/wiki/Unicode V1.0 2013-01-15 Page 231 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 4. Terminologies and Semantics 4.1. Languages for Knowledge Representation OWL: Web Ontology Language Profile Reference Name Categories OWL OWL: Web Ontology Language Ambient Intelligence; Terminologies and Semantics; Languages for Knowledge Representation; W3C ICS 35.060 Languages used in information technology Abstract The Web Ontology Language (OWL) is a family of knowledge representation languages for authoring ontologies. Current Version 2 Other editions AAL Relevance OWL is important for formal representations of knowledge as a set of concepts within the domains related to AAL. Available from http://www.w3.org/TR/owl-ref/ Description The Web Ontology Language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL is developed as a vocabulary extension of RDF (the Resource Description Framework) and is derived from the DAML+OIL Web Ontology Language. [Source: http://www.w3.org/TR/owl-ref/, accessed 2012-10-10] External links • Web Ontology Language • OWL Web Ontology Language Reference RDF: Resource Description Framework Profile Reference Name Categories V1.0 RDF RDF: Resource Description Framework Ambient Intelligence; Terminologies and Semantics; Languages for Knowledge Representation; W3C 2013-01-15 Page 232 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract 35.080 Software The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. Current Version 2004 Other editions AAL Relevance RDF is important for representing information about resources in the World Wide Web related to AAL. Available from http://www.w3.org/TR/rdf-primer Description The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. It is particularly intended for representing metadata about Web resources, such as the title, author, and modification date of a Web page, copyright and licensing information about a Web document, or the availability schedule for some shared resource. However, by generalizing the concept of a “Web resource”, RDF can also be used to represent information about things that can be identified on the Web, even when they cannot be directly retrieved on the Web. Examples include information about items available from on-line shopping facilities (e.g., information about specifications, prices, and availability), or the description of a Web user's preferences for information delivery. RDF is intended for situations in which this information needs to be processed by applications, rather than being only displayed to people. RDF provides a common framework for expressing this information so it can be exchanged between applications without loss of meaning. Since it is a common framework, application designers can leverage the availability of common RDF parsers and processing tools. The ability to exchange information between different applications means that the information may be made available to applications other than those for which it was originally created. RDF is based on the idea of identifying things using Web identifiers (called Uniform Resource Identifiers, or URIs), and describing resources in terms of simple properties and property values. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values. To make this discussion somewhat more concrete as soon as possible, the group of statements “there is a Person identified by http://www.w3.org/People/EM/contact#me, whose name is Eric Miller, whose email address is [email protected], and whose title is Dr.” could be represented as the RDF graph in Figure 1: V1.0 2013-01-15 Page 233 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Figure 1: An RDF Graph Describing Eric Miller [Source: http://www.w3.org/TR/rdf-primer/, accessed 2012-10-10] External links • RDF Primer (W3) • Resource Description Framework (Wikipedia) • Resource Description Framework (Community Wiki) RDFS: RDF Schema Profile Reference Name Categories RDFS RDFS: RDF Schema Terminologies and Semantics; Languages for Knowledge Representation; ICS Abstract RDF Schema (variously abbreviated as RDFS, RDF(S), RDF-S, or RDF/S) is a set of classes with certain properties using the RDF extensible knowledge representation language, providing basic elements for the description of ontologies, otherwise called RDF vocabularies, intended to structure RDF resources. [Source: Wikipedia] Current Version 2004 V1.0 2013-01-15 Page 234 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance As RDF is important to AAL for representing information about resources in the World Wide Web related to AAL, RDFS provides a syntax for data exchange Available from Description RDF's vocabulary description language, RDF Schema, is a semantic extension (as defined in [RDF-SEMANTICS]) of RDF. It provides mechanisms for describing groups of related resources and the relationships between these resources. RDF Schema vocabulary descriptions are written in RDF using the terms described in this document. These resources are used to determine characteristics of other resources, such as the domains and ranges of properties. The RDF vocabulary description language class and property system is similar to the type systems of object-oriented programming languages such as Java. RDF differs from many such systems in that instead of defining a class in terms of the properties its instances may have, the RDF vocabulary description language describes properties in terms of the classes of resource to which they apply. This is the role of the domain and range mechanisms described in this specification. For example, we could define the e.g.:author property to have a domain of e.g.:Document and a range of e.g.:Person, whereas a classical object oriented system might typically define a class e.g.:Book with an attribute called e.g.:author of type e.g.:Person. Using the RDF approach, it is easy for others to subsequently define additional properties with a domain of e.g.:Document or a range of e.g.:Person. This can be done without the need to re-define the original description of these classes. One benefit of the RDF property-centric approach is that it allows anyone to extend the description of existing resources, one of the architectural principles of the Web. This specification does not attempt to enumerate all the possible forms of vocabulary description that are useful for representing the meaning of RDF classes and properties. Instead, the RDF vocabulary description strategy is to acknowledge that there are many techniques through which the meaning of classes and properties can be described. Richer vocabulary or 'ontology' languages such as DAML+OIL, W3C's [OWL] language, inference rule languages and other formalisms (for example temporal logics) will each contribute to our ability to capture meaningful generalizations about data in the Web. RDF vocabulary designers can create and deploy Semantic Web applications using the RDF vocabulary description language 1.0 facilities, while exploring richer vocabulary description languages that share this general approach. The language defined in this specification consists of a collection of RDF resources that can be used to describe properties of other RDF resources (including properties) in application-specific RDF vocabularies. The core vocabulary is defined in a namespace informally called 'rdfs' here. That namespace is identified by the URI-Reference http://www.w3.org/2000/01/rdf-schema# and is associated with the prefix 'rdfs'. This specification also uses the prefix 'rdf' to refer to the RDF namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. For convenience and readability, this specification uses an abbreviated form to represent URI-References. A name of the form prefix:suffix should be interpreted as a URIReference consisting of the URI-Reference associated with the prefix concatenated with V1.0 2013-01-15 Page 235 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot the suffix. [Source: W3C] External links • http://www.w3.org/TR/2004/REC-rdf-schema-20040210/ • http://www.w3.org/2001/sw/wiki/RDFS • http://en.wikipedia.org/w/index.php?title=RDF_Schema&oldid=519392007 XML: eXtensible Markup Language Profile Reference Name Categories XML XML: eXtensible Markup Language Terminologies and Semantics; Languages for Knowledge Representation; ICS 35.240.30: IT applications in information, documentation and publishing Abstract Extensible Markup Language (XML) is a markup language created to structure, store, and transport data by defining a set of rules for encoding documents in a format that is both human-readable and machine-readable. [Source: Wikipedia] Current Version Other editions ISO/IEC 13250-3:2007; Extensible Markup Language (XML) 1.0 (Fifth Edition); Extensible Markup Language (XML) 1.1 (Second Edition) AAL Relevance XML can be used in different ways, e.g. for building multimodal interfaces Available from Description The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML. Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behaviour of computer programs which process them. XML is an application profile or restricted form of SGML, the Standard Generalized Markup Language [ISO 8879]. By construction, XML documents are conforming SGML documents. XML documents are made up of storage units called entities, which contain either parsed or unparsed data. Parsed data is made up of characters, some of which form character data, and some of which form markup. Markup encodes a description of the document's storage layout and logical structure. XML provides a mechanism to impose constraints on the storage layout and logical structure. V1.0 2013-01-15 Page 236 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot [Source: W3C] External links • http://en.wikipedia.org/w/index.php?title=XML&oldid=522247610 • http://www.w3.org/TR/xml/ • http://www.w3.org/TR/xml11/ 4.2. Electrotechnical Terminology IEC 60050 Profile Reference Name Categories ICS Abstract IEC 60050 IEC 60050: International Electrotechnical Vocabulary Terminologies and Semantics; Electrotechnical Terminology; IEC; Depends on the discipline The International Electrotechnical Vocabulary (IEV) aims on the standardisation of the vocabulary in electrical engineering. Current Version Miscellaneous Other editions AAL Relevance Some parts of the IEV may be relevant to AAL. Available from http://www.electropedia.org/ Standard Parts Standard 101 102 103 111 112 113 121 131 141 151 161 191 195 212 V1.0 Title Mathematics Mathematics - General concepts and linear algebra Mathematics - Functions Physics and chemistry Quantities and units Physics for electrotechnology Electromagnetism Circuit theory Polyphase systems and circuits Electrical and magnetic devices Electromagnetic compatibility Dependability and quality of service Earthing and protection against electric shock Electrical insulating solids, liquids and gases 2013-01-15 Page 237 of 490 AALIANCE2 221 311 312 313 314 321 351 371 393 394 411 415 421 426 431 436 441 442 444 445 447 448 461 466 471 482 521 531 541 551 561 581 601 602 603 V1.0 D4.1 Online Repository of Standards - Snapshot Magnetic materials and components Electrical and electronic measurements - General terms relating to measurements Electrical and electronic measurements - General terms relating to electrical measurements Electrical and electronic measurements - Types of electrical measuring instruments Electrical and electronic measurements - Specific terms according to the type of instrument Instrument transformers Control technology Telecontrol Nuclear instrumentation - Physical phenomena and basic concepts Nuclear instrumentation - Instruments, systems, equipment and detectors Rotating machinery Wind turbine generator systems Power transformers and reactors Equipment for explosive atmospheres Transductors Power capacitors Switchgear, controlgear and fuses Electrical accessories Elementary relays Time relays Measuring relays Power system protection Electric cables Overhead lines Insulators Primary and secondary cells and batteries Semiconductor devices and integrated circuits Electronic tubes Printed circuits Power electronics Piezoelectric devices for frequency control and selection Electromechanical components for electronic equipment Generation, transmission and distribution of electricity - General Generation, transmission and distribution of electricity - Generation Generation, transmission and distribution of electricity - Power systems planning and management 2013-01-15 Page 238 of 490 AALIANCE2 604 605 617 651 691 701 702 704 705 712 713 714 715 716 721 722 723 725 726 731 732 801 802 806 807 808 811 815 821 826 841 845 851 881 891 D4.1 Online Repository of Standards - Snapshot Generation, transmission and distribution of electricity - Operation Generation, transmission and distribution of electricity - Substations Organization/Market of electricity Live working Tariffs for electricity Telecommunications, channels and networks Oscillations, signals and related devices Transmission Radio wave propagation Antennas Radiocommunications: transmitters, receivers, networks and operation Switching and signalling in telecommunications Telecommunication networks, teletraffic and operation Integrated services digital network (ISDN) - Part 1: General aspects Telegraphy, facsimile and data communication Telephony Broadcasting: Sound, television, data Space radiocommunications Transmission lines and waveguides Optical fibre communication Computer network technology Acoustics and electroacoustics Ultrasonics Recording and reproduction of audio and video Digital recording of audio and video signals Video cameras for non-broadcasting Electric traction Superconductivity Signalling and security apparatus for railways Electrical installations Industrial electroheat Lighting Electric welding Radiology and radiological physics Electrobiology Description Electropedia (also known as the “IEV Online”) is the world's most comprehensive online electrical and electronic terminology database containing more than 20 000 terms and definitions in English and French organized by subject area, with equivalent terms in various other languages: Arabic, Chinese, German, Italian, Japanese, Norwegian (Bokmål V1.0 2013-01-15 Page 239 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot and Nynorsk), Portuguese, Polish, Russian, Slovenian, Spanish and Swedish (coverage varies by subject area). Electropedia is produced by the IEC, the world’s leading organization that prepares and publishes International Standards for all electrical, electronic and related technologies – collectively known as “electrotechnology”. Electropedia contains all the terms and definitions in the International Electrotechnical Vocabulary or IEV which is published also as a set of publications in the IEC 60050 series that can be ordered separately from the IEC webstore. The world’s experts in electrotechnical terminology work to produce Electropedia under the responsibility of IEC Technical Committee 1 (Terminology), one of the 175 IEC technical committees. [Source: Electropedia] External links • http://www.electropedia.org/ 4.3. Medical Terminology ATC/DDD Profile Reference Name ATC/DDD ATC/DDD: Anatomical Therapeutic Chemical classification system/ Defined Daily Dose Categories Terminologies and Semantics; Medical Terminology; WHO ICS 01.040.11 - Health care technology (Vocabularies) Abstract The Anatomical, Therapeutic and Chemical (ATC) classification system and the Defined Daily Dose (DDD) are recommended by WHO for measuring drug utilization in countries. The WHO Collaborating Centre for Drug Statistics Methodology in Oslo, Norway (WHO CC, Oslo), develops and maintains the ATC/DDD system. An International Working Group meets twice a year to guide the Centre in this work. [Source: WHO] Current Version Other editions AAL Relevance Useful for storing patient-related information about drugs and dosage. Available from http://www.whocc.no/atc_ddd_publications/guidelines/ Description The Anatomical Therapeutic Chemical (ATC) Classification System is used for the classification of drugs. It is controlled by the WHO Collaborating Centre for Drug Statistics Methodology (WHOCC), and was first published in 1976. V1.0 2013-01-15 Page 240 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot This pharmaceutical coding system divides drugs into different groups according to the organ or system on which they act and/or their therapeutic and chemical characteristics. Each bottom-level ATC code stands for a pharmaceutically used substance in a single indication (or use). This means that one drug can have more than one code: acetylsalicylic acid (aspirin), for example, has A01AD05 as a drug for local oral treatment, B01AC06 as a platelet inhibitor, and N02BA01 as an analgesic and antipyretic. On the other hand, several different brands share the same code if they have the same active substance and indications. [Source: Wikipedia] External links • http://www.who.int/medicines/areas/quality_safety/safety_efficacy/utilization/en/index.ht ml • http://en.wikipedia.org/w/index.php? title=Anatomical_Therapeutic_Chemical_Classification_System&oldid=523185572 DICOM Profile Reference Name Categories DICOM DICOM: Digital Imaging and Communications in Medicine Communication Protocols; Medical Devices; File Formats and Persistent Data Structures; General Purpose; Medical; ISO ICS 35.240.80: IT applications in health care technology Abstract DICOM defines criteria for communication, visualization, archiving and printing of biomedical information Current Version http://medical.nema.org/ (there may be daily changes) Other editions ISO 12052:2006: Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management AAL Relevance DICOM is a public standard, so it achieves a great diffusion among medical devices. This involves a greater exchange of information Available from http://medical.nema.org/standard.html http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=43218 Description DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting information in medical imaging. It includes a file format definition and a network communications protocol. The communication protocol is an application protocol that uses TCP/IP to communicate between systems. DICOM files can be exchanged between two entities that are capable of receiving image and patient data in DICOM format. The National Electrical Manufacturers Association (NEMA) holds the copyright to this standard.[1] It was developed by the DICOM Standards Committee, V1.0 2013-01-15 Page 241 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot whose members[2] are also partly members of NEMA.[3] DICOM enables the integration of scanners, servers, workstations, printers, and network hardware from multiple manufacturers into a picture archiving and communication system (PACS). The different devices come with DICOM conformance statements which clearly state which DICOM classes they support. DICOM has been widely adopted by hospitals and is making inroads in smaller applications like dentists' and doctors' offices. DICOM is known as NEMA standard PS3, and as ISO standard 12052:2006 “Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management”. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/DICOM ICD Profile Reference Name ICD ICD: International Statistical Classification of Diseases and Related Health Problems Categories Terminologies and Semantics; Medical Terminology ICS 01.040.11 - Health care technology (Vocabularies) Abstract The International Classification of Diseases (ICD) is according to its publisher, (World Health Organization) “the standard diagnostic tool for epidemiology, health management and clinical purposes. It is known as a health care classification system that provides codes to classify diseases and a wide variety of signs, symptoms, abnormal findings, complaints, social circumstances, and external causes of injury or disease. Current Version ICD-10, minor annual updates, major triennial updates Other editions National adoptions available AAL Relevance Useful for storing patient-related information about diagnosis. ICD may also be useful to classify diagnosis related AAL technologies/ scenarios, i.e. in context of a planning tool. Available from http://apps.who.int/classifications/icd10/browse/2010/en Description The International Classification of Diseases (ICD) is the standard diagnostic tool for epidemiology, health management and clinical purposes. This includes the analysis of the general health situation of population groups. It is used to monitor the incidence and prevalence of diseases and other health problems. It is used to classify diseases and other health problems recorded on many types of health and vital records including death certificates and health records. In addition to enabling the V1.0 2013-01-15 Page 242 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot storage and retrieval of diagnostic information for clinical, epidemiological and quality purposes, these records also provide the basis for the compilation of national mortality and morbidity statistics by WHO Member States. It is used for reimbursement and resource allocation decision-making by countries. ICD-10 was endorsed by the Forty-third World Health Assembly in May 1990 and came into use in WHO Member States as from 1994. The 11th revision of the classification has already started and will continue until 2015. [Source: WHO] External links • http://www.who.int/classifications/icd/en/ • http://en.wikipedia.org/w/index.php? title=International_Statistical_Classification_of_Diseases_and_Related_Health_Problem s&oldid=518130878 ICF Profile Reference Name Categories ICS Abstract ICF ICF: International Classification of Functioning, Disability and Health Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) The International Classification of Functioning, Disability and Health, also known as ICF, is a classification of the health components of functioning and disability. [Source: Wikipedia] Current Version Other editions National adoptions/ translations AAL Relevance Useful for storing patient-related information about disabilities and functionalities. ICD may also be useful to classify disability and functional related AAL technologies/ scenarios, i.e. in context of a planning tool. Available from http://apps.who.int/classifications/icfbrowser/ Description The International Classification of Functioning, Disability and Health, known more commonly as ICF, is a classification of health and health-related domains. These domains are classified from body, individual and societal perspectives by means of two lists: a list of body functions and structure, and a list of domains of activity and participation. Since an individual’s functioning and disability occurs in a context, the ICF also includes a list of environmental factors. The ICF is WHO's framework for measuring health and disability at both individual and population levels. The ICF was officially endorsed by all 191 WHO Member States in the Fifty-fourth World Health Assembly on 22 May 2001(resolution WHA 54.21). Unlike its V1.0 2013-01-15 Page 243 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot predecessor, which was endorsed for field trail purposes only, the ICF was endorsed for use in Member States as the international standard to describe and measure health and disability. The ICF puts the notions of ‘health’ and ‘disability’ in a new light. It acknowledges that every human being can experience a decrement in health and thereby experience some degree of disability. Disability is not something that only happens to a minority of humanity. The ICF thus ‘mainstreams’ the experience of disability and recognises it as a universal human experience. By shifting the focus from cause to impact it places all health conditions on an equal footing allowing them to be compared using a common metric – the ruler of health and disability. Furthermore ICF takes into account the social aspects of disability and does not see disability only as a 'medical' or 'biological' dysfunction. By including Contextual Factors, in which environmental factors are listed ICF allows to records the impact of the environment on the person's functioning. [Source: WHO] External links • http://www.who.int/classifications/icf/en/ • http://en.wikipedia.org/w/index.php? title=International_Classification_of_Functioning,_Disability_and_Health&oldid=4989331 94 ICHI Profile Reference Name Categories ICS Abstract ICHI ICHI: International Classification of Health Interventions Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) The ICHI is a system of classifying procedure codes being developed by the WHO and currently only available as a beta release. ICHI will replace the International Classification of Procedures in Medicine (ICPM). Current Version Other editions AAL Relevance The ICHI may be relevant in the future if AAL technologies will have a medical purpose, i.e. telerehabilitation, assessments or drug delivery. Available from http://www.who.int/classifications/ichi/en/ Description The purpose of this classification is to provide Member States, health care service providers and organizers, and researchers with a common tool for reporting and analysing the distribution and evolution of health interventions for statistical purposes. It is structured with various degrees of specificity for use at the different levels of the health systems, and V1.0 2013-01-15 Page 244 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot uses a common accepted terminology in order to permit comparison of data between countries and services. History: The need to classify interventions first emerged in 1971. It was initially limited to surgical procedures. The first International Classification of Procedures in Medicine (ICPM) was published in 1978. International work on the subject came to a virtual halt in 1989 , because of the inadequacy of the consultation procedures with regard to the necessary adaptability to rapid and extensive changes in the field. A number of countries, however, undertook work for national purposes. The resulting classifications came short of providing adequate tools for use at the international level. Today, the need for an international classification has reemerged with a wider scope. The envisaged International Classification of Health Interventions aims to cover a wide range of measures taken for curative and preventive purposes by medical, surgical and other health-related care services. Current status: In recent years, the Network of WHO Collaborating Centres for the Family of International Classifications has promoted the development of a short list of health Interventions for international use, based on the Australian Modification of the International Classification of Diseases, 10th revision (ICD-10-AM) It is intended to be used in countries that do not, as yet, have their own classification of interventions. An initial ICHI version is being adapted to meet present day conformance criteria with recognized standards. In particular, the multiple application areas of such a classification calls for a multiaxial capture of the underlying knowledge. Furthermore rapid change in science and technology implies frequent updates. Adequate technical solutions must therefore be developed. The Family Development Committee of the Network of WHO Collaborating Centres for the Family of international Classifications is actively developing plans and canvassing support to that end. [Source: WHO] External links • http://www.who.int/classifications/ichi/en/ • http://en.wikipedia.org/w/index.php? title=International_Classification_of_Health_Interventions&oldid=507101190 ISO/IEEE 11073 Profile Reference Name Categories ICS Abstract V1.0 ISO/IEEE 11073 ISO/IEEE 11073: Health informatics - Medical / health device communication standards Communication Protocols; Medical Devices; Personal Health Records; Terminologies and Semantics; Medical Terminology; ISO; IEEE 35.240.80: IT applications in health care technology CEN ISO/IEEE 11073 Health informatics - Medical / health device communication standards enable communication between medical, 2013-01-15 Page 245 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot health care and wellness devices and with external computer systems. They provide automatic and detailed electronic data capture of clientrelated and vital signs information, and of device operational data. Current Version see Standard Parts below Other editions AAL Relevance This is the standard for data communications between health devices Available from see Standard Parts below Standard Parts Standard ISO/IEEE 11073-20101:2004 ISO/IEEE 11073-20601:2010 Title Health informatics – Point-of-care medical device communication – Part 20101: Application profiles – Base standard Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale Health informatics – Personal health device communication – Part 10471: Device specialization Independent living activity hub Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter Health informatics – Point-of-care medical device communication – Part 30200: Transport profile – Cable connected Health informatics – Point-of-care medical device communication – Part 30300: Transport profile – Infrared wireless Health informatics – Point-of-care medical device communication – Part 10201: Domain information model Health informatics – Point-of-care medical device communication – Part 10101: Nomenclature Health informatics – Standard communication protocol – Part 91064: Computer-assisted electrocardiography Health informatics – Personal health device V1.0 2013-01-15 ISO/IEEE 11073-10408:2010 ISO/IEEE 11073-10415:2010 ISO/IEEE 11073-10471:2010 ISO/IEEE 11073-10407:2010 ISO/IEEE 11073-10404:2010 ISO/IEEE 11073-10417:2010 ISO/IEEE 11073-30200:2004 ISO/IEEE 11073-30300:2004 ISO/IEEE 11073-10201:2004 ISO/IEEE 11073-10101:2004 ISO 11073-91064:2009 Page 246 of 490 AALIANCE2 ISO 11073-90101:2008 ISO/TS 11073-92001:2007 ISO/IEEE FDIS 11073-10406 ISO/IEEE DIS 11073-10417 ISO/IEEE DIS 11073-10418 ISO/IEEE FDIS 11073-10420 ISO/IEEE FDIS 11073-10421 ISO/IEEE FDIS 11073-10472 ISO/IEEE FDIS 11073-30400 D4.1 Online Repository of Standards - Snapshot communication – Part 20601: Application profile – Optimized exchange protocol Health informatics – Point-of-care medical device communication – Part 90101: Analytical instruments – Point-of-care test Health informatics – Medical waveform format – Part 92001: Encoding rules Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG) Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter Health informatics – Personal health device communication – Part 10418: Device specialization– International Normalized Ratio (INR) monitor Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyser Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow) Health Informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor Health informatics – Point-of-care medical device communication – Part 30400: Interface profile – Cabled Ethernet Description 7. Provide real-time plug-and-play interoperability for citizen-related medical, healthcare and wellness devices; 8. Facilitate efficient exchange of care device data, acquired at the point-of-care, in all care environments. • “Real-time” means that data from multiple devices can be retrieved, time correlated, and displayed or processed in fractions of a second. • “Plug-and-play” means that all a user has to do is make the connection – the systems automatically detect, configure, and communicate without any other human interaction. • “Efficient exchange of care device data” means that information that is captured at the point-of-care (e.g., personal vital signs data) can be archived, retrieved, and processed by many different types of applications without extensive software and equipment support, and without needless loss of information. The standards are targeted at personal health and fitness devices (such as glucose monitors, pulse oximeters, weighing scales, medication dispensers and activity monitors) V1.0 2013-01-15 Page 247 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot and at continuing and acute care devices (such as pulse oximeters, ventilators and infusion pumps). They comprise a family of standards that can be layered together to provide connectivity optimized for the specific devices being interfaced. There are four main partitions to the standards: • Device data, including a nomenclature, or terminology, optimized for vital signs information representation based on an object-oriented data model, and device • General application services (e.g., polled vs. “event driven” services); • Internetworking and gateway standards (e.g., an observation reporting interface from CEN ISO/IEEE 11073-based messaging and data representation to HL7 or DICOM); • Transports (e.g., cable connected or wireless). [Source: Wikipedia] External links • ISO/IEEE11073 (Wikipedia) LOINC Profile Reference Name Categories ICS Abstract LOINC LOINC: Logical Observation Identifiers Names and Codes Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical laboratory observations. Current Version LOINC 2.40 (Released: 2012-06-30 ) Other editions AAL Relevance Some future AAL technologies may be used for laboratory purposes, i.e. intelligent toilet systems analysing urine or systems for analysing air conditions. Portable systems for analysing blood values, i.e. in context of diabetes are already available. Available from http://loinc.org/downloads Description LOINC applies universal code names and identifiers to medical terminology related to electronic health records. The purpose is to assist in the electronic exchange and gathering of clinical results (such as laboratory tests, clinical observations, outcomes management and research). LOINC has two main parts: laboratory LOINC and clinical LOINC. Clinical LOINC contains a subdomain of Document Ontology which captures types of clinical reports and documents. A formal, distinct, and unique 6-part name is given to each term for test or observation V1.0 2013-01-15 Page 248 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot identity.[4] The database currently has over 58,000 observation terms that can be accessed and understood universally. Each database record includes six fields for the unique specification of each identified single test, observation, or measurement: • Component- what is measured, evaluated, or observed (example: urea,…) • Kind of property- characteristics of what is measured, such as length, mass, volume, time stamp and so on • Time aspect- interval of time over which the observation or measurement was made • System- context or specimen type within which the observation was made (example: blood, urine,…) • Type of scale- the scale of measure. The scale may be quantitative, ordinal, nominal or narrative • Type of method- procedure used to make the measurement or observation [Source: Wikipedia] External links • http://loinc.org/ • http://en.wikipedia.org/w/index.php?title=LOINC&oldid=519804143 MeSH Profile Reference Name Categories ICS Abstract MeSH MeSH: Medical Subject Headings Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) Medical Subject Headings (MeSH) is a comprehensive controlled vocabulary for the purpose of indexing journal articles and books in the life sciences; it can also serve as a thesaurus that facilitates searching. [Source: Wikipedia] Current Version 2012, annual updates Other editions AAL Relevance MeSH can also be used for medical information retrieval which might be relevant for information gathering in AAL scenarios. Available from Files: http://www.nlm.nih.gov/mesh/filelist.html Browser: http://www.nlm.nih.gov/mesh/MBrowser.html Description The 2009 version of MeSH contains a total of 25,186 subject headings, also known as descriptors. Most of these are accompanied by a short description or definition, links to related descriptors, and a list of synonyms or very similar terms (known as entry terms). Because of these synonym lists, MeSH can also be viewed as a thesaurus. V1.0 2013-01-15 Page 249 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot The descriptors or subject headings are arranged in a hierarchy. A given descriptor may appear at several locations in the hierarchical tree. The tree locations carry systematic labels known as tree numbers, and consequently one descriptor can carry several tree numbers. For example, the descriptor “Digestive System Neoplasms” has the tree numbers C06.301 and C04.588.274; C stands for Diseases, C06 for Digestive System Diseases and C06.301 for Digestive System Neoplasms; C04 for Neoplasms, C04.588 for Neoplasms By Site, and C04.588.274 also for Digestive System Neoplasms. The tree numbers of a given descriptor are subject to change as MeSH is updated. Every descriptor also carries a unique alphanumerical ID that will not change. Most subject headings come with a short description or definition. See the MeSH description for diabetes type 2 as an example. The explanatory text is written by the MeSH team based on their standard sources if not otherwise stated. References are mostly encyclopaedias and standard textbooks of the subject areas. References for specific statements in the descriptions are not given, instead readers are referred to the bibliography. In addition to the descriptor hierarchy, MeSH contains a small number of standard qualifiers (also known as subheadings), which can be added to descriptors to narrow down the topic. For example, “Measles” is a descriptor and “epidemiology” is a qualifier; “Measles/epidemiology” describes the subheading of epidemiological articles about Measles. The “epidemiology” qualifier can be added to all other disease descriptors. Not all descriptor/qualifier combinations are allowed since some of them may be meaningless. In all there are 83 different qualifiers. In addition to the descriptors, MeSH also contains some 139,000 Supplementary Concept Records. These do not belong to the controlled vocabulary as such; instead they enlarge the thesaurus and contain links to the closest fitting descriptor to be used in a MEDLINE search. Many of these records describe chemical substances. [Source: Wikipedia] External links • http://www.nlm.nih.gov/mesh/ • http://en.wikipedia.org/w/index.php?title=Medical_Subject_Headings&oldid=518942179 SNOMED Profile Reference Name Categories ICS Abstract V1.0 SNOMED SNOMED: Systematized Nomenclature of Medicine Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) SNOMED CT (Systematized Nomenclature of Medicine – Clinical Terms), is a systematically organised computer processable collection of medical terms providing codes, terms, synonyms and definitions covering diseases, findings, procedures, microorganisms, substances, 2013-01-15 Page 250 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot etc. It allows a consistent way to index, store, retrieve, and aggregate clinical data across specialities and sites of care. [Source: Wikipedia] Current Version Other editions SNOMED-CT AAL Relevance As AAL systems may interact with clinical systems, SNOMED/ SNOMED-CT may help retrieving relevant information. Available from Information on licensing at http://www.ihtsdo.org/licensing/ Description SNOMED CT allows a consistent way to index, store, retrieve, and aggregate clinical data across specialities and sites of care. It also helps in organizing the content of medical records, reducing the variability in the way data is captured, encoded and used for clinical care of patients and research. The primary purpose of SNOMED CT is to support the effective clinical recording of data with the aim of improving patient care. It is a structured collection of medical terms that are used internationally for recording clinical information and are coded in order to be computer processable. It covers areas such as diseases, symptoms, operations, treatments, devices and drugs. Its purpose is to consistently index, store, retrieve, and aggregate clinical data across specialities and sites of care. It helps organizing the content of electronic health records systems, reducing the variability in the way data is captured, encoded and used for clinical care of patients and research. Specific language editions are available which augment the international Edition and can contain language translations as well as additional national terms. SNOMED CT is considered by some to be the most comprehensive, multilingual clinical healthcare terminology in the world. It provides for consistent information interchange and is fundamental to an interoperable electronic health record. It can be used to record the clinical details of individuals in electronic patient records and support application functionality such as informed decision making, linkage to clinical care pathways and knowledge resources, shared care plans and as such support long term patient care. The availability of free automatic coding tools and services, which can return a ranked list of SNOMED CT descriptors to encode any clinical report, could help healthcare professionals to navigate the terminology. [Source: Wikipedia] External links • http://www.ihtsdo.org/snomed-ct/ • http://en.wikipedia.org/w/index.php?title=SNOMED_CT&oldid=523851664 UCUM Profile Reference Name Categories ICS V1.0 UCUM UCUM: Unified Code for Units of Measure Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) 2013-01-15 Page 251 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract The Unified Code for Units of Measure (the UCUM) is a system of codes for unambiguously representing measurement units to both humans and machines. [Source: Wikipedia] Current Version Version: 1.8.2 (2009) Other editions AAL Relevance As some AAL technologies include measurement functionalities UCUM should be considered for data exchange. Available from http://unitsofmeasure.org/ucum.html Description The Unified Code for Units of Measure is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. The purpose is to facilitate unambiguous electronic communication of quantities together with their units. The focus is on electronic communication, as opposed to communication between humans. A typical application of The Unified Code for Units of Measure are electronic data interchange (EDI) protocols, but there is nothing that prevents it from being used in other types of machine communication. The Unified Code for Units of Measure is inspired by and heavily based on ISO 29551983, ANSI X3.50-1986, and HL7's extensions called ISO+. The respective ISO and ANSI standards are both entitled Representation of […] units in systems with limited character sets where ISO 2955 refers to SI and other units provided by ISO 1000-1981, while ANSI X3.50 extends ISO 2955 to include U.S. customary units. Because these standards carry the restriction of limited character sets in their names they seem to be of less value today where graphical user interface and laser printers are in wide-spread use, which is why the European standard ENV 12435 in its clause 7.3 declares ISO 2955 obsolete. ENV 12435 is dedicated exclusively to the communication of measurements between humans in display and print, and does not provide codes that can be used in communication between systems. It does not even provide a specification that would allow communication of units from one system to the screen or printer of another system. The issue about displaying units in the common style defined by the 9th Conférence Générale des Poids et Mesures (CGPM) in 1947 is not just the character set. Although The Unicode Standard and its predecessor ISO/IEC 10646 is the richest character set ever it is still not enough to specify the presentation of units because there are important typographical details such as superscripts, subscripts, roman and italics. [Source: Unitsofmeasure.org] External links • http://unitsofmeasure.org/trac/ • http://en.wikipedia.org/w/index.php? title=Unified_Code_for_Units_of_Measure&oldid=520913962 V1.0 2013-01-15 Page 252 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot UMDNS Profile Reference Name Categories ICS Abstract UMDNS UMDNS: Universal Medical Device Nomenclature System Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) Universal Medical Device Nomenclature System™ (UMDNS) is a standard international nomenclature and computer coding system for medical devices. [Source: ecri.org] Current Version Other editions AAL Relevance As AAL technologies may be used for medical applications (telerehabilitation, emergency detection) they might be included in UMDNS. Available from Description The purpose of UMDNS is to facilitate identifying, processing, filing, storing, retrieving, transferring, and communicating data about medical devices. The nomenclature is used in applications ranging from hospital inventory and work-order controls to national agency medical device regulatory systems and from e-commerce and procurement to medical device databases. UMDNS contains 9,110 unique medical device concepts and definitions (preferred terms), along with an additional 17,036 entry terms to facilitate classifying of biomedical information. UMDNS contains explicit relationships among the nearly 25,000 terms, including hierarchical relationships (e.g., parent:child terms) and synonymous relations, as well as relationships among related devices (e.g., component devices versus the overall system). [Source: ecri.org] External links • https://www.ecri.org/Products/Pages/UMDNS.aspx UMLS Profile Reference Name Categories ICS Abstract V1.0 UMLS UMLS: Unified Medical Language System Terminologies and Semantics; Medical Terminology 01.040.11 - Health care technology (Vocabularies) The Unified Medical Language System (UMLS) is a compendium of 2013-01-15 Page 253 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot many controlled vocabularies in the biomedical sciences. Over 100 vocabularies are part of the UMLS including ICD, SNOMED, LOINC and MeSH. It provides a mapping structure among these vocabularies and thus allows one to translate among the various terminology systems. Current Version 2012AB, continuously updated Other editions AAL Relevance As some of the included vocabularies were already identified as relevant for AAL, UMLS as an aggregation and mapping of these vocabularies is also relevant for AAL. Available from http://www.nlm.nih.gov/research/umls/ Description UMLS consists of three parts: Metathesaurus, Semantic Network and SPECIALIST Lexicon. Metathesaurus The Metathesaurus forms the base of the UMLS and comprises over 1 million biomedical concepts and 5 million concept names, all of which stem from the over 100 incorporated controlled vocabularies and classification systems. Some examples of the incorporated controlled vocabularies are ICD-10, MeSH, SNOMED CT, DSM-IV, LOINC, WHO Adverse Drug Reaction Terminology, UK Clinical Terms, RxNorm, Gene Ontology, and OMIM. The Metathesaurus is organized by concept, and each concept has specific attributes defining its meaning and is linked to the corresponding concept names in the various source vocabularies. Semantic Network Each concept in the Metathesaurus is assigned one or more semantic types (categories), which are linked with one another through semantic relationships. The semantic network is a catalogue of these semantic types and relationships. This is a rather broad classification; there are 135 semantic types and 54 relationships in total. SPECIALIST Lexicon The SPECIALIST Lexicon contains information about common English vocabulary, biomedical terms, terms found in MEDLINE and terms found in the UMLS Metathesaurus. Each entry contains syntactic (how words are put together to create meaning), morphological (form and structure) and orthographic (spelling) information. A set of Java programs use the lexicon to work through the variations in biomedical texts by relating words by their parts of speech, which can be helpful in web searches or searches through an electronic medical record. [Source: Wikipedia] External links • http://www.openclinical.org/medTermUmls.html • http://www.nlm.nih.gov/research/umls/ V1.0 2013-01-15 Page 254 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • http://en.wikipedia.org/w/index.php? title=Unified_Medical_Language_System&oldid=499225647 4.4. Home Automation Terminology DomoML Profile Reference Name Categories DomoML DomoML: Domestic mark-up language Terminologies and Semantics; Home Automation Terminology; Research approach ICS Abstract DomoML is a research approach offering a mark-up language for domestic resources and the human-machine interaction in the home environment. Current Version Research approach, under development Other editions AAL Relevance As AAL scenarios may include home automation and interaction with home automation devices DomoML may be useful to support this interaction. Available from see External links Description DomoML is a mark-up language aimed at the definition of interoperability standard for domestic resources within the NICHE project (Natural Interaction in Computerised Home Environment). The project focuses on human language as a means for mediating user interaction with the home environment, enabling a user to control, query and program devices. Various heterogeneous components are going to take part in this architecture, and DomoML is the glue which allows them to be interfaced. It is a mark-up language intended to define a semantic layer on which novel value-added services (agents) can easily be built. [Source: Furfari et. al. 2004] External links • Furfari F, Sommaruga L, Soria C, Fresco R. DomoML: the definition of a standard markup for interoperability of Human Home Interactions. Proceeding EUSAI '04 Proceedings of the 2nd European Union symposium on Ambient intelligence Pages 4144. doi:10.1145/1031419.1031430 (http://dl.acm.org/citation.cfm?id=1031430) V1.0 2013-01-15 Page 255 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IEC 61331 Profile Reference Name Categories ICS IEC 61331 IEC 61331: Programmable controllers Terminologies and Semantics; Home Automation Terminology; IEC 25.040: Industrial automation systems 25.040.40: Industrial process measurement and control 35.240.50: IT applications in industry (including design automation ) Abstract IEC 61131 applies to programmable controllers (PLC) and their associated peri-pherals such as programming and debugging tools (PADTs), human-machine interfaces (HMIs), etc., which have as their intended use the control and command of machines and industrial processes. It gives the definitions of terms used in this standard. It identifies the principal functional characteristics of programmable controller systems. IEC 61131 is used in industrial settings. [Source: IEC] Current Version see Standard Parts below Other editions AAL Relevance Primarily used in industrial settings IEC 61131 offers device description for sensors and actuators which may be relevant for AAL scenarios Available from see Standard Parts below Standard Parts Standard IEC 61131-1 ed2.0 IEC 61131-2 ed3.0 IEC 61131-3 ed2.0 IEC/TR 61131-4 ed2.0 IEC 61131-5 ed1.0 IEC 61131-6 ed1.0 IEC 61131-7 ed1.0 IEC/TR 61131-8 ed2.0 Title Programmable controllers - Part 1: General information Programmable controllers - Part 2: Equipment requirements and tests Programmable controllers - Part 3: Programming languages Programmable controllers - Part 4: User guidelines Programmable controllers - Part 5: Communications Programmable controllers - Part 6: Functional safety Programmable controllers - Part 7: Fuzzy control programming Programmable controllers - Part 8: Guidelines for the application and implementation of programming languages Description IEC 61131-1:2003 applies to programmable controllers (PLC) and their associated peripherals such as programming and debugging tools (PADTs), human-machine interfaces (HMIs), etc., which have as their intended use the control and command of machines and industrial processes. It gives the definitions of terms used in this standard. It identifies the principal functional characteristics of programmable controller systems. This second edition cancels and replaces the first edition published in 1992 and constitutes a technical revision. This bilingual version (2012-05) corresponds to the monolingual English version, V1.0 2013-01-15 Page 256 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot published in 2003-05. IEC 61131-2:2007 specifies requirements and related tests for programmable controllers (PLCs) and their associated peripherals (for example, programming and debugging tools (PADTs), human-machine interfaces (HMIs), etc.) which have as their intended use the control and command of machines and industrial processes. It establishes the definitions and identifies the principal characteristics relevant to the selection and application of PLCs and their associated peripherals. It specifies the minimum requirements for functional, electrical, mechanical, environmental and construction characteristics, service conditions, safety, EMC, user programming and tests applicable to PLCs and the associated peripherals. This third edition of IEC 61131-2 cancels and replaces the second edition published in 2003 and constitutes a technical revision. This third edition includes some technical changes. IEC 61131-3 specifies syntax and semantics of programming languages for programmable controllers as defined in part 1 of IEC 61131. IEC/TR 61131-4:2004 introduces the end-users of Programmable Controller (PLC) to the IEC 61131 series, and to assist the end-users in their selection and specification of their PLC equipment according to the IEC 61131 series. This user guideline has as its main audience PLC end-users. IEC 61131-5:2000 specifies communication aspects of a programmable controller. It specifies from the viewpoint of a PC how any device can communicate with a PC as a server and how a PC can communicate with any device. In particular, it specifies the behaviour of the PC as it provides services on behalf of other devices and the services the PC application program can request from other devices. This bilingual version (2012-08) corresponds to the monolingual English version, published in 2000-11. IEC 61131-6:2012 specifies requirements for programmable controllers (PLCs) and their associated peripherals, as defined in Part 1, which are intended to be used as the logic subsystem of an electrical/electronic/programmable electronic (E/E/PE) safety-related system. A programmable controller and its associated peripherals complying with the requirements of this part is considered suitable for use in an E/E/PE safety-related system and is identified as a functional safety programmable logic controller (FS-PLC). An FSPLC is generally a hardware (HW) / software (SW) subsystem. An FS-PLC may also include software elements, for example predefined function blocks. IEC 61131-7:2000 defines a language for the programming of Fuzzy Control applications used by programmable controllers. IEC/TR 61131-8:2003 applies to the programming of programmable controller systems using the programming languages defined in IEC 61131-3. It also provides guidelines for the implementation of these languages in programmable controller systems and their programming support environments (PSEs). One implementation using IEC 61131 is IO Link including IODD (IO Device Description) offering descriptions for sensors and actuators. [Source: IEC] External links • http://en.wikipedia.org/w/index.php?title=IEC_61131&oldid=493824097 V1.0 2013-01-15 Page 257 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC TR 15044 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/IEC TR 15044 ISO/IEC TR 15044: Information technology – Terminology for the Home Electronic System (HES) Terminologies and Semantics; Home Automation Terminology; ISO; IEC; 01.040.35: Information technology. Office machines (Vocabularies) 35.240.99: IT applications in other fields 35.200: Interface and interconnection equipment ISO/IEC TR 15044 offers a terminology for Home Electronic Systems (HES). ISO/IEC TR 15044:2000 As AAL systems may use HES the terminology offered by ISO/IEC TR 15044 is also relevant. http://www.iso.org/iso/catalogue_detail.htm?csnumber=26312 Description The home electronic system (HES) provides a common method for interfacing equipment with a variety of home control systems (HCS) such as sensors, actuators, appliances, user interfaces, controllers, switches etc. An HCS is a local area network specialized for residential communications, commonly called home automation. This terminology is applicable to all standards and technical reports dealing with HES. ISO/IEC/TR 29107 Profile Reference Name ISO/IEC/TR 29107 ISO/IEC/TR 29107: Information technology – Intelligent homes Taxonomy of specifications Categories Terminologies and Semantics; Home Automation Terminology: ISO; IEC ICS 35.200: Interface and interconnection equipment 35.240.99: IT applications in other fields Abstract ISO/IEC 29107-1:2010(E) specifies the concept for a taxonomy of standards and other related specifications applicable to intelligent homes. [Source: IEC] Current Version Other editions AAL Relevance As AAL technologies have strong similarities with intelligent homes this taxonomy may be useful and may be also used as a basis for an AAL V1.0 2013-01-15 Page 258 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot taxonomy. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=45130 Description ISO/IEC TR 29107-1 aims on the classification of specifications from ISO, IEC, ISO/IEC JTC 1, ITU and from organizations with liaison status with any of these. It is intended to the various standardisation bodies that are contributing to the intelligent home. With the help of the concept described in this report they should be able to classify their specifications. This will benefit the standardisation bodies to determine if there are overlapping specifications or areas for which specifications are missing. [Source: IEC] 4.5. Building Information Modelling CityGML Profile Reference Name Categories ICS Abstract CityGML CityGML: City Geography Markup Language Terminologies and Semantics; Building Information Modelling CityGML is a common information model for the representation of sets of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical and appearance properties. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. This thematic information goes beyond graphic exchange formats and makes it possible to employ virtual 3D city models for sophisticated analysis tasks in different application domains like simulations, urban data mining, facility management, and thematic inquiries. [Source: Wikipedia] Current Version CityGML 2.0.0 Other editions AAL Relevance CityGML offers also interior architectural models. This may be relevant for modelling AAL interior environments. Available from http://www.citygml.org/index.php?id=1522 Description More and more applications need comprehensive information about the shape and the meaning of urban and landscape structures. Whereas in the past city models often have been built as purely graphical 3D models, new applications have information needs V1.0 2013-01-15 Page 259 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot beyond visual characteristics. Besides geometry, semantics and topology of the 3D objects have to be taken into account in order to enable for thematic queries, analysis tasks, automatic integration, validity checking, or spatial data mining. Since the limited reusability of models inhibits the broader use of 3D city models, a more general modelling approach has to be taken in order to satisfy the information needs of the various application fields. CityGML is a common information model for the representation of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical, and appearance properties. “City” is broadly defined to comprise not just built structures, but also elevation, vegetation, water bodies, “city furniture”, and more. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. These thematic information go beyond graphic exchange formats and allow to employ virtual 3D city models for sophisticated analysis tasks in different application domains like simulations, urban data mining, facility management, and thematic inquiries. For specific domain areas, CityGML also provides an extension mechanism to enrich the data with identifiable features under preservation of semantic interoperability. The rich and general purpose information model provided by CityGML is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing for the possibility of selling the same data to customers from different application fields. CityGML is applicable for large areas and small regions and can represent the terrain and 3D objects in different levels of detail simultaneously. Since either simple, single-scale models without topology and few semantics or very complex multi-scale models with full topology and fine-grained semantical differentiations can be represented, CityGML enables lossless information exchange between different GI systems and users. CityGML is implemented as an XML application schema for the Geography Markup Language version 3.1.1 (GML3). GML3 is the extensible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. CityGML has been adopted as official international standard by the OGC (as an approved GML3 application schema), enabling easy and free access to all the international community. CityGML offers several types of taxonomies and aggregations like • Digital Terrain Models as a combination of (including nested) triangulated irregular networks (TINs), regular rasters, break and skeleton lines, mass points • Sites (currently buildings; bridges and tunnels in the future) • Vegetation (areas, volumes and solitary objects with vegetation classification) • Water bodies (volumes, surfaces) • Transportation facilities (both graph structures and 3D surface data) • City furniture • Generic city objects and attributes • User-definable (recursive) grouping CityGML also offers several levels of detail: V1.0 2013-01-15 Page 260 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • LOD 0 – regional, landscape • LOD 1 – city, region • LOD 2 – city districts, projects • LOD 3 – architectural models (outside), landmarks • LOD 4 – architectural models (interior) [Source: citygmlwiki.org] External links • http://www.citygml.org/ • http://www.citygmlwiki.org/index.php/Main_Page • http://en.wikipedia.org/w/index.php?title=CityGML&oldid=505475747 IFC Profile Reference Name Categories ICS Abstract IFC IFC: Industry Foundation Classes Terminologies and Semantics; Building Information Modelling 25.040.40: Industrial process measurement and control The Industry Foundation Classes (IFC) data model is intended to describe building and construction industry data. IFCs have been developed by buildingSMART International (bSI), as a neutral, nonproprietary or open standard for sharing BIM data among different software applications. Current Version IFC2x3 TC1 Other editions ISO/PAS 16739:2005 AAL Relevance As planning tools for AAL scenarios including floor plans and domestic electrical installations are needed, IFC can be a suitable basis for planning AAL environments. Available from bSI ISO Description In general, Building information modelling (BIM) is a process involving the generation and management of digital representations of physical and functional characteristics of a facility. The resulting building information models become shared knowledge resources to support decision-making about a facility from earliest conceptual stages, through design and construction, through its operational life and eventual demolition. [Source: Wikipedia] Industry Foundation Classes (IFC) represent a data model structure for sharing V1.0 2013-01-15 Page 261 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot construction and facility management data across various applications used in the building domain. The IFC data model is an object-oriented data model based on class definitions representing the things (elements, processes, shapes, etc.) that are used by software applications during a construction or facility management project. The IFC data model focusses on those classes that are needed to share information (rather then processing it in a particular proprietary software). The IFC data model is a neutral and open specification that is not controlled by a singular vendor or group of vendors. [Source: IFC-Wiki] External links • http://www.buildingsmart-tech.org/ • http://www.ifcwiki.org/index.php/Main_Page • http://en.wikipedia.org/w/index.php? title=Industry_Foundation_Classes&oldid=525746250 • http://en.wikipedia.org/w/index.php? title=Building_information_modelling&oldid=525557531 ISO 19000 Profile Reference Name Categories ICS Abstract ISO 19000 ISO 19000 series: ISO geographic information suite of standards Terminologies and Semantics; Building Information Modelling; ISO 35.240.70: IT applications in science ISO 19000ff covers the areas of digital geographic information (such as used by geographic information systems) and geomatics. ISO 19000ff is maintained by ISO/TC 211 and the work is closely related to the efforts of the Open Geospatial Consortium. Current Version see Series Parts below Other editions AAL Relevance As some AAL scenarios contain spatial location technologies and location-based services the ISO 19000 series should be referenced. Available from see Series Parts below Series Parts Standard ISO 6709:2008 ISO 19101:2002 ISO/DIS 19101-1 ISO/TS 19101-2:2008 V1.0 Title Standard representation of geographic point location by coordinates Geographic information – Reference model Geographic information – Reference model - Part 1: Fundamentals Geographic information – Reference model – Part 2: Imagery 2013-01-15 Page 262 of 490 AALIANCE2 ISO/TS 19103:2005 ISO/TS 19104:2008 ISO 19105:2000 ISO 19106:2004 ISO 19107:2003 ISO 19108:2002 ISO/CD 19109 ISO 19109:2005 ISO 19110:2005 ISO 19111:2007 ISO 19111-2:2009 ISO 19112:2003 ISO 19113:2002 ISO 19114:2003 ISO 19115:2003 ISO/DIS 19115-1 ISO 19115-2:2009 ISO 19116:2004 ISO 19117:2012 ISO 19118:2011 ISO 19119:2011 ISO/TR 19120:2001 ISO/TR 19121:2000 ISO/TR 19122:2004 ISO 19123:2005 ISO 19125-1:2004 ISO 19125-2:2004 ISO 19126:2009 ISO/TS 19127:2005 ISO 19128:2005 ISO/TS 19129:2009 ISO/TS 19130:2010 V1.0 D4.1 Online Repository of Standards - Snapshot Geographic information – Conceptual schema language Geographic information – Terminology Geographic information – Conformance and testing Geographic information – Profiles Geographic information – Spatial schema Geographic information – Temporal schema Geographic information – Rules for application schema Geographic information – Rules for application schema Geographic information – Methodology for feature cataloguing Geographic information – Spatial referencing by coordinates Geographic information – Spatial referencing by coordinates – Part 2: Extension for parametric values Geographic information – Spatial referencing by geographic identifiers Geographic information – Quality principles Geographic information – Quality evaluation procedures Geographic information – Metadata Geographic information – Metadata – Part 1: Fundamentals Geographic information – Metadata – Part 2: Extensions for imagery and gridded data Geographic information – Positioning services Geographic information – Portrayal Geographic information – Encoding Geographic information – Services Geographic information – Functional standards Geographic information – Imagery and gridded data Geographic information/Geomatics – Qualification and certification of personnel Geographic information – Schema for coverage geometry and functions Geographic information – Simple feature access – Part 1: Common architecture Geographic information – Simple feature access – Part 2: SQL option Geographic information – Feature concept dictionaries and registers Geographic information – Geodetic codes and parameters Geographic information – Web map server interface Geographic information – Imagery, gridded and coverage data framework Geographic information - Imagery sensor models for geopositioning 2013-01-15 Page 263 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/DTS 19130-2 Geographic information – Imagery sensor models for geopositioning – Part 2: SAR, InSAR, Lidar and Sonar ISO 19131:2007 Geographic information – Data product specifications ISO 19132:2007 Geographic information – Location-based services – Reference model ISO 19133:2005 Geographic information – Location-based services – Tracking and navigation ISO 19134:2007 Geographic information – Location-based services – Multimodal routing and navigation ISO 19135:2005 Geographic information – Procedures for item registration ISO/TS 19135-2:2012 Geographic information - Procedures for item registration – Part 2: XML schema implementation ISO 19136:2007 Geographic information – Geography Markup Language (GML) ISO 19137:2007 Geographic information – Core profile of the spatial schema ISO/TS 19138:2006 Geographic information – Data quality measures ISO/TS 19139:2007 Geographic information – Metadata – XML schema implementation ISO/DTS 19139-2:2012 Geographic Information – Metadata – XML Schema Implementation – Part 2: Extensions for imagery and gridded data ISO 19141:2008 Geographic information – Schema for moving features ISO 19142:2010 Geographic information – Web Feature Service ISO 19143:2010 Geographic information – Filter encoding ISO 19144-1:2009 Geographic information – Classification systems – Part 1: Classification system structure ISO 19144-2:2012 Geographic information - Classification systems – Part 2: Land Cover Meta Language (LCML) ISO/FDIS 19145 Geographic information – Registry of representations of geographic point location ISO 19146:2010 Geographic information – Cross-domain vocabularies ISO/CD 19147 Geographic information – Location based services – Transfer Nodes ISO 19148:2012 Geographic information – Linear referencing ISO 19149:2011 Geographic information – Rights expression language for geographic information – GeoREL ISO/TS 19150-1:2012 Geographic information – Ontology – Part 1: Framework ISO/CD 19150-2 Geographic information – Ontology – Part 2: Rules for developing ontologies in the Web Ontology Language (OWL) ISO 19152:2012 Geographic information – Land Administration Domain Model (LADM) ISO/DIS 19153 Geospatial Digital Rights Management Reference Model (GeoDRM RM) ISO/CD 19154 Geographic information – Ubiquitous public access – Reference V1.0 2013-01-15 Page 264 of 490 AALIANCE2 ISO 19155:2012 ISO 19156:2011 ISO/DIS 19157 ISO/TS 19158:2012 ISO/DTS 19159-1 ISO/NP 19160-1 D4.1 Online Repository of Standards - Snapshot model Geographic information – Place Identifier (PI) architecture Geographic information – Observations and measurements Geographic information – Data quality Geographic information – Quality assurance of data supply' Geographic information – Calibration and validation of remote sensing imagery sensors and data – Part 1: Optical sensors Addressing – Part 1: Conceptual model Description ISO 6709:2008 is applicable to the interchange of coordinates describing geographic point location. It specifies the representation of coordinates, including latitude and longitude, to be used in data interchange. It additionally specifies representation of horizontal point location using coordinate types other than latitude and longitude. It also specifies the representation of height and depth that can be associated with horizontal coordinates. Representation includes units of measure and coordinate order. ISO 6709:2008 is not applicable to the representation of information held within computer memories during processing and in their use in registers of geodetic codes and parameters. ISO 6709:2008 supports point location representation through the eXtensible Markup Language (XML) and, recognizing the need for compatibility with the previous version of this International Standard, ISO 6709:1983, allows for the use of a single alpha-numeric string to describe point locations. For computer data interchange of latitude and longitude, ISO 6709:2008 generally suggests that decimal degrees be used. It allows the use of sexagesimal notations: degrees, minutes and decimal minutes or degrees, minutes, seconds and decimal seconds. ISO 6709:2008 does not require special internal procedures, fileorganization techniques, storage medium, languages, etc., to be used in its implementation. ISO 19101:2002 defines the framework for standardization in the field of geographic information and sets forth the basic principles by which this standardization takes place. This framework identifies the scope of the standardization activity being undertaken and the context in which it takes place. The framework provides the method by which what is to be standardized can be determined and describes how the contents of the standards are related. Although structured in the context of information technology and information technology standards, this International Standard is independent of any application development method or technology implementation approach. ISO TS 19103:2005 provides rules and guidelines for the use of a conceptual schema language within the ISO geographic information standards. The chosen conceptual schema language is the Unified Modelling Language (UML). ISO TS 19103:2005 provides a profile of UML for use with geographic information. In addition, it provides guidelines on how UML should be used to create standardized geographic information and service models. ISO TS 19104:2008 is applicable to international communication in the field of geographic information. It provides the guidelines for collection and maintenance of terminology in the field of geographic information. It establishes criteria for selection of concepts to be included in other standards concerning geographic information, which are developed by V1.0 2013-01-15 Page 265 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/TC 211, specifies the structure of the terminological record, and describes the principles for definition writing. ISO TS 19104:2008 also lays down the guidelines for maintenance of a Terminology Repository. ISO 19106:2004 is intended to define the concept of a profile of the ISO geographic information standards developed by ISO/TC 211 and to provide guidance for the creation of such profiles. Only those components of specifications that meet the definition of a profile contained herein can be established and managed through the mechanisms described in this International Standard. These profiles can be standardized internationally using the ISO standardization process. This document also provides guidance for establishing, managing, and standardizing at the national level (or in some other forum). ISO 19107:2003 specifies conceptual schemas for describing the spatial characteristics of geographic features, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology up to three dimensions. It defines standard spatial operations for use in access, query, management, processing, and data exchange of geographic information for spatial (geometric and topological) objects of up to three topological dimensions embedded in coordinate spaces of up to three axes. ISO 19108:2002 defines concepts for describing temporal characteristics of geographic information. It depends upon existing information technology standards for the interchange of temporal information. It provides a basis for defining temporal feature attributes, feature operations, and feature associations, and for defining the temporal aspects of metadata about geographic information. Since this International Standard is concerned with the temporal characteristics of geographic information as they are abstracted from the real world, it emphasizes valid time rather than transaction time. ISO 19109:2005(E) defines rules for creating and documenting application schemas, including principles for the definition of features. Its scope includes the following: • conceptual modelling of features and their properties from a universe of discourse; • definition of application schemas; • use of the conceptual schema language for application schemas; • transition from the concepts in the conceptual model to the data types in the application schema; • integration of standardized schemas from other ISO geographic information standards with the application schema. The following are outside the scope: • choice of one particular conceptual schema language for application schemas; • definition of any particular application schema; • representation of feature types and their properties in a feature catalogue; • representation of metadata; • rules for mapping one application schema to another; • implementation of the application schema in a computer environment; • computer system and application software design; V1.0 2013-01-15 Page 266 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • programming. ISO 19110:2005 defines the methodology for cataloguing feature types and specifies how the classification of feature types is organized into a feature catalogue and presented to the users of a set of geographic data. ISO 19110:2005 is applicable to creating catalogues of feature types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard practice. ISO 19110:2005 applies to the cataloguing of feature types that are represented in digital form. Its principles can be extended to the cataloguing of other forms of geographic data. ISO 19110:2005 is applicable to the definition of geographic features at the type level. ISO 19110:2005 is not applicable to the representation of individual instances of each type and excludes spatial, temporal, and portrayal schemas as specified in ISO 19107, ISO 19108, and the future ISO 19117, respectively. It also excludes collection criteria for feature instances. ISO 19910:2005 may be used as a basis for defining the universe of discourse being modelled in a particular application, or to standardize general aspects of real world features being modelled in more than one application. ISO 19111:2007 defines the conceptual schema for the description of spatial referencing by coordinates, optionally extended to spatio-temporal referencing. It describes the minimum data required to define one-, two- and three-dimensional spatial coordinate reference systems with an extension to merged spatial-temporal reference systems. It allows additional descriptive information to be provided. It also describes the information required to change coordinates from one coordinate reference system to another. In ISO 19111:2007, a coordinate reference system does not change with time. For coordinate reference systems defined on moving platforms such as cars, ships, aircraft and spacecraft, the transformation to an Earth-fixed coordinate reference system can include a time element. ISO 19111:2007 is applicable to producers and users of geographic information. Although it is applicable to digital geographic data, its principles can be extended to many other forms of geographic data such as maps, charts and text documents. The schema described can be applied to the combination of horizontal position with a third non-spatial parameter which varies monotonically with height or depth. This extension to non-spatial data is beyond the scope of ISO 19111:2007 but can be implemented through profiles. ISO 19111-2:2009 specifies the conceptual schema for the description of spatial referencing using parametric values or functions. It applies the schema of ISO 19111 to combine a position referenced by coordinates with a parametric value to form a spatio-parametric coordinate reference system (CRS). The spatio-parametric CRS can optionally be extended to include time. The intended users of ISO 19111-2:2009 are producers and users of environmental information. Parameters which are attributes of spatial locations or features, but which are not involved in their spatial referencing, are not addressed by ISO 19111-2:2009. ISO 19912:2003 defines the conceptual schema for spatial references based on geographic identifiers. It establishes a general model for spatial referencing using geographic identifiers, defines the components of a spatial reference system and defines the essential components of a gazetteer. Spatial referencing by coordinates is not addressed in this document; however, a mechanism for recording complementary coordinate references is included. ISO 19912:2003 assists users in understanding the spatial references used in datasets. It enables gazetteers to be constructed in a consistent V1.0 2013-01-15 Page 267 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot manner and supports the development of other standards in the field of geographic information. It is applicable to digital geographic data, and its principles may be extended to other forms of geographic data such as maps, charts and textual documents. ISO 19113:2002 establishes the principles for describing the quality of geographic data and specifies components for reporting quality information. It also provides an approach to organizing information about data quality. ISO 19113:2002 is applicable to data producers providing quality information to describe and assess how well a dataset meets its mapping of the universe of discourse as specified in the product specification, formal or implied, and to data users attempting to determine whether or not specific geographic data is of sufficient quality for their particular application. This International Standard should be considered by organizations involved in data acquisition and purchase, in such a way that it makes it possible to fulfil the intentions of the product specification. It can additionally be used for defining application schemas and describing quality requirements. As well as being applicable to digital geographic data, the principles of ISO 19113:2002 can be extended to identify, collect and report the quality information for a geographic dataset, its principles can be extended and used to identify, collect and report quality information for a dataset series or smaller groupings of data that are a subset of a dataset. Although ISO 19113:2002 is applicable to digital geographic data, its principles can be extended to many other forms of geographic data such as maps, charts and textual documents. ISO 19113:2002 does not attempt to define a minimum acceptable level of quality for geographic data. ISO 19114:2003 provides a framework of procedures for determining and evaluating quality that is applicable to digital geographic datasets, consistent with the data quality principles defined in ISO 19113. It also establishes a framework for evaluating and reporting data quality results, either as part of data quality metadata only, or also as a quality evaluation report. ISO 19114:2003 is applicable to data producers when providing quality information on how well a dataset conforms to the product specification, and to data users attempting to determine whether or not the dataset contains data of sufficient quality to be fit for use in their particular applications. Although ISO 19114:2003 is applicable to all types of digital geographic data, its principles can be extended to many other forms of geographic data such as maps, charts and textual documents. ISO 19115:2003 defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. ISO 19115:2003 is applicable to: • the cataloguing of datasets, clearinghouse activities, and the full description of datasets; • geographic datasets, dataset series, and individual geographic features and feature properties. ISO 19115:2003 defines: • mandatory and conditional metadata sections, metadata entities, and metadata elements; • the minimum set of metadata required to serve the full range of metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data); V1.0 2013-01-15 Page 268 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • optional metadata elements - to allow for a more extensive standard description of geographic data, if required; a method for extending metadata to fit specialized needs. Though ISO 19115:2003 is applicable to digital data, its principles can be extended to many other forms of geographic data such as maps, charts, and textual documents as well as non-geographic data. ISO 19115-2:2009 extends the existing geographic metadata standard by defining the schema required for describing imagery and gridded data. It provides information about the properties of the measuring equipment used to acquire the data, the geometry of the measuring process employed by the equipment, and the production process used to digitize the raw data. This extension deals with metadata needed to describe the derivation of geographic information from raw data, including the properties of the measuring system, and the numerical methods and computational procedures used in the derivation. The metadata required to address coverage data in general is addressed sufficiently in the general part of ISO 19115. ISO 19116:2004 specifies the data structure and content of an interface that permits communication between position-providing device(s) and position-using device(s) so that the position-using device(s) can obtain and unambiguously interpret position information and determine whether the results meet the requirements of the use. A standardized interface of geographic information with position allows the integration of positional information from a variety of positioning technologies into a variety of geographic information applications, such as surveying, navigation and intelligent transportation systems. ISO 19116:2004 will benefit a wide range of applications for which positional information is important. ISO 19117:2012 specifies a conceptual schema for describing symbols, portrayal functions that map geospatial features to symbols, and the collection of symbols and portrayal functions into portrayal catalogues. This conceptual schema can be used in the design of portrayal systems. It allows feature data to be separate from portrayal data, permitting data to be portrayed in a dataset independent manner. ISO 19118:2011 specifies the requirements for defining encoding rules for use for the interchange of data that conform to the geographic information in the set of International Standards known as the “ISO 19100 series”. ISO 19118:2011 specifies requirements for creating encoding rules based on UML schemas, requirements for creating encoding services, and requirements for XML-based encoding rules for neutral interchange of data. ISO 19118:2011 does not specify any digital media, does not define any transfer services or transfer protocols, nor does it specify how to encode inline large images. ISO 19119:2005 identifies and defines the architecture patterns for service interfaces used for geographic information, defines its relationship to the Open Systems Environment model, presents a geographic services taxonomy and a list of example geographic services placed in the services taxonomy. It also prescribes how to create a platformneutral service specification, how to derive conformant platform-specific service specifications, and provides guidelines for the selection and specification of geographic services from both platform-neutral and platform-specific perspectives. ISO/TR 19122:2004 is applicable to the following aspects of the field of Geographic Information/Geomatics: V1.0 2013-01-15 Page 269 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • To develop a Type 3 report, which describes a system for the qualification and certification, by a central independent body, of personnel in the field of Geographic Information/Geomatics. • To define the boundaries between Geographic Information/ Geomatics and other related disciplines and professions. • To specify technologies and tasks pertaining to Geographic Information/Geomatics. • To establish skill sets and competency levels for technologists, professional staff and management in the field. • To research the relationship between this initiative and other similar certification processes performed by existing professional associations. • To develop a plan for the accreditation of candidate institutions and programs, for the certification of individuals in the workforce, and for collaboration with other professional bodies. ISO 19123:2005 defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension. Examples of coverages include rasters, triangulated irregular networks, point coverages and polygon coverages. Coverages are the prevailing data structures in a number of application areas, such as remote sensing, meteorology and mapping of bathymetry, elevation, soil and vegetation. ISO 19123:2005 defines the relationship between the domain of a coverage and an associated attribute range. The characteristics of the spatial domain are defined whereas the characteristics of the attribute range are not part of ISO 19123:2005. ISO 19125-1:2004 establishes a common architecture for geographic information and defines terms to use within the architecture. It also standardizes names and geometric definitions for Types for Geometry. ISO 19125-1:2004 does not place any requirements on how to define the Geometry Types in the internal schema nor does it place any requirements on when or how or who defines the Geometry Types. ISO 19125-1:2004 does not attempt to standardize and does not depend upon any part of the mechanism by which Types are added and maintained. ISO 19125-2:2004 specifies an SQL schema that supports storage, retrieval, query and update of simple geospatial feature collections via the SQL Call Level Interface (SQL/CLI) and establishes an architecture for the implementation of feature tables. This part of ISO 19125:2004 defines terms to use within the architecture. of geographic information and defines a simple feature profile of ISO 19107. In addition, this part of ISO 19125:2004 describes a set of SQL Geometry Types together with SQL functions on those types. The Geometry Types and Functions described represent a profile of ISO 13249-3. This part of ISO 19125:2004 standardizes the names and geometric definitions of the SQL Types for Geometry and the names, signatures and geometric definitions of the SQL Functions for Geometry. This part of ISO 19125:2004 does not attempt to standardize and does not depend upon any part of the mechanism by which Types are added and maintained in the SQL environment, including the following: V1.0 2013-01-15 Page 270 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • the syntax and functionality provided for defining types; • the syntax and functionality provided for defining SQL functions; • the physical storage of type instances in the database; • specific terminology used to refer to User Defined Types, for example, UDT. ISO 19123:2009 specifies a schema for feature concept dictionaries to be established and managed as registers. It does not specify schemas for feature catalogues or for the management of feature catalogues as registers. However, because feature catalogue are often derived from feature concept dictionaries, ISO 19123:2009 does specify a schema for a hierarchical register of feature concept dictionaries and feature catalogues. These registers are in accordance with ISO 19135. ISO TS 19127:2005 defines rules for the population and maintenance of registers of geodetic codes and parameters and identifies the data elements, in compliance with ISO 19135 and ISO 19111, required within these registers. Recommendations for the use of the registers, the legal aspects, the applicability to historic data, the completeness of the registers, and a mechanism for maintenance are specified by the registers themselves. ISO 19128:2005 specifies the behaviour of a service that produces spatially referenced maps dynamically from geographic information. It specifies operations to retrieve a description of the maps offered by a server, to retrieve a map, and to query a server about features displayed on a map. ISO 19128:2005 is applicable to pictorial renderings of maps in a graphical format; it is not applicable to retrieval of actual feature data or coverage data values. ISO/TS 19129:2009 defines the framework for imagery, gridded and coverage data. This framework defines a content model for the content type imagery and for other specific content types that can be represented as coverage data. These content models are represented as a set of generic UML patterns for application schemas. ISO/TS 19130:2010 identifies the information required to determine the relationship between the position of a remotely sensed pixel in image coordinates and its geoposition. It supports exploitation of remotely sensed images. It defines the metadata to be distributed with the image to enable user determination of geographic position from the observations. ISO/TS 19130:2010 specifies several ways in which information in support of geopositioning may be provided. 9. It may be provided as a sensor description with the associated physical and geometric information necessary to rigorously construct a Physical Sensor Model. For the case where precise geoposition information is needed, ISO/TS 19130:2010 identifies the mathematical formulae for rigorously constructing Physical Sensor Models that relate two-dimensional image space to three-dimensional ground space and the calculation of the associated propagated errors. ISO/TS 19130:2010 provides detailed information for three types of passive electro-optical/infrared (IR) sensors (frame, pushbroom and whiskbroom) and for an active microwave sensing system [Synthetic Aperture Radar (SAR)]. It provides a framework by which these sensor models can be extended to other sensor types. 10. It may be provided as a True Replacement Model, using functions whose coefficients are based on a Physical Sensor Model so that they provide information for precise geopositioning, including the calculation of errors, as precisely as the Physical V1.0 2013-01-15 Page 271 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Sensor Model they replace. 11. It may be provided as a Correspondence Model that provides a functional fitting based on observed relationships between the geopositions of a set of ground control points and their image coordinates. 12. It may be provided as a set of ground control points that can be used to develop a Correspondence Model or to refine a Physical Sensor Model or True Replacement Model. ISO/TS 19130:2010 does not specify either how users derive geoposition data or the format or content of the data the users generate. ISO 19131:2007 specifies requirements for the specification of geographic data products, based upon the concepts of other ISO 19100 International Standards. It also provides help in the creation of data product specifications, so that they are easily understood and fit for their intended purpose. ISO 19132:2007 defines a reference model and a conceptual framework for locationbased services (LBS), and describes the basic principles by which LBS applications may interoperate. This framework references or contains an ontology, a taxonomy, a set of design patterns and a core set of LBS service abstract specifications in UML. ISO 19132:2007 further specifies the framework's relationship to other frameworks, applications and services for geographic information and to client applications. ISO 19132:2007 addresses, for an LBS system, the first three basic viewpoints as defined in the Reference Model for Open Distributed Processing (RM-ODP, see ISO/IEC 10746-1). These viewpoints are the Enterprise Viewpoint – detailing the purpose, scope, and policies of the system; Information Viewpoint – detailing the semantics of information and processing within the system; Computational Viewpoint – detailing the functional decomposition of the system. The fourth and fifth viewpoints are addressed only in requirements or examples. These are the Engineering Viewpoint – detailing the infrastructure for distribution; Technology Viewpoint – detailing the technology for implementation; Reference models and frameworks can be defined at a variety of levels, from conceptual design to software documentation. ISO 19132:2007 defines the conceptual framework for and the type of applications included within LBS, establishes general principles for LBS for both mobile and fixed clients, specifies the interface for data access while roaming, defines the architectural relationship with other ISO geographic information standards, and identifies areas in which further standards for LBS are required. ISO 19132:2007 does not address rules by which LBS are developed, nor general principles for roaming agreements for mobile clients and tracking targets. ISO 19133:2005 describes the data types, and operations associated with those types, for the implementation of tracking and navigation services. It is designed to specify web services that can be made available to wireless devices through web-resident proxy applications, but is not restricted to that environment. ISO 19134:2006 specifies the data types and their associated operations for the implementation of multimodal location-based services for routing and navigation. It is designed to specify web services that may be made available to wireless devices through web-resident proxy applications, but is not limited to that environment. ISO 19135:2005 specifies procedures to be followed in establishing, maintaining and publishing registers of unique, unambiguous and permanent identifiers, and meanings that V1.0 2013-01-15 Page 272 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot are assigned to items of geographic information. In order to accomplish this purpose, ISO 19135:2005 specifies elements of information that are necessary to provide identification and meaning to the registered items and to manage the registration of these items. The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. ISO 19136:2007 defines the XML Schema syntax, mechanisms and conventions that: • provide an open, vendor-neutral framework for the description of geospatial application schemas for the transport and storage of geographic information in XML; • allow profiles that support proper subsets of GML framework descriptive capabilities; • support the description of geospatial application schemas for specialized domains and information communities; • enable the creation and maintenance of linked geographic application schemas and datasets; • support the storage and transport of application schemas and data sets; • increase the ability of organizations to share geographic application schemas and the information they describe. Implementers may decide to store geographic application schemas and information in GML, or they may decide to convert from some other storage format on demand and use GML only for schema and data transport. ISO 19137:2007 defines a core profile of the spatial schema specified in ISO 19107 that specifies, in accordance with ISO 19106, a minimal set of geometric elements necessary for the efficient creation of application schemata. It supports many of the spatial data formats and description languages already developed and in broad use within several nations or liaison organizations. ISO/TS 19138:2006 defines a set of data quality measures. These can be used when reporting data quality for the data quality subelements identified in ISO 19113. Multiple measures are defined for each data quality subelement, and the choice of which to use will depend on the type of data and its intended purpose. The data quality measures are structured so that they can be maintained in a register established in conformance with ISO 19135. ISO/TS 19138:2006 does not attempt to describe every possible data quality measure, only a set of commonly used ones. ISO/TS 19139:2007 defines Geographic MetaData XML (gmd) encoding, an XML Schema implementation derived from ISO 19115. ISO 19139-2:2012 defines Geographic Metadata for imagery and gridded data (gmi) encoding. This is an XML Schema implementation derived from ISO 19115-2. ISO 19141:2008 defines a method to describe the geometry of a feature that moves as a rigid body. Such movement has the following characteristics. • The feature moves within any domain composed of spatial objects as specified in ISO 19107. V1.0 2013-01-15 Page 273 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • The feature may move along a planned route, but it may deviate from the planned route. • Motion may be influenced by physical forces, such as orbital, gravitational, or inertial forces. • Motion of a feature may influence or be influenced by other features, for example: • The moving feature might follow a predefined route (e.g. road), perhaps part of a network, and might change routes at known points (e.g. bus stops, waypoints). • Two or more moving features may be “pulled” together or pushed apart (e.g. an airplane will be refuelled during flight, a predator detects and tracks a prey, refugee groups join forces). • Two or more moving features may be constrained to maintain a given spatial relationship for some period (e.g. tractor and trailer, convoy). ISO 19141:2008 does not address other types of change to the feature. Examples of changes that are not addressed include the following: • The deformation of features. • The succession of either features or their associations. • The change of non-spatial attributes of features. • The feature's geometric representation cannot be embedded in a geometric complex that contains the geometric representations of other features, since this would require the other features' representations to be updated as the feature moves. Because ISO 19141:2008 is concerned with the geometric description of feature movement, it does not specify a mechanism for describing feature motion in terms of geographic identifiers. This is done, in part, in ISO 19133. ISO 19142:2010 specifies the behaviour of a web feature service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parametrised query expressions. ISO 19143:2010 describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. These components are modular and intended to be used together or individually by other International Standards which reference ISO 19143:2010. ISO 19143:2010 defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. It also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow the following query pattern: • An abstract query element from which service specifications can subclass a concrete query element that implements a query operation that allows a client to specify a list of resource types, an optional projection clause, an optional selection clause, and an optional sorting clause to query a subset of resources that satisfy the selection clause. V1.0 2013-01-15 Page 274 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot This pattern is referred to as an ad hoc query pattern since the server in not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier. ISO 19143:2010 also describes an XML and KVP encoding of a system-neutral representation of a select clause. The XML representation is easily validated, parsed and transformed into a server-specific language required to retrieve or modify object instances stored in some persistent object store. ISO 19143:2010 defines the XML encoding for the following predicates: • A standard set of logical predicates: and, or and not. • A standard set of comparison predicates: equal to, not equal to, less than, less than or equal to, greater than, greater than or equal to, like, is null and between. • A standard set of spatial predicates: equal, disjoint, touches, within, overlaps, crosses, intersects, contains, within a specified distance, beyond a specified distance and BBOX. • A standard set of temporal predicates: after, before, begins, begun by, contains, during, ends, equals, meets, met by, overlaps and overlapped by. • A predicate to test whether the identifier of an object matches the specified value. ISO 19143:2010 defines the XML encoding of metadata that allows a service to declare which conformance classes, predicates, operators, operands and functions it supports. This metadata is referred to as Filter Capabilities. ISO 19144-1:2009 establishes the structure of a geographic information classification system, together with the mechanism for defining and registering the classifiers for such a system. It specifies the use of discrete coverages to represent the result of applying the classification system to a particular area and defines the technical structure of a register of classifiers in accordance with ISO 19135. ISO 19144-2:2012 specifies a Land Cover Meta Language (LCML) expressed as a UML metamodel that allows different land cover classification systems to be described based on the physiognomic aspects. ISO 19144-2:2012 also specifies the detailed structure of a register for the extension of LCML but does not specify the maintenance of the register. ISO 19144-2:2012 recognizes that there exist a number of land cover classification systems. It provides a common reference structure for the comparison and integration of data for any generic land cover classification system, but does not intend to replace those classification systems. ISO 19146:2010 defines a methodology for cross-mapping technical vocabularies that have been adopted by industry-specific geospatial communities. It also specifies an implementation of ISO 19135 for the registration of geographic information concepts for the purpose of integrating multiple domain-based vocabularies. ISO 19148:2012 specifies a conceptual schema for locations relative to a one-dimensional object as measurement along (and optionally offset from) that object. It defines a description of the data and operations required to use and support linear referencing. ISO 19148:2012 is applicable to transportation, utilities, location-based services and other applications which define locations relative to linear objects. ISO 19149:2011 defines an XML-based vocabulary or language to express rights for geographic information in order that digital licenses can be created for such information and related services. This language, GeoREL, is an extension of the rights expression V1.0 2013-01-15 Page 275 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot language in ISO/IEC 21000-5 and is to be used to compose digital licenses. Each digital license will unambiguously express those particular rights that the owners (or their agent) of a digital geographic resource extend to the holders of that license. The digital rights management system in which these licenses are used can then offer ex ante (before the fact) protection for all such resources. ISO/TS 19150-1:2012 defines the framework for semantic interoperability of geographic information. This framework defines a high level model of the components required to handle semantics in the ISO geographic information standards with the use of ontologies. ISO 19152:2012: • defines a reference Land Administration Domain Model (LADM) covering basic information-related components of land administration (including those over water and land, and elements above and below the surface of the earth); • provides an abstract, conceptual model with four packages related to parties (people and organizations); basic administrative units, rights, responsibilities, and restrictions (ownership rights); spatial units (parcels, and the legal space of buildings and utility networks); spatial sources (surveying), and spatial representations (geometry and topology); • provides terminology for land administration, based on various national and international systems, that is as simple as possible in order to be useful in practice. The terminology allows a shared description of different formal or informal practices and procedures in various jurisdictions; • provides a basis for national and regional profiles; and • enables the combining of land administration information from different sources in a coherent manner. ISO 19155:2012 specifies an architecture that defines a reference model with an encoding method for an identifier of a place. The concept of “place” within ISO 19155:2012 includes “places” not only in the real world but also those in the virtual world. These “places” are identified using either coordinate identifiers, geographic identifiers, or virtual world identifiers such as URI. In ISO 19155:2012, an identifier of a place is referred to as a Place Identifier (PI). The reference model defines a mechanism to match multiple Place Identifiers to the same place. In addition, a data structure and set of service interfaces are also defined in this reference model. ISO 19155:2012 is applicable to location based services, emergency management services and other application domains that require a common architecture, across specific domains, for the representation of place descriptions using coordinate, geographic, or virtual world identifiers. ISO 19156:2011 defines a conceptual schema for observations, 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. ISO 19156:2011 defines a common set of sampling feature types classified primarily by topological dimension, as well as samples for ex-situ observations. The schema includes relationships between sampling features (subsampling, derived samples). ISO 19156:2011 concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to V1.0 2013-01-15 Page 276 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot satisfy the interface specifications in the actual situation. ISO/TS 19158:2012 provides a framework for quality assurance specific to geographic information. It is based upon the quality principles and quality evaluation procedures of geographic information identified in ISO 19157 and the general quality management principles defined in ISO 9000. The framework defined in ISO/TS 19158:2012 enables a customer to satisfy itself that its suppliers, both internal and external, are capable of delivering geographic information to the required quality. Fundamental to the framework is the assurance of the supplier's ability to understand and meet the quality requirements. Through the quality assurance framework both the customer and the supplier are able to consider the quality required at the earliest opportunity in the production/update process. Principles and responsibilities of the relationship between the customer and the supplier that facilitate the framework are provided. The responsibility for the quality assessment procedure is shared between the customer and the supplier. ISO/TS 19158:2012 is applicable to customers and suppliers of all geographic information where the quality of the product may be impacted upon by the supplier's processes in any of the following scenarios: • 1) there is an agreement or legislation for the supply of data acquisition services, • 2) data acquisition services are being tendered for, and • 3) one or more suppliers exist in the supply chain. ISO/TS 19158:2012 is not applicable for the supply of legacy datasets or ?off the shelf' products where there is no further data production or update activity to manage. [Source: ISO] External links • http://en.wikipedia.org/w/index.php?title=ISO/TC_211&oldid=524328850 ISO 29481 Profile Reference Name ISO 29481 ISO 29481: Building information modelling – Information delivery manual Categories Terminologies and Semantics; Building Information Modelling; ISO ICS 91.010.01: Construction industry in general Abstract Building information modelling (BIM) is a process involving the generation and management of digital representations of physical and functional characteristics of a facility. The resulting building information models become shared knowledge resources to support decisionmaking about a facility from earliest conceptual stages, through design and construction, through its operational life and eventual demolition. [Source: Wikipedia] Current Version see Standard Parts below V1.0 2013-01-15 Page 277 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance As AAL technologies are integrated into existing buildings or new buildings, ISO 29481/ Building Information Modelling should be taken into account. Available from see Standard Parts below Standard Parts Standard ISO 29481-1:2010 ISO 29481-2:2012 Title Building information modelling – Information delivery manual – Part 1: Methodology and format Building information models – Information delivery manual – Part 2: Interaction framework Description ISO 29481-1:2010 specifies a methodology and format for the development of an information delivery manual (IDM). ISO 29481-1:2010 specifies a methodology that unites the flow of construction processes with the specification of the information required by this flow, a form in which the information should be specified, and an appropriate way to map and describe the information processes within a construction life cycle. ISO 29481-1:2010 is intended to facilitate interoperability between software applications used in the construction process, to promote digital collaboration between actors in the construction process and to provide a basis for accurate, reliable, repeatable and highquality information exchange. ISO 29481-2:2012 specifies a methodology and format for describing ?coordination acts' between actors in a building construction project during all life cycle stages. It therefore specifies • a methodology that describes an interaction framework, • an appropriate way to map responsibilities and interactions that provides a process context for information flow, • a format in which the interaction framework should be specified. ISO 29481-2:2012 is intended to facilitate interoperability between software applications used in the construction process, to promote digital collaboration between actors in the building construction process, and to provide a basis for accurate, reliable, repeatable, and high-quality information exchange. [Source: ISO] External links • http://en.wikipedia.org/w/index.php? title=Building_information_modelling&oldid=525557531 V1.0 2013-01-15 Page 278 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 5. Runtime Environments Note: Many Real-Time Operating Systems not covered here are described in the Wikipedia lists of List of RTOS. CORBA Profile Reference Name Categories ICS Abstract CORBA CORBA: Common Object Request Broker Architecture Runtime Environment The Common Object Request Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) that enables software components written in multiple computer languages and running on multiple computers to work together. Current Version Other editions AAL Relevance Popular runtime environment, may be used for AAL Available from http://www.omg.org/corba/ Description CORBA is the acronym for Common Object Request Broker Architecture, OMG's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks. Using the standard protocol IIOP, a CORBA-based program from any vendor, on almost any computer, operating system, programming language, and network, can interoperate with a CORBA-based program from the same or another vendor, on almost any other computer, operating system, programming language, and network. CORBA enables separate pieces of software written in different languages and running on different computers to work with each other like a single application or set of services. More specifically, CORBA is a mechanism in software for normalizing the method-call semantics between application objects residing either in the same address space (application) or remote address space (same host, or remote host on a network). Version 1.0 was released in October 1991. CORBA uses an interface definition language (IDL) to specify the interfaces which objects present to the outer world. CORBA then specifies a mapping from IDL to a specific implementation language like C++ or Java. Standard mappings exist for Ada, C, C++, C++11, Lisp, Ruby, Smalltalk, Java, COBOL, PL/Iand Python. There are also non-standard mappings for Perl, Visual Basic, Erlang, and Tcl implemented by object request brokers (ORBs) written for those languages. The CORBA specification dictates there shall be an ORB through which an application would interact with other objects. In practice, the application simply initializes the ORB, and accesses an internal Object Adapter, which maintains things like reference counting, object (and reference) instantiation policies, and object lifetime policies. The Object Adapter is used to register instances of the generated code classes. Generated code V1.0 2013-01-15 Page 279 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot classes are the result of compiling the user IDL code, which translates the high-level interface definition into an OS- and language-specific class base for use by the user application. This step is necessary in order to enforce CORBA semantics and provide a clean user process for interfacing with the CORBA infrastructure. Some IDL mappings are more difficult to use than others. For example, due to the nature of Java, the IDL-Java mapping is rather straightforward and makes usage of CORBA very simple in a Java application. This is also true of the IDL to Python mapping. The C++ mapping is notoriously difficult; the mapping requires the programmer to learn complex and confusing datatypes that predate the C++ Standard Template Library (STL). The C++11 mapping is very easy to use, it uses Standard Template Library (STL) heavily. Since the C language is not object-oriented, the IDL to C mapping requires a C programmer to manually emulate object-oriented features External links • http://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture • http://www.omg.org/gettingstarted/corbafaq.htm#VersionNumber .Net Profile Reference Name Categories ICS Abstract .Net .Net Runtime Environment 35.060: Languages used in information technology, The .NET Framework is a software framework developed by Microsoft that runs primarily on Microsoft Windows. It includes a large library and provides language interoperability (each language can use code written in other languages) across several programming languages Current Version 4.0.30319.1 Other editions AAL Relevance Popular runtime environment, may be used for AAL Available from see Standard Parts below Standard Parts Standard ISO/IEC 23271:2012 ISO/IEC TR 25438:2006 ECMA-335 ECMA-334 V1.0 Title Information technology – Common Language Infrastructure (CLI) Information technology – Common Language Infrastructure (CLI) – Technical Report: Common Generics ICommon Language Infrastructure (CLI) C# Language Specification 2013-01-15 Page 280 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description The .NET Framework is a technology that supports building and running the next generation of applications and XML Web services. The .NET Framework is designed to fulfil the following objectives: • To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. • To provide a code-execution environment that minimizes software deployment and versioning conflicts. • To provide a code-execution environment that promotes safe execution of code, including code created by an unknown or semi-trusted third party. • To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments. • To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. • To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. The .NET Framework consists of the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that promote security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable ASP.NET applications and XML Web services, both of which are discussed later in this topic. Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and isolated file storage. V1.0 2013-01-15 Page 281 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot DPWS Profile Reference Name Categories OASIS DPWS DPWS: Devices Profile for Web Services Communication Protocol, General Purpose Protocol, Control; Communication Protocol, Ad-hoc networks; Runtime Environment ICS 35.110 - Networking Abstract DPWS is a web-service protocol for communication between different devices. Current Version 1.1 Other editions AAL Relevance DPWS can be used to implement service calls between different components of an AAL system, partly implemented in resource-limited embedded devices Available from http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01 Description The Devices Profile for Web Services (DPWS) is also sometimes called Web Services for Devices (WSD). A PC or other device can detect DPWS-enabled devices on a network, then discover and invoke the Web service functionality each device provides. DPWS has been developed with implementation on resource-limited embedded devices in mind. In Web Services terms, a “profile” is a set of guidelines for how to use Web Services technologies for a given purpose. The Web Services standards allow implementers to choose from a variety of message representations, text encodings, transport protocols, and other options, some of which are not mutually interoperable. By constraining these decisions, profiles ensure that implementations conforming to the profile will work well together. DPWS provides the following functionality between compatible devices: • Discovering DPWS-capable devices on the network and the services they offer • Sending messages to DPWS-capable devices and receiving replies • Describing a Web service by providing a WSDL file • Interacting with a service using its description • Subscribing to and receiving events from a Web service Devices can be DPWS clients (invoking services on devices), servers (providing services), or both. External links • http://msdn.microsoft.com/en-us/library/dd170125.aspx • http://en.wikipedia.org/wiki/DPWS V1.0 2013-01-15 Page 282 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Linux Profile Reference Name Categories ICS Abstract Linux Linux Runtime Environment; Operating System Linux is a Unix-like computer operating system assembled under the model of free and open source software development and distribution Current Version Other editions AAL Relevance Popular runtime environment/ operating system, may be used for AAL Available from http://www.linux.com/ http://www.linuxfoundation.org/about Description Linux is, in simplest terms, an operating system. It is the software on a computer that enables applications and the computer operator to access the devices on the computer to perform desired functions. The operating system (OS) relays instructions from an application to, for instance, the computer's processor. The processor performs the instructed task, then sends the results back to the application via the operating system. There are currently several Linux distributions available for example: Ubuntu SUSE Linux Enterprise Red Hat Fedora Project (Red Hat free version) Debian - The Universal Operating System Android Linux Busybox http://www.ubuntu.com/ https://www.suse.com/ http://www.redhat.com/ http://fedoraproject.org/de/ http://www.debian.org/ http://www.android.com/ http://www.busybox.net/ External links • http://en.wikipedia.org/w/index.php?title=Linux&oldid=531771152 M2M Profile Reference Name Categories ICS Abstract V1.0 M2M M2M: Machine-to-Machine Runtime Environment Machine to Machine or M2M communications is a new business 2013-01-15 Page 283 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot concept, borne from the original telemetry technology, used for automatic transmission and measurement of data from remote sources by wire, radio or other means. Current Version Other editions AAL Relevance Popular runtime environment, may be used for AAL Available from Description Machine to machine (M2M) refers to technologies that allow both wireless and wired systems to communicate with other devices of the same ability. M2M uses a device (such as a sensor or meter) to capture an event (such as temperature, inventory level, etc.), which is relayed through a network (wireless, wired or hybrid) to an application (software program), that translates the captured event into meaningful information (for example, items need to be restocked). Such communication was originally accomplished by having a remote network of machines relay information back to a central hub for analysis, which would then be rerouted into a system like a personal computer. However, modern M2M communication has expanded beyond a one-to-one connection and changed into a system of networks that transmits data to personal appliances. The expansion of IP networks across the world has made it far easier for M2M communication to take place and has lessened the amount of power and time necessary for information to be communicated between machines. These networks also allow an array of new business opportunities and connections between consumers and producers in terms of the products being sold. External links • http://en.wikipedia.org/wiki/Machine_to_machine • http://www.mobilein.com/M2M.htm MHP Profile Reference Name Categories ICS Abstract V1.0 MHP MHP: Multimedia Home Platform Runtime environment The DVB Project works to develop, set and promote technical guidelines, standards and specifications to benefit and advance digital media markets world-wide. MHP (Developed by DVB Project) is an open middleware system standard for interactive digital television. The MHP enables the reception and execution of interactive, Java-based applications on a TV-set. Interactive TV applications can be delivered over the broadcast channel, together with audio and video streams. 2013-01-15 Page 284 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot These applications can be for example information services, games, interactive voting, e-mail, SMS or shopping. MHP applications can use an additional return channel that has to support IP Current Version Other editions AAL Relevance Popular runtime environment, may be used for AAL Available from http://www.mhp.org/ Description Multimedia Home Platform (DVB-MHP) is an open middleware system standard designed by the DVB project for interactive digital television. The MHP enables the reception and execution of interactive, Java-based applications on a TV-set. Interactive TV applications can be delivered over the broadcast channel, together with audio and video streams. These applications can be for example information services, games, interactive voting, email, SMS or shopping. MHP applications can use an additional return channel that has to support IP. The MHP specifies an extensive application execution environment for digital interactive TV, independent of the underlying, vendor-specific, hardware and software. This execution environment is based on the use of a Java virtual machine and the definition of generic APIs that provide access to the interactive digital TV terminal's typical resources and facilities. The interoperable MHP applications are running on top of these APIs. A so-called Navigator-application, which is part of the terminal software, allows the user the access to all MHP applications and other DVB services (like TV and radio). Sometimes Navigator can be also a Java program itself but that is not a requirement. The MHP is just a part of a family of specifications, which all base on the Globally Executable MHP (GEM)-Standard, which was defined to allow the worldwide adoption of MHP. External links • http://en.wikipedia.org/wiki/Multimedia_Home_Platform OSGi Profile Reference Name Categories ICS Abstract OSGi OSGi: OSGi Alliance (former Open Services Gateway initiative) Runtime Environment The OSGi Alliance, therefore, promotes widespread adoption of the OSGi technology to enable the componentization of applications into well-defined software modules and ensure remote management and interoperability of applications and services over a broad variety of devices Current Version Release 5 Other editions AAL Relevance A lot of AAL projects are based on OSGi therefore OSGi is relevant to V1.0 2013-01-15 Page 285 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL e.g. OSAmI, Universaal, Hearing at Home, Paaliativ, GAL Available from http://www.osgi.org Description The OSGi Alliance is a worldwide consortium of technology innovators that advances a proven and mature process to create open specifications that enable the modular assembly of software built with Java technology. Modularity reduces software complexity; OSGi is the best model to modularize Java. The OSGi technology facilitates the componentization of software modules and applications and assures remote management and interoperability of applications and services over a broad variety of devices. Building systems from in-house and off-the-shelf OSGi modules increases development productivity and makes them much easier to modify and evolve. The OSGi technology is delivered in many Fortune Global 100 company products and services and in diverse markets including enterprise, mobile, home, telematics and consumer. The alliance provides specifications, reference implementations, test suites and certification to foster a valuable cross-industry ecosystem. Member companies collaborate within an egalitarian, equitable and transparent environment and promote adoption of OSGi technology through business benefits, user experiences and forums. The alliance also promotes collaboration among important ecosystem players within and outside the OSGi Alliance in order to provide the market with innovative solutions based on open standards. Adoption of the component-based platform reduces time-to-market and development costs because it enables integration of pre-built and pre-tested modules. It reduces maintenance costs and provides aftermarket opportunities because networks are used to dynamically update or deliver services and applications in the field. Member company industries include leading service and content providers, infrastructure/network operators, utilities, enterprise software vendors, software developers, gateway suppliers, consumer electronics/device suppliers (wired and wireless) and research institutions. The OSGi Alliance is a non-profit corporation founded in March 1999. The MISSION of OSGi Alliance is to create a market for universal middleware. The OSGi Alliance, therefore, promotes widespread adoption of the OSGi technology to enable the componentization of applications into well-defined software modules and ensure remote management and interoperability of applications and services over a broad variety of devices. To realize this mission, the alliance provides specifications, reference implementations, test suites and certification to foster a valuable cross-industry ecosystem. Member companies collaborate within an egalitarian, equitable and transparent environment and promote adoption of OSGi technology through business benefits, user experiences and forums. External links • http://en.wikipedia.org/w/index.php?title=OSGi&oldid=532038712 UPnP Profile Reference Name V1.0 UPnP UPnP: Universal Plug and Play 2013-01-15 Page 286 of 490 AALIANCE2 Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot Communication Protocols; General Purpose; Control; Ad-hoc networks; Runtime Environment; ISO; IEC 35.200: Interface and interconnection equipment Universal Plug and Play (UPnP) is a set of networking protocols that allows networked devices, such as personal computers, printers, Internet gateways,Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment. 1.0 Help to create a network of interconnected devices ISO/IEC 29341-1:2011 Description ISO/IEC 29341-1:2011(E) Information technology – UPnP Device Architecture – Part 1: UPnP Device Architecture Version 1.0 Defines UPnP technology which describes an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, and PCs of all form factors. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces, or attached to the Internet. UPnP technology provides a distributed, open networking architecture that leverages TCP/IP and the Web technologies to enable seamless proximity networking in addition to control and data transfer among networked devices. The UPnP Device Architecture (UDA) is designed to support zeroconfiguration, “invisible” networking, and automatic discovery for a breadth of device categories from a wide range of vendors. A device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. Finally, a device can leave a network smoothly and automatically without leaving any unwanted state behind. The technologies leveraged in the UPnP architecture include Internet protocols such as IP, TCP, UDP, HTTP, and XML. Like the Internet, contracts are based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. This International Standard replaces ISO/IEC 29341-1, first edition, published in 2008, and constitutes a technical revision. External links • http://en.wikipedia.org/wiki/Upnp URC Profile Reference Name Categories ICS V1.0 URC URC: Universal Remote Console Runtime Environments; Software Infrastructure for AAL 35.240.20: IT applications in office work 2013-01-15 Page 287 of 490 AALIANCE2 Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot The Universal Remote Console (URC) standards developed by the V2 Technical Committee of ANSI/INCITS are focused on providing a standard mechanism for manufacturers to build a “User Interface Socket” into their products that would allow users to be able to control the products from other devices, including intelligent user agents. ISO/IEC 24752 Describes URC Standard see Standard Parts below ISO/IEC 24752 The URC standard addresses user needs for adaptable and usable devices and services in the context of Ambient Intelligence. This work should be of particular interest for: Manufacturers of networked devices and services for the home, the work place and the public; manufacturers of personal devices, cell phones and universal remote controls; communities for open networking platforms such as UPnP and Jini; researchers working on user interfaces for Ambient Intelligence; and organizations developing related standards. see Standard Parts below Standard Parts Standard ISO/IEC 24752-1:2008 ISO/ISO/IEC 24752-2:2008 ISO/IEC 24752-3:2008 ISO/IEC 24752-4:2008 ISO/IEC 24752-5:2008 Title Information technology – User interfaces – Universal remote console – Part 1: Framework Information technology – User interfaces – Universal remote console – Part 2: User interface socket description Information technology – User interfaces – Universal remote console – Part 3: Presentation template Information technology – User interfaces – Universal remote console – Part 4: Target description Information technology – User interfaces – Universal remote console – Part 5: Resource description Description Part 1 - Framework: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-1:2008 defines a framework of components that combine to enable remote user interfaces and remote control of network-accessible electronic devices and services through a universal remote console (URC). It provides an overview of the URC framework and its components. Part 2 - User interface socket description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-2:2008 describes user interface sockets, an abstract concept that describes the functionality and state of a device or service (target) in a machine interpretable manner. It defines an extensible markup language (XML) based language for V1.0 2013-01-15 Page 288 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot describing a user interface socket. The purpose of the user interface socket is to expose the relevant information about a target so that a user can perceive its state and operate it. This includes data presented to the user, variables that can be manipulated by the user, commands that the user can activate, and exceptions that the user is notified about. The user interface socket specification is applicable to the construction or customization of user interfaces. Annexes entail an XML schema definition and an example user interface socket description. Part 3 - Presentation template: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-3:2008 defines a language (presentation template markup language) for describing modality-independent user interface specifications, or presentation templates, associated with a user interface socket description as defined by ISO/IEC 24752-2. The purpose of a presentation template is to provide the universal remote console (URC) defined in ISO/IEC 24752-1 with hints as to how to build a usable and consistent user interface for a target device or service that is described in a user interface socket description as referenced above. The hints are of an abstract nature, and are intended to apply to any delivery context. These hints primarily provide information on structuring, grouping and linearisation of the socket elements. Elements within a presentation template can be referenced by atomic resources whose format is given by ISO/IEC 24752-5. Taken together, a presentation template, socket description, and appropriate atomic resources can be used to construct a user interface in any modality (e.g. visual, auditory, tactile, multimodal), through which a user can access and control a target. Part 4 - Target description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-4:2008 defines an eXtensible Markup Language (XML) based language for the description of targets and their sockets, as used within the universal remote console framework for discovery purposes. A document conforming to this language is a target description. Annexes propose an XML schema and an example of target descriptions. Part 5 - Resource description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-5:2008 defines a syntax for describing atomic resources, resource sheets, user interface implementation descriptions, resource services, and resource directories relevant to the user interface of a device or service (“target”). Annexes propose an example of atomic resource description, resource description framework (RDF) schema, and a sample resource sheet. External links • http://myurc.org V1.0 2013-01-15 Page 289 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot JRE Profile Reference Name Categories ICS Abstract JRE JRE: Java Runtime Environment Runtime Environment The JRE provides the libraries, Java virtual machine, and other components necessary for you to run applets and applications written in the Java programming language. This runtime environment can be redistributed with applications to make them free-standing. Current Version 1.7.0.9 Other editions OPEN JDK - http://openjdk.java.net/ AAL Relevance Popular runtime environment, may be used for AAL Available from http://www.java.com/ Description The Java Runtime Environment (JRE) provides the libraries, the Java Virtual Machine, and other components to run applets and applications written in the Java programming language. In addition, two key deployment technologies are part of the JRE: Java Plug-in, which enables applets to run in popular browsers; and Java Web Start, which deploys standalone applications over a network. This is the official Java Download from Sun Microsystems. External links • http://download.cnet.com/Java-Runtime-Environment-JRE/3000-2378_410009607.html?tag=sideBar;downloadLinks V1.0 2013-01-15 Page 290 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 6. Integration Profiles Continua Health Alliance Profile Reference Name Categories ICS Abstract Continua Health Alliance Continua Health Alliance Integration Profiles; Personal Health Records 35.240.80 IT applications in health care technology Continua is an organization that develops implementation guidelines for personal health applications Current Version 2012 Other editions AAL Relevance Plug-and-play interoperability for personal health applications Available from http://www.continuaalliance.org/products/design-guidelines.html Standard Parts Standard Guidelines 2011 Guidelines 2012 Title Continua Design Guidelines, Version 2011 Continua Design Guidelines, Version 2012 (available to members only) Description Continua Health Alliance is an international non-profit organization in which about 240 companies collaborate on developing specifications and a certification program for a plugand-play interoperability of applications in the field of “personal health”, more precisely: chronic disease management, ageing independently (which essentially means AAL), and health & physical fitness. Very much like the IHE Technical Frameworks, the Continua Design Guidelines are specifications based on existing standards that describe the IT systems involved in a specific use case and the interfaces between these IT systems, based on existing standards. Where possible, options are narrowed down as far as possible to achieve “plug and play” interoperability. The most important specifications on which the Continua Design Guidelines are based are ISO/IEEE 11073, Bluetooth (Health Device Profile and Low Energy), ZigBee, USB, HL7v2, the HL7 Personal Health Monitoring Report (PHMR) and IHE Cross-Enterprise Document Reliable Interchange (XDR). The Continua Design Guidelines are published annually. The predecessor version of the current specification is available freely for non-commercial purposes. Access to the current specification, and commercial use of it, requires membership in the Continua Health Alliance. Furthermore, Continua has established a product certification program that certifies the V1.0 2013-01-15 Page 291 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot interoperability of labelled products with other Continua-certified products. A list of certified products is available from the Continua website. External links • http://www.continuaalliance.org/index.html • http://www.continuaalliance.org/products/design-guidelines.html • http://www.continuaalliance.org/products/productshowcase.html • http://en.wikipedia.org/wiki/The_Continua_Health_Alliance Integrating the Healthcare Enterprise (IHE) Profile Reference Name Categories ICS Abstract IHE Integrating the Healthcare Enterprise (IHE) Integration Profiles 35.240.80 IT applications in health care technology IHE is an organization that develops standards for healthcare IT integration, several of which are relevant for AAL Current Version see below Other editions AAL Relevance Publishes communication protocols and document formats for exchanging medical information with healthcare enterprises Available from http://www.ihe.net/technical_framework Standard Parts See list of separate pages for relevant IHE Integration Profiles below. Description Integrating the Healthcare Enterprise (IHE) is an initiative supported by medical professional associations and medical device industry that was founded in 1997 with the goal of improving the standardization and harmonization of medical data exchange. IHE's work is based on a close collaboration of users and vendors: users (e.g. medical doctors of certain specialities) describe, which information is needed for their clinical workflows and which data must be captured, processed and stored at which point. The technical experts of the vendors involved in IHE develop specifications, based on these requirements, that describe how existing standards and publicly available specifications can be used to implement the user requirements. IHE was originally started in the field of Radiology, but it quickly turned out that the approach to modelling and solving IT integration problems can also be used for different medical specialities In addition to medical specialities such as ophthalmology, cardiology, laboratory medicine, pathology, pharmacology, radiology and radiation therapy there are also working groups on “horizontal” topics such as IT infrastructure, cross-enterprise care V1.0 2013-01-15 Page 292 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot chains, and quality assurance. Of relevance for the field of AAL are in particular the technical specifications of the “horizontal”, domain-independent working groups, since these in particular specify data structures and communication protocols for the exchange of medical information between hospitals and private practices and thus also offer a “blueprint” on how medical information from the home environment might be integrated with professional healthcare. For each domain, IHE yearly publishes a so-called “Technical Framework”. In this document, use cases (so-called “Integration Profiles”) are described along with the IT systems involved (“actors”) and the interactions or interfaces between these IT systems (“transactions”). Each transaction is based on an existing standard (or a combination of multiple standards), whereas IHE defines at a very fine-grained level which services, messages and options of the standards must be supported by IHE compliant implementations. This allows for a level of interoperability between conformant systems that comes very close to “plug and play” implementing complementary roles of one transaction. One real IT system can implement multiple actors and multiple integration profiles at the same time - this actually is the normal case for complex IT systems such as Hospital Information Systems. Several Integration Profiles developed and published by IHE are described on separate pages: • Communication Protocols for Electronic Health Records • IHE XDM: Cross-Enterprise Media Interchange • IHE XDR: Cross-Enterprise Document Reliable Interchange • IHE XDS: Cross-Enterprise Document Sharing • IHE XCA: Cross-Community Access • IHE XUA: Cross-Enterprise User Assertion • Persistent Document Formats for Medical Information • IHE XPHR: Exchange of Personal Health Record Content External links • http://www.ihe.net/ • http://www.ihe.net/technical_framework • http://en.wikipedia.org/wiki/Integrating_the_Healthcare_Enterprise V1.0 2013-01-15 Page 293 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 7. Software Infrastructure for AAL universAAL Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from universAAL Universal open platform and reference specification for ambient assisted living Software Infrastructure for AAL The universAAL platform will provide runtime support for the execution of AAL applications in accordance with a reference architecture, development support through core AAL services and an online developer depot of various development resources. n/a n/a The platform will be produced by a mixture of new development and consolidation of state-of-the-art results from existing initiatives. We recognise that this not only poses technical challenges but also raises issues of adoption and uptake. So work on establishing and running a sustainable community will achieve attention right from the start, with promotion of existing results gradually evolving into promotion of the universAAL platform, as it develops into one consolidated, validated and standardised European open AAL platform. universAAL Developer Depot Description The potential benefits of Ambient Assisted Living (AAL) solutions are already clearly recognised, and societal trends indicate that they will be attractive to a large and increasing number of people. But uptake of such solutions has so far been limited. universAAL aims to reduce barriers to adoption and to promote the development and widespread uptake of innovative AAL solutions. It will benefit end-users (i.e. elderly people and people with disabilities, their carers and family members) by making new solutions affordable, simple to configure, personalise and deploy. It will benefit solution providers by making it easier and cheaper to create innovative new AAL services or adapt existing ones using a compositional approach based on existing components, services and external systems. Our vision is that it should be as simple for users to download and setup AAL services as it is to download and install software applications on a modern operating system. universAAL will establish a store providing plug-and-play AAL applications and services that support multiple execution platforms and can be deployed to various devices and users. Finally the allocation of local human resources is also supported in the store. universAAL aims to produce an open platform that provides a standardized approach V1.0 2013-01-15 Page 294 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot making it technically feasible and economically viable to develop AAL solutions. The platform will be produced by a mixture of new development and consolidation of state ‐of ‐ the art results from existing initiatives. Work on establishing and running a sustainable community will receive attention right from the start, with promotion of existing results gradually evolving into promotion of the universAAL platform, as it develops into one consolidated, validated and standardized European open AAL platform. [Source: http://www.universaal.org/en/about/project-description] External links • universAAL homepage 7.1. Agent-based Systems Galaxy Communicator Profile Reference Name Categories ICS Abstract Galaxy Communicator Galaxy Communicator Software Infrastructure for AAL; Agent-based Systems Galaxy Communicator is an open source architecture for constructing dialogue systems. Current Version Version 4.0 (2004-09) Other editions AAL Relevance Development for dialogue systems Available from http://communicator.sourceforge.net/index.shtml Description Galaxy Communicator is an open source architecture for constructing dialogue systems. Its plug-and-play approach enables developers to combine architecture-compliant commercial software and cutting edge research components. Galaxy Communicator was funded by the Defence Advanced Research Projects Agency (DARPA) of the United States Government. The DARPA Communicator program was designed to support the creation of speech-enabled interfaces that scale gracefully across modalities, from speech-only to interfaces that include graphics, maps, pointing and gesture. Although the DARPA Communicator program has concluded, the open source software and documentation are still available on this website. External links • Galaxy Communicator Website V1.0 2013-01-15 Page 295 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot INCA Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from INCA INCA: An Infrastructure for Capture & Access Supporting the Generation, Preservation and Use of Memories from Everyday Life Software Infrastructure for AAL; Agent-based Systems; Research approach This dissertation presents a set of abstractions for a conceptual framework and a focused design process that encourages designers to decompose the design of capture and access applications into a set of concerns that will be easier to develop and to manage. In addition, an implementation of the framework called the INCA Toolkit is discussed, along with a number of capture and access applications that have been built with it. These applications illustrate how the toolkit is used in practice and supports explorations of the capture and access design space. Research approach As AAL scenarios may include memory function this approach may become interesting for future developments. http://smartech.gatech.edu/xmlui/bitstream/handle/1853/7167/truong_k hai_n_200508_phd.pdf?sequence=1 (dissertation) Description Peoples daily lives and experiences often contain memories and information that they may want to recall again at a later time. Human memory, however, has its limitations and many times it alone may not be sufficient. People sometimes have difficulty recalling salient information and can forget important details over time. To complement what they can remember naturally, people must expend much time and manual effort to record desired content from their lives for future retrieval. Unfortunately, manual methods for capturing information are far from ideal. Over the years, ubiquitous computing researchers have constructed devices and applications to support the automated capture of live experiences and access to those records. At Georgia Tech, we have also investigated the benefits of automated capture and access in over half a dozen projects since 1995. As we encountered challenges in developing these systems, we began to understand how the difficulty of building capture and access systems can prevent exploration of the hard issues intertwined with understanding how capture impacts our everyday lives. These challenges illustrate the need for support structures in building this class of ubiquitous computing systems. This dissertation presents a set of abstractions for a conceptual framework and a focused design process that encourages designers to decompose the design of capture and access applications into a set of concerns that will be easier to develop and to manage. In addition, an implementation of the framework called the INCA Toolkit is discussed, along with a number of capture and access applications that have been built with it. These applications illustrate how the toolkit is used in practice and V1.0 2013-01-15 Page 296 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot supports explorations of the capture and access design space. External links • Website (Data base entry) • Dissertation (PDF) Jaspis Profile Reference Name Categories Jaspis Jaspis: A Spoken Dialogue Architecture and its Applications Software Infrastructure for AAL; Agent-based Systems; Research approach ICS Abstract This dissertation introduces the Jaspis speech application architecture that has been designed to support adaptive and flexible humancomputer interaction techniques. Current Version Research approach Other editions AAL Relevance As AAL scenarios may include speech function this approach may become interesting for future developments. Available from http://wwwhome.cs.utwente.nl/~schooten/vidiam/papersindexed/turunen04jaspis.pdf (dissertation) Description This dissertation introduces the Jaspis speech application architecture that has been designed to support adaptive and flexible human-computer interaction techniques. This work also presents several applications constructed on the Jaspis architecture. Two multilingual e-mail applications, and two timetable applications are presented to provide concrete examples. External links • Dissertation about Jaspis (PDF) OAA Profile Reference Name Categories ICS V1.0 OAA OAA: Open Agent Architecture Software Infrastructure for AAL; Agent-based Systems; - 2013-01-15 Page 297 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract A framework for integrating a community of heterogeneous software agents in a distributed environment. Current Version 2.3.2 (2007-06) Other editions AAL Relevance As AAL systems may include multiple agents with different backgrounds these architecture may be useful. Available from Description Distributed Agent technology can be thought of as the next step in the evolution of programming methodologies. In the beginning, there were machine and assembly languages. These evolved into higher level programming languages able to break apart programming steps into subroutines. A next generalization allowed programmers to group collections of subroutines into libraries or modules. A subsequent innovation added the notion of object orientation: data and routines could be grouped into a single object, which further encapsulated the internals of the routines and increased modularity and reuse. Distributed Object technologies, such as CORBA or DCOM, then broke the rule that every object must reside on the local machine; now object libraries could post services through a broker, and the objects themselves could even be written in different programming languages, as long as they used the same Interface Definition Language. So, what can Distributed Agents possibly add to the Distributed Object paradigm? With distributed objects, even though objects may run on different platforms, applications generally form a single monolithic entity of tightly-bound objects, with hand-coded calls to known methods of pre-existing objects. In a distributed agent framework, we conceptualize a dynamic community of agents, where multiple agents contribute services to the community. When external services or information are required by a given agent, instead of calling a known subroutine or asking a specific agent to perform a task, the agent submits a high-level expression describing the needs and attributes of the request to a specialized Facilitator agent. The Facilitator agent will make decisions about which agents are available and capable of handling subparts of the request, and will manage all agent interactions required to handle the complex query. The advantage? Such a distributed agent architecture allows the construction of systems that are more flexible and adaptable than distributed object frameworks. Individual agents can be dynamically added to the community, extending the functionality that the agent community can provide as a whole. The agent system is also able to adapt to available resources in a way that hardcoded distributed objects systems can't. In the context of the Open Agent Architecture (TM) (OAA®), we are focused on building distributed communities of agents, where agent is defined as any software process that meets the conventions of the OAA society. An agent satisfies this requirement by registering the services it can provide in an acceptable form, by being able to speak the Interagent Communication Language (ICL), and by sharing functionality common to all OAA agents, such as the ability to install triggers, manage data in certain ways, etc. In our community of agents, we are able to include, and make use of, each of the different types of agents mentioned above. Characteristics: V1.0 2013-01-15 Page 298 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Open: agents can be created in multiple programming languages and interface with existing legacy systems. • Extensible: agents can be added or replaced individually at runtime. • Distributed: agents can be spread across any network-enabled computers. • Parallel: agents can cooperate or compete on tasks in parallel. • Mobile: lightweight user interfaces can run on handheld PDA's or in a web browser using Java or HTML and most applications can be run through a telephone-only interface. • Multimodal: When communicating with agents, handwriting, speech, pen gestures and direct manipulation (GUIs) can be combined in a natural way. External links • OAA Webpage 7.2. Service Oriented Architectures Amigo Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from Amigo Amigo: Ambient Intelligence for the networked home environment Software Infrastructure for AAL; Service-Oriented Architectures The aim of Amigo is to increase the awareness for problems concerning ambient intelligence and networked home environments. As AAL scenarios include ambient intelligence in domestic environment Amigo address relevant topics. - Description Home networking has already emerged in specific applications such as PC to PC communication and home entertainment systems, but its ability to really change people’s lives is still dogged by complex installation procedures, the lack of interoperability between different manufacturer’s equipment and the absence of compelling user services. By focusing on solving these key issues, the Amigo project aims to overcome the obstacles to widespread acceptance of this new technology. The project will develop open, standardized, interoperable middleware and attractive user services, thus improving enduser usability and attractiveness. The project will show the end-user usability and attractiveness of such a home system by creating and demonstrating prototype applications improving everyday life, addressing all vital user aspects: home care and V1.0 2013-01-15 Page 299 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot safety, home information and entertainment, and extension of the home environment by means of ambience sharing for advanced personal communication. The Amigo project will further support interoperability between equipment and services within the networked home environment by using standard technology when possible and by making the basic middleware (components and infrastructure) and basic user services available as open source software together with architectural rules for everyone to use. External links • http://www.hitech-projects.com/euprojects/amigo/project_information.htm LinkSmart Profile Reference Name Categories ICS Abstract LinkSmart LinkSmart - Text-linking Optimization Solution Software Infrastructure for AAL; Service-Oriented Architectures LinkSmart is a middleware that allows developers to incorporate heterogeneous physical devices into their applications through easy-touse web services for controlling any device. It was developed within the Hydra EU project for Networked Embedded Systems. Current Version Other editions AAL Relevance As AAL scenarios include physical devices LinkSmart makes them accessible over web services. Available from http://sourceforge.net/projects/linksmart/ Description The Hydra middleware allows developers to incorporate heterogeneous physical devices into their applications by offering easy-to-use web service interfaces for controlling any type of physical device irrespective of its network technology such as Bluetooth, RF, ZigBee, RFID, WiFi, etc. Hydra incorporates means for Device and Service Discovery, Semantic Model Driven Architecture, P2P communication, and Diagnostics. Hydra enabled devices and services can be secure and trustworthy through distributed security and social trust components of the middleware. [source: http://www.hydramiddleware.eu/] External links • http://www.hydramiddleware.eu/ V1.0 2013-01-15 Page 300 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot SOAP Profile Reference Name Categories ICS Abstract SOAP SOAP: Simple Object Access Protocol Software Infrastructure for AAL; Service-Oriented Architectures; W3C SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) for its message format, and usually relies on other Application Layer protocols, most notably Hypertext Transfer Protocol (HTTP) and Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission. Current Version 1.2 (2004-06) Other editions AAL Relevance As AAL scenarios may include web services SOAP is a relevant protocol. Available from http://www.w3.org/TR/soap/ Description SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built. This XML based protocol consists of three parts: an envelope, which defines what is in the message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing procedure calls and responses. SOAP has three major characteristics: • Extensibility (security and WS-routing are among the extensions under development), • Neutrality (SOAP can be used over any transport protocol such as HTTP, SMTP, TCP, or JMS) and • Independence (SOAP allows for any programming model). SOAP was designed as an object-access protocol in 1998 by Dave Winer, Don Box, Bob Atkinson, and Mohsen Al-Ghosein for Microsoft, where Atkinson and Al-Ghosein were working at the time. The SOAP specification is currently maintained by the XML Protocol Working Group of the World Wide Web Consortium. SOAP originally stood for 'Simple Object Access Protocol' but this acronym was dropped with Version 1.2 of the standard. Version 1.2 became a W3C recommendation on June 24, 2003. The acronym is sometimes confused with SOA, which stands for Service-oriented architecture, but the acronyms are unrelated. After SOAP was first introduced, it became the underlying layer of a more complex set of Web Services, based on Web Services Description Language (WSDL) and Universal Description Discovery and Integration (UDDI). These services, especially UDDI, have V1.0 2013-01-15 Page 301 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot proved to be of far less interest, but an appreciation of them gives a more complete understanding of the expected role of SOAP compared to how web services have actually evolved. External links • http://www.w3.org/TR/soap12/ • http://en.wikipedia.org/w/index.php?title=SOAP&oldid=532133329 WS-* Profile Reference Name Categories ICS Abstract WS-* WS-* Web Services Software Infrastructure for AAL; Service-Oriented Architectures; W3C This entry provides an overview of standards for Web services. A Web service is a method of communication between two electronic devices over the World Wide Web. A Web service is a software function provided at a network address over the web or the cloud, it is a service that is “always on” as in the concept of utility computing. Current Version not applicable Other editions AAL Relevance As AAL scenarios may include web services this standard is relevant. Available from http://www.w3.org/TR/ws-arch/ Standard Parts • WS-Addressing • WS-Agreement • WS-BPEL4People (Extension of WS-BPEL) • WS-Business Process Execution Language (WS-BPEL) • WS-Choreography Description Language (WS-CDL) • WS-Choreography Interface (WSCI) • WS-Coordination (WS-C) • WS-Atomic Transaction (WS-AT) • WS-Business Activity • WS-Transaction (WS-TX) • WS-Discovery • WS-Distributed Management (WSDM) V1.0 2013-01-15 Page 302 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Management Of Web Services (MOWS) • Management Using Web Services (MUWS) • WS-Enumeration • WS-Federation • WS-Federation Active Requestor Profile • WS-Federation Passive Requestor Profile • WS-Flow Language (WSFL) • WS-Fragment (based on WS-Transfer) • WS-HumanTask (Assistance for WS-BPEL4People) • WS-Inspection • WS-Notification • WS-Base Notification • WS-Brokered Notification • WS-Topics • WS-Policy • WS-Policy Assertions • WS-Policy Attachment • WS-Referral • WS-Reliability • WS-Reliable Messaging (WSRM) • WS-Reliable Messaging Policy Assertion • WS-Resource Framework (WSRF) • WS-BaseFaults • WS-Resource • WS-ResourceLifetime • WS-ResourceProperties • WS-ServiceGroup • WS-Routing Description The W3C defines a “Web service” as “a software system designed to support interoperable machine-to-machine interaction over a network”. It has an interface described in a machine-processable format (specifically Web Services Description Language, known by the acronym WSDL). Other systems interact with the Web service in V1.0 2013-01-15 Page 303 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.”[1] The W3C also states, “We can identify two major classes of Web services, RESTcompliant Web services, in which the primary purpose of the service is to manipulate XML representations of Web resources using a uniform set of “stateless” operations; and arbitrary Web services, in which the service may expose an arbitrary set of operations.”[ External links • http://www.w3.org/2002/ws/ • http://en.wikipedia.org/w/index.php? title=List_of_web_service_specifications&oldid=530791948 7.3. Event Driven Architectures EMBASSI Profile Reference Name Categories EMBASSI EMBASSI: Elektronische Multimediale Bedien- und Service-Assistenz Software Infrastructure for AAL; Event Driven Architectures; Research approach ICS Abstract EMBASSI developed an intelligent assistance architecture to ensure a natural and intuitive control of electronic devices of different standards and from different vendors. Current Version not applicable Other editions AAL Relevance As AAL scenarios include electronic devices for assisting purposes this architecture approach could be useful. Available from Description The project EMBASSI – supported and co-funded by the German Ministry of Research – deals with new and alternative forms of on-line assistance for the users of everyday technology, as present in private homes, cars, and in public places. It developed an intelligent assistance architecture to ensure a natural and intuitive control of electronic devices of different standards and from different vendors with a special emphasis on usability for the handicapped users. Several smaller companies from the market of assistive technology for disabled consumers have joined this working group. Together, we aim at a technology providing potentially global access to the user interfaces of every interactive machine operated in the public, home or car. To achieve this very ambitious goal, we are working on the definition of a standard user interaction language that shall enable communication between the locally fixed terminal systems and a variety of handV1.0 2013-01-15 Page 304 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot held, personally configured control devices. External links • http://www.embassi.de (in German) PERSONA Profile Reference Name Categories PERSONA PERSONA: Perceptive spaces promoting independent ageing Software Infrastructure for AAL; Event Driven Architectures; Research approach ICS Abstract PERSONA as an integrated European Project developed a scalable open standard technological platform to build a broad range of AAL Services, to demonstrate and test the concept in real life implementations, assessing their social impact and establishing the initial business strategy for future deployment of the proposed technologies and services. Within the project the AAL-Spaces cover the body, home, neighbourhood and village. The goal was to empower elderly people to feel included, secure, protected and supported, by developing Ambient Assisted Living products and services for the achievement of more autonomy and quality in their lives. Current Version not applicable Other editions AAL Relevance PERSONA offers definitions and evaluations of typical scenarios and activities of daily life for elderly and / or handicapped persons which may occur in AAL scenarios. Available from Description The aim of the PERSONA project is to further the development of AAL products and services that are affordable, easy to use and commercially viable. Crucially, the project partners are developing an integrated technological platform that seamlessly links up the different products and services. Furthermore, the team is working on certain hardware developments, such as intelligent textiles for use in devices that interact with the users, short-range communication networks to link up sensors and systems, and an indoor localisation system. External links • http://www.persona.eu V1.0 2013-01-15 Page 305 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 7.4. Universal Remote Console (URC) URC Profile Reference Name Categories ICS Abstract URC URC: Universal Remote Console Runtime Environments; Software Infrastructure for AAL 35.240.20: IT applications in office work The Universal Remote Console (URC) standards developed by the V2 Technical Committee of ANSI/INCITS are focused on providing a standard mechanism for manufacturers to build a “User Interface Socket” into their products that would allow users to be able to control the products from other devices, including intelligent user agents. ISO/IEC 24752 Describes URC Standard Current Version see Standard Parts below Other editions ISO/IEC 24752 AAL Relevance The URC standard addresses user needs for adaptable and usable devices and services in the context of Ambient Intelligence. This work should be of particular interest for: Manufacturers of networked devices and services for the home, the work place and the public; manufacturers of personal devices, cell phones and universal remote controls; communities for open networking platforms such as UPnP and Jini; researchers working on user interfaces for Ambient Intelligence; and organizations developing related standards. Available from see Standard Parts below Standard Parts Standard ISO/IEC 24752-1:2008 ISO/ISO/IEC 24752-2:2008 ISO/IEC 24752-3:2008 ISO/IEC 24752-4:2008 ISO/IEC 24752-5:2008 Title Information technology – User interfaces – Universal remote console – Part 1: Framework Information technology – User interfaces – Universal remote console – Part 2: User interface socket description Information technology – User interfaces – Universal remote console – Part 3: Presentation template Information technology – User interfaces – Universal remote console – Part 4: Target description Information technology – User interfaces – Universal remote console – Part 5: Resource description Description Part 1 - Framework: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. V1.0 2013-01-15 Page 306 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 24752-1:2008 defines a framework of components that combine to enable remote user interfaces and remote control of network-accessible electronic devices and services through a universal remote console (URC). It provides an overview of the URC framework and its components. Part 2 - User interface socket description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-2:2008 describes user interface sockets, an abstract concept that describes the functionality and state of a device or service (target) in a machine interpretable manner. It defines an extensible markup language (XML) based language for describing a user interface socket. The purpose of the user interface socket is to expose the relevant information about a target so that a user can perceive its state and operate it. This includes data presented to the user, variables that can be manipulated by the user, commands that the user can activate, and exceptions that the user is notified about. The user interface socket specification is applicable to the construction or customization of user interfaces. Annexes entail an XML schema definition and an example user interface socket description. Part 3 - Presentation template: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-3:2008 defines a language (presentation template markup language) for describing modality-independent user interface specifications, or presentation templates, associated with a user interface socket description as defined by ISO/IEC 24752-2. The purpose of a presentation template is to provide the universal remote console (URC) defined in ISO/IEC 24752-1 with hints as to how to build a usable and consistent user interface for a target device or service that is described in a user interface socket description as referenced above. The hints are of an abstract nature, and are intended to apply to any delivery context. These hints primarily provide information on structuring, grouping and linearisation of the socket elements. Elements within a presentation template can be referenced by atomic resources whose format is given by ISO/IEC 24752-5. Taken together, a presentation template, socket description, and appropriate atomic resources can be used to construct a user interface in any modality (e.g. visual, auditory, tactile, multimodal), through which a user can access and control a target. Part 4 - Target description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. ISO/IEC 24752-4:2008 defines an eXtensible Markup Language (XML) based language for the description of targets and their sockets, as used within the universal remote console framework for discovery purposes. A document conforming to this language is a target description. Annexes propose an XML schema and an example of target descriptions. Part 5 - Resource description: ISO/IEC 24752 facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. V1.0 2013-01-15 Page 307 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 24752-5:2008 defines a syntax for describing atomic resources, resource sheets, user interface implementation descriptions, resource services, and resource directories relevant to the user interface of a device or service (“target”). Annexes propose an example of atomic resource description, resource description framework (RDF) schema, and a sample resource sheet. External links • http://myurc.org V1.0 2013-01-15 Page 308 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 8. Personal Health Records CEN/TR 15300 Profile Reference Name CEN/TR 15300 CEN/TR 15300: Health informatics - Framework for formal modelling of healthcare security policies Categories Health Informatics; Personal Health Records; Data protection specifications ICS 35.240.80 : IT applications in health care technology Abstract This CEN Technical report specifies the starting point for working on some formalising tools that could be used by the healthcare actors to express, compare and validate local and/or network security policies Current Version CEN/TR 15300:2007 Other editions AAL Relevance Healthcare security policies may play a role in medical AAL applications. Available from http://www.cen.eu Description This CEN Technical report specifies the starting point for working on some formalising tools that could be used by the healthcare actors to express, compare and validate local and/or network security policies. Defining and validating a correct security policy encompass different activities such as expressing correctly (i.e. without any ambiguity), formulating correctly (i.e. without any misinterpretation) and proving the correctness (i.e. without known failures or major lack) of the [to be formally modelled] security policy. This CEN Technical report does NOT intend at all to specify a UNIQUE or UNIVERSAL formal model that need to be used by the European healthcare community: it only indicates, as a first working step, some ways that could be followed to help that healthcare community to correctly and fruitfully manipulate the security policy concept(s) and the formal modelling techniques. This CEN Technical report does NOT intend to indicate an EXHAUSTIVE spectrum of all the published formal security policy models: it only gives a readable and understandable flavour of the most well-known formal models and also of the [maybe] most interesting ones from the healthcare activity and needs point of view. [Source: lsd.it] External links • http://www.lsd.lt/standards/catalog.php?ics=0&pid=605687 V1.0 2013-01-15 Page 309 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot CEN/TR 15640 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from CEN/TR 15640 CEN/TR 15640: Health informatics - Measures for ensuring the patient safety of health software Health Informatics; Personal Health Records 35.240.80: IT applications in health care technology CEN/TR 15640 considers the control measures required to ensure patient safety in respect to health software products. CEN/TR 15640:2007 This standard is relevant to AAL because it regards the safety of AAL products. http://shop.bsigroup.com/ProductDetail/?pid=000000000030149192 Description PD CEN/TR 15640 considers the control measures required to ensure patient safety in respect to health software products. PD CEN/TR 15640 is a document that aims to identify what standards might best be used or created, and their nature, if health software products were to be regulated or controlled in some other formal or informal or voluntary manner whether national, regional or local. However it is not the purpose of this document to recommend whether or not health software products should be regulated. This document applies to any health software product whether or not it is placed on the market and whether or not it is for sale or free of charge. It is addressed to manufacturers of health software products. The scope is intended to cover health software products which are not, in practice, covered by medical device regulations, and PD CEN/TR 15640 considers this matter in detail. PD CEN/TR 15640 acknowledges that, on the boundary, there are health software products that are encompassed by medical device regulations in some countries but not in others and that some definitions of medical devices may appear to cover health software products in general but in practice do not. [Source: BSI shop] The safety of medicines and of medical devices is ensured in many countries through a variety of legal and administrative measures. In the European Union it is subject to several EU directives. These measures are often backed by a range of safety related standards from a number of sources, both national and international, including the European Standards Organisation (CEN), the International Standards Organisation (ISO) and the International Electrotechnical Committee (IEC). Some software such as that necessary for the proper application or functioning of a medical device is often encompassed by these legislative controls. However other software applied to health of a stand-alone nature is not usually covered or is encompassed in a less than clear manner. This document is V1.0 2013-01-15 Page 310 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot concerned with software applied to health excluding that which is encompassed by medical device controls. A necessary precursor for determining and implementing appropriate design and production controls to minimise risks to patients from product malfunction or inadequate performance, is a clear understanding of the hazards which a product might present to patients if malfunction or an unintended event should occur, and the likelihood of such a malfunction or event causing harm to the patient. Additionally if guidance is to be given to designers and producers of health software products as to design and production control (and corresponding standards produced) then it will need to be recognised that the controls necessary for products presenting low risks will not be the same as for those presenting high risks. Controls need to match the level of risk which a product might present to a patient. For these purposes many standards, legislation and specifications dealing with control of risks in design and production, group products in to a limited number of classes or types according to the risk they might present. Controls are then tailored to the class or type. This document follows that philosophy. There is a wide range of controls which might be exerted on the design, development, production, distribution, installation, up-grading/version control/up-dating of a health software product etc. This document starts with considering how those controls are applied to medical devices and offers practical solutions how to adapt them to health software products. [source: standard document] External links http://shop.bsigroup.com/ProductDetail/?pid=000000000030149192 CEN/TS 15260 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from V1.0 CEN/TS 15260 CEN/TS 15260: Health informatics - Classification of safety risks from health informatics products Health Informatics; Personal Health Records; Quality and risk management of medical devices 35.240.80: IT applications in health care technology CEN/TS 15260 is concerned with software applied to health which is not encompassed by EU Directives covering medical devices. (from Introduction of the standard, see external link) CEN/TS 15260:2006 This standard may be relevant to AAL because it regards a classification of risks that may affect the users of AAL systems http://shop.bsigroup.com/ProductDetail/?pid=000000000030124364 2013-01-15 Page 311 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description A necessary precursor for determining and implementing appropriate design and production controls to minimise risks to patients from product malfunction or inadequate performance, is a clear understanding of the hazards which a product might present to patients if malfunction or an unintended event should occur and the likelihood of such a malfunction or event causing harm to the patient. Additionally if guidance is to be given to designers and producers of health informatics products as to design and production control (and corresponding standards produced) then it will need to be recognised that the controls necessary for products presenting low risks will not be the same as for those presenting high risks. Controls need to match the level of risk which a product might present to a patient. For these purposes many standards, legislation and specifications dealing with control of risks in design and production, group products in to a limited number of classes or types according to the risk they might present. This document presents a process for such a grouping of health informatics products. It proposes five risk classes. This will facilitate broad screening of generic product types and of individual products to allow different levels of, or rigour in, the application of design and production controls which are matched to risk. Thus the classification proposed may be a precursor for standards on design and production control, where the latter might require a far more detailed, in depth and rigorous risk analysis for a particular product than that required for the broad classification process in this document. Examples of the application of the process for assigning a risk class are given for a number of different types of health informatics products. By ‘health informatics products’ is meant any health informatics product whether or not it is placed on the market and whether or not it is for sale or free of charge. This document thus covers commercial products as well as, for example, opensource health informatics software and software created for, and used in, only one health organisation such as a hospital. [source: standard document] External links • PreStandard CEN/TS 15260 CSN CR 14301 Profile Reference Name CSN CR 14301 CSN CR 14301: Health informatics - Framework for security protection of healthcare communication Categories Health Informatics; Personal Health Records ICS 35.240.80: IT applications in health care technology Abstract This report gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services Current Version CR 14301:2002 Other editions V1.0 2013-01-15 Page 312 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance This standard is relevant to AAL because it also regards medical devices. Available from http://www.cen.eu/CEN/Sectors/TechnicalCommitteesWorkshops/CEN TechnicalCommittees/Pages/Standards.aspx? param=6232&title=CEN/TC+251 Standard Parts Standard CSN CR 14301 Title Health informatics - Framework for security protection of healthcare communication Description This report gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services. The report also gives important advice for passive devices such as magnetic stripe card systems or floppy disks. The major focus is on systems for handling sensitive medical information on devices (mainly cards) held by patients. However, some requirements on ICDs to be used by health care persons (professionals and others) are also given. Detailed protocols for interaction between such devices and general medical information systems for the purpose of secure user identification will be developed within a separate work item. CR 14302 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from CR 14302 CR 14302: Health informatics - Framework for security requirements for intermittently connected devices Health Informatics; Personal Health Records 11.020: Medical sciences and health care facilities in general 35.240.80: IT applications in health care technology The standard gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services. CR 14302:2002 This standard may be relevant to AAL because it regards security mechanisms for electronic devices. http://infostore.saiglobal.com/store/Details.aspx?ProductID=268273 Description Intermittently connected devices such as patient cards may carry important clinical information as well as administrative data of importance to health care delivery. The information regarding an identifiable individual is always sensitive and with clinical data it is particularly important to provide appropriate means to ensure the protection of V1.0 2013-01-15 Page 313 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot confidentiality. In addition several other security services must be ensured to protect the patient safety as well as accountability of the professionals responsible for recording data and reading data from intermittently connected devices. Health care person devices, particularly microprocessor cards, carried by professionals and other persons working in the health care sector, may play an important role in the provision of security for all health information systems for the following core functions; to provide a secure user authentication, to provide a digital signature mechanism and as a means to carry cryptographic keys for confidentiality protection of stored and communicated health care information. The authentication function may serve as a key to protected data on a Patient data card. [source: standard document] ISO/EN 13606 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/EN 13606 ISO/EN 13606: Electronic Health Record Communication (EHRcom) Health informatics; Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical; ISO; EN 35.240.80: IT applications in health care technology The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). see Standard Parts below This standard is relevant to PHRs, EHRs and thereby to AAL. see Standard Parts below Standard Parts Standard ISO 13606-1:2007 ISO 13606-2:2007 ISO 13606-3:2008 ISO/TS 13606-4:2007 ISO 13606-5:2010 V1.0 Title Health informatics - Electronic health record communication Part 1: Reference model Health informatics - Electronic health record communication Part 2: Archetypes interchange specification Health informatics - Electronic health record communication Part 3: Reference archetypes and term lists Health informatics - Electronic health record communication Part 4: Security Health informatics - Electronic health record communication Part 5: Interface specification (ISO 13606-5:2010) 2013-01-15 Page 314 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). This is to support the interoperability of systems and components that need to communicate (access, transfer, add or modify) EHR data via electronic messages or as distributed objects: • preserving the original clinical meaning intended by the author; • reflecting the confidentiality of that data as intended by the author and patient. The name of this European Standard suggests that it is not intended to specify the internal architecture or database design of EHR systems or components, but the scope includes the use of an 'object'. This implies that the 'objects' can be stored, retrieved and exchanged. It is explicitly not intended to prescribe the kinds of clinical applications that might request or contribute EHR data in particular settings, domains or specialities. For this reason, the information model proposed here is called the EHR Extract, and might be used to define a message, an XML document or schema, or an object interface. The information model in this European Standard is an ISO RM-ODP Information Viewpoint of the EHR Extract. This European Standard considers the EHR to be the persistent longitudinal and potentially multi-enterprise or multi-national record of health and care provision relating to a single subject of care (the patient), created and stored in one or more physical systems in order to inform the subject’s future health care and to provide a medico-legal record of care that has been provided. Whilst an EHR service or system will need to interact with many other services or systems providing terminology, medical knowledge, guidelines, workflow, security, persons registries, billing etc. this European Standard has only touched on those areas if some persistent trace of such interactions is required in the EHR itself, and requires specific features in the reference model to allow their communication. This European Standard may offer a practical and useful contribution to the design of EHR systems but will primarily be realised as a common set of external interfaces or messages built on otherwise heterogeneous clinical systems. The openEHR Framework is the basis of this new Electronic Health Record Communication Standard (EN 13606) [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/EN_13606 EN 13940-1 Profile Reference Name Categories V1.0 EN 13940-1 EN 13940-1: Health informatics - System of concepts to support continuity of care - Part 1: Basic concepts Personal Health Records; Health Informatics 2013-01-15 Page 315 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract 35.240.80: IT applications in health care technology This International Standard seeks to identify and define those processes which relate to co-operation between all parties involved in health care provided to human beings (to the exclusion of other living subjects). Current Version EN 13940-1:2007 Other editions AAL Relevance Due to its relation to longitudinal PHRs this standard is relevant to AAL. Available from http://www.named.din.de/projekte/DIN+EN+139401+rev/en/143993873.html Description This International Standard seeks to identify and define those processes which relate to co-operation between all parties involved in health care provided to human beings (to the exclusion of other living subjects).Given the definition of health as agreed by WHO, this International Standard will include those aspects of health care that rely on the acts of other actors than simply health care professionals. This International standard specifically addresses aspects of sharing information related to a subject of care that is needed in the process of health care. This International multi-part Standard addresses topics including: • health care actors and other parties; • organisational principles of health care, including co-operation between actors; • health issues, health conditions and their management; • time-related concepts like contacts, encounters, episodes of care and periods of care; • concepts related to process, workflow and activities; • concepts related to decision support, use of clinical knowledge and quality; • concepts related to responsibility and information flows within the clinical process, like health mandates and their notification; concepts related to health data management. Whenever continuity of health care delivery implies social care activities as part of, or in support to, the process towards health recovery, these are to be mentioned wherever relevant in the process and workflow. In order to establish a common conceptual framework for continuity of care across national, cultural and professional barriers, all these concepts are defined in this document, and their inter-relationships identified. [source: DIN] In order to establish a common conceptual framework for continuity of care across national, cultural and professional barriers, all these concepts are defined in this document, and their inter-relationships identified. The system of concepts and the terms defined in this European standard are designed to support the management of health care related information over time and the delivery of care by different health care agents who are working together. This includes primary care professionals and teams, health care funding organisations, managers, patients, V1.0 2013-01-15 Page 316 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot secondary and tertiary health care providers, and community care teams. This harmonised system of concepts will be used to facilitate clinical and administrative decision making, health care logistics such as provision of coherent services— and to enhance relationships between healthcare professionals and their patients. Within this European standard, 'subject of care' —a concept definitely restricted here to human beings refers to an individual. It is assumed that in those cases where a health care activity addresses a group of more than one individual (e.g. a family, a community, etc.), and where a single health record is used to capture the health care activities provided to the group, each individual within the group will be referenced explicitly within that health record. [source: standard document] External links • http://www.named.din.de/projekte/DIN+EN+13940-1+rev/en/143993873.html EN 14484 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN 14484 EN 14484: Health informatics - International transfer of personal health data covered by the EU data protection directive - High level security policy Heath Informatics; Personal Health Records; Data protection specifications 35.240.80: IT applications in health care technology This standard provides guidance on a High Level Security Policy for third country organisations and is restricted to aspects relevant to personal health data transferred from a compliant country to a third country. (from webshop.ds.dk) EN 14484:2003 This standard may be relevant to AAL if personal health data is sent over country borders. http://shop.bsigroup.com/ProductDetail/?pid=000000000030078508 Description EN 14484 will provide guidance on the data protection policy which should be implemented by organisations which are participants in international applications which involve transfer of person identifiable data across national borders and which require compliance with the EU Data Protection Directive. (from CEN) External links • http://www.cen.eu/CEN/sectors/sectors/isss/Pages/default.aspx V1.0 2013-01-15 Page 317 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • http://shop.bsigroup.com/ProductDetail/?pid=000000000030078508 EN 14485 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN 14485 EN 14485:2003: Health informatics - Guidance for handling personal health data in international applications in the context of the EU data protection directive Health Informatics; Personal Health Records; Data protection specifications 35.240.80: IT applications in health care technology This standard provides guidance on data protection for those involved in international informatics applications which entail transmission of person health data from an EU Member State to a non-EU Member State. Its purpose is to assist in the application of the EU Directive on Data Protection. (from cen.eu, see external link) EN 14485:2003 This standard may be relevant to AAL if personal health data is sent over country borders to non-EU member states. http://shop.bsigroup.com/ProductDetail/?pid=000000000030078512 External links • http://www.cen.eu/cen/pages/default.aspx EN ISO 10781 Profile Reference Name EN ISO 10781 EN ISO 10781: Electronic Health Record-System Functional Model, Release 1.1 (ISO 10781:2009) Categories Personal Health Records; Health Informatics ICS 35.240.80: IT applications in health care technology Abstract ISO 10781:2009 describes the content and means of functioning of the electronic health record system of the HL7 EHR Work Group. Current Version EN ISO 10781:2012-04 Other editions AAL Relevance This standard is relevant to EHRs and thereby to AAL. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=46087 V1.0 2013-01-15 Page 318 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description This standard is based on the work of HL7. It defines a function model for electronic health records. External links • ISO/HL7 10781 EHRS FM Release 2 ENV 13607 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ENV 13607 ENV 13607: Health informatics - Messages for the exchange of information on medicine prescriptions Health Informatics; Personal Health Records 35.240.80: IT applications in health care technology This European Prestandard specifies general messages for electronic information exchange between computer systems used by healthcare parties prescribing, dispensing or administering medicinal products/medicinal appliances ENV 13607:2000 This standard is relevant to AAL because it regards the exchange of prescriptions, which may be relevant to AAL applications. http://shop.bsigroup.com/ProductDetail/?pid=000000000030012311 Description This European prestandard is applicable to the issue of new prescription messages carrying a first date for dispensing. Such messages may be used according to national regulations e.g. in countries where repeat prescribing is not allowed. The mechanisms and rules for checking and releasing these new prescription messages are outside the scope of this European prestandard. When implementing information exchange based upon this European prestandard, data protection and confidentiality principles have to be guaranteed according to the laws actually in force in the different CEN member countries. The mechanisms needed to secure data integrity, data protection and confidentiality, authentication of communicating parties and patients are outside the scope of this European prestandard. While the messages specified in this European prestandard may convey clinical and administrative information concerning patients, the way in which this information is treated in this European prestandard does not constrain the development of future standards for the electronic healthcare record or for other clinical and administrative messages. [source: standard document] V1.0 2013-01-15 Page 319 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/TR 16056 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/TR 16056 Health informatics – Interoperability of telehealth systems and networks Health Informatics; Personal Health Records; Medical Devices 01.040.35: Information technology. Office machines (Vocabularies); 35.240.80: IT applications in health care technology ISO/TR 16056-1:2004 gives a brief introduction to interoperability of telehealth systems and networks, along with definitions of telehealth and related terms. see Standard Parts below This standard may be relevant to AAL because it provides an abstract overview of telehealth components, which have to be used for interoperability of AAL-Applications. see Standard Parts below Standard Parts Standard ISO/TR 16056-1:2004 Title Health informatics – Interoperability of telehealth systems and networks – Part 1: Introduction and definitions Health informatics – Interoperability of telehealth systems and networks – Part 2: Real-time systems ISO/TR 16056-2:2004 Description ISO/TR 16056-1:2004 gives a brief introduction to interoperability of telehealth systems and networks, along with definitions of telehealth and related terms. An informative annex describing the Telehealth Technical Reference Architecture has also been included to describe more clearly the various components of a telehealth system and the elements that need to be addressed in formulating a set of requirements for these various components. The scope of the document does not include conformity and interoperability tests or functional specifications for telehealth systems and networks. [Source: ISO] HL7 Profile Reference V1.0 HL7 2013-01-15 Page 320 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name Categories HL7: Health Level Seven Communication Protocols; Medical Devices; ISO; Personal Health Records ICS Abstract HL7 provides standards for interoperability that improve care delivery, optimize workflow, reduce ambiguity and enhance knowledge transfer among all of our stakeholders, including healthcare providers, government agencies, the vendor community, fellow standardisation bodies and patients. Current Version see Standard Parts below Other editions AAL Relevance HL7 defines standard for different area of health care in order to define an unambiguous communications protocol Available from http://www.hl7.org/about/FAQs/index.cfm?ref=nav http://www.hl7.org/implement/standards/product_matrix.cfm?ref=nav Standard Parts following are reported the HL7's standard published by ISO Standard ISO/HL7 21731:2006 ISO/HL7 27932:2009 ISO/HL7 10781:2009 ISO/HL7 27953-1:2011 ISO/HL7 27931:2009 ISO/TS 15000-2:2004 ISO/TS 11073-92001:2007 ISO 13606-3:2009 ISO 21090:2011 Title Data Exchange Standards – HL7 Clinical Document Architecture, Release 2 Health informatics – HL7 version 3 – Reference information model – Release 1 Electronic Health Record-System Functional Model, Release 1.1 Health informatics – Individual case safety reports (ICSRs) in pharmacovigilance – Part 1: Framework for adverse event reporting Data Exchange Standards – Health Level Seven Version 2.5 – An application protocol for electronic data exchange in healthcare environments Electronic business eXtensible Markup Language (ebXML) – Part 2: Message service specification (ebMS) EHealth informatics – Medical waveform format – Part 92001: Encoding rules Health informatics – Electronic health record communication – Part 3: Reference archetypes and term lists Health informatics – Harmonized data types for information interchange Description Health Level Seven International is one of several American National Standards Institute (ANSI) -accredited Standards Developing Organizations (SDOs) operating in the healthcare arena. Most SDOs produce standards (sometimes called specifications or V1.0 2013-01-15 Page 321 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot protocols) for a particular healthcare domain such as pharmacy, medical devices, imaging or insurance (claims processing) transactions. Health Level Seven's domain is clinical and administrative data. HL7 and its members provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information. These standards define how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world. External links • http://www.hl7.org/ • http://en.wikipedia.org/wiki/Health_Level_7 IHE XDM Profile Reference Name Categories ICS Abstract IHE XDM IHE XDM: Cross-Enterprise Media Interchange Communication Protocols; Medical Devices; Personal Health Records Cross-Enterprise Document Media Interchange (XDM) provides document interchange using a common file and directory structure over several standard media. This permits the patient to use physical media to carry medical documents. This also permits the use of person-toperson email to convey medical documents. (from wiki.ihe.net, see external link) Current Version Current Technical Framework - Revision 9.0 Other editions AAL Relevance Exchanging of medical documents can be very useful is AAL systems. Available from http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description This Supplement introduces a new IHE Integration Profile that facilitates interchange across health enterprises of electronic patient related medical documents, using media or email. This Integration Profile, referred to as XDM (for Cross-Enterprise Document Media Interchange), complements the existing XDS Integration Profile by providing for the use of XDS defined formats and metadata in a simpler environment: • Transfer of documents and related metadata over CD-R and USB memory devices • Transfer of documents and related metadata over email using a ZIP attachment It focuses on providing a standards-based specification for managing the interchange of V1.0 2013-01-15 Page 322 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot documents that healthcare enterprises (anywhere from a private physician to a clinic to an acute care in-patient facility) have decided to explicitly exchange documents using media between the patient and the patient’s care providers, or between care providers. This enables better interoperability between Electronic Health Records (EHRs) and Personal Health Records (PHRs), as a natural complement to the IHE ITI XDS Integration Profile (for cross-enterprise document sharing). [Source: ihe.net, see external link] External links • http://wiki.ihe.net/index.php?title=Cross-enterprise_Document_Media_Interchange • http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Supplement_XDM_TI_200 6_08_15.pdf IHE XDR Profile Reference Name Categories ICS Abstract IHE XDR IHE XDR: Cross-Enterprise Document Reliable Interchange Communications Protocols; Medical Devices; Personal Health Records Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories. [Source: from wiki.ihe.net, see external link] Current Version Other editions AAL Relevance XDR provides a reliable and automatic transfer of documents and metadata for one patient between EHR systems even in the absence of an XDS infrastructure. Available from http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description XDR provides a reliable and automatic transfer of documents and metadata for one patient between EHR systems even in the absence of an XDS infrastructure. XDR supports the reuse of the Provide and Register Set transaction-b with Web-Services as transport. Transfer is direct from source to recipient, no repository or registry actors are involved. XDR is document format agnostic, supporting the same document content as XDS and XDM. Document content is described in XDS Document Content Profiles. Examples are XDS-MS, XD-LAB, XPHR, and XDS-SD. XDR defines no new metadata or message formats. It leverages XDS metadata with emphasis on patient identification, document identification, description, and relationships. V1.0 2013-01-15 Page 323 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot [Source: wiki.ihe.net, see external link] External links • http://wiki.ihe.net/index.php?title=Cross-enterprise_Document_Reliable_Interchange IHE XDS Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from IHE XDS IHE XDS: Cross-Enterprise Document Sharing Communication Protocols; Medical Devices; Personal Health Records Cross-Enterprise Document Sharing (XDS) facilitates the registration, distribution and access across health enterprises of patient electronic health records. [Source: wiki.ihe.net, see external link] Technical Framework version 9.0 XDS providing a standards-based specification for managing the sharing of documents between any healthcare enterprise http://www.ihe.net/ http://www.ihe.net/Technical_Framework/index.cfm#IT Description Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility and personal health record systems. This is managed through federated document repositories and a document registry to create a longitudinal record of information about a patient within a given clinical affinity domain. These are distinct entities with separate responsibilities: • A Document Repository is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests. • A Document Registry is responsible for storing information about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored. In addition to these features the figure of document administrator has been inserted. The Document Administrator actor supports metadata update by issuing the Update Document, Set transaction and Delete Document Set transaction to the Document Registry actor. Facilitates management of the Electronic Health Record • facilitates the registration, distribution and access across health enterprises of patient electronic health records. V1.0 2013-01-15 Page 324 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility. [Source: from wiki.ihe.net] External links • http://wiki.ihe.net/index.php?title=Cross-Enterprise_Document_Sharing XPHR Profile Reference Name Categories XPHR XPHR: Exchange of Personal Health Record Content Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract This profile describes the content and format of summary information extracted from a PHR System for import into an EHR System, and visa versa. Current Version 8.0 Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant to data storage and communication in the field of AAL. Available from http://www.ihe.net/ Description Exchange of Personal Health Record Content (XPHR) was defined by the IHE to enable the exchange of important personal health data of a patient between electronic health record systems in the professional domain and personal health record systems in the home domain. XPHR is based on CDA and represented in XML. External links • http://wiki.ihe.net/index.php?title=Exchange_of_Personal_Health_Record_Content ISO/IEEE 11073 Profile Reference Name Categories V1.0 ISO/IEEE 11073 ISO/IEEE 11073: Health informatics - Medical / health device communication standards Communication Protocols; Medical Devices; Personal Health Records; Terminologies and Semantics; Medical Terminology; ISO; IEEE 2013-01-15 Page 325 of 490 AALIANCE2 ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot 35.240.80: IT applications in health care technology CEN ISO/IEEE 11073 Health informatics - Medical / health device communication standards enable communication between medical, health care and wellness devices and with external computer systems. They provide automatic and detailed electronic data capture of clientrelated and vital signs information, and of device operational data. see Standard Parts below This is the standard for data communications between health devices see Standard Parts below Standard Parts Standard ISO/IEEE 11073-20101:2004 ISO/IEEE 11073-10408:2010 ISO/IEEE 11073-10415:2010 ISO/IEEE 11073-10471:2010 ISO/IEEE 11073-10407:2010 ISO/IEEE 11073-10404:2010 ISO/IEEE 11073-10417:2010 ISO/IEEE 11073-30200:2004 ISO/IEEE 11073-30300:2004 ISO/IEEE 11073-10201:2004 ISO/IEEE 11073-10101:2004 V1.0 Title Health informatics – Point-of-care medical device communication – Part 20101: Application profiles – Base standard Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale Health informatics – Personal health device communication – Part 10471: Device specialization Independent living activity hub Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor Health informatics – Personal health device communication – Part 10404: Device specialization – Pulse oximeter Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter Health informatics – Point-of-care medical device communication – Part 30200: Transport profile – Cable connected Health informatics – Point-of-care medical device communication – Part 30300: Transport profile – Infrared wireless Health informatics – Point-of-care medical device communication – Part 10201: Domain information model Health informatics – Point-of-care medical device communication – Part 10101: Nomenclature 2013-01-15 Page 326 of 490 AALIANCE2 ISO 11073-91064:2009 ISO/IEEE 11073-20601:2010 ISO 11073-90101:2008 ISO/TS 11073-92001:2007 ISO/IEEE FDIS 11073-10406 ISO/IEEE DIS 11073-10417 ISO/IEEE DIS 11073-10418 ISO/IEEE FDIS 11073-10420 ISO/IEEE FDIS 11073-10421 ISO/IEEE FDIS 11073-10472 ISO/IEEE FDIS 11073-30400 D4.1 Online Repository of Standards - Snapshot Health informatics – Standard communication protocol – Part 91064: Computer-assisted electrocardiography Health informatics – Personal health device communication – Part 20601: Application profile – Optimized exchange protocol Health informatics – Point-of-care medical device communication – Part 90101: Analytical instruments – Point-of-care test Health informatics – Medical waveform format – Part 92001: Encoding rules Health informatics – Personal health device communication – Part 10406: Device specialization – Basic electrocardiograph (ECG) (1- to 3-lead ECG) Health informatics – Personal health device communication – Part 10417: Device specialization – Glucose meter Health informatics – Personal health device communication – Part 10418: Device specialization– International Normalized Ratio (INR) monitor Health informatics – Personal health device communication – Part 10420: Device specialization – Body composition analyser Health informatics – Personal health device communication – Part 10421: Device specialization – Peak expiratory flow monitor (peak flow) Health Informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor Health informatics – Point-of-care medical device communication – Part 30400: Interface profile – Cabled Ethernet Description 13. Provide real-time plug-and-play interoperability for citizen-related medical, healthcare and wellness devices; 14. Facilitate efficient exchange of care device data, acquired at the point-of-care, in all care environments. • “Real-time” means that data from multiple devices can be retrieved, time correlated, and displayed or processed in fractions of a second. • “Plug-and-play” means that all a user has to do is make the connection – the systems automatically detect, configure, and communicate without any other human interaction. • “Efficient exchange of care device data” means that information that is captured at the point-of-care (e.g., personal vital signs data) can be archived, retrieved, and processed by many different types of applications without extensive software and equipment V1.0 2013-01-15 Page 327 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot support, and without needless loss of information. The standards are targeted at personal health and fitness devices (such as glucose monitors, pulse oximeters, weighing scales, medication dispensers and activity monitors) and at continuing and acute care devices (such as pulse oximeters, ventilators and infusion pumps). They comprise a family of standards that can be layered together to provide connectivity optimized for the specific devices being interfaced. There are four main partitions to the standards: • Device data, including a nomenclature, or terminology, optimized for vital signs information representation based on an object-oriented data model, and device • General application services (e.g., polled vs. “event driven” services); • Internetworking and gateway standards (e.g., an observation reporting interface from CEN ISO/IEEE 11073-based messaging and data representation to HL7 or DICOM); • Transports (e.g., cable connected or wireless). [Source: Wikipedia] External links • ISO/IEEE11073 (Wikipedia) Continua Health Alliance Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from Continua Health Alliance Continua Health Alliance Integration Profiles; Personal Health Records 35.240.80 IT applications in health care technology Continua is an organization that develops implementation guidelines for personal health applications 2012 Plug-and-play interoperability for personal health applications http://www.continuaalliance.org/products/design-guidelines.html Standard Parts Standard Guidelines 2011 Guidelines 2012 Title Continua Design Guidelines, Version 2011 Continua Design Guidelines, Version 2012 (available to members only) Description Continua Health Alliance is an international non-profit organization in which about 240 companies collaborate on developing specifications and a certification program for a plugV1.0 2013-01-15 Page 328 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot and-play interoperability of applications in the field of “personal health”, more precisely: chronic disease management, ageing independently (which essentially means AAL), and health & physical fitness. Very much like the IHE Technical Frameworks, the Continua Design Guidelines are specifications based on existing standards that describe the IT systems involved in a specific use case and the interfaces between these IT systems, based on existing standards. Where possible, options are narrowed down as far as possible to achieve “plug and play” interoperability. The most important specifications on which the Continua Design Guidelines are based are ISO/IEEE 11073, Bluetooth (Health Device Profile and Low Energy), ZigBee, USB, HL7v2, the HL7 Personal Health Monitoring Report (PHMR) and IHE Cross-Enterprise Document Reliable Interchange (XDR). The Continua Design Guidelines are published annually. The predecessor version of the current specification is available freely for non-commercial purposes. Access to the current specification, and commercial use of it, requires membership in the Continua Health Alliance. Furthermore, Continua has established a product certification program that certifies the interoperability of labelled products with other Continua-certified products. A list of certified products is available from the Continua website. External links • http://www.continuaalliance.org/index.html • http://www.continuaalliance.org/products/design-guidelines.html • http://www.continuaalliance.org/products/productshowcase.html • http://en.wikipedia.org/wiki/The_Continua_Health_Alliance CCD Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from V1.0 CCD CCD: Continuity of Care Document Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical The Continuity of Care Document (CCD) specification is an XML-based markup standard intended to specify the encoding, structure and semantics of a patient summary clinical document for exchange. As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. http://hl7book.net/index.php?title=CDA 2013-01-15 Page 329 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description The Continuity of Care Document (CCD) summarizes the most important health data of a patient. The Document was developed on the basis of the contents of the CCR but uses the structure of a CDA-Document. It is represented in XML. The CCD specification is a constraint on the HL7 Clinical Document Architecture (CDA) standard. The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part is based on the HL7 Reference Information Model (RIM) and provides a framework for referring to concepts from coding systems, such as the SNOMED or the LOINC. The patient summary contains a core data set of the most relevant administrative, demographic, and clinical information facts about a patient's healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another practitioner, system, or setting to support the continuity of care. Its primary use case is to provide a snapshot in time containing the pertinent clinical, demographic, and administrative data for a specific patient. The CCD specification contains U.S. specific requirements; its use is therefore limited to the U.S. The U.S. Healthcare Information Technology Standards Panel has selected the CCD as one of its standards. CCDs are quickly becoming one of the most ubiquitous and thorough means of transferring health data on patients as each can contain vast amounts of data based on the standard format, in a relatively easy to use and portable file. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Continuity_of_Care_Document CCR Profile Reference Name Categories CCR CCR: Continuity of Care Record Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract Continuity of Care Record (CCR) is a health record standard specification developed jointly by ASTM International, the Massachusetts Medical Society (MMS), the Healthcare Information and Management Systems Society (HIMSS), the American Academy of Family Physicians (AAFP), the American Academy of Pediatrics (AAP), and other health informatics vendors. Current Version Other editions V1.0 2013-01-15 Page 330 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://www.astm.org/Standards/E2369.htm Description The Continuity of Care Document (CCR) summarizes the most important health data of a patient. It was developed with the support of different medical committees under the lead of the American Society for Testing and Materials (ASTM). The CCR is represented in XML and uses terminology systems like SNOMED and ICD to enable a semantic interoperability. CCR-Header (administrative data), CCR-Body (the actual content) and the CCR-Footer. The CCR standard is a patient health summary standard. It is a way to create flexible documents that contain the most relevant and timely core health information about a patient, and to send these electronically from one caregiver to another. It contains various sections such as patient demographics, insurance information, diagnoses and problem list, medications, allergies and care plan. These represent a “snapshot” of a patient's health data that can be useful or possibly lifesaving, if available at the time of clinical encounter. The ASTM CCR standard is designed[opinion] to permit easy creation by a physician using an electronic health record (EHR) system at the end of an encounter. Because it is expressed in the standard data interchange language known as XML, a CCR can potentially be created, read, and interpreted by any EHR or EMR software application. A CCR can also be exported to other formats, such as PDF or Office Open XML (Microsoft Word 2007 format). The Continuity of Care Document (CCD) is an HL7 CDA implementation of the Continuity of Care Record (CCR). A CCR document can generally be converted into CCD using Extensible Stylesheet Language Transformations (XSLT), but it is not always possible to perform the inverse transformation, since some CCD features are not supported in CCR. HITSP provides reference information that demonstrates how CCD and CCR (as HITSP C32) are embedded in CDA. Although the CCR and CCD standards could continue to coexist, with CCR providing for basic information requests and CCD servicing more detailed requests, the newer CCD standard might eventually completely supplant CCR. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Continuity_of_Care_Record CDA Profile Reference Name Categories V1.0 CDA CDA: HL7 Clinical Document Architecture Personal Health Record; File Formats and Persistent Data Structures; 2013-01-15 Page 331 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot General Purpose; Medical ICS Abstract The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. Current Version Other editions AAL Relevance As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://hl7book.net/index.php?title=CDA Description The Clinical Document Architecture (CDA) is a standard for the generic representation of health related documents. CDA is uses so called templates, specifying the concrete data items for a specific use case. CDA is part of the HL7 version 3 standard family and was accepted as ISO standard. CDA documents are represented in XML and consist of three levels. The first level is only human readable free text. The second level contains structured headings, which are machine interpretable. A CDA document on level three have to be complete machine interpretable. The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. CDA is part of the HL7 version 3 standard. Akin to other parts of the HL7 version 3 standard it was developed using the HL7 Development Framework (HDF) and it is based on the HL7 Reference Information Model (RIM) and the HL7 Version 3 Data Types. CDA documents are persistent in nature. The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part relies on coding systems (such as from SNOMED and LOINC) to represent concepts. CDA Release 2 has been adopted as an ISO standard, ISO/HL7 27932:2009. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Clinical_Document_Architecture DICOM Profile Reference Name Categories V1.0 DICOM DICOM: Digital Imaging and Communications in Medicine Communication Protocols; Medical Devices; File Formats and 2013-01-15 Page 332 of 490 AALIANCE2 ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot Persistent Data Structures; General Purpose; Medical; ISO 35.240.80: IT applications in health care technology DICOM defines criteria for communication, visualization, archiving and printing of biomedical information http://medical.nema.org/ (there may be daily changes) ISO 12052:2006: Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management DICOM is a public standard, so it achieves a great diffusion among medical devices. This involves a greater exchange of information http://medical.nema.org/standard.html http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=43218 Description DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting information in medical imaging. It includes a file format definition and a network communications protocol. The communication protocol is an application protocol that uses TCP/IP to communicate between systems. DICOM files can be exchanged between two entities that are capable of receiving image and patient data in DICOM format. The National Electrical Manufacturers Association (NEMA) holds the copyright to this standard.[1] It was developed by the DICOM Standards Committee, whose members[2] are also partly members of NEMA.[3] DICOM enables the integration of scanners, servers, workstations, printers, and network hardware from multiple manufacturers into a picture archiving and communication system (PACS). The different devices come with DICOM conformance statements which clearly state which DICOM classes they support. DICOM has been widely adopted by hospitals and is making inroads in smaller applications like dentists' and doctors' offices. DICOM is known as NEMA standard PS3, and as ISO standard 12052:2006 “Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management”. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/DICOM ePflegebericht Profile Reference Name Categories V1.0 ePflegebericht ePflegebericht Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical 2013-01-15 Page 333 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ICS Abstract Current Version Other editions AAL Relevance CDA-based document in German care context. As this standard is relevant to Personal Health Records, it is relevant for the data storage and communication in the field of AAL. Available from http://www.hl7.de/publikationen/techdok.php Description The ePflegebericht (electronic care report) is a CDA –based document that is currently under development by the German Hochschule Osnabrück. The document consists of a header with administrative data and a body, which holds the actual content (like diagnoses, care targets and so on). The document is intended to share information between different institutions, which participate in the care process of a patient. PHMR Profile Reference Name Categories PHMR PHMR: Personal Health Monitoring Report File Formats and Persistent Data Structures; General Purpose; Medical; Personal Health Records ICS Abstract The PHMR carries personal healthcare monitoring information. The information is transmitted as notes and as raw data. Current Version HL7 Implementation Guide for CDA Release 2 - Personal Healthcare Monitoring Report Other editions AAL Relevance This standard is used by the Continua Alliance to collect an share information that is acquired in the users home and is thereby relevant to AAL. Available from http://www.hl7.org/implement/standards/product_brief.cfm? product_id=33 Description The purpose of this document is to describe constraints on the CDA Header and Body elements for Personal Healthcare Monitoring Report (PHMR) documents mostly containing analysed and raw information of data generated by personal healthcare monitoring devices such as glucometers, BP cuffs, thermometers, weight scales, etc. The PHMR carries personal healthcare monitoring information. The information may have multiple characteristics, including representation of: • Measurements captured by devices V1.0 2013-01-15 Page 334 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Notes, summaries, and other kinds of narrative information • Graphs that may be added by intermediary devices that represent trends of users’ health [Source: HL7] VHitG Profile Reference Name Categories VHitG VHitG: VHitG Medical report Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical ICS Abstract Current Version Other editions AAL Relevance As this standard is relevant to Electronic and Personal Health Records and communication in the healthcare system, it is relevant for the data storage and communication in the field of AAL. Available from http://www.bvitg.de/arztbrief.html Description The initiative was founded in May 2005 through the bvitg. The target of this standard is the exchange of a structured document in a medical context. The document contains information for the discharge or referral of a patient and is intended to be read by professionals in the medical domain. V1.0 2013-01-15 Page 335 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 9. Sensors & Actuators IEEE 1451 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from IEEE 1451 IEEE 1451: IEEE Standard for a Smart Transducer Interface for Sensors and Actuators Networks and Buses; Wireless Protocols for Mobile Applications; IEEE; Robots/ Robotics IEEE 1451 is a set of smart transducer interface standards developed by the Institute of Electrical and Electronics Engineers (IEEE) Instrumentation and Measurement Society’s Sensor Technology Technical Committee that describe a set of open, common, networkindependent communication interfaces for connecting transducers (sensors or actuators) to microprocessors, instrumentation systems, and control/field networks. (from Wikipedia) see Standard Parts below As AAL scenarios use sensors and maybe actors IEEE 1451 might be useful for connecting these devices to other systems/ devices. see Standard Parts below Standard Parts Standard IEEE Std 1451.0-2007 IEEE Std 1451.1-1999 IEEE Std 1451.2-1997 IEEE Std 1451.3-2003 IEEE Std 1451.4-2004 V1.0 Title IEEE Standard for a Smart Transducer Interface for Sensors and Actuators - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats IEEE Standard for a Smart Transducer Interface for Sensors and Actuators-Network Capable Application Processor (NCAP) Information Model IEEE Standard for a Smart Transducer Interface for Sensors and Actuators - Transducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats IEEE Standard for a Smart Transducer Interface for Sensors and Actuators-Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems IEEE Standard for a Smart Transducer Interface for Sensors and Actuators - Mixed-Mode Communication Protocols and 2013-01-15 Page 336 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot IEEE Std 1451.5-2007 IEEE Std 1451.7-2010 Transducer Electronic Data Sheet (TEDS) Formats IEEE Standard for a Smart Transducer Interface for Sensors and Actuators Wireless Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats IEEE Standard for Smart Transducer Interface for Sensors and Actuators–Transducers to Radio Frequency Identification (RFID) Systems Communication Protocols and Transducer Electronic Data Sheet Formats Description One of the key elements of these standards is the definition of Transducer electronic data sheets (TEDS) for each transducer. The TEDS is a memory device attached to the transducer, which stores transducer identification, calibration, correction data, and manufacturer-related information. The goal of the IEEE 1451 family of standards is to allow the access of transducer data through a common set of interfaces whether the transducers are connected to systems or networks via a wired or wireless means. [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=IEEE_1451&oldid=528031505 9.1. Safety EN 957 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from V1.0 EN 957 EN 957: Stationary training equipment Safety; Testing; Indoor sports equipment Sensors & Actuators 97.220.30 - Indoor sports equipment EN 957 specifies safety requirements and test methods for stationary training equipment. See below for individual standard parts Some AAL scenarios include rehabilitation or prevention elements with stationary training equipment. In this case EN 957 should be taken into account. CEN - Sports, playground and other recreational facilities and equipment - Published standards 2013-01-15 Page 337 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard EN 957-1:2005 EN 957-2:2003 EN 957-4:2006+A1:2010 EN 957-5:2009 EN 957-6:2010 EN 957-7:1998 EN 957-8:1998 EN 957-9:2003 EN 957-10:2005 Title Stationary training equipment - Part 1: General safety requirements and test methods Stationary training equipment - Part 2: Strength training equipment, additional specific safety requirements and test methods Stationary training equipment - Part 4: Strength training benches, additional specific safety requirements and test methods Stationary training equipment - Part 5: Stationary exercise bicycles and upper body crank training equipment, additional specific safety requirements and test methods Stationary training equipment - Part 6: Treadmills, additional specific safety requirements and test methods Stationary training equipment - Part 7: Rowing machines, additional specific safety requirements and test methods Stationary training equipment - Part 8: Steppers, stairclimbers and climbers - Additional specific safety requirements and test methods Stationary training equipment - Part 9: Elliptical trainers, additional specific safety requirements and test methods Stationary training equipment - Part 10: Exercise bicycles with a fixed wheel or without freewheel, additional specific safety requirements and test methods Description This European Standard specifies general safety requirements for stationary training equipment during use unless modified in the other parts of this European Standard. It also specifies a classification system (see Clause 4). This European Standard is applicable to all stationary training equipment as defined in 3.1. This includes equipment for use in training areas of organizations such as sport associations, educational establishments, hotels, sport halls, clubs, rehabilitation centres and studios (classes S and I) where access and control is specifically regulated by the owner (person who has the legal responsibility), equipment for domestic use (class H) and other types of equipment including motor driven equipment as defined in 3.1. If a user has special needs (medical rehabilitation, disability) it is essential that the owner (the person with legal responsibility) conducts a specific risk assessment to determine safe use and if necessary to insure trained staff are available to supervise the activity. The requirements of a specific standard take priority over the corresponding requirements of this general European Standard. This European Standard does not apply to stationary training equipment intended for use by children. NOTE 1 In the event that the stationary training equipment is intended for medical purposes, attention is drawn to the requirements of Council Directive of 14 June 1993 on V1.0 2013-01-15 Page 338 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot the approximation of the laws of the Member States relating to medical devices 93/42/EEC in addition to the requirements of this European Standard. NOTE 2 In the event that the stationary training equipment is designed to be accessible to people with disability, attention is drawn to any relevant national guidelines (see bibliography). [source: CEN] External links • CEN - Sports, playground and other recreational facilities and equipment - Published standards • EC - European standards - General product safety EN 41003 Profile Reference Name EN 41003 EN 41003: Particular safety requirements for equipment to be connected to telecommunication networks and/or a cable distribution system Categories Sensors & Actuators; Safety;Robots/ Robotics ICS 33.040 - Telecommunication systems Abstract This European Standard applies to equipment designed and intended to be connected as a terminal to a TELECOMMUNICATION NETWORK and/or a CABLE DISTRIBUTION SYSTEM termination. (It does not apply to equipment covered by EN 60950-1 and EN 60065.) Current Version EN 41003:2008 Other editions AAL Relevance In AAL some devices need to be connected to telecommunication network and cable distribution system, so it is important to refer to EN 41003 for the safety requirements Available from http://www.cenelec.eu/dyn/www/f? p=104:110:2402176393734147::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:85,15235,25 Description This European Standard specifies the safety requirements of the interface to the TELECOMMUNICATION NETWORK and/or the CABLE DISTRIBUTION SYSTEM only and it does not specify any other safety requirements. It applies regardless of ownership or responsibility for installation or maintenance of the equipment, and regardless of the source of power. V1.0 2013-01-15 Page 339 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 50194 Profile Reference Name EN 50194 EN 50194: Electrical apparatus for the detection of combustible gases in domestic premises Categories Sensors & Actuators; Safety ICS 13.320 - Alarm and warning systems Abstract This European Standard specifies general requirements for the construction, testing and performance of electrically operated apparatus for the detection of combustible gases, designed for continuous operation in a fixed installation in domestic premises. Current Version see Standard Parts below Other editions AAL Relevance In order to protect residents against combustible gases, this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 50194-1:2009 EN 50194-2:2006 Title Electrical apparatus for the detection of combustible gases in domestic premises - Part 1: Test methods and performance requirements Electrical apparatus for the detection of combustible gases in domestic premises - Part 2: Electrical apparatus for continuous operation in a fixed installation in recreational vehicles and similar premises - Additional test methods and performance requirements Description The apparatus may be mains or battery powered. This European Standard specifies two types of apparatus to operate in the event of an escape of town gas, natural gas or Liquefied petroleum gas (LPG): • Type A apparatus - to provide a visual and audible alarm and an executive action in the form of an output signal that may actuate directly or indirectly a shut-off device and/or other ancillary device; • Type B apparatus - to provide a visual and audible alarm only. This European Standard excludes apparatus for the detection of toxic hazards of gases such as carbon monoxide (see EN 50291-1 and EN 50291-2). EN 50364 Profile Reference V1.0 EN 50364 2013-01-15 Page 340 of 490 AALIANCE2 Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot EN 50364: Limitation of human exposure to electromagnetic fields from devices operating in the frequency range 0 Hz to 300 GHz, used in Electronic Article Surveillance (EAS), Radio Frequency Identification (RFID) and similar applications Sensors & Actuators; Safety; Robots/ Robotics 13.280 - Radiation protection 33.100.01 - Electromagnetic compatibility in general This product standard applies to devices operating within the frequency range 0 Hz to 300 GHz, used in electronic article surveillance (EAS), radio frequency identification (RFID) and similar applications. EN 50364:2010 The devices of systems installed in AAL homes should consider the limitations of human exposure. http://www.cenelec.eu/dyn/www/f? p=104:110:3215759554642698::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:1003,21313,25 Description This product standard applies to devices operating within the frequency range 0 Hz to 300 GHz, used in electronic article surveillance (EAS), radio frequency identification (RFID) and similar applications. This product standard may be used for demonstration of compliance to the requirements of the RTTED Directive 1999/5/EC, with regard to the limitation of human exposure to electromagnetic fields (EMFs). There are additional requirements covered by the Directive, which are not included in this product standard. This product standard may be used for demonstration of compliance to the requirements of the Low Voltage Directive 2006/95/EC, with regard to the limitation of human exposure to EMFs. There are additional requirements covered by the Directive, which are not included in this product standard. It should be noted that the supplier of a specific piece of equipment might not know the overall exposure environment in which the equipment is being used. This product standard can only assess the human exposure from the specific equipment under evaluation when being used according to the supplier’s guidelines. Other standards can apply to products covered by this document. In particular this document is not designed to evaluate the electromagnetic compatibility with other equipment; nor does it reflect any product safety requirements other than those specifically related to human exposure to electromagnetic fields. [source: webshop.ds.dk] External links • http://engineers.ihs.com/document/abstract/GWKOHBAAAAAAAAAA V1.0 2013-01-15 Page 341 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 50491 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN 50491 EN 50491: General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Networks and Buses; Home Automation Field Buses; Cable-based Home Automation Field Buses; EN; HBES; Building Automation; BACS; Sensors & Actuators; Safety 97.120 - Automatic controls for household use The EN 50491 series of standards is entitled “General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS)” and contains requirements for HBES devices including environmental performance, safety, functional safety, EMC, and desing, planning and installation. The EN 50491 series is in the process of replacing the existing EN 50090 series of standards entitled “Home and Building Electronic Systems (HBES)” covering the areas system overview, aspects of application, media independent layers, media and media dependent layers, interfaces, system management, conformity assessment of products and installation requirements. [source: etsi.org] see Standard Parts below As AAL scenarios often will use HBES and BACS EN 50491 is an essential standard. see Standard Parts below Standard Parts Standard prEN 50491-1:201X EN 50491-2:2010 EN 50491-3:2009 EN 50491-4-1:2012 V1.0 Title General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 1: General requirements General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 2: Environmental conditions General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 3: Electrical safety requirements General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 4-1: General functional safety requirements for products intended to be integrated in Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) 2013-01-15 Page 342 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 50491-5-1:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-1: EMC requirements, conditions and test set-up prEN 50491-5-2 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-2: EMC requirements for HBES/BACS (Class A) used in residential, commercial and light industry environment EN 50491-5-2:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-2: EMC requirements for HBES/BACS used in residential, commercial and light industry environment EN 50491-5-3:2010 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 5-3: EMC requirements for HBES/BACS used in industry environment prEN 50491-6-1:2011 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 6-1: HBES installations - Installation and planning CLC/TR 50491-6General requirements for Home and Building Electronic Systems 3:2011 (HBES) and Building Automation and Control Systems (BACS) Part 6-3: HBES installations - Assessment and definition of levels prEN 50491-11 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 11: Smart metering - Application specification - Home display prEN 50491-12 General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) Part 12: Smart grid - Application specification - Interface and framework for customer Description EN 50491-3:2009 provides the electrical safety requirements for all devices connected to HBES/BACS. This European Standard is applicable to – operator stations and other human system interface devices, – devices for management functions, – control devices, automation stations and application specific controllers, – field devices, – cabling and interconnection of devices. This European Standard covers the following requirements and compliance criteria: – protection from hazards in the device; – protection from overvoltages on the network; – protection from touch current; – protection from hazards caused by different type of circuits; – protection of the communication wiring from overheating caused by excessive current. EN 50491-4-1:2012 sets the requirements for functional safety for HBES/BACS products and systems, a multi-application bus system where the functions are decentralised, distributed and linked through a common communication process. The requirements may also apply to the distributed functions of any equipment connected in a home or building control system if no specific functional safety standard exists for this equipment or system. The functional safety requirements of this European Standard apply together with the relevant product standard for the device if any. This European Standard is part of the EN V1.0 2013-01-15 Page 343 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 50491 series of standards. This European Standard does not provide functional safety requirements for safety-related systems. EN 50491-5-1:2010 sets the minimum level of EMC performance for HBES/BACS products intended to be connected to an HBES/BACS system. A set of devices connected to perform a stand alone application is not considered to be an HBES/BACS system and therefore are outside the scope of this European Standard. This European Standard provides the general performance requirements and test setups for EMC for all products connected to HBES/BACS. This connection can be wired (e.g. communication cable, power line) or wireless (e.g. radiofrequency, infrared). This European Standard is applicable (but not limited) to – operator stations and other human system interface devices, – devices for management functions, – control devices, automation stations and application specific controllers, – field devices and their interfaces, – cabling and interconnection of devices, – dedicated devices for engineering and commissioning tools for HBES/BACS CLC/TR 50491-6-3:2011 establishes the general rules for assessing HBES installations, according to its complexity and energy performance. This Technical Report applies to – household HBES installation, from and up to the connection point with the utility (i.e. electricity, telecommunications, tele-service, water, gas, security and similar), – HBES installations that include applications related to automation and integrated control of electrical and/or electronic devices, – the networks used for the HBES interconnection regardless of the transmission media used for their communications, – new HBES installations, retrofitting and enlargement of existing installations. [Source: CENELEC] External links • http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740501/01.01.01_60/tr_1051740 501v010101p.pdf EN 60065 Profile Reference Name EN 60065 EN 60065: Audio, video and similar electronic apparatus - Safety requirements Categories Sensors & Actuators; Safety ICS 97.020 - Home economics in general Abstract Applies to receiving apparatus for sound or vision, amplifiers, load and source transducers, motor-driven apparatus (radio-gramophones, tape recorders and sound-film projectors, etc.) which are to be connected to the mains, directly or indirectly, and which are intended for domestic and similar indoor use. Current Version see Standard Parts below Other editions AAL Relevance As AAL homes may contain such devices, this standard is relevant. V1.0 2013-01-15 Page 344 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from see Standard Parts below Standard Parts Standard EN 60065:2002 EN 60065:2002/Corr.:2007 EN 60065:2002/A1:2006 EN 60065:2002/A11:2008 EN 60065:2002/A2:2010 EN 60065:2002/A12:2012 FprEN 60065:2012 Title Audio, video and similar electronic apparatus - Safety requirements Description EN 60065 applies to receiving apparatus for sound or vision, amplifiers, load and source transducers, motor-driven apparatus (radio-gramophones, tape recorders and sound-film projectors, etc.) which are to be connected to the mains, directly or indirectly, and which are intended for domestic and similar indoor use. It gives a safety and classification terminology based on EN 60536 and specifies requirements for marking, insulation, components, electrical connections and fixings, protection against ionizing radiation, resistance to heating, mechanical strength and stability, etc., as well as a requirement for splash-proof mains operated electronic equipment. EN 60065 does not apply to apparatus designed for rated supply voltage exceeding 433 V (r.m.s.) between phases in the case of three-phase supply and 250 V (r.m.s.) in all other cases and has the status of a group safety publication in accordance with IEC Guide 104. Please refer to Guide 112 for using the current editions of EN 60065 and EN 60950 in evaluating the safety of multimedia equipment. [Source: CENELEC] EN 60335 Profile Reference Name Categories ICS EN 60335 EN 60335: Household and similar electrical appliances - Safety Sensors & Actuators; Safety; EN; CENELEC 13.120 - Domestic safety 97.030 - Domestic electrical appliances in general Abstract In this document the safety of electrical appliances for household and similar purposes is considered, evaluating also the hazards presented by these appliances encountered by all persons in and around the home. Current Version see Standard Parts below Other editions IEC 60335 AAL Relevance As AAL scenarios integrate household and similar electrical appliances this standard should be taken into account for safety reasons. V1.0 2013-01-15 Page 345 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from see Standard Parts below Standard Parts Standard EN 60335-1:2012 EN 60335-2-2:2010 EN 60335-2-3:2002 superseded by EN 60335-2-3:201X EN 60335-2-4:2010 EN 60335-2-5:2003 superseded by EN 60335-2-5:201X EN 60335-2-6:2003 superseded by FprEN 60335-2-6:2010 EN 60335-2-7:2010 EN 60335-2-8:2003 superseded by FprEN 60335-2-8:2012 EN 60335-2-9:2003 superseded by FprEN 60335-2-9:2009 EN 60335-2-10:2003 EN 60335-2-10:2003/A1:2008 EN 60335-2-11:2010 EN 60335-2-11:2010/A11:2012 EN 60335-2-12:2003 EN 60335-2-12:2003/A1:2008 EN 60335-2-13:2010 EN 60335-2-13:2010/A11:2012 V1.0 2013-01-15 Title Household and similar electrical appliances Safety - Part 1: General requirements Household and similar electrical appliances Safety - Part 2-2: Particular requirements for vacuum cleaners and water-suction cleaning appliances Household and similar electrical appliances Safety - Part 2-3: Particular requirements for electric irons Household and similar electrical appliances Safety - Part 2-4: Particular requirements for spin extractors Household and similar electrical appliances Safety - Part 2-5: Particular requirements for dishwashers Household and similar electrical appliances Safety - Part 2-6: Particular requirements for stationary cooking ranges, hobs, ovens and similar appliances Household and similar electrical appliances Safety - Part 2-7: Particular requirements for washing machines Household and similar electrical appliances Safety - Part 2-8: Particular requirements for shavers, hair clippers and similar appliances Household and similar electrical appliances Safety - Part 2-9: Particular requirements for grills, toasters and similar portable cooking appliances Household and similar electrical appliances Safety - Part 2-10: Particular requirements for floor treatment machines and wet scrubbing machines Household and similar electrical appliances Safety - Part 2-11: Particular requirements for tumble dryers Household and similar electrical appliances Safety - Part 2-12: Particular requirements for warming plates and similar appliances Household and similar electrical appliances Safety - Part 2-13: Particular requirements Page 346 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-14:2006 EN 60335-2-14:2006/A1:2008 EN 60335-2-14:2006/A11:2012 EN 60335-2-15:2002 superseded by FprEN 60335-2-15:2012 EN 60335-2-16:2003 EN 60335-2-16:2003/A1:2008 EN 60335-2-16:2003/A2:2012 EN 60335-2-17:2002 superseded by EN 60335-2-17:201X EN 60335-2-21:2003 superseded by EN 60335-2-21:201X EN 60335-2-23:2003 EN 60335-2-23:2003/A1:2008 EN 60335-2-23:2003/A11:2010 EN 60335-2-23:2003/A11:2010/AC:2012 EN 60335-2-24:2010 Household and similar electrical appliances Safety - Part 2-24: Particular requirements for refrigerating appliances, ice-cream appliances and ice makers Household and similar electrical appliances Safety - Part 2-25: Particular requirements for microwave ovens, including combination microwave ovens Household and similar electrical appliances Safety - Part 2-26: Particular requirements for clocks Household and similar electrical appliances Safety - Part 2-27: Particular requirements for appliances for skin exposure to ultraviolet and infrared radiation Household and similar electrical appliances Safety - Part 2-28: Particular requirements for sewing machines Household and similar electrical appliances Safety - Part 2-29: Particular requirements for battery chargers Household and similar electrical appliances - EN 60335-2-25:2012 EN 60335-2-26:2003 EN 60335-2-26:2003/A1:2008 EN 60335-2-27:2010 EN 60335-2-28:2003 EN 60335-2-28:2003/A1:2008 EN 60335-2-29:2004 EN 60335-2-29:2004/A2:2010 EN 60335-2-30:2009 V1.0 for deep fat fryers, frying pans and similar appliances Household and similar electrical appliances Safety - Part 2-14: Particular requirements for kitchen machines Household and similar electrical appliances Safety - Part 2-15: Particular requirements for appliances for heating liquids Household and similar electrical appliances Safety - Part 2-16: Particular requirements for food waste disposers Household and similar electrical appliances Safety - Part 2-17: Particular requirements for blankets, pads, clothing and similar flexible heating appliances Household and similar electrical appliances Safety - Part 2-21: Particular requirements for storage water heaters Household and similar electrical appliances Safety - Part 2-23: Particular requirements for appliances for skin or hair care 2013-01-15 Page 347 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-30:2009/A11:2012 EN 60335-2-31:2003 superseded by EN 60335-2-31:201X EN 60335-2-32:2003 EN 60335-2-32:2003/A1:2008 EN 60335-2-34:2002 superseded by EN 60335-2-34:201X EN 60335-2-35:2002 superseded by EN 60335-2-35:201X EN 60335-2-36:2002 EN 60335-2-36:2002/A1:2004 EN 60335-2-36:2002/A2:2008 EN 60335-2-36:2002/A11:2012 EN 60335-2-37:2002 EN 60335-2-37:2002/A1:2008 EN 60335-2-37:2002/A11:2012 EN 60335-2-38:2003 EN 60335-2-38:2003/A1:2008 EN 60335-2-39:2003 superseded by FprEN 60335-2-39:2012 EN 60335-2-40:2003 FprEN 60335-2-40:2012 EN 60335-2-41:2003 supervised by FprEN 60335-2-41:2012 EN 60335-2-42:2003 EN 60335-2-42:2003/A1:2008 EN 60335-2-42:2003/A11:2012 EN 60335-2-43:2003 EN 60335-2-43:2003/A1:2006 EN 60335-2-43:2003/A2:2008 V1.0 2013-01-15 Safety - Part 2-30: Particular requirements for room heaters Household and similar electrical appliances Safety - Part 2-31: Particular requirements for range hoods and other cooking fume extractors Household and similar electrical appliances Safety - Part 2-32: Particular requirements for massage appliances Household and similar electrical appliances Safety - Part 2-34: Particular requirements for motor-compressors Household and similar electrical appliances Safety - Part 2-35: Particular requirements for instantaneous water heaters Household and similar electrical appliances Safety - Part 2-36: Particular requirements for commercial electric cooking ranges, ovens, hobs and hob elements Household and similar electrical appliances Safety - Part 2-37: Particular requirements for commercial electric deep fat fryers Household and similar electrical appliances Safety - Part 2-38: Particular requirements for commercial electric griddles and griddle grills Household and similar electrical appliances Safety - Part 2-39: Particular requirements for commercial electric multi-purpose cooking pans Household and similar electrical appliances Safety - Part 2-40: Particular requirements for electrical heat pumps, air-conditioners and dehumidifiers Household and similar electrical appliances Safety - Part 2-41: Particular requirements for pumps Household and similar electrical appliances Safety - Part 2-42: Particular requirements for commercial electric forced convection ovens, steam cookers and steam-convection ovens Household and similar electrical appliances Safety - Part 2-43: Particular requirements for clothes dryers and towel rails Page 348 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-44:2002 EN 60335-2-44:2002/A1:2008 EN 60335-2-44:2002/A2:2012 EN 60335-2-45:2002 EN 60335-2-45:2002/A1:2008 EN 60335-2-45:2002/A2:2012 Household and similar electrical appliances Safety - Part 2-44: Particular requirements for ironers Household and similar electrical appliances Safety - Part 2-45: Particular requirements for portable heating tools and similar appliances EN 60335-2-47:2003 Household and similar electrical appliances EN 60335-2-47:2003/A1:2008 Safety - Part 2-47: Particular requirements EN 60335-2-47:2003/A11:2012 for commercial electric boiling pans EN 60335-2-48:2003 Household and similar electrical appliances EN 60335-2-48:2003/A1:2008 Safety - Part 2-48: Particular requirements EN 60335-2-48:2003/A11:2012 for commercial electric grillers and toasters EN 60335-2-49:2003 Household and similar electrical appliances EN 60335-2-49:2003/A1:2008 EN 60335-2- Safety - Part 2-49: Particular requirements 49:2003/A11:2012 for commercial electric appliances for keeping food and crockery warm EN 60335-2-50:2003 Household and similar electrical appliances EN 60335-2-50:2003/A1:2008 Safety - Part 2-50: Particular requirements for commercial electric bains-marie EN 60335-2-51:2003 Household and similar electrical appliances EN 60335-2-51:2003/A1:2008 Safety - Part 2-51: Particular requirements EN 60335-2-51:2003/A2:2012 for stationary circulation pumps for heating and service water installations EN 60335-2-52:2003 Household and similar electrical appliances EN 60335-2-52:2003/A1:2008 Safety - Part 2-52: Particular requirements EN 60335-2-52:2003/A11:2010 for oral hygiene appliances EN 60335-2-52:2003/A11:2010/AC:2012 EN 60335-2-53:2011 Household and similar electrical appliances Safety - Part 2-53: Particular requirements for sauna heating appliances and infrared cabins EN 60335-2-54:2008 Household and similar electrical appliances EN 60335-2-54:2008/A11:2012 Safety - Part 2-54: Particular requirements for surface-cleaning appliances for household use employing liquids or steam EN 60335-2-55:2003 Household and similar electrical appliances EN 60335-2-55:2003/A1:2008 Safety - Part 2-55: Particular requirements for electrical appliances for use with aquariums and garden ponds EN 60335-2-56:2003 Household and similar electrical appliances EN 60335-2-56:2003/A1:2008 Safety - Part 2-56: Particular requirements for projectors and similar appliances EN 60335-2-58:2005 Household and similar electrical appliances EN 60335-2-58:2005/A1:2008 Safety - Part 2-58: Particular requirements V1.0 2013-01-15 Page 349 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-58:2005/A11:2010 for commercial electric dishwashing machines Household and similar electrical appliances Safety - Part 2-59: Particular requirements for insect killers Household and similar electrical appliances Safety - Part 2-60: Particular requirements for whirlpool baths and whirlpool spas EN 60335-2-59:2003 EN 60335-2-59:2003/A1:2006 EN 60335-2-59:2003/A2:2009 EN 60335-2-60:2003 EN 60335-2-60:2003/A1:2005 EN 60335-2-60:2003/A2:2008 EN 60335-2-60:2003/A11:2010 EN 60335-2-60:2003/A12:2010 EN 60335-2-61:2003 EN 60335-2-61:2003/A1:2005 EN 60335-2-61:2003/A2:2008 EN 60335-2-62:2003 EN 60335-2-62:2003/A1:2008 Household and similar electrical appliances Safety - Part 2-61: Particular requirements for thermal-storage room heaters Household and similar electrical appliances Safety - Part 2-62: Particular requirements for commercial electric rinsing sinks Safety of household and similar electrical appliances - Part 2-64: Particular requirements for commercial electric kitchen machines Household and similar electrical appliances Safety - Part 2-65: Particular requirements for air-cleaning appliances Household and similar electrical appliances Safety - Part 2-66: Particular requirements for water-bed heaters Household and similar electrical appliances Safety - Part 2-67: Particular requirements for floor treatment machines for commercial use Household and similar electrical appliances Safety - Part 2-68: Particular requirements for spray extraction machines, for commercial use Household and similar electrical appliances Safety - Part 2-69: Particular requirements for wet and dry vacuum cleaners, including power brush for commercial use Household and similar electrical appliances Safety - Part 2-70: Particular requirements for milking machines Household and similar electrical appliances Safety - Part 2-71: Particular requirements for electrical heating appliances for breeding and rearing animals EN 60335-2-64:2000 EN 60335-2-64:2000/A1:2002 EN 60335-2-65:2003 EN 60335-2-65:2003/A1:2008 EN 60335-2-65:2003/A11:2012 EN 60335-2-66:2003 EN 60335-2-66:2003/A1:2008 EN 60335-2-66:2003/A2:2012 EN 60335-2-67:2012 EN 60335-2-68:2012 EN 60335-2-69:2012 EN 60335-2-70:2002 EN 60335-2-70:2002/A1:2007 EN 60335-2-71:2003 EN 60335-2-71:2003/A1:2007 V1.0 2013-01-15 Page 350 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-72:2012 Household and similar electrical appliances Safety - Part 2-72: Particular requirements for floor treatment machines with or without traction drive, for commercial use Household and similar electrical appliances Safety - Part 2-73: Particular requirements for fixed immersion heaters Household and similar electrical appliances Safety - Part 2-74: Particular requirements for portable immersion heaters Household and similar electrical appliances Safety - Part 2-75: Particular requirements for commercial dispensing appliances and vending machines EN 60335-2-73:2003 EN 60335-2-73:2003/A1:2006 EN 60335-2-73:2003/A2:2009 EN 60335-2-74:2003 EN 60335-2-74:2003/A1:2006 EN 60335-2-74:2003/A2:2009 EN 60335-2-75:2004 EN 60335-2-75:2004/A1:2005 EN 60335-2-75:2004/A2:2008 EN 60335-2-75:2004/A11:2006 EN 60335-2-75:2004/A12:2010 EN 60335-2-76:2005 EN 60335-2-76:2005/A1:2006 EN 60335-2-76:2005/A11:2008 EN 60335-2-76:2005/A12:2010 EN 60335-2-77:2010 Household and similar electrical appliances Safety - Part 2-76: Particular requirements for electric fence energizers Safety of household and similar appliances Part 2-77: Particular requirements for pedestrian-controlled walk-behind electrically powered lawn mowers Household and similar electrical appliances Safety - Part 2-78: Particular requirements for outdoor barbecues Household and similar electrical appliances Safety - Part 2-79: Particular requirements for high pressure cleaners and steam cleaners Household and similar electrical appliances Safety - Part 2-80: Particular requirements for fans Household and similar electrical appliances Safety - Part 2-81: Particular requirements for foot warmers and heating mats Household and similar electrical appliances Safety - Part 2-82: Particular requirements for amusement machines and personal service machines Household and similar electrical appliances Safety - Part 2-83: Particular requirements for heated gullies for roof drainage Household and similar electrical appliances Safety - Part 2-84: Particular requirements EN 60335-2-78:2003 EN 60335-2-78:2003/A1:2008 EN 60335-2-79:2012 EN 60335-2-80:2003 EN 60335-2-80:2003/A1:2004 EN 60335-2-80:2003/A2:2009 EN 60335-2-81:2003 EN 60335-2-81:2003/A1:2007 EN 60335-2-81:2003/A2:2012 EN 60335-2-82:2003 EN 60335-2-82:2003/A1:2008 EN 60335-2-83:2002 EN 60335-2-83:2002/A1:2008 EN 60335-2-84:2003 EN 60335-2-84:2003/A1:2008 V1.0 2013-01-15 Page 351 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot for toilets Household and similar electrical appliances Safety - Part 2-85: Particular requirements for fabric steamers Household and similar electrical appliances Safety - Part 2-86: Particular requirements for electric fishing machines Household and similar electrical appliances Safety - Part 2-87: Particular requirements for electrical animal-stunning equipment Household and similar electrical appliances Safety - Part 2-88: Particular requirements for humidifiers intended for use with heating, ventilation, or air-conditioning systems Household and similar electrical appliances Safety - Part 2-89: Particular requirements for commercial refrigerating appliances with an incorporated or remote refrigerant condensing unit or compressor Household and similar electrical appliances Safety - Part 2-90: Particular requirements for commercial microwave ovens Household and similar electrical appliances Safety - Part 2-91: Particular requirements for walk-behind and hand-held lawn trimmers and lawn edge trimmers Household and similar electrical appliances Safety - Part 2-92: Particular requirements for pedestrian-controlled mains-operated lawn scarifiers and aerators Household and similar electrical appliances Safety - Part 2-95: Particular requirements for drives for vertically moving garage doors for residential use Household and similar electrical appliances Safety - Part 2-96: Particular requirements for flexible sheet heating elements for room heating Household and similar electrical appliances Safety - Part 2-97: Particular requirements for drives for rolling shutters, awnings, blinds and similar equipment Household and similar electrical appliances Safety - Part 2-98: Particular requirements for humidifiers EN 60335-2-85:2003 EN 60335-2-85:2003/A1:2008 EN 60335-2-86:2003 EN 60335-2-86:2003/A1:2005 EN 60335-2-87:2002 EN 60335-2-87:2002/A1:2007 EN 60335-2-88:2002 EN 60335-2-89:2010 EN 60335-2-90:2006 EN 60335-2-90:2006/A1:2010 EN 60335-2-91:2003 EN 60335-2-92:2005 EN 60335-2-95:2004 EN 60335-2-96:2002 EN 60335-2-96:2002/A1:2004 EN 60335-2-96:2002/A2:2009 EN 60335-2-97:2006 EN 60335-2-97:2006/A2:2010 EN 60335-2-97:2006/A11:2008 EN 60335-2-98:2003 EN 60335-2-98:2003/A1:2005 EN 60335-2-98:2003/A2:2008 V1.0 2013-01-15 Page 352 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60335-2-99:2003 Household and similar electrical appliances Safety - Part 2-99: Particular requirements for commercial electric hoods Household and similar electrical appliances Safety - Part 2-101: Particular requirements for vaporizers Household and similar electrical appliances Safety - Part 2-102: Particular requirements for gas, oil and solid-fuel burning appliances having electrical connections Household and similar electrical appliances Safety - Part 2-103: Particular requirements for drives for gates, doors and windows Household and similar electrical appliances Safety - Part 2-105: Particular requirements for multifunctional shower cabinets Household and similar electrical appliances Safety - Part 2-106: Particular requirements for heated carpets and for heating units for room heating installed under removable floor coverings Household and similar electrical appliances Safety - Part 2-108: Particular requirements for electrolysers Household and similar electrical appliances Safety - Part 2-109: Particular requirements for UV radiation water treatment appliances EN 60335-2-101:2002 EN 60335-2-101:2002/A1:2008 EN 60335-2-102:2006 EN 60335-2-102:2006/A1:2010 EN 60335-2-103:2003 EN 60335-2-103:2003/A11:2009 EN 60335-2-105:2005 EN 60335-2-105:2005/A1:2008 EN 60335-2-105:2005/A11:2010 EN 60335-2-106:2007 EN 60335-2-108:2008 EN 60335-2-109:2010 Description This Standard deals with the safety of electrical appliances for household environment and commercial purposes, their rated voltage being not more than 250 V for single-phase and 480 V for others. EN 60598 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance V1.0 EN 60598 EN 60598: Luminaires Sensors & Actuators; Safety 29.140.40 - Luminaires This standard specifies general requirements all kinds of luminaires. see Standard Parts below IEC 60598 As AAL scenarios may include lighting scenarios (for guidance at night) 2013-01-15 Page 353 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot this standard should be taken into account. Available from see Standard Parts below Standard Parts Standard EN 60598-1:2008 superseded by FprEN 60598-1:2012 EN 60598-2-1:1989 EN 60598-2-2:2012 EN 60598-2-3:2003 EN 60598-2-3:2003/A1:2011 EN 60598-2-4:1997 EN 60598-2-5:1998 EN 60598-2-6:1994 EN 60598-2-6:1994/A1:1997 EN 60598-2-7:1989 EN 60598-2-7:1989/A2:1996 EN 60598-2-7:1989/A13:1997 EN 60598-2-8:1997 superseded by FprEN 60598-2-8:2012 EN 60598-2-9:1989 EN 60598-2-9:1989/A1:1994 EN 60598-2-10:2003 EN 60598-2-11:2005 superseded by FprEN 60598-2-11:2011 EN 60598-2-12:2006 superseded by FprEN 60598-2-12:2012 EN 60598-2-13:2006 EN 60598-2-13:2006/A1:2012 EN 60598-2-14:2009 V1.0 2013-01-15 Title Luminaires - Part 1: General requirements and tests Luminaires - Part 2: Particular requirements - Section 1: Fixed general purpose luminaires Luminaires - Part 2-2: Particular requirements - Recessed luminaires Luminaires - Part 2-3: Particular requirements - Luminaires for road and street lighting Luminaires - Part 2: Particular requirements - Section 4: Portable general purpose luminaires Luminaires - Part 2-5: Particular requirements - Floodlights Luminaires - Part 2: Particular requirements - Section 6: Luminaires with built-in transformers or convertors for filament lamps Luminaires - Part 2: Particular requirements - Section 7: Portable luminaires for garden use Luminaires - Part 2-8: Particular requirements - Handlamps Luminaires - Part 2: Particular requirements - Section 9: Photo and film luminaires (nonprofessional) Luminaires - Part 2-10: Particular requirements - Portable luminaires for children Luminaires - Part 2-11: Particular requirements - Aquarium luminaires Luminaires - Part 2-12: Particular requirements - Mains socket-outlet mounted nightlights Luminaires - Part 2-13: Particular requirements - Ground recessed luminaires Luminaires - Part 2-14: Particular requirements - Luminaires for cold cathode Page 354 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot tubular discharge lamps (neon tubes) and similar equipment Luminaires - Part 2: Particular requirements - Section 17: Luminaires for stage lighting, television film and photographic studios (outdoor and indoor) Luminaires - Part 2: Particular requirements - Section 18: Luminaires for swimming pools and similar applications Luminaires - Part 2: Particular requirements - Section 19: Air-handling luminaires (safety requirements) Luminaires - Part 2-20: Particular requirements - Lighting chains Luminaires - Part 2-22: Particular requirements - Luminaires for emergency lighting Luminaires - Part 2-23: Particular requirements - Extra low-voltage lighting systems for filament lamps Luminaires - Part 2: Particular requirements - Section 24: Luminaires with limited surface temperatures Luminaires - Part 2-25: Particular requirements - Luminaires for use in clinical areas of hospitals and health care buildings EN 60598-2-17:1989 EN 60598-2-17:1989/A2:1991 EN 60598-2-18:1994 EN 60598-2-18:1994/A1:2012 EN 60598-2-19:1989 EN 60598-2-19:1989/A2:1998 EN 60598-2-20:2010 EN 60598-2-22:1998 EN 60598-2-22:1998/A1:2003 EN 60598-2-22:1998/A2:2008 EN 60598-2-23:1996 EN 60598-2-23:1996/A1:2000 EN 60598-2-24:1998 EN 60598-2-25:1994 EN 60598-2-25:1994/A1:2004 Description EN 60598 specifies general requirements for luminaires, incorporating electric light sources for operation from supply voltages up to 1000 V. The requirements and related tests of this standard cover: classification, marking, mechanical construction and electrical construction. EN 60730 Profile Reference Name Categories ICS Abstract V1.0 EN 60730 EN 60730: Automatic electrical controls for household and similar use Sensors & Actuators; Safety Sensors & Actuators; Electromagnetic compatibility 97.120 - Automatic controls for household use EN 60730 applies to automatic electrical controls for use in, on, or in association with equipment for household and similar use, including controls for heating, air conditioning and similar applications. 2013-01-15 Page 355 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Current Version see Standard Parts below Other editions IEC 60730 AAL Relevance Often in the AAL automatic electrical controls are used, so it is important to establish a standard that standardize controls and make them safe. Available from see Standard Parts below Standard Parts Standard EN 60730-1:2011 superseded by FprEN 60730-1:2011 EN 60730-2-2:2002 superseded by FprEN 60730-2-22:2012 EN 60730-2-3:2007 EN 60730-2-4:2007 EN 60730-2-5:2002 superseded by FprEN 60730-2-5:2011 EN 60730-2-6:2008 EN 60730-2-7:2010 EN 60730-2-7:2010/AC:2011 EN 60730-2-8:2002 EN 60730-2-8:2002/A1:2003 EN 60730-2-9:2010 EN 60730-2-10:2007 V1.0 2013-01-15 Title Automatic electrical controls for household and similar use - Part 1: General requirements Automatic electrical controls for household and similar use – Part 2-22: Particular requirements for thermal motor protectors Automatic electrical controls for household and similar use - Part 2-3: Particular requirements for thermal protectors for ballasts for tubular fluorescent lamps Automatic electrical controls for household and similar use - Part 2-4: Particular requirements for thermal motor protectors for motor-compressors of hermetic and semi-hermetic type Automatic electrical controls for household and similar use - Part 2-5: Particular requirements for automatic electrical burner control systems Automatic electrical controls for household and similar use - Part 2-6: Particular requirements for automatic electrical pressure sensing controls including mechanical requirements Automatic electrical controls for household and similar use - Part 2-7: Particular requirements for timers and time switches Automatic electrical controls for household and similar use - Part 2-8: Particular requirements for electrically operated water valves, including mechanical requirements Automatic electrical controls for household and similar use - Part 2-9: Particular requirements for temperature sensing controls Automatic electrical controls for household Page 356 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot and similar use - Part 2-10: Particular requirements for motor-starting relays Automatic electrical controls for household and similar use - Part 2-11: Particular requirements for energy regulators Automatic electrical controls for household and similar use - Part 2-12: Particular requirements for electrically operated door locks Automatic electrical controls for household and similar use - Part 2-13: Particular requirements for humidity sensing controls Automatic electrical controls for household and similar use - Part 2-14: Particular requirements for electric actuators EN 60730-2-11:2008 EN 60730-2-12:2006 EN 60730-2-12:2006/A11:2008 EN 60730-2-13:2008 EN 60730-2-14:1997 EN 60730-2-14:1997/A1:2001 EN 60730-2-14:1997/A2:2008 EN 60730-2-14:1997/A11:2005 EN 60730-2-15:2010 Automatic electrical controls for household and similar use - Part 2-15: Particular requirements for automatic electrical air flow, water flow and water level sensing controls Automatic electrical controls for household and similar use - Part 2-19: Particular requirements for electrically operated oil valves, including mechanical requirements EN 60730-2-19:2002 EN 60730-2-19:2002/A2:2008 EN 60730-2-19:2002/A2:2008 Description EN 60730 applies to automatic electrical controls for use in, on, or in association with equipment for household and similar use, including controls for heating, air conditioning and similar applications. The equipment may use electricity, gas, oil, solid fuel, solar thermal energy, etc., or a combination thereof. This standard also applies to the inherent safety; to the operating values, operating times, and operating sequences where such are associated with equipment safety, and to the testing of automatic electrical control devices used in, or in association with, household or similar equipment. This standard is also applicable to controls for appliances within the scope of IEC 60335-1 as well as controls for building automation systems within the scope of ISO 16484-2.. [source: cenelec.eu] EN 60947 Profile Reference Name Categories ICS V1.0 EN 60947 EN 60947: Low-voltage switchgear Sensors & Actuators; Safety 29.130.20 - Low voltage switchgear and controlgear 2013-01-15 Page 357 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract Applies, when required by the relevant product standard, to switchgear and controlgear hereinafter referred to as equipment and intended to be connected to circuits, the rated voltage of which does not exceed 1 000 V a.c. or 1 500 V [source: cenelec.eu] Current Version see Standard Parts below Other editions IEC 60947 AAL Relevance As AAL scenarios may include switch and control devices this standard should be taken into account. Available from see Standard Parts below Standard Parts Standard EN 60947-1:2007 EN 60947-1:2007/A1:2011 EN 60947-2:2006 EN 60947-2:2006/A1:2009 EN 60947-3:2009 EN 60947-3:2009/A1:2012 Title Low-voltage switchgear and controlgear - Part 1: General rules Low-voltage switchgear and controlgear - Part 2: Circuitbreakers Low-voltage switchgear and controlgear - Part 3: Switches, disconnectors, switch-disconnectors and fusecombination units EN 60947-4-1:2010 Low-voltage switchgear and controlgear - Part 4-1: EN 60947-4-1:2010/A1:2012 Contactors and motor-starters - Electromechanical contactors and motor-starters EN 60947-4-2:2012 Low-voltage switchgear and controlgear - Part 4-2: Contactors and motor-starters - AC semiconductor motor controllers and starters EN 60947-4-3:2000 Low-voltage switchgear and controlgear - Part 4-3: EN 60947-4-3:2000/A1:2006 Contactors and motor-starters - AC semiconductor EN 60947-4-3:2000/A2:2011 controllers and contactors for non-motor loads EN 60947-5-1:2004 Low-voltage switchgear and controlgear - Part 5-1: EN 60947-5-1:2004/A1:2009 Control circuit devices and switching elements Electromechanical control circuit devices EN 60947-5-2:2007 Low-voltage switchgear and controlgear - Part 5-2: EN 60947-5-2:2007/A1:2012 Control circuit devices and switching elements Proximity switches EN 60947-5-3:1999 Low-voltage switchgear and controlgear - Part 5-3: superseded by FprEN 60947-5- Control circuit devices and switching elements 3:2012 Requirements for proximity devices with defined behaviour under fault conditions (PDF) EN 60947-5-4:2003 Low-voltage switchgear and controlgear - Part 5-4: Control circuit devices and switching elements - Method of assessing the performance of low-energy contacts Special tests EN 60947-5-5:1997 Low-voltage switchgear and controlgear - Part 5-5: EN 60947-5-5:1997/A1:2005 Control circuit devices and switching elements Electrical emergency stop device with mechanical V1.0 2013-01-15 Page 358 of 490 AALIANCE2 EN 60947-5-6:2000 EN 60947-5-7:2003 EN 60947-5-8:2006 EN 60947-5-9:2007 EN 60947-6-1:2005 EN 60947-6-2:2003 EN 60947-6-2:2003/A1:2007 EN 60947-7-1:2009 EN 60947-7-2:2009 EN 60947-7-3:2009 EN 60947-8:2003 EN 60947-8:2003/A1:2006 EN 60947-8:2003/A2:2012 D4.1 Online Repository of Standards - Snapshot latching function Low-voltage switchgear and controlgear - Part 5-6: Control circuit devices and switching elements - DC interface for proximity sensors and switching amplifiers (NAMUR) Low-voltage switchgear and controlgear - Part 5-7: Control circuit devices and switching elements Requirements for proximity devices with analogue output Low-voltage switchgear and controlgear - Part 5-8: Control circuit devices and switching elements - Threeposition enabling switches Low-voltage switchgear and controlgear - Part 5-9: Control circuit devices and switching elements - Flow rate switches Low-voltage switchgear and controlgear - Part 6-1: Multiple function equipment - Transfer switching equipment Low-voltage switchgear and controlgear - Part 6-2: Multiple function equipment - Control and protective switching devices (or equipment) (CPS) Low-voltage switchgear and controlgear - Part 7-1: Ancillary equipment - Terminal blocks for copper conductors Low-voltage switchgear and controlgear - Part 7-2: Ancillary equipment - Protective conductor terminal blocks for copper conductors Low-voltage switchgear and controlgear - Part 7-3: Ancillary equipment - Safety requirements for fuse terminal blocks Low-voltage switchgear and controlgear - Part 8: Control units for built-in thermal protection (PTC) for rotating electrical machines Description Applies, when required by the relevant product standard, to switchgear and controlgear hereinafter referred to as equipment and intended to be connected to circuits, the rated voltage of which does not exceed 1 000 V a.c. or 1 500 V d.c. It does not apply to lowvoltage switchgear and controlgear assemblies which are dealt with in EN 60439. The object of this standard is to state those general rules and requirements which are common to low-voltage equipment as defined in 1.1, including for example: - definitions; characteristics; - information supplied with the equipment; - normal service, mounting and transport conditions; - constructional and performance requirements; - verification of characteristics and performance. [source: webshop.ds.dk] V1.0 2013-01-15 Page 359 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60950 Profile Reference Name Categories ICS EN 60950 EN 60950: Information technology equipment - Safety Sensors & Actuators; Safety; EN; CENELEC; Robots/ Robotics 35.020 - Information technology (IT) in general 35.260 - Office machines Abstract This standard is applicable to mains-powered or battery-powered information technology equipment. Current Version see Standard Parts below Other editions IEC 60950 AAL Relevance The safety of all the IT equipment is indispensable for the AAL Available from see Standard Parts below Standard Parts Standard EN 60950-1:2006 EN 60950-1:2006/AC:2011 EN 60950-1:2006/A1:2010 EN 60950-1:2006/A11:2009 EN 60950-1:2006/A12:2011 EN 60950-21:2003 EN 60950-22:2006 EN 60950-22:2006/A11:2008 EN 60950-23:2006 Title Information technology equipment - Safety - Part 1: General requirements Information technology equipment - Safety - Part 21: Remote power feeding Information technology equipment - Safety - Part 22: Equipment installed outdoors Information technology equipment - Safety - Part 23: Large data storage equipment Description This standard is applicable to mains-powered or battery-powered information technology equipment, including electrical business equipment and associated equipment, with a RATED VOLTAGE not exceeding 600 V. This standard is also applicable to such information technology equipment: - designed for use as telecommunication terminal equipment and TELECOMMUNICATION NETWORK infrastructure equipment, regardless of the source of power; - designed and intended to be connected directly to, or used as infrastructure equipment in, a CABLE DISTRIBUTION SYSTEM, regardless of the source of power; - designed to use the AC MAINS SUPPLY as a communication transmission medium. [source: webshop.ds.dk] V1.0 2013-01-15 Page 360 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 61000 Profile Reference Name Categories ICS Abstract EN 61000 EN 61000 : Electromagnetic compatibility (EMC) Sensors & Actuators; Safety; Robots/ Robotics 33.100.10 - Emission Electromagnetic compatibility (EMC) is the branch of electrical sciences which studies the unintentional generation, propagation and reception of electromagnetic energy with reference to the unwanted effects (Electromagnetic interference, or EMI) that such energy may induce. EN 61000 is the standard on this topic. Current Version see Standard Parts below Other editions IEC 61000 AAL Relevance As AAL systems include electrical devices EN 61000 is a relevant standard. Available from see Standard Parts below Standard Parts Standard EN 61000-2-2:2002 EN 61000-2-10:1999 EN 61000-2-12:2003 EN 61000-4-1:2007 Title Electromagnetic compatibility (EMC) - Part 2-2: Environment Compatibility levels for low-frequency conducted disturbances and signalling in public low-voltage power supply systems Electromagnetic compatibility (EMC) - Part 2-10: Environment Description of HEMP environment - Conducted disturbance Electromagnetic compatibility (EMC) - Part 2-12: Environment Compatibility levels for low-frequency conducted disturbances and signalling in public medium-voltage power supply systems Electromagnetic compatibility (EMC) - Part 4-1: Testing and measurement techniques - Overview of IEC 61000-4 series Description EN 61000-2-2:2002 gives compatibility levels to be considered in public low-voltage supply systems with regard to the above-mentioned phenomena. Compatibility levels are intended to serve as reference values for trouble-free operation for equipment installed in public power supply systems. EN 61000-2-10:1999 defines the high-altitude electromagnetic pulse (HEMP) conducted environment that is one of the consequences of a high-altitude nuclear explosion. Establishes a common reference for this environment in order to select realistic stresses to apply to victim equipment for evaluating their performance. Presents the conducted HEMP environment induced on metallic lines, such as cables or power lines, external and internal to installations, and external antennas. EN 61000-2-12:2003 is concerned with conducted disturbances in the frequency range from 0 kHz to 9 kHz, with an extension up to 148,5 kHz specifically for mains signalling V1.0 2013-01-15 Page 361 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot systems. Compatibility levels are specified for electromagnetic disturbances of the types which can be expected in public medium voltage power supply systems, for guidance in: a) the limits to be set for disturbance emission into public power supply systems (including the planning levels defined in 3.1.5); b) the immunity limits to be set by product committees and others for the equipment exposed to the conducted disturbances present in public power supply systems. The disturbance phenomena considered are: voltage fluctuations and flicker, harmonics up to and including order 50, inter-harmonics up to the 50th harmonic, voltage distortions at higher frequencies (above 50th harmonic), voltage dips and short supply interruptions, voltage unbalance, transient overvoltages, power frequency variation, d.c. components, mains signalling. The medium-voltage systems covered by this standard are public distribution systems supplying either: a) private installations in which equipment is connected directly or through transformers, or b) substations feeding public low-voltage distribution systems. The object of EN 61000-4-1:2007 is to give applicability assistance to the technical committees of IEC or other bodies, users and manufacturers of electrical and electronic equipment on EMC standards within the IEC 61000-4 series on testing and measurement techniques and to provide general recommendations concerning the choice of relevant tests. This standard has the status of a basic EMC publication in accordance with IEC Guide 107. [source: cenelec.eu] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on 9.2. Safety for non-industrial robots ISO/DIS 13482 Profile Reference Name ISO/DIS 13482 ISO/DIS 13482: Robots and robotic devices – Safety requirements for non-industrial robots – Non-medical personal care robot Categories Sensors & Actuators; Safety for non-industrial robot; ISO; Robots/ Robotics ICS 25.040.30: Industrial robots. Manipulators Abstract In this standard requirements and guidelines for the development of non-industrial robot are given, so to reduce the hazards connected to the use of robot and robotic devices in non-industrial environment. Current Version ISO/DIS 13482 under development Other editions AAL Relevance As AAL scenarios may include robots this standard is relevant. V1.0 2013-01-15 Page 362 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=53820 Description Because of the newly emerging robots and robotic devices for non-industrial applications, it is necessary to give some safety requirements for the development of new devices working in a non-industrial environment and/or interacting with human. This International Standard gives necessity and guidelines for the safe design, protective measures and information for use of personal care robots. A list of hazard is given and requirements to reduce the risks associated with them as well. Definition of personal care robot is also given. ISO/DIS 13482 covers also the personal care robot and human-robot physical contact application. It is limited to earthbound robots. 9.3. Electromagnetic compatibility EN 50130-4 Profile Reference Name EN 50130-4 EN 50130-4: Alarm systems - Part 4: Electromagnetic compatibility Product family standard: Immunity requirements for components of fire, intruder, hold up, CCTV, access control and social alarm systems Categories Sensors & Actuators; Electromagnetic compatibility ICS 13.320 - Alarm and warning systems 29.020 - Electrical engineering in general Abstract This EMC product-family standard, for immunity requirements, applies to the components of the alarm systems, intended for use in and around buildings in residential, commercial, light industrial and industrial environments. Current Version EN 50130-4:2011 Other editions AAL Relevance The functionality of AAL-specific devices must not be affected by electromagnetic interference. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:2433964281766777::::FSP_PROJECT:22803 Description This EMC product-family standard, for immunity requirements, applies to the components of the following alarm systems, intended for use in and around buildings in residential, commercial, light industrial and industrial environments: • access control systems, for security applications V1.0 2013-01-15 Page 363 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • alarm transmission systems • CCTV systems, for security applications • fire detection and fire alarm systems • hold-up alarm systems • intruder alarm systems • social alarm systems The tests and severities to be used are the same for indoor and outdoor applications of fixed, movable and portable equipment. The levels do not cover extreme cases, which may occur in any location, but with an extremely low probability of occurrence, or in special locations close to powerful emitters (e.g. radar transmitters). Equipment within the scope of this standard should be designed in order to operate satisfactorily in the environmental electromagnetic conditions of residential, commercial, light industrial and industrial environments. This implies particularly that it should be able to operate correctly within the conditions fixed by the electromagnetic compatibility levels for the various disturbances on the low voltage public supply system as defined by EN 61000 2 2. The immunity tests in this standard only concern the most critical disturbance phenomena. For equipment using radio signalling, mains signalling or with connections to the public telephone system, additional requirements, from other standards specific to these signalling media, might apply. This standard does not specify basic safety requirements, such as protection against electrical shocks, unsafe operation, insulation coordination and related dielectric tests. This standard does not cover EMC emission requirements. These are covered by other appropriate standards. External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55013 Profile Reference Name Categories ICS Abstract V1.0 EN 55013 EN 55013: Sound and television broadcast receivers and associated equipment - Radio disturbance characteristics - Limits and methods of measurement Sensors & Actuators; Electromagnetic compatibility 33.100.10 - Emission Applies to the generation of electromagnetic energy from sound and television receivers for the reception of broadcast and similar transmissions and from associated equipment. Describes the methods of measurement applicable to sound and television receivers or associated equipment and specifies limits for the control of disturbance 2013-01-15 Page 364 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot from such equipment. The frequency range covered extends from 9 kHz to 400 GHz. Current Version see Standard Parts below Other editions AAL Relevance As such devices are normally in AAL homes, this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 55013:2001 EN 55013:2001/A1:2003 EN 55013:2001/A2:2006 EN 55013:2001/IS1:2009 FprEN 55013:2009 Title Sound and television broadcast receivers and associated equipment - Radio disturbance characteristics - Limits and methods of measurement External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55014 Profile Reference Name EN 55014 EN 55014: Electromagnetic compatibility - Requirements for household appliances, electric tools and similar apparatus Categories Sensors & Actuators; Electromagnetic compatibility ICS 33.100 - Electromagnetic compatibility (EMC) 33.100.10 - Emission Abstract Deals with the electromagnetic immunity of appliances and similar apparatus for household and similar purposes that use electricity, as well as electric toys and electric tools, the rated voltage of the apparatus being not more than 250 V for single-phase apparatus to be connected to phase and neutral, and 480 V for other apparatus. Current Version see Standard Parts below Other editions AAL Relevance It is necessary to be sure that every device does not interfere with the other devices in smart homes. Available from see Standard Parts below Standard Parts Standard EN 55014-1:2006 V1.0 Title Electromagnetic compatibility - Requirements for 2013-01-15 Page 365 of 490 AALIANCE2 EN 55014-1:2006/A1:2009 EN 55014-1:2006/A2:2011 EN 55014-2:1997 EN 55014-2:1997/Corr.:1998 EN 55014-2:1997/A1:2001 EN 55014-2:1997/A2:2008 EN 55014-2:1997/IS1:2007 D4.1 Online Repository of Standards - Snapshot household appliances, electric tools and similar apparatus - Part 1: Emission Electromagnetic compatibility - Requirements for household appliances, electric tools and similar apparatus - Part 2: Immunity - Product family standard Description EN 55014-1 applies to the conduction and the radiation of radio-frequency disturbances from appliances whose main functions are performed by motors and switching or regulating devices, unless the r.f. energy is intentionally generated or intended for illumination. It includes such equipment as: household electrical appliances, electric tools, regulating controls using semiconductor devices, motor-driven electro-medical apparatus, electric/ electronic toys, automatic dispensing machines as well as cine or slide projectors. [source: IHS.com] EN 55014-2 specifies the immunity requirements in relation to continuous and transient, conducted and radiated electromagnetic disturbances, including electrostatic discharges, for the above-mentioned apparatus. Apparatus may incorporate motors, heating elements or their combination, may contain electric or electronic circuitry, and may be powered by the mains, by batteries, or by any other electrical power source. Immunity requirements in the frequency range 0 Hz to 400 GHz are covered. [Source: CENELEC] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55015 Profile Reference Name EN 55015 EN 55015: Limits and methods of measurement of radio disturbance characteristics of electrical lighting and similar equipment Categories Sensors & Actuators; Electromagnetic compatibility ICS 33.100.10 - Emission Abstract This standard applies to the emission (radiated and conducted) of radiofrequency disturbances from electrical lighting and similar equipment. Current Version EN 55015:2006 Other editions AAL Relevance As electrical lighting devices are normally in AAL homes, this standard V1.0 2013-01-15 Page 366 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot is relevant. Available from see Standard Parts below Standard Parts Standard EN 55015:2006 EN 55015:2006/A1:2007 EN 55015:2006/A2:2009 EN 55015:2006/FprA3:2011 Title Limits and methods of measurement of radio disturbance characteristics of electrical lighting and similar equipment Description This standard applies to the emission (radiated and conducted) of radiofrequency disturbances from: • all lighting equipment with a primary function of generating and/or distributing light intended for illumination purposes, and intended either for connection to the low voltage electricity supply or for battery operation • the lighting part of multi-function equipment where one of the primary functions of this is illumination • independent auxiliaries exclusively for use with lighting equipment • UV and IR radiation equipment • neon advertising signs • street/flood lighting intended for outdoor use • transport lighting (installed in buses and trains). Excluded from the scope of this standard are: • lighting equipment operating in the ISM frequency bands (as defined in Resolution 63 (1979) of the ITU Radio Regulation) • lighting equipment for aircraft and airports • apparatus for which the electromagnetic compatibility requirements in the radiofrequency range are explicitly formulated in other IEC or CISPR standards. NOTE Examples are: • built-in lighting devices in other equipment, for example scale illumination or neon devices • photocopiers • slide projectors • lighting equipment for road vehicles. The frequency range covered is 9 kHz to 400 GHz. Multi-function equipment which is subjected simultaneously to different clauses of this standard and/or other standards shall meet the provisions of each clause/standard with the relevant functions in operation. The limits in this standard have been determined on a probabilistic basis to keep the V1.0 2013-01-15 Page 367 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot suppression of disturbances within economically reasonable limits while still achieving an adequate level of radio protection and electromagnetic compatibility. In exceptional cases, additional provisions may be required. [source: webshop.ds.dk] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55020 Profile Reference Name EN 55020 EN 55020: Sound and television broadcast receivers and associated equipment - Immunity characteristics - Limits and methods of measurement Categories Sensors & Actuators; Electromagnetic compatibility ICS 33.100.20 - Immunity Abstract Applies to television broadcast receivers, sound broadcast receivers and associated equipment intended for use in the residential, commercial and light industrial environment. Describes the methods of measurement and specified limits applicable to sound and television receivers and to associated equipment with regard to their immunity characteristics to disturbing signals. Current Version see Standard Parts below Other editions AAL Relevance As such devices are normally in AAL homes, this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 55020:2007 EN 55020:2007/IS1:2009 EN 55020:2007/IS2:2010 EN 55020:2007/A11:2011 EN 55020:2007/FprA1:2012 Title Sound and television broadcast receivers and associated equipment - Immunity characteristics - Limits and methods of measurement Description Applies to television broadcast receivers, sound broadcast receivers and associated equipment intended for use in the residential, commercial and light industrial environment. Describes the methods of measurement and specified limits applicable to sound and television receivers and to associated equipment with regard to their immunity characteristics to disturbing signals. This standard is also applicable to the immunity of V1.0 2013-01-15 Page 368 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot outdoor units of direct to home (DTH) satellite receiving systems for individual reception. Immunity requirements are given in the frequency range 0 Hz to 400 GHz. Radiofrequency tests outside the specified frequency bands or concerning other phenomena than given in this standard are not required. The objective of this standard is to define the immunity test requirements for equipment defined in the scope in relation to continuous and transient, conducted and radiated disturbances including electrostatic discharges. These test requirements represent essential electromagnetic immunity requirements. Test requirements are specified for each port (enclosure or connector) considered. The environments encompassed by this standard are residential, commercial and lightindustrial locations, both indoor and outdoor. The following list, although not comprehensive, gives an indication of locations which are included: • residential properties, e.g. houses, apartments, etc. • retail outlets, e.g. shops, supermarkets, etc. • business premises, e.g. offices, banks, etc. • areas of public entertainment, e.g. cinemas, public bars, dance halls, etc. • outdoor locations, e.g. petrol stations, car parks, amusement and sports centres, etc. • light-industrial locations e.g. workshops, laboratories, service centres, etc. • car and boat. Locations which are characterized by their mains power being supplied directly at low voltage from the public mains are considered to be residential, commercial or light industrial. [Source: CENELEC] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55022 Profile Reference Name EN 55022 EN 55022: Information technology equipment - Radio disturbance characteristics - Limits and methods of measurement Categories Sensors & Actuators; Electromagnetic compatibility ICS 33.100.10 - Emission Abstract Applies to information technology equipment (ITE). Procedures are given for the measurement of the levels of spurious signals generated by the ITE and limits are specified for the frequency range 9 kHz to 400 GHz for both class A and class B equipment. Current Version see Standard Parts below V1.0 2013-01-15 Page 369 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance It is important to define the limits for the radio disturbance in a smart environment where more devices are present. Available from see Standard Parts below Standard Parts Standard EN 55022:2010 EN 55022:2010/AC:2011 Title Information technology equipment - Radio disturbance characteristics - Limits and methods of measurement Description This standard applies to information technology equipment (ITE). Procedures are given for the measurement of the levels of spurious signals generated by the ITE and limits are specified for the frequency range 9 kHz to 400 GHz for both class A and class B equipment. No measurements need be performed at frequencies where no limits are specified. The intention of this publication is to establish uniform requirements for the radio disturbance level of the equipment contained in the scope, to fix limits of disturbance, to describe methods of measurement and to standardize operating conditions and interpretation of results. [Source: CENELEC] External links • http://webstore.iec.ch/webstore/webstore.nsf/artnum/S042222?opendocument • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 55024 Profile Reference Name EN 55024 EN 55024: Information technology equipment - Immunity characteristics - Limits and methods of measurement Categories Sensors & Actuators; Electromagnetic compatibility ICS 33.100.20 - Immunity Abstract Defines the immunity test requirements for information technology equipment (ITE, as defined in CISPR 22) in relation to continuous and transient, conducted and radiated disturbances, including electrostatic discharges (ESD). Current Version EN 55024:2010 Other editions AAL Relevance As AAL homes normally contain information technology equipment, this standard is relevant. V1.0 2013-01-15 Page 370 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Available from http://www.cenelec.eu/dyn/www/f? p=104:110:3721925764008579::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:814,22298,25 Description EN 55024 defines the immunity test requirements for information technology equipment (ITE) in relation to continuous and transient, conducted and radiated disturbances, including electrostatic discharges (ESD). Procedures are defined for the measurement of ITE and limits are specified which are developed for ITE and within the frequency range from 0 Hz to 400 GHz. This publication establishes requirements which will provide an adequate level of intrinsic immunity so that the equipment will operate as intended in its environment. The test requirements are specified for each port considered. [Source: CENELEC] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 60601-1-2 Profile Reference Name EN 60601-1-2 EN 60601-1-2: Medical electrical equipment - Part 1-2: General requirements for basic safety and essential performance - Collateral standard: Electromagnetic compatibility - Requirements and tests (IEC 60601-1-2:2007, modified) Categories Sensors & Actuators; Electromagnetic compatibility ICS 11.040.01 - Medical equipment in general 33.100.10 - Emission 33.100.20 - Immunity Abstract This collateral standard applies to electromagnetic compatibility of medical electrical equipment and medical electrical systems. The object of this collateral standard is to specify general requirements and tests for electromagnetic compatibility of medical electrical equipment and medical electrical systems. Current Version see Standard Parts below Other editions AAL Relevance Medical electrical equipment and systems can be used in AAL homes. Therefore, they must not interfere with other electrical devices to protect their own functionality and the functionality of the other devices. Available from see Standard Parts below V1.0 2013-01-15 Page 371 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard EN 60601-1-2:2007 EN 60601-1-2:2007/AC:2010 FprEN 60601-1-2:2012 Title Medical electrical equipment - Part 1-2: General requirements for basic safety and essential performance - Collateral standard: Electromagnetic disturbances - Requirements and tests Description This collateral standard applies to electromagnetic compatibility of medical electrical equipment and medical electrical systems. The object of this collateral standard is to specify general requirements and tests for electromagnetic compatibility of medical electrical equipment and medical electrical systems. They are in addition to the requirements of the general standard and serve as the basis for particular standards. This edition of IEC 60601-1-2 was revised to structurally align it with the 2005 edition of IEC 60601-1 and to implement the decision of IEC subcommittee 62A that the clause numbering structure of collateral standards written to IEC 60601-1:2005 would adhere to the form specified in ISO/IEC Directives, Part 2:2004. The principle technical changes are in Clause 4, which now recognizes that there is a general requirement for a risk management process in IEC 60601-1:2005. [Source: CENELEC] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 60601-1-11 Profile Reference Name EN 60601-1-11 EN 60601-1-11: Medical electrical equipment - Part 1-11: General requirements for basic safety and essential performance - Collateral standard: Requirements for medical electrical equipment and medical electrical systems used in the home healthcare environment (IEC 60601-1-11:2010) Categories Sensors & Actuators; Electromagnetic compatibility ICS 11.040 - Medical equipment Abstract It applies to the basic safety and essential performance of medical electrical equipment and medical electrical systems which are intended by their manufacturer for use in the home healthcare environment, regardless of whether the medical electrical equipment or medical electrical system is intended for use by a lay operator or by trained healthcare personnel. Current Version EN 60601-1-11:2010 V1.0 2013-01-15 Page 372 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance This standard considers medical electrical equipment and systems that were manufactured for the use in domestic environments, e.g. in AAL homes. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:3721925764008579::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:68,22366,25 Description EN 60601-1-11 applies to the basic safety and essential performance of medical electrical equipment and medical electrical systems which are intended by their manufacturer for use in the home healthcare environment, regardless of whether the medical electrical equipment or medical electrical system is intended for use by a lay operator or by trained healthcare personnel. The object of EN 60601-1-11:2010 is to specify general requirements that are in addition to those of the general standard EN 60601-1:2005 and to serve as the basis for particular standards. It is the recommendation of the committee that the content of this publication be adopted for implementation nationally not earlier than 3 years from the date of publication. [Source: CENELEC] External links • http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030155522 for information about BS EN 60601-1-11:2010 EN 60669-2 Profile Reference Name EN 60669-2 EN 60669-2: Switches for household and similar fixed electrical installations Categories Sensors & Actuators; Electromagnetic compatibility; EN; CENELEC ICS 29.120.40 - Switches Abstract Applies to manually operated general purpose switches for a.c. only, with a rated voltage not exceeding 440 V and a rated current not exceeding 63 A. [source: cenelec.eu] Current Version see Standard Parts below Other editions IEC 60669 AAL Relevance As AAL scenarios include switches this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 60669-1:1999 V1.0 Title Switches for household and similar fixed2013-01-15 Page 373 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN 60669-1:1999/IS1:2009 superseded by FprEN 60669-1:2011 EN 60669-2-1:2004 EN 60669-2-1:2004/A1:2009 EN 60669-2-1:2004/A12:2010 EN 60669-2-2:2006 EN 60669-2-3:2006 EN 60669-2-4:2005 EN 60669-2-6:2012 electrical installations - Part 1: General requirements Switches for household and similar fixed electrical installations - Part 2-1: Particular requirements - Electronic switches Switches for household and similar fixed electrical installations - Part 2-2: Particular requirements - Electromagnetic remote-control switches (RCS) Switches for household and similar fixed electrical installations - Part 2-3: Particular requirements - Time delay switches (TDS) Switches for household and similar fixed electrical installations - Part 2-4: Particular requirements - Isolating switches Switches for household and similar fixed electrical installations - Part 2-6: Particular requirements - Fireman's switches for exterior and interior signs and luminaires Description Applies to manually operated general purpose switches for a.c. only, with a rated voltage not exceeding 440 V and a rated current not exceeding 63 A. The rated current is limited to 16 A for switches provided with screwless terminals. Unless otherwise specified in subsequent parts, this standard applies to switches intended to be used at 50 Hz. [source: webshop.ds.dk] EN 60730 Profile Reference Name Categories EN 60730 EN 60730: Automatic electrical controls for household and similar use Sensors & Actuators; Safety Sensors & Actuators; Electromagnetic compatibility ICS 97.120 - Automatic controls for household use Abstract EN 60730 applies to automatic electrical controls for use in, on, or in association with equipment for household and similar use, including controls for heating, air conditioning and similar applications. Current Version see Standard Parts below Other editions IEC 60730 AAL Relevance Often in the AAL automatic electrical controls are used, so it is important to establish a standard that standardize controls and make them safe. Available from see Standard Parts below V1.0 2013-01-15 Page 374 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard EN 60730-1:2011 superseded by FprEN 60730-1:2011 EN 60730-2-2:2002 superseded by FprEN 60730-2-22:2012 EN 60730-2-3:2007 EN 60730-2-4:2007 EN 60730-2-5:2002 superseded by FprEN 60730-2-5:2011 EN 60730-2-6:2008 EN 60730-2-7:2010 EN 60730-2-7:2010/AC:2011 EN 60730-2-8:2002 EN 60730-2-8:2002/A1:2003 EN 60730-2-9:2010 EN 60730-2-10:2007 EN 60730-2-11:2008 EN 60730-2-12:2006 EN 60730-2-12:2006/A11:2008 V1.0 2013-01-15 Title Automatic electrical controls for household and similar use - Part 1: General requirements Automatic electrical controls for household and similar use – Part 2-22: Particular requirements for thermal motor protectors Automatic electrical controls for household and similar use - Part 2-3: Particular requirements for thermal protectors for ballasts for tubular fluorescent lamps Automatic electrical controls for household and similar use - Part 2-4: Particular requirements for thermal motor protectors for motor-compressors of hermetic and semi-hermetic type Automatic electrical controls for household and similar use - Part 2-5: Particular requirements for automatic electrical burner control systems Automatic electrical controls for household and similar use - Part 2-6: Particular requirements for automatic electrical pressure sensing controls including mechanical requirements Automatic electrical controls for household and similar use - Part 2-7: Particular requirements for timers and time switches Automatic electrical controls for household and similar use - Part 2-8: Particular requirements for electrically operated water valves, including mechanical requirements Automatic electrical controls for household and similar use - Part 2-9: Particular requirements for temperature sensing controls Automatic electrical controls for household and similar use - Part 2-10: Particular requirements for motor-starting relays Automatic electrical controls for household and similar use - Part 2-11: Particular requirements for energy regulators Automatic electrical controls for household and similar use - Part 2-12: Particular Page 375 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot requirements for electrically operated door locks Automatic electrical controls for household and similar use - Part 2-13: Particular requirements for humidity sensing controls Automatic electrical controls for household and similar use - Part 2-14: Particular requirements for electric actuators EN 60730-2-13:2008 EN 60730-2-14:1997 EN 60730-2-14:1997/A1:2001 EN 60730-2-14:1997/A2:2008 EN 60730-2-14:1997/A11:2005 EN 60730-2-15:2010 Automatic electrical controls for household and similar use - Part 2-15: Particular requirements for automatic electrical air flow, water flow and water level sensing controls Automatic electrical controls for household and similar use - Part 2-19: Particular requirements for electrically operated oil valves, including mechanical requirements EN 60730-2-19:2002 EN 60730-2-19:2002/A2:2008 EN 60730-2-19:2002/A2:2008 Description EN 60730 applies to automatic electrical controls for use in, on, or in association with equipment for household and similar use, including controls for heating, air conditioning and similar applications. The equipment may use electricity, gas, oil, solid fuel, solar thermal energy, etc., or a combination thereof. This standard also applies to the inherent safety; to the operating values, operating times, and operating sequences where such are associated with equipment safety, and to the testing of automatic electrical control devices used in, or in association with, household or similar equipment. This standard is also applicable to controls for appliances within the scope of IEC 60335-1 as well as controls for building automation systems within the scope of ISO 16484-2.. [source: cenelec.eu] EN 60870-2-1 Profile Reference Name EN 60870-2-1 EN 60870-2-1: Telecontrol equipment and systems - Part 2: Operating conditions; section 1: Power supply and electromagnetic compatibility (IEC 60870-2-1:1995) Categories Sensors & Actuators; Electromagnetic compatibility ICS 29.020 - Electrical engineering in general 33.200 - Telecontrol. Telemetering Abstract EN 60870-2-1 specifies classes for environmental conditions under which telecontrol equipment has to operate. Current Version EN 60870-2-1:1996 Other editions V1.0 2013-01-15 Page 376 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance As AAL scenarios may include telecontrol components this standard may be relevant. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:3721925764008579::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:10649,6822,25 Description This standard part applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and control of geographically widespread processes. It is also a reference document for teleprotection equipment and systems and for equipment included in a distribution line carrier (DLC) system supporting a distribution automation system (DAS). [source: webshop.ds.dk] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 60947 Profile Reference Name Categories ICS Abstract EN 60947 EN 60947: Low-voltage switchgear Sensors & Actuators; Safety 29.130.20 - Low voltage switchgear and controlgear Applies, when required by the relevant product standard, to switchgear and controlgear hereinafter referred to as equipment and intended to be connected to circuits, the rated voltage of which does not exceed 1 000 V a.c. or 1 500 V [source: cenelec.eu] Current Version see Standard Parts below Other editions IEC 60947 AAL Relevance As AAL scenarios may include switch and control devices this standard should be taken into account. Available from see Standard Parts below Standard Parts Standard EN 60947-1:2007 EN 60947-1:2007/A1:2011 EN 60947-2:2006 EN 60947-2:2006/A1:2009 EN 60947-3:2009 V1.0 Title Low-voltage switchgear and controlgear - Part 1: General rules Low-voltage switchgear and controlgear - Part 2: Circuit-breakers Low-voltage switchgear and controlgear - Part 3: 2013-01-15 Page 377 of 490 AALIANCE2 EN 60947-3:2009/A1:2012 EN 60947-4-1:2010 EN 60947-4-1:2010/A1:2012 EN 60947-4-2:2012 EN 60947-4-3:2000 EN 60947-4-3:2000/A1:2006 EN 60947-4-3:2000/A2:2011 EN 60947-5-1:2004 EN 60947-5-1:2004/A1:2009 EN 60947-5-2:2007 EN 60947-5-2:2007/A1:2012 EN 60947-5-3:1999 superseded by FprEN 60947-53:2012 EN 60947-5-4:2003 EN 60947-5-5:1997 EN 60947-5-5:1997/A1:2005 EN 60947-5-6:2000 EN 60947-5-7:2003 EN 60947-5-8:2006 EN 60947-5-9:2007 EN 60947-6-1:2005 V1.0 D4.1 Online Repository of Standards - Snapshot Switches, disconnectors, switch-disconnectors and fuse-combination units Low-voltage switchgear and controlgear - Part 4-1: Contactors and motor-starters - Electromechanical contactors and motor-starters Low-voltage switchgear and controlgear - Part 4-2: Contactors and motor-starters - AC semiconductor motor controllers and starters Low-voltage switchgear and controlgear - Part 4-3: Contactors and motor-starters - AC semiconductor controllers and contactors for non-motor loads Low-voltage switchgear and controlgear - Part 5-1: Control circuit devices and switching elements Electromechanical control circuit devices Low-voltage switchgear and controlgear - Part 5-2: Control circuit devices and switching elements Proximity switches Low-voltage switchgear and controlgear - Part 5-3: Control circuit devices and switching elements Requirements for proximity devices with defined behaviour under fault conditions (PDF) Low-voltage switchgear and controlgear - Part 5-4: Control circuit devices and switching elements Method of assessing the performance of low-energy contacts - Special tests Low-voltage switchgear and controlgear - Part 5-5: Control circuit devices and switching elements Electrical emergency stop device with mechanical latching function Low-voltage switchgear and controlgear - Part 5-6: Control circuit devices and switching elements - DC interface for proximity sensors and switching amplifiers (NAMUR) Low-voltage switchgear and controlgear - Part 5-7: Control circuit devices and switching elements Requirements for proximity devices with analogue output Low-voltage switchgear and controlgear - Part 5-8: Control circuit devices and switching elements Three-position enabling switches Low-voltage switchgear and controlgear - Part 5-9: Control circuit devices and switching elements - Flow rate switches Low-voltage switchgear and controlgear - Part 6-1: Multiple function equipment - Transfer switching 2013-01-15 Page 378 of 490 AALIANCE2 EN 60947-6-2:2003 EN 60947-6-2:2003/A1:2007 EN 60947-7-1:2009 EN 60947-7-2:2009 EN 60947-7-3:2009 EN 60947-8:2003 EN 60947-8:2003/A1:2006 EN 60947-8:2003/A2:2012 D4.1 Online Repository of Standards - Snapshot equipment Low-voltage switchgear and controlgear - Part 6-2: Multiple function equipment - Control and protective switching devices (or equipment) (CPS) Low-voltage switchgear and controlgear - Part 7-1: Ancillary equipment - Terminal blocks for copper conductors Low-voltage switchgear and controlgear - Part 7-2: Ancillary equipment - Protective conductor terminal blocks for copper conductors Low-voltage switchgear and controlgear - Part 7-3: Ancillary equipment - Safety requirements for fuse terminal blocks Low-voltage switchgear and controlgear - Part 8: Control units for built-in thermal protection (PTC) for rotating electrical machines Description Applies, when required by the relevant product standard, to switchgear and controlgear hereinafter referred to as equipment and intended to be connected to circuits, the rated voltage of which does not exceed 1 000 V a.c. or 1 500 V d.c. It does not apply to lowvoltage switchgear and controlgear assemblies which are dealt with in EN 60439. The object of this standard is to state those general rules and requirements which are common to low-voltage equipment as defined in 1.1, including for example: - definitions; characteristics; - information supplied with the equipment; - normal service, mounting and transport conditions; - constructional and performance requirements; - verification of characteristics and performance. [source: webshop.ds.dk] EN 61547 Profile Reference Name EN 61547 EN 61547: Equipment for general lighting purposes - EMC immunity requirements Categories Sensors & Actuators; Electromagnetic compatibility ICS 29.020 - Electrical engineering in general 29.140 - Lamps and related equipment 33.100.10 - Emission Abstract It applies to lighting equipment which is within the scope of IEC Technical Committee 34, such as lamps, auxiliaries and luminaires, intended either for connecting to a low voltage electricity supply or for battery operation. Current Version EN 61547:2009 V1.0 2013-01-15 Page 379 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance The addressed devices are also used in AAL homes and should not interfere with other devices. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:3721925764008579::::FSP_ORG_ID,FSP_PROJECT,FSP_ LANG_ID:108,21712,25 Description This International Standard for electromagnetic immunity requirements applies to lighting equipment which is within the scope of IEC technical committee 34, such as lamps, auxiliaries and luminaires, intended either for connecting to a low voltage electricity supply or for battery operation. Excluded from the scope of this standard is equipment for which the immunity requirements are formulated in other IEC or CISPR standards such as: • lighting equipment for use in transport vehicles • entertainment lighting control equipment for professional purposes • lighting devices built into other equipment such as: • scale illumination or indicators • photocopiers • slide and overhead projectors • multimedia equipment However, in multi-function equipment where the lighting part operates independently from other parts, the electromagnetic immunity requirements of this standard apply to the lighting part. The requirements of this standard are based on the requirements for domestic, commercial and light-industrial environments as given in IEC 61000-6-1, but modified to lighting engineering practice. It can be expected that lighting equipment complying with the requirements of this standard will operate satisfactorily in other environments. In some special cases, measures have to be taken to provide higher immunity. It is impracticable to deal with all these possibilities. Such requirements may be established by contractual agreement between supplier and purchaser. [source: webshop.ds.dk] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) for further information on EN 61800-3 Profile Reference Name V1.0 EN 61800-3 EN 61800-3: Adjustable speed electrical power drive systems - Part 3: 2013-01-15 Page 380 of 490 AALIANCE2 Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot EMC requirements and specific test methods (IEC 61800-3:2004) Sensors & Actuators; Electromagnetic compatibility 29.200 - Rectifiers. Convertors. Stabilized power supply 33.100 - Electromagnetic compatibility (EMC) Specifies electromagnetic compatibility (EMC) requirements for power drive systems (PDSs). see Standard Parts below As PDSs can exist in AAL homes, this standard is relevant. see Standard Parts below Standard Parts Standard EN 61800-3:2004 EN 61800-3:2004/A1:2012 Title Adjustable speed electrical power drive systems - Part 3: EMC requirements and specific test methods Description This part of 61800 specifies electromagnetic compatibility (EMC) requirements for power drive systems (PDSs). A PDS is defined in 3.1. These are adjustable speed a.c. or d.c. motor drives. Requirements are stated for PDSs with converter input and/or output voltages (line-to-line voltage), up to 35 kV a.c. r.m.s. PDSs covered by this standard are those installed in residential, commercial and industrial locations with the exception of traction applications, and electric vehicles. PDSs may be connected to either industrial or public power distribution networks. Industrial networks are supplied by a dedicated distribution transformer, which is usually adjacent to or inside the industrial location, and supplies only industrial customers. Industrial networks can also be supplied by their own electric generating equipment. On the other hand, PDSs can be directly connected to lowvoltage public mains networks which also supply domestic premises, and in which the neutral is generally earthed (grounded). The scope of this part of IEC 61800, related to EMC, includes a broad range of PDSs from a few hundred watts to hundreds of megawatts. PDSs are often included in a larger system. The system aspect is not covered by this standard but guidance is provided in the informative annexes. [source: webshop.ds.dk] External links • http://en.wikipedia.org/w/index.php? title=Electromagnetic_compatibility&oldid=524793308 electromagnetic compatibility (EMC) V1.0 2013-01-15 for further information on Page 381 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 10. User Interfaces EN 60601-1-6 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN 60601-1-6 EN 60601-1-6: Medical electrical equipment - Part 1-6: General requirements for basic safety and essential performance - Collateral standard: Usability Medical devices, IEC, Usability, Safety 11.040 - Medical equipment IEC 60601-1-6:2010 specifies a process for a manufacturer to analyse, specify, design, verify and validate usability, as it relates to basic safety and essential performance of medical electrical equipment. 3 AAL products can include medical equipment, which should therefore ensure the respect of this standard. http://www.cenelec.eu/dyn/www/f? p=104:110:719249165943260::::FSP_ORG_ID,FSP_LANG_ID,FSP_P ROJECT:,25,22408# Description IEC 60601-1-6:2010 specifies a process for a manufacturer to analyse, specify, design, verify and validate usability, as it relates to basic safety and essential performance of medical electrical equipment. This usability engineering process assesses and mitigates risks caused by usability problems associated with correct use and use errors, i.e., normal use. It can be used to identify but does not assess or mitigate risks associated with abnormal use. If the usability engineering process detailed in this collateral standard has been complied with and the acceptance criteria documented in the usability validation plan have been met (see 5.9 of IEC 62366:2007), then the residual risks, as defined in ISO 14971, associated with usability of me equipment are presumed to be acceptable, unless there is objective evidence to the contrary (see 4.1.2 of IEC 62366:2007). External links • Wikipedia contributors, "IEC 60601," Wikipedia, The Free Encyclopedia, accessed January 13, 2013. EN 62366 Profile Reference V1.0 EN 62366 2013-01-15 Page 382 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name EN 62366: Medical devices - Application of usability engineering to medical devices Categories Medical device, IEC, Usability, Safety ICS 11.040.01 - Medical equipment in general Abstract Specifies a process for a manufacturer to analyse, specify, design, verify and validate usability, as it relates to safety of a medical device. Current Version 1 Other editions AAL Relevance AAL technologies include medical devices Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=38594 Description Specifies a process for a manufacturer to analyse, specify, design, verify and validate usability, as it relates to safety of a medical device. This usability engineering process assesses and mitigates risks caused by usability problems associated with correct use and use errors, i.e. normal use. It can be used to identify but does not assess or mitigate risks associated with abnormal use. If the usability engineering process detailed in this International Standard has been complied with and the acceptance criteria documented in the usability validation plan have been met, then the residual risks, as defined in ISO 14971, associated with usability of a medical device are presumed to be acceptable, unless there is objective evidence to the contrary. EN ISO 11064 Profile Reference Name Categories ICS Abstract EN ISO 11064 EN ISO 11064: Ergonomic design of control centres Accessibility 13.180 - Ergonomics EN ISO 11064 specifies standards on ergonomic design of control centres Current Version see Standard Parts below Other editions See below AAL Relevance As AAL services may include monitoring and security service providers this standard is relevant for their control centres. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=22470 Standard Parts Standard ISO 11064-1:2000 ISO 11064-2:2000 V1.0 Title Part 1: Principles for the design of control centres Part 2: Principles for the arrangement of control suites 2013-01-15 Page 383 of 490 AALIANCE2 ISO 11064-3:1999 ISO 11064-4:2004 ISO 11064-5:2008 ISO 11064-6:2005 ISO 11064-7:2006 D4.1 Online Repository of Standards - Snapshot Part 3: Control room layout Part 4: Layout and dimensions of workstations Part 5: Displays and controls Part 6: Environmental requirements for control centres Part 7: Principles for the evaluation of control centres Description ISO 11064-7:2006 establishes ergonomic principles for the evaluation of control centres. It gives requirements, recommendations and guidelines on evaluation of the different elements of the control centre, i.e. control suite, control room, workstations, displays and controls, and work environment. It covers all types of control centres, including those for the process industry, transport systems and dispatching rooms in the emergency services. Although ISO 11064-7:2006 is primarily intended for non-mobile control centres, many of the principles could be relevant/applicable to mobile centres, such as those found on ships and aircraft. [Source: ISO, last access 2013-01-13] External links • ISO 11064-7:2006 Ergonomic design of control centres -- Part 7: Principles for the evaluation of control centres, last access 2013-01-13 EN ISO 14915 Profile Reference Name Categories ICS EN ISO 14915 EN ISO 14915: Software ergonomics for multimedia user interfaces Accessibility, Usability, User interfaces, ISO 13.180 - Ergonomics 35.200 - Interface and interconnection equipment Abstract ISO 14915-1:2002 establishes design principles for multimedia user interfaces and provides a framework for handling the different considerations involved in their design. Current Version see Standard Parts below Other editions AAL Relevance AAL technologies should always use user-friendly interfaces. This standard will help interfaces designers to do it. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=25578 Standard Parts Standard ISO 14915-2:2003 V1.0 Title Part 2: Multimedia navigation and control 2013-01-15 Page 384 of 490 AALIANCE2 ISO 14915-3:2002 D4.1 Online Repository of Standards - Snapshot Part 3: Media selection and combination Description ISO 14915-1:2002 establishes design principles for multimedia user interfaces and provides a framework for handling the different considerations involved in their design. It addresses user interfaces for applications that incorporate, integrate and synchronize different media. This includes static media such as text, graphics or images, and dynamic media such as audio, animation, video or media related to other sensory modalities. Detailed design issues within a single medium (e.g. the graphical design of an animation sequence) are only addressed as far as they imply ergonomic consequences for the user. ISO 14915-1:2002 gives requirements and recommendations for the ergonomic design of multimedia applications mainly intended for professional and vocational activities such as work or learning. It does not specifically address applications outside this area, such as entertainment, although some recommendations can also be applicable in such domains. ISO 14915-1:2002 is applicable to software aspects related to multimedia user interfaces and does not address hardware or implementation issues. The ergonomic requirements and recommendations described in ISO 14915-1:2002 can be realized through very different techniques, e.g. the delivery system, a scripting language, or the application. The focus of ISO 14915-1:2002 is on multimedia presentation issues. Multimodal input which uses different media such as speech in combination with pointing for entering information is not considered in the recommendations provided. [Source: ISO] EN ISO 9241 Profile Reference Name Categories ICS EN ISO 9241 EN ISO 9241: Ergonomics of Human System Interaction Accessibility, Human body communication, Usability 13.180 - Ergonomics 35.180 - IT terminal and other peripheral equipment Abstract ISO 9241-420:2011 provides guidance for the selection of input devices for interactive systems, based on ergonomic factors, considering the limitations and capabilities of users and the specific tasks and context of use. Current Version 1 Other editions AAL Relevance Human system interaction can be used in AAL Technologies, which will need to respect ergonomics standards. Available from http://www.iso.org/iso/catalogue_detail.htm?csnumber=52938 Description It describes methods for selecting a device or a combination of devices for the task at V1.0 2013-01-15 Page 385 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot hand. It can also be used for evaluating the acceptability of trade-offs under the existing conditions. The target users of ISO 9241-420:2011 are user organizations and systems integrators who tailor systems for a given context of use. It is applicable to the following input devices: keyboards, mice, pucks, joysticks, trackballs, trackpads, tablets and overlays, touch-sensitive screens, styli and light pens. It does not specify design requirements or give recommendations for those devices. Former editions: • ISO-TS 16071 • ISO 13407 • ISO AWI 18789 • ISO 13406 ETSI EG 202 416 - DEG/HF-00069 Profile Reference Name ETSI EG 202 416 - DEG/HF-00069 Human Factors (HF); User Interfaces; Setup procedure design guidelines for mobile terminals and services Categories User interfaces ICS 13.180 - Ergonomics 35.180 - IT terminal and other peripheral equipment Abstract The present document provides user interface design guidelines for setup procedures, applicable to mobile terminals and services throughout the product life-cycle Current Version V1.1.2 (2006-12) Other editions AAL Relevance User-friendly interfaces are important for AAL systems Available from http://www.etsi.org/deliver/etsi_eg/202400_202499/202416/01.01.02_6 0/eg_202416v010102p.pdf Description The present document provides user interface design guidelines for setup procedures, applicable to mobile terminals and services throughout the product life-cycle. The design guidelines address the design, specification, implementation, deployment and maintenance of mobile terminals and services and are equally applicable to consumer use as well as to professional use. For the purpose of the present document, it is assumed that access to mobile services is primarily achieved through handheld terminals, typically characterized by a limited screen size, a 12 key-keypad and possibly, additional function keys and/or a stylus and/or a touch screen. The guidelines provided in the present document focus on public mobile network terminals and services, but they are also applicable to other technologies (e.g. cordless or IP-based telephony and Wi-Fi). Wherever possible, an integrated design-for-all approach has been adopted, taking needs V1.0 2013-01-15 Page 386 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot and abilities of children, older users and users with physical, cognitive, or sensory impairments into account. When appropriate, specific guidelines for the optimization of the accessibility of setup procedures are presented and existing guideline documents are referenced for further details. [source: standard document] ETSI EN 300 175-1 Profile Reference Name ETSI EN 300 175-1 - REN/DECT-000248-1 Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 1: Overview Categories User interface; ETSI ICS 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT) Abstract The present document gives an introduction and overview of the complete Digital Enhanced Cordless Telecommunications (DECT) Common Interface (CI). Current Version V2.2.1 (2008-11) Other editions AAL Relevance Devices that use the DECT standard (cordless phones) are found in many households Available from http://www.etsi.org/deliver/etsi_en/300100_300199/30017501/02.02.01 _60/en_30017501v020201p.pdf Description The present document gives an introduction and overview of the complete Digital Enhanced Cordless Telecommunications (DECT) Common Interface (CI). The present document contains an abstract of the other parts of the DECT standard together with a general description of: • the objectives of the present document; • the DECT Common Interface; • the protocol architecture of DECT. The present document also provides an extensive vocabulary; in particular it contains the common definitions of all the technical terms used in different parts of the present document. The present document includes New Generation DECT, a further development of the DECT standard introducing wideband speech, improved data services, new slot types and other technical enhancements. [source: standard document] V1.0 2013-01-15 Page 387 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ETSI TS 102 511 Profile Reference Name ETSI TS 102 511 Human Factors (HF); AT Commands for Assistive Mobile Device Interfaces Categories User interfaces ICS Abstract The present document sets out the requirements for new AT command protocols that can be used to enable assistive devices to interwork satisfactorily with mobile terminals over a range of suitable interfaces. Current Version Other editions AAL Relevance Standardized AT command protocols are key in AAL systems Available from http://www.etsi.org/deliver/etsi_ts/102500_102599/102511/01.01.01_60 /ts_102511v010101p.pdf Description An European community that promotes fair and comprehensive access to advanced information and communication services for all citizens must ensure that those citizens whose disabilities are such that they cannot use devices “designed-for-all” are not excluded from the common access policies. In principle, all European citizens expect to have access to information through technology mediated services and devices. In the context of this report, this implies that all citizens can choose to have access through mobile platforms, and to choose the complexity of the devices and the range of services that meet their needs, at reasonable and equitable costs. Some users with disabilities, however, are unable to use conventional devices and services, even those designed according to the “design-for-all” principles, as their disabilities are too severe or their requirements conflict with those of people with a different disability. In this case, these users should be able to choose the mobile devices that they need to use, and to easily and cheaply enhance those devices and services with an adaptation appropriate to their needs. Examples could include a speaking output adaptation for blind people or icon representation of functions for people with reduced reading skills. In order for this objective to be realised, mobile devices and services should be implemented with a standardized set of interfaces that can be the channel through which these adaptations become integrated with the rest of the system. Without this standardized interface, each adaptation will require significant technical expertise and effort, and will consequently be expensive and practically unrealistic. People with disabilities will be confined to using a small subset of the available devices and services, and will not be able to join other citizens in selecting devices and services according to personal preferences (e.g. style, design, functionality), but instead will have to persist with using specific devices long after they have ceased to be supported by manufacturers and operators, simply because it is impossible to replace them. V1.0 2013-01-15 Page 388 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot A standardized set of interfaces will, therefore, encourage growth in the market for mobile devices and services by enabling the large numbers of disabled and elderly people who are currently excluded to participate, and the strength of the European rehabilitation technology market, particularly the small and medium enterprises that currently dominate this sector. As one candidate technology that is present in all mobile devices is AT commands, the work to promote increased accessibility and adaptability of the mobile devices is expected to include the upgrading of existing standards where the necessary AT commands [2] and [3] do not exist (as recommended in “Requirements for assistive technology devices in ICT” [7]). Requirements on this set of interface standards have been collected in a process which has involved manufacturers of assistive devices and groups representing the user with different special needs. The draft versions have been presented to appropriate standards fora (e.g. 3GPP) and interested mainstream mobile device manufacturers. The present document also provides a basis for national regulatory authorities to implement the Framework Directive (2002/21/EC) [28], enable member states to take specific measures for disabled end-users in order to ensure access to publicly available telephone services and emergency services in accordance with the Universal Service Directive (2002/22/EC) [29] and facilitate the implementation of the Public Procurement Directive (2004/18/EC) [36]. [source: standard document] HSS Profile Reference Name HSS HSS: U.S. Department of Health and Human Services: Research based Web Design & Usability Guidelines Categories User Interfaces ICS Abstract The Guidelines were developed to assist those involved in the creation of Websites to base their decisions on the most current and best available evidence. Current Version 2006 Other editions AAL Relevance AAL may use websites, which need to be accessible Available from http://www.usability.gov/guidelines/guidelines_book.pdf Description The Research-Based Web Design & Usability Guidelines (Guidelines) were developed by the U.S. Department of Health and Human Services (HHS), in partnership with the U.S. General Services Administration. The 2006 edition of the Guidelines updates the original set of 187 guidelines, and adds 22 new ones. Many of the guidelines were edited, and numerous new references have been added. There are now 209 guidelines. The primary audiences for the Guidelines are Web site managers, designers, and others involved in the creation or maintenance of Web sites. A secondary audience is V1.0 2013-01-15 Page 389 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot researchers who investigate Web design issues. The HSS Guidelines help researchers determine what research has been conducted, and where little or no research exists. The Guidelines cover the following areas: • Design Process and Evaluation • Optimizing the User Experience • Accessibility • Hardware and Software • Homepage • Page Layout • Navigation • Scrolling and Paging • Headings, Titles, and Labels • Links • Text Appearance • ListsScreen-Based Controls (Widgets) • Graphics, Images, and Multimedia • Writing Web Content • Content Organization • Search • Usability Testing [source: standard document] ISO/IEC 10741-1:1995 Profile Reference Name ISO/IEC 10741-1:1995 Information technology – User system interfaces – Dialogue interaction – Part 1: Cursor control for text editing Categories User interfaces ICS 35.240.20 - IT applications in office work Abstract Specifies how incremental cursor control is effected as a result of user interaction with a text editor. Current Version Stage: 90.93 (2008-07-29) Other editions AAL Relevance User friendly cursor control is important in AAL systems Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? V1.0 2013-01-15 Page 390 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot csnumber=18832 Description Specifies how incremental cursor control is effected as a result of user interaction with a text editor. Cursor control in form filling and spread sheet applications, cursor control in editing other forms of text such as graphics and cursor control in manipulating simple and complex documents are not covered. ISO/IEC 12119 Profile Reference Name ISO/IEC 25051 (former 12119) ISO/IEC 25051: Software engineering – Software product Quality Requirements and Evaluation (SQuaRE) – Requirements for quality of Commercial Off-The-Shelf (COTS) software product and instructions for testing Categories Software infrastructure for AAL ICS 35.080 - Software Abstract ISO/IEC 25051:2005 defines quality requirements for COTS software products. Current Version 1 Other editions ISO/IEC 25051:2006/Cor 1:2007 AAL Relevance Available from http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.ht m?csnumber=37457 Description ISO/IEC 25051:2005 defines quality requirements for COTS software products. A COTS software product includes the product description, the user documentation, and the software contained on a computer sensible media. The quality requirements, functionality, reliability, usability, efficiency, maintainability, portability, and quality in use are consistent with the definitions of SQuaRE. In addition to the quality requirements, ISO/IEC 25051:2005 also defines requirements for test documentation. The test documentation purpose is to demonstrate the conformity of the software with the requirements. The documentation contains a test plan, the description of the tests cases, and the tests results. ISO/IEC 25051:2005 can be used by suppliers, certification bodies, testing laboratories, accreditation bodies, regulatory authorities and acquirers. [source: iso.org] V1.0 2013-01-15 Page 391 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 18021 Profile Reference Name ISO/IEC 18021 ISO/IEC 18021: Information technology – User interfaces for mobile tools for management of database communications in a client-server model Categories User Interfaces; ISO; IEC; ICS 35.240.20 Abstract This standard contains user interface specifications for PDAs with a data interchange capability with corresponding servers. Current Version ISO/IEC 18021:2002 Other editions AAL Relevance Good user interfaces are key in AAL systems Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=30806 Description This International Standard defines user interface functions for management of database communication of an MBT (Mobile tools) client capable of interchanging data with an MBT server. This International Standard is applicable to MBT clients. This International Standard specifically defines the following two user interfaces: • The user interface function for obtaining user approval in advance when MBT client's database is updated via communication link, or when data in the MBT client’s database is transmitted to another database. • The user interface function for providing feedback to the user, after the MBT client's or the MBT server's database has been updated via a communication link, or data in MBT client's database has been transmitted to another database. [source: standard document] External links • http://www.usabilitynet.org/tools/r_international.htm#18021 ISO/IEC 24786 Profile Reference Name Categories ICS V1.0 ISO/IEC 24786:2009 Information technology – User interfaces – Accessible user interface for accessibility settings Accessibility; User interfaces 35.240.20 - IT applications in office work 2013-01-15 Page 392 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Abstract Accessible user interfaces, as defined in ISO/IEC 24786:2009, can help them to operate computers if they are able to adjust accessibility settings prior to use. Current Version Ed. 1; Stage: 60.60 (2009-12-07) Other editions AAL Relevance Accessible user interfaces makes AAL system more accessible Available from http://www.iso.org/iso/catalogue_detail.htm?csnumber=41556 Description People with disabilities (e.g. visual, hearing, physical) can experience difficulties in accessing computers and other information/communication technology (ICT) devices. Accessible user interfaces, as defined in ISO/IEC 24786:2009, can help them to operate computers if they are able to adjust accessibility settings prior to use. If this is not possible, some people will not be able to access these devices without help from another party. ISO/IEC 24786:2009 specifies requirements and recommendations for making accessibility settings accessible. This will make the information technologies more accessible by ensuring that people with disabilities can adjust accessibility settings by themselves. ISO/IEC 24786:2009 provides guidance on specific accessibility settings. It specifies how to access and operate the accessibility setting mode, and how to directly activate specific accessibility functions. ISO/IEC 24786:2009 applies to all operating system user interfaces on computers, but can also be applied to other types of ICT, where appropriate. It does not apply to the user interface before the operating system is loaded and active. [Source: ISO] ISO/IEC 7816-4 Profile Reference Name ISO/IEC 7816-4:2005 Identification cards – Integrated circuit cards – Part 4: Organization, security and commands for interchanges Categories Safety ICS 35.240.15 Abstract ISO/IEC 7816 is an international standard related to electronic identification cards with contacts, especially smart cards Current Version Stage: 90.92 (2008-10-03) Other editions AAL Relevance As AAL scenarios may include security systems this standard is relevant for the accessibility of identity cards. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=36134 V1.0 2013-01-15 Page 393 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description ISO/IEC 7816-4:2005 specifies: • contents of command-response pairs exchanged at the interface, • means of retrieval of data elements and data objects in the card, • structures and contents of historical bytes to describe operating characteristics of the card, • structures for applications and data in the card, as seen at the interface when processing commands, • access methods to files and data in the card, • a security architecture defining access rights to files and data in the card, • means and mechanisms for identifying and addressing applications in the card, • methods for secure messaging, • access methods to the algorithms processed by the card. It does not describe these algorithms. It does not cover the internal implementation within the card or the outside world. ISO/IEC 7816-4:2005 is independent from the physical interface technology. It applies to cards accessed by one or more of the following methods: contacts, close coupling, and radio frequency. [Source: ISO] External links • Wikipedia: http://en.wikipedia.org/wiki/ISO/IEC_7816 ISO/IEC 25010 (former 9126) Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from V1.0 ISO/IEC 25010 ISO/IEC 25010: Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – System and software quality models Software infrastructure for AAL 35.080 - Software ISO/IEC 25010:2011 defines both a quality in use model and a product quality model relevant to all software products and computer systems. 1 AAL software should respect quality standards http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.ht m?csnumber=35733 2013-01-15 Page 394 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description ISO/IEC 25010:2011 defines: • A quality in use model composed of five characteristics (some of which are further subdivided into subcharacteristics) that relate to the outcome of interaction when a product is used in a particular context of use. This system model is applicable to the complete human-computer system, including both computer systems in use and software products in use. • A product quality model composed of eight characteristics (which are further subdivided into subcharacteristics) that relate to static properties of software and dynamic properties of the computer system. The model is applicable to both computer systems and software products. • The characteristics defined by both models are relevant to all software products and computer systems. The characteristics and subcharacteristics provide consistent terminology for specifying, measuring and evaluating system and software product quality. They also provide a set of quality characteristics against which stated quality requirements can be compared for completeness. Although the scope of the product quality model is intended to be software and computer systems, many of the characteristics are also relevant to wider systems and services. ISO/IEC 25012 contains a model for data quality that is complementary to this model. The scope of the models excludes purely functional properties, but it does include functional suitability. The scope of application of the quality models includes supporting specification and evaluation of software and software-intensive computer systems from different perspectives by those associated with their acquisition, requirements, development, use, evaluation, support, maintenance, quality assurance and control, and audit. The models can, for example, be used by developers, acquirers, quality assurance and control staff and independent evaluators, particularly those responsible for specifying and evaluating software product quality. Activities during product development that can benefit from the use of the quality models include: • identifying software and system requirements; • validating the comprehensiveness of a requirements definition; • identifying software and system design objectives; • identifying software and system testing objectives; • identifying quality control criteria as part of quality assurance; • identifying acceptance criteria for a software product and/or software-intensive computer system; • establishing measures of quality characteristics in support of these activities. [Source: ISO] V1.0 2013-01-15 Page 395 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC Guide 71 Profile Reference Name ISO/IEC Guide 71 ISO/IEC Guide 71: Guidelines for standards developers to address the needs of older persons and persons with disabilities Categories Accessibility ICS 01.120 Standardization. General rules 11.180.01 Aids for disabled and handicapped persons in general Abstract This Guide provides guidance to writers of relevant International Standards on how to take into account the needs of older persons and persons with disabilities. Current Version 1 Other editions AAL Relevance AAL standards should include these guidelines when being developed (see abstract). Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=33987 Description 1.1 This Guide provides guidance to writers of relevant International Standards on how to take into account the needs of older persons and persons with disabilities. Whilst recognizing that some people with very extensive and complex disabilities may have requirements beyond the level addressed in this Guide, a very large number of people have minor impairments which can be easily addressed by relatively small changes of approach in standards, thereby increasing the market for the product or service. This Guide aims • to inform, increase understanding and raise awareness about how human abilities impact on the usability of products, services and environments, • to outline the relationship between the requirements in standards and the accessibility and usability of products and services, and • to raise awareness about the benefits of adopting accessible design principles in terms of a wider market. 1.2 This Guide applies to products, services and environments encountered in all aspects of daily life and intended for the consumer market and the workplace. For the purposes of this document, the term 'products and services' is used to reflect all these purposes. 1.3 This Guide • describes a process by which the needs of older persons and persons with disabilities may be considered in the development of standards, • provides tables to enable standards developers to relate the relevant clauses of a standard to the factors which should be considered to ensure that all abilities are addressed, V1.0 2013-01-15 Page 396 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • offers descriptions of body functions or human abilities and the practical implications of impairment, • offers a list of sources that standards developers can use to investigate more detailed and specific guidance materials. 1.4 This Guide provides general guidance. Consideration should be given to the development of additional guides for specific product or service sectors. 1.5 While it is recognized that accessibility and usability are important for both products and services, international work on services standards is at the preliminary stage. At present, this Guide contains considerably more guidance on products than on services. 1.6 This Guide is also available as a Braille version. Copies may be obtained through the ISO Central Secretariat. [Source: ISO] External links • http://www.iso.org/iso/iso_iec_guide_71_2001.pdf ISO/IEC TR 13818 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/IEC TR 13818 ISO/IEC TR 13818: Information technology – Generic coding of moving pictures and associated audio information User Interfaces; ISO; IEC 35.040 - Character sets and information coding ISO/IEC 13818-1:2007 specifies the system layer of the coding. Ed. 3; Stage: 90.92 (2012-05-07) http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.ht m?csnumber=44169 Description ISO/IEC 13818-1:2007 specifies the system layer of the coding. It was developed principally to support the combination of the video and audio coding methods defined in ISO/IEC 13818-2 and ISO/IEC 13818-3. The system layer supports six basic functions: the synchronization of multiple compressed streams on decoding; the interleaving of multiple compressed streams into a single stream; the initialization of buffering for decoding start up; continuous buffer management; time identification; multiplexing and signalling of various components in a system stream. An ISO/IEC 13818-1:2007 multiplexed bit stream is either a Transport Stream or a Program Stream. Both streams are constructed from PES packets and packets containing other necessary information. Both stream types support multiplexing of video and audio compressed streams from one V1.0 2013-01-15 Page 397 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot program with a common time base. The Transport Stream additionally supports the multiplexing of video and audio compressed streams from multiple programs with independent time bases. For almost error-free environments the Program Stream is generally more appropriate, supporting software processing of program information. The Transport Stream is more suitable for use in environments where errors are likely. An ISO/IEC 13818-1:2007 multiplexed bit stream, whether a Transport Stream or a Program Stream, is constructed in two layers: the outermost layer is the system layer, and the innermost is the compression layer. The system layer provides the functions necessary for using one or more compressed data streams in a system. The video and audio parts of ISO/IEC 13818-1:2007 define the compression coding layer for audio and video data. Coding of other types of data is not defined by ISO/IEC 13818-1:2007, but is supported by the system layer provided that the other types of data adhere to the constraints defined in 2.7. [Source: ISO] ISO/IEC TR 19765 Profile Reference Name ISO/IEC TR 19765:2007 Information technology – Survey of icons and symbols that provide access to functions and facilities to improve the use of information technology products by the elderly and persons with disabilities Categories User interfaces ICS 35.040 - Character sets and information coding 01.080.50 - Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation 11.180.99 – Other standards related to aids for disabled and handicapped people Abstract ISO/IEC TR 19765:2007 presents icons and symbols currently used to provide access to facilities and tools to support the needs of elderly and disabled users of information technology (IT) products, and could form the basis of a future International Standard which would provide a recommended collection of icons and symbols. Current Version Ed. 1; Stage: 90.60 (2012-12-19) Other editions AAL Relevance AAL systems need to use intuitive and easy to understand interfaces Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=33903 Description Different users of information technology products possess different sets of abilities. Some abilities may not ever be present in a user as they may have been born without them. V1.0 2013-01-15 Page 398 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Some abilities are acquired, developed or deteriorate over time due to education, maturity, injury, illness or age. Just as it is possible that a user possesses a combination of abilities, it is also possible that they may lack a combination of abilities. ISO/IEC TR 19765:2007 presents icons and symbols currently used to provide access to facilities and tools to support the needs of elderly and disabled users of information technology (IT) products, and could form the basis of a future International Standard which would provide a recommended collection of icons and symbols. These icons and symbols have been collected from a variety of sources including other standards, contemporary software products, web sites and hardware devices. These sources are cross-referenced and listed in a bibliography. The icons and symbols presented in ISO/IEC TR 19765:2007 are categorized by modality and method of use. [Source: ISO] ISO/IEC TR 19766 Profile Reference Name ISO/IEC TR 19766:2007 Information technology – Guidelines for the design of icons and symbols accessible to all users, including the elderly and persons with disabilities Categories User interfaces ICS 35.040 - Character sets and information coding 01.080.50 - Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation 11.180.99 – Other standards related to aids for disabled and handicapped people Abstract ISO/IEC TR 19766:2007 provides recommendations relating to the design of icons to support accessibility by the elderly and people with disabilities. Current Version Ed. 1; Stage: 90.60 (2012-12-19)Other editions AAL Relevance AAL systems should use accessible and intuitive user interfaces Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=42128 Description ISO/IEC TR 19766:2007 provides recommendations relating to the design of icons to support accessibility by the elderly and people with disabilities. These recommendations assist accessible implementation of all icons for users. While these recommendations were developed to meet the needs of the elderly and people with disabilities, they can also provide greater accessibility to a wider range of users in a variety of different contexts. V1.0 2013-01-15 Page 399 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC TR 19766:2007 introduces a set of attributes and operations that can be implemented as features of graphic icons to make the functionality of these icons accessible to the widest possible range of users. Textual attributes are emphasized because they can be rendered in various alternate modalities. ISO/IEC 11581-1 provides guidance on the graphic aspects of icons. Specific renderings of these attributes (or of icons in general) are not dealt with as part of ISO/IEC TR 19766:2007. [Source: ISO] ISO/TR 22411 Profile Reference Name ISO/TR 22411 ISO/TR 22411: Ergonomics data and guidelines for the application of ISO/IEC Guide 71 to products and services to address the needs of older persons and persons with disabilities Categories Accessibility, Usability ICS 01.120 - Standardization. General rules 11.180.01 - Aids for disabled and handicapped persons in general Abstract ISO/TR 22411:2008 presents ergonomics data and guidelines for applying ISO/IEC Guide 71 in addressing the needs of older persons and persons with disabilities in standards development. Current Version Ed. 1; Stage: 60.60 (2008-08-27) Other editions AAL Relevance AAL systems should be accessible for all groups, including older people and persons with disabilities Available from http://www.iso.org/iso/catalogue_detail?csnumber=40933 Description ISO/TR 22411:2008 presents ergonomics data and guidelines for applying ISO/IEC Guide 71 in addressing the needs of older persons and persons with disabilities in standards development. It provides ergonomics data and knowledge about human abilities — sensory, physical and cognitive — and allergies, as well as guidance on the accessible design of products, services and environments. [Source: ISO] W3C Rec17 Profile Reference Name Categories ICS V1.0 W3C Rec17 W3C Recommendation 17 December 2002: User Agent Accessibility Guidelines 1.0 Accessibility; User Interfaces; W3C 01.120 - Standardization. General rules 2013-01-15 Page 400 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 11.180.01 - Aids for disabled and handicapped persons in general Abstract This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). Current Version 1 (2002-12-17) Other editions AAL Relevance AAL technologies should use and promote the use of accessible websites Available from http://www.w3.org/TR/UAAG10/ Description This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable. In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for Braille rendering) will be essential to ensuring Web access for some users with disabilities. [Source: W3C] V1.0 2013-01-15 Page 401 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 11. Specifications and standards for operator models 11.1. Quality management systems in general EMAS Profile Reference Name Categories ISO 14001 EMAS: Eco Management and Audit Scheme Specifications and standards for operator models; Quality management systems in general ICS 13.020.10 - Environmental management Abstract Requirements for management system enabling organisations to evaluate, report and improve their environmental performance Current Version 2011-11-03 Other editions 2009-12-22 AAL Relevance AAL service providers should consider the environmental impact of the service they provide. Available from http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.ht m?csnumber=31807 Description ISO 14001 (or EMAS) specifies requirements to develop and implement policies and objectives for an environmental management system for organisations. Whilst legal demands and other requirements has subscribed, are met. Instead of prescribing performance criteria it merely offers guidelines in those environmental aspects an organisation has influence and control. The application of the ISO 14001 is voluntary. [source: iso.org] External links • http://www.iso-14001-milieu.nl/page/310/audit-iso-14001.html (in Dutch) • ISO 14001:2004 - Environmental management systems -- Requirements with guidance for use EN ISO 9000 Profile Reference V1.0 EN ISO 9000 2013-01-15 Page 402 of 490 AALIANCE2 Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot EN ISO 9000: Quality management systems Specifications and standards for operator models; Quality management systems in general; EN; ISO 03.120.10 - Quality management and quality assurance 01.040.03 - Services. Company organization, management and quality. Administration. Transport. Sociology The ISO 9000 provides the fundamentals and vocabulary used in the ISO 9000 family of standards. It introduces eight Quality Management Principles. 2005-09-29 Draft 04/30093427 DC This standard is fundamental for numerous other AAL standards http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=42180 Description This International Standard describes fundamentals of quality management systems, which form the subject of the ISO 9000 family, and defines related terms. This International Standard is applicable to the following: • a) organizations seeking advantage through the implementation of a quality management system; • b) organizations seeking confidence from their suppliers that their product requirements will be satisfied; • c) users of the products; • d) those concerned with a mutual understanding of the terminology used in quality management (e.g. suppliers, customers, regulators); • e) those internal or external to the organization who assess the quality management system or audit it for conformity with the requirements of ISO9001 (e.g. auditors, regulators, certification/registration bodies); • f) those internal or external to the organization who give advice or training on the quality management system appropriate to that organization; • g) developers of related standards. [Source http://shop.iccsafe.org/iso-9000-download.html accessed on 14-01-2012] External links • http://www.iso.org/iso/home/standards/management-standards/iso_9000.htm • http://en.wikipedia.org/wiki/ISO_9000 V1.0 2013-01-15 Page 403 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN ISO 14000 Profile Reference Name Categories EN ISO 14000 EN ISO 14000: Environmental management system Specifications and standards for operator models; Quality management systems in general; EN; ISO; ICS 13.020.10 - Environmental management Abstract ISO 14001 is one of the standards of the ISO 14000 series and is widely applied to environmental management systems and certification. Current Version N/A Other editions N/A AAL Relevance AAL services should respect the environment they operate in, the ISO 14001 series supplies guidelines to do this. Available from http://www.iso14000-iso14001-environmental-management.com Standard Parts Standard ISO14001 ISO14004 ISO19011 ISO14013 ISO14020 ISO14030 ISO14040 Title Environmental Management Development and implementation of environmental systems Audit of an environmental system, including qualification criteria for auditors Audit Program review and assessment material Labelling issues Performance targets and monitoring within Environmental Management System Life Cycle issues Description The ISO 14000 family of standards sets a framework and guidelines for the development of an environmental management system and supporting audit programme. The actual standard is described in the ISO 14001. Guidelines for audit programs, qualification criteria for environmental auditors, life cycle issues and more can be found in the other members of the series. [Source: http://www.iso.org/iso/home/standards/management-standards/iso14000.htm accessed on 14012012] External links • Wikipedia contributors, "ISO 14000," Wikipedia, The Free Encyclopedia, accessed January 13, 2013. V1.0 2013-01-15 Page 404 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot VDE-AR-E 2757-2 Profile Reference Name VDE-AR-E 2757-2 VDE-AR-E 2757-2: Service staying at home - Requirements for suppliers of combined services Categories Specifications and standards for operator models; Quality management systems in general; Germany; Health Informatics; Medical Devices ICS 03.080.30 - Services for consumers 11.040.55 - Diagnostic equipment 97.120 Automatic controls for household use Abstract Integration of the description of both Telemedicine requirement as well as requirements for the supporting technology Current Version 2011-08 Other editions N/A AAL Relevance Can be used as a reference on those situations where AAL Telemedicine services are provided Available from http://www.vde-verlag.de/standards/0757001/vde-ar-e-2757-2anwendungsregel-2011-08.html Description Provides definitions, housing requirements and service provisioning in “Wohnselbst”. In the standard, three chronical types of diseases are addressed, Herpensia, heart dysfunction and Diabetes mellitus. External links • http://www.vde.com/en/dke/std/VDEapplicationguides/Publications/Pages/VDE-ARE2757-2.aspx VDE-AR-E 2757-3 Profile Reference Name VDE-AR-E 2757-3 VDE-AR-E 2757-3: Staying at home service - Criteria for the selection and installation of AAL components Categories Specifications and standards for operator models; Quality management systems in general; Germany; Criteria AAL-Components ICS 13.180 - Ergonomics 97.120 - Automatic controls for household use Abstract Guidelines for selection and installation of technical components that take into account a person's needs and limitations. Current Version 2012-01 Other editions N/A V1.0 2013-01-15 Page 405 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance This standard may be used for the selection of AAL components for AAL services Available from http://www.vde-verlag.de/standards/0757002/vde-ar-e-2757-3anwendungsregel-2012-01.html Description With the installations of technical components to support elderly people to stay healthy at their own home as long as possible not only the the device related or correct technical implementation but also the person's limitations should be looked into in detail. This standard provides the proper guidelines for selection and installation of devices. External links • http://www.vde.com/en/dke/std/VDEapplicationguides/Publications/Pages/VDE-ARE2757-3.aspx VDE-AR-E 2757-4 Profile Reference Name VDE-AR-E 2757-4 VDE-AR-E 2757-4: Staying at home service - Quality criteria for providers, services and products of Ambient Assisted Living (AAL) Categories Specifications and standards for operator models; Quality management systems in general; Germany; Quality and risk management of medical devices ICS 03.080.30 - Services for consumers 11.180.01 - Aids for disabled and handicapped persons in general 97.120 Automatic controls for household use Abstract Description of Quality criteria for the promotion the quality of AAL products and services and and associated service concepts. Current Version 2012/1/1 Other editions AAL Relevance VDE is responsible for several standards that can be useful in the AAL domain Available from http://www.vde-verlag.de/standards/0757003/vde-ar-e-2757-4anwendungsregel-2012-01.html Description This German standard describes criteria for Quality assurance for AAL products and services as well as related service concepts. Besides Technical safety the following themes are covered: data-quality, performance capabilities, usefulness and ergonomics, visual and auditive and olfactory sensing, motoric and cognitive aspects, aspects of AAL services, the role of the service provider, quality assurance, knowledge and customer insights. V1.0 2013-01-15 Page 406 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.vde.com/en/dke/std/VDEapplicationguides/Publications/Pages/VDE-ARE2757-4.aspx ISO/IEEE11073-10471 Profile Reference Name ISO/IEEE11073-10471 ISO/IEEE11073-10471: Personal health device communication. Part 10471 Device specification Independent living activity hub Categories Specifications and standards for operator models; Quality management systems in general; ISO; IEEE; Telehealth; Interoperability ICS 35.240.80 - IT applications in health care technology Abstract ISO/IEEE 11073-10471:2010 addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers Current Version Stage: 90.92 (2013-01-11) Other editions AAL Relevance ISO and IEEE have an agreement in place to increase their cooperation in developing international standards. The PSDO cooperation agreement provides new opportunities to adopt and jointly develop international standards to serve the global marketplace. Available from http://www.iso.org/iso/catalogue_detail.htm?csnumber=54328 Description ISO-IEEE 11073-10471:2010 establishes a normative definition of the communication between independent living activity hubs and managers (e.g., cell phones, personal computers, personal health appliances and set top boxes) in a manner that enables plugand-play (PnP) interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology and information models. It specifies the use of specific term codes, formats, and behaviours in telehealth environments restricting ambiguity in base frameworks in favour of interoperability. ISO-IEEE 11073-10471:2010 defines a common core of communication functionality for independent living activity hubs. In this context, independent living activity hubs are defined as devices that communicate with simple situation monitors (binary sensors), normalize information received from the simple environmental monitors, and provide this normalized information to one or more managers. This information can be examined (for example) to determine when a person's activities/behaviour have deviated significantly from what is normal for them such that relevant parties can be notified. Independent living activity hubs will normalize information from the following simple situation monitors (binary sensors) for the initial release of the proposed standard: fall sensor, motion sensor, door sensor, bed/chair occupancy sensor, light switch sensor, smoke sensor, (ambient) temperature threshold sensor, personal emergency response system (PERS), and enuresis sensor (bed-wetting). V1.0 2013-01-15 Page 407 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.iso.org/iso/catalogue_detail.htm?csnumber=54328 11.2. Quality management on the health sector Certification Geriatric Seal of Approval Profile Reference Name Categories Certification Geriatric Seal of Approval Certification Geriatric Seal of Approval Specifications and standards for operator models; Quality management health sector; Germany; ISO 9001; ICS 11.020 - Medical sciences and health care facilities in general Abstract Improves quality management for Geriatrics Hospitals en Rehabilitation Current Version 2010-04-01 Other editions 2009-11-26 AAL Relevance AAL services provided by these operators in Germany should respect this seal of quality Available from http://www.bv-geriatrie.de/index.php?page=qualitaetssiegel Description The standard is met by applying the checklist provided by the Office of Association of Geriatrics ([email protected]). Then a certification process can be started were an independent certification body will examine the Quality Management Handbook and determine if it is according to the checklist. There are three options. Option 1 provides the Seal for acute geriatric care together with the ISO 9001 standard for hospitals. Option 2 provides the same but with the ISO 9001 focussed on geriatric rehabilitation facilities. Option 3 deals with the seal of quality for geriatric care hospitals and rehabilitation clinics and fully integrated the demands of ISO 9001. Furthermore, it meets specific requirements for acute geriatric care. The process for certification is aimed at both facilities for in-house treatment and patient care as to institutions that offer extramural care services. EPA Profile Reference Name Categories ICS Abstract V1.0 EPA EPA: European Practice Assessment Specifications and standards for operator models; Quality management health sector; 11.020 - Medical sciences and health care facilities in general The “European Practice Assessment” EPA 2005 is a tool which allows to evaluate and to improve the quality of general practice in Europe 2013-01-15 Page 408 of 490 AALIANCE2 Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot 2008-01-09 EPA 2005 In case that one of the actors in a AAL-service is a General Practitioner http://www.topaseurope.eu/?q=node/3 Description EPA 2005 instrument allows: • The quality of an individual person about a general practitioner to evaluate and improve • The quality of GP practices in a given region to compare, • The quality of GP practices between countries to compare. The EPA instrument consists of questionnaires that are completed, and a site visit from a visitor (EPA coach). External links • http://www.topaseurope.eu/files/EPA-Information-Paper-English-vs11_0.pdf KTQ Profile Reference Name KTQ KTQ: Cooperation for Transparency und Quality in Healthcare (Kooperation für Transparenz und Qualität im Gesundheitswesen) Categories Specifications and standards for operator models; Quality management health sector; Germany; ICS 11.020 - Medical sciences and health care facilities in general 13.020.10 - Environmental management Abstract In the KTQ are listed the quality assurance criteria in six categories which can be queried for the certification of health care facilities in order to draw conclusions about the quality of the processes in the supply chain. A holistic approach with Patient Welfare is the starting point. Current Version N/A Other editions N/A AAL Relevance Although not specifically mentioned, both holistic and Patient Welfare approach is in line with Good Practice for AAL service providers in Germany. Available from http://www.tuv.com/en/corporate/business_customers/management_sy stem/medicine_health_care/ktq_certification/ktq.html Description After a self assessment from the criteria mentioned in the KTQ catalogue you first assess your own organisation on several categories. V1.0 2013-01-15 Page 409 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot These categories are: • patient orientation, • employee orientation, • security, • communication and information sciences, • leadership, • quality management. Then after describing the current situation, you identify room for improvement and establish interdepartmental communication structures. After this stage, you get a site visit by external KTQ visitors and one TÜV Rheinland official to coordinate the process. If your organisation reaches a positive score of 55% of the criteria to meet you will get certified. The certificate is valid for three years. pCC Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from pCC pCC: proCum Cert Specifications and standards for operator models; Quality management health sector; Germany; 11.020 - Medical sciences and health care facilities in general 03.120.10 - Quality management and quality assurance pCC is equal to the KTQ with an addition of Quality Management based on Christian values. 2002 N/A This certification is relevant for quality management of several AAL services. http://www.procumcert.de/Startseite.1.0.html Description In addition to KTQ pCC it provides the anchorage of Christian values in the requirements to be met as well as the demonstration of those Christian values to the in and outside of the organisation. External links • proCum Cert GmbH Zertifizierungsgesellschaft: "pCC inkl. KTQ" , last access 2013-0113 V1.0 2013-01-15 Page 410 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot QEP Profile Reference Name Categories QEP QEP: Quality Enhancement Program Specifications and standards for operator models; Quality management health sector; Germany; ICS 11.020 - Medical sciences and health care facilities in general 03.120.10 - Quality management and quality assurance Abstract QEP is a Quality management system for the ambulatory contractual medical and psychotherapeutic care Current Version 2010 Other editions 2005 AAL Relevance This quality management system aims at a very specific part of ambulant care only if the same values are met with AAL service this quality management should be interesting Available from http://www.kbv.de/qep/11627.html Description The Association of Statutory Health Insurance Physicians (KBV) developed a specific quality management system ‘QEP – quality and development in practices’ with practicebased doctors and psychotherapists as well as employees of the Association of SHI Physicians and quality management experts including professional associations and medical assistants. The quality management system of the Association of KBV Physicians QEP is established modularly. It fits to all branches and practice sizes and fulfils all legal requirements for quality management systems. It fits exactly to the processes and conditions of the practices and enables a gradual entry for the internal practice depending on the initial situation. [source: 3cert.de] External links • http://www.kbv.de/qep/11627.html • 3cert GmbH: "Certification of medical practices to QEP", last access 2013-01-14 VDE-AR-M 3756-1 Profile Reference Name Categories V1.0 VDE-AR-M 3756-1 VDE-AR-M 3756-1: Quality management for telemonitoring in medical applications Specifications and standards for operator models; Quality management 2013-01-15 Page 411 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot health sector; VDE; Germany; Telehealth; ICS 03.120.10 - Quality management and quality assurance 11.040.55 - Diagnostic equipment Abstract The VDE application rule for Telemonitoring specifies requirements for a quality management system for an organization Current Version 2009-10 Other editions AAL Relevance The primary goal of this application rule is to enable the requirements essential for the organization from DIN EN ISO 9000: 2000 and DIN EN ISO 9001: 2008 and DIN EN ISO 13485: 2001 on the application for a Telemonitoring system to interpret. Available from http://www.vde-verlag.de/standards/0756000/vde-ar-m-3756-1anwendungsregel-2009-10.html Description Telemonitoring is a part of Telemedicine. This standard is specific for the quality management of Telemonitoring. Goals to be achieved with telemonitoring are cost reduction, whilst the quality of the treatment increases. NEN8028 Profile Reference Name NEN8028 Health informatics - Quality criteria for services and systems for telemedicine Categories Specifications and standards for operator models; Quality management health sector; Netherlands; Telehealth; Health Informatics; ICS 35.240.80 - IT applications in health care technology 03.120.10 - Quality management and quality assurance 11.040.55 - Diagnostic equipment Abstract NEN 8028 proposes requirements that relate to the care institution, care processes and the manufacturers/suppliers of technological resources Current Version 2011-02 Other editions AAL Relevance It describes how to apply quality criteria for service and systems that will be used in AAL environments Available from http://www.nen.nl/web/Normshop/Norm/NEN-80282011-nl.htm Description In the Netherlands, a standard for quality of telemedicine which is operational since 2011. Telemedicine is (a) care process(es) that: 1) uses ICT and telecommunications to bridge distance and 2) involves two actors (at least one accredited health practitioner). The standard dictates quality requirements: — the healthcare institution must perform risk V1.0 2013-01-15 Page 412 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot management by identifying subprocesses and for each subprocess: 1)defining the conditions that must be fulfilled regarding the following categories: • people (healthcare professional, patient, carers), • procedures (protocols), • information • technical facilities • Finance 2) identifying the risks that could occur if one of more of the conditions are not fulfilled, and 3) defining the quality requirements to cope with these risks — requirements for care provision (orientation by patient, intake and care delivery) — requirements for the supplier for effectiveness, safety, openness and transparency. [Source: Meijer 2010: The Dutch Standard for Telemedicine] External links • http://www.vanmorgen.nu/medialib/186/dutch-standard-of-quality.pdf 11.3. Quality management systems for AAL DIN SPEC 77002 Profile Reference Name Categories DIN SPEC 77002 DIN SPEC 77002: Requirements for external AAL service providers Specifications and standards for operator models; Quality management systems for AAL; Germany; DIN; ICS 35.240.80 - IT applications in health care technology 11.180 - Aids for disabled or handicapped persons Abstract Standardisation of requirements for AAL services enabling persons to live independently as long as possible Current Version Under development Other editions N/A AAL Relevance This Standard aims directly on AAL related service, thus should taken into account when providing AAL-Services Available from http://www.nadl.din.de/projekte/DIN+SPEC+77002/en/151933185.html Description This standard aims to provide a definition of which services are AAL and which not. It will also define an AAL housing definition. Either case; whenever a person related service has originated form an AAL-system. V1.0 2013-01-15 Page 413 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.stadiwami.de/images/abschluss/workshop3.pdf.pdf DIN SPEC 91280 Profile Reference Name DIN SPEC 91280 DIN SPEC 91280: Classification Of Ambient Assistant Living Services In The Home Environment And Immediate Vicinity Of The Home Categories Specifications and standards for operator models; Quality management systems for AAL; Germany; DIN; ICS 35.240.80 - IT applications in health care technology 11.180 - Aids for disabled or handicapped persons Abstract This standard specifies a classification method for the engineering of services for AAL services. Current Version 2012-09-01 Other editions AAL Relevance This standard has been written especially on behalf of AAL service provisioning excluding non-person acted provision Available from http://www.din.de/cmd?level=tpl-artdetailansicht&committeeid=0&subcommitteeid=0&artid=155214353&bc rumblevel=2&languageid=de Description This classification of AAL services offers a method to engineer AAL services. Apart from normative directions, as well as definitions, and common guidelines en requirements for AAL services, there has been made a division in the service provision itself as to the infrastructure providing the service, including installation, training and maintenance. Some examples of the service provision itself are: Health care, supported by activity monitoring; Health care supported by Vital Signs Monitoring; Teleconsultation. Examples of services providing the related infrastructure are: Consulting services in the field of status quo analysis; Contract on the operation of AAL systems; Installation and Configuration; Operation of AAL systems; Maintenance and repair. External links • http://www.din.de/cmd%3Bjsessionid=702DBFD7CEBE135B7AFC99620C262189.1? workflowname=infoInstantdownload&docname=1909231&contextid=din&servicerefnam e=dino&ixos=toc DIN SPEC 91300 Profile Reference V1.0 DIN SPEC 91300 2013-01-15 Page 414 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Name DIN SPEC 91300: guideline for building a business model for residential support services Categories Specifications and standards for operator models; Quality management systems for AAL; Germany; DIN; ICS Abstract This standard will describe in several parts how a business can be created around providing residential services Current Version Part 1 and 2 are available Other editions N/A AAL Relevance To operate residential AAL service a business model is an absolute condition. This standard aims to simplify the creation of such model Available from http://www.spec.din.de/cmd?level=tpl-artdetailansicht&committeeid=0&artid=169872916&bcrumblevel=2&langu ageid=en Description The first part of this standard describes the need for a business model and organisational structure. The second part defines the associated workflows as an extended event-driven process chain. Part 3 will describe interfaces. External links • Part 1: http://www.spec.din.de/cmd?level=tpl-artdetailansicht&committeeid=0&subcommitteeid=0&artid=169871420&bcrumblevel=2&lan guageid=en • Part 2: http://www.spec.din.de/cmd?level=tpl-artdetailansicht&committeeid=0&artid=169872916&bcrumblevel=2&languageid=en • Part 3: http://www.beuth.de/en/technical-rule/din-spec-913003/169873505;jsessionid=DDA62E0B7C0FE6A7F0631A8768C6520E.1 11.4. Standards for quality and risk management of medical devices EN 60601 Profile Reference Name Categories ICS Abstract V1.0 EN 60601-1 EN 60601-1: Medical equipment/medical electrical equipment Quality management systems in general; Standards for quality and risk management of medical devices; Medical devices; EN; 11.040 - Medical equipment EN 60601 Requirements for medical electrical equipment and medical 2013-01-15 Page 415 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot electrical systems used in the home healthcare environment Current Version Stage 6060 (2006-10-20) Other editions 1990 AAL Relevance 60601 is an global accepted standard for medical electric equipment it should be respected for AAL services Available from http://www.cenelec.eu/dyn/www/f? p=104:110:1679325996811488::::FSP_PROJECT,FSP_LANG_ID:151 26,25 Description This Standard has its focus on the basic safety and essential performance of medical electrical equipment and medical electric systems. Hazards inherent in the intended physiological function within the scope of this standard are not covered by specific requirements in this standard except in 7.2.13 and 8.4.1. This standard can also be applied to equipment used for compensation or alleviation of disease, injury or disability. In vitro diagnostic equipment that does not fall within the definition of ME EQUIPMENT is covered by the IEC 61010 series 2). This standard does not apply to the implantable parts of active implantable medical devices covered by ISO 14708-1. This EN 60601-1:2006 has been restructured compared to EN 60601-1:1990. Requirements in the electrical section have been further aligned with those for information technology equipment covered by EN 60950-1 and a requirement for including a risk management added. [Source: http://www.nen.nl/web/Normshop/Norm/NENENIEC-6060112006-en.htm 30122012] on EN ISO 13485 Profile Reference Name EN ISO 13485:2012 EN ISO 13485: Medical devices – Quality management systems – Requirements for regulatory purposes Categories Quality management systems in general; Standards for quality and risk management of medical devices; Medical devices; EN; ISO; ICS 03.120.10 - Quality management and quality assurance 11.040.01 - Medical equipment in general Abstract Describes the requirements for the quality management system of organisations that provide medical equipment or services that apply medical equipment. Current Version 2012-02 Other editions 2003 AAL Relevance AAL Service providers who make use of medical equipment will have to take this standard into account Available from http://www.nen.nl/web/Normshop/Norm/NENENISO-134852012-en.htm V1.0 2013-01-15 Page 416 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description ISO 13485 aims at harmonizing legal demands on medical devices at the benefit of Quality management systems. Therefore ISO 13485 contains some specific requirements for medical devices. Moreover, some of the ISO9001 requirements are excluded because they are not suitable as a legal demand. EN ISO 14971 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from EN ISO 14971:2012 EN ISO 14971: Medical devices – Application of risk management to medical devices Quality management systems in general; Standards for quality and risk management of medical devices; Medical devices; EN; ISO; 11.040.01 - Medical equipment in general This is a key standard specifying a process for a manufacturer to identify the hazards associated with medical devices. 2012 2007 The risk of the applying of medical devices should be controlled and managed. http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030268035 Description In general ISO14971 is about Risk Management, not Quality Management (even though it seems to be unthinkable that one could perform Quality Management without the use of Risk Management). Manufacturers of Medical Devices are obliged to apply Risk Management on the design, manufacturing, operating and maintenance of their medical devices. The standard describes the application in terms of General requirements for risk management. Risk analysis, with identification of hazards and estimation of the risks for each hazardous situation. Then these risks are evaluated and necessary counter measurements are defined, implemented and evaluated. Note the 2012 version has not changed in the normative sections in comparison to the version of 2007. External links • The 2007 version in PDF: http://www.isosert.ru/isosert_iso_14971.pdf VDE-AR-M 3756-1 Profile Reference Name V1.0 VDE-AR-M 3756-1 VDE-AR-M 3756-1: Quality management for telemonitoring in medical applications 2013-01-15 Page 417 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories Quality management systems in general; Standards for quality and risk management of medical devices; Medical devices; VDE; Germany; Telehealth; ICS 03.120.10 - Quality management and quality assurance 11.040.55 - Diagnostic equipment Abstract The VDE application rule for Telemonitoring specifies requirements for a quality management system for an organization Current Version 2009-10 Other editions AAL Relevance The primary goal of this application rule is to enable the requirements essential for the organization from DIN EN ISO 9000: 2000 and DIN EN ISO 9001: 2008 and DIN EN ISO 13485: 2001 on the application for a Telemonitoring system to interpret. Available from http://www.vde-verlag.de/standards/0756000/vde-ar-m-3756-1anwendungsregel-2009-10.html Description Telemonitoring is a part of Telemedicine. This standard is specific for the quality management of Telemonitoring. Goals to be achieved with telemonitoring are cost reduction, whilst the quality of the treatment increases. 11.5. Other relevant standards and certifications 11.5.1 Quality management facility management GEFMA FMExcellence Profile Reference Name Categories GEFMA FMExcellence GEFMA FMExcellence (German Facility Management Association) Specifications and standards for operator models; Germany; Facility Management; Quality Management ICS 03.120.10 - Quality management and quality assurance Abstract Provides a three-stages quality program for German facility management with its roots in ISO 9001 Current Version 2012-06 Other editions 2006 AAL Relevance As AAL flats may be located in larger building complexes with centralised caretaking and management this standard should be taken into account. Available from http://www.gefma.de/fm_excellence.html V1.0 2013-01-15 Page 418 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard GEFMA710 GEFMA720 GEFMA730ff Title Single Service provisioning Package Service provisioning System Service provisioning Description For Facility Management the FM Excellence program describes three stages of quality management. In GEFMA710 directions are provided for quality management in general management, workshops, operation, catering, cleaning, protection and safety. GEFMA720 deals with occupational safety and health management, environmental management, risk management and quality management. GEFMA730ff tops this off with integral process responsibility. 11.5.2 Other NEN-EN-ISO 9999_2011 Profile Reference Name NEN-EN-ISO 9999:2011 NEN-EN-ISO 9999:2011 Assistive products for persons with disability Classification and terminology Categories Specifications and standards for operator models; Other relevant standards and certifications; ICS 11.180.01 - Aids for disabled and handicapped persons in general Abstract A classification of assistive products for persons with disability. Current Version 2011-07 Other editions NF EN ISO 9999:2007; NF EN 29999:1994 AAL Relevance AAL products can be used by people with disabilities; classifications improve the quality and safety of products Available from http://www.nen.nl/web/Normshop/Norm/NENENISO-99992011-en.htm Description This standard describes how assistive products (including software) for people with disabilities can be classified according to their function. The current edition has about 980 titles in three hierarchic levels. The classified products are intended to be used both inside and outside healthcare settings, which makes this classification useful for AAL purposes. The definition of assistive products is inline with the terminology of the ICF. V1.0 2013-01-15 Page 419 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 12. Health Informatics CEN/TR 15300 Profile Reference Name CEN/TR 15300 CEN/TR 15300: Health informatics - Framework for formal modelling of healthcare security policies Categories Health Informatics; Personal Health Records; Data protection specifications ICS 35.240.80 : IT applications in health care technology Abstract This CEN Technical report specifies the starting point for working on some formalising tools that could be used by the healthcare actors to express, compare and validate local and/or network security policies Current Version CEN/TR 15300:2007 Other editions AAL Relevance Healthcare security policies may play a role in medical AAL applications. Available from http://www.cen.eu Description This CEN Technical report specifies the starting point for working on some formalising tools that could be used by the healthcare actors to express, compare and validate local and/or network security policies. Defining and validating a correct security policy encompass different activities such as expressing correctly (i.e. without any ambiguity), formulating correctly (i.e. without any misinterpretation) and proving the correctness (i.e. without known failures or major lack) of the [to be formally modelled] security policy. This CEN Technical report does NOT intend at all to specify a UNIQUE or UNIVERSAL formal model that need to be used by the European healthcare community: it only indicates, as a first working step, some ways that could be followed to help that healthcare community to correctly and fruitfully manipulate the security policy concept(s) and the formal modelling techniques. This CEN Technical report does NOT intend to indicate an EXHAUSTIVE spectrum of all the published formal security policy models: it only gives a readable and understandable flavour of the most well-known formal models and also of the [maybe] most interesting ones from the healthcare activity and needs point of view. [Source: lsd.it] External links • http://www.lsd.lt/standards/catalog.php?ics=0&pid=605687 V1.0 2013-01-15 Page 420 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot CEN/TR 15640 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from CEN/TR 15640 CEN/TR 15640: Health informatics - Measures for ensuring the patient safety of health software Health Informatics; Personal Health Records 35.240.80: IT applications in health care technology CEN/TR 15640 considers the control measures required to ensure patient safety in respect to health software products. CEN/TR 15640:2007 This standard is relevant to AAL because it regards the safety of AAL products. http://shop.bsigroup.com/ProductDetail/?pid=000000000030149192 Description PD CEN/TR 15640 considers the control measures required to ensure patient safety in respect to health software products. PD CEN/TR 15640 is a document that aims to identify what standards might best be used or created, and their nature, if health software products were to be regulated or controlled in some other formal or informal or voluntary manner whether national, regional or local. However it is not the purpose of this document to recommend whether or not health software products should be regulated. This document applies to any health software product whether or not it is placed on the market and whether or not it is for sale or free of charge. It is addressed to manufacturers of health software products. The scope is intended to cover health software products which are not, in practice, covered by medical device regulations, and PD CEN/TR 15640 considers this matter in detail. PD CEN/TR 15640 acknowledges that, on the boundary, there are health software products that are encompassed by medical device regulations in some countries but not in others and that some definitions of medical devices may appear to cover health software products in general but in practice do not. [Source: BSI shop] The safety of medicines and of medical devices is ensured in many countries through a variety of legal and administrative measures. In the European Union it is subject to several EU directives. These measures are often backed by a range of safety related standards from a number of sources, both national and international, including the European Standards Organisation (CEN), the International Standards Organisation (ISO) and the International Electrotechnical Committee (IEC). Some software such as that necessary for the proper application or functioning of a medical device is often encompassed by these legislative controls. However other software applied to health of a stand-alone nature is not usually covered or is encompassed in a less than clear manner. This document is V1.0 2013-01-15 Page 421 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot concerned with software applied to health excluding that which is encompassed by medical device controls. A necessary precursor for determining and implementing appropriate design and production controls to minimise risks to patients from product malfunction or inadequate performance, is a clear understanding of the hazards which a product might present to patients if malfunction or an unintended event should occur, and the likelihood of such a malfunction or event causing harm to the patient. Additionally if guidance is to be given to designers and producers of health software products as to design and production control (and corresponding standards produced) then it will need to be recognised that the controls necessary for products presenting low risks will not be the same as for those presenting high risks. Controls need to match the level of risk which a product might present to a patient. For these purposes many standards, legislation and specifications dealing with control of risks in design and production, group products in to a limited number of classes or types according to the risk they might present. Controls are then tailored to the class or type. This document follows that philosophy. There is a wide range of controls which might be exerted on the design, development, production, distribution, installation, up-grading/version control/up-dating of a health software product etc. This document starts with considering how those controls are applied to medical devices and offers practical solutions how to adapt them to health software products. [source: standard document] External links • http://shop.bsigroup.com/ProductDetail/?pid=000000000030149192 CEN/TS 15260 Profile Reference Name CEN/TS 15260 CEN/TS 15260: Health informatics - Classification of safety risks from health informatics products Categories Health Informatics; Personal Health Records; Quality and risk management of medical devices ICS 35.240.80: IT applications in health care technology Abstract CEN/TS 15260 is concerned with software applied to health which is not encompassed by EU Directives covering medical devices. (from Introduction of the standard, see external link) Current Version CEN/TS 15260:2006 Other editions AAL Relevance This standard may be relevant to AAL because it regards a classification of risks that may affect the users of AAL systems Available from http://shop.bsigroup.com/ProductDetail/?pid=000000000030124364 V1.0 2013-01-15 Page 422 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description A necessary precursor for determining and implementing appropriate design and production controls to minimise risks to patients from product malfunction or inadequate performance, is a clear understanding of the hazards which a product might present to patients if malfunction or an unintended event should occur and the likelihood of such a malfunction or event causing harm to the patient. Additionally if guidance is to be given to designers and producers of health informatics products as to design and production control (and corresponding standards produced) then it will need to be recognised that the controls necessary for products presenting low risks will not be the same as for those presenting high risks. Controls need to match the level of risk which a product might present to a patient. For these purposes many standards, legislation and specifications dealing with control of risks in design and production, group products in to a limited number of classes or types according to the risk they might present. This document presents a process for such a grouping of health informatics products. It proposes five risk classes. This will facilitate broad screening of generic product types and of individual products to allow different levels of, or rigour in, the application of design and production controls which are matched to risk. Thus the classification proposed may be a precursor for standards on design and production control, where the latter might require a far more detailed, in depth and rigorous risk analysis for a particular product than that required for the broad classification process in this document. Examples of the application of the process for assigning a risk class are given for a number of different types of health informatics products. By ‘health informatics products’ is meant any health informatics product whether or not it is placed on the market and whether or not it is for sale or free of charge. This document thus covers commercial products as well as, for example, open-source health informatics software and software created for, and used in, only one health organisation such as a hospital. [source: standard document] External links • PreStandard CEN/TS 15260 CSN CR 14301 Profile Reference Name CSN CR 14301 CSN CR 14301: Health informatics - Framework for security protection of healthcare communication Categories Health Informatics; Personal Health Records ICS 35.240.80: IT applications in health care technology Abstract This report gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services Current Version CR 14301:2002 V1.0 2013-01-15 Page 423 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance This standard is relevant to AAL because it also regards medical devices. Available from http://www.cen.eu/CEN/Sectors/TechnicalCommitteesWorkshops/CEN TechnicalCommittees/Pages/Standards.aspx? param=6232&title=CEN/TC+251 Standard Parts Standard CSN CR 14301 Title Health informatics - Framework for security protection of healthcare communication Description This report gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services. The report also gives important advice for passive devices such as magnetic stripe card systems or floppy disks. The major focus is on systems for handling sensitive medical information on devices (mainly cards) held by patients. However, some requirements on ICDs to be used by health care persons (professionals and others) are also given. Detailed protocols for interaction between such devices and general medical information systems for the purpose of secure user identification will be developed within a separate work item. CR 14302 Profile Reference Name CR 14302 CR 14302: Health informatics - Framework for security requirements for intermittently connected devices Categories Health Informatics; Personal Health Records ICS 11.020: Medical sciences and health care facilities in general 35.240.80: IT applications in health care technology Abstract The standard gives detailed security requirements for active devices such as microprocessor cards, which are the only possibilities to implement some of the proposed services. Current Version CR 14302:2002 Other editions AAL Relevance This standard may be relevant to AAL because it regards security mechanisms for electronic devices. Available from http://infostore.saiglobal.com/store/Details.aspx?ProductID=268273 Description Intermittently connected devices such as patient cards may carry important clinical information as well as administrative data of importance to health care delivery. The information regarding an identifiable individual is always sensitive and with clinical data it is V1.0 2013-01-15 Page 424 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot particularly important to provide appropriate means to ensure the protection of confidentiality. In addition several other security services must be ensured to protect the patient safety as well as accountability of the professionals responsible for recording data and reading data from intermittently connected devices. Health care person devices, particularly microprocessor cards, carried by professionals and other persons working in the health care sector, may play an important role in the provision of security for all health information systems for the following core functions; to provide a secure user authentication, to provide a digital signature mechanism and as a means to carry cryptographic keys for confidentiality protection of stored and communicated health care information. The authentication function may serve as a key to protected data on a Patient data card. [source: standard document] ISO/EN 13606 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/EN 13606 ISO/EN 13606: Electronic Health Record Communication (EHRcom) Health informatics; Personal Health Record; File Formats and Persistent Data Structures; General Purpose; Medical; ISO; EN 35.240.80: IT applications in health care technology The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). see Standard Parts below This standard is relevant to PHRs, EHRs and thereby to AAL. see Standard Parts below Standard Parts Standard ISO 13606-1:2007 ISO 13606-2:2007 ISO 13606-3:2008 ISO/TS 13606-4:2007 ISO 13606-5:2010 V1.0 Title Health informatics - Electronic health record communication Part 1: Reference model Health informatics - Electronic health record communication Part 2: Archetypes interchange specification Health informatics - Electronic health record communication Part 3: Reference archetypes and term lists Health informatics - Electronic health record communication Part 4: Security Health informatics - Electronic health record communication Part 5: Interface specification (ISO 13606-5:2010) 2013-01-15 Page 425 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description The overall goal of this Health informatics - Electronic Health Record Communication (EN 13606) European Standard is to define a rigorous and stable information architecture for communicating part or all of the Electronic Health Record (EHR) of a single subject of care (patient). This is to support the interoperability of systems and components that need to communicate (access, transfer, add or modify) EHR data via electronic messages or as distributed objects: • preserving the original clinical meaning intended by the author; • reflecting the confidentiality of that data as intended by the author and patient. The name of this European Standard suggests that it is not intended to specify the internal architecture or database design of EHR systems or components, but the scope includes the use of an 'object'. This implies that the 'objects' can be stored, retrieved and exchanged. It is explicitly not intended to prescribe the kinds of clinical applications that might request or contribute EHR data in particular settings, domains or specialities. For this reason, the information model proposed here is called the EHR Extract, and might be used to define a message, an XML document or schema, or an object interface. The information model in this European Standard is an ISO RM-ODP Information Viewpoint of the EHR Extract. This European Standard considers the EHR to be the persistent longitudinal and potentially multi-enterprise or multi-national record of health and care provision relating to a single subject of care (the patient), created and stored in one or more physical systems in order to inform the subject’s future health care and to provide a medico-legal record of care that has been provided. Whilst an EHR service or system will need to interact with many other services or systems providing terminology, medical knowledge, guidelines, workflow, security, persons registries, billing etc. this European Standard has only touched on those areas if some persistent trace of such interactions is required in the EHR itself, and requires specific features in the reference model to allow their communication. This European Standard may offer a practical and useful contribution to the design of EHR systems but will primarily be realised as a common set of external interfaces or messages built on otherwise heterogeneous clinical systems. The openEHR Framework is the basis of this new Electronic Health Record Communication Standard (EN 13606) [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/EN_13606 EN 13609-1 Profile Reference Name V1.0 EN 13609-1 EN 13609-1: Health informatics - Messages for maintenance of supporting information in healthcare systems - Part 1: Updating of coding scheme 2013-01-15 Page 426 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories ICS Abstract Health Informatics; Medical Terminology 35.240.80: IT applications in health care technology This European Standard specifies messages for electronic information exchange between computer systems using coding schemes in healthcare. Current Version EN 13609-1:2005 Other editions AAL Relevance This standard may be relevant to AAL due to its relation to medical coding schemes Available from http://www.lsd.lt/standards/catalog.php?ics=35.240.80&pid=605690 Description EN 13609-1 specifies messages for electronic information exchange between computer systems using coding schemes in healthcare. It describes a message that may be used to populate or update the content of a coding scheme at user applications. EN 13609-1 is limited to a definition of the content of a message that serves the following functions: • a) to populate a new coding scheme where individual entries are composed of a code value related to zero or more (textual) code meanings, • b) to add new entries into an existing coding scheme where these entries are composed of new code values and their associated meanings, • c) to mark existing code value entries as no longer active, • d) to mark new and existing code meanings to be of a certain status (e.g. preferred, obsolete, etc.), • e) to mark new and existing code values with dates of applicability, f) to mark new and existing code meanings with dates of applicability. EN 13609-1 provides a specification of a message that may be used to populate or update a mapping between a single code value in a coding scheme and simple list of code values that together have an equivalent meaning in the same coding scheme. This meets the requirements of ENV1614 - Healthcare Informatics - Structure for nomenclature, classification and coding of properties in clinical laboratory sciences. EN 13609-1 provides a specification of a message that may be used to populate or update a mapping showing equivalence between code values in two different coding schemes. The specification supports mappings in which: • a) a single code value in one (source) coding scheme is mapped to a single equivalent code value within another (target) coding scheme, • b) a single code value in the source coding scheme is mapped to a set of code values which together represent an equivalent concept within the target coding scheme. [Source: en-standard.eu] V1.0 2013-01-15 Page 427 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.en-standard.eu/de/csn-en-13609-1-health-informatics-messages-formaintenance-of-supporting-information-in-healthcare-systems-part-1-updating-of-codingschemes/ EN 13940-1 Profile Reference Name EN 13940-1 EN 13940-1: Health informatics - System of concepts to support continuity of care - Part 1: Basic concepts Categories Personal Health Records; Health Informatics ICS 35.240.80: IT applications in health care technology Abstract This International Standard seeks to identify and define those processes which relate to co-operation between all parties involved in health care provided to human beings (to the exclusion of other living subjects). Current Version EN 13940-1:2007 Other editions AAL Relevance Due to its relation to longitudinal PHRs this standard is relevant to AAL. Available from http://www.named.din.de/projekte/DIN+EN+139401+rev/en/143993873.html Description This International Standard seeks to identify and define those processes which relate to co-operation between all parties involved in health care provided to human beings (to the exclusion of other living subjects).Given the definition of health as agreed by WHO, this International Standard will include those aspects of health care that rely on the acts of other actors than simply health care professionals. This International standard specifically addresses aspects of sharing information related to a subject of care that is needed in the process of health care. This International multi-part Standard addresses topics including: • health care actors and other parties; • organisational principles of health care, including co-operation between actors; • health issues, health conditions and their management; • time-related concepts like contacts, encounters, episodes of care and periods of care; • concepts related to process, workflow and activities; • concepts related to decision support, use of clinical knowledge and quality; • concepts related to responsibility and information flows within the clinical process, like health mandates and their notification; • concepts related to health data management. V1.0 2013-01-15 Page 428 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Whenever continuity of health care delivery implies social care activities as part of, or in support to, the process towards health recovery, these are to be mentioned wherever relevant in the process and workflow. In order to establish a common conceptual framework for continuity of care across national, cultural and professional barriers, all these concepts are defined in this document, and their inter-relationships identified. [source: DIN] In order to establish a common conceptual framework for continuity of care across national, cultural and professional barriers, all these concepts are defined in this document, and their inter-relationships identified. The system of concepts and the terms defined in this European standard are designed to support the management of health care related information over time and the delivery of care by different health care agents who are working together. This includes primary care professionals and teams, health care funding organisations, managers, patients, secondary and tertiary health care providers, and community care teams. This harmonised system of concepts will be used to facilitate clinical and administrative decision making, health care logistics such as provision of coherent services— and to enhance relationships between healthcare professionals and their patients. Within this European standard, 'subject of care' —a concept definitely restricted here to human beings refers to an individual. It is assumed that in those cases where a health care activity addresses a group of more than one individual (e.g. a family, a community, etc.), and where a single health record is used to capture the health care activities provided to the group, each individual within the group will be referenced explicitly within that health record. [source: standard document] External links • http://www.named.din.de/projekte/DIN+EN+13940-1+rev/en/143993873.html EN 14484 Profile Reference Name EN 14484 EN 14484: Health informatics - International transfer of personal health data covered by the EU data protection directive - High level security policy Categories Heath Informatics; Personal Health Records; Data protection specifications ICS 35.240.80: IT applications in health care technology Abstract This standard provides guidance on a High Level Security Policy for third country organisations and is restricted to aspects relevant to personal health data transferred from a compliant country to a third country. (from webshop.ds.dk) Current Version EN 14484:2003 V1.0 2013-01-15 Page 429 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance This standard may be relevant to AAL if personal health data is sent over country borders. Available from http://shop.bsigroup.com/ProductDetail/?pid=000000000030078508 Description EN 14484 will provide guidance on the data protection policy which should be implemented by organisations which are participants in international applications which involve transfer of person identifiable data across national borders and which require compliance with the EU Data Protection Directive. (from CEN) External links • http://www.cen.eu/CEN/sectors/sectors/isss/Pages/default.aspx • http://shop.bsigroup.com/ProductDetail/?pid=000000000030078508 EN 14485 Profile Reference Name EN 14485 EN 14485:2003: Health informatics - Guidance for handling personal health data in international applications in the context of the EU data protection directive Categories Health Informatics; Personal Health Records; Data protection specifications ICS 35.240.80: IT applications in health care technology Abstract This standard provides guidance on data protection for those involved in international informatics applications which entail transmission of person health data from an EU Member State to a non-EU Member State. Its purpose is to assist in the application of the EU Directive on Data Protection. (from cen.eu, see external link) Current Version EN 14485:2003 Other editions AAL Relevance This standard may be relevant to AAL if personal health data is sent over country borders to non-EU member states. Available from http://shop.bsigroup.com/ProductDetail/?pid=000000000030078512 External links • http://www.cen.eu/cen/pages/default.aspx V1.0 2013-01-15 Page 430 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot EN ISO 10781 Profile Reference Name EN ISO 10781 EN ISO 10781: Electronic Health Record-System Functional Model, Release 1.1 (ISO 10781:2009) Categories Personal Health Records; Health Informatics ICS 35.240.80: IT applications in health care technology Abstract ISO 10781:2009 describes the content and means of functioning of the electronic health record system of the HL7 EHR Work Group. Current Version EN ISO 10781:2012-04 Other editions AAL Relevance This standard is relevant to EHRs and thereby to AAL. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=46087 Description This standard is based on the work of HL7. It defines a function model for electronic health records. External links • ISO/HL7 10781 EHRS FM Release 2 ENV 12443 Profile Reference Name ENV 12443 ENV 12443: Medical Informatics - Healthcare Information Framework (HIF) Categories Health Informatics ICS 35.240.80: IT applications in health care technology Abstract This European Prestandard sets out to establish general concepts, requirements, relationships, context and the terminology to be used in subsequent developments of specific standards for healthcare domain specific informatics standards. Current Version ENV 12443:1999 Other editions AAL Relevance As this standard regards different aspects of medical informatics, it may be relevant to AAL Available from http://shop.bsigroup.com/ProductDetail/?pid=000000000030018279 V1.0 2013-01-15 Page 431 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description This European Prestandard establishes the Healthcare Information Framework (HIF) as a logical mapping between the healthcare environment and informatics applications which support and facilitate clinical and other functions. This European Prestandard specifies the set of requirements, recommendations and guidelines which apply to developments within CEN/TC 251 which enable consistent development and evolution of healthcare domain specific informatics standards. This European Prestandard is applicable to, and will be primarily used by, healthcare domain specific informatics standards writers and, in particular, those writing Healthcare Reference Architectures standards. [source: standard document] ENV 13607 Profile Reference Name ENV 13607 ENV 13607: Health informatics - Messages for the exchange of information on medicine prescriptions Categories Health Informatics; Personal Health Records ICS 35.240.80: IT applications in health care technology Abstract This European Prestandard specifies general messages for electronic information exchange between computer systems used by healthcare parties prescribing, dispensing or administering medicinal products/medicinal appliances Current Version ENV 13607:2000 Other editions AAL Relevance This standard is relevant to AAL because it regards the exchange of prescriptions, which may be relevant to AAL applications. Available from http://shop.bsigroup.com/ProductDetail/?pid=000000000030012311 Description This European prestandard is applicable to the issue of new prescription messages carrying a first date for dispensing. Such messages may be used according to national regulations e.g. in countries where repeat prescribing is not allowed. The mechanisms and rules for checking and releasing these new prescription messages are outside the scope of this European prestandard. When implementing information exchange based upon this European prestandard, data protection and confidentiality principles have to be guaranteed according to the laws actually in force in the different CEN member countries. The mechanisms needed to secure data integrity, data protection and confidentiality, authentication of communicating parties and patients are outside the scope of this European prestandard. While the messages specified in this European prestandard may convey clinical and administrative information concerning patients, the way in which this information is treated V1.0 2013-01-15 Page 432 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot in this European prestandard does not constrain the development of future standards for the electronic healthcare record or for other clinical and administrative messages. [source: standard document] ISO 17090 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO 17090 Health informatics – Public key infrastructure Health informatics; Privacy and Security; Data protection specifications 35.240.80: IT applications in health care technology ISO 17090-3:2008 gives guidelines for certificate management issues involved in deploying digital certificates in healthcare. see Standard Parts below This standard is relevant to AAL because it regards security infrastructure that is necessary for AAL-Applications. see Standard Parts below Standard Parts Standard ISO 17090-1:2008 ISO 17090-2:2008 ISO 17090-3:2008 Title Health informatics – Public key infrastructure – Part 1: Overview of digital certificate services Health informatics – Public key infrastructure – Part 2: Certificate profile Health informatics – Public key infrastructure – Part 3: Policy management of certification authority Description ISO 17090-3:2008 gives guidelines for certificate management issues involved in deploying digital certificates in healthcare. It specifies a structure and minimum requirements for certificate policies, as well as a structure for associated certification practice statements. ISO 17090-3:2008 also identifies the principles needed in a healthcare security policy for cross-border communication and defines the minimum levels of security required, concentrating on aspects unique to healthcare. [Source: ISO] Interoperability of PKI technology and supporting policies, procedures, and practices is of fundamental importance if information is to be exchanged between organisations and between jurisdictions in support of health care applications (for example between a hospital and a community physician working with the same patient). Achieving interoperability between different PKI schemes, not only requires that technical V1.0 2013-01-15 Page 433 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot interoperability be achieved, but most importantly, the establishment of a framework of trust under which parties responsible for protecting an individual’s information rights may rely on the policies and practices and, by extension, the validity of digital certificates issued by other established authorities. Many countries are adopting public key infrastructures to support secure communications within their national boundaries. Inconsistencies will arise in policies and procedures between the Certification and Registration Authorities of different countries, if PKI standards development activity is restricted to within national boundaries. Public Key Infrastructure technology is still rapidly evolving in certain aspects that are not specific to health care. Important standardization efforts and in some cases supporting legislation are ongoing. On the other hand health care providers in many countries are already using or planning to use PKI. This Technical Specification seeks to address the need for guidance of these rapid international developments. […] This three-part ISO Technical Specification (ISO/TS) describes the common technical, operational and policy requirements that need to be addressed to enable Public Key Infrastructures (PKI) to be used in protecting the exchange of health care information within a single domain, between domains and across jurisdictional boundaries. The purpose of this technical specification is to create a platform for global interoperability. It specifically supports PKI enabled communication across borders but the specification could also provide guidance for the establishment of health care PKIs nationally or regionally. The Internet is increasingly used as the vehicle of choice to support the movement of health care data between health care organisations and is the only realistic choice for cross-border communication in this sector. [source: standard document] ISO/TR 16056 Profile Reference Name Categories ICS ISO/TR 16056 Health informatics – Interoperability of telehealth systems and networks Health Informatics; Personal Health Records; Medical Devices 01.040.35: Information technology. Office machines (Vocabularies); 35.240.80: IT applications in health care technology Abstract ISO/TR 16056-1:2004 gives a brief introduction to interoperability of telehealth systems and networks, along with definitions of telehealth and related terms. Current Version see Standard Parts below Other editions AAL Relevance This standard may be relevant to AAL because it provides an abstract overview of telehealth components, which have to be used for interoperability of AAL-Applications. Available from see Standard Parts below V1.0 2013-01-15 Page 434 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Standard Parts Standard ISO/TR 16056-1:2004 ISO/TR 16056-2:2004 Title Health informatics – Interoperability of telehealth systems and networks – Part 1: Introduction and definitions Health informatics – Interoperability of telehealth systems and networks – Part 2: Real-time systems Description ISO/TR 16056-1:2004 gives a brief introduction to interoperability of telehealth systems and networks, along with definitions of telehealth and related terms. An informative annex describing the Telehealth Technical Reference Architecture has also been included to describe more clearly the various components of a telehealth system and the elements that need to be addressed in formulating a set of requirements for these various components. The scope of the document does not include conformity and interoperability tests or functional specifications for telehealth systems and networks. [Source: ISO] V1.0 2013-01-15 Page 435 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 13. Localization 13.1. Localization and Navigation ISO 14825:2011 (version 5.0) Profile Reference Name Categories ICS ISO 14825:2011 GDF: Geographic Data Files ISO; 03.220.01 - Transport in general; 35.240.60 - IT applications in transport and trade; 35.240.70 - IT applications in science Abstract Geographic Data Files or GDF is an interchange file format for geographic data. In contrast with generic GIS formats, GDF provides detailed rules for data capture and representation, and an extensive catalogue of standard features, attributes and relationships. Current Version ISO 14825:2011 (version 5.0) Other editions AAL Relevance The international standard on road networks and other geographic data is important for outdoor localization of older adults. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=54610 Description GDF is an international standard that is used to model, describe and transfer road networks and other geographic data. The standard was initially drawn up by European Committee for Standardization (CEN) in co-operation with digital map providers, automotive and electronic equipment manufacturers. The outcome of these standardisation efforts (CEN GDF 3.0, or ENV14825:1996) has formed the major input to a global standard created by ISO/TC204 Sub Working group 3: • ISO GDF 4.0, formally referred to ISO14825:2004, now replaced by • ISO GDF 5.0, formally referred to ISO14825:2011. However, despite the existence of an ISO GDF standard, the nature of model abstractions as well as semantic interpretations and proprietary content extensions lead to interoperability issues between flavours of GDF map products from different vendors. In practice the GDF files are not fully interchangeable due to vendor specific extensions. To this end, GDF5.0 provides major improvements in terms of extended meta data and flags for signalling implementation choices. The new GDF5.0 V1.0 2013-01-15 Page 436 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot The specifications of GDF5.0 were developed and compiled between 2001 and 2008, involving experts from Australia, Canada, Czech Republic, France, Germany, Japan, Republic of Korea, the Netherlands, and the United States of America. Extensive activities towards harmonization with ISO/TC211 standards were undertaken. GDF 5.0 was published in July 2011. Major GDF5.0 enhancements include UML model migration & refinements; harmonization with linear referencing and geo-spatial web standards; support for 3-D content and time coordinates; comprehensive character set and phonetic representations; and new XML and SQL based delivery formats. [Source: Wikipedia] External links • GDF 5.0 standard on ISO website • Ertico website on GDF • http://en.wikipedia.org/wiki/Geographic_Data_Files ISO 19136 Profile Reference Name ISO 19136 ISO 19136: Geographic information – Geography Markup Language (GML) Categories Localization; Localization and Navigation; ISO ICS 35.240.70 - IT applications in science Abstract The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. Current Version ISO 19136:2007 Other editions AAL Relevance The international standard on road networks and other geographic data is important for outdoor localization of older adults. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=32554 Description The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. V1.0 2013-01-15 Page 437 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO 19136:2007 defines the XML Schema syntax, mechanisms and conventions that: • Provide an open, vendor-neutral framework for the description of geospatial application schemas for the transport and storage of geographic information in XML; • Allow profiles that support proper subsets of GML framework descriptive capabilities; • Support the description of geospatial application schemas for specialized domains and information communities; • Enable the creation and maintenance of linked geographic application schemas and datasets; • Support the storage and transport of application schemas and data sets; • Increase the ability of organizations to share geographic application schemas and the information they describe. Implementers may decide to store geographic application schemas and information in GML, or they may decide to convert from some other storage format on demand and use GML only for schema and data transport. [Source: ISO, accessed 2012-10-08] External links • Geographic information -- Geography Markup Language (GML) • ISO 19136 NMEA 0183 Profile Reference Name Categories ICS Abstract NMEA 0183 NMEA 0183 Communication Protocols NMEA 0183 is a combined electrical and data specification for communication between marine electronic devices such as echo sounder, sonars, anemometer, gyrocompass, autopilot, GPS receivers and many other types of instruments. It has been defined by, and is controlled by, the U.S.-based National Marine Electronics Association. Current Version Other editions AAL Relevance The international standard on road networks and other geographic data is important for outdoor localization of older adults. Available from http://www.gpsinformation.org/dale/nmea.htm Description NMEA 0183 is a combined electrical and data specification for communication between V1.0 2013-01-15 Page 438 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot marine electronic devices such as echo sounder, sonars, anemometer, gyrocompass, autopilot, GPS receivers and many other types of instruments. It has been defined by, and is controlled by, the U.S.-based National Marine Electronics Association. The electrical standard that is used is EIA-422 although most hardware with NMEA-0183 outputs are also able to drive a single EIA-232 port. Although the standard calls for isolated inputs and outputs there are various series of hardware that do not adhere to this requirement. The NMEA 0183 standard uses a simple ASCII, serial communications protocol that defines how data is transmitted in a “sentence” from one “talker” to multiple “listeners” at a time. Through the use of intermediate expanders, a talker can have a unidirectional conversation with a nearly unlimited number of listeners, and using multiplexers, multiple sensors can talk to a single computer port. At the application layer, the standard also defines the contents of each sentence (message) type so that all listeners can parse messages accurately. Serial configuration: • Typical baud rate: 4800 • Data bits: 8 • Parity: None • Stop bits: 1 • Handshake: None [Source: Wikipedia, accessed 2012-10-02] External links • http://en.wikipedia.org/wiki/NMEA_0183 • NMEA data • The NMEA 0183 Protocol RTCM SC-104 Profile Reference Name Categories ICS Abstract V1.0 RTCM SC-104 RTCM SC-104: Radio Technical Commission for Maritime Services (RTCM) Communication Protocols 35.240.70 - IT applications in science 33.030 - Telecommunication services. Applications 33.040.99 - Other equipment for telecommunication systems 33.070.01 - Mobile services in general 47.020.70 - Navigation and control equipment Industry standard for communication of correction information, often 2013-01-15 Page 439 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot used in Differential GPS and Real Time Kinematic operations. Current Version see Standard Parts below Other editions AAL Relevance The international standard on road networks and other geographic data is important for outdoor localization of older adults. Available from ftp://gis.leicageosystems.com/GPS/Outgoing/GS5_Resources/GS5%20Specificatio ns/136-2001-SC104-STD-RTCM%20ETC%20VER %202.3_4Leica_internal.pdf Standard Parts Standard RTCM 10402.3 RTCM 10403.1 RTCM 10410.0 RTCM 10401.2 Title RTCM Recommended Standards for Differential GNSS (Global Navigation Satellite Systems) Service, Version 2.3. This standard is used around the world for differential satellite navigation systems, both maritime and terrestrial. Differential GNSS (Global Navigation Satellite Systems) Services Version 3 - A more efficient alternative to RTCM 10402.3 Standard for Networked Transport of RTCM via Internet Protocol (Ntrip) (RTCM Paper 200-2004/SC104-STD, Version 1.0) - An applicationlevel protocol that supports streaming Global Navigation Satellite System (GNSS) data over the Internet. Standard for Differential Navstar GPS Reference Stations and Integrity Monitors (RSIM) - A companion to RTCM 10402.3, this standard addresses the performance requirements for the equipment which broadcasts DGNSS corrections. Description The Radio Technical Commission for Maritime Services (RTCM) is an international nonprofit scientific, professional and educational organization. RTCM members are organizations (not individuals) that are both non-government and government. Although started in 1947 as a U.S. government advisory committee, RTCM is now an independent organization supported by its members from all over the world. RTCM Special Committees are formed to provide in-depth areas of concern to the RTCM membership, these special committees normally produce documents in the form of standards. Current special committees are: • Special Committee (SC) 101 on Digital Selective Calling (DSC) • Joint Special Committee (SC) 101/110 on GPS Equipped Hand Held VHF Radios • Special Committee (SC) 104 on Differential Global Navigation Satellite Systems (DGNSS). Provides standards that are often used in Differential GPS and Real Time Kinematic operations. • Special Committee (SC) 109 on Electronic Charts • Special Committee (SC) 110 on Emergency Beacons (EPIRBs and PLBs) V1.0 2013-01-15 Page 440 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Special Committee (SC) 117 on Maritime VHF Interference • Special Committee (SC) 119 on Maritime Survivor Locator Devices • Special Committee (SC) 121 on Automatic Identification Systems (AIS) and digital Messaging • Special Committee (SC) 123 on VHF-FM Digital Small Message Services • Special Committee (SC) 127 on Enhanced Loran (eLoran) • Special Committee (SC) 128 on Satellite Emergency Notification Device (SEND) [Source: Wikipedia, accessed 2012-10-02] External links • http://en.wikipedia.org/wiki/RTCM • RTCM Recommended Standards for Differential GNSS (Global Navigation Satellite Systems) Service v2.3 • Radio Technical Commission for Maritime Services (RTCM) 13.2. Interoperability of location-based applications and services ISO 19101 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO 19101 ISO 19101: Geographic information – Reference model Localization; Localization and Navigation; ISO 35.240.70 - IT applications in science This International Standard defines the framework for standardization in the field of geographic information. ISO 19101:2002 This reference model for geographic information is important for outdoor localization and navigation for older adults. http://www.iso.org/iso/catalogue_detail.htm?csnumber=26002 Description This International Standard defines the framework for standardization in the field of geographic information and sets forth the basic principles by which this standardization takes place. This framework identifies the scope of the standardization activity being undertaken and the context in which it takes place. The framework provides the method by which what is to V1.0 2013-01-15 Page 441 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot be standardized can be determined and describes how the contents of the standards are related. Although structured in the context of information technology and information technology standards, this International Standard is independent of any application development method or technology implementation approach. (from ISO.org) It is being revised by ISO/DIS 19101-1, Geographic information - Reference model – Part 1: Fundamentals. External links • http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm? csnumber=59164 ISO 19136 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO 19136 ISO 19136: Geographic information – Geography Markup Language (GML) Localization; Localization and Navigation; ISO 35.240.70 - IT applications in science The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. ISO 19136:2007 The international standard on road networks and other geographic data is important for outdoor localization of older adults. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=32554 Description The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. ISO 19136:2007 defines the XML Schema syntax, mechanisms and conventions that: • Provide an open, vendor-neutral framework for the description of geospatial application schemas for the transport and storage of geographic information in XML; V1.0 2013-01-15 Page 442 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • Allow profiles that support proper subsets of GML framework descriptive capabilities; • Support the description of geospatial application schemas for specialized domains and information communities; • Enable the creation and maintenance of linked geographic application schemas and datasets; • Support the storage and transport of application schemas and data sets; • Increase the ability of organizations to share geographic application schemas and the information they describe. Implementers may decide to store geographic application schemas and information in GML, or they may decide to convert from some other storage format on demand and use GML only for schema and data transport. [Source: ISO, accessed 2012-10-08] External links • Geographic information -- Geography Markup Language (GML) • ISO 19136 JSR 179 Profile Reference Name Categories ICS Abstract JSR 179 JSR 179: JSR 179 v.2.1 – Location API for J2ME (Java Micro Edition) Localization; Localization and Navigation; Java 35.240.70 - IT applications in science Compact and generic Java 2 ME API that produces information about the device's present physical location to Java applications. Current Version 1.1 Other editions 1.0 / 1.0.1 AAL Relevance As AAL scenarios may include localisation aspects with mobile devices (e.g. in case of an emergency), this API is useful. Available from http://jcp.org/en/jsr/detail?id=179 Description The Location API for Java ME is a compact and generic Java 2 ME API that produces information about the device's present physical location to Java applications. This API can be optionally supported by mobile phone and PDA manufacturers, with the minimum Java platform required for this API being CLDC v1.1. The Location API was developed under the Java Community Process as JSR 179, released in September 2003 and updated to version 1.0.1 in March 2006. Nokia is the main author and maintainer of this JSR. [Source: Wikipedia] V1.0 2013-01-15 Page 443 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • http://www.developer.nokia.com/Community/Wiki/How_to_get_Location_Using_Location _API_JSR_179 • http://en.wikipedia.org/wiki/Location_API_for_Java_ME JSR 293 Profile Reference Name Categories ICS Abstract JSR 293 JSR 293: JSR 293 – Location API 2.0 Localization; Localization and Navigation; Java 35.240.70 - IT applications in science JSR 293 offers mobile location-based applications for resource limited devices. Current Version 2.0 Other editions AAL Relevance As AAL scenarios may include location-based services and may use resource limited devices JSR 293 may be useful. Available from http://jcp.org/en/jsr/detail?id=293 Description JSR 293 defines a Java ME Optional Package that enables mobile location-based applications for resource limited devices. The API is designed to be a compact and generic API that produces information about the present geographic location of the devices to Java applications. This API covers obtaining information about the present geographic location and orientation of the device and accessing a database of known landmarks stored in the device. [source: standard document] MLP Profile Reference Name Categories ICS Abstract MLP MLP: Mobile Location Protocol Localization; Localization and Navigation; 35.240.70 - IT applications in science The Mobile Location Protocol (MLP) is an application-level protocol for receiving the position of Mobile Stations (MS: mobile phones, wireless devices, etc.) independent of underlying network technology. Current Version 3.3 Other editions - V1.0 2013-01-15 Page 444 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot AAL Relevance As AAL scenarios may include localisation aspects with mobile devices (e.g. in case of an emergency), MLP might be useful. Available from http://technical.openmobilealliance.org/tech/affiliates/lif/lifindex.html Description The Mobile Location Protocol (MLP) is an application-level protocol for receiving the position of Mobile Stations (MS: mobile phones, wireless devices, etc.) independent of underlying network technology. The MLP serves as the interface between a Location Server and a location-based application. Basic MLP Services are based on location services defined by 3GPP. The Mobile Location Protocol (MLP) is described in LIF TS 101 Specification. The purpose of this technology is to define a simple and secure access method that allows mobile application to query location information from a wireless network, regardless of its underlying network technology and positioning methods. The MLP can be used by a location-based application to request mobile station location information from a location server (GMLC/MPC or other entity in the wireless network). This protocol has been prepared by Location Interoperability Forum (LIF: Open Mobile Alliance in nowadays) to provide a simple and secure API (Application Programmer’s Interface), but also could be used for other kinds of location servers and entities in the wireless network. The API is based on XML and is defined to be transported in HTTP or SOAP. Only mapping to HTTP is defined in present days. For security reasons Secure Socket Layer (SSL) or Transport Layer Security (TLS) cryptographic protocols can be used to carry HTTP (HTTPS). Apart from HTTPS Mobile Location Protocol which uses authentication by user and password, the information is carried in header part of MLP message. [Source: Wikipedia] External links • http://en.wikipedia.org/wiki/Mobile_Location_Protocol OpenLS Profile Reference Name Categories ICS Abstract OpenLS OpenLS: Open GIS Location Service Localization; Localization and Navigation; 35.240.70 - IT applications in science Open Location Services Interface Standard (OpenLS) offers locationbased services for mobile devices like navigation or localisation. Current Version 1.2.0 Other editions AAL Relevance As AAL scenarios may include outdoor location based services (like navigation to next pharmacy) OpenLS might be useful. Available from http://www.opengeospatial.org/standards/ols V1.0 2013-01-15 Page 445 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others. [Source: opengeospatial.org] External links • http://www.opengeospatial.org/standards/ols V1.0 2013-01-15 Page 446 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 14. Privacy and Security 14.1. Data protection specifications ISO IEC 10181 Profile Reference Name ISO IEC 10181 ISO IEC 10181: Information technology - Open Systems Interconnection - Security frameworks for open systems Categories Privacy and Security; Data protection specifications ICS 35.100.01: Open systems interconnection in general Abstract ISO IEC 10181 describes security frameworks for open systems whereas the term “Open Systems” is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios may include distributed applications and open systems this standard should be taken into account for security reasons. Available from see Standard Parts below Standard Parts Standard ISO/IEC 10181-1:1996 ISO/IEC 10181-2:1996 ISO/IEC 10181-3:1996 ISO/IEC 10181-4:1997 ISO/IEC 10181-5:1996 ISO/IEC 10181-6:1996 V1.0 Title Information technology – Open Systems Interconnection – Security frameworks for open systems: Overview Information technology – Open Systems Interconnection – Security frameworks for open systems: Authentication framework Information technology – Open Systems Interconnection – Security frameworks for open systems: Access control framework Information technology – Open Systems Interconnection – Security frameworks for open systems: Non-repudiation framework Information technology – Open Systems Interconnection – Security frameworks for open systems: Confidentiality framework Information technology – Open Systems Interconnection – Security frameworks for open systems: Integrity framework 2013-01-15 Page 447 of 490 AALIANCE2 ISO/IEC 10181-7:1996 D4.1 Online Repository of Standards - Snapshot Information technology – Open Systems Interconnection – Security frameworks for open systems: Security audit and alarms framework Description ISO/IEC 10181-2:1996 addresses the application of security services in an Open Systems environment, where the term Open Systems is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. ISO/IEC 10181-3:1996 specifies a general framework for the provision of access control. The purpose of access control is to counter the threat of unauthorized operations involving a computer or communication system. ISO/IEC 10181-5:1996 specifies a general framework for the provision of confidentiality services and ISO/IEC 10181-6:1996 specifies a general framework for the provision of integrity services. [Source: ISO] ISO/IEC 29100 Profile Reference Name ISO/IEC 29100 ISO/IEC 29100: Information technology – Security techniques – Privacy framework Categories Privacy and Security; Data protection specifications ICS 35.040: Character sets and information coding Abstract ISO/IEC 29100 provides a high-level framework for the protection of personally identifiable information (PII) within information and communication technology (ICT) systems. It is general in nature and places organizational, technical, and procedural aspects in an overall privacy framework. Current Version 2011 Other editions AAL Relevance As AAL scenarios use and collect personal informations of the user this standard should be taken into account. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=45123 Description The privacy framework is intended to help organizations define their privacy safeguarding requirements related to PII within an ICT environment by: • specifying a common privacy terminology; • defining the actors and their roles in processing PII; • describing privacy safeguarding requirements; and V1.0 2013-01-15 Page 448 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • referencing known privacy principles. In some jurisdictions, this International Standard’s references to privacy safeguarding requirements might be understood as being complementary to legal requirements for the protection of PII. Due to the increasing number of information and communication technologies that process PII, it is important to have international information security standards that provide a common understanding for the protection of PII. This International Standard is intended to enhance existing security standards by adding a focus relevant to the processing of PII. The increasing commercial use and value of PII, the sharing of PII across legal jurisdictions, and the growing complexity of ICT systems, can make it difficult for an organization to ensure privacy and to achieve compliance with the various applicable laws. Privacy stakeholders can prevent uncertainty and distrust from arising by handling privacy matters properly and avoiding cases of PII misuse. Use of this International Standard will: • aid in the design, implementation, operation, and maintenance of ICT systems that handle and protect PII; • spur innovative solutions to enable the protection of PII within ICT systems; and • improve organizations’ privacy programs through the use of best practices. The privacy framework provided within this International Standard can serve as a basis for additional privacy standardization initiatives, such as for: • a technical reference architecture; • the implementation and use of specific privacy technologies and overall privacy management; • privacy controls for outsourced data processes; • privacy risk assessments; or • specific engineering specifications. Some jurisdictions might require compliance with one or more of the documents referenced in ISO/IEC JTC 1/SC 27 WG 5 Standing Document 2 (WG 5 SD2) — Official Privacy Documents References or with other applicable laws and regulations, but this International Standard is not intended to be a global model policy, nor a legislative framework. [source: standard document] External links • http://webstore.iec.ch/preview/info_isoiec29100%7Bed1.0%7Den.pdf (free preview of standard) V1.0 2013-01-15 Page 449 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC CD 29101 Profile Reference Name ISO/IEC CD 29101 ISO/IEC CD 29101: Information technology – Security techniques – Privacy architecture framework Categories Privacy and Security; Data protection specifications ICS 35.040 Character sets and information coding Abstract ISO/IEC CD 29101 will offer best practices for consistent technical implementation of privacy principles. Current Version Draft International Standard, to be published by 2013-05-15 Other editions AAL Relevance As AAL scenarios use and collect personal informations of the user this standard should be taken into account. Available from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm ?csnumber=45124 Description ISO/ IEC 29101 • provides a consistent, high-level approach to the implementation of privacy safeguarding requirements to safeguard the processing of PII in ICT systems; • provides guidance for planning, designing and building ICT system architectures that more effectively facilitate the privacy of individuals by preventing inappropriate use of an individual's PII; and • show how privacy enhancing technologies can be used to enhance the implementation of privacy controls. ISO/ IEC 29101 sets up • organisational provisions that should be established; • PII protections mechanisms that should be integrated; • available PETs that should be used in privacy-enhanced systems. [Source: Weiß 2010, see link to presentation below; cited from ISO SC27 Document N8808 ISO/IEC 1st CD 29101] External links • https://www.datenschutzzentrum.de/sommerakademie/2010/sak10-weiss-internationalestandardisierung-im-datenschutz.pdf V1.0 2013-01-15 Page 450 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC WD 24760 Profile Reference Name ISO/IEC WD 24760 ISO/IEC WD 24760: Information Technology – Security Techniques – A Framework for Identity Management Categories Privacy and Security; Data protection specifications ICS 35.040 Character sets and information coding Abstract ISO/IEC WD 24760 offers a framework for identity management. Current Version see Standard Parts below Other editions AAL Relevance As AAL scenarios may have the need for identity management this standard should be taken into account. Available from see Standard Parts below Standard Parts Standard ISO/IEC 24760-1:2011 ISO/IEC CD 24760-2 ISO/IEC WD 24760-3 Title Information technology – Security techniques – A framework for identity management – Part 1: Terminology and concepts Information Technology – Security Techniques – A Framework for Identity Management – Part 2: Reference architecture and requirements Information Technology – Security Techniques – A Framework for Identity Management – Part 3: Practice Description Identity management (IdM) describes the management of individual identifiers, their authentication, authorization, and privileges within or across system and enterprise boundaries with the goal of increasing security and productivity while decreasing cost, downtime and repetitive tasks. [Source: Wikipedia] ISO/IEC 24760-1:2011 • defines terms for identity management, and • specifies core concepts of identity and identity management and their relationships. It is applicable to any information system that processes identity information. A bibliography of documents describing various aspects of identity information management is provided. [Source: ISO] External links • http://en.wikipedia.org/w/index.php?title=Identity_management&oldid=532252163 V1.0 2013-01-15 Page 451 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot (further information on identity management) ISO 17090 Profile Reference Name Categories ICS Abstract ISO 17090 Health informatics – Public key infrastructure Health informatics; Privacy and Security; Data protection specifications 35.240.80: IT applications in health care technology ISO 17090-3:2008 gives guidelines for certificate management issues involved in deploying digital certificates in healthcare. Current Version see Standard Parts below Other editions AAL Relevance This standard is relevant to AAL because it regards security infrastructure that is necessary for AAL-Applications. Available from see Standard Parts below Standard Parts Standard ISO 17090-1:2008 ISO 17090-2:2008 ISO 17090-3:2008 Title Health informatics – Public key infrastructure – Part 1: Overview of digital certificate services Health informatics – Public key infrastructure – Part 2: Certificate profile Health informatics – Public key infrastructure – Part 3: Policy management of certification authority Description ISO 17090-3:2008 gives guidelines for certificate management issues involved in deploying digital certificates in healthcare. It specifies a structure and minimum requirements for certificate policies, as well as a structure for associated certification practice statements. ISO 17090-3:2008 also identifies the principles needed in a healthcare security policy for cross-border communication and defines the minimum levels of security required, concentrating on aspects unique to healthcare. [Source: ISO] Interoperability of PKI technology and supporting policies, procedures, and practices is of fundamental importance if information is to be exchanged between organisations and between jurisdictions in support of health care applications (for example between a hospital and a community physician working with the same patient). Achieving interoperability between different PKI schemes, not only requires that technical interoperability be achieved, but most importantly, the establishment of a framework of trust under which parties responsible for protecting an individual’s information rights may rely on the policies and practices and, by extension, the validity of digital certificates issued V1.0 2013-01-15 Page 452 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot by other established authorities. Many countries are adopting public key infrastructures to support secure communications within their national boundaries. Inconsistencies will arise in policies and procedures between the Certification and Registration Authorities of different countries, if PKI standards development activity is restricted to within national boundaries. Public Key Infrastructure technology is still rapidly evolving in certain aspects that are not specific to health care. Important standardization efforts and in some cases supporting legislation are ongoing. On the other hand health care providers in many countries are already using or planning to use PKI. This Technical Specification seeks to address the need for guidance of these rapid international developments. […] This three-part ISO Technical Specification (ISO/TS) describes the common technical, operational and policy requirements that need to be addressed to enable Public Key Infrastructures (PKI) to be used in protecting the exchange of health care information within a single domain, between domains and across jurisdictional boundaries. The purpose of this technical specification is to create a platform for global interoperability. It specifically supports PKI enabled communication across borders but the specification could also provide guidance for the establishment of health care PKIs nationally or regionally. The Internet is increasingly used as the vehicle of choice to support the movement of health care data between health care organisations and is the only realistic choice for cross-border communication in this sector. [source: standard document] ISO/TR 21089 Profile Reference Name ISO/TR 21089 ISO/TR 21089: Health informatics – Trusted end-to-end information flows Categories Privacy and Security; Data protection specifications ICS 35.240.80: IT applications in health care technology Abstract ISO/TR 21089:2004 offers a guide to trusted end-to-end information flow for health(care) records and to the key trace points and audit events in the electronic entity/act record life cycle (from point of record origination to each ultimate point of record access/use). It also offers recommendations regarding the trace/audit detail relevant to each. Current Version ISO/TR 21089:2004 Other editions AAL Relevance As AAL scenarios may include personal health records trusted information flows may be essential and in this case this Technical Report should be consulted. Available from http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm? csnumber=35645 V1.0 2013-01-15 Page 453 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description It offers recommendations of best practice for healthcare providers, health record stewards, software developers and vendors, end users and other stakeholders, including patients. [Source: ISO] Directive 95/46/EC Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from Directive 95/46/EC Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data Privacy and Security; Data protection specifications The Data Protection Directive (officially Directive 95/46/EC on the protection of individuals with regard to the processing of personal data and on the free movement of such data) is a European Union directive which regulates the processing of personal data within the European Union. It is an important component of EU privacy and human rights law. On 25 January 2012, the European Commission unveiled a draft European Data Protection Regulation that will supersede the Data Protection Directive. As AAL scenarios often include the processing and storage of personal data this directive (and the superseding Data Protection Regulation) is mandatory. http://eur-lex.europa.eu/LexUriServ/LexUriServ.do? uri=CELEX:31995L0046:en:HTML Description Scope Personal data are defined as “any information relating to an identified or identifiable natural person (“data subject”); an identifiable person is one who can be identified, directly or indirectly, in particular by reference to an identification number or to one or more factors specific to his physical, physiological, mental, economic, cultural or social identity;” (art. 2 a) This definition is meant to be very broad. Data are “personal data” when someone is able to link the information to a person, even if the person holding the data cannot make this link. Some examples of “personal data” are: address, credit card number, bank statements, criminal record, etc. The notion processing means “any operation or set of operations which is performed upon V1.0 2013-01-15 Page 454 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot personal data, whether or not by automatic means, such as collection, recording, organization, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, blocking, erasure or destruction;” (art. 2 b) The responsibility for compliance rests on the shoulders of the “controller”, meaning the natural or artificial person, public authority, agency or any other body which alone or jointly with others determines the purposes and means of the processing of personal data; (art. 2 d) The data protection rules are applicable not only when the controller is established within the EU, but whenever the controller uses equipment situated within the EU in order to process data. (art. 4) Controllers from outside the EU, processing data in the EU, will have to follow data protection regulation. In principle, any online business trading with EU citizens would process some personal data and would be using equipment in the EU to process the data (i.e. the customer's computer). As a consequence, the website operator would have to comply with the European data protection rules. The directive was written before the breakthrough of the Internet, and to date there is little jurisprudence on this subject. The proposed new European Union Data Protection Regulation (a draft for which was unveiled in January 2012) extends the scope of the EU data protection law to all foreign companies processing data of European Union residents. Principles Personal data should not be processed at all, except when certain conditions are met. These conditions fall into three categories: transparency, legitimate purpose and proportionality. Transparency The data subject has the right to be informed when his personal data is being processed. The controller must provide his name and address, the purpose of processing, the recipients of the data and all other information required to ensure the processing is fair. (art. 10 and 11) Data may be processed only under the following circumstances (art. 7): • when the data subject has given his consent • when the processing is necessary for the performance of or the entering into a contract • when processing is necessary for compliance with a legal obligation • when processing is necessary in order to protect the vital interests of the data subject • processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller or in a third party to whom the data are disclosed • processing is necessary for the purposes of the legitimate interests pursued by the controller or by the third party or parties to whom the data are disclosed, except where such interests are overridden by the interests for fundamental rights and freedoms of the data subject. The data subject has the right to access all data processed about him. The data subject even has the right to demand the rectification, deletion or blocking of data V1.0 2013-01-15 Page 455 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot that is incomplete, inaccurate or isn't being processed in compliance with the data protection rules. (art. 12) Legitimate purpose Personal data can only be processed for specified explicit and legitimate purposes and may not be processed further in a way incompatible with those purposes. (art. 6 b) Proportionality Personal data may be processed only insofar as it is adequate, relevant and not excessive in relation to the purposes for which they are collected and/or further processed. The data must be accurate and, where necessary, kept up to date; every reasonable step must be taken to ensure that data which are inaccurate or incomplete, having regard to the purposes for which they were collected or for which they are further processed, are erased or rectified; The data shouldn't be kept in a form which permits identification of data subjects for longer than is necessary for the purposes for which the data were collected or for which they are further processed. Member States shall lay down appropriate safeguards for personal data stored for longer periods for historical, statistical or scientific use. (art. 6) When sensitive personal data (can be: religious beliefs, political opinions, health, sexual orientation, race, membership of past organisations) are being processed, extra restrictions apply. (art. 8) The data subject may object at any time to the processing of personal data for the purpose of direct marketing. (art. 14) A decision which produces legal effects or significantly affects the data subject may not be based solely on automated processing of data. (art. 15) A form of appeal should be provided when automatic decision making processes are used. Supervisory authority and the public register of processing operations Each member state must set up a supervisory authority, an independent body that will monitor the data protection level in that member state, give advice to the government about administrative measures and regulations, and start legal proceedings when data protection regulation has been violated. (art. 28) Individuals may lodge complaints about violations to the supervisory authority or in a court of law. The controller must notify the supervisory authority before he starts to process data. The notification contains at least the following information (art. 19): • the name and address of the controller and of his representative, if any; • the purpose or purposes of the processing; • a description of the category or categories of data subject and of the data or categories of data relating to them; • the recipients or categories of recipient to whom the data might be disclosed; • proposed transfers of data to third countries; • a general description of the measures taken to ensure security of processing. This information is kept in a public register. V1.0 2013-01-15 Page 456 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot [Source: Wikipedia] External links • http://en.wikipedia.org/w/index.php?title=Data_Protection_Directive&oldid=531794057 ISO/IEC 27001:2005 Profile Reference Name Categories ICS Abstract Current Version Other editions AAL Relevance Available from ISO/IEC 27001:2005 ISO/IEC 27001:2005: Information technology – Security techniques – Information security management systems – Requirements Privacy and Security; Data protection specifications 35.040: Character sets and information coding ISO/IEC 27001 formally specifies a management system that is intended to bring information security under explicit management control. Being a formal specification means that it mandates specific requirements. Organizations that claim to have adopted ISO/IEC 27001 can therefore be formally audited and certified compliant with the standard. [Source: Wikipedia] 2005 As AAL service providers processing personal data from their customers ISO/ IEC 27001 provides all necessary requirements for an Information Security Management System and offers a certification which may be useful for confidence building towards customers. http://www.iso.org/iso/catalogue_detail?csnumber=42103 Description An information security management system (ISMS) is a set of policies concerned with information security management or IT related risks. The governing principle behind an ISMS is that an organization should design, implement and maintain a coherent set of policies, processes and systems to manage risks to its information assets, thus ensuring acceptable levels of information security risk. [Source: Wikipedia] ISO/IEC 27001:2005 covers all types of organizations (e.g. commercial enterprises, government agencies, not-for profit organizations). ISO/IEC 27001:2005 specifies the requirements for establishing, implementing, operating, monitoring, reviewing, maintaining and improving a documented Information Security Management System within the context of the organization's overall business risks. It specifies requirements for the implementation of security controls customized to the needs of individual organizations or parts thereof. ISO/IEC 27001:2005 is designed to ensure the selection of adequate and proportionate security controls that protect information assets and give confidence to interested parties. V1.0 2013-01-15 Page 457 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot ISO/IEC 27001:2005 is intended to be suitable for several different types of use, including the following: • use within organizations to formulate security requirements and objectives; • use within organizations as a way to ensure that security risks are cost effectively managed; • use within organizations to ensure compliance with laws and regulations; • use within an organization as a process framework for the implementation and management of controls to ensure that the specific security objectives of an organization are met; • definition of new information security management processes; • identification and clarification of existing information security management processes; • use by the management of organizations to determine the status of information security management activities; • use by the internal and external auditors of organizations to determine the degree of compliance with the policies, directives and standards adopted by an organization; • use by organizations to provide relevant information about information security policies, directives, standards and procedures to trading partners and other organizations with whom they interact for operational or commercial reasons; • implementation of business-enabling information security; • use by organizations to provide relevant information about information security to customers. [Source: ISO] External links • http://en.wikipedia.org/w/index.php?title=ISO/IEC_27001&oldid=531245621 • http://en.wikipedia.org/w/index.php? title=Information_security_management_system&oldid=530873158 (further information on Information security management systems) 14.2. Alarm systems CLC/TR 5045 Profile Reference Name Categories V1.0 CLC/TR 5045 CLC/TR 50456: Alarm systems - Guidelines to achieving compliance with EC directives for equipment of alarm systems Privacy and Security; Alarm systems 2013-01-15 Page 458 of 490 AALIANCE2 ICS Abstract Current Version Other editions AAL Relevance Available from D4.1 Online Repository of Standards - Snapshot 13.320 - Alarm and warning systems This Technical Report gives guidance on the use of standards for alarm systems in the frame of the implementation of the EC directives. 2008 As alarm systems in AAL scenarios also have to meet EC directives this Technical Report should be consulted. http://www.cenelec.eu/dyn/www/f? p=104:110:4405797246295738::::FSP_PROJECT,FSP_LANG_ID:208 60,25 Description The purpose of CLC/TR 50456:2008 is: • to find, among all EC directives, those directives which are directly covering equipment used in alarm systems; • to identify the Essential Requirements (ERs) of the above EC directives which have to be taken into account during the standardization process and which should be known by bodies interested with equipment used in alarm systems; • to register the standards that CLC/TC 79 recommends to use for showing presumption of conformity according to the EC directives and the ERs previously identified. This Technical Report mainly covers equipment used in the following fields of activities: access control, alarm transmission, CCTV, fire detection and fire alarm, intrusion and holdup, social alarm. [Source: CENELEC] CLC/TR 50515 Profile Reference Name CLC/TR 50515 CLC/TR 50515: List of interpretations on published standards on “Alarm Systems” Categories Privacy and Security; Alarm systems ICS 13.310-Protection against crime Abstract CLC/TR 50515 is a list of interpretations to currently published standards in the context of “Alarm Systems” Current Version 2008 Other editions AAL Relevance For AAL scenarios containing alarm systems this technical report might be useful as orientation. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:2256795242264638::::FSP_PROJECT,FSP_LANG_ID:207 62,25 V1.0 2013-01-15 Page 459 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Description CLC/TR 50515:2008 contains information and responses on: • EN 50131-1:1997 “Alarm systems – Intrusion systems – Part 1: General requirements” • EN 50131-6:1997 inconsistencies with EN 50131-1:1997 • EN 50131-6:1997 “Alarm systems – Intrusion systems – Part 6: Power supplies” • CLC/TS 50131-7:2003 “Alarm systems – Intrusion systems – Part 7: Application guidelines” • EN 50131-6:1997 + Corrigendum 1998 “Alarm systems – Intrusion systems – Part 6: Power supplies” • EN 50130-4:1995 “Alarm systems – Part 4: Electromagnetic compatibility – Product family standard: Immunity requirements for components of fire, intruder and social alarm systems” • EN 50136-1-2:1998 “Alarm systems – Alarm transmission systems and equipment – Part 1-2: Requirements for systems using dedicated alarm paths” • CLC/TS 50131-7:2003 “Alarm systems – Intrusion systems – Part 7: Application guidelines” CLC/TR 50531 Profile Reference Name Categories ICS CLC/TR 50531 CLC/TR 50531: Alarm systems - Terms and definitions Privacy and Security; Alarm systems 01.040.13 - Environment and health protection. Safety (Vocabularies) 13.320 - Alarm and warning systemsAbstract This Technical Report contains a compilation of terms (glossary) used in CENELEC TC 79 publications in the area of alarm systems. Current Version 2009 Other editions AAL Relevance For better and correct understanding of alarm systems CLC/TR 50531 should be consulted. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:4460081020653604::::FSP_PROJECT,FSP_LANG_ID:211 35,25 Description In this publication terms from TC 79 standards are classified in six different categories based on their original publication category. These categories are: • Common items • Intrusion and hold-up systems V1.0 2013-01-15 Page 460 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • CCTV surveillance systems • Access control systems • Social alarm systems • Alarm transmission systems [source: standard document] External links • http://www.evs.ee/preview/clc-tr-50531-2009-en.pdf (from EVS, Estonian Centre for Standardisation) CLC/TS 50398 Profile Reference Name CLC/TS 50398 CLC/TS 50398: Alarm systems - Combined and integrated alarm systems Categories Privacy and Security; Alarm systems ICS 13.320 - Alarm and warning systems Abstract CLC/TS 50398 specifies the requirements for alarm systems combined and integrated with other systems which may or may not be alarm systems. Current Version 2009 Other editions AAL Relevance As alarm systems may be part of AAL scenarios and may be integrated into other systems this technical specification should be consulted. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:3173769539612899::::FSP_PROJECT,FSP_LANG_ID:207 28,25 Description This Technical Specification defines requirements, related to integration, in order to complement the individual alarm application standards and to provide clarification where there is conflict. Alarm transmission systems are excluded from the scope of this Technical Specification. [Source: CENELEC] EN 50130 Profile Reference Name V1.0 EN 50130 EN 50130: Alarm systems 2013-01-15 Page 461 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Categories ICS Privacy and Security; Alarm systems 13.320 - Alarm and warning systems 29.020 - Electrical engineering in general Abstract EN 50130 specifies the electromagnetic compatibility and environmental test methods for different kinds of alarm systems (specified by other standards). Current Version see Standard Parts below Other editions AAL Relevance As alarm systems may cover security aspects in AAL scenarios this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 50130-4:2011 EN 50130-5:2011 Title Alarm systems - Part 4: Electromagnetic compatibility - Product family standard: Immunity requirements for components of fire, intruder, hold up, CCTV, access control and social alarm systems Alarm systems - Part 5: Environmental test methods Description EN 50130-4:2011, for immunity requirements, applies to the components of the following alarm systems, intended for use in and around buildings in residential, commercial, light industrial and industrial environments: • access control systems, for security applications; • alarm transmission systems; • CCTV systems, for security applications; • fire detection and fire alarm systems; • hold-up alarm systems; • intruder alarm systems; • social alarm systems; The tests and severities to be used are the same for indoor and outdoor applications of fixed, movable and portable equipment. The levels do not cover extreme cases, which may occur in any location, but with an extremely low probability of occurrence, or in special locations close to powerful emitters (e.g. radar transmitters). Equipment within the scope of this standard should be designed in order to operate satisfactorily in the environmental electromagnetic conditions of residential, commercial, light industrial and industrial environments. This implies particularly that it should be able to operate correctly within the conditions fixed by the electromagnetic compatibility levels for the various disturbances on the low voltage public supply system as defined by EN 61000 2 2. The immunity tests in this standard only concern the most critical disturbance phenomena. For equipment using radio signalling, mains signalling or with connections to the public telephone system, additional requirements, from other standards specific to these signalling media, might V1.0 2013-01-15 Page 462 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot apply. This standard does not specify basic safety requirements, such as protection against electrical shocks, unsafe operation, insulation coordination and related dielectric tests. This standard does not cover EMC emission requirements. These are covered by other appropriate standards. EN 50130-5:2011 specifies environmental test methods to be used for testing the system components of the following alarm systems, intended for use in and around buildings: • intruder alarm systems; • hold-up alarm systems; • social alarm systems; • CCTV systems, for security applications; • access control systems, for security applications; • alarm transmission systems. This European Standard specifies three equipment classes (fixed, movable & portable equipment) and four environmental classes. The environmental classes only include the general service environments envisaged for equipment installed in typical residential, commercial and industrial environments. It may be necessary for the product standard to require additional or different environmental tests or severities where a) there could be specific environmental problems (e.g. some different severities may be required for break glass detectors stuck to glass windows, due to the local extremes of temperature and humidity), b) the test exposure falls within the intended detection phenomenon of the detector (e.g. during a vibration test on a seismic detector). In order to provide reproducible test methods and to avoid the proliferation of technically similar test methods, the test procedures have been chosen, where possible, from internationally accepted standards (e.g. IEC publications). For specific guidance on these tests, reference should be made to the appropriate document, which is indicated in the relevant sub section. For more general guidance and background information on environmental testing, reference should be made to EN 60068 1 and to the EN 60068 3 series. This European Standard does not specify a) the requirements or performance criteria to be applied, which should be specified in the relevant product standard, b) special tests only applicable to a particular device (e.g. the effects of turbulent air draughts on ultrasonic movement detectors), c) basic safety requirements, such as protection against electrical shocks, unsafe operation, insulation coordination and related dielectric tests, d) tests relating to deliberate acts of damage or tampering. [Source: CENELEC] The standard family of alarm system comprises: • EN 50131: Alarm systems - Intrusion and hold-up systems • EN 50132: Alarm systems - CCTV surveillance systems for use in security applications • EN 50133: Alarm systems - Access control systems for use in security applications • EN 50134: Alarm systems - Social alarm systems • EN 50135: Alarm systems - Hold up alarm systems V1.0 2013-01-15 Page 463 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot • EN 50136: Alarm systems - Alarm transmission systems and equipment EN 50486 Profile Reference Name Categories ICS EN 50486 EN 50486: Equipment for use in audio and video door-entry systems Privacy and Security; Alarm systems 13.310 - Protection against crime 97.120 - Automatic controls for household use Abstract This European Standard specifies the requirements for equipment installed in audio and video door-entry systems. Current Version 2008 Other editions AAL Relevance As AAL scenarios may have door-entry systems for security reasons this standard is relevant. Available from http://www.cenelec.eu/dyn/www/f? p=104:110:164465929545649::::FSP_PROJECT,FSP_LANG_ID:1375 6,25 Description This European Standard sets out the following system requirements: • safety and electromagnetic compatibility (EMC) compliance; • audio specifications; • video specifications; • environmental conditions; • vandal resistance. Devices integrated into other systems shall also comply with the requirements of those systems (e.g. telephone system or alarm systems). [Source: CENELEC] EN 50518 Profile Reference Name Categories ICS Abstract Current Version V1.0 EN 50518 EN 50518: Monitoring and alarm receiving centre Privacy and Security; Alarm systems 13.320: Alarm and warning systems EN 50518 specifies monitoring and alarm receiving centre (ARC). see Standard Parts below 2013-01-15 Page 464 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot Other editions AAL Relevance As AAL scenarios may include emergency and information forwarding from the home of elderly people to external users/ organisations this standard is relevant. Available from see Standard Parts below Standard Parts Standard EN 50518-1:2010 EN 50518-2:2010 EN 50518-2/AC:2011 EN 50518-3:2011 Title Monitoring and alarm receiving centre - Part 1: Location and construction requirements Monitoring and alarm receiving centre - Part 2: Technical requirements Monitoring and alarm receiving centre - Part 2: Technical requirements Monitoring and alarm receiving centre - Part 3: Procedures and requirements for operation Description Part 1 of EN 50518 specifies the minimum requirements for the design, construction, and functioning equipment for premises where the monitoring, receiving and processing of (alarm) signals generated by alarm systems takes place as an integrated part of the total safety and security process. The requirements apply for applications in a remote configuration where multiple systems report to a single or multiple Alarm Receiving Centre(s) (ARC) as well as to a single site facility aimed for the monitoring and processing of alarms generated by one or more alarm systems installed within the perimeter of that particular site. part 2 of EN 50518 specifies the technical requirements of an ARC. This also includes functional performance criteria and verification of performance. A newer version (prEN 50518-2) consolidating EN 50518-2:2010 and EN 50518-2/AC:2011 is under development. Part 3 of EN 50518 specifies the minimum procedures and requirements for the operation of an ARC. [Source: CENELEC] V1.0 2013-01-15 Page 465 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot 15. Ambient Intelligence FIPA XC00080B Profile Reference Name Categories FIPA XC00080B FIPA XC00080B: FIPA Personal Travel Assistance Specification Agent-based Systems; Software Infrastructure for AAL; ServiceOriented Architectures; FIPA ICS 03.220.01 - Transport in general 33.030 - Telecommunication services. Applications 35.080 - Software 35.110 - Networking 35.240.60 - IT applications in transport and trade Abstract This specification for the travel industry provides an overview of the current industry in regard to agents, a reference architecture for a multiagent system in this industry and several examples: agent management details (e.g. domains and naming), agent communication details (e.g. content ontologies and communication protocols), agent/software integration (e.g. access to databases and mobile users). Current Version 2001/08/10 Other editions AAL Relevance FIPA specifications represent a collection of standards which are intended to promote the interoperation of heterogeneous agents and the services that they can represent, so they are useful for large I+D projects. Available from http://www.fipa.org/specs/fipa00080/XC00080B.html Description This document extends the FIPA standard by providing an application specification for the travel industry. This specification provides: • An overview of the current industry in regard to agents, • A reference architecture for a multi-agent system in this industry, • Examples of the agent management details such as domains and naming, • Examples of agent communication communication protocols, and, details such as content ontologies and • Examples of agent/software integration such as for accessing databases and mobile users This specification is not complete, but the included examples help to illustrate the use of V1.0 2013-01-15 Page 466 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot FIPA standard and thereby quicken the development and deployment of real systems. Some points of this architecture have been selected as normative in order to begin interoperability tests of field trials. These requirements are noted throughout the specification as they arise. In summary, this specification servers three purposes: • To continue testing the FIPA technical specifications. The context of a real application serves to determine the strengths and weaknesses of the specifications, • To demonstrate the real business value and requirement of a standard specification for such a large, distributed, multi-vendor application, and, • To define initial application architecture, object design and use case analysis for actual development of field trials. [Source: FIPA, accessed 2012-10-10] External links • FIPA Personal Travel Assistance Specification FIPA SC00008I Profile Reference Name Categories FIPA SC00008I FIPA SC00008I: FIPA SL Content Language Specification Agent-based Systems; Software Infrastructure for AAL; ServiceOriented Architectures; FIPA ICS 35.060 - Languages used in information technology Abstract This specification defines a concrete syntax for the FIPA Semantic Language (SL) content language, suggested as a candidate for use in conjunction with the FIPA Agent Communication Language Current Version 2002/12/03 Other editions AAL Relevance FIPA specifications represent a collection of standards which are intended to promote the interoperation of heterogeneous agents and the services that they can represent, so they are useful for large I+D projects. Available from http://www.fipa.org/specs/fipa00008/SC00008I.html Description This specification defines a concrete syntax for the FIPA Semantic Language (SL) content language. This syntax and its associated semantics are suggested as a candidate content language for use in conjunction with the FIPA Agent Communication Language. In particular, the syntax is defined to be a sub-grammar of the very general s-expression syntax. [Source: FIPA, accessed 2012-10-10] V1.0 2013-01-15 Page 467 of 490 AALIANCE2 D4.1 Online Repository of Standards - Snapshot External links • FIPA SL Content Language Specification FIPA XC00011B Profile Reference Name Categories FIPA XC00011B FIPA XC00011B: FIPA RDF Content Language Specification Agent-based Systems; Software Infrastructure for AAL; ServiceOriented Architectures; FIPA ICS 35.060 - Languages used in information technology Abstract This specification desc