CLC TS 50560-2014 Interoperability framework requirement specification.pdf

《CLC TS 50560-2014 Interoperability framework requirement specification.pdf》由会员分享，可在线阅读，更多相关《CLC TS 50560-2014 Interoperability framework requirement specification.pdf（90页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards PublicationInteroperability frameworkrequirement specificationPD CLC/TS 50560:2014National forewordThis Published Document is the UK implementation of CLC/TS 50560:2014. The UK participation in its preparation was entrusted by TechnicalCommittee IST/6, Data communications, to Panel IST

2、/6/-/12, HomeElectronic Systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Institutio

3、n 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 85910 6ICS 35.240.99; 97.120Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 30 April 2015.Amendments

4、/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CLC/TS 50560:2014TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CLC/TS 50560 October 2014 ICS 35.240.99; 97.120 Supersedes CWA 50560:2010 English Version Interoperability framework requirement specifi

5、cation Spcification dexigences cadre dinteroprabilit Rahmenspezifikation fr Interoperabilittsanforderungen (IFRS) This Technical Specification was approved by CENELEC on 2014-08-11. CENELEC members are required to announce the existence of this TS in the same way as for an EN and to make the TS avai

6、lable promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Repu

7、blic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. European Committee for Electrotechnical Standardizati

8、on Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members. Ref. No. CLC/TS 50560:2014

9、 E PD CLC/TS 50560:2014CLC/TS 50560:2014 2 Contents Contents 1 Foreword 6 Introduction. 7 1 Scope . 9 2 Normative References 9 3 Terms, definitions and Abbreviations 10 3.1 Security Definitions . 10 3.2 Process Definitions . 12 3.3 Interoperability 14 3.4 Abbreviations 14 4 The Interoperability Fram

10、ework 17 4.1 The Function Steps . 17 4.1.1 General . 17 4.1.2 Discovery 17 4.1.3 Configuration . 17 4.1.4 Operation 17 4.1.5 Management 18 4.2 The Levels 18 5 Conformance clauses . 19 5.1 Interoperability Conformance Requirements 19 5.1.1 General . 19 5.1.2 Identifier 19 5.1.3 Object Description . 1

11、9 5.1.4 Object Discovery . 20 5.1.5 Object Configuration 20 5.1.6 Object Operation . 20 5.1.7 Object Management 20 5.1.8 Object Access and Safety Requirements . 20 5.2 Conformance sub-clauses . 20 5.2.1 Object Identifier Description Requirements 20 5.2.2 Object Functional Description Requirements .

12、21 5.2.3 Discovery Process Requirements 22 5.2.4 Configuration Process Requirements . 23 5.2.5 Operation Requirements 23 5.2.6 Management Requirements . 23 5.2.7 Object Security, Safety and Priority and Access Requirements 24 Annex A (informative) Steps of discovery, configuration, operation and man

13、agement 25 A.1 Methodology . 25 A.1.1 Objectives . 25 A.1.2 Assumptions 25 A.2 Approach 26 A.3 The Function Steps 26 A.3.1 General . 26 A.3.2 Discovery 26 A.3.3 Configuration . 29 PD CLC/TS 50560:2014 3 CLC/TS 50560:2014 A.3.4 Operation 30 A.3.5 Management . 30 A.4 The Levels . 30 A.4.1 Level 0 30 A

14、.4.2 Level 1 31 A.4.3 Level 2 32 A.4.4 Level 3 33 A.4.5 Level 4 34 A.4.6 Level 5 37 A.4.7 Level 6 38 A.4.8 Combinations of Different Levels in the Same Installation . 40 A.5 Use Cases 41 A.5.1 Methodology 41 A.5.1.1 General . 41 A.5.1.2 Describe use-case . 41 A.5.2 Scenarios to Illustrate Interopera

15、bility Levels 42 A.5.2.1 General . 42 A.5.2.2 Level 0 43 A.5.2.3 Level 1 43 A.5.2.4 Level 2 43 A.5.2.5 Level 3 44 A.5.2.6 Level 4 44 A.5.2.7 Level 5 44 A.5.2.8 Level 6 45 A.6 IFRS Methodology 45 A.6.1 General . 45 A.6.2 Physical Layer, Pathways and Media (PHY) 45 A.6.3 Data Link Control (DLC) 46 A.6

16、.4 Network Layer and Routing (NWK) 47 A.6.5 Transport and Session (TRS) 48 A.6.6 Presentation and Application (APP) . 49 A.6.7 IFRS Issues A Summary . 49 A.6.8 Working Assumptions 50 A.6.9 Rationale for the Function Steps and Associated Processes 51 A.6.9.1 General . 51 A.6.9.2 Architectural Issues

17、. 52 A.7 Security, Safety, Access and Priority Considerations 52 A.7.1 Introduction to Security Considerations . 52 A.7.2 References and Standards 55 Annex B (normative) Interoperability Implementation Conformance Statement . 56 B.1 Scope . 56 B.2 References . 56 B.3 Definitions and abbreviations 56

18、 PD CLC/TS 50560:2014CLC/TS 50560:2014 4 B.3.1 Definitions . 56 B.3.1.1 General Definitions 56 B.3.1.2 Security Definitions . 60 B.3.1.3 Interaction Model Definitions . 62 B.3.1.4 Process Definition . 66 B.3.1.5 Interoperability 67 B.3.1.6 Other Definitions . 68 B.4 Requirements for Conformance to t

19、his IICS 69 B.4.1 General . 69 B.4.2 Object Identifier Description Requirements 69 B.4.3 Object Functional Description Requirements . 69 B.4.3.1 General . 69 B.4.3.2 Object Classification 69 B.4.3.3 Object Discovery Interface 70 B.4.3.4 Object Configuration Interface . 70 B.4.3.5 Object Management I

20、nterface 70 B.4.3.6 Object Functional Interface 70 B.4.4 Discovery Requirements 70 B.4.4.1 General . 70 B.4.4.2 Object Descriptions: Self and Objects to be Discovered 70 B.4.4.3 Communication Mode 71 B.4.4.4 Discovery Process . 71 B.4.4.5 Discovery Scope . 71 B.4.4.6 Security and Privacy 71 B.4.5 Co

21、nfiguration Requirements 71 B.4.5.1 Bindings 71 B.4.5.2 Communication Mode 71 B.4.5.3 Configuration Process . 71 B.4.5.4 Security and Privacy 72 B.4.6 Operation Requirements 72 B.4.6.1 Application Operation 72 B.4.6.2 Security and Privacy 72 B.4.7 Management Requirements . 72 B.4.7.1 Communication M

22、ode 72 B.4.7.2 Management Process 72 B.4.7.3 Security and Privacy 73 B.5 Instructions for Completion of the IICS . 73 B.5.1 General . 73 B.5.2 Key to the Table Entries 73 B.6 Global Statement of IICS Conformance 74 B.7 Specific Statements of IICS Conformance 74 B.7.1 General . 74 B.7.2 Object Catalo

23、gue. 74 PD CLC/TS 50560:2014 5 CLC/TS 50560:2014 B.7.3 Operation Catalogue . 75 B.7.4 Object and Operation Interoperability Catalogue . 76 B.7.5 Upper Layer PICS (APP) . 77 B.7.5.1 General . 77 B.7.5.2 Additional Requirements for Gateways at APP Layer . 77 B.7.6 Network Layer and Routing PICS (NWK)

24、. 78 B.7.6.1 General . 78 B.7.6.2 Additional Requirements for Gateways at NWK Layer 79 B.7.7 Data Link Control and MAC PICS (DLC/MAC) . 80 B.7.7.1 General . 80 B.7.7.2 Additional Requirements for Gateways at DLC/MAC Layer 81 B.7.8 Media and PHY PICS (PHY) 82 Bibliography 83 PD CLC/TS 50560:2014CLC/T

25、S 50560:2014 6 Foreword This document (CLC/TS 50560:2014) has been prepared by CLC/TC 205, “Home and Building Electronic Systems (HBES)“. This document supersedes CWA 50560:2010. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN

26、ELEC and/or CEN shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate given to CENELEC by the European Commission and the European Free Trade Association. PD CLC/TS 50560:2014 7 CLC/TS 50560:2014 Introduction The objective of thi

27、s Technical Specification, the Interoperability Framework Requirements Specification (IFRS), is to specify a methodology that will give consumers the confidence to buy products from different companies both now and in the future, knowing that they will operate together. Achieving this requires sever

28、al phases of standardisation to ensure integration from the physical connectors to the way systems function. There are three phases of integration: Co-existence - where different systems can operate in the same environment without hindering each others operation; Interworking - where different techn

29、ologies are connected together to transfer data end-to-end. It is primarily a technical solution encompassing connectors, protocols, bridges, etc. ; Interoperability - where different application functions are able use the shared information in a consistent way. This requires interworking as a build

30、ing block as well as coexistence, and adds business rules, processes, and security provisions that enable applications to be joined together. Figure 1 The Interoperability Framework Requirements Specification, IFRS, addresses the third of these terms. It provides a common set of rules to enable prod

31、ucts that use different standards to interoperate when they are present in an installation. This TS covers four high level functional activities: discovery, configuration, operations and system management. It puts forward a common set of requirements that if complied with, and if coexistence and int

32、erworking are assured, will enable interoperability. It does not address co-existence or interworking on the basis that this is achieved by technology standards. PD CLC/TS 50560:2014CLC/TS 50560:2014 8 Interoperability is provided by alliances of commercial businesses (and there are several such all

33、iances), but to ensure interoperability customers are limited to purchasing products from members of the alliance. This TS acknowledges the work and the value of such alliances but specifically addresses the ability for customers to purchase products and services from competing alliances and still a

34、chieve interoperability. In doing so it expects to increase the market for those alliances that conform to the IFRS as customers will purchase their products with greater freedom of choice and confidence that they will work. PD CLC/TS 50560:2014 9 CLC/TS 50560:2014 1 Scope This Technical Specificati

35、on contains a specification of an Interoperability Requirements Framework, specifying seven levels of interoperability, based on four groups of interoperability steps specified by five types of interaction, plus a methodology based on conformance clauses for satisfying requirements related to the cl

36、aimed level of interoperability of devices installed in a Home and Building Electronic System (HBES, HES). It is applicable to installations of a single type of HBES, or that interconnect two or more dissimilar HBESs. Within a HBES of a single type any of its capabilities for service, applications a

37、nd connectivity topology can be used. Interconnection technologies used to interconnect dissimilar HBES are similarly unconstrained. For applicable installations, the scope of its provisions applies to: the connection of devices to the various communications services to enable them to communicate en

38、d-to-end across internetworked media; the processes of discovery by which devices find out about each other and configuration to associate them with each other; and the generic aspects of application operation; and management. This Technical Specification is not applicable to the interoperability re

39、quired between devices to implement specific applications, such as heating or lighting control, energy management, or entertainment. The interoperability requirements defined in this Technical Specification are necessary for such application interoperability but not sufficient. This Technical Specif

40、ication does not define how measurements are made; nor the algorithms that receive, process and respond to them; nor the interaction between users, service providers, and the HBES application(s). This is the responsibility of experts and organisations that specialise in particular application domain

41、s. 2 Normative References The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any am

42、endments) applies. ETSI/TS 101 761-2, Broadband Radio Access Networks (BRAN);HIPERLAN Type 2; Data Link Control (DLC) Layer;Part 2: Radio Link Control (RLC) sublayer ETSI/TS 300 406:1995, Methods for testing and Specification (MTS); Protocol and profile, conformance testing specifications; Standardi

43、zation methodology. ISO/IEC 9646-1, Information technology Open Systems Interconnection Conformance testing methodology and framework Part 1: General concepts. ISO/IEC 9646-7, Information technology Open Systems Interconnection Conformance testing methodology and framework Part 7: Implementation Con

44、formance Statements ITU X.800, Data communication networks: Open systems interconnection (OSI); Security structure and applications - Security architecture for open systems interconnection for CITT applications PD CLC/TS 50560:2014CLC/TS 50560:2014 10 3 Terms, definitions and Abbreviations For the p

45、urposes of this document, the following terms and definitions apply. 3.1 Security Definitions 3.1.1 access control the prevention of unauthorized use of a resource, including the prevention of use of a resource in an unauthorized manner SOURCE: ITU X.800 Note 1 to entry : Access Control becomes impo

46、rtant when more than one entity or system is required to access a resource. In such cases and especially where safety is an issue, there may need to be levels of Access Rights depending on the priority of the accessing application and the nature of the resource. Permission and ability to use an obje

47、ct for a specified purpose requesting information from it, changing values of variables in it or modifying its state. Note 2 to entry: Where more than one service or Application requires access to an Object for one or more specific purposes, then levels of access shall be defined, including the defi

48、nition of the primary owner of the Access Rights (possibly the owner of the Object) EXAMPLE: Read access to a shared variable; permission to turn on, or off, i.e. execute certain operations. 3.1.2 access rights permission and ability to use an Object for a specified purpose requesting information fr

49、om it, changing values of variables in it or modifying its state Note 1 to entry: Where more than one service or application requires access to an Object for one or more specific purposes, then levels of access shall be defined, including the definition of the primary owner of the access rights (possibly the owner of the Object) EXAMPLE: read access to a shared variable; permission to turn on, or off, i.e. execute certain operations. 3.1.3 authentication the validation of a claimed identity Note 1 to ent