Skip to product information
1 of 7

PayPal, credit cards. Download editable-PDF and invoice in 1 second!

GB/T 38323-2019 English PDF (GBT38323-2019)

GB/T 38323-2019 English PDF (GBT38323-2019)

Regular price $200.00 USD
Regular price Sale price $200.00 USD
Sale Sold out
Shipping calculated at checkout.
Delivery: 3 seconds (Download full-editable-PDF + Invoice).
Quotation: Click GB/T 38323-2019>>Add to cart>>Quote
Editable-PDF Preview (Reload if blank, scroll for next page)

GB/T 38323-2019: Digital technique application of building and residence community -- Cooperation management protocol for home internet of things
This Standard specifies the collaborative management architecture, scenario description file format, and scenario management that are involved in the cooperation management protocol for home internet of things. This Standard applies to the connectivity among intelligent devices in the home environment.
GB/T 38323-2019
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 35.240
L 70
Digital technique application of building and
residence community - Cooperation management
protocol for home internet of things
ISSUED ON: DECEMBER 10, 2019
IMPLEMENTED ON: JULY 01, 2020
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of
China.
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative references ... 4
3 Terms and definitions ... 4
4 Abbreviations ... 5
5 Collaborative management architecture ... 5
6 Scenario description file format ... 8
7 Scenario management ... 15
Digital technique application of building and
residence community - Cooperation management
protocol for home internet of things
1 Scope
This Standard specifies the collaborative management architecture, scenario description file format, and scenario management that are involved in the cooperation management protocol for home internet of things.
This Standard applies to the connectivity among intelligent devices in the home environment.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only the dated version applies to this document. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 35134, Smart home for Internet of things - Device description method GB/T 35143, Smart home for Internet of things - Unicode of data and device 3 Terms and definitions
The following terms and definitions are applicable to this document.
3.1 Home internet of things
The network that connects computers, health devices, household appliances, water and electricity heating meters, lighting equipment, and safety and alarm devices in the home category according to Internet protocols.
3.2 Cooperative management
The process of coordinating among associated devices in the smart home
network to complete the predetermined goals.
3.3 Home smart gateway
c) Common scenario types shall include manual trigger, timing trigger, and conditional trigger, which shall meet the following requirements:
1) Manual trigger: cause the linkage of the device or service, by manually clicking the software button or hardware switch panel, remote control,
etc.;
2) Timing trigger: cause the linkage of device or service, by setting the timing time;
3) Conditional triggering: cause the linkage of device or service, by setting conditions such as device alarm, device status change event, service
status change event, etc.
5.2 Collaborative architecture
5.2.1 Architecture
The home internet of things collaborative management architecture shall include instruction set layer, service layer, collaboration layer, and application layer (as shown in Figure 1) and shall meet the following requirements: a) Instruction set: the control instruction that uniformly defines the device or service;
b) Service layer: the device description file describes the functional services that are supported by the device; the service description file describes the application services other than the device;
c) Collaboration layer: the scenario description file is defined according to the device description file and the service description file;
d) Application layer: it manages the generation, storage, editing,
transmission, execution and deletion of scenarios.
Trigger Object Optional
Trigger, including header information, multiple
conditions and their logical relationships; if there
is no such a field, the scenario is triggered
manually
Actuator Object Required Actuator, including header information, multiple actions and their logical relationships 6.2.2 File header
The scenario description file header shall include information such as the version number, scenario ID, scenario name, scenario summary of the scenario description file specification. See Table 2 for details.
Table 2 -- Scenario description file header field
Field name Type Selection status Note
Version Character string Required
The version number of the scenario description
file specification is divided into a major version
number and a minor version number, which are
represented by numbers, and are separated by
a ".", such as 0.2
ID Character string Required
The unique identification information of the
scenario conforms to the UUID standard; the
format is xxxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx,
36 digits in total
Name Character string Required
Scenario name, which is used to identify the
scenario, can be customized and modified; it is
up to 16 digits
Abstract Character string Optional
Scenario introduction, which is used to briefly
describe the characteristics of the scenario, can
be customized and modified; it is up to 144 digits
Type Character string Optional
Scenario is divided into three types: single
product scenario, recommended scenario, and
custom scenario. This item is optional; if it is not
filled, it is a custom scenario by default
Grouping Character string Optional
Scenario grouping; this item is mainly used for
APP automatic menu generation. The item
value conforms to the "ABC.DEF.GHI" format;
multiple scenario files automatically compose a
tree menu on this account
6.2.3 Trigger
6.2.3.1 Overview
only in the form of a switch in the scenario editing
interface; if it is not set, it is False by default
Validity Boolean Optional
True -- valid; False -- invalid. It indicates whether
the condition is executed in the scenario
execution engine. If it is not set, it is True by
default
6.2.3.3 Time condition
For the time condition, types such time points, multiple time points, periodic time points, time periods, multiple time periods, periodic time periods can be set. See Table 5 for specific fields of time conditions.
Table 5 -- Specific fields of time condition
Field name Type Selection status Note
Time
parameter
Character
string Required
Format according to the setting rules of spring
timer in Java programming language
6.2.3.4 Device alarm
The device alarm shall be based on the device's alarm event as the triggering condition to link the relevant actions. Its specific fields are shown in Table 6. Table 6 -- Device alarm specific fields
Field name Type Selection status Note
Device
model
Character
string Required
Uniquely identify a device description file, device
type + device model
Device ID Character string Optional
For device ID, according to the device description
file specification, if there is this field, it means a
specific device; if there is not this field, it means
all devices under the model that is represented by
the device model
Alarm code Integer Required
Uniquely identify an alarm code in the device
description file; refer to the device description file
specification
6.2.3.5 Device status
The device status shall be based on the device's status as the triggering condition to link the relevant actions. Its specific fields are shown in Table 7. Table 7 -- Device status specific fields
Field name Type Selection status Note
equal to 2, it also indicates the relative delay
execution order
Delay time Integer Required
Action delay execution time, in seconds (s);
when the delay time type exists, this field is
valid
Action type Integer Required
It represents the action type, which can be the
following: 1 -- status action; 2 -- frequency
action; 3 -- continuous action, this field is
reserved for the future
Function
code Integer Required
Uniquely identify a function in the device
description file
Comparison
operation
code
Character
string Required The value is: isEqual -- equal to
Function
value
Character
string Optional
The variable value that represents the action
change. When the action type is equal to 1, this
field is valid; it shall be formatted according to
several data types that are supported by the
description file specification.
Execution
time Integer Optional
It indicates the number of times the action is
executed. When the action type is equal to 2,
this field is valid
Duration Integer Optional
It indicates the duration of the action, in
seconds (s); when the action type is equal to 3,
this field is valid
Text Character string Optional Additional text of this action
Edit status Boolean Optional
True -- editable; False -- not editable. It
indicates whether the action can be edited. If it
is not editable, the edit item will not be
displayed in the scenario editing interface; only
the text will be displayed (if set). If it is not set,
it is True by default
Switch
setting Boolean Optional
True -- only switch can be set; False -- common
setting. It indicates whether this action exists
only in the form of a switch in the scenario
editing interface; if it is not set, it is False by
default
Validity Boolean Optional
True -- valid; False -- invalid. It indicates
whether the action is executed in the scenario
execution engine. If it is not set, it is True by
default
6.2.4.3 Device action
View full details