6 Architecture
This clause describes how the different components of this use case can be represented by corresponding oneM2M architectural entities as shown in figure 6-1.
Figure 6-1: oneM2M functional architecture of remote lights control use case
In the oneM2M functional architecture two basic types of entities are defined. One is an AE (short for Application Entity) and the other is a CSE (short for Common Services Entity). In this use case, the lights and smartphone each host an AE. Also an IN-CSE (short for Infrastructure Node CSE) is hosted in the cloud by the oneM2M Service Provider and a MN-CSE (short for Middle Node CSE) is hosted on the Home Gateway.
The oneM2M defined Mca reference point is used to interface an AE and CSE. The oneM2M defined Mcc reference point is used to interface CSEs. In this use case, the reference point used between a Light AE and home gateway MN-CSE or Smartphone AE and IN-CSE is Mca while reference point used between the home gateway MN-CSE and oneM2M service platform IN-CSE is Mcc
In summary, applications used in the current use case are classified as follows:
- ADN-AE1: an application embedded in Light#1 with capabilities to control Light#1 and interact with the home gateway MN-CSE through M ca reference point;
- ADN-AE2: an application embedded in Light# 2 with capabilities to control Light# 2 and interact with the home gateway MN-CSE through M ca reference point;
- IN-AE: a smartphone application embedded in the smartphone device with capabilities to interact directly with the oneM2M service platform IN-CSE through M cc reference point and thereby remotely control Light#1 and Light# 2 ;
- MN-AE: a gateway application embedded into the home gateway that interacts with the MN-CSE through M ca reference point.