Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PCC, so the 3GPP intends to first agree on a solution and then bring it to the attention of the BBF for<br />
agreement.<br />
At this stage of the work we can presumably assume that the 3GPP EPC architecture and procedures<br />
included in 3GPP TS 23.402, the PCC specification 3GPP TS 23.203 and the relevant stage 3<br />
specification will be enhanced for support of BBF interworking scenario. As mentioned above, the BBF is<br />
working on the definition of the functionalities, procedures and parameters for the Policy Framework (WT-<br />
134) so the implications of supporting interworking are not fully investigated.<br />
In 3GPP the FMC work has been moved from Rel-10 to Rel-11 framework; in BBF the approval of WT-<br />
203 is planned for Q1 2011 and for WT-134 in Q2 2011.<br />
7.3.4 MACHINE‐TO‐MACHINE COMMUNICATIONS<br />
Machine-Type Communication (MTC) is a form of data communication that involves one or more entities<br />
that do not need human interaction. Machine-Type Communications is different from current mobile<br />
network communication services as it mainly involves communication amongst large number of terminals<br />
and little traffic per terminal. Smart meters with metering application are expected to be one among the<br />
early MTC devices deployed by utility companies, who will be using the services provided by wireless<br />
network operators. Many other MTC devices such as e-health monitors (running monitoring applications)<br />
are envisioned and are expected to be widely used in the near future.<br />
MTC functionality is provided by the visited and home networks when the networks are configured to<br />
support Machine-Type Communication. The number of MTC devices may be several orders of magnitude<br />
greater than “traditional” devices. A service optimized for Machine-Type Communications differs from a<br />
service optimized for human-to-human communications. By leveraging connectivity, Machine-to-Machine<br />
(M2M) communication enables machines to communicate directly with one another. In so doing, M2M<br />
communication has the potential to radically change the world around us and the way that we interact<br />
with machines.<br />
In the Rel-10 timeframe, 3GPP studied a number of M2M application scenarios to establish requirements<br />
for 3GPP network system improvements that support Machine-Type Communications (MTC). The<br />
objective was to identify 3GPP network enhancements required to support a large number of MTC<br />
devices in the network and to provide necessary network enablers for MTC communication service.<br />
Specifically, transport services for MTC as provided by the 3GPP system and the related optimizations<br />
are being considered as well as aspects needed to ensure that data and signaling traffic related to MTC<br />
devices does not cause network congestion or system overload. It is also important to enable network<br />
operators to offer MTC services at a low cost level, to match the expectations of mass market machinetype<br />
services and applications.<br />
The 3GPP stage 1 on Machine-Type Communications (3GPP TS 22.368) describes common and specific<br />
service requirements. Common service requirements include:<br />
� MTC device triggering<br />
� Addressing and Identifiers<br />
� Charging requirements<br />
� Security requirements<br />
www.4gamericas.org February 2011 Page 71
Change language