ITU-T F 744-2009 Service description and requirements for ubiquitous sensor network middleware (Study Group 16)《泛在传感器网络中间件的业务描述和要求 16号研究组》.pdf

《ITU-T F 744-2009 Service description and requirements for ubiquitous sensor network middleware (Study Group 16)《泛在传感器网络中间件的业务描述和要求 16号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T F 744-2009 Service description and requirements for ubiquitous sensor network middleware (Study Group 16)《泛在传感器网络中间件的业务描述和要求 16号研究组》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T F.744TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2009) SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES Audiovisual services Service description and requirements for ubiquitous sensor network middleware Recommendation ITU-T F.744 ITU-T F-SERIES

2、RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES TELEGRAPH SERVICE Operating methods for the international public telegram service F.1F.19 The gentex network F.20F.29 Message switching F.30F.39 The international telemessage service F.40F.58 The international telex service F.59F.89 Statistics

3、 and publications on international telegraph services F.90F.99 Scheduled and leased communication services F.100F.104 Phototelegraph service F.105F.109 MOBILE SERVICE Mobile services and multidestination satellite services F.110F.159 TELEMATIC SERVICES Public facsimile service F.160F.199 Teletex ser

4、vice F.200F.299 Videotex service F.300F.349 General provisions for telematic services F.350F.399 MESSAGE HANDLING SERVICES F.400F.499 DIRECTORY SERVICES F.500F.549 DOCUMENT COMMUNICATION Document communication F.550F.579 Programming communication interfaces F.580F.599 DATA TRANSMISSION SERVICES F.60

5、0F.699 AUDIOVISUAL SERVICES F.700F.799ISDN SERVICES F.800F.849 UNIVERSAL PERSONAL TELECOMMUNICATION F.850F.899 HUMAN FACTORS F.900F.999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T F.744 (12/2009) i Recommendation ITU-T F.744 Service description and requirements

6、 for ubiquitous sensor network middleware Summary The purpose of Recommendation ITU-T F.744 is to describe ubiquitous sensor network (USN) services and requirements for USN middleware. To provide various USN services easily and effectively, it is desirable to define an intermediate entity such as US

7、N middleware for providing functions commonly required by various USN services. This Recommendation covers USN service description, USN middleware description, use cases of USN services using USN middleware, the functional model for USN middleware and requirements for USN middleware. History Edition

8、 Recommendation Approval Study Group 1.0 ITU-T F.744 2009-12-14 16 Keywords Functional model, requirement, sensor network, USN middleware, USN services. ii Rec. ITU-T F.744 (12/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of tel

9、ecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telec

10、ommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the p

11、rocedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a t

12、elecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of

13、 these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS

14、 ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU m

15、embers or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may

16、 not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T F.7

17、44 (12/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Description of USN services, USN middleware and use cases 2 6.1 Description of USN services 2 6.2 Descr

18、iption of USN middleware 3 6.3 Use cases of USN services . 3 7 Functional model of USN middleware . 8 7.1 Open application interface processing 9 7.2 Basic functions . 9 7.3 Advanced functions 9 7.4 Sensor network common interface processing . 10 7.5 Security service 10 8 Requirements for USN middle

19、ware 10 8.1 Interface requirements 10 8.2 Functional requirements . 10 8.3 Security requirements . 11 Bibliography. 12 Rec. ITU-T F.744 (12/2009) 1 Recommendation ITU-T F.744 Service description and requirements for ubiquitous sensor network middleware 1 Scope This Recommendation describes USN servi

20、ces and requirements for ubiquitous sensor network (USN) middleware. This Recommendation covers: description of the USN services; description of the USN middleware; use cases of USN services that use USN middleware; functional model of USN middleware; requirements for USN middleware to support funct

21、ions commonly required by USN services. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and

22、 other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. Th

23、e reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2201 Recommendation ITU-T Y.2201 (2009), Requirements and capabilities for ITU-T NGN. ITU-T Y.2221 Recommendation ITU-T Y.2221 (2010), Requirements for support of

24、 ubiquitous sensor network (USN) applications and services in the NGN environment. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 context awareness ITU-T Y.2201: Context awareness is a capability to determine or influence a next action

25、 in telecommunication or process by referring to the status of relevant entities, which form a coherent environment as a context. NOTE This Recommendation also uses context-aware with same meaning of context awareness. 3.1.2 sensor ITU-T Y.2221: An electronic device that senses a physical condition

26、or chemical compound and delivers an electronic signal proportional to the observed characteristic. 3.1.3 sensor network ITU-T Y.2221: A network comprised of inter-connected sensor nodes exchanging sensed data by wired or wireless communication. 3.1.4 sensor node ITU-T Y.2221: A device consisting of

27、 sensor(s) and optional actuator(s) with capabilities of sensed data processing and networking. 3.1.5 ubiquitous sensor network (USN) ITU-T Y.2221: A conceptual network built over existing physical networks which make use of sensed data and provide knowledge services to 2 Rec. ITU-T F.744 (12/2009)

28、anyone, anywhere and at anytime, and where the information is generated by using context awareness. 3.1.6 USN middleware ITU-T Y.2221: A set of logical functions to support USN applications and services. NOTE The functionalities of USN middleware include sensor network management and connectivity, e

29、vent processing, sensor data mining, etc. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 open application interface: An interface used by USN applications to access USN middleware. 3.2.2 processed data: Data that are processed from raw sensed data by

30、sensor network or USN middleware. 3.2.3 sensed data: Data sensed by a sensor that is attached to a specific sensor node. 3.2.4 sensor network common interface: An interface used between USN middleware and a sensor network/radio frequency identification (RFID) reader. 3.2.5 sensor network metadata: I

31、nformation about a sensor network, such as description of the sensor network, sensor node identifier, supported sensor type, the number of attached sensors for each sensor node, and the number of sensor nodes connected to the specific sensor network, etc. 3.2.6 sensor network metadata directory serv

32、ice: A directory service that provides sensor network metadata. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ECG Electrocardiogram RFID Radio Frequency Identification USN Ubiquitous Sensor Network WSN Wireless Sensor Network 5 Conventions None. 6 De

33、scription of USN services, USN middleware and use cases 6.1 Description of USN services USN is a conceptual network built over existing physical networks that make use of sensed data and provide knowledge services to anyone, anywhere and at anytime, and where the information is generated by using co

34、ntext awareness. USN utilizes wireline sensor networks and/or wireless sensor networks (WSNs). See ITU-T Y.2221. USN applications and services can be used in many civilian application areas such as, industrial automation, home automation, agricultural monitoring, healthcare, environment, pollution a

35、nd disaster surveillance; in homeland security, military field, etc., see ITU-T Y.2221. Rec. ITU-T F.744 (12/2009) 3 A USN service is a type of service that uses various sensors and/or actuators. In the USN services framework, communications take place between USN applications and sensor networks di

36、rectly or via some intermediate entity. Some USN applications and services use basic data processing to obtain the necessary data and others may use advanced data processing such as data mining, context-aware processing, and event processing. In addition, authentication of sensor network and confide

37、ntiality of sensed data are very important to protect the USN services from fraudulent data. The functions of various USN applications and services can be summarized as follows: finding appropriate sensor networks to obtain sensed data; requesting raw sensed data and/or processed data; processing re

38、ceived sensed data; activating actuators; monitoring sensor network status; controlling sensor networks; authenticating sensor networks; providing appropriate services to users. These functions are commonly required by many types of USN applications and services. Concerning complexity, scalability a

39、nd cost-effectiveness, it would be beneficial to support functions by a separate entity rather than by each USN application and service. 6.2 Description of USN middleware USN middleware is an intermediate entity that provides functions commonly required by different types of USN applications and ser

40、vices. USN middleware receives requests from USN applications and delivers those requests to appropriate sensor networks. Similarly, USN middleware receives sensed data or processed data from sensor networks and delivers them to appropriate USN applications. USN middleware can provide information pr

41、ocessing functions such as query processing, context-aware processing, event processing, sensor network monitoring and so on. 6.3 Use cases of USN services USN services use only sensor nodes or both sensor nodes and RFID readers. In some cases, USN services can activate actuators after processing th

42、e sensed data. Some other USN services monitor and/or control sensor networks. USN services can be categorized into three groups, based on the above observations: using only sensed data including RFID tag data (e.g., healthcare applications); activating one or more actuators, based on the sensed dat

43、a, including RFID tag data (e.g., cold chain management applications); monitoring and/or controlling sensor networks, including RFID readers (e.g., sensor network monitoring applications). Use cases in this Recommendation show how USN services and USN middleware work together. 6.3.1 Healthcare appli

44、cations A healthcare application continuously monitors the location and the health status of the persons within the range of a sensor network in buildings, in order to handle possible emergencies. See Figure 1. Every resident wears a sensor node on his/her wrist, which looks like a wristwatch. The s

45、ensor node senses body temperature, pulse, momentum, and electrocardiogram (ECG) of the resident and then periodically transmits the sensed data to the USN application. A healthcare 4 Rec. ITU-T F.744 (12/2009) application displays the current location and health condition of the resident based on t

46、he sensed data. Sensor node Gateway USN middlewareApplicationserver Temperature sensor Pressure sensor Pulse sensor ECG sensor F.744(09)_F01.doc Bedroom Living room Bathroom Kitchen Family Hospital Police station Figure 1 Use case of a healthcare service A healthcare application needs residents medi

47、cal histories and medical background to provide context-aware service for each resident. Based on the medical background, context-aware rules can be created. Context-aware rules take sensed data and residents medical histories as inputs and issue emergency notifications when certain emergency condit

48、ions are met. Emergency notifications are delivered to the related authorities such as a hospital, a police station and the relatives or family to handle the situation appropriately. The steps are as follows: Step 1: Managers or operators of a healthcare application should generate appropriate rules

49、 based on the medical background to process context-aware information. For services tailored to the individual, the rules need to take residents medical histories as inputs. Step 2: Each resident wears a sensor node on his/her wrist. After being turned on, each sensor node senses body temperature, pulse, momentum, and ECG and then periodically sends that sensed data to USN middleware. Step 3: When a sensor network tries to connect to USN middleware, the USN middleware authenticates the connecting