IEEE ISO IEC 18881 2016
$39.00
ISO/IEC/IEEE International Standard — Information technology — Ubiquitous green community control network — Control and management
Published By | Publication Date | Number of Pages |
IEEE | 2016 | 65 |
– Active. This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), Ubiquitous Green Community Control Network Protocol; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.
PDF Catalog
PDF Pages | PDF Title |
---|---|
5 | ISO/IEC/IEEE 18881:2016 IEEE Std 1888.1™-2013 Front Cover |
7 | Title page |
10 | Notice to users Laws and regulations Copyrights Updating of IEEE documents Errata |
11 | Patents |
12 | Participants |
14 | Introduction |
15 | Contents |
17 | Important Notice 1. Overview 1.1 Scope 1.2 Purpose |
18 | 2. Normative references 3. Definitions, acronyms, and abbreviations 3.1 Definitions 3.2 Acronyms and abbreviations |
19 | 4. Architecture 4.1 General |
20 | 4.2 System architecture |
22 | 4.3 General workflow to manage sensors and actuators |
24 | 5. Management and control unit (MCU) 5.1 General 5.2 Framework |
25 | 5.3 Typical MCU communication sequences |
27 | 6. Gateway (GW) 6.1 General 6.2 Framework |
28 | 6.3 Access control |
29 | 6.4 Event handling 7. Gateway (GW) control and management 7.1 Overview |
31 | 7.2 Setting the configuration and running status of the GW |
32 | 7.3 Getting the configuration and running status of the GW |
33 | 7.4 Sending control command data to actuators |
34 | 7.5 Reading the real-time data of sensors |
35 | 8. SERVICE protocol 8.1 Protocol definition |
36 | 8.2 Data structure |
42 | 9. WRITE, FETCH, and TRAP protocol extension 9.1 General |
43 | 9.2 Data structure 9.3 Redefinition of header class |
44 | 9.4 Control class |
45 | 10. Compatibilities with IEEE Std 1888-2011 |
46 | 11. Security considerations |
47 | Annex A (informative) A typical process of the service provided by the MCU A.1 Scenario |
48 | A.2 Query service using service protocol A.3 Service invocation using service protocol |
50 | Annex B (informative) Recommended component model for component management B.1 Naming rule of Point ID |
51 | B.2 Product information (product namespace) B.3 Implemented function profile |
53 | B.4 Configuration items of the component |
55 | B.5 Status items of the component |
56 | Annex C (informative) Access control list encoding C.1 An example of the rule of ACL encoding |
57 | C.2 An example to encode an ACL |
61 | Annex D (informative) Procedures to provide the ACL from the MCU to the components D.1 Example 1: The MCU sets the ACL for GW1 D.2 Example 2: Following C.2, GW1 requests own ACL from the MCU |
63 | Annex E (informative) Importing an SNMP management information base |
64 | Annex F (informative) Bibliography |