8.5 Resource Structure

8.5.0 Introduction

The development of an oneM2M application includes the design of the resource trees of service capability layers i.e. IN-CSE and MN-CSE in the current use case. The resource tree is constructed with child resources created according to the high level procedures presented in oneM2M application developer guide clause 7. All the child resources shown in the resource trees are mandatorily required in order to correctly implement the remote lights control use case.

8.5.1 Resource Structure of IN-CSE

The resource tree of IN-CSE starts with a CSEBase named server depicted in figure 8.5.1-1.

The root CSEBase has two direct child resources, a remoteCSE named home_gateway and an AE named smartphone_ae .

Figure 8.5.1-1: IN-CSE resource structure

8.5.2 Resource Structure of MN-CSE

The resource tree of MN-CSE starts with a CSEBase named home_gateway depicted in figure 8.5.2-1.

The resource tree of MN-CSE is constructed with child resources as follows:

• an accessControlPolicy named gateway_acp ,
• an ADN-AE named light_ae1 which contains sub-resources of a container named light and multiple contentInstances,
• an ADN-AE named light_ae2 which contains sub-resources of a container named light and multiple contentInstances,
• light_state_sub1 and light_state_sub2 subscription resources that are child resources of the two light containers, and
• a MN-AE named gateway_ae which contains a group child resource,
• A group resource named containers_group whose members are the light containers of each AND-AEs. Smartphone application users with proper access control privileges can send a fanOutPoint request to this group to create and retrieve content instances in the two_light_ containers.

Figure 8.5.2-1: MN-CSE resource tree