12.10 Underlying network service activation and deactivation

12.10.1 Description

• Background of the use case
  Currently, for flexible M2M service deployments and low network service subscription cost, some underlying network operators have developed their private network service activation and deactivation APIs and opened them to M2M application providers. The M2M systems may need to support reusing the network service activation and deactivation capability provided by underlying network via transforming these network APIs and opening for M2M applications.
• Overview of the use case
  In the M2M device, a network service module (e.g. SIM card) will be embedded to support the network communication. For some potential requirements, the network service module need be activated or deactivated by remote or local M2M applications via M2M platform.
  In the context of this use case, an active network service module means that the network service module enables the M2M device to send / receive M2M traffic. An inactive network service module does not allow the M2M device to send / receive M2M traffic, however the service module, together with the M2M device, is capable to exchange signalling with M2M platform according to network operator's policy.
  The network entity of underlying network can activate/deactivate network service module according to network policy and network service activation/deactivation request.
  The following scenarios are given to show above requirements.
• Factory acceptance test
  During the factory acceptance test of the M2M device, the network service module need be activated for M2M service testing. After the test, the network service module need be deactivated for saving the network subscription cost.
• Starting usage
  When the M2M device are sold and the user starts to use it, the network service module need be activated to support the M2M service. The network service module may be activated via M2M platform by local M2M applications in the case that the local M2M applications detects the M2M device in use or by remote M2M applications in the case that the user requests the M2M application server to active the M2M device.
• Abandon
  When the M2M device is abandoned by user, the network service of the M2M device need to be deactivated for reducing network service subscription cost. In this case, the network service module will be deactivated via M2M platform by remote M2M applications.
• Lost
  When the M2M device is lost or stolen, the network service of the M2M device need be deactivated for reducing network service subscription cost. In this case, the network service module will be deactivated via M2M platform by remote M2M applications.
• Abused
  When the M2M device is misused by user (e.g. used for certain forbidden services), the remote M2M application server intends to stop providing M2M service and deactivate the network service of target M2M device via M2M platform.
  Similarly, if a M2M device is used outside a specific geographic area in which the M2M device is supposed to operate (e.g. a vending machine is removed from its assigned place) then a location enabled M2M device may deactivate the network service module.

12.10.2 Source

REQ-2014-0446R02 Underlying network service activation and deactivation use case

12.10.3 Actors

• Underlying network operator
• M2M service provider
• M2M Application server (operated by a M2M Application Service provider)
• M2M platform (operated by the M2M service provider)
• M2M device (containing a network service module)
• Network service module (operated by the Underlying network operator)

12.10.4 Pre-conditions

• The mobile network operator opens the service interface, i.e. network API, for remote activation and deactivation of underlying network service.

12.10.5 Triggers

The following triggers could initiate exchange of information.

Trigger A:

The M2M application on M2M device initiates the activation request. In this case, the M2M device is in use, and the M2M application intends to activate / deactivate the network service of the corresponding M2M device via an M2M platform.

(Note that even if the network service of the M2M device is deactivated, the M2M device may still be able to connect to target M2M platform according to the policy of network operator. )

Trigger B:

The M2M application server initiates the activation/deactivation request. In this case, the M2M application intends to activate / deactivate the network service of the target M2M device via M2M platform.

12.10.6 Normal Flow

Trigger A:
When the M2M device is in first use, network service activation request will be triggered by local M2M application on M2M device (Trigger A).

1. The M2M application on M2M device initiates the activation request to M2M platform.
2. The M2M platform uses the network service activation API provided by the underlying network operator to active the network service module of the corresponding M2M device and feedback the activation information.

Trigger B:
When the user intends to reuse the M2M device, network service activation request will be triggered by remote M2M application, and when the M2M device is misused by users, network service deactivation request will be triggered by remote M2M application. (Trigger B).

1. The M2M application server initiates the activation/deactivation request to M2M platform.
2. The M2M platform uses the network service activation/deactivation API provided by the underlying network operator to activate/deactivate the network service module of target M2M device and feedback the activation/deactivation information to the M2M application server.

12.10.7 Alternative Flow

None

12.10.8 Post-conditions

Trigger A:
The M2M device can send / receive M2M traffic if the network service module is activated successfully according to network activation request.

Trigger B:
The M2M device cannot send / receive M2M traffic but may be able to exchange signalling with M2M platform if the network service module is deactivated successfully according to network deactivation request.

12.10.9 High Level Illustration

Fig. 12.10.9-1 and Fig. 12.10.9-2 describe the normal flow of this use case for Trigger A and Trigger 2 from high level aspect.

Figure 12.10.9-1 - Normal flow description for Trigger A

Figure 12.10.9-2 - Normal flow description for Trigger B

12.10.10 Potential requirements

1. The M2M systems shall support the capability of reusing the network service activation and deactivation capability in underlying network via Mcn reference point.