Transcript TR50-20101006-011_ALU__TR

Machine-to-Machine(M2M)
Communication for
cdma2000 Systems
Orlett W. Pearson, 3GPP2 LS to TR-50
October 2010
M2M Study - Scope
• Identify applicable M2M communications use cases and characteristics.
• Identify the list of potential requirements needed to enable machine type
communications on cdma2000 networks based on the identified M2M service
functionalities.
• Identify possible enhancements that would help in providing cdma2000
network operators with lower operational complexities when offering
machine-type communication services
• Evaluate the impact of the anticipated large number of M2M devices and how
to minimize this impact on the cdma2000 networks; e.g., Group Based.
• Optimize network operations that can minimize the impact on device battery
power usage.
2 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50
3GPP2 M2M Activity
• 3GPP2 SC Ad Hoc on M2M Numbering and Addressing
• M2M Study work being developed in TSG-S
— Completion date: 4Q2010
— Items being addressed: recognizing a potentially large number of communicating
devices, lower costs and less effort, data communications (packet/circuit switch),
majority of these communications involve small to little traffic
• TSG-X kicked off an M2M joint session with TSG-A and TSG-C (September)
— Introduced Network Optimizations
— M2M E2E Procedures
— Architecture
3 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50
M2M Study – Characteristics Being Considered
Low Mobility - M2M devices that have a limited
Infrequent Transmission - Used with M2M devices
scope of movement.
that are expected to send or receive data with a
Time Controlled - M2M Applications that can
tolerate sending or receiving data during certain
long period of time between two data
transmissions.
time intervals in order to avoid unnecessary
Group Based M2M Characteristics, Group Based
signalling.
Policy, Group Based Addressing - A group of M2M
Time Tolerant - M2M devices that can postpone
their data transmission (load conditions).
Location Specific Trigger – Used to trigger M2M
devices that are known by the M2M Application to
be in a particular area or location.
devices which could share the same subscription
and a common set of M2M characteristics can be
handled by the network as a group rather than
individually.
Priority Access - Used with M2M devices
that need to communicate information in an
Uplink Data for Provided Network Destination -
emergency situation, and may be related to
Used with M2M Applications that require all data
public safety.
from a M2M device to be sent to a specific
network (using IP address).
4 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50
M2M Study – Use Cases
 The group is reviewing various Use Cases relative to groups. A few are
noted:
 Smart Metering
– Fixed to Low Mobility, Small Data Transmission, Time Controlled, Groupbased Policy, Group-based Billing, Group-based Addressing
 Professional Health Care Monitoring
– Low Mobility, Small Data Transmission, High Priority
 Fleet Management Tracking
– Small Data Transmission, Mobile Device, Group-based Billing
 Public Safety
– Priority Access, Small Data Transmission, Group-based Policy
 Payment Machine
– Fixed or low mobility. Some payment terminals (e.g., hand-held credit
card machines used in restaurants) have low mobility. Exception cases
include vending machines on high-mobility transportation (e.g., trains).
 Group-based address & policy - The operator might want to address this type of
device on a group basis.
5 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50
M2M Study – Terminal Security
Terminal Security:
 M2M devices might use detachable device such as M2M UICC with CSIM
application or R-UIM to store subscription information for M2M applications.
 Since many M2M terminals might be installed outside and not monitored in
real time, the detachable device for storing subscription information
would create security issue.
 Develop a mechanism to prevent theft, tampering with subscription
credentials and subscription information.
 May need to develop some special mechanism to authenticate M2M
terminals.
6 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50
M2M Study Battery Life
 Battery Life Improvement for Battery Operated M2M Devices:
—Many M2M devices might not need to periodically wake up to monitor the network
— providing an opportunity to save battery life by configuring M2M devices
for different sleep duration and wakeup time.
— Reducing unnecessary re-transmissions of M2M application packets.
Consider categorizing M2M applications (allow more transmission
delay/response:
 Low sensitive latency
 Medium sensitive latency
 High sensitive latency
7 | 3GPP2 M2M | October 2010 3GPP2 LS to TIA TR-50