CHANGE REQUEST
Meeting ID:*	PRO 30
Source:*	Hao Wu, ZTE, wu.hao18@zte.com.cn

Kun Yang, ZTE, yang.kun15@zte.com.cn

Jingting Hu, ZTE, hu.jingting@zte.com.cn
Date:*	2017-07-10
Reason for Change/s:*	Move the attributes deletion procedure to section 7.3.3.11.
CR against: Release*	Release2
CR against: WI*	Active <Work Item number>

MNT maintenance / < Work Item number(optional)>

Is this a mirror CR? Yes No

mirror CR number:XXX

STE Small Technical Enhancements / < Work Item number (optional)>

Only ONE of the above shall be ticked
CR against: TS/TR*	TS-0004 V2.12.0
Clauses *	7.3.3.10 Announce the resource or attribute

7.3.3.11 De-announce the resource or attribute
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)	<TS/TR number>, <Version Number>, and <Description on which aspect should be reflected in this TS/TR>
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)

oneM2M Notice

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.

GUIDELINES for Change Requests:

Provide an informative introduction containing the problem(s) being solved, and a summary list of proposals.

Each CR should contain changes related to only one particular issue/problem.

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

Mirror CR: applies only when the text, including clause numbering are exactly the same.

Companion CR: applies when the change means the same but the baselines differ in some way (e.g. clause number).

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.

Follow the drafting rules.

All pictures must be editable.

Check spelling and grammar to the extent practicable.

Use Change bars for modifications.

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.

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.

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.

Introduction

This contribution is trying to move the case of attribute deletion to the section of De-announce the resource or attribute. It is also proposed to add some missing “Wait for the Response primitive” process.

-----------------------Start of change 1-------------------------------------------

Announce the resource or attribute

If CREATE Request that contains an announceTo attribute is received,

Compose the CREATE Request primitive as follows:

The link attribute is set to the URI of the original resource.

If accessControlPolicyIDs attribute of the original resource is not present, accessControlPolicyIDs attribute is set to the same value with the parent resource or from the local policy of the original resource.

Attributes marked with MA in TS-0001 [6]. Such attributes shall be included if present in the original resource and set to same value as in the original resource.

Attributes marked with OA that are included in the announcedAttribute attribute. Such attributes shall be included if present in the original resource and set to same value as in the original resource.

The resourceType attribute is set to the announced variant of the original resource (see the Table 6.3.4.2.1‑1)

If announceTo attribute contains a list of CSE-ID(s) ,

Check if the parent resource of the original resource has been announced to the announcement target CSE(s).

If yes , announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the announced parent resource.

If no, check if the CSE hosting the original resource has registered and created a <remoteCSE> resource to the announcement target CSE(s).

If yes , announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the <remoteCSE> of the CSE hosting the original resource.

If no, then check if the CSE hosting the original resource has been announced to the announcement target CSE(s) and created a <remoteCSEAnnc> resource as a child of the <CSEBase>.

If yes, announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the <remoteCSEAnnc> resource

If no, then CSE hosting the original resource shall perform the following steps.

Announce itself to the CSE(s) specified in the announceTo attribute such that its <remoteCSEAnnc> resource is present at the announcement target CSE(s).

Send a CREATE Request to the CSE(s) specified in the announceTo of the request and that target the <remoteCSEAnnc> resource.

Otherwise, Send a CREATE Request to the CSE(s) represented by exact URI(s) in the announceTo of the request.

Wait for the Response primitive

Add the URI of successfully announced resource to the announceTo attribute of the resource

Include updated announceTo attribute in the Content parameter in the Response to the received CREATE Request.

If UPDATE Request that adds the URI or CSE-ID into the announceTo attribute is received,

Compose the CREATE Request primitive as follows:

Link is set to the URI of the original resource.

If accessControlPolicyIDs of the original resource is not present, accessControlPolicyIDs is set to the same value with the parent resource or from the local policy of the original resource.

Attributes marked with MA and attributes marked with OA that are included in the announcedAttribute attribute. Such attributes shall be present in the original resource and set to same value as the original resource.

If announceTo attribute contains a list of CSE-ID(s) ,

Check if the parent resource of the original resource has been announced to the announcement target CSE(s).

If yes , announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the announced parent resource.

If no, check if the CSE hosting the original resource has registered and created a <remoteCSE> resource to the announcement target CSE(s).

If yes , announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the <remoteCSE> of the CSE hosting the original resource.

If no, then check if the CSE hosting the original resource has been announced to the announcement target CSE(s) and created a <remoteCSEAnnc> resource as a child of the <CSEBase>.

If yes, announce the original resource by sending a CREATE Request to the CSE(s) specified in the announceTo and that targets the <remoteCSEAnnc> resource

If no, then CSE hosting the original resource shall perform the following steps.

Announce itself to the CSE(s) specified in the announceTo attribute such that its <remoteCSEAnnc> resource is present at the announcement target CSE(s).

Send a CREATE Request to the CSE(s) specified in the announceTo of the request and that target the <remoteCSEAnnc> resource.

Otherwise, Send a CREATE Request to the CSE(s) represented by exact URI(s) in the announceTo of the request.

Wait for the Response primitive

Add the URI of successfully announced resource to the announceTo attribute of the resource

Include updated announceTo attribute in the Content parameter in the Response to the received UPDATE Request.

If UPDATE Request that adds the attribute name into the announcedAttribute attribute is received,

Compose the UPDATE Request primitive. The UPDATE Request shall provide the attribute name for the attribute to be announced, and the initial value for the attribute in the Content parameter. The initial value shall be the same with the value from the original resource. The attribute that will be announced shall be marked as OA.

Send UPDATE Requests to all announced resources listed in the announceTo attribute.

Wait for Response primitive.

Add the attribute name of the successfully announced attribute to the announcedAttribute attribute.

Include updated announcedAttribute attribute in the Content parameter in the Response to the received UPDATE Request.

If an attribute(s) specified as MA (See TS-0001 [6]) or an attribute(s) included in the announcedAttribute attribute is updated:

Compose an UPDATE Request primitive by including the updated attribute(s) with its associated updated value.

Send the UPDATE Request to all CSE(s) represented by the URI(s) in the announceTo attribute of the original resource.

Wait for Response primitive.

De-announce the resource or attribute

If UPDATE Request that deletes the URI from the announceTo attribute is received:

Compose the DELETE Request primitive.

Send a DELETE Request to the CSE(s) represented by URI(s) in the announceTo attribute of the resource, which is not included in the announceTo of the request. The To parameter in the DELETE Request shall be set to the URI for the announced resource that will be deleted.

Wait for Response primitive.

Remove the URI of successfully de-announced resource from the announceTo attribute of the resource.

Include updated announceTo attribute in the Content parameter in the Response to the UPDATE Request of the original resource.

If DELETE Request is received:

Compose the DELETE Request primitive.

Send DELETE Requests to all of the CSE(s) represented by the URI(s) in the announceTo attribute of the resource.

Wait for Response primitive.

If UPDATE request that deletes the attribute name from the announcedAttribute attribute is received:

Compose the UPDATE Request primitive. The To parameter in the UPDATE Request shall be set to the URI for the announced resource. The UPDATE Request shall set the attribute that will be de-announced (i.e. to be deleted) in the Content parameter to NULL. The attribute that will be de-announced shall be marked as OA.

Send UPDATE Requests to all announced resources listed in the announceTo attribute of the original resource.

Wait for Response primitive.

Delete the attribute name of the successfully de-announced attribute from the announcedAttribute attribute.

Include updated announcedAttribute attribute in the Content parameter in the Response to the received UPDATE Request.

If an attribute(s) specified as MA (See TS-0001 [6]) or an attribute(s) included in the announcedAttribute attribute is deleted:

Compose an UPDATE Request primitive by including the deleted attribute(s) with its value set to NULL.

Send the UPDATE Request to all CSE(s) represented by the URI(s) in the announceTo attribute of the original resource.

Wait for Response primitive.

-----------------------End of change 1---------------------------------------------

CHECK LIST

Does this Change Request include an informative introduction containing the problem(s) being solved, and a summary list of proposals.?

Does this CR contain changes related to only one particular issue/problem?

Have any mirror CRs been posted?

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?

Are all pictures editable?

Have you checked the spelling and grammar?

Have you used change bars for all modifications?

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.)

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.?

Doc# ARC-2017-0150R01-Clarification of Resource announcement and de-announcement procedure.doc

Change Request

© 2017 oneM2M Partners	Page 6 (of 7)

oneM2M Template Change Request

oneM2M

2017-07-10

Windows 用户

ZTE