12.2 M2M Data Traffic Management by the Underlying Network Operator

12.2.1 Description

According to the data traffic condition, e.g. current traffic congestion status, in underlying networks, the underlying network operators (e.g. mobile network operators) would like to manage the M2M data traffic in their networks in conjunction with M2M service platform and/or M2M application server providers in order to avoid losing the M2M communication data packets in the networks.

The M2M service platform and/or M2M application server providers will change their configuration such as data transmission interval or stop sending data over the underlying networks for some duration after receiving the notification from underlying networks.

This use case illustrates handling of M2M data transmission based on the data traffic condition information of underlying network and interworking among the M2M service application server, M2M platform and the underlying network.

12.2.2 Source

oneM2M-REQ-2013-0175R03 Use Case on M2M data traffic management by underlying network operator

12.2.3 Actors

• The M2M application server providing data transmission control according to the data traffic condition of underlying network
  The application server has functions to receive data traffic condition information from the M2M platforms and/or the underlying networks, and control M2M data transmissions according to the received information.
• The M2M service platform providing data transmission control according to the data traffic condition information of underlying networks
  The M2M service platform has functions to receive the data traffic condition information from the underlying networks, and/or control M2M data transmissions according to the information.
• The underlying network providing the data traffic condition information
  The underlying network has functions to send the data traffic condition information to M2M application servers, M2M service platforms, and/or M2M devices. The data traffic condition information includes required transmission interval, required maximum data rate, required maximum data volume, current traffic congestion status, congested network area information etc.
• The M2M device providing data transmission control according to the data traffic condition information
  The M2M device to receive the data traffic condition information from the underlying networks or M2M service platforms, and control M2M data transmissions.

12.2.4 Pre-conditions

The underlying network monitors the status of the data traffic, analyse the status, define the traffic condition and provides the data traffic condition information to M2M application servers, M2M platforms and/or M2M devices.

12.2.5 Triggers

None

12.2.6 Normal Flow

Normal Flow 1:

1. The mobile network sends the data traffic condition information to the M2M service platform and/or M2M application server.
2. After the M2M service application server receives the data traffic condition information from the underlying network in step1, and it controls M2M data transmission accordingly.
3. After the M2M application service platform receives the data traffic condition information from the underlying network in step 1 via the M2M service platform, it and controls M2M data transmissions accordingly.
4. The M2M service platform may send M2M data transmission configuration information to the M2M device.
5. After the M2M device may receive M2M data transmission configuration information from the M2M service platform in step 4, it and may controls M2M data transmissions accordingly.

Figure 12.2.6-1 Normal Flow 1 of Data Traffic Management by Underlying Network Operator

Normal Flow 2:

1. The underlying mobile network sends the data traffic condition information to the M2M device as well as M2M service platform.
2. Upon receiving the information, the M2M device re-configures the application behavior, e.g. the interval extension of communication, by M2M service layer capability. The re-configuration profile may be statically stored or can be overwritten by control from the M2M service platform.
3. Upon receiving the information, the M2M service platform controls M2M data transmission accordingly in cooperation with M2M service application server described in step 1 to step 3 in normal flow 1.

Figure 12.2.6-2 Normal Flow 2 of Data Traffic Management by Underlying Network Operator

12.2.7 Alternative Flow

None

12.2.8 Post-conditions

None

12.2.9 High Level Illustration

Figure 12.2.9-1 High Level Illustration of Data Traffic Management by Underlying Network Operator

12.2.10 Potential Requirements

1. The M2M service platform SHALL be able to receive the data traffic condition information from the Underlying network and notify it to the M2M application server. The M2M application server SHALL be able to control M2M data transmission based on the Underlying Network data traffic condition.
2. The M2M service platform MAY SHALL be able to control M2M data transmission based on the Underlying Network data traffic condition.
3. The M2M device SHALL be able to control M2M data transmission based on the Underlying Network data traffic condition.
4. The M2M device SHALL control M2M application behavior implemented on top of M2M service layer when the M2M device received notification regarding Underlying Network data traffic condition from the Underlying Network.