ITU Workshop on the “Internet of Things Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Focus Group on
M2M Service Layer
Kaoru Kenyoshi (NEC)
(Kaoru.Kenyoshi@EMEA.NEC.COM )
On behalf of Heyuan Xu
FG M2M Chairman,
MIIT, China, xuheyuan@catr.cn
Geneva, Switzerland, 18 February 2014
International
Telecommunication
Union
Focus Group on M2M Service Layer
Focus Groups can be created for the quick
development of specifications (deliverables, not
Recommendations) in their chosen areas which
are not covered within an existing Study Group.
FG M2M initiated in April 2012
FG M2M concluded officially in December 2013.
M2M (Machine to Machine communication) covers
a wide area. FG M2M focuses initially on the
services and applications for e-health.
2
Focus Group on M2M Service Layer
Study areas of M2M service layer and
e-health
definitions, terminology, taxonomies
business model
use case
Network requirements
Network architecture
interface and protocols.
Collaborate with medical and clinical sector
(e.g. WHO, mHealth Alliance)
3
Objectives
Collect documents from other SDOs
Draft technical reports focused on M2M
service layer and e-health.
Facilitate and encourage the participation
and contribution of vertical market
stakeholders
4
Working Groups structure
FG Chairperson
Leadership: Heyuan Xu (CATR)
WG1 Use cases and service models
Leadership: M. Morrow (Cisco), R. Istepanian
(Kingston University), M. Berrebi (eDevice)
WG2 Requirements and architectural
framework of the M2M Service Layer
Leadership: M. Carugi (ZTE), H.J. Kim (ETRI)
WG3 API and protocols
Leadership: A. Amer(STC), H. Himeno (NEC)
5
Deliverables
No.
Title
Editors
M2M standardization activities and gap
analysis: e-health
Hideo Himeno (NEC)
D0.2
M2M enabled ecosystems: e-health
Marco Carugi (ZTE)
Cheng Li (CATR)
Jae-young Ahn (ETRI)
Hao Chen (CU)
D1.1
M2M use cases: e-health
Yasuo Ishigure (NTT)
Jun Seob Lee (ETRI)
D2.1
M2M service layer: requirements and
architectural framework
Jun Soeb Lee (ETRI)
Jiajia Deng (CT)
Yasunobu Akaoka
(NICT)
D3.1
M2M service layer: API and protocol
overview
Ali Amer (STC)
Hideo Himeno (NEC)
D0.1
6
Deliverables D0.1
M2M standardization activities and
gap analysis: e-health
Scope
The scope of this document is to provide a list of e-health related
standardization activities of relevant organizations and to produce a
gap analysis of relevant study items resulting in a work that could be
undertaken by the ITU-T.
•
•
•
•
•
•
•
•
•
•
•
•
•
WHO
CEN/TC 251
ISO/TC 215
Continua Health Alliance
GS1 Healthcare
DICOM
HL7
esSOS
IHE
mHealth Alliance
GSMA
ETSI TC M2M
ITU-T SG11,13,16,17
7
Deliverables D0.2
M2M enabled ecosystems: e-health
Scope
This deliverable provides an overview of the e-health ecosystem
enabled by M2M. The main objectives of this deliverable are to
describe concepts of e-health and the conceptual model of the ehealth ecosystem incorporating M2M capabilities. .
e-health system overview
8
Deliverables D1.1
M2M use cases: e-health
Scope
The main objective of this deliverable is to describe use cases of
e-health applications and services involving the usage of M2M
technologies..
No.
Use case title
1 Legacy mass medical
examination
2 Travelling mass medical
examination with BAN
3
4
5
Summary
This use case deals with a person who undergoes a mass medical
examination carrying an examination sheet.
This use case deals with a person who undergoes a travelling mass
medical examination using BAN-configured medical devices.
Remote patient monitoring This use case deals with Remote patient monitoring that typically
involves patient information collection by sensor devices and
transmission of this information through a wide area network.
Telehealth Counseling
This use case introduces Telehealth Counseling System that enables easy
System
and convenient health management and tele-consultation using video
phone.
Telehealth management
This use case introduces Telehealth Management System using NFC esystem using NFC e-health health device and smart phone to upload health data.
device and smart phone
Deliverables D1.1
M2M use cases: e-health
No.
Use case title
6 Telehealth system for
home care support
7
Ambient Assisted Living
(AAL)
8
Easy Clinic
9
Personal healthcare data
management
Summary
This use case introduces Telehealth system for healthcare in the home
using a Continua-based system with glucose meter and pulse oximeter.
This set of use case deals with AAL concerning the use of information
technology to assist the elderly, or people who are handicapped in any
way, in order to live a fully independent life.
This use case aims to make the monitoring process of remote patients in
general, and for elderly patients in particular simple and easy. It consists
of sending the remote patient readings (Blood Pressure and Sugar Level)
from the medical devices to the hospitals/ clinics through land line and
broadband connection or using smart phone.
This use case introduces the personal healthcare data management
system for consumers.
Healthcare data are collected through the gateway device, and the data
may be synchronized between the gateway device and the PHR server.
Note that the PHR server provides a Web service API for end user
access.
10 Expert system for medical This use case deals with medical doctor or institute accessing an expert
information/applications system for medical information/applications sharing.
sharing
10
Deliverables D2.1
M2M service layer: requirements and
architectural framework
Scope
The objective of this Deliverable is to identify common requirements
of M2M service layer for al M2M verticals including e-health specific
requirements, and provide architectural framework of M2M service
layer.
Management
capabilities
Application
layer
M2M
applications
DA
GA
NA
Security
capabilities
ITU-T M2M service layer
Service support and Application support layer
Specific support capabilities
Telematics
support
...
Networking capabilities
Network layer
Transport capabilities
Device layer
Device
capabilities
General security capabilities
e-health
support
Specific security capabilities
General management capabilities
Specific management capabilities
Generic
support
capabilities
Gateway
capabilities
ITU-T M2M service layer
11
Deliverables D3.1
M2M service layer: API and protocol
overview
Scope
This Deliverable provides an overview of APIs and protocols for the
M2M service layer and the related API and protocol requirements.At
first, it describes the technical reference model for a M2M enabled
system, including the reference points of the M2M service layer.
Then, APIs and protocols for M2M are introduced, including existing
APIs and protocols for M2M and M2M protocol structure and stacks.
Finally, API and protocol requirements with respect to the M2M service
layer are analysed.
M2M reference system model
12
Past meetings
in 2012
1st : April 17-18
Geneva
2nd: June 26-28
Beijing by CATR
3rd: August 29-31
Geneva
4th: November 13-15
San Jose by Cisco
in 2013
5th: January
22-24
Santander
by Univ. of
Cantabria
7th: April
27-30,
Riyadh by
STC
9th: July 16-19,
Bordeaux by edevice
11th: October
8-11,
Jeju by ETRI
12th:
December 3-6,
London by
NEC
6th, 8th and 10th meetings were e-meetings between F2F meetings.
13
Future plan
E-meeting will be held on 27 and 28 March 2014
and to review the 5 deliverables and the report
to SG11
Five deliverables will be transferred to the
relevant SGs of ITU-T (SG11, SG13 and SG16
etc) after concluding of FG M2M and each SG
studies them
14
Conclusion
Making unified consensus among countries is a
big challenge because of difference of economic
situation, culture, custom and regulation.
It is important to create specifications and
guidance by ITU for developing countries as well
as developed countries to introduce e-health
systems using M2M technology in an easy way.
FG M2M service layer has concluded in December
2013 and relevant SGs in ITU will succeed that
work. We are looking forward to close
collaboration with Continua Health Alliance, WHO
and other interested parties.
15
Thank you!
http://www.itu.int/en/ITU-T/focusgroups/m2m/Pages/default.aspx