Skip to content

5.8 Gateway as MN

5.8.1 Profile description

The profile defines gateways that may support multiple different area network technologies and connect devices from the corresponding area networks. The devices may be oneM2M defined ADNs, ASNs or NoDNs which are not defined by oneM2M. The gateway hosts resources to enforce common services that devices in the area network may utilize the enable local services without the dependency of the platform and the wide area network.

5.8.2 Profile usage examples

Home gateways deployed in the home for smart home:

Sensors, actuators and home appliances are connected with the home gateway. Applications can be connected through the platfrom to access the smart home service as well as applications can be directly connected with the gateway to do the same thing.

Head unit in connected vehicles:

Sensors and actuators in the car are connected with the head unit. The sensed data and control command are reported to delivered through the head unit. Applications may access the head unit and monitor the car state via the platform. Applications may also access the head unit once connected directly with the head unit via area network such as Wifi or Bluetooth.

5.8.3 Fundamental feature sets

Table 5.8.3-1: Fundamental feature sets for gateway as MN GEN

Feature Set Feature Remark
CE/GEN/00001 CE/GEN/00001/00001 Unstructured resource id
CE/GEN/00001/00002 Structured resource id
CE/GEN/00002 CE/GEN/00002/00001 Support blocking request

Table 5.8.3-2: Fundamental feature sets for gateway as MN REG

Feature Set Feature Remark
CE/REG/00001 CE/REG/00001/00001 Support <CSEBase> resource with attributes multiplicity equals 1[1].
CE/REG/00001/00002 Support the cseType attribute of <CSEBase> resource
CE/REG/00001/00003 Support the nodeLink attribute of <CSEBase> resource. This is dependent on the feature set for <node> resource.
CE/REG/00002 CE/REG/00002/00001 Support <AE> resource with attributes multiplicity equals 1[1]
CE/REG/00002/00002 AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'C'.
CE/REG/00002/00003 AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S'.
CE/REG/00002/00004 AE registration/de-registration without a pre-assigned AE-ID in the registration request and where no AE-ID Stem is included.
CE/REG/00002/00005 AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S' and where announcement to an IN-CSE is needed to get an AE-ID assigned
CE/DIS/00001/00006 Support the labels attribute of <AE> resource
CE/REG/00002/00007 Support the applicationName attribute of <AE> resource
CE/REG/00002/00008 Support the pointOfAccess attribute of <AE> resource
CE/REG/00002/00009 AE registration with pre-assigned AE-ID
CE/REG/00004 CE/REG/00004/00001 Support <remoteCSE> resource with attributes multiplicity equals 1[1]
CE/DIS/00001/00006 Support the labels attribute of <remoteCSE> resource
CE/REG/00004/00002 Support the cseType attribute of <remoteCSE> resource
CE/REG/00004/00003 Support the pointOfAccess attribute of <remoteCSE> resource
CE/REG/00004/00004 Support the nodeLink attribute of <remoteCSE> resource
CE/REG/00005 CE/REG/00005/00001 The Creation with <remoteCSE> resource for CSE registration with mandatory attributes[2] for Create and locally create <remoteCSE> that represents the Regstree CSE
CE/REG/00005/00001 Create the <remoteCSE> with resourceName attribute
CE/REG/00005/00001 Create the <remoteCSE> with expirationTime attribute
CE/REG/00005/00004 Create the <remoteCSE> with labels attribute
CE/REG/00005/00002 Create the <remoteCSE> with cseType attribute
CE/REG/00005/00003 Create the <remoteCSE> with pointOfAccess attribute
CE/REG/00005/00005 Create the <remoteCSE> with nodeLink attribute
CE/DIS/00001/00006 Update the <remoteCSE> with labels
CE/REG/00005/00001 Update the <remoteCSE> with expirationTime
CE/REG/00005/00006 Update the <remoteCSE> with pointOfAccess attribute
CE/REG/00005/00007 Update the <remoteCSE> with requestReachability
CE/REG/00005/00008 Update the <remoteCSE> with nodeLink attribute
CE/REG/00005/00001 Delete the <remoteCSE> resource on the Registrar, also delete the <remoteCSE> resource on the Registree
CE/REG/00005/00009 Retrieve the <remoteCSE> resource

Table 5. 8 .3- 3 : Fundamental feature sets for gateway as M N DMR

Feature Set Feature Remark
CE/DMR/00001 CE/DMR/00001/00001 Support <container> resource with attributes multiplicity equals 1[1]
CE/DIS/00001/00006 Support the labels attribute of <container> resource
CE/DMR/00001/00001 Support the creator attribute of <container> resource
CE/DMR/00001/00002 Support the maxNrOfInstances attribute of <container> resource
CE/DMR/00001/00003 Support the maxByteSize attribute of <container> resource
CE/DMR/00001/00004 Support the maxInstanceAge attribute of <container> resource
CE/DMR/00002 CE/DMR/00002/00001 Support <contentInstance> resource with attributes multiplicity equals 1[1]
CE/DIS/00001/00006 Support the labels attribute of <contentInstance> resource
CE/DMR/00002/00001 Support the creator attribute of <contentInstance> resource
CE/DMR/00002/00002 Support the contentInfo attribute of <contentInstance> resource
CE/DMR/00002/00004 Retrieve and Delete of latest <contentInstance> resource by <latest> virtual resource
CE/DMR/00002/00057 Retrieve and Delete of oldest <contentInstance> resource by <oldest> virtual resource

Table 5. 8 .3- 4 : Fundamental feature sets for gateway as M N SUB

Feature Set Feature Remark
CE/SUB/00001 CE/SUB/00001/00001 The Support of <subscription> resource with attributes multiplicity equals 1[1]
CE/DIS/00001/00006 Support the labels attribute of <subscription> resource.
CE/SUB/00001/00001 Support the creator attribute of <subscription> resource
CE/SUB/00001/00001 Support the subscriberURI attribute of <subscription> resource
CE/SUB/00004 CE/SUB/00004/00001 Notify the address indicated in notificationURI with notification elements multiplicity equals 1[2]
CE/SUB/00004/00002 Notify with notificationEvent/representation set in the notification
CE/SUB/00004/00003 Notify with creator set in the notification

Table 5. 8 .3- 5 : Fundamental feature sets for gateway as M N SEC

Feature Set Feature Remark
CE/SEC/00001 CE/SEC/00001/00001 Support <accessControlPolicy> resource with attributes multiplicity equals 1[1]
CE/DIS/00001/00006 Support the labels attribute of <accessControlPolicy> resource
CE/SEC/00002 CE/SEC/00002/00001 Support accessControlPolicyIDs attribute for <resource> that the Implementation supports.
CE/SEC/00002/00002 Support access control decision and enforcement making on the Hosting CSE