prEN IEC 63203-801-2:2026
(Main)Wearable electronic devices and technologies - Part 801-2: Smart body area network (SmartBAN) - Low complexity medium access control (MAC) for SmartBAN
Tragbare elektronische Geräte und Technologien -Teil 801-2: Smartes am Körper getragenes Netzwerk (SmartBAN) - Medium Access Control (MAC) mit geringer Komplexität für SmartBAN
Technologies et dispositifs électroniques prêts-à-porter - Partie 801-2: Smart body area network (SmartBAN) - Contrôle d’accès au support (MAC) à faible complexité pour SmartBAN
Nosljive elektronske naprave in tehnologije - 801-2. del: Pametno telesno omrežje (SmartBAN) - Manj zahteven nadzor dostopa do medija (MAC) za SmartBAN
General Information
- Status
- Not Published
- Publication Date
- 09-Jan-2028
- Technical Committee
- CLC/SR 124 - Wearable Electronic Devices and Technologies
- Current Stage
- 4020 - Enquiry circulated - Enquiry
- Start Date
- 19-Jun-2026
- Due Date
- 31-Oct-2024
- Completion Date
- 19-Jun-2026
Relations
- Effective Date
- 20-Feb-2024
Get Certified
Connect with accredited certification bodies for this standard

BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
prEN IEC 63203-801-2:2026 is a draft published by CLC. Its full title is "Wearable electronic devices and technologies - Part 801-2: Smart body area network (SmartBAN) - Low complexity medium access control (MAC) for SmartBAN". This standard covers: Wearable electronic devices and technologies - Part 801-2: Smart body area network (SmartBAN) - Low complexity medium access control (MAC) for SmartBAN
Wearable electronic devices and technologies - Part 801-2: Smart body area network (SmartBAN) - Low complexity medium access control (MAC) for SmartBAN
prEN IEC 63203-801-2:2026 is classified under the following ICS (International Classification for Standards) categories: 35.100.01 - Open systems interconnection in general; 35.240.80 - IT applications in health care technology. The ICS classification helps identify the subject area and facilitates finding related standards.
prEN IEC 63203-801-2:2026 has the following relationships with other standards: It is inter standard links to EN IEC 63203-801-2:2022. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
prEN IEC 63203-801-2:2026 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-september-2026
Nosljive elektronske naprave in tehnologije - 801-2. del: Pametno telesno omrežje
(SmartBAN) - Manj zahteven nadzor dostopa do medija (MAC) za SmartBAN
Wearable electronic devices and technologies - Part 801-2: Smart body area network
(SmartBAN) - Low complexity medium access control (MAC) for SmartBAN
Tragbare elektronische Geräte und Technologien -Teil 801-2: Smartes am Körper
getragenes Netzwerk (SmartBAN) - Medium Access Control (MAC) mit geringer
Komplexität für SmartBAN
Technologies et dispositifs électroniques prêts-à-porter - Partie 801-2: Smart body area
network (SmartBAN) - Contrôle d’accès au support (MAC) à faible complexité pour
SmartBAN
Ta slovenski standard je istoveten z: prEN IEC 63203-801-2:2026
ICS:
31.080.99 Drugi polprevodniški elementi Other semiconductor devices
35.110 Omreževanje Networking
59.080.80 Inteligentne tekstilije Smart textiles
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
124/388/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 63203-801-2 ED2
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2026-06-19 2026-09-11
SUPERSEDES DOCUMENTS:
124/267/RR
IEC TC 124 : WEARABLE ELECTRONIC DEVICES AND TECHNOLOGIES
SECRETARIAT: SECRETARY:
Korea, Republic of Mr Jae Yeong Park
OF INTEREST TO THE FOLLOWING COMMITTEES: HORIZONTAL FUNCTION(S):
TC 100,SyC AAL,SEG 8
ASPECTS CONCERNED:
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft
for Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some
Countries” clauses to be included should this proposal proceed. Recipients are reminded that the CDV stage is
the final stage for submitting ISC clauses. (SEE AC/22/2007 OR NEW GUIDANCE DOC).
TITLE:
Wearable electronic devices and technologies - Part 801-2: Smart body area network
(SmartBAN) - Low complexity medium access control (MAC) for SmartBAN
PROPOSED STABILITY DATE: 2031
NOTE FROM TC/SC OFFICERS:
In accordance with Decision #3 of 124/351/DL, TC 124 agreed to proceed the project to CDV stage if
there is no additional critical comments after 4-week review.
download this electronic file, to make a copy and to print out the content for the sole purpose of preparing National
Committee positions. You may not copy or "mirror" the file or printed version of the document, o r any part of it, for
any other purpose without permission in writing from IEC.
IEC CDV 63203-801-2 ED2 © IEC 2026
1 CONTENTS
3 FOREWORD . 5
4 INTRODUCTION . 7
5 1 Scope . 8
6 2 Normative references . 8
7 3 Terms and definitions . 8
8 4 Abbreviated terms . 9
9 5 General MAC framework . 10
10 5.1 Different device types . 10
11 5.2 Frequency spectrum . 11
12 5.3 Channel format . 11
13 5.3.1 Control channel format . 11
14 5.3.2 Data channel format . 11
15 5.4 User priorities . 14
16 5.5 Node ID . 14
17 5.6 IU . 14
18 6 Frame formats . 15
19 6.1 MAC general frame format . 15
20 6.1.1 General description . 15
21 6.1.2 MAC header . 16
22 6.1.3 MAC frame body . 18
23 6.1.4 Frame parity . 19
24 6.2 Management frames . 19
25 6.2.1 C-Beacon . 19
26 6.2.2 D-Beacon . 21
27 6.2.3 C-Req . 23
28 6.2.4 C-Ass . 25
29 6.2.5 S-Ras . 28
30 6.2.6 D-Req . 28
31 6.2.7 D-Res . 28
32 6.3 C-Frame . 29
33 6.3.1 ACK/NACK . 29
34 6.4 D-Frame . 29
35 7 MAC functions . 29
36 7.1 General . 29
37 7.2 SmartBAN creation and connection initialization . 29
38 7.2.1 SmartBAN creation . 29
39 7.2.2 Connection initialization . 29
40 7.3 Channel access . 30
41 7.3.1 Scheduled channel access . 30
42 7.3.2 Slotted aloha channel access . 31
43 7.3.3 Multi-use channel access . 32
44 7.4 Supplementary downlink data transmission . 34
45 7.5 Slot reassignment . 34
IEC CDV 63203-801-2 ED2 © IEC 2026
46 7.6 Data channel migration . 36
47 8 MAC parameters. 36
48 Annex A (informative) Multi-use channel access . 37
49 Bibliography . 38
50 ___________ . 38
52 Figure 1 – SmartBAN topology . 10
53 Figure 2 – Structure of Control Channel . 11
54 Figure 3 – Access periods in Data Channel . 12
55 Figure 4 – Scheduled access slot structure . 12
56 Figure 5 – Control and management slot structure . 13
57 Figure 6 – Multi-use access slot structure . 13
58 Figure 7 – Structure of an IU . 15
59 Figure 8 – MAC general frame format . 15
60 Figure 9 – MAC header format . 16
61 Figure 10 – Frame control format . 16
62 Figure 11 – C-Beacon frame format . 19
63 Figure 12 – D-Beacon frame format . 21
64 Figure 13 – C-Req frame format . 23
65 Figure 14 – C-Ass frame format . 26
66 Figure 15 – D-Req frame structure (hub to node) . 29
67 Figure 16 – Connection procedure . 30
68 Figure 17 – Scheduled channel access . 30
69 Figure 18 – Downlink data transmission illustration . 34
70 Figure 19 – Slot reassignment illustration . 35
71 Figure 20 – Scheduled period slot reassignment procedure . 35
72 Figure 21 – Example of data channel migration (from #1 to #3) . 36
73 Figure A.1 – Flowchart of multi-use channel access . 37
75 Table 1 – Values of T . 13
MUA
76 Table 2 – List of user priorities . 14
77 Table 3 – Contention probabilities for different user priorities . 14
78 Table 4 – Node ID table . 14
79 Table 5 – Element ID for different operations . 15
80 Table 6 – Frame Type and Frame Subtype fields . 16
81 Table 7 – Table of IDs . 18
82 Table 8 – Slot Length field encoding . 20
83 Table 9 – Bit values for the Duty Cycling field . 20
84 Table 10 – Mapping of PHY Capability field . 24
85 Table 11 – IM field for allocation request IU . 25
86 Table 12 – IM field for allocation assignment IU . 27
87 Table 13 – IM field for S-Ras IU . 28
IEC CDV 63203-801-2 ED2 © IEC 2026
88 Table 14 – The MAC parameters . 36
IEC CDV 63203-801-2 ED2 © IEC 2026
91 INTERNATIONAL ELECTROTECHNICAL COMMISSION
92 ____________
94 WEARABLE ELECTRONIC DEVICES AND TECHNOLOGIES –
96 Part 801-2: Smart body area network (SmartBAN) –
97 Low complexity medium access control (MAC) for SmartBAN
99 FOREWORD
100 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
101 all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
102 co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
103 in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
104 Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
105 preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
106 may participate in this preparatory work. International, governmental and non-governmental organizations liaising
107 with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
108 Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
109 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
110 consensus of opinion on the relevant subjects since each technical committee has representation from all
111 interested IEC National Committees.
112 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
113 Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
114 Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
115 misinterpretation by any end user.
116 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
117 transparently to the maximum extent possible in their national and regional publications. Any divergence between
118 any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
119 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
120 assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
121 services carried out by independent certification bodies.
122 6) All users should ensure that they have the latest edition of this publication.
123 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
124 members of its technical committees and IEC National Committees for any personal injury, property damage or
125 other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
126 expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
127 Publications.
128 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
129 indispensable for the correct application of this publication.
130 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent
131 rights. IEC shall not be held responsible for identifying any or all such patent rights.
132 IEC 63203-801-2 has been prepared by IEC technical committee 124: Wearable electronic
133 devices and technologies. It is an International Standard.
134 The text of this International Standard is based on the following documents:
Draft Report on voting
124/XX/FDIS 124/XX/RVD
136 Full information on the voting for its approval can be found in the report on voting indicated in
137 the above table.
138 The language used for the development of this International Standard is English [change
139 language if necessary].
140 This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
141 accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
IEC CDV 63203-801-2 ED2 © IEC 2026
142 at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
143 described in greater detail at www.iec.ch/standardsdev/publications.
144 A list of all parts in the IEC 63203 series, published under the general title Wearable electronic
145 devices and technologies, can be found on the IEC website.
146 The committee has decided that the contents of this document will remain unchanged until the
147 stability date indicated on the IEC website under webstore.iec.ch in the data related to the
148 specific document. At this date, the document will be
149 • reconfirmed,
150 • withdrawn,
151 • replaced by a revised edition, or
152 • amended.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.
IEC CDV 63203-801-2 ED2 © IEC 2026
156 INTRODUCTION
157 TC124 is developing International Standards (IS) for body area network (BAN) to define the
158 wireless connectivity between the hub coordinator and the sensing nodes. The IEC 63203-801
159 series consists of the following sub-parts, under the general part title “Smart body area network
160 (SmartBAN)”:
161 IEC 63203-801-1: Enhanced ultra-low power physical layer
162 IEC 63203-810-2: Low complexity medium access control (MAC) for SmartBAN
163 The document describes the medium access control (MAC) specifications including channel
164 structure, MAC frame formats and MAC functions.
165 This document originates from the corresponding technical specification (TS 103 325)
166 standardized in the European Telecommunication Standard Institute (ETSI) and captures the
167 results the work of IEC TC 124 Working Group 4 on devices and systems. The current document
168 reflects contributions and discussions by IEC TC 124 experts, mirror committees, liaison
169 members and Joint Advisory Group (JAG) between IEC SyC. AAL, IEC TC 100 and IEC TC 124.
170 This document contains material gathered from reports and group output from the IEC TC 124
171 meetings in May 2018 (Manchester), October 2018 (Busan), May 2019 (San Francisco),
172 September 2019 (Shanghai), November 2020 (online) as well as information obtained during
173 various web meetings.
174 Experts from the following national committees, liaison organizations have contributed: BE, CN,
175 DE, FI, FR, GB, IN, JP, KR, MY, NL, US and ETSI TC SmartBAN.
176 This document is also positioned as a result of the activities of the JAG. At the IEC General
177 Meeting in Busan in 2018, three committees related to wearable systems and technologies,
178 SyC. AAL, IEC TC 100 and IEC TC 124 had a joint workshop and agreed to collaborate to
179 develop relevant standards and to share roles. This collaboration agreement was advanced to
180 a Joint Advisory Group (JAG) and the JAG was established managed by SyC. AAL in 2019.
181 The target audience for this document includes the following stakeholders who have an interest
182 in the systems and services using wearable devices:
183 • consumer electronics (CE) and information communications technology (ICT) device
184 manufacturers;
185 • system integrators who want to utilize wearable device and technologies;
186 • service operators who are interested in the AAL systems and services ;
187 • stakeholders who want to understand the technologies and requirements for wireless
188 connectivity between wearable sensor nodes and hub coordinators.
IEC CDV 63203-801-2 ED2 © IEC 2026
191 WEARABLE ELECTRONIC DEVICES AND TECHNOLOGIES –
193 Part 801-2: Smart body area network (SmartBAN) –
194 Low complexity medium access control (MAC) for SmartBAN
198 1 Scope
199 This document specifies low complexity medium access control (MAC) for SmartBAN.
200 As the use of wearables and connected body sensor devices grows rapidly in the Internet of
201 Things (IoT), wireless body area networks (BAN) facilitate the sharing of data in smart
202 environments such as smart homes, smart life etc. In specific areas of digital healthcare,
203 wireless connectivity between the edge computing device or hub coordinator and the sensing
204 nodes requires a standardized communication interface and protocols.
205 The present document describes the following MAC specifications:
206 – channel structure;
207 – MAC frame formats;
208 – MAC functions.
209 2 Normative references
210 The following documents are referred to in the text in such a way that some or all of their content
211 constitutes requirements of this document. For dated references, only the edition cited applies.
212 For undated references, the latest edition of the referenced document (including any
213 amendments) applies.
214 IEC 63203-801-1:2022, Smart body area networks (SmartBAN) – Part 1: Enhanced ultra-low
215 power physical layer
216 3 Terms and definitions
217 For the purposes of this document, the following terms and definitions apply.
218 ISO and IEC maintain terminological databases for use in standardization at the following
219 addresses:
220 • IEC Electropedia: available at http://www.electropedia.org/
221 • ISO Online browsing platform: available at http://www.iso.org/obp
222 3.1
223 beacon
224 frame transmitted by a hub to facilitate network management, such as the coordination of
225 medium access and power management of the nodes in the SmartBAN, and to facilitate clock
226 synchronizationwith the hub
227 3.2
228 beacon period
229 duration during which a beacon is transmitted
230 3.3
231 downlink
232 communication link for transfer of management and data traffic from a hub to a node
IEC CDV 63203-801-2 ED2 © IEC 2026
233 3.4
234 hub
235 entity that possesses a node’s functionality and coordinates the medium access and power
236 management of the nodes in the SmartBAN
237 3.5
238 inactive period
239 period in time following an active transmission sequence during which the equipment does not
240 transmit or receive
241 3.6
242 node
243 any entity conforming to the SmartBAN medium access control and physical interface to the
244 wireless medium
245 3.7
246 priority channel access
247 highest priority access during multi-use channel access
248 3.8
249 re-use channel access
250 priority access during multi-use channel access which enables re-use of scheduled but non-
251 utilised slots
252 3.9
253 scheduled access
254 one or more scheduled recurring time intervals that a node and a hub obtain using scheduled
255 access to initiate frame transactions
256 Note 1 to entry: A scheduled allocation is an uplink allocation, a downlink allocation suitable for servicing high or
257 low duty cycle periodic or quasi-periodic traffic on a committed schedule.
258 3.10
259 uplink
260 communication link for transfer of management and data traffic from a node to a hub
261 4 Abbreviated terms
ACK Acknowledgement
BAN Body area network
C-Ass Connection assignment
C-Beacon Control channel BeaconC-frame
(control frame)
CRC Cyclic redundancy check
C-Req Connection request
D/SR Downlink/slot reassignment
D-Beacon Data channel beacon
D-Frame Data frame
D-Req Disconnection request
D-Res Disconnection response
TM
EUI-48 Extended Unique Identifier-48 bits
FCS Frame check sequence
FEC Forward error correction
IFS Inter-frame spacing
IEC CDV 63203-801-2 ED2 © IEC 2026
IM Information module
ISM Industrial, scientific and medical
IU Information unit
MAC Medium access control
NACK Negative acknowledgement
NID Node ID
PHY Physical layer
REP Repetition coding
Rx Receive
S-Ras Slot reassignment
Tx Transmit
UL Uplink
264 5 General MAC framework
265 5.1 Different device types
266 Clause 5 provides the basic MAC framework for the nodes and hubs.
267 Two different device types can participate in SmartBAN:
268 1) sensor device (node); and
269 2) coordinator device (hub).
270 A hub is a device that acts as a SmartBAN coordinator. A node is any device that acts as an
271 information source or an information sink. One hub and at least one node constitute a SmartBAN.
272 A SmartBAN shall be organized into a star topology illustrated in Figure 1. It shall consist of at
273 least one node communicating directly with the hub.
276 Figure 1 – SmartBAN topology
277 The hub and nodes shall communicate using communication media known as channels. A
278 SmartBAN shall use two different channel entities to enable communication between the hub
279 and nodes. The channel entities are assigned the following names:
280 – Data Channel
IEC CDV 63203-801-2 ED2 © IEC 2026
281 – Control Channel
282 Each SmartBAN shall utilise one Control Channel and one Data Channel at any one time.
283 5.2 Frequency spectrum
284 The frequency of operation shall fall between 2 401 MHz and 2 481 MHz. The channels shall
285 be arranged in blocks of 2 MHz with centre frequencies as follows:
286 f = 2 402 + 2 × n MHz, where n = 0 to 39.
c
287 The channels are categorised into data and Control Channels with:
288 • 3 Control Channels, where control frames (in the form of C-Beacon) from the hub are
289 transmitted;
290 • 37 Data Channels, where data, control, and management frames are transmitted.
291 The list of channels can be found in Clause 5 of IEC 63203-801-1.
292 5.3 Channel format
293 5.3.1 Control channel format
294 Only hub devices shall transmit on Control Channels shown in Figure 2. A hub shall select one
295 Control Channel from the list of Control Channels in IEC 63203-801-1:2022, Table 1 and
296 transmit one control beacon frame (C-Beacon) on the chosen Control Channel every T s. The
C
297 format of the C-Beacon is set out in 6.2.1.
300 Figure 2 – Structure of Control Channel
301 5.3.2 Data channel format
302 5.3.2.1 Data channel description
303 Both hub and node devices may transmit on the Data Channels. A hub shall select one Data
304 Channel from the list of Data Channels in IEC 63203-801-1:2022, Table 1, on which both hub
305 and node devices in the associated SmartBAN may transmit. Data Channel format is illustrated
306 in Figure 3. For any SmartBAN, the Data Channel is partitioned into time intervals of T s,
D
307 known as the Inter-beacon Interval. The boundaries of each Inter-beacon Interval shall be
308 marked by the transmission of a Data Channel Beacon (D-Beacon). A hub shall transmit a D-
309 Beacon at the beginning of each Inter-beacon Interval.
310 Each Inter-beacon Interval shall be partitioned into L distinct time epochs known as slots. The
D
311 duration of each time slot is T . The duration of each Inter-beacon Interval shall be (L × T ) s.
S D S
312 Any device transmitting in a time slot shall ensure that the transmission takes place within the
313 duration of that time slot.
314 Each Inter-beacon Interval shall consist of four distinct periods:
315 1) Beacon Period, consisting of one single time slot, where the D-Beacon frame shall be
316 transmitted by the hub. No nodes shall transmit in this period;
317 2) Scheduled Period, consisting of N time slots, where scheduled transmissions and
S
318 acknowledgements occur;
IEC CDV 63203-801-2 ED2 © IEC 2026
319 3) Control and Management Period, consisting of N time slots, where unscheduled access,
CM
320 and management and control signaling occur;
321 4) Inactive Period, where no transmission occurs.
322 The time slots shall be identified by a 10-bit sequence denoting the position of the time slot in
323 an Inter-beacon Interval. The Beacon Period, consisting of 1 time slot shall have the sequence
324 number 0000000000. Subsequent time slots shall have sequence numbers incremented by the
325 number of time slots following the Beacon Period.
328 Figure 3 – Access periods in Data Channel
329 The Scheduled Access Period shall begin on the slot boundary immediately following the
330 Beacon. The Scheduled Access Period may be of zero length, in which case, the Control and
331 Management Period shall begin immediately following the Beacon Period. The Control and
332 Management Period shall begin on the slot boundary immediately following the Scheduled
333 Access Period. The Inactive Period shall begin on the slot boundary immediately following the
334 Control and Management Period.
335 Three types of channel access mechanisms can be used in the access periods:
336 – Scheduled Channel Access, in the Scheduled Access Period;
337 – Slotted Aloha Channel Access, in the Control and Management Period;
338 – Multi-use Channel Access, in both Scheduled Access and Control and Management Period.
339 The hub and nodes shall always support Scheduled Channel Access and Slotted Aloha Channel
340 Acces, and may support Multi-use Channel Access. Multi-use Channel Access may only be
341 used when every node in the SmartBAN supports it. Each channel access mechanism shall
342 adhere to its respective slot structure as described in 5.3.2.2.
343 5.3.2.2 Scheduled access slot structure
346 Figure 4 – Scheduled access slot structure
347 The Scheduled Access time slots shall follow the structure as illustrated in Figure 4. Any
348 Scheduled Access time slots allocated by the hub shall be in the Scheduled Access Period.
349 The Scheduled Access slot shall consist of at most two transmission periods:
350 1) D-Frame Transmission: the device allocated to the time slot shall transmit;
351 2) ACK Frame Transmission: If the ACK policy of the received frame defined in 6.1.2.2.3 is ‘0’
352 and the transmission is successful, the receiving device shall transmit an Acknowledgement
353 Frame. If the ACK policy is ‘1’ and the transmission is not successful, the receiving device
354 shall transmit a NACK Frame. The ACK Frame Transmission period shall commence one
IEC CDV 63203-801-2 ED2 © IEC 2026
355 IFS after the end of the Data Transmission period and end at least one IFS before the end
356 of the time slot.
357 5.3.2.3 Control and management slot structure
360 Figure 5 – Control and management slot structure
361 The Control and Management time slots shall follow the structure as illustrated in Figure 5.
362 The Control and Management slot shall consist of two transmission periods:
363 1) Data/Management Frame Transmission: any device wishing to transmit either data or
364 management frames may transmit;
365 2) ACK Frame Transmission: If the ACK policy of the received frame defined in clause 6.1.2.2.3
366 is ‘0’ and the transmission is successful, the receiving device shall transmit an
367 Acknowledgement Frame. If the ACK policy is ‘1’ and the transmission is not successful, the
368 receiving device shall transmit a NACK Frame. The ACK Frame Transmission period shall
369 commence one IFS after the end of the Data Transmission period and end at least one IFS
370 before the end of the time slot.
371 5.3.2.4 Multi-use access slot structure
374 Figure 6 – Multi-use access slot structure
375 The Multi-use Access time slots shall follow the structure as illustrated in Figure 6. The Multi-
376 use Access time slots shall be used when Multi-use Access is in operation.
377 The Multi-use Access slot shall consist of one sensing period, and at most two transmission
378 periods:
379 – Sensing: the sensing period, T , shall depend on the traffic type. The values of T are
MUA MUA
380 defined in Table 1, where T is the minimum sensing period as defined in Clause 8. Any
sch
381 device wishing to transmit should sense the channel for a period of T . If the channel is
MUA
382 busy, the device should wait for the next available Multi-use Access time before another
383 attempt is made. If the channel is found to be idle, the device may commence data
384 transmission.
385 – D-Frame Transmission: any device that has sensed the channel for the sensing period
386 above may transmit if the channel is found to be idle.
387 – Acknowledgement period: the receiving device may transmit an Acknowledgement frame if
388 the transmission is successful, depending on the acknowledgement policy.
389 Table 1 – Values of T
MUA
Type of user Type of traffic Access period T
MUA
Any user Very high priority traffic (User priority 3) Scheduled Access 0
IEC CDV 63203-801-2 ED2 © IEC 2026
Slot owner Any traffic Scheduled Access T
sch
Non-slot owner Any traffic Scheduled Access 2 × T
sch
Any user Very high priority traffic (User priority 3) Control & Management Access 0
Any user Any traffic Control & Management Access T
sch
391 5.4 User priorities
392 Four user priority levels shall be defined in the operation of a SmartBAN. The user priorities are
393 defined in Table 2. The user priority shall determine the contention probability of the node in
394 Slotted Aloha Channel Access. The range of contention probabilities for different user priority
395 levels is listed in Table 3.
396 Table 2 – List of user priorities
User priority Data type
0 Low priority
1 Mid priority
2 High priority
3 Very high priority
398 Table 3 – Contention probabilities for different user priorities
User priority Contention probability
CP CP
max min
0 1/8 1/16
1 1/4 1/16
2 1/2 1/8
3 1 1/2
400 5.5 Node ID
401 The Node ID of devices in a SmartBAN shall be assigned according to Table 4.
402 Table 4 – Node ID table
NID value NID NID notation NID usage
subtotal
00000000 1 Unconnected NID For unicast from/to unconnected nodes in a BAN
00000001- 16 Connected NID For unicast from/to connected nodes in a BAN
00010101 1 Hub NID For hubs
11111111 1 Broadcast NID For broadcast to all nodes
404 5.6 IU
405 IUs encapsulate the required information for specific operations. Operations requiring IUs shall
406 use the appropriate Element ID listed in Table 5. An IU shall be formatted as in Figure 7.
IEC CDV 63203-801-2 ED2 © IEC 2026
409 Figure 7 – Structure of an IU
410 An IU comprises an Element ID field, a Length field, and multiple Information Module (IM) fields.
411 The Element ID field denotes the type of operation the IU is used for. The field shall be set
412 according to Table 5.
413 The Length field denotes the number of IM fields the IU has. Each IU can have up to 32 IM
414 fields.
415 The Information Module field is operation specific and has a length of L .
IM
416 Table 5 – Element ID for different operations
Element ID Operation Description
000 Uplink request Specifies uplink requirements for scheduled uplink transmissions
001 Downlink request Specifies downlink requirements for scheduled downlink
transmissions
010 Uplink assignment Specifies uplink assignment parameters for scheduled
transmissions
011 Downlink request Specifies downlink assignment parameters for scheduled
assignment transmissions
100 Uplink slot reassignment Specifies new slot allocations in the Scheduled Access Period
for different nodes in the uplink
101 Downlink slot Specifies new slot allocations in the Scheduled Access Period
reassignment for different nodes in the downlink
418 6 Frame formats
419 6.1 MAC general frame format
420 6.1.1 General description
421 All MAC frames shall be formed by concatenation of a MAC Header of 56 bits, a MAC Frame
422 Body of L bits, and a Frame Parity of 16 bits as shown in Figure 8. The MAC Frame Body has
F
423 a length of L bits and is present only if it has a nonzero length. The MAC frame shall also be
F
424 called the MPDU.
Bits: 16
56 L
F
MAC Frame Frame
MAC
Body Parity
Header
MPDU
428 Figure 8 – MAC general frame format
IEC CDV 63203-801-2 ED2 © IEC 2026
429 6.1.2 MAC header
430 6.1.2.1 MAC header format
431 Figure 9 illustrates the MAC header format. The MAC header shall consist of:
432 • a Frame Control field,
433 • a Recipient ID field,
434 • a Sender ID field,
435 • a BAN ID field, and
436 • an FCS.
439 Figure 9 – MAC header format
440 6.1.2.2 Frame control
441 6.1.2.2.1 Frame control format
442 The 24-bit Frame Control field shall be formatted as shown in Figure 10.
445 Figure 10 – Frame control format
446 6.1.2.2.2 Protocol version
447 The Protocol Version field is set to ‘000’. All other values are reserved.
448 6.1.2.2.3 ACK policy
449 The ACK Policy field indicates the acknowledgement type used by the current frame. The field
450 is set to ‘0’ to indicate that an ACK frame shall be sent when a transmission is successful. The
451 field is set to ‘1’ to indicate that no ACK frames shall be sent when a transmission is successful,
452 but a NACK shall be sent when a transmission is unsuccessful. When NID is set to ‘11111111’
453 (Broadcast), ACK policy is not applied.
454 6.1.2.2.4 Frame type
455 The Frame Type field is set to indicate the type of the current frame. The three defined Frame
456 Types are: Management, Control, and Data. The Frame Subtype and Frame Type are given in
457 Table 6.
458 Table 6 – Frame Type and Frame Subtype fields
Field value Frame Type Field value Frame Subtype
00 Management 000 Beacon
00 Management 001 Connection Request
00 Management 010 Connection Assignment
IEC CDV 63203-801-2 ED2 © IEC 2026
Field value Frame Type Field value Frame Subtype
00 Management 011 Slot Reassignment
00 Management 100 Disconnection Request
00 Management 101 Disconnection Response
00 Management 110 Inter HUB
00 Management 111 Reserved
01 Control 000 ACK
01 Control 001 NACK
10 Data 000 User Priority 0
10 Data 001 User Priority 1
10 Data 010 User Priority 2
10 Data 011 User Priority 3
10 Data 100 Inter HUB
11 Reserved 101-111 Reserved
460 6.1.2.2.5 Frame subtype
461 The Frame Subtype field shall be set as defined in Table 6.
462 6.1.2.2.6 Sequence number
463 The Sequence Number field specifies the sequence identifier of the frame.
464 The Sequence Number is applicable for both beacon and data frames. The values of Sequence
465 Number field are set as follows:
466 – The field is set to zero if the frame is the first data type frame of this frame subtype to a
467 recipient.
468 – The field is incremented by one, modulo 256, from its value in the frame that was the same
469 frame type of this frame subtype and addressed to a recipient.
470 – For data type frames, the field is kept with the same value if frames contain fragments of
471 the same MAC Frame Body or are being retransmitted to the same recipient.
472 6.1.2.2.7 Fragment number
473 The 3-bit Fragment Number field is applicable for the data type frames. The values of Fragment
474 Number are set as follows:
475 – The Fragment Number field is set to zero if the current frame contains no MAC Frame Body,
476 a MAC Frame Body not fragmented, or the first fragment of a fragmented MAC Frame Body.
477 – The value of the field is incremented by one from its value in the frame containing the
478 previous fragment of the MAC Frame Body if the current frame contains a non-first fragment
479 of a fragmented MAC Frame Body or is kept with the same value if the frame is being
480 retransmitted to the same recipient.
481 In all other frames, it is reserved.
482 6.1.2.2.8 Non-final fragment
483 The 1-bit Non-final Fragment field is only applicable to data type frames.
484 The Non-final Fragment field is set as follows:
485 – to 0 (zero) if the current frame contains no MAC Frame Body, a MAC Frame Body not
486 fragmented, or the final fragment of a fragmented MAC Frame Body; or
487 – to 1 (one) if the frame contains a non-final fragment of a fragmented MAC Frame Body.
488 In all other frames, it is reserved.
IEC CDV 63203-801-2 ED2 © IEC 2026
489 6.1.2.2.9 Command acknowledgement
490 The 1-bit Command Acknowledgement field shall be set as follows:
491 – to 1 (one) if the node acknowledges that the node has received the slot reassignment or
492 downlink data request command from the hub;
493 – to 0 (zero) otherwise.
494 6.1.2.3 Recipient ID
495 The Recipient ID is an 8-bit ID identifying the recipient of the frame, assigned previously by the
496 hub according to Table 4. The specific recipient ID of each frame is defined in Table 7.
497 6.1.2.4 Sender ID
498 The Sender ID is an 8-bit sequence identifying the sender of the frame. The specific sender ID
499 of each frame is defined in Table 7.
500 6.1.2.5 BAN ID
501 The BAN ID is an 8-bit abbreviated address identifying the SmartBAN of the sender and
502 recipient. The specific BAN ID of each frame is defined in
...



