Focus Group on M2M Service Layer

1
Focus Group on M2M Service Layer

• October 2013
• On behalf of SG11

2
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
• To conclude in December 2013.
• M2M (Machine to Machine communication) covers a
  wide area. FG M2M focuses initially on the
  services and applications for e-health.

3
Focus Group on M2M Service Layer

• Study areas of 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)

4
Objectives

• Collect documents from other SDOs
• Draft technical reports focused on e-health.
• Facilitate and encourage the participation and
  contribution of vertical market stakeholders

5
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)

6
Deliverables
No. Title Editors
D0.1 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)
7
M2M standardization activities and gap analysis
e-health
Deliverables D0.1

• Scope
• The scope of this document is to provide a list
  of e-health related standardization activities
  progressed by relevant SDOs and to produce a gap
  analysis resulting in a unique work that could be
  under the ITU-T purview.
• ITU-T (Q2/13 and Q28/16)
• WHO
• GSMA
• M-Health Alliance
• ETSI (M2M for use cases)
• HL7
• DICOM
• Continua Health Alliance
• ISO/IEC TC215)
• CEN TC251
• IHE

8
M2M enabled ecosystems e-health
Deliverables D0.2

• 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 e-health ecosystem incorporating M2M
  capabilities.

Application deployment examples of an e-health
system and their environments
9
M2M use cases e-health
Deliverables D1.1

• Scope
• The main objective of this deliverable is to
  describe use cases of e-health applications and
  services involving the usage of M2M technologies.
  Annex A contains some contributed use cases
  outside of the scope of the FG M2M (that is,
  these uses cases do not necessarily involve the
  usage of M2M technologies).

No. Use case title
1 Legacy mass medical examination
2 Travelling mass medical examination with BAN
3 Remote patient monitoring
4 Telehealth Counseling System
5 Telehealth management system using NFC health equipment and smart phone
6 Tele-health system for home care support
7 Ambient Assisted Living (AAL)
8 Easy Clinic
9 Personal healthcare data management
10 Expert system for medical information/applications sharing
10
M2M service layer requirements and architectural
framework
Deliverables D2.1

• 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.

ITU-T M2M service layer
11
M2M service layer API and protocol overview
Deliverables D3.1

• Scope
• This Deliverable provides an overview of APIs and
  Protocols of the M2M service layer and highlights
  the M2M reference system model, reference points,
  protocol structure and stacks. Existing APIs and
  protocols are summarized for better, and more
  complete, understanding. API and Protocol
  requirements are then analysed.

M2M protocol stack
12
Past meetings
in 2012
2nd June 26-28 Beijing by CATR
3rd August 29-31 Geneva
4th November 13-15 San Jose by Cisco
1st April 17-18 Geneva
in 2013
5th January 22-24 Santander by Univ. of
Cantabria
7th April 27-30, Riyadh by STC
9th July 16-19, Bordeaux by e-device
11th October 8-11, Jeju by ETRI
6th, 8th and 10th meetings were e-meetings
between F2F meetings.
13
Future meeting plan

• 12th 3-6 December 2013, London by NEC

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 for further standardizations.
14
Conclusion

• Reaching consensus amongst differences in
  cultures, economies, etc., is no easy task
• The goal of ITU is to create specifications and
  guidance for developing countries. It is also
  important that developing countries roll out
  e-Health systems using M2M technology based on
  documentation created at ITU by member states.
• FG M2M service layer work will concluded December
  2013. Going forward, relevant SGs in ITU will
  continue the work. ITU feels it is important to
  keep close collaboration with Continua Health
  Alliance and WHO.

15
Thank you!
http//www.itu.int/en/ITU-T/focusgroups/m2m/Pages/
default.aspx