Transcript oneM2M-REQ-2013-0136R02

oneM2M-REQ-2013-0136R02
Optimized M2M interworking
with mobile networks
Group Name: oneM2M REQ
Source: Takanori Iwai, NEC, ([email protected])
Meeting Date: 2013-02-25
Agenda Item: <agenda item topic name>
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]
Process to be adjusted
(parameter)
Detail
Benefit
Utilization 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 sessionestablishment
Paging Area (spec. completed)
The area seeking a User Equipment
Signaling load reduced on paging
moving 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 saved
Acceptable 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 avoided
Acceptable delay, Frequency of
session-establishment
Page 2
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
Example M2M Services (or Devices) which behavior
(Mobility/Communication Characteristics) can vary
Service
Mobility Characteristics
(mobile – high and
stationary – low)
Communication Characteristics
(Intervals of communication
establishment)
ITS
Mobility 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)
Healthcare
In the street (mobile) or
At home (stationary)
Communication characteristic of device may
be Static or Dynamic
Home/Office Security
Out the door (mobile) or
At home (stationary)
Communication characteristic of device may
be Static or Dynamic
Smart Meter
Mobility characteristic of device is Static
(device is not moving)
Normal operation (long interval) or
Out of order (short interval)
Agriculture
Mobility 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 Monitoring
Out the door (mobile) or
At home (stationary)
Normal operation (long interval) or
Out of order (short interval)
colour code:
… characteristics are dynamic
Page 4
NEC proposal:
NW increase in efficiency supported by M2M service Platform
ITS
Electric
Transportation
power
Health care
Behavior change
detection of a
terminal
M2M service PF
Crime
prevention
- The mechanism which detects
the behavior change of a device
- PF for notifying the behavior change
of the detected device to NW
INPUT
Network dynamic
control according to
the terminal
characteristic
Mobile Network
(MME, S/P-GW,
HSS, eNB)
Car
The function to change a parameter in
consideration of the information from
service according to the behavior
change of a device
Smart
Meter
Truck
Sensor
・Paging Area
・Inactivity Timer
Burglar
alarm
Page 5
Use Cases of the NEC proposal
• Use cases
– oneM2M-REQ-2013-0137 Mobile network interworking (Mobility management)
– oneM2M-REQ-2013-0231 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 Rel13 (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!