Specialist Task Force 456:
eCall Transport
Who we are:
(back) Laurent Velez (TO)
(Front) Esa Barck (Chairman), Ban Al-Bakri, Robert Williams, David Williams
Team Leader: David Williams, Teleplus Ltd,
dhwillia@qti.qualcomm.com
Team Members: Robert Williams, CSI (UK) Ltd, bw_csi@fastmail.fm
Ban Al-Bakri, MeadowCOM,
ban.al-bakri@gmail.com
What we do:
We are investigating the long term solution for eCall.
For more details, see our
Terms of Reference
Why we do it:
eCall is being deployed on 2G and 3G networks but these will not last forever.
Already there are 4G networks, and cooperative ITS is on the horizon.
How we do it:
We are making proposals to 3GPP to show how eCall could be specified for 4G.
We are considering how eCall would migrate to 4G and ITS, and in this respect we
make presentations to as many eCall stakeholder organisations as possible (e.g.
EeIP, HeERO, CEN TC 278, ETSI TC ITS, ISO TC204) to get their views.
Deliverables:
TR 103 140. Technical Report on eCall in packet based networks, including
migration options to 4G and cooperative ITS.
- performance of eCall in-band modem on VoIP
- how eCall could be implemented in 4G specifications (IMS/LTE)
- migration options towards 4G and cooperative ITS.
The STF ToR foresees that Intermediate results have to be made openly
available via download from this dedicated STF page on the ETSI web site.
To this extent you can find here below final draft TR103140 v0.6.2, this is now
for stakeholder feedback and discussion and TB approval at the next MSG meeting
(MSG#38, 5-7 March 2014):
MSG-00eCall03v111_062
Final draft approved by MSG Meeting #38 (5-7 March 2014):
MSG-00eCall03v111_071
Presentation: "Migration of eCall Transport":
STF456_presentation_closing
Set of pseudo change requests to implement STF456 recommendations into 3GPP
specifications:
Time plan:
TR 103 140, interim draft, 50% complete, July 2013.
TR 103 140, final draft, near 100% complete, December 2013
TR 103 140 publication, early 2014.
How to contact us:
David Williams:
dhwillia@qti.qualcomm.com
This information is based upon STF working assumptions.
The views expressed do not necessarily represent the position of ETSI in this
context.
Last updated: 2014-03-19 16:40:30