IEC 62734:2014/AMD1:2019

Amendment 1 - Industrial networks - Wireless communication network and communication profiles - ISA 100.11a

Amendement 1 - Réseaux industriels - Réseau de communication sans fil et profils de communication - ISA 100.11a

General Information

• Status: Published
• Publication Date: 30-Jul-2019
• ICS: 01 - GENERALITIES. TERMINOLOGY. STANDARDIZATION. DOCUMENTATION
• ICS: 33.160.60 - Multimedia systems and teleconferencing equipment
• ICS: 33.170 - Television and radio broadcasting
• Technical Committee: SC 65C - Industrial networks
• Current Stage: PPUB - Publication issued
• Start Date: 09-Aug-2019
• Completion Date: 31-Jul-2019

Relations

• Amends: IEC 62734:2014 - Industrial networks - Wireless communication network and communication profiles - ISA 100.11a
• Effective Date: 05-Sep-2023

Standards Content (Sample)

IEC 62734
®

Edition 1.0 2019-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
A MENDMENT 1
AM ENDEMENT 1

Industrial networks –
Wireless communication network and communication profiles – ISA 100.11a

Réseaux industriels –
Réseau de communication sans fil et profils de communication – ISA 100.11a

IEC 62734:2014-10/AMD1:2019-07(en-fr)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2019 IEC, Geneva, Switzerland

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.


Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Central Office Tel.: [phone]
3, rue de Varembé [e-mail]
CH-1211 Geneva 20 www.iec.ch
Switzerland

About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.

need further assistance, please contact the Customer Service

Centre: [e-mail].


A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Recherche de publications IEC - Electropedia - www.electropedia.org
webstore.iec.ch/advsearchform Le premier dictionnaire d'électrotechnologie en ligne au
La recherche avancée permet de trouver des publications IEC monde, avec plus de 22 000 articles terminologiques en
en utilisant différents critères (numéro de référence, texte, anglais et en français, ainsi que les termes équivalents dans
comité d’études,…). Elle donne aussi des informations sur les 16 langues additionnelles. Egalement appelé Vocabulaire
projets et les publications remplacées ou retirées. Electrotechnique International (IEV) en ligne.

IEC Just Published - webstore.iec.ch/justpublished Glossaire IEC - std.iec.ch/glossary
Restez informé sur les nouvelles publications IEC. Just 67 000 entrées terminologiques électrotechniques, en anglais
Published détaille les nouvelles publications parues. et en français, extraites des articles Termes et Définitions des
Disponible en ligne et une fois par mois par email. publications IEC parues depuis 2002. Plus certaines entrées
antérieures extraites des publications des CE 37, 77, 86 et
Service Clients - webstore.iec.ch/csc CISPR de l'IEC.

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
[e-mail].

---------------------- Page: 2 ----------------------
IEC 62734

®


Edition 1.0 2019-07




INTERNATIONAL



STANDARD




NORME



INTERNATIONALE




A MENDMENT 1

AM ENDEMENT 1





Industrial networks –

Wireless communication network and communication profiles – ISA 100.11a




Réseaux industriels –

Réseau de communication sans fil et profils de communication – ISA 100.11a
















INTERNATIONAL

ELECTROTECHNICAL

COMMISSION


COMMISSION

ELECTROTECHNIQUE


INTERNATIONALE




ICS 33.160.60; 33.170 ISBN 978-2-8322-7149-0



Warning! Make sure that you obtained this publication from an authorized distributor.

Attention! Veuillez vous assurer que vous avez obtenu cette publication via un distributeur agréé.

® Registered trademark of the International Electrotechnical Commission
Marque déposée de la Commission Electrotechnique Internationale

---------------------- Page: 3 ----------------------
– 2 – IEC 62734:2014/AMD1:2019
© IEC 2019

FOREWORD
This amendment has been prepared by subcommittee 65C: Industrial networks, of IEC
technical committee 65: Industrial-process measurement, control and automation.
The text of this amendment is based on the following documents:
FDIS Report on voting
65C/965/FDIS 65C/970/RVD

Full information on the voting for the approval of this amendment can be found in the report
on voting indicated in the above table.
The committee has decided that the contents of this amendment and the base publication will
remain unchanged until the stability date indicated on the IEC website under
"http://webstore.iec.ch" in the data related to the specific publication. At this date, the
publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.

___________

GENERAL REPLACEMENTS
Throughout the document, replace references to IEEE 802.15.4:2011 as follows.
Location Replace With
4.6.10.2.8 “IEEE 802.15.4:2011” “IEEE 802.15.4”
th
“IEEE 802.15.4e” “IEEE 802.15.4”
6.3.5.2, 6 dash
st
“IEEE 802.15.4:2011, 7.4.1” “IEEE 802.15.4-2015, 9.4.1”
7.3.1.2, 1 paragraph
th
“IEEE 802.15.4:2011, Table 58” “IEEE 802.15.4-2015, Table 9-6”
7.3.1.2, 4 paragraph
st
“IEEE 802.15.4:2011, 7.4.3” “IEEE 802.15.4-2015, 9.4.3”
7.3.2.3.2, 1 paragraph
st
“IEEE 802.15.4:2011, 7.3.2” “IEEE 802.15.4-2015, 9.3.2.1”
7.3.2.4.10, 1 bullet
7.3.2.5, step i), (4 times) “IEEE 802.15.4:2011, 7.3.4” “IEEE 802.15.4-2015, 9.3.4”
7.3.2.5, step i)1) “IEEE 802.15.4:2011, Table 58” “IEEE 802.15.4-2015, Table 9-6”
7.3.2.6, step f), (4 times) “IEEE 802.15.4:2011, 7.3.5” “IEEE 802.15.4-2015, 9.3.5”
7.3.2.6, step f)1) “IEEE 802.15.4:2011, Table 58” “IEEE 802.15.4-2015, Table 9-6”
7.3.2.6, step f)1) “IEEE 802.15.4:2011, 5.2.2.2.2” “IEEE 802.15.4-2015, 7.3.2.2
7.3.2.6, step f)2) “IEEE 802.15.4:2011, Table 57” “IEEE 802.15.4-2015, Table 9-5”
7.3.3.8, step i), (4 times) “IEEE 802.15.4:2011, 7.3.4” “IEEE 802.15.4-2015, 9.3.4”
7.3.3.8, step i)1) “IEEE 802.15.4:2011, Table 58” “IEEE 802.15.4-2015, Table 9-6”
7.3.3.9, step g), (4 times) “IEEE 802.15.4:2011, 7.3.5” “IEEE 802.15.4-2015, 9.3.5”

---------------------- Page: 4 ----------------------
IEC 62734:2014/AMD1:2019 – 3 –
© IEC 2019
Location Replace With
7.3.3.9, step g)1) “IEEE 802.15.4:2011, Table 58” “IEEE 802.15.4-2015, Table 9-6”
7.3.3.9, step g)1) “IEEE 802.15.4:2011, 5.2.2.2.2” “IEEE 802.15.4-2015, 7.3.2.2
7.3.3.9, step g)2) “IEEE 802.15.4:2011, Table 57” “IEEE 802.15.4-2015, Table 9-5”
rd
“IEEE 802.15.4:2011, 8.1.5” “IEEE 802.15.4-2015, 10.1.5”
8.2.2.5, 3 paragraph
st
“IEEE 802.15.4:2011, Table 66” “IEEE 802.15.4-2015, Table 10-4”
8.2.3.2, 1 paragraph
9.3.2.1, NOTE “IEEE 802.15.4:2011” “IEEE 802.15.4-2015”
th
“IEEE 802.15.4:2011” “IEEE 802.15.4”
9.3.2.1, 5 paragraph
st
“IEEE 802.15.4:2011, 5.2.2.2” “IEEE 802.15.4-2015, 7.3.2”
9.3.3.1, 1 paragraph
st
“IEEE 802.15.4:2011, 5.2.1 and
“IEEE 802.15.4-2015, 7.2 and 7.3.2”
9.3.3.1, 1 paragraph
5.2.2.2”
nd
“IEEE 802.15.4:2011, 5.2.1.2” “IEEE 802.15.4-2015, 7.2.2”
9.3.3.1, 2 paragraph
rd
“IEEE 802.15.4:2011, 5.2.3” “IEEE 802.15.4-2015, 7.3.3”
9.3.3.1, 3 paragraph
rd
“IEEE 802.15.4:2011, 5.2.1.1.8” “IEEE 802.15.4-2015, 7.2.1.10”
9.3.3.1, 3 paragraph
st
“IEEE 802.15.4:2011, 5.2.1” “IEEE 802.15.4-2015, 7.2”
9.3.3.2, 1 paragraph
st
“IEEE 802.15.4:2011, Figure 35” “IEEE 802.15.4-2015, Figure 7-1”
9.3.3.2, 1 paragraph
9.3.3.2, field a) “IEEE 802.15.4:2011, 5.2.1.1” “IEEE 802.15.4-2015, 7.2.1”
rd
“IEEE 802.15.4:2011, Annex B” “IEEE 802.15.4-2015, Annex B”
11.3.2, 3 paragraph
13.11.2.6, d) “IEEE 802.15.4:2011” “IEEE 802.15.4”
rd
“IEEE 802.15.4:2011” “IEEE 802.15.4-2015”
Table B.5, 3 column header
st
“IEEE 802.15.4:2011, B.3.2” “IEEE 802.15.4-2015, B.3.2”
H.1.4, 1 paragraph

OTHER REPLACEMENTS
0.3 Potentially relevant patents
In cell d) of the table providing coordinates for the Yokogawa Electric Corporation patent
holder, replace “Musashina-shi” with “Musashino-shi”.
2 Normative references
™ ™ 2
Replace reference to IEEE 802.15.4 :2011 with “IEEE Std 802.15.4 -2015 , IEEE Standard
for Low-Rate Wireless Networks”.
4.6.11.1 Overview
Replace the existing NOTE 3 with the following note:
NOTE 3 IEEE 802.15.4 specifies channel hopping and TSCH mechanisms that are similar to, but not identical to,
many of the DL mechanisms specified in this document.
Table 7 – ARMO attributes
th
For attribute 2, 4 column, add “Valid range: –4 to 32 767”.
Table 10 – DMO attributes
th
For attribute 8, 4 column, add “Default value: null string (length zero)”.
th
For attribute 27, 4 column, replace “Default value: 30 s” with “Default value: 248 s”.

---------------------- Page: 5 ----------------------
– 4 – IEC 62734:2014/AMD1:2019
© IEC 2019
th
For attribute 29, 4 column, replace “Default value: 30 s” with “Default value: 62 s”.
Table 19 – Proxy_System_Manager_Join method
Add Input Argument 11 as follows:
11 Consortium_Info Type: Unsigned8 Provides Consortium-specific information
from the joining device that is not specified
by this document

Replace existing Output Arguments 7 and 8 with the following text:
7 Assigned_Max_TSDU_Size Type: Indicates the maximum TSDU supported in
Unsigned16 octets which can be converted by the
source into max APDU size by taking into
account the TL, security, AL headers and
TMIC sizes
8 MIC Type: This value is used for protecting argument
OctetString4 1 through 7 with Join key. This MIC value
is generated by the Security Manager. The
Advertisement router shall not overwrite
this value. See 7.4.4.3.3.2

Table 23 – System_Manager_Join method
Add Input Argument 11 as follows:
11 Consortium_Info Type: Provides Consortium-specific information
Unsigned8 from the joining device that is not specified
by this document

Replace existing Output Arguments 7 and 8 with the following text:
7 Assigned_Max_TSDU_Size Type: Indicates the maximum TSDU supported in
Unsigned16 octets which can be converted by the
source into max APDU size by taking into
account the TL, security, AL headers and
TMIC sizes
Type: This value is used for protecting argument
8 MIC
OctetString4 1 through 7 with Join key. This MIC value
is generated by the Security Manager. The
Advertisement router shall not overwrite
this value. See 7.4.4.3.3.2

Table 27 – SCO method for contract establishment, modification, or renewal
th
For Input Argument 16, 5 column, add “Valid range: –32 768 to 16”.
th
For Input Argument 17, 5 column, add “Valid range: –32 768 to 16”.
th
For Output Argument 13, 5 column, add “Valid range: –32 768 to 16”.
th
For Output Argument 14, 5 column, add “Valid range: –32 768 to 16”.
th
For Output Argument 24, 5 column, add “Valid range: –32 768 to 16”.
th
For Output Argument 25, 5 column, add “Valid range: –32 768 to 16”.

---------------------- Page: 6 ----------------------
IEC 62734:2014/AMD1:2019 – 5 –
© IEC 2019
Table 30 – Contract_Data data structure
rd
For element 15, 3 column, add “Valid range: –32 768 to 16”.
rd
For element 16, 3 column, add “Valid range: –32 768 to 16”.
Table 31 – New_Device_Contract_Response data structure
rd
column, add “Valid range: –32 768 to 16”.
For element 3, 3
rd
For element 4, 3 column, add “Valid range: –32 768 to 16”.
7.3.2.6 Processing of received DPDUs
In step e), delete “Additionally, the procedure shall verify that the 8-bit MHR sequence
number is not 0xFF. If the 8-bit MHR sequence number is 0xFF, the procedure shall return
with a status of INVALID_SEQUENCE_NUMBER.”
7.3.3.9 Processing for received TPDUs
In step h), replace “may decrement” with “shall decrement”.
7.4.4.3.3.2 MIC generation for System_Manager_Join response
Replace the existing formula with the following:
[Output Argument number 1 . number 7 in Table 23
MACTag = HMAC-MMO
K_join
|| EUI- || Challenge ]
64join_device join_device
Table 62 – Security_Sym_Join_Request data structure
Replace the elements in Table 62 with the following:
New_Device_EUI64 1 Type: EUI64Address
Classification: Constant
Accessibility: Read only
DL_Subnet_ID 2 Type: Unsigned16
Classification: Static
Accessibility: Read/write
Comm_SW_Major_Version 3 Type: Unsigned8
Classification: Static
Accessibility: Read only
Comm_SW_Minor_Version 4 Type: Unsigned8
Classification: Static
Accessibility: Read only
128_Bit_Challenge_From_New_Device 5 Type: Unsigned128
Classification: Static
Accessibility: Read/write
Algorithm_Identifier 6 Type: Unsigned8
Classification: Static
Accessibility: Read only
Default value: 1
MIC 7 Type: Unsigned32
Classification: Static
Accessibility: Read only

---------------------- Page: 7 ----------------------
– 6 – IEC 62734:2014/AMD1:2019
© IEC 2019
7.4.5.2.2 Symmetric-key join request
In the text following Table 62, after the first bullet (New_Device_EUI64), insert the following
three additional bullets:
• DL_Subnet_ID is the DL subnet that the new device is trying to join; it is also the DL
subnet of the advertising router.
• Comm_SW_Major_Version is a copy of the DMO Comm_SW_Major_Version attribute; see
Table 10, Attribute 20.
• Comm_SW_Minor_Version is a copy of the DMO Comm_SW_Minor_Version attribute; see
Table 10, Attribute 21.
In the last bullet following Table 62, replace “The MIC-32 is computed over the elements 1
through 4” with “The MIC-32 is computed over the elements 1 through 6”.
7.5.4 Proxy security management object methods related to the session
establishment
th
In the 7 bullet following Table 81, delete “assigned in the joining process”.
nd
In the 2 bullet following Table 82, delete “assigned during the joining process”.
7.6.3 Device security management object methods related to T-key update
th
bullet following Table 84, delete “assigned in the joining process”.
In the 4
nd
In the 2 bullet following Table 85, delete “assigned during the joining process”.
Table 95 – Delete key method
For Input Argument number 8, last column, delete “assigned in joining process”.
7.11.3.2 Additional device security management object methods to support key
management
At the end of the paragraph before Table 96, add the following:
Use of the Key_Policy_Update method shall be limited to changes to SoftLifespan_Ratio.
More general changes of key policy are accomplished by key replacement, as described in
7.6.
Table 96 – Key_Policy_Update method
For Input Argument number 10, last column, delete “assigned in joining process”.
9.1.9.4.3 Unicast transaction
th
Delete the 5 paragraph, beginning with "IEEE 802.15.4 permits CCA Mode 3".
9.1.15.6 Country code
Delete NOTE 1, change "NOTE 2" to "NOTE" (i.e., delete the number), and replace the
paragraph after the deleted NOTE 1 with the following:
When Bit11, Bit13 and Bit14 (ETSI, LBT and FHSS) are all true, operation may need to
switch momentarily to the non-adaptive rules of ETSI EN 300 328 v2.1.1 while sending a
near-maximal-size ACK/NAK DPDU (as short control signaling) within a transaction and
for the immediately following Tx-gap-time of EN-mandated non-transmission, thus

---------------------- Page: 8 ----------------------
IEC 62734:2014/AMD1:2019 – 7 –
© IEC 2019
supporting mode V.4 category 6), where the exact requirements for such momentary
mode-switching are specified.
Table 117 – ACK/NAK DPDU DHR
In the last row, first column, replace "0.3" with "0 or 3".
9.3.5.2.4.2 Advertisement join links
In the text after Table 128, replace the text of item a) as follows:
DauxJoinBackoff. During the join process, DauxJoinBackoff shall be used instead of
MaxBackoffExp, following the exponential backoff procedure described in 9.1.8.2.
Table 129 – Defaults for links created from advertisements
In the intersection of DauxJoinRx and Type_SelectiveAllowed, replace 1 with 0 as shown:
Field name DauxJoinTx DauxJoinRx DauxAdvRx (when
DauxJoinFldXmit.Bit3 =1)
Type-SelectiveAllowed 1 0 1

9.3.5.3.1 General
In the penultimate paragraph, after “a solicitation’s DMIC shall be built using a security key of
K_global and a nominal TAI time of zero”, add “and a source address of zero”.
Table 141 – DLMO attributes
th
For attribute 5, 4 column, replace “Default value: Null” with “Default value: 0x80”.
th
For attribute 12, 4 column, replace “Default value: 120 (30 s)” with “Default value:
248 (62 s)”.
Table 148 – dlmo.DeviceCapability OctetString structure
Replace the row for Energy Design with the following:
5-8 EnergyDesign (see Table 146)

9.4.2.23 DLMO device capabilities
In the text following Table 148, in the description of • dlmo.DeviceCapability.ClockStability
nd
(2 bullet), replace “absence” with “presence”.
9.4.2.27.1 General
th
In the 5 paragraph, replace “Such skipped links should be treated as equivalent to NAK for
the applicable channel” with “Such skipped links should be counted as a NoACK for the
applicable channel, that is, they should be counted as unacknowledged DL transmissions in
the ChannelDiag diagnostic”.
9.4.3.5.3 Superframe current timeslot state
Replace the formula for ChOffset (after " The timeslot offset into that channel-hopping cycle
is") with the following:
ChOffset = ((SlotNumAbs – ChBirth) mod ChCycle) / ChRate

---------------------- Page: 9 ----------------------
– 8 – IEC 62734:2014/AMD1:2019
© IEC 2019
Table 184 – Values for dlmo.Link[].Schedule
nd
For Element encoding, 2 column, replace "BooleanArray32" with "32-bit BitString".
Table 188 – Diagnostic summary OctetString fields
nd
For ClockSigma, 2 column, replace “Type: Integer16” with “Type: Unsigned16”.
Table 229 – TLMO attributes
rd
For attribute 2, 3 column, replace in the description “Number of active ports” with “Maximum
number of ports available”.
Add attribute 11 as follows:
TPDUoutOfSecurityPolicies 11 Used to change the priority Type: Alert report –
AlertDescriptor of the descriptor
TPDUoutOfSecurityPolicies
Classification: Static
alert; this alert can also be
turned on or turned off
Accessibility:
Read/write
Initial default value:
Alert report disabled
= True
Alert report priority =
2 (journal)
Valid value set: See
type definition

Table 368 – Device provisioning object
nd
In the latter part of Table 368, replace, in the 2 column, attribute identifiers as follows:
Attribute name Attribute identifier
PKI_Certificate_Type 22
PKI_Root_Certificate 18
Number of PKI_Certificates 19
PKI_Certificate 20
Current_UTC_Adjustment 21

th
For attribute 11, in the 4 column, replace “Default value: 0” with “Default value: 1”.
th
For attribute 13, in the 4 column, replace “Default value: 1” with the following:
Default value:
0: if asymmetric key join not supported
1: if asymmetric key join supported
th
For attribute 16, in the 4 column, replace “Type: BitArray16” with “Type: Unsigned16”.
Table 371 – Device provisioning service object
th
For attribute 8, in the 4 column, replace “Type: BitArray16” with “Type: Unsigned16”.

---------------------- Page: 10 ----------------------
IEC 62734:2014/AMD1:2019 – 9 –
© IEC 2019
Table B.18 – Routing table size
rd
For Item number RTS3, 3 column, replace “15” with “5”.
Table B.19 – Address table size
rd
For Item number ATS3, 3 column, replace “15” with “5”.
Annex V – Compliance with ETSI EN 300 328 v1.8.1
In the annex heading, replace “v1.8.1” with “v2.1.1”.
rd
In the 3 paragraph, replace “at least 15 channels” with “at least NC channels, where NC = 5
for non-adaptive FHSSM and NC = 15 for adaptive FHSSM”.
Replace existing NOTE 3 with the following:
NOTE 3 ETSI 300 328:2016 v2.1.1 4.3.1.4 permits “blacklisting” (i.e. blocking) operation on some of the channels
specified in a FHSSM frequency-hopping schedule, but does not permit the number of different hopping channels
to be reduced to fewer than NC channels. Therefore inclusion of fewer than NC channels in a channel map that
determines the frequency-hopping cycle of selected channels means that the only possible remaining operating
regimes are those under WBM.
In NOTE 4, replace the first sentence with: “These requirements are ETSI EN 300 328:2016
v2.1.1 4.3.1.7.2 (FHSSM) and 4.3.2.6.3.2.2 (WBM) and related text.”
th
Under the 5 paragraph, first bullet, replace “≤ 1 ms” with “≤ 1,056 ms”.
th
Under the 5 paragraph, third bullet, replace “a given channel” with “a given channel, whether
transmitting or not,”.
Replace existing NOTE 5 with the following:
NOTE 5 Tx-sequence-time and Tx-gap-time are defined in ETSI EN 300 328:2016 v2.1.1, 4.3.1.3 (FHSSM) and
4.3.2.4 (WBM). Dwell time, which applies to FHSSM, is defined in ETSI EN 300 328 v2.1.1, 3.1. Dwell time is
necessarily at least as large as Tx-sequence-time. Dwell time need never be larger than the duration of one
timeslot.
th th th
Replace existing 6 , 7 and 8 paragraphs with the following:
ETSI EN 300 328:2016 v2.1.1, 4.3.2.3.3 (WBM) imposes a power spectral density limit for
WBM of 10 dBm/MHz EIRP. Due to the spectrum of the IEEE 802.15.4:2015 2,4 GHz DSSS
modulation, this constraint limits equipment operating under ETSI EN 300 328 v2.1.1’s WBM
regulations to a maximum transmit power (total for all active transmit chains after any antenna
and beam-forming gain) of 20 mW (+13 dBm) EIRP.
ETSI EN 300 328:2016 v2.1.1, 4.3.1.2 (FHSSM) and 4.3.2.2 (WBM) limit maximum transmit
power, after any antenna and beamforming gain, to 100 mW (+20 dBm) EIRP.
ETSI EN 300 328:2016 v2.1.1, 4.3.1.6 (FHSSM) and 4.3.2.5 (WBM) limit the Medium
Utilization of non-adaptive equipment, and of adaptive equipment operating in a non-adaptive
mode, so that the total energy transmitted over any observation interval as specified by EN
300 328 averages ≤ 10 mW (+10 dBm) EIRP. Use of adaptivity removes this restriction on
average transmit power.
th
In the 9 paragraph, replace “2012 v1.8.1, 4.3.2.3” with “2016 v2.1.1, 4.3.2.4”.
th
In the 10 paragraph, replace “2012 v1.8.1, 4.3.1.2” with “2016 v2.1.1, 4.3.1.3”.

---------------------- Page: 11 ----------------------
– 10 – IEC 62734:2014/AMD1:2019
© IEC 2019
th th th
Replace existing 11 , 12 and 13 paragraphs as follows:
The ACK/NAK DPDUs that are sent by D-transaction respondents as immediate responses
(within the same slot) to the Data DPDU sent by the D-transaction initiator can be considered
as “short control signaling” (SCS, ETSI EN 300 328:2016 v2.1.1 4.3.1.7.4 (FHSSM) and
4.3.2.6.4 (WBM)). While LBT is not required before transmitting SCS, ETSI EN 300 328:2016
v2.1.1, 4.3.1.7.4.2 (FHSSM) and 4.3.2.6.4.2 (WBM) constrain each instance of SCS to occupy
no more than 10 % of the claimed dwell time. That restriction has an inverse impact on the
minimum timeslot duration for the system, requiring the timeslot duration to be increased (and
aggregate system throughput correspondingly decreased) relative to that otherwise required,
just so that the channel occupancy of each SCS instance (i.e., an ACK/NAK DPDU) is never
greater than 10 % of the claimed dwell time.
In devices claiming conformance to adaptive-mode FHSSM, the recommended alternative
approach to meeting ETSI EN 300 328:2016 v2.1.1, 4.3.1.7.4.2 is to have each D-transaction-
respondent dynamically mode-switch to operation in a non-adaptive mode while sending any
ACK/NAK DPDU that is too lengthy to meet the 10 % of-dwell-time restriction, and for 5 ms
thereafter (the mandated minimum Tx-gap-time), after which the responding device reverts to
the adaptive mode of operation. It appears that the only significant consequence of such a
temporary non-adaptive operating mode is that the responding device is not permitted to
initiate a D-transaction in the immediately following timeslot unless the intervening period of
non-transmission meets the minimum Tx-gap-time requirement.
ETSI EN 300 328:2016 v2.1.1, 4.3.1.4.3 (FHSSM) requires that each cyclic channel-hopping
sequence contain a minimum of NC channels, whether idle or active, where NC = 5 for non-
adaptive FHSSM and NC = 15 for adaptive FHSSM. In terms of this document, this
requirement means that only dlmo.Ch entries (Table 160) whose size field has a value of NC
or greater are suitable for use in FHSSM mode under ETSI EN 300 328 v2.1.1. Therefore,
when channel-hopping sequences with cycle lengths less than NC are used, operation under
ETSI EN 300 328 v2.1.1 necessarily conforms to the EN’s WBM regulations.
th
In the 14 paragraph, replace “v1.8.1” with “v2.1.1”.
th
In the 15 paragraph, replace “v1.8.1” with “v2.1.1”.
th
Under the 15 paragraph, replace existing item 6) and its existing NOTE 7 with the following:
6) adaptive FHSSM equipment that may momentarily mode-switch to non-adaptive
operation when operating as a D-transaction responder (i.e. to send an ACK/NAK
DPDU that is too lengthy to qualify as SCS) with
dlmo.CountryCode.mode=0b”x1101x”.
NOTE 7 Such momentarily mode-switching is only required when the ACK/NAK PPDU to be transmitted will
occupy more than 10 % of a timeslot, which can only occur when the timeslot is < 10,56 ms and the ACK/NAK
DPDU's MHR conveys an EUI-64 source address, or when the timeslot is < 9,28 ms.
From item d) to the end of Annex V, replace all existing text with the following:
d) for operation in mode 2), limiting the total number of transmissions, both of Data
DPDUs and of ACK/NAK DPDUs, such that the mean output power, P Avg, is
out
≤ 10 mW (+10 dBm) EIRP over each possible 1,0 s measurement interval;
e) for operation in mode 5), limiting the total number of transmissions, both of Data
DPDUs and of ACK/NAK DPDUs, such that the mean output power, P Avg, is
out
≤ 10 mW (+10 dBm) EIRP over each possible of 100-timeslot measurement interval;
f) for operation in modes 2) and 5), meeting the required Tx-gap-time of non-
transmission after transmission of a Data DPDU;
NOTE 9 This constraint is met automatically whenever the timeslot duration is ≥ 8,508 ms in mode 2), or
≥ 9,256 ms in mode 5).

---------------------- Page: 12 ----------------------
IEC 62734:2014/AMD1:2019 – 11 –
© IEC 2019
g) for operation in modes 2) and 5), and in mode 6) when momentarily operating under
non-adaptive rules, meeting the required Tx-gap-time interval of non-transmission after
transmission of an ACK/NAK DPDU.
NOTE 10 For operation in mode 6), EN 300 328 v2.1.1:2015 4.3.1.6.3 limits the medium utilization for
transmissions of ACK/NAK DPDUs sent while the device is momentarily operating under non-adaptive FHSSM
rules to ≤ 10 %, as measured over any possible 100-timeslot interval. That constraint is met automatically due to
the small percentage of timeslots in which the device could be sending ACK/NAK DPDUs that require momentary
non-adaptive operation, and the relatively short length of those ACK/NAK DPDUs.
For d), e), f), and g), the equipment dynamically monitors its recent activity to avoid
transmitting whenever doing so would violate any of those constraints.
NOTE 11 While a system manager can schedule device activity pessimistically to ensure that d), e), f), and g) are
always met, it is the device's own responsibility to monitor its recent activity and inhibit transmission when doing so
would violate regulatory constraints. Thus the ultimate responsibility for operation of a collection of devices rests
with the individual devices themselves, not some remote manager that could be subverted by a successful
cyberattack on a single device.
EN 300 328 v2.1.1:2016 specifies Receiver Categories (4.2.3) based on maximum and mean
transmitter output power, P Max and P Avg. Equipment designed to operate under this
out out
document typically will fall under Receiver Category 1 (4.2.3.2.1) or Receiver Category 2
(4.2.3.2.2). The claimed receiver
...