1 概述
本文主要总结了IMS紧急服务相关概念,包括:
1) IMS 紧急服务的情况和处理过程,参考section 2.1
2) 紧急attach和紧急承载的概念,参见section 2.2
3) 紧急号码检测和处理,参见section 2.3
4) 紧急服务的相关消息和信元,参见section 4 和 5
2 IMS Emergency Service
2.1 概述
IMS紧急服务情况
NW type | 是否注册 | IP-CAN定义 紧急承载 | 其他 | 操作 |
home | 注册 | 否 | NA | 紧急呼叫,已普通注册 |
home | 注册 | 是【note1】 | NA | 先紧急注册,再紧急呼叫 |
home | 未注册 | NA | NA | 先紧急注册,再紧急呼叫 |
VPLMN | NA | NA |
| 先紧急注册,再紧急呼叫 |
NA | NA | NA | UE无法鉴权 | 紧急呼叫,无注册 |
Note:
UE 在VPLMN,须先紧急注册,再紧急呼叫
UE无法鉴权,可直接紧急呼叫,不需要注册
UE 在home PLMN,若已注册且IP-CAN未定义紧急承载,可直接紧急呼叫(已普通注册),其他情况均需先紧急注册,再紧急呼叫。
Note1: 同时需要网侧支持紧急承载。
IMS紧急服务相关过程
1) UE拨号时,UE根据本地紧急号码表检测号码,决定是否发起紧急服务
- 紧急服务的号码包括网侧下发紧急号码(ATTACHaccept/TAU accept),以及USIM/设备存储号码。
2) UE发起紧急服务时,需要发起紧急attach建立紧急承载
- 承载建立后,UE才可以紧急注册。
3) UE发起紧急注册
- UE需在紧急承载建立紧急注册
4) UE发起紧急呼叫
Note: 2)/3)的操作,某些场景可以省略,参见IMS紧急服务情况。
网侧对紧急承载的支持
网侧在Attach Accept和TAU accept通过EPS network feature support IE的EMC-BS来指示是否支持紧急承载。参见section 3.3,3.4,4.3
2.2 紧急attach和紧急承载
紧急attach
紧急attach用于紧急承载的建立,其attach request的EPS attach type为emrgency attach。
Note: 紧急attach携带的PDN连接请求必须是紧急PDN承载;
普通attach携带的PDN连接请求也可为紧急PDN承载。
相关信元具体参见section 3.1,4.1
紧急承载
紧急承载,可在普通或紧急attach携带,也可单独建立。其携带的RequestType为emergency bearer。
紧急PDN承载最多一个;
若UE attached,且仅包含一个承载,其为紧急PDN,则UE不可再建立其他PDN承载。
即UE普通注册时,若无紧急承载,可请求建立紧急承载。
相关信元具体参见section 3.2,4.2
2.3 紧急号码检测和处理
UE紧急号码检测
用户拨号时,UE应使用本地紧急号码列表,用于紧急号码检测。
UE存储的本地紧急号码列表,包括USIM/设备存储号码 + 网侧下发紧急号码;
UE仅保存唯一本地紧急号码列表,该列表可通过EMM过程更新。
该列表被UE注册和更新时可被下载。
网侧紧急号码发送
网侧可在ATTACH ACCEPT或TAUACCEPT发送紧急号码列表。参见3.3/3.4.
紧急号码列表内容为EmergencyNumber List IE,参见section 4.4
其格式基本为紧急号码种类+紧急号码,可包含多组紧急号码。
紧急号码种类如下(该域用一个字节低7位表示服务类型):
紧急号码种类 | 紧急号码 | BIT |
Police |
| Bit 1 |
Ambulance |
| Bit 2 |
Fire Brigade |
| Bit 3 |
Marine Guard |
| Bit 4 |
Mountain Rescue |
| Bit 5 |
manually initiated eCall |
| Bit 6 |
automatically initiated eCall |
| Bit 7 |
网侧紧急号码处理
UE在每次收到网侧新的网侧list后,更新本地紧急号码列表(USIM + 网络下发)
- UE 存储本地紧急号码列表时,应先删除与USIM/设备存储相同的号码(即USIM/设备存储号码优先)。
- 从网侧收到的紧急号码列表,仅对相同MCC的小区有效。
- UE应能存储网侧发来的10个紧急号码。
若ATTACH ACCEPT或TAU ACCEPT未包含紧急号码列表,则原存储列表保留,除非UE注册到了MCC不同的网络。
本地紧急号码列表在关机或USIM移除时删除。
相关信元具体参见section 4.4,4.5
3 相关消息
本章介绍如下消息:
消息类型 | 说明 |
Attach Request | 紧急attach相关 |
PDN connectivity request | 紧急PDN承载请求相关 |
Attach Accept | 1 EPS network feature support IE包含紧急承载支持标识EMC-BS 2 Emergency Number List IE包含网侧下发的紧急号码列表 |
TAU accept | 1 EPS network feature support IE包含紧急承载支持标识EMC-BS 2 Emergency Number List IE包含网侧下发的紧急号码列表 |
3.1 Attach request
note: attachrequest含EPS attach type(section5.1)指示是否emrgency attach
参考24301 section 8.2.4
3.2 PDN connectivityrequest
Note: PDN connectivity request包含Request Type(section4.2)指示是否为emergency bearer
引用24301 8.3.20.
3.3 Attach Accept
note: attach accept 含EPS network feature support和Emergency NumberList
EPS network feature support:包含网侧是否支持emergency bearer的指示,refer section 5.3
Emergency NumberList: 包含网侧提供的紧急号码,包括紧急服务类型和号码,
refer section 5.4
refer 24301section 8.2.1
3.4 TAU accept
note: TAU accept 含EPS network feature support和Emergency NumberList
EPS network feature support:包含网侧是否支持emergency bearer的指示,refer section 5.3
Emergency NumberList: 包含网侧提供的紧急号码,包括紧急服务类型和号码,refer section 5.4
refer24301 section 8.2.26
4 相关信元
本章介绍如下信元
消息类型 | 说明 |
EPS attach type | 用于attach request消息, 指示attach类型 |
request type | 用于PDN connectivity request消息 指示PDN请求类型 |
EPS network feature support | 用于Attach Accept和TAU accept消息 其中EMC-BS指示是否支持紧急承载 |
Emergency Number List | 用于Attach Accept和TAU accept消息 包含网侧支持的紧急消息列表 |
Service category | 用于Emergency Number List IE 指示紧急号码对应的服务类别 |
4.1 EPS attach type
Note: EPS attach type用于attach request消息(section 3.1)指示attach类型
attach type值为6表示为emergency attach,
引用24301 9.9.3.11
4.2 Request type
Note:requesttype用于PDN连接请求消息(section 3.2)中,指示请求类型。
request type值为4表示emergency,
引用24008 10.5.6.17
4.3 EPS networkfeature support
Note: 其中EMC-BS用于Attach Accept(section3.3)和TAU accept(section3.4)中,指示是否支持紧急承载
refer 24301 9.9.3.12A EPS network feature support4.4 Emergency NumberList
Note: Emergency Number List IE用于Attach Accept和TAU accept中,携带网侧下发的紧急号码列表,其中的服务种类参见section 4.5
refer 24301 9.9.3.37 Emergency NumberList
refer24008 subclause 10.5.3.134.5 Service category
Note: Service category类型用于网侧下发的Emergency Number IE(section 4.4)中,用于指示紧急号码对应的服务类型。
refer24008 10.5.4.33 Service category
5 24301 emergency bearer相关描述
3 Definitionsand abbreviations Attached for emergency bearer services: A UE is attached for emergency bearer services if it has only a PDN
--紧急承载attached,即UE attached,仅包含唯一PDN连接且该连接为紧急承载。
5.1.2 Types ofEMM procedures
Initiated by the UE and used to attach the IMSI or IMEI for emergencybearer services, and to establish an EMM context and a default bearer to a PDNthat provides emergency bearer services:
- attach.
--UE发起attach,用于为紧急承载服务attach IMSI或IMEI,建立EMM上下文和提供紧急服务PDN的缺省承载。
即紧急attach,应该仅包含紧急PDN请求,不含normal PDN请求。
5.5.1.2.5BAttach for initiating a PDN connection for emergency bearer services not accepted bythe network
If the network cannot accept attach request for initiating a PDNconnection for emergency bearer services with attach type not set to "EPSemergency attach", the UE shall perform the procedures as described insubclause 5.5.1.2.5.
-- 若网络拒绝了UE的attach请求,其携带紧急PDN承载请求,但attach type不是”EPS emergency attach”,按照5.5.1.2.5处理
即携带紧急PDN承载时,attach type可以不为emergency,是否支持由网侧决定。
6.5.1 UErequested PDN connectivity procedure
If there is already a PDN connection for emergency bearer servicesestablished, the UE shall not request an additional PDN connection foremergency bearer services.
A UE attached for emergency bearer services shall not request a PDNconnection to any other PDN.
--若UE已建立一个PDN紧急承载,UE不应请求额外的PDN紧急承载;
对UE 紧急承载attached,不应请求任何其他PDN的连接。
即,紧急PDN承载最多一个;
若只有一个承载且为紧急PDN时,不可再建立其他PDN承载。
6.5.1.2 UErequested PDN connectivity procedure initiation
If the additional PDN connection is for emergency bearer services, the UEshall not include an APN in the PDN CONNECTIVITY REQUEST message; otherwise theUE shall include the requested APN.
- 若额外的PDN承载请求是紧急承载,不应包含APN;否则UE应包含请求APN
6.5.3 UE requestedbearer resource allocation procedure
If there is a PDN connection for emergency bearer services established,the UE shall not request additional bearer resources for this PDN connection.
- 若PDN紧急承载已建立,UE不能为PDN连接请求额外的承载资源。
即, PDN紧急承载建立后,其上不能填加专有承载
6.5.4 UErequested bearer resource modification procedure
If there is a PDN connection for emergency bearer services established,the UE shall not request a modification of bearer resources for this PDNconnection.
- 若PDN紧急承载已建立,UE不能为PDN连接请求资源修改。
D.1 Mapping ofNAS procedure to RRC establishment cause (S1 mode only)
If an ATTACHREQUEST has EPS attach type set to "EPS emergency attach" or if theATTACH REQUEST has EPS attach type not set to "EPS emergency attach"but the UE initiates the attach procedure on receiving request from upper layerto establish emergency bearer services, the RRC establishment cause shall be set to
Emergency call. (See Note1)
--紧急attach时,或普通attach但带有紧急承载时,RRC建链cause为emergency call
5.3.7 Handlingof the Local Emergency Numbers List
-该章描述本地紧急号码的处理
The Local Emergency Numbers List contains additional emergency numbersused by the serving network. The list can be downloaded by the network to theUE at successful registration and subsequent registration updates. There isonly one Local Emergency Numbers List in the UE, and it can be updated with EMMprocedures if the UE is in S1 mode and with GMM and MM procedures if the UE isin A/Gb or Iu mode.
- 本地紧急号码列表包含网侧使用的额外紧急号码;该列表被UE注册和更新时可被下载。
- UE仅保存唯一本地紧急号码列表,可通过EMM过程更新。
The UE shall use the stored Local Emergency Numbers List received from thenetwork in addition to the emergency numbers stored on the USIM or userequipment to detect that the number dialled is an emergency number.
- UE应使用网侧收到的本地紧急号码列表,加上USIM或用户设备存储的紧急号码,用于紧急号码检测。
NOTE: The user equipment may use the emergency numbers list to assist theend user in determining whether the dialled number is intended for an emergencyservice or for another destination, e.g. a local directory service. Thepossible interactions with the end user are implementation specific.
The network may send a Local Emergency Numbers List in the ATTACH ACCEPTor in the TRACKING AREA UPDATE ACCEPT messages, by including the Emergency Number List IE. The user equipment shall store the Local Emergency Numbers List,as provided by the network, except that any emergency number that is alreadystored in the USIM shall be removed from the Local Emergency Numbers Listbefore it is stored by the user equipment. If there are no emergency numbersstored on the USIM, then before storing the received Local Emergency NumbersList, the user equipment shall remove from the Local Emergency Numbers List anyemergency number stored permanently in the user equipment for use in this case (see3GPP TS 22.101 [8]). The Local Emergency Numbers List stored in the user equipmentshall be replaced on each receipt of a new Emergency Number List IE.
- 网侧可以在ATTACH ACCEPT或TAU ACCEPT发送紧急号码列表。参见2.3/2.4.
- UE 存储本地紧急号码列表时,应先删除与USIM/设备存储相同的号码。(即USIM/设备存储号码优先)
- UE存储的本地紧急号码列表,在每次收到新的网侧list后更新。
The emergency number(s) received in the Emergency Number List IE are validonly in networks with the same MCC as in the cell on which this IE is received.If no Local Emergency Numbers List is contained in the ATTACH ACCEPT or in theTRACKING AREA UPDATE ACCEPT message, then the stored Local Emergency NumbersList in the user equipment shall be kept, except if the user equipment hassuccessfully registered to a PLMN with an MCC different from that of the lastregistered PLMN.
- 从网侧收到的紧急号码列表,仅对相同MCC的小区有效。
- 若ATTACH ACCEPT或TAU ACCEPT未包含紧急号码列表,则原存储列表保留,除非UE注册到了MCC不同的网络。
The Local Emergency Numbers List shall be deleted at switch off andremoval of the USIM. The user equipment shall be able to store up to ten localemergency numbers received from the network.
- 本地紧急号码列表在关机或USIM移除时删除。
- UE应能存储网侧发来的10个紧急号码。
6 参考协议
[1] 3GPP TS 24.229: "IP multimedia callcontrol protocol based on Session Initiation Protocol (SIP) and SessionDescription Protocol (SDP); Stage 3".
[2] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved PacketSystem (EPS); Stage 3".
[3] 3GPP TS 24.008: "Mobile radio interfacelayer 3 specification; Core Network protocols; Stage 3".
[4] 3GPP TS22.101: "Service aspects; Service principles".