ISO/IEC 21559-3:2022

INTERNATIONAL ISO/IEC
STANDARD 21559-3
First edition
2022-03
Telecommunications and information
exchange between systems — Future
network protocols and mechanisms —
Part 3:
Networking of everything
Télécommunications et échange d'informations entre systèmes —
Futurs protocoles et mécanismes de réseau —
Partie 3: Réseautique universelle
Reference number
© ISO/IEC 2022
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2022 – All rights reserved

Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 FN-NoE functional description . 5
5.1 General . 5
5.2 Thing-user social community organization procedure . 5
5.3 Thing-user social community maintenance procedure . 6
5.4 Thing-user experiences sharing procedure . 8
5.5 Coordinated thing-user discovery procedure . 8
5.6 Proximal path establishment procedure . 9
6 FN-NoE services .10
6.1 General . 10
6.2 NoE SAP interface . 11
6.2.1 Thing-user centric communication service primitive . 11
6.2.2 Thing-user autonomous coordination . 15
6.3 TSN SAP interface .15
6.3.1 Thing-user social community organization primitives .15
6.3.2 Thing-user social community join primitives . 17
6.3.3 Thing-user social community maintenance primitives . 18
6.3.4 Thing-user subscribe/publish primitives . 19
6.4 PDN SAP interface . . .20
6.4.1 Thing-user discovery primitives . 20
6.4.2 Proximal path management primitives .22
7 FN-NoE protocols .23
7.1 General .23
7.2 TSN protocols . 24
7.2.1 Search a social community request message . 24
7.2.2 Search a social community report message. 25
7.2.3 Setup a new social group request message . 26
7.2.4 Setup a new social group report message . 26
7.2.5 Join a thing-user network request message . 27
7.2.6 Join a thing-user network report message . 27
7.2.7 Join a cluster request message .28
7.2.8 Join a cluster report message .29
7.2.9 Leave a TSN request message .29
7.2.10 Leave a TSN report message .30
7.2.11 Renew a coordinator request message . 31
7.2.12 Renew a coordinator report message . 31
7.2.13 Vote for a new coordinator request message . 31
7.2.14 Vote for a new coordinator report message . 32
7.2.15 Accept as a new coordinator message . 33
7.2.16 Subscribe thing-users request message . 33
7.2.17 Subscribe thing-users report message . 33
7.2.18 Publish to subscriber report message .34
7.3 PDN protocols .34
7.3.1 Set proximity measure request message .34
7.3.2 Set proximity measure report message. 35
7.3.3 Discover a peer request message.36
7.3.4 Discover a peer report message .36
iii
© ISO/IEC 2022 – All rights reserved

7.3.5 Maintain proximal path to a peer request message . 37
7.3.6 Maintain proximal path to a peer report message . 37
Bibliography .39
iv
© ISO/IEC 2022 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems.
A list of all parts in the ISO 21559 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
v
© ISO/IEC 2022 – All rights reserved

Introduction
ISO/IEC TR 29181 is a series of standards on Future Network (FN). The subject of ISO/IEC TR 29181-9
is Networking of Everything (NoE).
1)
ISO/IEC 21558-3 specifies the architecture of the FN-NoE to provide further advanced NoE services
identified in ISO/IEC TR 29181-9.
This document focuses on the FN-NoE protocols and mechanisms, consisting of functional procedures,
service interfaces, and protocols, to provide the thing-user centric communication service upon the FN-
NoE architecture defined in ISO/IEC 21558-3.
1) Under preparation. Stage at the time of publication: ISO/IEC PRF 21558-3.
vi
© ISO/IEC 2022 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 21559-3:2022(E)
Telecommunications and information exchange between
systems — Future network protocols and mechanisms —
Part 3:
Networking of everything
1 Scope
This document specifies:
— functional procedures to provide thing-user social networking and proximity defined networking;
— service access interfaces and protocols to support the FN-NoE functional procedure.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 21558-3:2022, Telecommunications and information exchange between systems — Future
network architecture — Part 3: Networking of everything
ISO/IEC/TR 29181-9:2017, Information technology — Future Network — Problem statement and
requirements — Part 9: Networking of everything
3 Terms and definitions
For the purposes of this document, the terms and definitions specified in ISO/IEC 21558-3 and
ISO/IEC TR 29181-9 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
object
intrinsic representation of an entity that is described at an appropriate level of abstraction in terms of
its attributes and functions
[SOURCE: ISO/IEC TR 29181-9:2017, 3.12]
3.2
identifier
series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s),
network element(s), function(s), network entity(ies) providing services/applications, or other entities
(e.g. physical or logical objects)
[SOURCE: ISO/IEC TR 29181-9:2017, 3.7]
© ISO/IEC 2022 – All rights reserved

3.3
context
information that can be used to characterize the environment of a user
[SOURCE: ISO/IEC TR 29181-9:2017, 3.4]
3.4
thing
object (3.1) of the physical world (physical things) or of the information world (virtual thing), which is
capable of being identified and integrated into communication networks
Note 1 to entry: Physical things are capable of being sensed, actuated and connected to things such as robots,
goods and electrical equipment. Virtual things are capable of being stored, processed and accessed by things
such as multimedia content and application software.
[SOURCE: ISO/IEC TR 29181-9:2017, 3.16]
3.5
collaborative work group
group of thing-users that can perform job planning, thing-user recruiting and coordination without
human intervention
[SOURCE: ISO/IEC TR 29181-9:2017, 3.2]
3.6
proximity defined network
PDN
network configured among devices in close proximity, using conventional wired/wireless LAN or WAN
technologies, which are in not only physically close proximity, but also closely related, or logically close
proximity.
Note 1 to entry: PDN is an instantaneous network which is formed during the networking of everything.
[SOURCE: ISO/IEC TR 29181-9:2017, 3.13, modified — Note 1 to entry was added.]
3.7
Future Network for Networking of Everything
FN-NoE
network that is capable of providing thing-user social networking (3.12) and thing-user centric
communication (3.13) service to the thing-users
[SOURCE: ISO/IEC 21558-3:2022, 3.8]
3.8
thing-user
thing that uses the Future Network for Networking of Everything (FN-NoE) (3.7) network service or the
FN-NoE services provided by other things
Note 1 to entry: The thing-user in FN-NoE is defined as a concept corresponding to a human-user. Thing-user has
an NoE terminal (3.11) function.
[SOURCE: ISO/IEC 21558-3:2022, 3.10, modified — Note 1 to entry was added.]
3.9
everything
equipment that is capable of performing Networking of Everything (NoE)
Note 1 to entry: "Everything" can be regarded as anything which can perform NoE in Future Network (FN).
Everything is limited to the NoE related documents if there are no other comments.
[SOURCE: ISO/IEC 21558-3:2022, 3.11, modified — The last sentence of Note 1 to entry was added.]
© ISO/IEC 2022 – All rights reserved

3.10
Networking of Everything
NoE
process that is capable of providing Future Network for Networking of Everything (FN-NoE) (3.7) services
[SOURCE: ISO/IEC 21558-3:2022, 3.12]
3.11
Networking of Everything (NoE) terminal
thing that can perform the process in the network capable of providing thing-user social networking
(3.12) and thing-user centric communication (3.13) service to the thing users
[SOURCE: ISO/IEC 21558-3:2022, 3.13]
3.12
thing-user social network
social network among thing-users (3.8) which automatically shares its capabilities, context (3.3),
communicative motivation, experiences and intentions of collaboration for delivering the intelligent
super-realistic service
Note 1 to entry: As the thing-user expands the social network, it may expand its knowledge.
Note 2 to entry: Thing-user social networking service can be a web application that thing-users use to build a
social network provided by Networking of Everything (NoE). For web implementations, please see references [2],
[3], [4], [5], and [6].
[SOURCE: ISO/IEC 21558-3:2022, 3.14, modified — The last sentence of Note 1 to entry was added.]
3.13
thing-user centric communication
process of conveying intended meanings from one thing-user (3.8) to another thing-user or thing-user
group through the use of mutually understood language
[SOURCE: ISO/IEC 21558-3:2022, 3.15]
3.14
thing-user centric network
network that allows a thing-user (3.8) to discover another thing-user or thing-user group who
understands its intention conveyed from the thing-user and supports the thing-user in achieving its
mission
[SOURCE: ISO/IEC 21558-3:2022, 3.16]
3.15
Profile
all or some of the following information statements about a thing-user (3.8): (1) basic statements
including Name, Identity, Address, URL, Account, Contract, Security; (2) motivation statements
describing why the thing-user joins the social network; (3) mission statements describing what
the thing-user plans to accomplish; and/or (4) capacity statements which describe its predications,
knowledge, resources
Note 1 to entry: The statements in the Profile can be represented by semantic web language, e.g. RDF, RDFS or
OWL, which can be standardized in W3C.
Note 2 to entry: In this document, semantic web technologies are used for explanation.
© ISO/IEC 2022 – All rights reserved

3.16
Networking of Everything (NoE) registry
resource which maintains and manages thing-user (3.8) social communities and clusters (3.17) by
keeping a list of all or some of the following characteristics of social communities and social clusters: (1)
types of social networks including category, place, means to connect with others, or a recommendation
system linked to trust; (2) coordinator information and status of social networks; (3) physical
characteristics, e.g. geographical locations, owner information, type, size; (4) network characteristics,
e.g. name, address, URI, capacity including QoS or security
3.17
cluster
one of the social groups of community (3.18) based on cultural and geographical relations
Note 1 to entry: Each cluster shall be built on characteristics of category place, communication type, or system
type. The cluster is organized and maintained by the cluster coordinator, who the cluster members elect.
3.18
community
one of the social groups of a thing-user (3.8) social network to share experiences and collaborate with
other thing-users to achieve a specific mission.
Note 1 to entry: The thing-users are autonomous and have equal rights to govern the thing-user social community.
A social community can be composed of one or more thing-user social clusters (3.17).
Note 2 to entry: The thing-user social community may have multi-tiered communities.
3.19
home thing-user
thing-user (3.8) that initially requests any action for a thing-user social network or a thing-user centric
network (3.14)
4 Abbreviated terms
dTU-ID destination Thing-User ID
FN Future Network
FN-NoE Future Network for Networking of Everything
ICT Information and Communication Technology
ID Identifier
NoE Networking of Everything
PDN Proximity Defined Network
SAP Service Access Point
sTU-ID source Thing-User ID
TSC Thing-User Service Control
TSN Thing-User Social Network
TU Thing-User
TU-ID Thing-User ID
TUn Thing-User n
© ISO/IEC 2022 – All rights reserved

TUn-ID Thing-User n ID
URI Uniform Resource Identifier
URL Uniform Resource Locator
5 FN-NoE functional description
5.1 General
The thing-user representing a NoE terminal or a virtual switch in the FN-NoE organizes the thing-
user social community to share experiences or collaborate on problem solving. The thing-user social
community provides intelligent collaboration services to accomplish mission described by a human-
user or by a thing-user. The thing-users configure the thing-user social community related to a specific
domain task, share an experience with another thing-user who has joined the thing-user social
community, and perform specific domain tasks autonomously without human operator intervention.
The thing-user social community has a procedure for consensus decision-making and for distributing
shared information. By discovering coordinated peers, the thing-user will establish a proximal path.
Then the thing-user is provided with the thing-user centric communication service.
5.2 Thing-user social community organization procedure
The thing-user of an NoE terminal or a virtual switch is initially specified with the Profile items
including identities, capability skill sets and mission statement to be accomplished.
After initiation, the thing-user visits well-known resources, like FN-NoE registry, to check whether a
thing-user social community exists for collaborating to accomplish the mission. If the thing-user finds a
coordinator of the thing-user social community with whom to collaborate, the thing-user sends a JOIN
message to the thing-user social community, as shown in Figure 2.
If the thing-user fails to find a thing-user social community, the thing-user organizes its own new
thing-user social community as shown in Figure 1. In this case, the thing-user becomes a community
coordinator. The TSN coordinator specifies the range of TSN and configures the structure of TSN.
The community coordinator searches the FN-NoE registry for the identities of the coordinator and
mission statement. The first community coordinator serves as a cluster coordinator as well, until the
cluster is renewed after joining another thing-user.
© ISO/IEC 2022 – All rights reserved

Figure 1 — Sequence chart for thing-user social community organization
5.3 Thing-user social community maintenance procedure
If the thing-user finds a social community coordinator to collaborate on its mission, the thing-user sends
a message to join the social community. The social community coordinator validates the thing-user
and assigns a cluster to join. If the assigned cluster coordinator is not located in the social community
coordinator, the social community coordinator requests the cluster coordinator to accept the thing-
user.
© ISO/IEC 2022 – All rights reserved

Figure 2 — Sequence chart for thing-user social community join
The community coordinator maintains the clusters and their coordinators. The periodic election of
a cluster coordinator renews the clusters of a social community. Similarly, the periodic election of a
community tier coordinator renews the community tier of a social community. The incumbent cluster
coordinator collects the ballots from the thing-users and selects a new coordinator and reports the
voting result to the new coordinator. The newly elected coordinator announces the voting results to
other thing-users. The incumbent cluster coordinator reports to the community coordinator that a new
cluster coordinator was elected.
When a thing-user leaves a social community, the cluster coordinator updates the list of cluster
members. If the departing thing-user is the last remaining thing-user of the social community, the
thing-user should check out of the FN-NoE registry.
Figure 3 — Sequence chart for thing-user social community renewal
© ISO/IEC 2022 – All rights reserved

5.4 Thing-user experiences sharing procedure
The experience of a thing-user is captured and shared with the thing-user social community in a
distributed manner. A cluster member may subscribe to an experience report from a certain cluster
member who publishes a captured experience to the subscribed thing-user according to its own
schedule.
The subscription request from a thing-user is reviewed and accepted based on the evaluation of the
subscribing thing-user’s social capital.
The subscription and publishing of experiences is managed at the cluster level.
Figure 4 — Sequence chart for thing-user experience sharing
5.5 Coordinated thing-user discovery procedure
The thing-user starts to search a coordinated peer or peer group to help solve the problem of the thing-
user described in the problem statement. The measure of proximity to a coordinated peer is defined in
the motive statement, mission statement, or capacity statement in the profile. If the thing-user does not
have enough information to specify the proximity measure, it may request the measure to the cluster
coordinator or the TSN coordinator.
The thing-user checks the proximity to subscribed thing-users in the cluster. If the thing-user finds an
appropriate peer thing-user, it sends a request for collaboration to solve a problem. If the thing-user
receives an acceptance of the collaboration request, the thing-user requests to establish the proximal
path to the coordinated thing-user.
If the thing-user fails to find a coordinated thing-user in the cluster, the thing-user starts to search for a
peer in another cluster in the same level of community tier. If the thing-user fails to find a coordinated
thing-user in the community tier In this case, the thing-user attempts to search for a peer in clusters in
the higher tier of community until it discovers a peer.
According to the profile, the proximal path will be established either to the single coordinated thing-
user or the sequentially ordered coordinated thing-users may be established.
© ISO/IEC 2022 – All rights reserved

Figure 5 — Sequence chart for thing-user discovery in case no appropriate thing-user was
found
Figure 6 — Sequence chart for thing-user discovery in case one or more appropriate thing-
user(s) were found
5.6 Proximal path establishment procedure
To accomplish a mission collaboratively, when a thing-user finds a thing-user or a thing-user group
belonging to the coordinated peers, the thing-user establishes proximal paths between them depending
© ISO/IEC 2022 – All rights reserved

on the type of collaboration group and the characteristics of collaborative communication. The type of
collaboration group can be peer-to-peer, peer-to-multi-peer, or multi-peer-to-multi-peer.
The thing-user who requests a search for the peers becomes the manager of the proximal paths between
peers. The manager of the proximal path has a responsibility to establish, maintain and release the
proximal paths. The manager of the proximal path monitors the status of the proximal path.
Figure 7 — Sequence chart for proximal path establishment
6 FN-NoE services
6.1 General
The coordinated networking layer consists of a thing-user service control (TSC) sublayer, thing-user
social network (TSN) sublayer, and proximity defined network (PDN) sublayer, as shown in Figure 8.
© ISO/IEC 2022 – All rights reserved

Figure 8 — FN-NoE terminal architecture
6.2 NoE SAP interface
The TSC sublayer provides NoE services to the application service layer through the NoE service access
point (NoE SAP). This sublayer maintains the profile of the thing-user and controls the execution of the
thing-user centric communication service.
6.2.1 Thing-user centric communication service primitive
The thing-user uses the thing-user centric communication service primitives to manage the thing-user
profile, maintain the thing-user social community to which it subscribed, and discover a peer thing-
user or a thing-user group that can accomplish a mission.
6.2.1.1 Managing thing-user profile
The MANAGE_TU_REQUEST and the MANAGE_TU_CONFIRM primitive are used to get the thing-user
profile or to set the thing-user profile. The structure of the thing-user profile is defined by a thing-user.
The name of an object in the thing-user profile shall be registered in the vocabulary set of the NoE
Registry.
The thing-user profile may consist of identities, thing-user descriptions, capabilities, mission statements,
social group descriptions and status of the thing-user. As identities, a thing-user may use combined
objects of the profile: name, location, URI, thing-user description objects, capability objects and social
group description objects. The thing-user description objects may consist of mobility, communication
access, processing, power, thing-user motivation, and thing-user limitation. The thing-user capability
description objects may consist of sensing capability skill sets and actuating capability skill sets. The
social group description objects may consist of social group identity, social group structure, role in a
social group, social group limitation and trustworthiness metrics.
NOTE The specification of the thing-user profile is outside the scope of this document. The object of the
thing-user profile can be described by semantic web language. The structure of the thing-user profile depends on
the domain ontologies related to the mission of the thing-user. In this document, the thing-user profile shall be
[1]
written in JSON text .
© ISO/IEC 2022 – All rights reserved

The MANAGE_TU_REQUEST primitive shall have two attributes: action and profile.
— MANAGE_TU_REQUEST (action, profile)
— action: “GET,” “SET”
— profile: JSON text
The MANAGE_TU_CONFIRM primitive shall have the following attributes: result, profile, and reason.
— MANAGE_TU_CONFIRM (result, profile, reason)
— result: “SUCCESS,” “FAIL”
— profile: JSON text
— reason: error comment
Upon receiving the MANAGE_TU_REQUEST primitive, the TSC sublayer starts to manage the thing-user
profile.
When the action is set to “GET” and the profile attribute is a blank object, the TSC sublayer shall respond
with the MANAGE_TU_CONFIRM by setting the result attribute to “SUCCESS” and the profile attribute
to the entire object of the thing-user profile. If the profile attribute indicates the list of selected objects,
the TSC sublayer shall respond with the MANAGE_TU_CONFIRM, by setting the result attribute to
“SUCCESS” and the profile attribute to the requested objects of the thing-user profile.
If the TSC sublayer is inactive or fails to identify the object, the TSC sublayer shall respond with
MANAGE_TU_CONFIRM, by setting the result attribute as “FAIL” and the reason attribute to error
comment using the words registered in the vocabulary set of the NoE Registry.
When the action is set to “SET,” the TSC sublayer identifies the objects of the profile attribute. If the
object is matched to the stored thing-user profile, the TSC sublayer changes the object of the thing-user
profile with the profile attribute and shall respond with MANAGE_TU_CONFIRM, by setting the result
attribute to “SUCCESS” and the profile attribute to the changed objects of the thing-user profile.
If the object is not found, the TSC sublayer shall respond with MANAGE_TU_CONFIRM, by setting the
result attribute to “FAIL” and the reason attribute to error comment.
6.2.1.2 Maintain thing-user social network (TSN)
The MANAGE_TSN_REQUEST and the MANAGE_TSN_CONFIRM primitives are used to maintain the
TSNs.
The MANAGE_TSN_REQUEST primitive shall have two attributes: action and profile.
— MANAGE_TSN_REQUEST (action, profile)
— action: “GET,” “JOIN,” “LEAVE,” “MAINTAIN”
— profile: JSON text
The MANAGE_TSN_CONFIRM primitive shall have the following attributes: result, profile, and reason.
— MANAGE_TSN_CONFIRM (result, profile, reason)
— result: “SUCCESS,” “FAIL”
— profile: JSON text
— reason: error comment
Upon receiving the MANAGE_TSN_REQUEST primitive, the TSC sublayer starts to manage the TSN.
© ISO/IEC 2022 – All rights reserved

When the action attribute is set to “GET,” and if the profile attribute indicates the list of the selected
social group, the TSC sublayer shall respond with MANAGE_TSN_CONFIRM by setting the result
attribute to “SUCCESS” and the profile attribute to the requested social group description objects of the
thing-user profile.
If the profile attribute is a blank object; In this case, the TSC sublayer shall respond with MANAGE_
TSN_CONFIRM by setting the result attribute to “SUCCESS” and the profile attribute to the entire social
group description that the thing-user joined.
If the thing-user is the community coordinator or the cluster coordinator, the structure of the
community or the structure of the cluster is contained in the profile attribute.
If the TSC sublayer fails to identify the social group or the TSN sublayer is not active; In this case, the
TSC sublayer shall respond with MANAGE_TSN_CONFIRM by setting the result attribute to “FAIL” and
the reason attribute to error comment text.
When the action attribute is set to “JOIN,” and if the profile attribute is not a blank object, the TSC
sublayer checks whether the thing-user already joined the TSN indicated in the profile attribute.
If the thing-user already joined, the TSC sublayer shall respond with MANAGE_TSN_CONFIRM by setting
the result attribute to “SUCCESS” and the profile attribute to the structure of the TSN joined.
If the thing-user did not already join, or if the profile attribute is a blank object, the TSC sublayer shall
search for a TSN by using the SEARCH_TSN_REQUEST primitive, as described in 6.3.1.1.
If the TSN sublayer reports to the TSC sublayer that it found a social group, the TSC sublayer shall join
the social group using the JOIN_TSN_REQUEST primitive, as described in 6.3.2.1.
If the TSN sublayer reports to the TSC sublayer that it did not find any social group, the TSC sublayer
shall organize a social group using the SETUP_TSN_REQUEST primitive, as described in 6.3.1.2.
When the TSN has social group organization, the TSC sublayer shall respond with MANAGE_TSN_
CONFIRM by setting the result attribute to “SUCCESS” and the profile attribute to the newly formed
social group description objects.
If the thing-user fails to join a social group, the TSC sublayer shall respond with MANAGE_TSN_
CONFIRM by setting the result attribute to “FAIL” and the reason attribute to the error comment text.
When the action attribute is set to “LEAVE,” and the profile attribute is not an empty object, the TSC
sublayer checks whether the thing-user still joining the TSN indicated in the profile attribute or not.
If the thing-user is still joining, the TSC sublayer shall leave a social community using the LEAVE_TSN_
REQUEST primitive, as described in 6.3.2.2.
Upon receiving the LEAVE_TSN_CONFIRM primitive with the result attribute set to “SUCCESS,” the TSC
sublayer shall confirm using MANAGE_TSN_CONFIRM with the result attribute set to “SUCCESS.”
If the thing-user did not join, the TSC sublayer confirms with MANAGE_TSN_CONFIRM by setting the
result attribute to “FAIL” and the reason attribute to the error comment text.
When the action attribute is set to “MAINTAIN,” and if the profile attribute is not a blank object, the TSC
sublayer checks whether the thing-user is the coordinator of the TSN.
If the thing-user is the coordinator of the TSN or the coordinator of the cluster, the TSC sublayer shall
maintain the social group using the MAINTAIN_TSN_REQUEST primitive by setting the action attribute
to “UPDATE,” “RENEW_TSN” or “RENEW_CLUSTER,” as described in 6.3.3.1.
Upon receiving the MAINTAIN_TSN_CONFIRM primitive with the result attribute set to “SUCCESS,” the
TSC sub-layer shall confirm using MANAGE_TSN_CONFIRM with the result attribute set to “SUCCESS.”
If the thing-user is not the coordinator, the TSC sublayer shall respond with MANAGE_TSN_CONFIRM
by setting the result attribute to “FAIL” and the reason attribute to the error comment text.
© ISO/IEC 2022 – All rights reserved

6.2.1.3 Discover peer thing-user
The MANAGE_PEER_REQUEST and the MANAGE_PEER_CONFIRM primitives are used to discover
a peer thing-user or peer thing-user group that collaborates to accomplish a mission by establishing
proximal paths to the thing-user.
The MANAGE_PEER_REQUEST primitive shall have the following attributes: action, profile, and path
ID.
— MANAGE_PEER_REQUEST (action, profile, path-ID)
— action: “DISCOVER,” “MAINTAIN,” “RELEASE”
— profile: JSON text
— path-ID: proximal path ID
The MANAGE_PEER_CONFIRM primitive shall have the following attributes: result, path-ID, peer-ID,
TU-profile, and reason.
— MANAGE_PEER_CONFIRM (result, path ID, peer ID, TU-profile, reason)
— result: “SUCCESS,” “FAIL”
— path-ID: proximal path ID
— peer-ID: a thing-user ID or the ID list of thing-users who collaborate
— TU-profile: profile of the peer thing-user who collaborates
— reason: error comment
Upon receiving the MANAGE_PEER_REQUEST primitive, the TSC sublayer starts to manage the peer
thing-user.
When the action attribute is set to “DISCOVER,” the TSC sublayer shall discover a peer thing-user or
peer thing-user group according to the mission statement, thing-user description, and social group
description objects included in the profile attribute.
The TSC sublayer shall specify the proximity measure by using the SET_PROXIMITY_REQUEST
primitive, as described in 6.4.1.1.
When the TSC sublayer is reported to have specified a proximity measure successfully by receiving the
SET_PROXIMITY_CONFIRM primitive with the result as attribute to “SUCCESS,” the TSC sublayer shall
start to discover a peer thing-user or peer thing-user group by using the DSICOVER_PEER_REQUEST
primitive, as described in 6.4.1.2.
Upon receiving the DISCOVER_PEER_CONFIRM primitive, the TSC sublayer completes peer discovery
by setting the resulting attribute to “SUCCESS,” and setting the profile attribute to the profile of the
discovered peer thing-user or the profile list of peer thing-users. If the TSC sublayer cannot find the
peer, the TSC sublayer shall respond with MANAGE_PEER_CONFIRM by setting the result attribute set
to “FAIL” and the reason attribute to the error annotation text.
When the action attribute is set to “MAINTAIN,” the TSC sublayer shall maintain a proximal path and
peer thing-user by using the MAINTAIN_PEER_REQUEST primitives by setting the action attribute to
“HEARTBEAT,” as described in 6.4.2.1.
When the action is set to “RELEASE,” the TSC sublayer shall release a proximal path by using the
MAINTAIN_PEER_REQUEST primitives by setting the action attribute to “RELEASE,” as described in
6.4.2.1.
© ISO/IEC 2022 – All rights reserved

6.2.2 Thing-user autonomous coordination
The TSC sublayer provides autonomous coordination services to the thing-user.
The TSC sublayer will autonomously manage the thing-user profile, maintain the thing-user social
community, discover a peer thing-user, and share the experiences by using the TSN SAP primitives and/
or the PDN SAP primitives.
6.3 TSN SAP interface
The TSN sublayer provides the social network service to the Thing-user Service Control sublayer
through the TSN SAP. This sublayer provides the thing-user social community organizing service, the
thing-user experience sharing service and the thing-user collaboration service.
6.3.1 Thing-user social community organization primitives
The TSC sublayer uses the thing-user social community organization primitives for searching the thing-
user social community to share experiences or for organizing a new social group.
6.3.1.1 Searching thing-user social community
The SEARCH_TSN_REQUEST primitive and the SEARCH_TSN_CONFIRM are used to search a TSN, which
will be used to share the experiences for the mission accomplishment.
The SEARCH_TSN_REQUEST primitive shall have the following attribute: profile.
— SEARCH_TSN_REQUEST (profile)
— profile: thing-user’s profile
The SEARCH_TSN_CONFIRM primitive shall have the following attributes: result, TSN-ID, TSN-profile,
and reason.
— SEARCH_TSN_CONFIRM (result, TSN-profile, reason)
— result: “SUCCESS,” “FAIL”
— TSN-ID: identifier of TSN discovered
— TSN-profile: social group description objects
— reason: error comment
Upon receiving the SEARCH_TSN_REQUEST primitive, the TSN sublayer of the home thing-user starts
to search a social community and to match up a TSN that is closely related to accomplishing the mission
stated in the profile attribute.
The TSN sublayer of the home thing-user shall send the SearchTSN request message to the NoE Registry
first, as described in 7.2.1.
When the TSN sublayer of the NoE Registry receives the SearchTSN request message, the TSN sublayer
of the NoE Registry looks up the social community database and finds a TSN related to the mission of
the home thing-user.
If the TSN sublayer finds a TSN, the TSN sublayer shall respond with the SearchTSN report message
containing a TSN-profile to the home thing-user, as described in 7.2.2.
If the TSN sublayer of the NoE Registry fails to find a TSN to collaborate with the home thing-user, the
TSN sublayer
...