The network operator provides network connectivity to MTC Server(s). This applies to MTC Server(s) controlled by the network operator (refer to figure 5-1) or to MTC Server(s) not controlled by the network operator (refer to figure 5-2.)
The MTC Device and the MTC Server it is communicating with may implement a service enablement framework (e.g. as specified in [4] and [5]) to provide generic functionality for applications. The MTC Device may implement multiple instances of service enablement frameworks, each communicating with a different MTC Server.
The communication scenario where the MTC Devices communicate directly without intermediate MTC Server (refer to figure 5-3) is not considered in this release of the specification.
Machine-Type Communication (MTC) applications do not all have the same characteristics. This implies that not every system optimization is suitable for every MTC application. Therefore, MTC Features are defined to provide structure for the different system optimization possibilities that can be invoked. MTC Features provided to a particular subscriber are identified in the subscription. MTC Features can be individually activated.
The following MTC Features have been defined: