3GPP-Protocol_details - Emergency Services Workshop

Protocol Details from
3GPP TS 24.229
SDO Emergency Services Coordination Workshop (ESW06)
Columbia University, New York
October 5-6, 2006
Atle Monrad, Ericsson Mobile Platform
([email protected])
Stage-3 specification ’philosophy’





3GPP TS 24.229 specifies the involved IMS entities
Reference relevant IETF-RFCs
Profile RFCs if only parts are supported
Specify additions and limitations
Work is ongoing and is planned to be completed by
mid-2007
© Ericsson AB 2006
2
2006-09-29
Involved entities




UE - User Equipment
Proxy-CSCF
Serving-CSCF
Emergency-CSCF
© Ericsson AB 2006
3
2006-09-29
UE – User equipment



Performs registration to the home IMS network
The emergency call is handled in the visiting network, thus a
dedicated emergency registration is needed when the terminal can
move out of the home network
Decides whether CS or IMS domain shall be used for initial
emergency call attempts
Can perform emergency call without SIM/UICC

Open issues:

-
© Ericsson AB 2006
when is a dedicated emergency registration needed?
How to indicate that location is not available?
How to transfer the equipment identifier?
4
2006-09-29
Proxy-CSCF


Is the initial point for communication with terminals
Is access-agnostic

Open issues:
-
© Ericsson AB 2006
when is a dedicated emergency registration needed?
How can the P-CSCF discover whether the terminal is in the home
network?
5
2006-09-29
Serving-CSCF


Is the central point in the home network handling the subscriber
Involved for emergency calls due to differences between normal
registrations and emergency registrations

Open issues:
-
© Ericsson AB 2006
No major
6
2006-09-29
Emergency-CSCF

Is the interface towards the PSAP

Open issues:
-
-
© Ericsson AB 2006
How to mark an emergency session after the PSAP address has
been resolved between the E-CSCF - PSAP and the E-CSCF MGCF?
The use of the Resource-Priority header?
MGCF interworking; any regulatory requirements?
7
2006-09-29
Other issues



Where shall the requirements on the PSAP be specified?
Call-back from the PSAP is currently not included.
The location is in current deployment often based on A-number
and cell-identity. Should LOST also consider these as ’valid
locations’, as existing databases in many cases are based on this?
© Ericsson AB 2006
8
2006-09-29
© Ericsson AB 2006
9
2006-09-29