Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda Item: oneM2M-REQ R02

Background: Discussion on Cellular Network Evolution M2M Needs: A more streamlined network will be required to address handling of traffic with lower ARPU such as M2M. 3GPP is trying to solve this problem by streamlining network functionalities (= optimize network parameters) depending on the utilization characteristics of a specific device.  3GPP assumes these characteristics to be relatively static. OneM2M knows, they are not! Using Existing Mechanisms: currently it is discussed in 3GPP how to adjust configuration parameters or procedures per device, in order to maximize processing efficiency and reliability of a 3GPP network. Utilization characteristics: Mobility (Frequency, Velocity of movement), Communication characteristics (Frequency of communication establishment, Data Volume, Required Bandwidth, Acceptable Delay). E.g. For a stationary device(=low mobility), larger value of the Tracking Area Update Timer should be set For a chatty device (=communicates frequently), larger value should be set for the Inactivity Timer  3GPP is active on these issues. [SA2 has prioritized MTCe-SDDTE (Small Data and Device Triggering Enhancements) and MTCe-UEPCOP (UE Power Consumption Optimizations) building blocks for Rel-12] Page 2 Process to be adjusted (parameter) DetailBenefitUtilization characteristics relevant for tweaking network parameters UE Inactivity Timer (discussion on-going in SA2) The timer release the RRC connection expires signaling load reduced on connection management Frequency of session- establishment Paging Area (spec. completed)The area seeking a User EquipmentSignaling load reduced on pagingmoving range and frequency Location registration interval (spec. completed) The cycle interval between location (tracking area) Update signaling load reduced on location registration moving range and frequency DRX Timer (discussion on-going in SA2) The cycle interval between monitoring Paging Occasion for a specific UE Device battery savedAcceptable delay, Frequency of session-establishment Back off Timer (spec. completed) The timer include some time randomisation to guard against a repeat of a load peak Network congestion avoidedAcceptable delay, Frequency of session-establishment

What is needed (missing in oneM2M and in mobile network standards, e.g. 3GPP) For streamlined networks, it is needed to handle the case that utilization characteristics of specific device can vary dynamically. – 3GPP MTC assumes that the characteristics of a device are static. – However, in many cases the characteristics of a device vary depending on status of M2M service. (See the next slide) New Requirement: A mobile network shall be able to permanently optimize the Network functionalities of Mobility and Connectivity management (= adjust network parameters) depending on the change of device utilization characteristics. Method Proposal: The Service Platform captures device behavior (=changing of mobility/ utilization characteristics) to inform the mobile network so that the network can keep optimized control. (For details to the next slide) – A Service Platform could assemble a spectrum of data (communication characteristics from service level) which is unavailable in a mobile Network, to capture device behavior Page 3

Page 4 Example M2M Services (or Devices) which behavior (Mobility/Communication Characteristics) can vary ServiceMobility Characteristics (mobile – high and stationary – low) Communication Characteristics (Intervals of communication establishment) ITSMobility characteristic of device is Dynamic: Driving (mobile) or Parking (stationary) Communication characteristic: Dynamic Navigation aids: ON (  short interval) Navigation aids: OFF (  long interval) Logistics – traceability of cargo Delivering (mobile) or Loading in a freight distribution center (stationary) Delivering (short interval) or Loading (long interval) HealthcareIn the street (mobile) or At home (stationary) Communication characteristic of device may be Static or Dynamic Home/Office SecurityOut the door (mobile) or At home (stationary) Communication characteristic of device may be Static or Dynamic Smart MeterMobility characteristic of device is Static (device is not moving) Normal operation (long interval) or Out of order (short interval) AgricultureMobility characteristic of device may be Static (device is mounted in the field) or Dynamic (device is mounted on vehicle) Normal operation (long interval) or Out of order (short interval) Pet MonitoringOut the door (mobile) or At home (stationary) Normal operation (long interval) or Out of order (short interval) colour code: … characteristics are dynamic

Page 5 NEC proposal: NW increase in efficiency supported by M2M service Platform ITS Network dynamic control according to the terminal characteristic Behavior change detection of a terminal Electric power Transportation Health care Crime prevention M2M service PF Mobile Network (MME, S/P-GW, HSS, eNB) Smart Meter Car - The mechanism which detects the behavior change of a device - PF for notifying the behavior change of the detected device to NW The function to change a parameter in consideration of the information from service according to the behavior change of a device ・ Paging Area ・ Inactivity Timer Burglar alarm Sensor INPUT Truck

Use Cases of the NEC proposal Use cases – oneM2M-REQ Mobile network interworking (Mobility management) – oneM2M-REQ Mobile network interworking (Connectivity management) – etc. Underlying Network – 3GPP, etc. Information related to M2M devices that allows optimizations in the Underlying Network with regard to M2M traffic – Mobility characteristics of M2M devices – Data transmission interval of M2M devices – etc. Mobility characteristics – Speed range – Direction – etc. Services – Refer to slide 4 – etc.

Potential requirements – oneM2M  3GPP The M2M service platform shall be able to provide the Underlying Network with information related to M2M devices that allows optimizations in the Underlying Network with regard to M2M traffic. Examples of such useful information to a cellular network are: the current (or change of the) set of data transmission scheduling descriptors including interval times (5min, 30 min, 1h), time ranges(10pm-6pm) etc. of the M2M Device the current (or change of the) mobility characteristics including moving range (e.g. high mobility, low mobility, no mobility, or speed range), moving direction and moving speed, etc. of the M2M device Note 1: How to utilize such information by the cellular network is dependent on the Network Operator’s implementation and outside the scope of oneM2M. Note 2: The interface to convey such information to the Underlying Network will depend on the type (e.g. 3GPP, 3GPP2, fixed) of the Underlying Network – oneM2M (Application  Service Capability) The M2M service platform may be able to compute the information to be provided to the Underlying Network by analyzing the information received from the M2M Application before providing it to the Underlying Network

Complementary action in 3GPP Interface towards MTC-IWF (Tsp ??) needs to be enhanced to receive device characteristics from oneM2M 3GPP needs to be able to map such device characteristics into network parameter  New work items in 3GPP need to be created in Rel-13 (e.g. enhance WI “Support for interworking with M2M service enablement (MTCe-SIMSE)”  NEC would welcome support of companies for this work in 3GPP Rel-13!