Doc# Document1
Change Request
CHANGE REQUEST
Meeting:*
ARC#28.1
Source:*
C-DOT
Date:*
2017-03-28
Contact:*
Moode Giribabu Naik ([email protected]) , Poornima ([email protected])
Reason for Change/s:*
See the introduction
CR against: Release*
Release 3
CR against: WI*
Active <Work Item number>
MNT maintenace / < Work Item number(optional)>
STE Small Technical Enhancements / < Work Item number (optional)>
Only ONE of the above shall be ticked
CR against: TS/TR*
TS-0001 v2_12_2
Clauses/Sub Clauses*
9.6.15
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
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
This CR is a mirror CR? YES
if YES, please indicate the document
number of the original CR: : NO
Template Version:27 May 2015 (Dot not modify)
1
2
oneM2M Notice
3
4
5
6
7
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 8)
Doc# Document1
Change Request
8
GUIDELINES for Change Requests:
9
Provide an informative introduction containing the problem(s) being solved, and a summary list of proposals.
10
Each CR should contain changes related to only one particular issue/problem.
11
12
In case of a correction, and the change apply to previous releases, a separated “mirror CR” should be posted at the same
time of this CR
13
14
15
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.
16
Follow the drafting rules.
17
All pictures must be editable.
18
Check spelling and grammar to the extent practicable.
19
Use Change bars for modifications.
20
21
22
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 sections need not show surrounding clauses as long as
the proposed section number clearly shows where the new section is proposed to be located.
23
24
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.
25
26
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.
27
Introduction
28
29
This CR proposes changes in the attributes of specialized resource [firmware]. In TS-0004 following attribute
updateStatus have the update Optionality “O” which implies that it can be updated either by AE or CSE.
30
31
Table Error! Use the Home tab to apply Annex 3 to the text that you want to appear here.-1: Resource
specific attributes of [firmware]
Attribute Name
mgmtDefinition
Request Optionality
Create
Update
NP
M
objectIDs
O
NP
O
NP
O
O
M
M
M
M
NP
O
O
O
O
O
objectPaths
description
version
firmwareName
URL
update
updateStatus
Data Type
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
xs:string
xs:string
xs:anyURI
xs:boolean
m2m:actionStatus
Default Value and
Constraints
1001 (firmware)
32
33
34
So, In TS-0001 [firmware] resource’s attribute updateStatus should be RW which implies that it can be updated by AE
or CSE.
© 2017 oneM2M Partners
Page 2 (of 8)
Doc# Document1
Change Request
35
36
37
38
39
40
41
This CR proposes changes in the attributes of specialized resource [battery]. In TS-0004 following attributes
batteryLevel and batteryStatus have the update Optionality “O” which implies that it can be updated either by AE or
CSE.
42
43
44
Table Error! Use the Home tab to apply Annex 3 to the text that you want to appear here.-2: Resource
specific attributes of [battery]
Attribute Name
mgmtDefinition
Request Optionality
Create
Update
NP
M
objectIDs
O
NP
O
NP
O
O
M
O
M
O
objectPaths
description
batteryLevel
batteryStatus
Data Type
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
See clause Error!
Reference source not
found.
xs:unsignedInt
Default Value and
Constraints
1006 (battery)
Range: 0-100
Unit: percent
m2m:batteryStatus
45
46
47
So, In TS-0001 [battery] resource’s attributes batteryLevel and batteryStatus should be RW which implies that it can be
updated by AE or CSE.
48
49
50
51
-----------------------Start of change 1----------------------------------------------
52
D.2
53
54
The [firmware] resource is used to share information regarding the firmware on the device. The [firmware] resource is
a specialization of the <mgmtObj>resource.
Resource firmware
© 2017 oneM2M Partners
Page 3 (of 8)
Doc# Document1
Change Request
[firmware]
1
mgmtDefinition
0..1 (L)
objectIDs
0..1(L)
objectPaths
0..1
description
1
version
1
name
1
URL
1
update
1
updateStatus
0..n
<subscription>
0..n
<semanticDescriptor>
55
Figure D.2-1: Structure of [firmware] resource
56
57
The [firmware] resource shall contain the child resources specified in table D.2-1.
Table D.2-1: Child resources of [firmware] resource
58
Child Resources of
[firmware]
[variable]
[variable]
Child Resource
Type
<subscription>
<semanticDescripto
r>
Multiplicity
0..n
0..n
Description
See clause 9.6.8 where the type of this
resource is described.
See clause 9.6.30
59
© 2017 oneM2M Partners
Page 4 (of 8)
Doc# Document1
Change Request
60
The [firmware] resource shall contain the attributes specified in table D.2-2.
Table D.2-2: Attributes of [firmware] resource
61
resourceType
resourceID
resourceName
parentID
expirationTime
accessControlPolicyIDs
creationTime
lastModifiedTime
labels
mgmtDefinition
1
1
1
1
1
0..1 (L)
1
1
0..1(L)
1
RW/
RO/
WO
RO
RO
WO
RO
RW
RW
RO
RO
RW
WO
objectIDs
objectPaths
description
version
0..1 (L)
0..1 (L)
0..1
1
RW
RW
RW
RW
name
1
RW
URL
1
RW
update
1
RW
updateStatus
1
RW
Attributes of
[firmware]
Multiplicity
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.15. Has fixed value "firmware" to indicate the
resource is for firmware management.
See clause 9.6.15.
See clause 9.6.15.
See clause 9.6.15.
The version of the firmware. This attribute is a specialization of
[objectAttribute] attribute.
The name of the firmware to be used on the device. This
attribute is a specialization of [objectAttribute] attribute.
The URL from which the firmware image can be downloaded.
This attribute is a specialization of [objectAttribute] attribute.
The action that downloads and installs a new firmware in a
single operation. The action is triggered by assigning value
"TRUE" to this attribute. This attribute is a specialization of
[objectAttribute] attribute.
Indicates the status of the update. This attribute is a
specialization of [objectAttribute] attribute.
62
63
64
-----------------------End of change 1----------------------------------------------
65
66
67
68
69
© 2017 oneM2M Partners
Page 5 (of 8)
Doc# Document1
Change Request
70
-----------------------Start of change 2----------------------------------------------
71
D.7
72
73
The [battery] resource is used to share information regarding the battery. The [battery] resource is a specialization of
the <mgmtObj> resource.
Resource battery
[battery]
1
mgmtDefinition
0..1 (L)
objectIDs
0..1 (L)
objectPaths
0..1
description
1
batteryLevel
1
batteryStatus
0..n
0..n
<subscription>
<semanticDescriptor>
74
Figure D.7-1: Structure of [battery] resource
75
76
The [battery] resource shall contain the child resources specified in table D.7-1.
Table D.7-1: Child resources of [battery] resource
77
Child Resources of
[battery]
[variable]
[variable]
Child Resource
Type
<subscription>
<semanticDescripto
r>
Multiplicity
0..n
0..n
Description
See clause 9.6.8 where the type of this
resource is described.
See clause 9.6.30
78
© 2017 oneM2M Partners
Page 6 (of 8)
Doc# Document1
Change Request
79
The [battery] resource shall contain the attributes specified in table D.7-2.
Table D.7-2: Attributes of [battery] resource
80
resourceType
resourceID
resourceName
parentID
expirationTime
accessControlPolicyIDs
creationTime
lastModifiedTime
labels
mgmtDefinition
1
1
1
1
1
0..1 (L)
1
1
0..1(L)
1
RW/
RO/
WO
RO
RO
WO
RO
RW
RW
RO
RO
RW
WO
objectIDs
objectPaths
description
batteryLevel
0..1 (L)
0..1 (L)
0..1
1
RW
RW
RW
RW
batteryStatus
1
RW
Attributes of
[battery]
Multiplicity
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.15. This attribute shall have the fixed value
"battery".
See clause 9.6.15.
See clause 9.6.15.
See clause 9.6.15.
The current battery level. This attribute is a specialization of
[objectAttribute] attribute.
Indicates the status of the battery. This attribute is a
specialization of [objectAttribute] attribute.
81
82
-----------------------End of change 1----------------------------------------------
83
84
85
86
CHECK LIST
87
88

Does this change request include an informative introduction containing the problem(s) being solved, and a
summary list of proposals.?
89

Does this CR contain changes related to only one particular issue/problem?
90

Have any mirror crs been posted?
91
92
93

Does this change request make all the changes necessary to address the issue or problem? 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?
94

Does this change request follow the drafting rules?
95

Are all pictures editable?
96

Have you checked the spelling and grammar?
97

Have you used change bars for all modifications?
98
99
100

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 sections need not show surrounding
clauses as long as the proposed section number clearly shows where the new section is proposed to be located.)
101
102

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.?
103
© 2017 oneM2M Partners
Page 7 (of 8)
Doc# Document1
Change Request
104
© 2017 oneM2M Partners
Page 8 (of 8)