ࡱ > " k l 7 v x _ R @ bjbj O: b b O8 [ T6 T6 C C C C C C C C 8 C , E C >! G oH oH oH oH I M , N G I I I I I I $ % ' m C iO I I iO iO m C C oH oH 4 h Y Y Y iO > C oH C oH G Y iO G Y Y 9 oH 93_ T ś 3 T >! ! ( U ^ ( 6 ( C x_ iO iO Y iO iO iO iO iO m m Y j iO iO iO >! iO iO iO iO ( iO iO iO iO iO iO iO iO iO T6 mB :
CHANGE REQUESTGroup Name:*WG2 - ArchitectureSource:*KTFormat:*ARC 16.0 Face-to-Face MeetingDate:*2015-03-16Contact:*Francisco Sang-Eon Kim (kim.sangeon@kt.com)Reason for Change/s:*Architectual support for performance of discovery for AECR against: Release*Release 2CR against: TS/TR*TS-0001Clauses/Sub Clauses*9.6.1.1 Resource Type Summary
9.6.5 Resource Type AEType of change: * FORMCHECKBOX Editorial change
FORMCHECKBOX Bug Fix or Correction
FORMCHECKBOX Change/correction to existing feature or functionality
FORMCHECKBOX New feature or functionalityPost Freeze checking:*This CR contains only essential changes and corrections
YES FORMCHECKBOX NO FORMCHECKBOX
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.
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 sections need not show surrounding clauses as long as the proposed section number clearly shows where the new section 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
The TR-0001-V1.4.0, Use Case Collection, describes 8 verticals and 34 use cases as shown in Table 1.
oneM2M Use Cases
VerticalUse caseEnergy Use CaseWide area Energy related measurement/control system for advanced transmission and distribution automation
Analytics Use Case for M2M
Smart Meter Reading
Environmental Monitoring of Remote Locations to Determine Hydropower
Oil and Gas Pipeline Cellular/Satellite GatewayEnterprise Use CasesSmart BuildingHealthcare Use CasesM2M Healthcare Gateway
Use Case on Wellness Services
Secure remote patient care and monitoringPublic Services Use Cases Street Light Automation
Use Case on Devices, Virtual Devices and Things
Car/Bicycle Sharing Services
Smart Parking
Information Delivery service in the devastated areaResidential Use CasesHome Energy Management
Home Energy Management System (HEMS)
Plug-In Electrical Charging Vehicles and power feed in home scenario
Real-time Audio/Video Communication
Event Triggered Task Execution Use Case
Semantic Home Control
Semantic Device Plug and Play
Triggering in the Field DomainRetail Use CasesVending MachinesTransportation Use CasesAn industrial use case for on-demand data collection for factoriesOther Use CasesExtending the M2M Access Network using Satellites
M2M Data Traffic Management by Underlying Network Operator
Optimized M2M interworking with mobile networks (Optimizing connectivity management parameters)
Sleepy Node Use Case
Use Case on collection of M2M System data
Leveraging Broadcasting/ Multicasting Capabilities of Underlying Networks
Leveraging Service Provisioning for Equipment with Built-in M2M Device
Semantics query for device discovery across M2M Service Providers
Underlying network service activation and deactivation
An industrial use case for on-demand data collection for factories
There are millions of application entities (AEs) expected at infrastructure node (IN). It is difficult to handle with flat architecture of AE when resources are big data. A hierarchical resource structure of AEs can improve efficiency of retrieval in the big data environment. When someone searchs specific AE, hierarchical structure can takes effect that the amount of resource to be searched reduces compared with flat structures.
Figure 1 shows concept of hierarchical resource structure of AEs.
EMBED Visio.Drawing.11
---------------------------- Start of change 1 --------------------------------
9.6.1.1 Resource Type Summary
Table 9.6.1.1-1 introduces the normal and virtual resource types and their related child or parent resource types. Details of each resource type follow in the remainder of this clause.
Table 9.6.1.1-1 lists each specified . An addition of suffix "Annc" to such indicates the associated announced resource type.
Table 9.6.1.1-1 Resource Types
Resource TypeShort DescriptionChild Resource TypesParent Resource TypesClauseaccessControlPolicyStores a representation of privileges. It is associated with resources that shall be accessible to entities external to the Hosting CSE. It controls "who" is allowed to do "what" and the context in which it can be used for accessing the resourcessubscriptionAE, remoteCSE, CSEBase9.6.2AEStores information about the AE. It is created as a result of successful registration of an AE with the registrar CSEsubscription, container, group, accessControlPolicy, pollingChannel
AEremoteCSE, CSEBase9.6.5containerShares data instances among entities. Used as a mediator that takes care of buffering the data to exchange "data" between AEs and/or CSEs. The exchange of data between AEs (e.g. an AE on a Node in a field domain and the peer-AE on the infrastructure domain) is abstracted from the need to set up direct connections and allows for scenarios where both entities in the exchange do not have the same reachability schedulecontainer, contentInstance, subscription, AE, container, remoteCSE, CSEBase9.6.6contentInstanceRepresents a data instance in the resource.subscriptioncontainer9.6.7CSEBaseThe structural root for all the resources that are residing on a CSE. It shall store information about the CSE itselfremoteCSE, node, AE, container, group, accessControlPolicy, subscription,, mgmtCmd, locationPolicy, statsConfig, statsCollect, request, delivery,
scheduleNone specified9.6.3deliveryForwards requests from CSE to CSEsubscriptionCSEBase9.6.11eventConfigDefines events that trigger statistics collectionsubscriptionstatsConfig9.6.24execInstanceThe Execution Instance resource contains all execution instances of the same management command mgmtCmdsubscriptionmgmtCmd9.6.17fanOutPointVirtual resource containing target fro group request.
It is used for addressing bulk operations to all the resources that belong to a group.None specifiedGroup9.6.14groupStores information about resources of the same type that need to be addressed as a Group. Operations addressed to a Group resource shall be executed in a bulk mode for all members belonging to the GroupfanOutPoint,
subscriptionAE, remoteCSE, CSEBase9.6.13locationPolicyIncludes information to obtain and manage geographical location. It is only referred from container, the contentInstances of the container provides location informationsubscriptionCSEBase9.6.10mgmtCmdManagement Command resource represents a method to execute management procedures required by existing management protocolsexecInstance,
subscriptionCSEBase9.6.16mgmtObjManagement Object resource represents management functions that provides an abstraction to be mapped to external management technology. It represents the node and the software installed in the node.
NOTE: See clause 9.6.12 for a summary of specializations of subscription, mgmtObjnode, mgmtObj9.6.15
Annex Dm2mServiceSubscriptionProfileData pertaining to the M2M Service SubscriptionserviceSubscribedNode,
subscriptionNone specified 9.6.19nodeRepresents specific Node informationmgmtObj,
subscriptionAE, CSEBase, remoteCSE9.6.18pollingChannelRepresent a channel that can be used for a request-unreachable entitypollingChannelURIremoteCSE, AE9.6.21remoteCSERepresents a remote CSE for which there has been a registration procedure with the registrar CSE identified by the CSEBase resourceAE, container, group, accessControlPolicy, subscription, pollingChannel, scheduleCSEBase9.6.4requestExpresses/access context of an issued RequestsubscriptionCSEBase9.6.12scheduleContains scheduling information for delivery of messagessubscriptionsubscription,mgmtObj, CSEBase, remoteCSE9.6.39
Annex DserviceSubscribedNodeNode informationSubscriptionm2mServiceSubscriptionProfile9.6.20statsCollectDefines triggers for the IN-CSE to collect statistics for applicationssubscriptionCSEBase (in IN-CSE)9.6.25statsConfigStores configuration of statistics for applicationseventConfig,
subscriptionCSEBase (in IN-CSE)9.6.23subscriptionSubscription resource represents the subscription information related to a resource. Such a resource shall be a child resource for the subscribe-to resourcescheduleaccessControlPolicy, container, CSEBase, delivery, eventConfig, execInstance, group, contentInstance, locationPolicy, mgmtCmd, mgmtObj, m2mServiceSubscriptionProfile, node, serviceSubscribedNode, remoteCSE, request, schedule, statsCollect, statsConfig9.6.8
---------------------------- End of change 1 --------------------------------
---------------------------- Start of change 2 --------------------------------
9.6.5 Resource Type AE
An resource shall represent information about an Application Entity registered to a CSE.
EMBED Visio.Drawing.11
EMBED Visio.Drawing.11
Figure 9.6.5-1: Structure of resource
The resource shall contain the child resources specified in table 9.6.5-1.
Table 9.6.5-1: Child resources of resource
Child Resources of Child Resource TypeMultiplicityDescription Child Resource Types[variable]0..nSee clause 9.6.8[variable]0..nSee clause 9.6.6 [variable]0..nSee clause 9.6.13
[variable]0..nSee clause 9.6.2
[variable]0..nSee clause 9.6.21.
When the registrar CSE of this AE is request-unreachable, the AE should create this resource and perform long polling.[variable]0..nSee clause 9.6.5
The resource shall contain the attributes specified in table 9.6.5-2.
Table 9.6.5-2: Attributes of resource
Attributes of MultiplicityRW/
RO/
WODescription AttributesresourceType1ROSee clause 9.6.1.3 where this common attribute is described.NAparentID1ROSee clause 9.6.1.3 where this common attribute is described.NAexpirationTime1RWSee clause 9.6.1.3 where this common attribute is described.MAaccessControlPolicyIDs0..1 (L)RWSee clause 9.6.1.3 where this common attribute is described.MAcreationTime1RWSee clause 9.6.1.3 where this common attribute is described.NAlastModifiedTime1ROSee clause 9.6.1.3 where this common attribute is described.NAlabels0..1 (L)ROSee clause 9.6.1.3 where this common attribute is described.MAannounceTo0..1RWSee clause 9.6.1.3 where this common attribute is described.NAannouncedAttribute0..1RWSee clause 9.6.1.3 where this common attribute is described.NAappName0..1RWThe name of the application, as declared by the application developer(e.g."HeatingMonitoring")OAApp-ID1WOThe identifier of the Application (see clause 7.1.2).OAAE-ID1ROThe identifier of the Application Entity (see clause 7.1.2). OApointOfAccess0..1 (L)RWThe list of addresses for communicating with the registered Application Entity over Mca reference point via the transport services provided by Underlying Network (e.g. IP address, FQDN, URI). This attribute shall be accessible only by the AE and the Hosting CSE.
If this information is not provided, the AE should use resource. Then the Hosting CSE can forward a request to the AE without using the PoA.OAontologyRef0..1RWA URI of the ontology used to represent the information that is managed and understood by the AE.OAnodeLink0..1ROA URI of a resource that stores the node specific information. OA
---------------------------- End of change 2 --------------------------------
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?
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?
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 sections need not show surrounding clauses as long as the proposed section number clearly shows where the new section 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.?
ARC-2015-1781 Hierarchical resource structure of AE
Change Request
2 3 4 = ? @ A J M O P g h i s t u z { | 涭椖捿~sh h PJ nHo(tHh-Q PJ nHo(tHh1 hA mH nHsH tH h1 nHo(tHhl hA PJ nHo(tHh nHo(tHhR nHo(tHh" nHo(tHh% nHo(tHhA nHo(tHh: nHo(tHhA mH nHsH tH hA hA CJ OJ QJ ^J aJ hA mHsH$ 3 T N H $If $If kd $$If T s . $ F$
t
% 0 $6 4 4
s B `
a p
% ytA T $If 2 $ g=-$+DYa$gdA gdA $a$gdA 3 4 = @ \ V P $If $If kd $$If T s | 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T @ A J h \ V M $If gd $If kd $$If T s | 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T h i p { \ V M $If gd $If kd $$If T s | 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T { | \ V P $If $If kd $$If T s | 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T \ V M $If gd $If kd $$If T s t 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T # $ % B C X u v 4
5
C
D
E
b
c
d
{
ᾴƴvnn hA OJ QJ j
h Uj\
h Uh CJ OJ QJ j h Uj hA Uj hA UhA CJ OJ QJ j hA UhA nHo(tHh% nHo(tHh nHo(tHhA hA mH nHsH tH hS hA PJ nHo(tH ) $ \ V M $If gd $If kd $$If T s s0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T $ % : B \ V P $If $If kd $$If T s s0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T B C X v \ V P P $If $If kd $$If T s s0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T 4
c
\ V P P P G $If gd $If $If kd $$If T s s0 ] $ F '
t 0 $6 4 4
s B `
a p ytA T c
d
{
\ V P P $If $If kd, $$If T s 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T
, - O P N O # $ % & 2 3 ýrd`W h" nHo(tHh" *hA h tt nHo(tH hA B*KH PJ mHph6_ sHhA B*ph6_ hA B*PJ ph6_ hA B*KH PJ ph6_ hA OJ QJ ^J hA 5CJ OJ QJ ^J aJ hA
hA PJ hA mH nHsH tH hA OJ QJ j hA UhA CJ OJ QJ j hA Uj$ hA U \ W W W - ) $$d%d&d'dN O P Q a$gdA gdA kd $$If T s 0 ] $ F F'
t 0 $6 4 4
s B `
a p ytA T (
u
- P O % & 3 f gd`k $a$gd# gd" gdCvt &