Skip to content

8.6 Role of Entities

8.6.1 oneM2M service platform (IN-CSE)

The oneM2M service platform is modelled as an IN-CSE and is responsible for

  • handling the registration requests from the smartphone AE and home gateway MN-CSE

8.6.2 Home gateway application (MN-AE)

The home gateway application is modelled as a MN-AE and is responsible for

  • initializing the home gateway device,
  • creating an access control policy resource gateway_acpin the MN-CSE,
  • registering the home gateway application with the MN-CSE,
  • creating the group resource with access control policy gateway_acp in the MN-CSE,
  • discovering device applications registered with the MN-CSE, and

8.6.3 Light applications (ADN-AE1 and ADN-AE2)

Each of the light applications are modelled as an ADN-AE and are responsible for

  • initializing the light control device,
  • registering the light devices with the MN-CSE,
  • creating container resources named "light " with access control policy gateway_acp in the MN-CSE, respectively,
  • creating subscription resources lightstate_sub1 and lightstate_sub2 under the two light containers, and
  • creating content instance resources under containers light1 and light2 with initial light state, respectively.

8.6.4 Smartphone application (IN-AE)

The smartphone application is modelled as a IN-AE, which directly communicates with the oneM2M service platform IN-CSE and is responsible for

  • initializing the smartphone light control application,
  • registering the smartphone application with the IN-CSE,
  • discovering the two light containers,
  • displaying the discovered light states,
  • accepting the light state modification commands from the smartphone application user,
  • executing the light state modification commands for single and multiple lights.