IEC 63430:2025

IEC 63430 ®
Edition 1.0 2025-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Data container format for wearable sensor

Conteneur de données pour capteur prêt-à-porter

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 Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
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 IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews, graphical symbols and the glossary.
committee, …). It also gives information on projects, replaced With a subscription you will always have access to up to date
and withdrawn publications. content tailored to your needs.

IEC Just Published - webstore.iec.ch/justpublished
Electropedia - www.electropedia.org
Stay up to date on all new IEC publications. Just Published
The world's leading online dictionary on electrotechnology,
details all new publications released. Available online and once
containing more than 22 500 terminological entries in English
a month by email.
and French, with equivalent terms in 25 additional languages.

Also known as the International Electrotechnical Vocabulary
IEC Customer Service Centre - webstore.iec.ch/csc
(IEV) online.
If you wish to give us your feedback on this publication or need

further assistance, please contact the Customer Service
Centre: sales@iec.ch.
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 -  IEC Products & Services Portal - products.iec.ch
webstore.iec.ch/advsearchform Découvrez notre puissant moteur de recherche et consultez
La recherche avancée permet de trouver des publications IEC gratuitement tous les aperçus des publications, symboles
en utilisant différents critères (numéro de référence, texte, graphiques et le glossaire. Avec un abonnement, vous aurez
comité d’études, …). Elle donne aussi des informations sur les toujours accès à un contenu à jour adapté à vos besoins.
projets et les publications remplacées ou retirées.

Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
Le premier dictionnaire d'électrotechnologie en ligne au monde,
Restez informé sur les nouvelles publications IEC. Just
avec plus de 22 500 articles terminologiques en anglais et en
Published détaille les nouvelles publications parues.
français, ainsi que les termes équivalents dans 25 langues
Disponible en ligne et une fois par mois par email.
additionnelles. Egalement appelé Vocabulaire

Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC 63430 ®
Edition 1.0 2025-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Data container format for wearable sensor

Conteneur de données pour capteur prêt-à-porter

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 35.240.50, 59.080.80 ISBN 978-2-8327-0181-2

– 2 – IEC 63430:2025 © IEC 2025
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Abbreviated terms . 8
5 System structure . 8
5.1 System overview . 8
5.2 Composition of Container format in edge computing device . 9
5.2.1 General description . 9
5.2.2 Container composer . 10
5.2.3 Supplementary processor . 10
5.2.4 Output coordinator . 11
6 Container format . 11
6.1 General description . 11
6.2 Header format . 11
6.2.1 Structure of Header format . 11
6.2.2 Container type . 12
6.2.3 Container Length . 12
6.2.4 Data ID Type . 13
6.2.5 Data ID Length . 13
6.2.6 Data ID . 13
6.2.7 Extended Header Length . 13
6.2.8 Attribute Type . 13
6.2.9 Attribute Length . 13
6.2.10 Attribute Value . 14
7 Schema Repository . 14
7.1 General description . 14
7.2 Schema Information . 14
7.2.1 Syntax of Schema Information . 14
7.2.2 dataIdType . 16
7.2.3 dataId . 16
7.2.4 Fields . 16
7.2.5 Class . 16
8 Communications and interface requirements . 19
8.1 Communication between edge computing device, IoT platform and Schema
Repository . 19
8.2 Interface requirements for sensor . 19
8.3 Security requirements . 20
8.3.1 General description . 20
8.3.2 Wearable sensor . 20
8.3.3 Edge computing device . 20
8.3.4 IoT platform . 20
8.3.5 Schema Repository . 21
8.3.6 Container . 21
8.3.7 Communication channel . 21

Annex A (informative) Examples of Data ID Length . 22
A.1 General description . 22
A.2 Data ID Length . 22
A.2.1 UUID . 22
A.2.2 GTIN . 22
A.2.3 Bluetooth® . 22
A.2.4 Proprietary Data ID Type and Data ID Length . 22
Annex B (informative) Examples of interpretation between Schema Information and
Container payload . 23
B.1 General description . 23
B.2 Example 1: An expression using 'repeat' identifier. 23
B.3 Example 2: An expression using 'length' identifier . 24
Bibliography . 27

Figure 1 – System overview . 9
Figure 2 – Composition of Container format . 10
Figure 3 – Container structure . 11
Figure 4 – Header format for bit stream type of Container . 12
Figure 5 – Syntax of Schema Information . 15
Figure 6 – Number list . 18
Figure 7 – Examples of String . 18
Figure 8 – Examples of ContentType . 19
Figure 9 – Syntax of Property . 19
Figure B.1 – Example1: Container format and Schema Information . 23
Figure B.2 – Example1: Syntax of Schema Information . 24
Figure B.3 – Example2: Container format and Schema information . 25
Figure B.4 – Example 2: Syntax of Schema Information . 26

Table 1 – Container type . 12
Table 2 – Data ID Type . 13
Table 3 – Attribute list . 14
Table A.1 – Data ID Type and Data ID Length . 22

– 4 – IEC 63430:2025 © IEC 2025
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DATA CONTAINER FORMAT FOR WEARABLE SENSOR

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC 63430 has been prepared by Technical Area 18: Multimedia home systems and applications
for end-user networks, of IEC Technical Committee 100: Audio, video and multimedia systems
and equipment. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
100/4141/CDV 100/4178/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.

This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
– 6 – IEC 63430:2025 © IEC 2025
INTRODUCTION
The target audience for this document includes the following stakeholders who have an interest
in the systems and services using wearable devices:
• Consumer electronics (CE) and Information Communications Technology (ICT) device
manufacturers.
• System integrators who want to utilize wearable device and technologies.
• Service operators who are interested in the IoT and multimedia systems and services.
• Stakeholders who want to understand the technologies and requirements for wireless
connectivity between wearable sensor nodes and hub coordinator.

DATA CONTAINER FORMAT FOR WEARABLE SENSOR

1 Scope
This International Standard specifies a Container format for sensing data and its system
requirements. This document applies to edge computing devices such as smartphones, home
gateways, multimedia coordinators, etc., and cloud systems.
This document describes the following technical specifications:
• Container format for wearable sensor data,
• Schema Repository that defines the parameters and syntax of sensor data,
• Communication and system requirements between the edge computing device and Schema
Repository.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1
Container
data structure that encapsulates one or multiple numbers of digital data
Note 1 to entry: Each piece of digital data consists of various kinds of data such as sensor signals, audio signals,
video signals, metadata, programs, etc.
3.2
Schema Information
structural information that represents the data structure of a Container payload
3.3
Schema Repository
server that stores Schema Information

– 8 – IEC 63430:2025 © IEC 2025
4 Abbreviated terms
BAN Body area network
CRC Cyclic redundancy check
DoS Denial of Service
FEC Forward error correction
GTIN Global trade item number
IANA Internet assigned numbers authority
ID Identifier
IoT Internet of Things
MAC Medium access control
RS Reed Solomon
UUID Universal unique identifier
5 System structure
5.1 System overview
Sensing data detected by wearable sensors (e.g. vital sensors, environmental sensors, etc.) is
transmitted from wearable sensors to edge computing devices (e.g. wearable signal
1 2
aggregators, smartphones, etc.) through BAN (e.g. SmartBAN [1] ,[2]), Bluetooth® [3] and
other short range communications. Figure 1 shows a diagram in which (1) SmartBAN hub and
(2) Bluetooth® client are installed in one (3) edge computing device for convenience. In reality,
either (1) SmartBAN or (2) Bluetooth® client may be installed. The sensing data collected by
either wireless method is encapsulated into a Container as a function of the (3) edge computing
device. Then, the Container is transferred to an (4) IoT platform located in a cloud. When
formatting the data collected by (1) SmartBAN hub or (2) Bluetooth® client into a Container in
(3) edge computing device, the edge computing device can obtain the header configuration and
payload information on how to encapsulate the sensing data into the Container from (5) Schema
Repository if the edge computing device does not have any pre-set header configuration nor
payload information for the above-mentioned wearable sensors.
___________
Unless otherwise specified in the text of this document, the numbers in square brackets refer to the Bibliography.
Bluetooth is the trademark of a product supplied by Bluetooth SIG, Inc. This information is given for the
convenience of users of this document and does not constitute an endorsement by IEC of the product named.
Equivalent products may be used if they can be shown to lead to the same results.

Figure 1 – System overview
5.2 Composition of Container format in edge computing device
5.2.1 General description
Figure 2 illustrates the composition of the Container format in an edge computing device.

– 10 – IEC 63430:2025 © IEC 2025

Figure 2 – Composition of Container format
5.2.2 Container composer
The Container composer encapsulates the sensor data received from the sensor device into a
Container as a payload and outputs it. When the Container composer receives the sensor data,
the Container composer adds the attribute information to the received sensor data to form a
Container.
5.2.3 Supplementary processor
The Supplementary processor performs calculations and processing on the Container output
from the Container composer. For example, the Supplementary processor can take a Container
as an input and can output the result of performing an operation on the header and payload
included in the Container as a new Container. Another example is that the Supplementary
processor may calculate an average value or a maximum value of sensor data to respond to
query operations. Further, the Supplementary processor may apply a window function or a filter
based on the time or the number of data to the sensor data, and periodically aggregate the
sensor data.
The Schema Repository stores and provides information necessary for interpreting Container
data. The Schema Repository stores several units of Schema Information containing an
attribute type for the header parameter and data type and sequence order described in the
payload. The Schema Information is stored in a local file or in a location on the network that
can be referenced by the Supplementary processor.
Upon receiving the input of the Container, the Supplementary processor divides the input
Container data into a header area and a payload area. Subsequently, the Supplementary
processor retrieves the Schema Information from the Schema Repository and applies the
example given in this Subclause 5.2.3 on the supplementary processing on the Attribute Value
stored in the header area and the value stored in the payload area.

5.2.4 Output coordinator
The Output coordinator receives the Container generated by Container composer or the
Container to which the operation by Supplementary processor is applied. The Output
coordinator stores the received Container and encapsulates it into a communication format
suitable for the output destination (e.g. TCP), and then outputs it to the subsequent
computational resources.
6 Container format
6.1 General description
The Container shall be formed by concatenation of a Container Header and a Container Payload
as shown in Figure 3. The Container shall consist of a L Byte header and L Byte payload.
hd pl
The Length of payload shall be longer than or equal to zero Byte. In this Clause 6, big endian
is applied for describing data.

Figure 3 – Container structure
6.2 Header format
6.2.1 Structure of Header format
Figure 4 illustrates the Header format for a Container. The common part of Container Header
shall consist of:
• a Container Type field,
• a Container Length field,
• a Data ID Type field,
• a Data ID Length field and
• a Data ID field.
– 12 – IEC 63430:2025 © IEC 2025
The extended part of Container Header shall consist of:
• an Extended Header Length field and
• one or many numbers of Attribute Type fields, Attribute Length fields and Attribute Value
fields.
Figure 4 – Header format for bit stream type of Container
6.2.2 Container Type
The 2 Byte Container Type field shall set one of the values in Table 1.
The Container Type field shall be set at one of the following: '0101010101010101',
'0011001100110011', '0110011001100110' or '0000111100001111' when the Container is
composed for streaming process. The Container Type field shall be set at one of the following:
'1010101010101010', '1100110011001100', '1001100110011001' or '1111000011110000' when
the Container is composed for non-streaming process, including storage.
Table 1 – Container Type
Streaming/Non-streaming Extended Unfragmented payload / End First / Middle of fragmented
Attributes of fragmented payload payload
(Yes/None)
Streaming process None 0101010101010101 0011001100110011
Yes 0110011001100110 0000111100001111
Non-streaming process None 1010101010101010 1100110011001100
Yes 1001100110011001 1111000011110000

6.2.3 Container Length
The 2 Byte Container Length field shall indicate the Length of the entire Container from the
beginning of Container Type to the end of payload in bytes.

6.2.4 Data ID Type
The 1 Byte Data ID Type field shall indicate the type of Data ID as shown in Table 2.
Table 2 – Data ID Type
Field Value Type of Data ID
0x00 UUID
0x01 GTIN-8+Suffix
0x02 GTIN-12+Suffix
0x03 GTIN-13+Suffix
0x04 GTIN-14+Suffix
0x05 Bluetooth®
0x06 Proprietary
0x07-0xFF Reserved
6.2.5 Data ID Length
The 1 Byte Data ID Length field shall indicate the Length of the Data ID. Examples of Data ID
Length are described in Annex A.
6.2.6 Data ID
The L Byte Data ID field shall be set based on the Data ID Type shown in Table 2.
did
6.2.7 Extended Header Length
The 1 Byte Extended Header Length field shall indicate the entire Length of the extended part
of the header.
6.2.8 Attribute Type
The 1 Byte Attribute Type field shall indicate the Attribute Type number as shown in Table 3.
6.2.9 Attribute Length
The Attribute Length field shall indicate the Length of the Attribute Value as shown in Table 3.

– 14 – IEC 63430:2025 © IEC 2025
6.2.10 Attribute Value
The Attribute Value shall indicate the value of Attribute corresponding to the Attribute number
shown in Table 3.
Table 3 – Attribute list
Attribute Type Attribute Name Attribute Length Description
(Byte)
b0,b1,b2,b3,b4,b5 b5,b6,b7
00000 000 Version Number 1
001 Sequence Number 2
010 Payload Length 2
011-111 Reserved N/A
00001 000 Time Stamp 4 Unix Time

001-111 Reserved N/A
00010 000 FEC Parity 2 Shortened (255-h, 253-h) RS code
001 FEC Parity 4 Shortened (255-h, 251-h) RS code
010 FEC Parity 16 Shortened (255-h, 239-h) RS code
011 CRC 1 CRC-8
100 CRC 2 CRC-16
101-111 Reserved N/A
00011- 11111 000-111 Reserved N/A

7 Schema Repository
7.1 General description
The Schema Repository shall store and provide Schema Information that is defined as the
information necessary for interpreting a Container payload. The Schema Repository may store
a plurality of Schema Information. The location of the Schema Repository server shall be on
the network that can be referenced by Container Composer and Supplementary Processor.
Examples of interpretation between Schema Information and Container payload are described
in Annex B.
7.2 Schema Information
7.2.1 Syntax of Schema Information
Figure 5 shows the syntax of Scheme information expressed by ASN.1 [4]. The Container shall
be uniquely identified in the Schema Information by the Data ID. Schema Information shall be
structured information that parses the Container payload into a sequence of 'field'.

Figure 5 – Syntax of Schema Information

– 16 – IEC 63430:2025 © IEC 2025
The Schema Information shall consist of:
• a dataIdType,
• a dataId and
• a Fields.
7.2.2 dataIdType
dataIdType shall be in accordance with 6.2.4.
7.2.3 dataId
dataId shall be in accordance with 6.2.6.
7.2.4 Fields
7.2.4.1 General description
The identifier of 'Fields' shall be one or more identifiers of 'Field'. The identifier of 'Field' shall
consist of:
• an offset
• a fieldName and
should consist of
• a repeat.
7.2.4.2 offset
This identifier is an integer that shall indicate the distance from the beginning position of the
payload to the position where data starts to be read.
7.2.4.3 fieldName
This identifier is a universal String that shall indicate the name or kinds of data encapsulated in
the payload of the Container.
7.2.4.4 repeat
This identifier shall indicate the number of repetitions for the 'Field'.
7.2.5 Class
7.2.5.1 General description
This identifier shall consist of:
• a classId
• a type.
This identifier should consist of:
• a length,
• a content Type and
• a properties.
7.2.5.2 classId
This identifier is a universal string that shall indicate the name or kinds of data encapsulated in
the payload of the Container.
7.2.5.3 length
This identifier is an integer and may be omitted if any of the following conditions are met:
• when the end of the data sequence can be detected,
• when there is at most one data sequence whose length cannot be identified in the 'fields'
column of the schema.
7.2.5.4 type
7.2.5.4.1 General description
This identifier indicates the unit or type of the data sequence encapsulated in payload
information. This identifier shall contain a choice of one of the following:
• a byte,
• a number,
• a string and
• a fields.
7.2.5.4.2 byte
This identifier shall indicate the unit of Byte.
7.2.5.4.3 Number
This identifier shall indicate one of those listed in Figure 6. In the case of "multiByte", the
"endian" may be omitted when the endian is little.

– 18 – IEC 63430:2025 © IEC 2025

Figure 6 – Number list
7.2.5.4.4 string
This identifier shall indicate one of the encoding schemes listed by ISO/IEC 10646 [5]. Figure 7
shows examples of them.
Figure 7 – Examples of String
7.2.5.5 contentType
This identifier shall indicate one of the media types listed by IANA [6]. Figure 8 shows examples
of them.
Figure 8 – Examples of ContentType
7.2.5.6 Property
This identifier shall consist of:
• a propertyName and
• a propertyValue.
Figure 9 shows the syntax of Property.

Figure 9 – Syntax of Property
8 Communications and interface requirements
8.1 Communication between edge computing device, IoT platform and Schema
Repository
The Schema Repository shall be indicated by a uniquely determined location that is described
in the field of Data ID of a Container. The Schema Repository shall accept requests from an
authenticated IoT platform and an edge computing device.
8.2 Interface requirements for sensor
The edge computing device and the sensors connected to them shall share unique information
such as sensor IDs to identify each sensor individually. This unique information may be used
to set the Data ID of the Container.

– 20 – IEC 63430:2025 © IEC 2025
8.3 Security requirements
8.3.1 General description
Sensor data may contain sensitive information such as personal healthcare data, so it is
desirable to implement countermeasures against leakage, eavesdropping, and falsification of
data. There is a threat of unauthorized access by stealing the login information of the IoT
platform. Through this threat, there is a possibility that the data stored in the IoT platform can
be obtained by impersonating an authorized user. Therefore, the login information of the IoT
platform shall be strictly managed. In addition, it is necessary to prepare for DoS attacks on IoT
platforms and internal fraud. In such a system, the following threats are assumed [7], [8]:
• leakage of sensor data stored on networked edge computing devices,
• leakage of sensor data temporally buffered in wearable sensors,
• eavesdropping and falsification of sensor data on communication channels,
• unauthorized access on edge computing devices,
• unauthorized access and DoS attacks on IoT platforms,
• bulk leak of sensor data collected and centrally managed on IoT platforms.
8.3.2 Wearable sensor
The following measures shall be applied as security requirements against the threats to
wearable sensors:
• data encryption on wearable sensors,
• disassembly measures for wearable sensors (tamper resistance),
• secure deletion of data on wearable sensors.
8.3.3 Edge computing device
The following measures shall be applied as security requirements against the threat to edge
computing devices:
• data encryption on edge computing devices,
• disassembly measures for edge computing devices, e.g. tamper resistance,
• secure deletion of data on edge computing devices,
• measures against loss or theft of edge computing devices,
• measures against unauthorized use of edge computing devices, e.g. authentication and
terminal lock,
• virus infection countermeasures for edge computing devices.
8.3.4 IoT platform
The following measures shall be applied as security requirements against the threat to IoT
platforms:
• data encryption on IoT platforms,
• unauthorized access countermeasures for IoT platforms,
• DoS countermeasures for IoT platforms.

8.3.5 Schema Repository
The following measures shall be applied as security requirements against the threat to IoT
platforms:
• data encryption on Schema Repository,
• unauthorized access countermeasures for Schema Repository,
• DoS countermeasures for Schema Repository.
8.3.6 Container
The Container should be transported over secure channels between the edge computing device
and IoT platform, and between IoT platforms. A part of payload or an entire payload of the
Container may be protected by encryption.
8.3.7 Communication channel
The channel between wearable sensors, edge computing devices, Schema Repository and IoT
devices shall be protected by end-to-end encryption.

– 22 – IEC 63430:2025 © IEC 2025
Annex A
(informative)
Examples of Data ID Length
A.1 General description
This Annex A describes examples of correspondence between Data ID Type and Data ID Length.
Table A.1 shows an example Data ID Length for each Type of Data ID.
Table A.1 – Data ID Type and Data ID Length
Field Value Type of Data ID Data ID Length (Byte)
0x00 UUID 16
0x01 GTIN-8+Suffix 10
0x02 GTIN-12+Suffix 14
0x03 GTIN-13+Suffix 15
0x04 GTIN-14+Suffix 16
0x05 Bluetooth® 0
0x06 Proprietary 16
0x07-0xFF Reserved N/A
A.2 Data ID Length
A.2.1 UUID
A UUID is an identifier for uniquely identifying an object on software. A UUID is a 128-bit number
[7][9].
A.2.2 GTIN
GTIN is a general term for GS1 standard product identification codes, and there are four types:
GTIN-8, GTIN-12, GTIN-13, and GTIN-14 [10].
It is also possible to use GTIN as it is a Data ID Type. It is also possible to identify the sensor
in more detail by adding a suffix following the GTIN. Table A.1 shows an example when adding
a 2 Byte suffix.
A.2.3 Bluetooth®
Data ID Length for Bluetooth® packet is zero because it may be assumed that Bluetooth®
packet does not apply interactions with Schema Repository.
A.2.4 Proprietary Data ID Type and Data ID Length
A proprietary Data ID Type and Data ID Length can be defined. The example in Table A.1
indicates a 16 Byte Data ID Length.

Annex B
(informative)
Examples of interpretation between Schema Information and
Container payload
B.1 General description
This Annex B describes how Schema Information interprets Container payload using ASN.1
syntax. Figure B.1 provides an explanation using an example of a 3-axis acceleration sensor
device.
B.2 Example 1: An expression using 'repeat' identifier
Figure B.1 illustrates an example indicating a correspondence between a Container and its
Schema Information. In Figure B.1, a Container whose Data ID is 'XYZ111' has a Container
payload containing the data named 'Acceleration[0]' and 'Acceleration[1]' (the numbers in
square brackets in these Containers do not refer to the Bibliography). A set of 'offset',
'FieldName', 'repeat' and 'ClassIdentifier' is listed on the Schema Information. Additionally,
detailed parameters for Acceleration are included in the Schema Information.
According to the Schema Information, ClassIdentifier 'Acceleration' has two repetitions and
contains Acceleration[0] and Acceleration[1] and the Acceleration[0] is located 4 Bytes from the
beginning of the Container payload, followed by Acceleration[1]. The Acceleration[0] and
Acceleration[1] both contain the 2 Byte values X,Y,Z represented in the Property int16 in that
order.
Figure B.1 – Example1: Container format and Schema Information
The syntax for the Schema Information of Figure B.1 is shown in Figure B.2.

– 24 – IEC 63430:2025 © IEC 2025

Figure B.2 – Example1: Syntax of Schema Information
B.3 Example 2: An expression using 'length' identifier
Figure B.3 illustrates another example indicating a correspondence between a Container and
its Schema Information. In Figure B.3, a Container whose Data ID is 'XYZ111' has a Container
payload containing the data named 'Acceleration0' and 'Acceleration1'. A set of 'offset',
'FieldName', 'length' and 'ClassIdentifier' is listed on the Schema Information. Additionally,
detailed parameters for Acceleration are included in the Schema Information.
According to the Schema Information, ClassIdentifier 'Acceleration' contains two elements of
fieldname, Acceleration0 and Acceleration1.The Acceleration0 is located 4 Bytes from the
beginning of the Container payload and Acceleration1 is located 10 Bytes from the beginning
of the Container payload. The Acceleration0 and Acceleration1 both contain the 2 Byte values
X,Y,Z represented in the Property int16 in that order.

Figure B.3 – Example2: Container format and Schema information
The syntax for the Schema Information given in Figure B.3 is shown in Figure B.4.

– 26 – IEC 63430:2025 © IEC 2025

Figure B.4 – Example 2: Syntax of Schema Information

Bibliography
[1] IEC 63203-801-1:2022, Wearable electronic devices and technologies – Part 801-1:
Smart body area network (SmartBAN) – Enhanced ultra-low power physical layer
[2] IEC 63203-801-2:2022, Wearable electronic devices and technologies – Part 801-2:
Smart body area network (SmartBAN) – Low complexity medium access control (MAC)
for SmartBAN
[3] Bluetooth Core Specification 6.0. Online. Available from:
https://www.bluetooth.com/specifications/specs/core-specification/. [viewed 2024-23-
10]
[4] ISO/IEC 8824-1:2002, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
[5] ISO/IEC 10646:2020, Information technology – Universal coded character set (UCS)
[6] Internet Assigned Numbers Authority (IANA). Online. Available from:
https://www.iana.org/assignments/media-types/media-types.xhtml. [viewed 2024-23-10]
[7] ISO/IEC 11578:1996, Information technology – Open Systems Interconnection – Remote
Procedure Call (RPC)
[8] GS1. Online. Available from: https://www.gs1.org/ [viewed 2024-23-10]
[9] ISO/IEC 27400:2022, Cybersecurity – IoT security and privacy – Guidelines
[10] ETSI EN 303 645 V2.1.1, CYBER; Cyber Security for Consumer Internet of Things:
Baseline Requirements
___________
– 28 – IEC 63430:2025 © IEC 2025
SOMMAIRE
AVANT-PROPOS . 30
...