[Sipping-emergency] RE: Emergency calls and 3GPP
"Drage, Keith (Keith)" <drage@lucent.com> Thu, 20 March 2003 19:20 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00662
for <sipping-emergency-archive@odin.ietf.org>;
Thu, 20 Mar 2003 14:20:10 -0500 (EST)
Received: (from mailnull@localhost)
by www1.ietf.org (8.11.6/8.11.6) id h2KJc8i18335
for sipping-emergency-archive@odin.ietf.org; Thu, 20 Mar 2003 14:38:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJc8O18332
for <sipping-emergency-web-archive@optimus.ietf.org>;
Thu, 20 Mar 2003 14:38:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00645
for <sipping-emergency-web-archive@ietf.org>;
Thu, 20 Mar 2003 14:19:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJc6O18322
for <sipping-emergency-web-archive@ietf.org>; Thu, 20 Mar 2003 14:38:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJbkO18275
for <sipping-emergency@optimus.ietf.org>; Thu, 20 Mar 2003 14:37:46 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00612
for <sipping-emergency@ietf.org>; Thu, 20 Mar 2003 14:19:16 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com
[135.86.145.57])
by ihemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id
h2KJLUQ14006
for <sipping-emergency@ietf.org>; Thu, 20 Mar 2003 14:21:30 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service
(5.5.2653.19) id <XNTCXGL2>; Thu, 20 Mar 2003 19:21:29 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC7A@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Atle Monrad (ETO)'" <Atle.Monrad@eto.ericsson.se>,
"Gonzalo Camarillo Gonzalez (LMF)" <Gonzalo.Camarillo@lmf.ericsson.se>,
"Drage, Keith (Keith)" <drage@lucent.com>
Cc: Emergency <sipping-emergency@ietf.org>
Date: Thu, 20 Mar 2003 19:21:27 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
charset="iso-8859-1"
Subject: [Sipping-emergency] RE: Emergency calls and 3GPP
Sender: sipping-emergency-admin@ietf.org
Errors-To: sipping-emergency-admin@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
<mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
<mailto:sipping-emergency-request@ietf.org?subject=subscribe>
A good summary Atle. As regards further input to requirements, I suspect that most of the requirements are already met by Hennings new requirements draft. Therefore I suspect what we need is a way of adding or modifying a small amount of additional material - Atle I suggest what we need is a review of the ietf requirements after the may SA2 meeting when things are a bit more solid, assuming that is not too late for ietf - plus some way of indicating which requirements or mechanisms are not relevant to 3GPP (e.g. the DNS lookup stuff for location). Keith Keith Drage Lucent Technologies Tel: +44 1793 776249 Email: drage@lucent.com > -----Original Message----- > From: Atle Monrad (ETO) [mailto:Atle.Monrad@eto.ericsson.se] > Sent: 20 March 2003 07:20 > To: Gonzalo Camarillo Gonzalez (LMF); Drage, Keith (Keith) > Cc: Emergency > Subject: RE: Emergency calls and 3GPP > > > Gonzalo > > I appreciate that you actively want to involve 3gpp at an > early stage in this issue. > > I would also like to take this opportunity to give you all > some background information about the emergency call feature > in 3gpp, and also a potential tutorial (for free due to the > financial situation of ietf). > > Currently, 3gpp supports emergency calls for CS, and enhanced > priority services (partly as a result of Sept. 11) is also > covered. This includes specification of a particular > emergency call handling setup, radio priority aspects and > setup from terminals without any subscription (without SIM-cards). > > Emergency call handling over packet based accesses, both GPRS > and UMTS-PS bearers do not exist in 3gpp releases up to and > including rel-5. In rel-5 where IMS is introduced, em-calls > shall be discovered by the handset and be set-up over CS. In > addition, if an INVITE destined for an emergency centre slips > through this filter and is sent from the UAC destined for an > em-center, an IMS proxy will stop the session set-up and > respond to the terminal to order CS to be used. > > ----- > > In rel-6, 3gpp will start working with emergency setups over > PS. Architectural aspects will be sorted out, impact on SIP > will be addressed, radio aspects will be identified, security > issues, possible impact on SIM-cards, conformance testing > (type approval), non-SIM card aspects, etc will be addressed. > > At present, the requirements and service aspects are > currently sorted out in the working group SA1 (work not finished). > > The working group SA2, where the architectural aspects are > outlined, has work ongoing, which first will result in a > technical report. This technical report will then be > converted into text suitable for the relevant 3gpp > specifications on the architectural level. > > As work in SA2 matures, the detailed work will be started and > will continue partly in parallell and as an iterative > process between architectural apsects and the details, > involving e.g. radio, core network signalling, and terminal -issues. > > Specification work for the protocol details on SIP-level is > specified in the CN (core network) groups. On CN-level, the > majority of this work is done by CN1. Our task is to use IETF > protocols to fulfil the 3gpp requirements without bending the > IDs and RFCs beyond what can be tolerated. If and when > needed, CN1 will address 3gpp issues to the relevant ietf > working group(s) in order to secure that the RFCs in the end > do fulfil our demands for an appropriate solution. I (as > rapporteur on CN-level for this work item) as well as other > will address requirements followed by solutions as things > mature a bit. > I do not know whether the format of our requirements towards > ietf best can be addressed as a req-id or as direct comments > to the list. > > Note that the current time schedule for 3gpp is to finalise > the emergency call work by the end of 2003, meaning that > feedback towards ietf can be expected quite soon. > > ----- > > Note also that the current work I am talking about is - to > say it in a popular way: > support for e.g. 911 or sos@domain over a PS connection. > > More work in the area, named Priority Multimedia Services > (yes; it has the abbr PMS) in 3gpp has just started in the > requirements and service aspects area, and may result in a > 2nd stage of emergency call handling over the PS-domain. > > /atle > > Best Regards > > Atle Monrad > ERICSSON > Wireless Data Terminals & Solutions > > Office: + 47 372 93 665 > Mobile: + 47 454 10 665 > Fax: + 47 372 94 058 > E-mail: atle.monrad@ericsson.com > Web-site: www.ericsson.com/mobileplatforms > > > -----Original Message----- > From: Gonzalo Camarillo Gonzalez (LMF) > Sent: Wednesday, March 19, 2003 10:32 PM > To: Drage, Keith (Keith); Atle Monrad (ETO) > Cc: Emergency > Subject: Emergency calls and 3GPP > > > Keith and Atle, > > the emergency calls design team within the SIPPING working group would > like to know which requirements 3GPP is taking into > consideration. Your > input would help the design team understand your needs. > > http://www.softarmor.com/sipping/teams/emergency/ > > Feel free to get in touch with the members of the design team and send > any message to the mailing list in the cc of this mail. > > Thanks, > > Gonzalo > _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- [Sipping-emergency] Emergency calls and 3GPP Gonzalo Camarillo
- [Sipping-emergency] RE: Emergency calls and 3GPP Atle Monrad (ETO)
- [Sipping-emergency] RE: Emergency calls and 3GPP Drage, Keith (Keith)