one m2m 3- managment_capability
TRANSCRIPT
OneM2M Standard Specification
Khamdamboy Urunov, a Ph.D. student.Special Communication Research Center.,
Financial Information Security., Kookmin University Seoul, South Korea
Functional Architecture
Management capability
2
The schedule of OneM2M Specification
• TS-0002-V2.7.1 Requirements
• TS-0001- Functional_Architecture-V2_10_0
• TS-
0004_Service_Layer_Core_Protocol_V2_7_1
3
Contents• Common Services Functions
• Application and Service Layer Management
Functional Architecture
4
TS-0002-V2.7.1 RequirementsComments
• International or Domestic Standard documents can use various preposition of
explain text. Conventions
• LWM2M definition
• M2M Area Network (MAN) definition
5
Conventions of Standard document
a : will have to : mustb : will be able to : canc: to have to : MUSTd: shall : should/need toe: shall be able to: can/ need to
6
LWM2M
7
LWM2M(1)
http://www.slideshare.net/zdshelby/oma-lightweightm2-mtutorial
8
M2M Area Network
Nippon Telegraph and Telephone (NTT) is Japan company., 1985 adjusting 36.5 % telecommunication in Japan. 3 place in the World.
M2M Area Network: an M2M Area Network provides connectivity between M2M Devices (both compliant and noncompliant to ETSI M2M) and ETSI M2M Gateways.
9
TS-0001- Functional_Architecture-V2_10_0
• Common Services Functions
• Application and Service Layer Management
10
Functional Architecture
Infrastructure nodes ~ servers
Middle Nodes ~ gateways
Application Service Nodes: smart oneM2M devices
Application Dedicated Nodes: dumb oneM2M devices
1 2
3
Mca reference point: communication flows between AE & CSE Mcc reference point: communication flows between two CSEs Mcn reference point: communication flows between CSE & Underlying Network Services Entity (NSE)Mcc' reference point: goal to be as similar as possible to Mcc reference point - some differences anticipated
1
2
№№
3
4
4
43
The Interworking Proxy Entity (IPE)
11
Common Services Functions
12
Management Capability
13
Management Layers and Function
The ASM CSF utilizes the functions provided by the Device Management (DMG) CSF for interaction with the Management Server. The management functions include: Configuration Function (CF): This function enables the configuration of the capabilities
and features of the CSE (e.g. CMDH policies). Communication Management and Delivery Handling (CMDH)
Software Management Function (SMF): This function provides lifecycle management for software components and associated artifacts (e.g. configuration files) for different entities such as CSE and AE.
Fig.3 Management Layers and Function
• The Application and Service Layer Management (ASM) CSF provides management capabilities for CSEs and AEs.
• This includes capabilities to configure, troubleshoot and upgrade the functions of the CSE, as well as to upgrade the AEs.
14
Communication Management and Delivery Handling (CMDH)
15
Device Management Architecture
16
Device Management Architecture
The Data Management and Repository (DMR) CSF is responsible for providing data storage and mediation functions. It includes the capability of collecting data for the purpose of aggregating large amounts of data, converting this data into a specified format, and storing it for analytics and semantic processing.
Application Service Node (ASN)
Middle Node (MN)
• la – local adapter• mp - management proxy• mc – management client• ms- management server
Figure 6.2.4.1.1-1: Device Management Architecture
17
Device Management Architecture (1)
The Management Server and Management Client can be implemented as an entity external to the Node or they can be implemented as an entity embedded within the Node (figure 6.2.4.1.1-1). The Management Server and the Management Client are located on the boundary of the Node to indicate this situation as well as to depict that an IN can utilize multiple Management Servers from various M2M and Network Service Providers.
Management Server Interaction
18
Mc is interface, is for delivering the
requests from the request Originator to
the Management Server, or receiving
information from the Management
Server that will be notified to subscribing
M2M Entities (e.g. AE, CSE)
The access control policy information for resources from Management Servers may be discovered using the ms interface.
• Discovery of technology specific data model objects:When the IN-DMG-MA maintains information (i.e. metadata, values) of the technology specific data model objects managed by a Management Server using the ms interface
19
Management Server Interaction(1)
6.2.4.1.2.1-1 the Management Server in the Underlying Network controls access of the exposed resources from the technology specific protocol, while, in the figure 6.2.4.1.2.1-2, the Management Server in the M2M Service Layer controls access to the resources
20
Management Client Interaction
By using la interface, the Management Adapter can communicate with the Management Client to discover the technology specific data model objects supported by the Management Client.
21
Device Management Resource Lifecycle
