Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
CHANGE REQUEST
Meeting ID:*
ARC 28
Source:*
Francisco Sang-Eon Kim, KT (TTA), [email protected]
Date:*
2017-03-19
Reason for Change/s:*
The access mode of memberType attribute of <group> resource has problem
considering consistencyStrategy attribute.
CR against: Release*
Release 3
CR against: WI*
Active <Work Item number>
MNT maintenance
Is this a mirror CR? Yes
No
mirror CR number: (Note to Rapporteur - use latest agreed revision)
STE Small Technical Enhancements / WI-0050
Only ONE of the above shall be ticked
CR against: TS/TR*
TS-0001-V3.4.0
Clauses *
9.6.13 Resource Type group
Type of change: *
Editorial change
Bug Fix or Correction
Change to existing feature or functionality
New feature or functionality
Only ONE of the above shall be ticked
Impacted other
TS/TR(s)
7.4.13 in TS-0004
Post Freeze checking:*
This CR contains only essential changes and corrections? YES
NO
This CR may break backwards compatibility with the last approved version
of the TS?
YES
NO
Template Version: January 2017 (Do not modify)
1
oneM2M Notice
2
3
4
5
6
The document to which this cover statement is attached is submitted to oneM2M. Participation in, or attendance at, any
activity of oneM2M, constitutes acceptance of and agreement to be bound by terms of the Working Procedures and the
Partnership Agreement, including the Intellectual Property Rights (IPR) Principles Governing oneM2M Work found in
Annex 1 of the Partnership Agreement.
© 2017 oneM2M Partners
Page 1 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
7
GUIDELINES for Change Requests:
8
Provide an informative introduction containing the problem(s) being solved, and a summary list of proposals.
9
Each CR should contain changes related to only one particular issue/problem.
10
11
In case of a correction, and the change apply to previous releases, a separate “mirror CR” should be posted at the same
time of this CR
12
Mirror CR: applies only when the text, including clause numbering are exactly the same.
13
Companion CR: applies when the change means the same but the baselines differ in some way (e.g. clause number).
14
15
16
Follow the principle of completeness, where all changes related to the issue or problem within a deliverable are
simultaneously proposed to be made E.g. A change impacting 5 tables should not only include a proposal to change
only 3 tables. Includes any changes to references, definitions, and acronyms in the same deliverable.
17
Follow the drafting rules.
18
All pictures must be editable.
19
Check spelling and grammar to the extent practicable.
20
Use Change bars for modifications.
21
22
23
The change should include the current and surrounding clauses to clearly show where a change is located and to provide
technical context of the proposed change. Additions of complete clauses need not show surrounding clauses as long as
the proposed clause number clearly shows where the new clause is proposed to be located.
24
25
Multiple changes in a single CR shall be clearly separated by horizontal lines with embedded text such as, start of
change 1, end of change 1, start of new clause, end of new clause.
26
27
When subsequent changes are made to content of a CR, then the accepted version should not show changes over
changes. The accepted version of the CR should only show changes relative to the baseline approved text.
28
Introduction
29
The memberType attribute is closely related to consistencyStrategy attribute. The descriptions are:
30
31
32
33
34
35
36
37
38
This attribute determines how to deal with the <group> resource if the memberType validation
fails. Its possible values are

ABANDON_MEMBER

ABANDON_GROUP

SET_MIXED
Which means delete the inconsistent member if the attribute is ABANDON_MEMBER; delete the group
if the attribute is ABANDON_GROUP; set the memberType to "mixed" if the attribute is SET_MIXED.
39
[case 1] single memberType of all reachable memberIDs
40
No issues.
If it is not given by the Originator at the creation procedure, default is "
ABANDON_MEMBER "
41
42
43
[case 2] single memberType of partial reachable memberIDs
To deal with an unreachable memberIDs, it should check consistencyStrategy.
44
45
First, the consistencyStrategy shall ABANDON_GROUP or ABANDON_MEMBER in case of single memberType.
If the consistencyStrategy is SET_MIXED, it is not clear to process.
46
Second, it is not clear to process for unreachable memberIDs. It depends on implementation.
© 2017 oneM2M Partners
Page 2 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
47
[case3] mixed memberType and consistencyStrategy is SET_MIXED
48
49
Third problem, it is not clear to process for unreachable memberIDs
This contribution proposes to resolve above issues by introducing unreachableMemberIDs and enforcement attributes.
50
51
52
53
54
An unreachableMemberIDs attribute is a list of memberIDs that is not reachable.
This is useful to check the validation of <group> resource. The TS-0004 is specified when memberIDs is not reachable,
whole validation is performed again.
With this unreachableMemberIDs attribute, validation for <group> resource can perform to partial memberIDs not
whole memberIDs
55
56
57
58
59
60
An enforcement attribute is value whether the unreachable memberIDs include or not. When enforcement is TRUE,
operation(Create, Retrieve, Update, Delete) shall be performed even if unreachableMemberIDs exist.
When enforcement is FALSE, it may check reachability for unreachableMemberIDs or check memberTypeValidated.
The TS-0004 is not explicitly specified on this at this time.
The followings are possible procedure for protocol aspects. It needs to be discussed at PRO WG.
© 2017 oneM2M Partners
Page 3 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
Start of validation on <group> resource
01: Check duplication of
memberIDs
yes
01-1: Remove duplicated
memberIDs
12-6: RSC = 6010
MAX_NUMBER_OF_MEMBER_EXCEEDED
no
no
02: currentNrOfMembers
< maxNrOfMembers
yes
03-2: Check to allow child
virtual resource at parent
resource
yes
03: Check virtual resource
no
yes
no
03-1: Retrieve resource of each
memberIDs
12-7: Table 6.6.3.6-1 RSC=XXXX
NOT_ALLOWED_VIRTUAL_RESOURCE
04: Check reachability to
all memberIDs
12-0: RSC = 2000
OK
success
05-1: Set
memberTypeValidated: TRUE
yes
05: Check privilege
no
fail
12-5: RSC = 5105
RECEIVER_HAS_NO_PRIVILEGE
04-1: Set
memberTypeValidated: FALSE
to 06
61
© 2017 oneM2M Partners
Page 4 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
from 04-1
06: Check
consistencyStrategy
ABANDON_GROUP
ABANDON_MEMBER
06-1: Abandon <group>
SET_MIXED
06-2: Remove memberIDs
12-1: Table 6.6.3.6-1 RSC=XXXX
ABANDON_GROUP_RESOURCE
12-2: Table 6.6.3.6-1 RSC=XXXX
SUCCESSFUL_OPERATION_GROUP_RESOURCE
TRUE
12-4: Table 6.6.3.6-1 RSC=XXXX
GROUP_MEMBERS_NOT_RESPONDED
FALSE
10: Check enforcement
FAIL
08: Check reachability for
unreachableMemberIDs
retry
08-1: Set
memberTypeValidated: TRUE
12-0: RSC = 2000
OK
success
08-1: Set
memberTypeValidated: TRUE
single
success
12-0: RSC = 2000
OK
09: Check reachability for
unreachableMemberIDs
mixed
07: Check memberType
(Resource Type)
fail
retry
11: Check enforcement
TRUE
12-3: Table 6.6.3.6-1 RSC=XXXX
SUCCESSFUL_MIXED_GROUP_RESOURCE
FALSE
12-4: Table 6.6.3.6-1 RSC=XXXX
GROUP_MEMBERS_NOT_RESPONDED
62
63
----------------------Start of change 1-------------------------------------------
© 2017 oneM2M Partners
Page 5 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
64
9.6.13
Resource Type group
65
66
67
68
69
70
The <group> resource represents a group of resources of the same or mixed types. The <group> resource can be used
to do bulk manipulations on the resources represented by the memberIDs attribute. The <group> resource contains an
attribute that represents the members of the group and the <fanOutPoint> virtual resource that enables generic
operations to be applied to all the resources represented by those members. By grouping <semanticDescriptor>
resources across which a semantic description is distributed, another virtual resource (<semanticFanOutPoint>) enables
semantic discovery procedures to be applied across the full logical tree in the description.
<group>
1
1
1
1(L)
0 .. 1 ( L)
0.. 1
1
0.. 1
0.. 1
0 ..n
0 ..n
0.. 1
1
memberType
currentNrOfMembers
maxNrOfMembers
memberIDs
membersAccesscontrolPolicyIDs
memberTypeValidated
consistencyStrategy
groupName
semanticSupportIndicator
<semanticDescriptor>
<subscription>
<semanticFanOutPoint>
<fanOutPoint>
71
Figure 9.6.13-1: Structure of <group> resource
72
© 2017 oneM2M Partners
Page 6 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
73
The <group> resource shall contain the child resources specified in table 9.6.13-1.
Table 9.6.13-1: Child resources of <group> resource
74
Child Resources of
<group>
[variable]
<semanticDescriptor>
0..n
[variable]
fopt
sfop
<subscription>
<fanOutPoint>
<semanticFanOutPoint>
0..n
1
0..1
Child Resource Type
Multiplicity
<groupAnnc> Child
Resource Types
See clause 9.6.30 <semanticDescriptor>,
<semanticDescriptorAnnc>
<subscription>
See clause 9.6.8
See clause 9.6.14
none
See clause 9.6.14a
none
Description
75
76
The <group> resource shall contain the attributes specified in table 9.6.13-2.
Table 9.6.13-2: Attributes of <group> resource
77
1
1
1
1
1
0..1 (L)
0..1 (L)
1
1
0..1 (L)
0..1 (L)
0..1 (L)
RW/
RO/
WO
RO
RO
WO
RO
RW
RW
RW
RO
RO
RW
RW
RW
0..1
1
RO
WO
currentNrOfMembers
1
RO
maxNrOfMembers
1
RW
1 (L)
RW
0..1 (L)
RW
0..1
RO
Attributes of
<group>
resourceType
resourceID
resourceName
parentID
expirationTime
accessControlPolicyIDs
labels
creationTime
lastModifiedTime
announceTo
announcedAttribute
dynamicAuthorizationCons
ultationIDs
creator
memberType
memberIDs
membersAccessControlPo
licyIDs
memberTypeValidated
© 2017 oneM2M Partners
Multiplicity
<groupAnnc>
Attributes
Description
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
See clause 9.6.1.3.
NA
NA
NA
NA
MA
MA
MA
NA
NA
NA
NA
OA
See clause 9.6.1.3.
It is the resource type of the member
resources of the group, if all member
resources (including the member
resources in any sub-groups) are of the
same type. Otherwise, it is of type
'mixed'.
<CSEBase> shall not be memberType.
When <CSEBase> needs to
memberType, <remoteCSE> which is
registered in registar shall be used.
Current number of members in a group. It
shall not be larger than
maxNrOfMembers.
Maximum number of members in the
<group>.
List of member resource IDs referred to
in the remaining of the present document
as memberID. Each ID (memberID)
should refer to a member resource or a
(sub-) <group> resource of the <group>.
A <group> resource with an empty
member list is allowed.
List of IDs of the <accessControlPolicy>
resources defining who is allowed to
access the <fanOutPoint> resource.
Denotes if the resource types of all
members resources of the group has
been validated by the Hosting CSE. In
the case that the memberType attribute
NA
OA
OA
OA
OA
OA
OA
Page 7 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
Attributes of
<group>
Multiplicity
consistencyStrategy
1
WO
0..1
0..1
RW
RO
0..1(L)
1
RW
WO
groupName
semanticSupportIndicator
unreachableMemberIDs
enforcement
RW/
RO/
WO
<groupAnnc>
Attributes
Description
of the <group> resource is not 'mixed',
then this attribute shall be set..
This attribute determines how to deal
with the <group> resource if the
memberType validation fails. Its possible
values are

ABANDON_MEMBER

ABANDON_GROUP

SET_MIXED
In case of ABANDON_MEMBER, the
<group> shall remove the inconsistent
memberIDs.
In case of ABANDON_GROUP, the
<group> shall not create or update to the
group.
In case of SET_MIXED, the <group>
shall set the memberType to "mixed" at
memberType attribute.
If it is not given by the Originator at the
creation procedure, default is "
ABANDON_MEMBER "
Human readable name of the <group>.
Indicator of support for sematic discovery
functionality via <semanticFanOutPoint>.
List of memberIDs that is not reachable
This is boolean value and default is
TRUE. When enforcement is TRUE,
operation shall be performed even if
unreachableMemberIDs exist.
When enforcement is FALSE, it may
check reachability for
unreachableMemberIDs or check
memberTypeValidated.
OA
OA
OA
NA
MA
78
79
-----------------------End of change 1---------------------------------------------
80
81
CHECK LIST
82
83

Does this Change Request include an informative introduction containing the problem(s) being solved, and a
summary list of proposals.?
84

Does this CR contain changes related to only one particular issue/problem?
85

Have any mirror CRs been posted?
86
87
88

Does this Change Request make all the changes necessary to address the issue or problem? E.g. A change
impacting 5 tables should not include a proposal to change only 3 tables?Does this Change Request follow the
drafting rules?
89

Are all pictures editable?
90

Have you checked the spelling and grammar?
91

Have you used change bars for all modifications?
92
93
94

Does the change include the current and surrounding clauses to clearly show where a change is located and to
provide technical context of the proposed change? (Additions of complete clauses need not show surrounding
clauses as long as the proposed clause number clearly shows where the new clause is proposed to be located.)
© 2017 oneM2M Partners
Page 8 (of 9)
Doc# ARC-2017-0115 Resource Type group Rel-3
Change Request
95
96

Are multiple changes in this CR clearly separated by horizontal lines with embedded text such as, start of
change 1, end of change 1, start of new clause, end of new clause.?
97
© 2017 oneM2M Partners
Page 9 (of 9)