5.2 Functional mapping between 3GPP and oneM2M

Figure 5.2-1 shows an architecture and functional mapping for the 3GPP Trust Domain which describes how oneM2M functional entities may access features and services that are exposed by 3GPP.

The "MTC Applications" hosted on the UE may be deployed as follows:

• Application only: UE may be an ADN oneM2M entity
• Application and CSE: UE may be an ASN or MN oneM2M entity
• CSE only: UE may be a MN oneM2M entity
• Neither application nor CSE: UE may be a NoDN.

The SCS may be an IN-CSE, and the "MTC-Applications" or ASs that are hosted in an external network may be IN-AEs.

The "3GPP Trust Domain" in Figures 5.1-1 and Figure 5.2-1 captures the functional entities that shall be part of the 3GPP domain (the network). Although Figure 5.2-1 shows that the IN-CSE and IN-AE are outside of the 3GPP Domain, the IN-CSE may be part of the operator domain.

This figure also shows the oneM2M reference points Mcn, Mcc and Mca. The Mcc reference point enables communication between CSEs such as the CSE shown on the left-hand side and the IN-CSE shown on the right-hand side of the figure 5.2-1.

Figure 5.2-1: oneM2M Interfaces to the underlying 3GPP Network

Several implementation options for the placement of the oneM2M IN-CSE relative to the SCEF and the underlying 3GPP network are envisioned. In all implementations, the SCEF always resides within 3GPP domain.

In some options the IN-CSE and the SCEF are deployed by a MNO and are both part of the operator domain. In other options the SCEF is part of the 3GPP domain and the IN-CSE is not part of the operator domain.

In all options, services within the IN-CSE may access the network services that are exposed by the SCEF via the T8 reference point APIs.