Bsi bs en 50090 3 2 2004

www bzfxw com BRITISH STANDARD BS EN 50090 3 2 2004 Home and Building Electronic Systems (HBES) — Part 3 2 Aspects of application — User process for HBES Class 1 The European Standard EN 50090 3 2 200[.]

Home and Building Electronic Systems (HBES) —

Part 3-2: Aspects of application — User process for HBES Class 1

The European Standard EN 50090-3-2:2004 has the status of a British Standard

ICS 97.120

12&23<,1*:,7+287%6,3(50,66,21(;&(37$63(50,77('%<&23<5,*+7/$:

This British Standard was

published under the authority

of the Standards Policy and

Strategy Committee on

31 March 2004

© BSI 31 March 2004

National foreword

This British Standard is the official English language version of

EN 50090-3-2:2004 It supersedes BS EN 50090-3-2:1996 which is withdrawn

The UK participation in its preparation was entrusted to Technical Committee IST/6, Data communications, which has the responsibility to:

A list of organizations represented on this committee can be obtained on request to its secretary

Cross-references

The British Standards which implement international or European

publications referred to in this document may be found in the BSI Catalogue

under the section entitled “International Standards Correspondence Index”, or

by using the “Search” facility of the BSI Electronic Catalogue or of British

Standards Online

This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application

Compliance with a British Standard does not of itself confer immunity from legal obligations.

— aid enquirers to understand the text;

— present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the

UK interests informed;

— monitor related international and European developments and promulgate them in the UK

Summary of pages

This document comprises a front cover, an inside front cover, the EN title page, pages 2 to 15 and a back cover

The BSI copyright notice displayed in this document indicates when the document was last issued

Amendments issued since publication

NORME EUROPÉENNE

CENELEC

European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung

Central Secretariat: rue de Stassart 35, B - 1050 Brussels

© 2004 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members

Ref No EN 50090-3-2:2004 E

ICS 97.120 Supersedes EN 50090-3-2:1995

English version

Home and Building Electronic Systems (HBES)

Part 3-2: Aspects of application - User process for HBES Class 1

Systèmes électroniques pour les foyers

domestiques et les bâtiments (HBES)

Partie 3-2: Aspects de l'application -

Processus utilisateur HBES Classe 1

Elektrische Systemtechnik für Heim

und Gebäude (ESHG) Teil 3-2: Anwendungsaspekte - Anwendungsprozess ESHG Klasse 1

This European Standard was approved by CENELEC on 2003-12-02 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration

Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member

This European Standard exists in one official version (English) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official version

CENELEC members are the national electrotechnical committees of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom

Contents

Foreword 3

Introduction 4

1 Scope 4

2 Normative references 5

3 Terms, definitions and abbreviations 5

3.1 Terms and definitions 5

3.2 Abbreviations 5

4 Object models 5

5 Group object server 6

5.1 Overview 6

5.2 General data structure group objects 6

5.3 Group object value transfers 9

6 Interface object server 11

6.1 Overview 11

6.2 Address levels for interface objects 13

6.3 Interworking requirements for interface objects 13

6.4 System interface objects (management objects) 13

6.5 Application interface objects 13

Figure 1 – User process model 6

Figure 2 – Data structure of group objects 7

Figure 3 – Reading a group object value 10

Figure 4 – Receiving a request to read the group object value 10

Figure 5 – Writing a group object value 11

Figure 6 – Receiving an update of the group object value 11

Figure 7 – Structure of interface objects 12

Figure 8 – Message flow for the A_PropertyValue_Read-service 14

Figure 9 - Message flow for the A_PropertyValue_Write-service 14

Figure 10 - Message flow for the A_PropertyDescription_Read-service 15

Table 1 – Group object types 7

Foreword

This European Standard was prepared by the Technical Committee CENELEC TC 205, Home and

Building Electronic Systems (HBES), with the help of CENELEC co-operation partner Konnex Association

(formerly EHBESA)

The text of the draft was submitted to the Unique Acceptance Procedure and was approved by CENELEC

as EN 50090-3-2 on 2003-12-02

This European Standard supersedes EN 50090-3-2:1995

CENELEC takes no position concerning the evidence, validity and scope of patent rights

Konnex Association as Cooperating Partner to CENELEC confirms that to the extent that the standard

contains patents and like rights, the Konnex Association's members are willing to negotiate licenses

thereof with applicants throughout the world on fair, reasonable and non-discriminatory terms and

conditions

Konnex Association Tel.: + 32 2 775 85 90 Neerveldstraat, 105 Fax.: + 32 2 675 50 28 Twin House e-mail: info@konnex.org

B - 1200 Brussels www.konnex.org

Attention is drawn to the possibility that some of the elements of this standard may be the subject of

patent rights other than those identified above CENELEC shall not be held responsible for identifying any

or all such patent rights

The following dates were fixed:

– latest date by which the EN has to be implemented

at national level by publication of an identical national standard or by endorsement (dop) 2004-12-01

– latest date by which the national standards conflicting

with the EN have to be withdrawn (dow) 2006-12-01

EN 50090-3-2 is part of the EN 50090 series of European Standards, which will comprise the following

parts:

Part 1: Standardization structure

Part 2: System overview

Part 3: Aspects of application

Part 4: Media independent layers

Part 5: Media and media dependent layers

Part 6: Interfaces

Part 7: System management

Part 8: Conformity assessment of products

Part 9: Installation requirements

Introduction

The application interface layer is the layer between the application layer and the application It contains

the communication relevant tasks of the application It eases the communication task of the application by

offering a communication interface that abstracts from many application layer details

This European Standard allows single-processor and dual-processor device designs A dual processor

device uses additional services to communicate via a serial External Message Interface with the external

user application running in the second processor

The following clauses specify the client and server functionality and the communication interface of the

internal user application located in the Bus Access Unit (BAU)

The application interface layer contains the following objects and the access routines to them:

– group objects: can be accessed via Transport layer Service Access Points (TSAPs) on

multicast communication services, see the corresponding clause in EN 50090-4-2 Group objects may also be references to interface objects;

– interface objects: can be accessed via application services on point-to-point

connection-less and point-to-point connection-oriented communication modes The interface objects are divided to system interface objects and application interface objects

– System interface objects are at this time:

− the device object;

− the group address table object;

− the association table object, and

− the application object

System interface objects are relevant for network management as specified in

EN 50090-7-1

– Application interface objects are objects defined in the user application They may be defined by the internal or external user application, based on interface object structure rules defined in this document Application interface objects may also be referenced by a group object reference

The following clause specifies the data structures of each of the application interface layer objects

Additionally they define by which application services these objects are accessible Both the object client

and object server functionality may be implemented by the external or the internal application interface

layer It is recommended to locate the group communication objects, the interface objects and the

resource objects in the internal application interface layer

1 Scope

This part of EN 50090 specifies the structure and functioning of servers for the objects which form the

interface between the application layer and the application and management

2 Normative references

The following referenced documents are indispensable for the application of this document For dated

references, only the edition cited applies For undated references, the latest edition of the referenced

document (including any amendments) applies

EN 50090-1 1) Home and Building Electronic Systems (HBES) –

Part 1: Standardization structure

EN 50090-4-1:2004 Home and Building Electronic Systems (HBES) –

Part 4-1: Media independent layers – Application layer for HBES Class 1

EN 50090-4-2:2004 Home and Building Electronic Systems (HBES) –

Part 4-2: Media independent layers – Transport layer, network layer and general parts of data link layer for HBES Class 1

EN 50090-7-1:2004 Home and Building Electronic Systems (HBES) –

Part 7-1: System management – Management procedures

3 Terms, definitions and abbreviations

3.1 Terms and definitions

For the purposes of this part the terms and definitions given in EN 50090-1 and EN 50090-4-1 apply

3.2 Abbreviations

ASAP Application Layer Service Access Point

BAU Bus Access Unit

EMI External Message Interface

HBES Class 1 refers to simple control and command

HBES Class 2 refers to Class 1 plus simple voice and stable picture transmission

HBES Class 3 refers to Class 2 plus complex video transfers

TSAP Transport layer Service Access Point

4 Object models

This European Standard specifies two different kinds of objects that shall be supported for operational

exchanges:

a) group objects

group objects shall be used to support the shared variable model;

b) interface objects

interface objects shall be used to support the client/server model and, if they are referenced by group objects, also the shared variable model of the group objects

An application may use each kind of objects at any time

———————

1)

At draft stage

Application Interface Layer

A-Group Object-Services

Group-Objects

Application Interface Objects

A- Interface Object-Services

Services

Group-Object-Server

Interface- Object-Server Reference

Application

Application Layer

Figure 1 – User process model

5 Group object server

5.1 Overview

Group objects can be distributed to a number of devices Each device may be transmitter and receiver for

group object values More than one group object can exist in an end device and a group object in a

device may be assigned to one or more group addresses Group objects of an end device may belong to

the same or to different groups Each group shall have a network wide unique group address The group

address shall be mapped to a local group-index (TSAP) by the transport layer; the group-index shall be

unique for the communication services of the device The application layer shall map the group-index by

the association table to the group reference ID (Application Layer Service Access Point, ASAP) that shall

be used to address the group objects

5.2 General data structure group objects

5.2.1 Structure

In the sense of the previous clause a group object shall consist of three parts:

a) the group object description;

b) the object-value;

c) the communication-flags

group object description communication

flags

group object value object

type

transmission priority

configuration flags

Figure 2 – Data structure of group objects

5.2.2 Group object description

5.2.2.1 Object type

The following value-types shall be possible:

Table 1 – Group object types

Value Length / Type Value-size

Unsigned Integer (1) 1 bit Unsigned Integer (2) 2 bit Unsigned Integer (3) 3 bit Unsigned Integer (4) 4 bit Unsigned Integer (5) 5 bit Unsigned Integer (6) 6 bit Unsigned Integer (7) 7 bit Unsigned Integer (8) 1 octet Unsigned Integer (16) 2 octets Octet (3) 3 octets Octet (4) 4 octets Octet (6) 6 octets Octet (8) 8 octets Octet (10) 10 octets Octet (14) 14 octets Interface object reference 4 to 14 octets

Only group objects of the same type may be linked to one group and for interface objects references also

the interface object type with the same instance number shall be the same

5.2.2.2 Transmission priority

The priority can only be “urgent”, “normal” or “low” The transmission priority “system” shall not be allowed

for communication using group objects

5.2.2.3 Configuration flags

The configuration flags shall include static configuration of the group object:

a) read enable;

b) write enable;

c) transmit enable;

d) update enable;

e) communication enable

If the “read enable” flag is set, the user process shall allow reading the group object value; the user

process shall thus react to an A_GroupValue_Read.ind service from the application layer as specified in

EN 50090-4-1 If the “read enable” flag is cleared, the user process shall neglect this service for this

group object

If the “write enable” flag is set, the user process shall allow setting the group object value; the user

process shall thus react to an A_GroupValue_Write.ind service from the application layer as specified in

EN 50090-4-1 If the “write enable” flag is cleared, the user process shall neglect this service for this

group object

If the “transmit enable” flag is set, the user process shall allow transmitting the group object value; on

request by the user application the user process shall thus pass an A_GroupValue_Write.req service to

the application layer as specified in EN 50090-4-1 If the “transmit enable” flag is cleared, the user

process shall neglect this request from the user application

If the “update enable” flag is set, the user process shall update the communication object value on

reception of an A_GroupValue_Read.con to that group object by setting the group object value to the

contained value If the “update enable” flag is cleared, the user process shall not react on

A_GroupValye_Read.res-services to that group object

The “communication enable” flag shall take priority over the “read enable”, “write enable”, “transmit

enable” and “update enable” flags If the “communication enable flag” is set, these flags shall be

evaluated as specified If the “communication enable flag” is cleared, these configuration flags shall not

be evaluated; instead, all services and requests shall be neglected

5.2.3 Communication flags

The communication flags show the state of a group communication object The following states are

possible:

a) update;

b) read_request;

c) write_request;

d) transmitting;

e) ok, error

The “update” flag shall be set by the user process to indicate to the user application that it has updated

the group object value The “update” flag shall be cleared by the user application

The “read-request” flag shall be set by the user application to indicate that it wants to obtain an update of

its group object value As a reaction, the user process shall generate an A_GroupValue_Read.req as

specified in EN 50090-4-1 and clear the “read request” flag if successful

The “write-request” shall be set by the user application to indicate that it wants to transmit the group