Upload
others
View
23
Download
0
Embed Size (px)
Citation preview
中 国 移 动 通 信 企 业 标 准
位置业务 Lp 接口规范
Lp Interface Specification For LSP
Interconnection
版 本 号 : 2.0 . 0
中国移动通信有限公司 发布
20 0 7 - 9 - 1 8 发 布 2 0 0 7 - 9 - 1 8 实 施
QB-D-121-2007
QB-D-121-2007
I
目 录 1. 范围...........................................................................................................................................1 2. 规范性引用文件.......................................................................................................................1 3. 术语、定义和缩略语...............................................................................................................1
3.1. 符号和语法...................................................................................................................2 3.1.1. 符号...........................................................................................................................2 3.1.2. 语法说明...................................................................................................................2
4. 协议...........................................................................................................................................3 4.1. 协议概述.......................................................................................................................3 4.2. 协议结构.......................................................................................................................3 4.3. 协议扩展机制...............................................................................................................3
5. 协议说明...................................................................................................................................3 5.1. DTD 文档解析 .............................................................................................................4 5.2. 不合法取值(Invalid Values) ....................................................................................4 5.3. QoP ...............................................................................................................................4 5.3.1. 请求消息中的 QoP...................................................................................................4 5.3.2. 应答/报告消息中的 QoP..........................................................................................4 5.4. 位置信息的类型(Types of Location Information) ..................................................5 5.4.1. 请求消息的位置信息...............................................................................................5 5.4.2. 应答/报告消息中的位置信息..................................................................................6 5.5. 定位请求处理优先级...................................................................................................6 5.6. 目标用户标识...............................................................................................................6
6. Lr 协议具体定义 ......................................................................................................................6 6.1. 传输层定义...................................................................................................................6 6.2. 元素层定义...................................................................................................................6 6.2.1. Identity Element Definitions .....................................................................................6 6.2.2. Function Element Definitions ...................................................................................6 6.2.3. Location Element Definitions ...................................................................................8 6.2.4. Result Element Definitions .......................................................................................9 6.2.5. Shape Element Definitions........................................................................................9 6.2.6. Quality of Position Element Definitions ...................................................................9 6.2.7. Network Parameters Element Definitions.................................................................9 6.2.8. Roaming Context and Privacy Element Definitions ...............................................11 6.3. 服务层定义.................................................................................................................12 6.3.1. 头信息结构.............................................................................................................12 6.3.2. Standard Roaming Location Immediate Service.....................................................14 6.3.2.1. Standard Roaming Location Immediate Request DTD.......................................14 6.3.2.2. Standard Roaming Location Immediate Answer DTD .......................................15 6.3.2.3. Standard Roaming Location Immediate Report DTD.........................................16 6.3.3. Triggered Roaming Location Reporting Service.....................................................17 6.3.3.1. Triggered Roaming Location Reporting Request DTD ......................................18
<trlrr ver="2.0.0" recv_role="HLS"> .....................................................................19
QB-D-121-2007
II
<change_area type="MS_ENTERING" loc_estimates="TRUE"> ..........................19 <name_area>Seoul</name_area>......................................................................................19 <target_area> .........................................................................................................................20
6.3.3.2. Triggered Roaming Location Reporting Answer DTD .......................................21 6.3.3.3. Triggered Roaming Location Report DTD .........................................................21 6.3.3.4. Triggered Roaming Location Reporting Stop Request DTD ..............................22 6.3.3.5. Triggered Roaming Location Reporting Stop Answer DTD...............................23 6.3.4. Emergency Roaming Location Immediate Service.................................................23 6.3.4.1. Emergency Roaming Location Immediate Request DTD...................................23 6.3.4.2. Emergency Roaming Location Immediate Answer DTD....................................24 6.3.5. Standard Roaming Subscriber Authentication Service............................................25 6.3.5.1. Standard Roaming Subscriber Authentication Request DTD..............................25 6.3.5.2. Standard Roaming Subscriber Authentication Answer DTD ..............................25 6.3.6. Standard Roaming Location Reporting Service ......................................................26 6.3.6.1. Standard Roaming Location Report DTD...........................................................26 6.3.6.2. Standard Roaming Location Report Answer DTD..............................................27 6.3.7. General Error Message Definition ..........................................................................27
7. 元素及属性定义.....................................................................................................................28 7.1. pseudoid ......................................................................................................................28 7.2. uc_id............................................................................................................................28 7.2.1. status .......................................................................................................................28 7.3. sac ...............................................................................................................................29 7.4. client............................................................................................................................29 7.4.1. type..........................................................................................................................29 7.5. clientname ...................................................................................................................30 7.6. imsi..............................................................................................................................30 7.7. poi ...............................................................................................................................30 7.7.1. flag ..........................................................................................................................31 7.8. serving_node_action ...................................................................................................31 7.8.1. passive_type ............................................................................................................31 7.8.2. active_type ..............................................................................................................32 7.9. nmr_element................................................................................................................32 7.9.1. arfcn ........................................................................................................................33 7.9.2. bsic ..........................................................................................................................33 7.9.3. rxlev ........................................................................................................................33 7.10. pce ...........................................................................................................................34 7.11. servicetype ..................................................................................................................34 7.12. sgsnid ......................................................................................................................34 7.12.1. capability.................................................................................................................35 7.13. ta..............................................................................................................................35 7.14. requestmode ............................................................................................................35 7.14.1. type..........................................................................................................................36 7.15. vlrid .........................................................................................................................36 7.15.1. capability.................................................................................................................36
QB-D-121-2007
III
7.16. vlrno ........................................................................................................................37 7.17. v_ls ..........................................................................................................................37 7.18. vmscid .....................................................................................................................37 7.18.1. capability.................................................................................................................38 7.19. vmscno ....................................................................................................................38 7.19.1. h_ls ..........................................................................................................................39 7.20. lcs_ref......................................................................................................................39 7.21. service attributes......................................................................................................39 7.21.1. recv_role..................................................................................................................39 7.22. supported_shapes ....................................................................................................40 7.22.1. Point ........................................................................................................................40 7.22.2. Linestring ................................................................................................................40 7.22.3. Polygon ...................................................................................................................41 7.22.4. Box..........................................................................................................................41 7.22.5. CircularArea............................................................................................................41 7.22.6. CircularArcArea......................................................................................................42 7.22.7. EllipticalArea ..........................................................................................................42 7.22.8. MultiLineString.......................................................................................................43 7.22.9. MultiPoint ...............................................................................................................43 7.22.10. MultiPolygon ......................................................................................................43 7.22.11. LinearRing ..........................................................................................................44 7.22.12. Altitude................................................................................................................44 7.23. primaryscramblingcode...........................................................................................44 7.24. uarfcn_ul .................................................................................................................45 7.25. uarfcn_dl .................................................................................................................45 7.26. uarfcn_nt .................................................................................................................45 7.27. nid ...........................................................................................................................45 7.28. sid ............................................................................................................................46 7.29. base_id ....................................................................................................................46 7.30. base_lat....................................................................................................................46 7.31. base_long ................................................................................................................47 7.32. ref_pn ......................................................................................................................47 7.33. sgsnno......................................................................................................................47 7.34. locationserver ..........................................................................................................48 7.35. post_auth .................................................................................................................48 7.36. posfixlspid...............................................................................................................48 7.37. target........................................................................................................................49 7.38. collab_id..................................................................................................................49
8. 结果码定义.............................................................................................................................49 LSP MISCONFIGURATION AND AGPS POSITIONING FAILURE .........................................50 LID 数据缺失且 AGPS 定位失败。该结果码仅用于 AGPS 返回 LSP 的应答/报告消息,接收
该结果码的 LSP 不再发起 Cell ID 定位作为回退的定位方法。 ..............................................50 AGPS POSITIONING FAILURE-- NEITHER LID POSTION NOR GPS POSTION .................50 AGPS 平台发送定位请求给终端,但终端无应答消息或发送异常应答消息。该错误码仅用于
QB-D-121-2007
IV
LSP 与 AGPS 平台之间。.............................................................................................................50 TARGET RECORDED AS A NON-SUPL –ENABLED-TERMINAL..........................................50 AGPS 平台判断该终端非 AGPS 终端,返回错误结果。..........................................................50 9. HTTP 映射..............................................................................................................................50
9.1. Location Services using HTTP ...................................................................................50 9.2. 定位请求和应答封装.................................................................................................51 9.2.1. Inter-Location Server Service Initiation DTD.........................................................51 9.2.2. Inter-Location Server Service Result DTD .............................................................52
10. 与 Lr2.0.0 的差别 ...........................................................................................................54 11. 编制历史.........................................................................................................................54 附录 A Server side requirements (Normative)................................................................................54
A.1 Server side requirements (Normative) .............................................................................54 A.1.1 General Requirements ...................................................................................................54 A.1.2 Inter-Location Server Service Initiation DTD...............................................................54 A.1.3 Inter-Location Server Service Result DTD ...................................................................55 A.1.4 Roaming Header............................................................................................................56 A.1.5 Standard Roaming Location Immediate Request ..........................................................56 A.1.6 Standard Roaming Location Immediate Answer...........................................................57 A.1.7 Standard Roaming Location Immediate Report ............................................................57 A.1.8 Triggered Roaming Location Reporting Request..........................................................57 A.1.9 Triggered Roaming Location Reporting Answer ..........................................................58 A.1.10 Triggered Roaming Location Report...........................................................................58 A.1.11 Triggered Roaming Location Reporting Stop Request................................................58 A.1.12 Triggered Roaming Location Reporting Stop Answer ................................................58 A.1.13 Emergency Roaming Location Immediate Request ....................................................59 A.1.14 Emergency Roaming Location Immediate Answer.....................................................59 A.1.15 Support for Identity Elements .....................................................................................59 A.1.16 Support for Function Elements ...................................................................................60 A.1.17 Support for Location Elements....................................................................................60 A.1.18 Support for Result Elements .......................................................................................60 A.1.19 Support for Shape Elements ........................................................................................61 A.1.20 Support for Quality of Position Elements ...................................................................62 A.1.21 Support for Network Parameter Elements...................................................................62 A.1.22 Support for Roaming Context and Privacy Elements..................................................63 A.1.23 Service attributes.........................................................................................................63 A.1.24 Standard Roaming Subscriber Authentication.............................................................63 A.1.25 Standard Roaming Location Report Answer ...............................................................63 A.1.26 Standard Roaming Location Report ............................................................................64 A.1.27 Transport mechanisms.................................................................................................64 A.1.28 Services .......................................................................................................................64 A.2 Client side requirements...................................................................................................65 A.2.1 General Requirements ...................................................................................................65 A.2.2 Inter-Location Server Service Initiation DTD...............................................................65 A.2.3 Inter-Location Server Service Result DTD ...................................................................66
QB-D-121-2007
V
A.2.4 Roaming Header............................................................................................................67 A.2.5 Standard Roaming Location Immediate Request ..........................................................67 A.2.6 Standard Roaming Location Immediate Answer...........................................................67 A.2.7 Standard Roaming Location Immediate Report ............................................................67 A.2.8 Triggered Roaming Location Reporting Request..........................................................68 A.2.8 Triggered Roaming Location Reporting Answer ..........................................................68 A.2.10 Triggered Roaming Location Report...........................................................................68 A.2.11 Triggered Roaming Location Reporting Stop Request................................................69 A.2.12 Triggered Roaming Location Reporting Stop Answer ................................................69 A.2.13 Emergency Roaming Location Immediate Request ....................................................69 A.2.14 Emergency Roaming Location Immediate Answer.....................................................69 A.2.15 Support for Identity Elements .....................................................................................70 A.2.16 Support for Function Elements ...................................................................................70 A.2.17 Support for Location Elements....................................................................................70 A.2.18 Support for Result Elements .......................................................................................71 A.2.19 Support for Shape Elements ........................................................................................71 A.2.20 Support for Quality of Position Elements ...................................................................72 A.2.21 Support for Network Parameter Elements...................................................................72 A.2.22 Support for Roaming Context and Privacy Elements..................................................73 A.2.23 Service attributes.........................................................................................................73
A.2.24 Standard Roaming Location Report Answer.......................................................................74 A.2.25 Standard Roaming Location Report ....................................................................................74
A.2.26 Transport mechanisms.................................................................................................74 A.2.27 Services .......................................................................................................................74
QB-D-121-2007
VI
前 言
本标准描述了中国移动定位服务系统 Lp 接口规范,此接口用于 LSP 平台与
AGPS 平台之间的定位请求和应答交互。本标准目标读者为省公司 LBS 业务技术
人员和业务人员、AGPS 平台、LSP 设备提供商技术人员。
本标准包括以下几方面内容协议、协议说明、Lr 协议具体定义、元素及属性
定义、结果码定义等。
本标准的附录 A为标准性附录。
本标准由中移有限技[2007]153 号印发。
本标准由中国移动通信有限公司技术部提出并归口。
本标准由标准归口部门负责解释。
本标准起草单位:中国移动通信有限公司研究院
本标准主要起草人:林智,于蓉蓉,陈心昕,陈莉华
QB-D-121-2007
1
1. 范围
本规范对中国移动开通的LBS业务中LSP平台和AGPS平台之间的接口协议进行了规定。
包括消息的类型和消息的元素的定义。
开通 LBS 业务的中国移动各省公司和 LBS 平台提供商在向中国移动提供 LBS 业务时,应
遵循本规范。
2. 规范性引用文件
下列文件中的条款通过本标准的引用而成为本标准的条款,其最新版本适用于本标准。
[1] 中国移动位置业务(LBS)总体技术要求
V1.1.0
中国移动通信有限公
司
[2] 中国移动位置业务(LBS)LSP设备技术规范
V1.1.0
中国移动通信有限公
司
[3] OMA-LIF-ROAMPROT-V1_0_0-20030319-D
LIF
[4] Hypertext Transfer Protocol –HTTP/1.1 RFC 2616, June 1999
IETF
[5] Extensible Markup Language (XML) 1.0 W3C
Recommendation: REC-xml-20001006
IETF
[6] OMA-TS-RLP-V1_0-20051124-C Open Mobile
Alliance
[7] OMA-TS-MLP-V3_2-20051124-C Open Mobile
Alliance
[8] 位置服务Le接口技术规范V2.0.0
[9] “OMA Interoperability Policy and
Process”, Version 1.1,
OMA-IOP-Process-V1_1
Open Mobile
Alliance
3. 术语、定义和缩略语
在本规范中使用了“必须”、“推荐”/“建议”、和“可选”等词汇来描述对移动终端产
品要求的强调程度。
“必选”/“必须”项是指终端产品所必须提供的功能或性能要求;对应于 RFC2119 MUST,REQUIRED,SHALL。
QB-D-121-2007
2
“推荐”/“建议”项是指在标准中未作强制要求,若终端产品提供的功能或性能要求
被认为更佳;对应于 RFC2119 RECOMMENDED,SHOULD。
“可选”/“可”项指参考性要求,是终端产品在目前阶段可不提供的功能或性能要求;
对应于 RFC2119 MAY,OPTIONAL。
必不能,不能,不得:表示绝对的禁止;对应于 RFC2119 MUST NOT,SHALL NOT。
不推荐,不建议:表示若产品按照所述内容制作,被认为略次;对应于 RFC2119 SHOULD
NOT,NOT RECOMMENDED。
规范中除了明确指明为 “推荐”/“建议”、“可选”外,均为必须要求。 AGPS Assisted Global Position System
CMLP CMCC Mobile Location Protocol
DTD Document Type Definition
LSP Location Service Platform
GMT Greenwich Mean Time
HTTP Hypertext Transfer Protocol
HTTPS HTTP Secure
LCS Location Services
MS Mobile Station
MSID Mobile Station Identifier
SSL Secure Socket Layer
URI Uniform Resource Identifier
URL Uniform Resource Locator
XML Extensible Markup Language
3.1. 符号和语法
3.1.1. 符号
SP Space 空格
CRLF “\r\n” 回车换行
3.1.2. 语法说明
[a-z] 任意小写字母
[A-Z] 任意大写字母
[0-9] 任意数字
{min,max} 重复次数大于等于min,小于等于max
[a-z,A-Z,0-9] 任意字母及数字
+ 一次或多次出现
* 零次或多次出现
? 可选
() 多个表达式合成一个整体
| 多选一
QB-D-121-2007
3
, 严格的序列,与AND相同
4. 协议
4.1. 协议概述
中国移动位置业务接口协议在网络结构中位置如下图所示:
Le
Lup
Lr,Lp
Lr,Lp
Lr
LSP
AGPS
� � � � � LCS Client�
LSP
图 5.1 位置业务接口示意图
本规范只对 Lp 进行规定,Le 接口规范参见《中国移动位置业务 Le 接口技术规范》,
Lr 接口规范参见《中国移动位置业务 Lr 接口技术规范》。 Lp 与 Lr 接口的差别见 10。
4.2. 协议结构
参考《中国移动位置服务 Le 接口技术规范》相关部分。
4.3. 协议扩展机制
参考《中国移动位置服务 Le 接口技术规范》相关部分。
5. 协议说明
本文在 OMA-TS-RLP-V1_0-20051124-C 基础上定义,不作特殊说明,名词术语的对应
如下: Service 服务
QB-D-121-2007
4
Element 元素 Attribute 属性
5.1. DTD文档解析
DTD 文档与本规范共同发布。 LSP 必须解析所有 RLP XML 文档。LSP 接收 XML 文档后若语法不合 XML 语法规定,
必须返回错误码 106(SYNTAX ERROR)。不遵守 RLP 协议规定,LSP 必须返回错误码 105, 110 或 111。
即使有些字段是可选字段,有些服务 LSP 不支持(未实现),LSP 必须解析所有符合语
法的字段,返回适当的错误码。例如,若 LSP 不支持 Emergency Roaming Location Immediate Request,LSP 必须解析该 XML 文档,并返回错误码表示 LSP 不支持该服务(108)。
5.2. 不合法取值(Invalid Values)
本协议中规定多数元素和属性的取值和范围。如果有值超出该规定(例如精度值为负
值),则对于元素取值错,LSP 必须返回"INVALID PROTOCOL ELEMENT VALUE"错误,
对于属性取值错,LSP 必须返回"INVALID PROTOCOL ELEMENT ATTRIBUTE VALUE"。
5.3. QoP
QoP(Quality of position)表示一个或多个如下指标(这些指标可有优先级要求,详见
eqop 元素子元素 resp_req 子元素): 期望响应时间(Response time requirement)。即业务平台期望 LSP 响应的时间 定位结果时间范围(Age of the location information)。每个定位结果有一个时间戳,
该指标表示结果的时效性。 定位精度(Accuracy of the location information),由系统估计。
5.3.1. 请求消息中的 QoP
定位结果时间范围 LSP 可规定一个最长的时间范围即 max_loc_age。该参数用于 LSP 判断某一个位置
信息是否足够及时。 位置信息的精确度(Accuracy of location information) LSP 可使用 QoP 定义精确度,该参数用于 LSP 或网络选择适当的定位技术以满足 QoP
要求。
5.3.2. 应答/报告消息中的 QoP
位置信息最大时间(Maximum age of location information) 1. 应答/报告消息必须包含位置信息最大时间(通过时间戳元素表示,除非无法得知)。
时间戳必须定义计算该位置信息的时间点,该时间点需标明时区或 GMT 时差。
QB-D-121-2007
5
2. 若无请求消息中无位置信息最大时间,该参数取决于 LSP 设置,即 LSP 可尽力而为
地获取位置信息,可使用最有效的定位方法,使用保存的位置信息。应答/报告消息
必须包含位置信息最大时间(通过时间戳元素表示,除非无法得知)。 3. 实际的位置信息最大时间可比请求的数值大,LSP 必不能将该信息翻译为错误信息。
若时效性重要,建议业务平台检查时间戳。传递的 LSP(例如接入地 LSP 将从归属
地 LSP 获得的定位结果传递给业务平台)必不能修改该参数。 位置信息的定位精度 任何定位精度信息与位置信息计算时间点相关,通过时间戳表示。 若请求消息中无特定定位精度元素,定位精度由 LSP 设置,即 LSP 可尽力而为地获取
位置信息,可使用最有效最精确的定位方法。(默认采用 Cell ID 定位方式)。LSP 必须返回
定位精度值(除非无法得知)。 实际的位置信息的定位精度可比请求的精度弱,即使定位精度比请求弱,LSP 必不能将
该信息翻译为错误信息。若定位精度值重要,建议应用平台检查返回的位置信息的该元素值。 定位精度的可信度(Confidence of accuracy information) LSP可标明位置信息的可信度,如“65%的可信度”,LSP在应答/报告消息中通过 lev_conf
元素表示定位精度的可信度。若应答/报告消息中无 lev_conf 元素,则定位精度的可信度未
被标明。lev_conf 元素的父元素为 pd 元素。 请求消息中的 QoP 无法满足 LSP 若无法获取满足 QoP 的位置信息(此时 qos_class=BEST_EFFORT),计算定位结果
的 LSP 必须(SHALL)设置 qop_not_met,提示业务平台 qop 不满足期望的 QoP,传递的
LSP 必不能修改定位结果。
5.4. 位置信息的类型(Types of Location Information)
RLP 允许 LSP 请求不同类型的位置信息,例如不同坐标系。LSP 可(MAY)实现提供
位置信息的其他信息,如速度、方向和海拔高度。LSP 必须实现如下功能:
• 支持 4326 EPSG 数据库地理坐标系
LSP 可(MAY)支持如下功能:
• 其他地理坐标参考系统
• 速度
• 方向
• 海拔
5.4.1. 请求消息的位置信息
LSP 通过请求消息中的 geo_info元素指定地理坐标参考系。
QB-D-121-2007
6
5.4.2. 应答/报告消息中的位置信息
1. 若无指定的地理坐标参考系值,LSP必须返回 4326 EPSG 数据库地理坐标系值。
2. 如果速度、方向和海拔值可得,LSP 需(SHOULD)将其和位置信息共同返回。
5.5. 定位请求处理优先级
LSP 可(MAY)通过 prio 元素指定请求消息处理的优先级(紧急定位消息是最高优
先级)。
由 LSP 决定以何种优先级处理接收到的的请求消息。传递的 LSP 必不能修改请求消息
中的优先级值。非紧急定位服务,若请求中未定义 prio 元素,表示优先级为正常
"NORMAL"。即 LSP 定位请求优先级默认设置:紧急定位服务优先级为“高”HIGH,其他
应用为“正常”。
5.6. 目标用户标识
LSP 必须指定目标用户标识,包括 MSISDN, IMSI, IP address, 等。3GPP 环境中的 LSP必须支持 MSISDN,3GPP2 环境中的 LSP 必须支持 MDN。
6. Lr 协议具体定义
6.1. 传输层定义
RLP 的传输层可使用多种传输协议,其中同 HTTP 的对应见 9 HTTP Mapping。 映射 章节 HTTP 9 HTTP 映射
6.2. 元素层定义
6.2.1. Identity Element Definitions
参考《中国移动位置服务 Le 接口技术规范》。
6.2.2. Function Element Definitions
<!-- RLP_FUNC -->
QB-D-121-2007
7
<!ELEMENT eme_event (eme_pos+)>
<!ATTLIST eme_event
eme_trigger (EME_ORG | EME_REL) #REQUIRED>
<!ELEMENT tlrr_event (ms_action |
change_area)>
<!ELEMENT ms_action EMPTY>
<!ATTLIST ms_action
type (MS_AVAIL) #REQUIRED>
<!ELEMENT change_area (target_area,
no_of_reports?)>
<!ATTLIST change_area
type (MS_ENTERING | MS_LEAVING |
MS_WITHIN_AREA)
#REQUIRED
loc_estimates (TRUE | FALSE) #REQUIRED>
<!ELEMENT target_area ((shape, cc?) | cc |
plmn+)>
<!ELEMENT no_of_reports (#PCDATA)>
<!ELEMENT name_area (#PCDATA)>
<!ELEMENT plmn (mcc, mnc)>
<!ELEMENT interval (#PCDATA)>
<!ELEMENT loc_type EMPTY>
<!ATTLIST loc_type
type (CURRENT | LAST |CURRENT_OR_LAST |
LAST_OR_CURRENT | INITIAL)
"CURRENT">
<!ELEMENT prio EMPTY>
<!ATTLIST prio
type (NORMAL | HIGH) "NORMAL">
<!ELEMENT pushaddr (url, id?, pwd?)>
<!ELEMENT req_id (#PCDATA)>
<!ELEMENT lcs_ref (#PCDATA)>
<!ELEMENT start_time (#PCDATA)>
<!ATTLIST start_time
utc_off CDATA "0000">
<!ELEMENT stop_time (#PCDATA)>
<!ATTLIST stop_time
utc_off CDATA "0000">
<!ELEMENT duration (#PCDATA)>
<!ELEMENT url (#PCDATA)>
<!ELEMENT time_remaining (#PCDATA)>
<!ELEMENT req_result EMPTY
QB-D-121-2007
8
<!ATTLIST req_result
type (POSITION | NET_PARAM | AREA_CODE) "POSITION">
6.2.3. Location Element Definitions
<!-- RLP_LOC -->
<!ELEMENT pos (msid, (pd | net_param |
area_code | poserr), posfixlspid?)>
<!ATTLIST pos
pos_method (CELL | OTDOA | GPS | A-GPS | E-OTD |
U-TDOA | OTHER)
#IMPLIED>
<!ELEMENT eme_pos (msid, (pd | poserr),
esrd?,
esrk?, posfixlspid?)>
<!ATTLIST eme_pos
pos_method (CELL | OTDOA | GPS | A-GPS | E-OTD |
U-TDOA | OTHER)
#IMPLIED>
<!ELEMENT pd (time, shape, (alt,
alt_unc?)?,
speed?, direction?,
lev_conf?,
qop_not_met?)>
<!ELEMENT trl_pos (msid, (pd | poserr |
time), posfixlspid?)>
<!ATTLIST trl_pos
trl_trigger (PERIODIC | MS_AVAIL | CHANGE_AREA) #REQUIRED
pos_method (CELL | OTDOA | GPS | A-GPS | E-OTD |
U-TDOA | OTHER)
#IMPLIED>
<!ELEMENT poserr (result, add_info?,
time)>
<!ELEMENT time (#PCDATA)>
<!ATTLIST time
utc_off CDATA "0000">
<!ELEMENT alt (#PCDATA)>
<!ELEMENT alt_unc (#PCDATA)>
<!ELEMENT qop_not_met EMPTY>
<!ELEMENT direction (#PCDATA)>
<!ELEMENT speed (#PCDATA)>
QB-D-121-2007
9
<!ELEMENT lev_conf (#PCDATA)>
<!ELEMENT geo_info (CoordinateReferenceSy
stem)>
<!ELEMENT CoordinateReferenceSystem (Identifier)>
<!ELEMENT Identifier (code, codeSpace,
edition)>
<!ELEMENT code (#PCDATA)>
<!ELEMENT codeSpace (#PCDATA)>
<!ELEMENT edition (#PCDATA)>
<!ELEMENT service_coverage ((cc, ndc*)+)>
<!ELEMENT area_code (#PCDATA)>
<!ATTLIST area_code
type (IDD | DDD) “DDD”>
<!ELEMENT posfixlspid (#PCDATA)>
<!ENTITY % mlp_res.dtd SYSTEM
"MLP_RES_200.DTD">
%mlp_res.dtd;
6.2.4. Result Element Definitions
参考《中国移动位置服务 Le 接口技术规范》。
6.2.5. Shape Element Definitions
参考《中国移动位置服务 Le 接口技术规范》。
6.2.6. Quality of Position Element Definitions
参考《中国移动位置服务 Le 接口技术规范》。
6.2.7. Network Parameters Element Definitions
<!-- RLP_NET -->
<!ELEMENT net_param (h_ls?, v_ls?, pce?, neid?, imsi?,
(gsm_net_param | wcdma_net_param |
cdma_net_param)?)>
<!ELEMENT gsm_net_param (cgi?, nmr?, ta?, lmsi?)>
<!ELEMENT wcdma_net_param (global_uc_id?, frequencyinfo?,
QB-D-121-2007
10
primaryscramblingcode?, sai?)>
<!ELEMENT cdma_net_param (nid, sid, base_id, base_lat?, base_long?,
ref_pn?)>
<!ELEMENT neid (vmscid?, sgsnid?, vlrid?)>
<!ELEMENT vmscid (cc?, ndc?, vmscno)>
<!ATTLIST vmscid
capability (1 | 2 | 3 | 4) #IMPLIED>
<!ELEMENT vlrid (cc?, ndc?, vlrno)>
<!ATTLIST vlrid
capability (1 | 2 | 3 | 4) #IMPLIED>
<!ELEMENT sgsnid (cc?, ndc?, sgsnno)>
<!ATTLIST sgsnid
capability (1 | 2 | 3 | 4) #IMPLIED>
<!ELEMENT imsi (#PCDATA)>
<!ELEMENT h_ls (#PCDATA)>
<!ELEMENT v_ls (#PCDATA)>
<!ELEMENT pce (#PCDATA)>
<!ELEMENT cgi (mcc, mnc, lac, cellid)>
<!ELEMENT nmr (nmr_element+)>
<!ELEMENT nmr_element (arfcn, bsic, rxlev)>
<!ELEMENT arfcn (#PCDATA)>
<!ELEMENT bsic (#PCDATA)>
<!ELEMENT rxlev (#PCDATA)>
<!ELEMENT mcc (#PCDATA)>
<!ELEMENT mnc (#PCDATA)>
<!ELEMENT ndc (#PCDATA)>
<!ELEMENT cc (#PCDATA)>
<!ELEMENT vmscno (#PCDATA)>
<!ELEMENT vlrno (#PCDATA)>
<!ELEMENT lac (#PCDATA)>
<!ELEMENT cellid (#PCDATA)>
<!ELEMENT ta (#PCDATA)>
<!ELEMENT lmsi (#PCDATA)>
<!ELEMENT global_uc_id (mcc, mnc, uc_id)>
<!ELEMENT uc_id (#PCDATA)>
<!ATTLIST uc_id
status (STALE | CURRENT |
UNKNOWN)
"CURRENT">
<!ELEMENT sai (mcc, mnc, lac, sac)>
<!ELEMENT sac (#PCDATA)>
<!ELEMENT frequencyinfo (uarfcn_ul?, uarfcn_dl?, uarfcn_nt?)>
<!ELEMENT primaryscramblingcode (#PCDATA)>
<!ELEMENT uarfcn_ul (#PCDATA)>
<!ELEMENT uarfcn_dl (#PCDATA)>
QB-D-121-2007
11
<!ELEMENT uarfcn_nt (#PCDATA)>
<!ELEMENT nid (#PCDATA)>
<!ELEMENT sid (#PCDATA)>
<!ELEMENT base_id (#PCDATA)>
<!ELEMENT base_lat (#PCDATA)>
<!ELEMENT base_long (#PCDATA)>
<!ELEMENT ref_pn (#PCDATA)>
6.2.8. Roaming Context and Privacy Element Definitions
<!-- RLP_CTXT -->
<!ELEMENT client (servicetype, id?, serviceid?,
requestmode?, clientname?, pseudoid?, poi?)>
<!ATTLIST client
type (1 | 2 | 3) "1">
<!ELEMENT id (#PCDATA)>
<!ELEMENT requestor (#PCDATA)>
<!ATTLIST requestor
type (MSISDN | NAME | E-MAIL
| URL | SIPURL | IMS)
"MSISDN">
<!ELEMENT pwd (#PCDATA)>
<!ELEMENT serviceid (#PCDATA)>
<!ELEMENT requestmode (requestor | session)?>
<!ATTLIST requestmode
type (ACTIVE | PASSIVE) "PASSIVE">
<!ELEMENT locationserver (id, pwd?)>
<!ELEMENT clientname (#PCDATA)>
<!ELEMENT serving_node_action EMPTY>
<!ATTLIST serving_node_action
passive_type
(POSITION_NOT_ALLOWED |
POSITION |
NOTIFY_AND_POSITION |
POSITION_IF_NOT_DISALLOWE
D | POSITION_IF_ALLOWED)
#REQUIRED
active_type
(POSITION_NOT_ALLOWED |
POSITION |
NOTIFY_AND_POSITION |
POSITION_IF_NOT_DISALLOWE
D | POSITION_IF_ALLOWED)
"POSITION_NOT_ALLOWED">
<!ELEMENT poi EMPTY>
<!ATTLIST poi
QB-D-121-2007
12
flag (ON | OFF) "OFF">
<!ELEMENT pseudoid (#PCDATA)>
<!ELEMENT servicetype (#PCDATA)>
<!ELEMENT supported_shapes EMPTY>
<!ATTLIST supported_shapes
Point (NO | YES) "NO"
LineString (NO | YES) "NO"
Polygon (NO | YES) "NO"
Box (NO | YES) "NO"
CircularArea (NO | YES) "NO"
CircularArcArea (NO | YES) "NO"
EllipticalArea (NO | YES) "NO"
MultiLineString (NO | YES) "NO"
MultiPoint (NO | YES) "NO"
MultiPolygon (NO | YES) "NO"
LinearRing (NO | YES) "NO"
Altitude (NO | YES) "NO">
<!ELEMENT target (#PCDATA)>
6.3. 服务层定义
归属地 LSP 必须根据 client 的子元素 id 检查系统配置数据,检查其是否被授权接入。
漫游地 LSP 不需检查 client 的系统配置数据。请求 LSP 通过 locationserver 的 id 和 pwd 接入
服务 LSP。sessionid 的使用参考《中国移动位置服务 Le 接口技术规范》。
6.3.1. 头信息结构
<!-- RLP_HDR -->
<!ELEMENT rlp_hdr ((sessionid | locationserver, sessionid?)), client?,
serving_node_action?, supported_shapes?, net_param?,
collab_id)>
<!ATTLIST rlp_hdr
ver CDATA #FIXED "2.0.0">
在归属地 LSP 至漫游地 LSP 的 Lr 接口中必须包含 net_param 元素,且必须包含其 neid子元素的 vmscid 子元素。接入地 LSP 产生 collab_id(协同号),接入地 LSP 与归属地 LSP、归属地 LSP 与漫游地 LSP 的 Lr 请求消息、归属地 LSP 与 AGPS 平台的 Lp 请求消息、AGPS平台与 LSP 平台之间的 Lr 请求消息,其对应的应答消息和报告消息必须包含此 collab_id,以便应答/报告消息和请求消息对应。 例 1: 业务平台发起定位
<rlp_svc_init> <rlp_hdr ver="2.0.0">
QB-D-121-2007
13
<locationserver> <id>461018768787</id> <pwd>remoteLocationServer1</pwd> </locationserver> <client> <id>theasp</id> <serviceid>0005</serviceid> <requestmode type="PASSIVE"/> <clientname>TheClientName</clientname> <pseudoid>358401234567</pseudoid> </client>
<net_param> <neid>
<vmscid capability="4"> <cc>46</cc> <ndc>10</ndc> <vmscno>28544781612</vmscno>
</vmscid> </neid> <imsi>217567810164</imsi> </net_param> <collab_id>C100200701010000100002</collab_id> </rlp_hdr> ... </rlp_svc_init>
例 2: MS 发起定位
<rlp_svc_init>
<rlp_hdr ver="2.0.0">
<locationserver>
<id>461018768787</id>
<pwd>remoteLocationServer1</pwd>
</locationserver>
<client>
<id>theasp</id>
<serviceid>0005</serviceid>
<requestmode type="ACTIVE"/>
<clientname>TheClientName</clientname>
<pseudoid>358401234567</pseudoid>
</client>
<net_param>
<neid>
<vmscid capability="4">
<cc>46</cc>
<ndc>10</ndc>
QB-D-121-2007
14
<vmscno>28544781612</vmscno>
</vmscid>
</neid>
<imsi>217567810164</imsi>
<net_param>
<collab_id>C100200701010000100002</collab_id>
</rlp_hdr>
...
</rlp_svc_init>
6.3.2. Standard Roaming Location Immediate Service
LSP 设备的 Lr 接口应该支持同步和异步的方式。 Standard Roaming Location Immediate Service:为处于漫游的移动用户提供的定位服务,
此服务要求定位结果立即(或在一个指定的时间段内)返回,此服务可以是同步的或异步的
方式。 此服务包括以下的消息: - Standard Roaming Location Immediate Request - Standard Roaming Location Immediate Answer - Standard Roaming Location Immediate Report 消息流程如图 6-1 所示:
Location Location Server
standard roaming location immediate request
standard roaming location immediate answer
standard roaming location immediate reportIf (needed)
图 错误!文档中没有指定样式的文字。-1漫游立即定位流程示意图
6.3.2.1. Standard Roaming Location Immediate Request DTD
<!-- RLP_SRLIR_200 -->
<!ENTITY % extension.param "">
<!ELEMENT srlir (msid, codeword?, eqop?, geo_info?, loc_type?,
prio?, pushaddr?,service_coverage?, req_result?
QB-D-121-2007
15
%extension.param;)>
<!ATTLIST srlir
ver CDATA #FIXED "2.0.0"
res_type (SYNC | ASYNC) "SYNC"
recv_role (HLS | VLS) #REQUIRED>
例: <srlir ver="2.0.0" res_type="SYNC" recv_role="HLS">
<msid>461018765712</msid>
<eqop>
<resp_req type="LOW_DELAY"/>
<hor_acc>1000</hor_acc>
</eqop>
<geo_info>
<CoordinateReferenceSystem>
<Identifier>
<code>4004</code>
<codeSpace>EPSG</codeSpace>
<edition>6.1</edition>
</Identifier>
</CoordinateReferenceSystem>
</geo_info>
<loc_type type="CURRENT_OR_LAST" />
<prio type="HIGH" />
</srlir>
6.3.2.2. Standard Roaming Location Immediate Answer DTD
<!-- RLP_SRLIA -->
<!ENTITY % extension.param "">
<!ELEMENT srlia ((pos | req_id | (result, add_info?))
%extension.param;)>
<!ATTLIST srlia
ver CDATA #FIXED "2.0.0">
例 1: 同步通信方式,定位成功
<srlia ver="2.0.0" >
<pos>
<msid>461011334411</msid>
<pd>
QB-D-121-2007
16
<time utc_off="+0200">20020623134453</time>
<shape>
<CircularArea srsName="www.epsg.org#4326">
<coord>
<X>30 16 28.308N</X>
<Y>45 15 33.444E</Y>
</coord>
<radius>240</radius>
</CircularArea>
</shape>
</pd>
</pos>
</srlia>
例 2: 异步通信方式
<srlia ver="2.0.0" >
<req_id> R100200701010000100005</req_id>
</srlia>
6.3.2.3. Standard Roaming Location Immediate Report DTD
<!-- RLP_SRLIREP_200 -->
<!ENTITY % extension.param "">
<!ELEMENT srlirep (req_id, pos %extension.param;)>
<!ATTLIST srlirep
ver CDATA #FIXED "2.0.0">
例: 异步报告
<srlirep ver="2.0.0">
<req_id> R100200701010000100005</req_id>
<pos>
<msid>471011334411</msid>
<pd>
<time utc_off="+0300">20020813010423</time>
<shape>
<CircularArea srsName="www.epsg.org#4327">
<coord>
<X>35 03 28.244N</X>
<Y>135 47 08.711E</Y>
</coord>
<radius>15</radius>
QB-D-121-2007
17
</CircularArea>
</shape>
</pd>
</pos>
</srlirep>
6.3.3. Triggered Roaming Location Reporting Service
The triggered roaming location reporting service:若应用想在用户处于漫游状态时获取用
户位置信息,则需要使用该服务。触发器可以有以下几种:
- 周期性触发
- MS Action,3GPP [23.271] 称"UE available"
- 基于位置触发,3GPP [23.271]称“change of area”
当预定义的事件发生时。就会触发报告。该服务包含以下消息: - Triggered Roaming Location Reporting Request
- Triggered Roaming Location Reporting Answer
- Triggered Roaming Location Report
- Triggered Roaming Location Report Stop Request
- Triggered Roaming Location Reporting Stop Answer
Triggered Roaming Location Reporting Service 必须(SHALL)包含 Triggered Roaming Location Reporting Request,其后为 Triggered Roaming Location Reporting Answer,可(MAY)
包含 0、1 或多个 Triggered Roaming Location Reports。
Triggered Roaming Location Reporting Service 还可(MAY)包含 Triggered Roaming Location Reporting Stop Request,和 Triggered Roaming Location Reporting Stop Answer。此外,
Triggered Roaming Location Reporting Stop Answer 可(MAY)在没有 Triggered Roaming Location Reporting Stop Request 的情况下发送。
消息流程如图 6-2 所示:
QB-D-121-2007
18
Location Server
triggered roaming location reporting request
triggered roaming location reporting answer
triggered roaming location report
triggered roaming location report
triggered roaming location reporting stop request
triggered roaming location reporting stop answer
Location Server
图 错误!文档中没有指定样式的文字。-2漫游立即定位流程示意图 TRLRS 仅适用于接入地 LSP 与被叫归属地 LSP 之间,不适用于被叫归属地 LSP 与被叫
漫游地 LSP 之间。 如果网络决定单方面的终止定位报告,那么 trlrep 中应该包含停止报告的信息。由于某
些原因(例如隐私数据更新),任何定位平台都可以发起取消 triggered roaming。
6.3.3.1. Triggered Roaming Location Reporting Request DTD
<!-- RLP_TRLRR -->
<!ENTITY % extension.param "">
<!ELEMENT trlrr (msid, lcs_ref?, codeword?, interval?, start_time?,
stop_time?, duration?, tlrr_event?, qop?,
geo_info?, pushaddr?, loc_type?, prio?
%extension.param;)>
<!ATTLIST trlrr
ver CDATA #FIXED "2.0.0"
recv_role (HLS | VLS) #REQUIRED>
关于‘start_time’, ‘stop_time’, ‘interval’ , ’duration’ and ‘tlrr_event’的规定如
下:
TLRR有‘interval’元素则为周期性触发事件,TLRR有‘tlrr_event’元素则为基于位
置触发事件,两个元素并列可组成联合周期性/ MS_AVAIL触发事件。若无此其一或两个元素,
则LSP拒绝接收该请求,返回106错误码。
interval必须不大于24小时。
QB-D-121-2007
19
若无start_time元素,则LSP将立即开始返回定位结果。
若无stop_time元素,直到有明确的停止定位请求或定时器超时,LSP将持续返回定位结
果。定时器超时由TLREP中time_remaining元素指示。
若stop_time和duration两个元素并存,则LSP必须拒绝该定位请求。
若start_time比LSP当前时间早,则LSP必须拒绝该定位请求,错误码110。
若stop_time比LSP当前时间早,则LSP必须拒绝该定位请求,错误码110。
若stop_time比start_time早,则LSP必须拒绝该定位请求,错误码110。
若stop_time同start_time,则LSP必须返回一次响应消息,interval元素将被忽略。
若duration为0,则LSP必须返回一次响应消息,interval元素将被忽略。
例 1: MS_AVAIL 事件的 TRLRR 请求 <trlrr ver="2.0.0" recv_role="HLS">
<msid>461011678298</msid>
<start_time utc_off="+0300">20021003112700</start_time> <trlrr_event>
<ms_action type="MS_AVAIL"/>
</trlrr_event>
<qop>
<hor_acc>100</hor_acc>
</qop>
<geo_info>
<CoordinateReferenceSystem>
<Identifier>
<code>4326</code>
<codeSpace>EPSG</codeSpace>
<edition>6.1</edition>
</Identifier>
</CoordinateReferenceSystem>
</geo_info>
<pushaddr>
<url>http://location.application.com</url>
</pushaddr>
<loc_type type="CURRENT" />
<prio type="HIGH" />
</trlrr>
例 2: MS_ENTERING 事件 TRLRR 请求
<trlrr ver="2.0.0" recv_role="HLS">
<msid>461011678298</msid>
<lcs_ref>50</lcs_ref>
<tlrr_event>
<change_area type="MS_ENTERING" loc_estimates="TRUE">
<target_area>
<name_area>Seoul</name_area>
</target_area>
QB-D-121-2007
20
</change_area>
</tlrr_event>
<qop>
<hor_acc>100</hor_acc>
</qop>
<geo_info>
<CoordinateReferenceSystem>
<Identifier>
<code>4326</code>
<codeSpace>EPSG</codeSpace>
<edition>6.1</edition>
</Identifier>
</CoordinateReferenceSystem>
</geo_info>
<pushaddr>
<url>http://location.application.com</url>
</pushaddr>
<loc_type type="CURRENT" />
<prio type="HIGH" />
</trlrr>
例 7.3.3.1-3: MS_WITHIN_AREA 事件 TRLRR 请求
<trlrr ver="2.0.0" recv_role="HLS">
<msid>461011678298</msid>
<lcs_ref>50</lcs_ref>
<tlrr_event>
<change_area type="MS_WITHIN_AREA" loc_estimates="FALSE">
<target_area>
<shape>
<CircularArea srsName="www.epsg.org#4326">
<coord>
<X>35 35 24.139N</X>
<Y>139 35 24.754E</Y>
</coord>
<radius>15</radius>
</CircularArea>
</shape>
</target_area>
<no_of_reports>10</no_of_reports>
</change_area>
</tlrr_event>
<pushaddr>
<url>http://location.application.com</url>
</pushaddr>
QB-D-121-2007
21
</trlrr>
6.3.3.2. Triggered Roaming Location Reporting Answer DTD
<!-- RLP_TRLRA -->
<!ENTITY % extension.param "">
<!ELEMENT trlra (((req_id, lcs_ref?) | (result, add_info?))
%extension.param;)>
<!ATTLIST trlra
ver CDATA #FIXED "2.0.0">
例 1:对应的 TLRR 成功
<trlra ver="2.0.0">
<req_id> R100200701010000100004</req_id>
</trlra>
例 2:对应的 TLRR 失败
<trlra ver="2.0.0">
<result resid="4">UNKNOWN SUBSCRIBER</result>
</trlra>
6.3.3.3. Triggered Roaming Location Report DTD
<!-- RLP_TRLREP -->
<!ENTITY % extension.param "">
<!ELEMENT trlrep (req_id, lcs_ref?, trl_pos, time_remaining?
%extension.param;)>
<!ATTLIST trlrep
ver CDATA #FIXED "2.0.0">
例 1:定位成功 <trlrep ver="2.0.0"> <req_id> R100200701010000100003</req_id> <lcs_ref>50</lcs_ref> <trl_pos trl_trigger="MS_AVAIL"> <msid>461011678298</msid> <pd> <time utc_off="+0300">20020813010423</time> <shape> <CircularArea srsName="www.epsg.org#4326">
QB-D-121-2007
22
<coord> <X>35 35 24.139N</X> <Y>139 35 24.754E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </trl_pos> <time_remaining>00010000</time_remaining> </trlrep> 例 2:取消定位 <trlrep ver="2.0.0">
<req_id> R100200701010000100003</req_id>
<lcs_ref>50</lcs_ref>
<trl_pos trl_trigger="MS_AVAIL">
<msid>461011678298</msid>
<poserr>
<result resid="114"> CANCELLATION OF TRIGGERED LOCATION REQUEST</result>
<time utc_off="+0200">20041007110237</time>
</poserr>
</trl_pos>
</trlrep>
6.3.3.4. Triggered Roaming Location Reporting Stop Request DTD
<!-- RLP_TRLRSR -->
<!ENTITY % extension.param "">
<!ELEMENT trlrsr (req_id, lcs_ref? %extension.param;)>
<!ATTLIST trlrsr
ver CDATA #FIXED "2.0.0"
Recv_role (HLS | VLS) #REQUIRED>
例: <trlrsr ver="2.0.0" recv_role="HLS">
<req_id> R100200701010000100007</req_id>
<lcs_ref>50</lcs_ref>
</trlrsr>
QB-D-121-2007
23
6.3.3.5. Triggered Roaming Location Reporting Stop Answer DTD
<!-- RLP_TRLRSA -->
<!ENTITY % extension.param "">
<!ELEMENT trlrsa ((req_id | (result, add_info?)) %extension.param;)>
<!ATTLIST trlrsa
ver CDATA #FIXED "2.0.0">
例: <trlrsa ver="2.0.0">
<req_id> R100200701010000100002</req_id>
</trlrsa>
6.3.4. Emergency Roaming Location Immediate Service
The emergency roaming location immediate service 用来将定位请求透明传送给当前为用
户提供服务的网络。 该服务包含以下消息:
- Emergency Roaming Location Immediate Request
- Emergency Roaming Location Immediate Answer
消息流程如图 6-3 示:
Location Server 1 Location Server 2
emergency roaming location immediate request
emergency roaming location immediate answer
图 错误!文档中没有指定样式的文字。-3漫游立即定位流程示意图
6.3.4.1. Emergency Roaming Location Immediate Request DTD
<!-- RLP_ERLIR -->
<!ENTITY % extension.param "">
<!ELEMENT erlir (msid, esrd?, esrk?, eqop?, geo_info?, loc_type?
%extension.param;)>
<!ATTLIST erlir
QB-D-121-2007
24
ver CDATA #FIXED "2.0.0"
recv_role (HLS | VLS) #REQUIRED>
例: <erlir ver="2.0.0" recv_role="HLS">
<msid type="MSISDN">461011334411</msid>
<geo_info>
<CoordinateReferenceSystem>
<Identifier>
<code>4004</code>
<codeSpace>EPSG</codeSpace>
<edition>6.1</edition>
</Identifier>
</CoordinateReferenceSystem>
</geo_info>
<loc_type type="CURRENT_OR_LAST"/>
</erlir>
6.3.4.2. Emergency Roaming Location Immediate Answer DTD
<!-- RLP_ERLIA -->
<!ENTITY % extension.param "">
<!ELEMENT erlia ((eme_pos | (result, add_info?))
%extension.param;)>
<!ATTLIST erlia
ver CDATA #FIXED "2.0.0">
例: <erlia ver="2.0.0">
<eme_pos>
<msid type="MSISDN">461011334411</msid>
<pd>
<time utc_off="+0300">20020623134453</time>
<shape>
<CircularArea srsName="www.epsg.org#4326">
<coord>
<X>30 24 43.53N</X>
<Y>45 28 09.534W</Y>
</coord>
<radius>15</radius>
</CircularArea>
</shape>
</pd>
QB-D-121-2007
25
<esrk>7839298236</esrk>
</eme_pos>
</erlia>
6.3.5. Standard Roaming Subscriber Authentication Service
Standard Roaming Subscriber Authentication Service:实现对业务发起方用户的鉴权功能。
此服务要求立即返回,此服务是同步的方式。 此服务包括以下的消息: - Standard Roaming Subscriber Authentication Request - Standard Roaming Subscriber Authentication Answer 消息流程如图 6-4 所示:
LSP LSP
Standard Roaming Subscriber Authentication Request
Standard Roaming Subscriber Authentication Answer
图 错误!文档中没有指定样式的文字。-4漫游用户鉴权流程示意图
6.3.5.1. Standard Roaming Subscriber Authentication Request DTD
<!-- RLP_SRSAR-->
<!ENTITY % extension.param "">
<!ELEMENT srsar (target, %extension.param;)>
<!ATTLIST srsar
ver CDATA #FIXED "2.0.0">
例:
<srsar ver="2.0.0">
<target></target>
</srsar>
6.3.5.2. Standard Roaming Subscriber Authentication Answer DTD
<!-- RLP_SRSAA -->
<!ENTITY % extension.param "">
<!ELEMENT srsaa (result, add_info?%extension.param;)>
QB-D-121-2007
26
<!ATTLIST srsaa
ver CDATA #FIXED "2.0.0">
post_auth (YES|NO) "NO">
例:
<srsaa ver="2.0.0" post_auth="NO" >
<result resid=“000”>OK</result>
</srsaa>
6.3.6. Standard Roaming Location Reporting Service
SRLRS服务用于用户欲业务平台接收其MS位置时候,即用户漫游且发起MO-LR请求。
该服务由以下消息组成: - Standard Roaming Location Report
- Standard Roaming Location Report Answer
SRLRS 服务必须包含 SRLREP 消息,其后跟 SRLRA 消息。 消息流程如图 6-5 所示:
Location Server Location Server
standard roaming location report
standard roaming location report answer
图 错误!文档中没有指定样式的文字。-5 Standard roaming location report
6.3.6.1. Standard Roaming Location Report DTD
<!-- RLP_SRLREP -->
<!ENTITY % extension.param "">
<!ELEMENT srlrep (pos %extension.param;)>
<!ATTLIST srlrep
ver CDATA #FIXED "2.0.0">
例 1:
<srlrep ver="2.0.0">
<pos>
<msid>461011678298</msid>
QB-D-121-2007
27
<pd>
<time utc_off="+0300">20041031074711</time>
<shape>
<CircularArea srsName="www.epsg.org#4326">
<coord>
<X>35 35 24.139N</X>
<Y>139 35 24.754E</Y>
</coord>
<radius>15</radius>
</CircularArea>
</shape>
</pd>
</pos>
</srlrep >
6.3.6.2. Standard Roaming Location Report Answer DTD
<!-- RLP_SRLRA -->
<!ENTITY % extension.param "">
<!ELEMENT srlra (result, add_info? %extension.param;)>
<!ATTLIST srlra
ver CDATA #FIXED "2.0.0">
例 1: SRLRA in case the handling of corresponding SRLREP was successful
<srlra ver="2.0.0" >
<result resid="0">OK</result>
</srlra>
例 2: SRLRA in case the handling of corresponding SRLREP was in error
<srlra ver="2.0.0" >
<result resid="4">UNKNOWN SUBSCRIBER</result>
<add_info> the subscriber is not registered in the LCS Client</add_info>
</srlra>
6.3.7. General Error Message Definition
参考《中国移动位置服务 Le 接口技术规范》。
QB-D-121-2007
28
7. 元素及属性定义
未定义的元素和属性请参见《中国移动位置业务 Le 接口技术规范》。
7.1. pseudoid
描述:
伪码用于VPLMN隐私策略,参考3GPP 23.271 Release 6。在3GPP中该号码定义为E.164。
类型: Element
格式: Char string
定义值:
缺省值: -
例子: <pseudoid>358401234567</pseudoid>
注释: -
7.2. uc_id
描述:
在WCDMA网中的小区标识
类型: Element
格式: Char String
定义值: 0-268435455
缺省值: -
例子: <uc_id>228435001</uc_id>
注释:
7.2.1. status
描述:
uc_id 元素的状态.
格式: Attribute
定义值: Char String
STALE The value of uc_id is not may no longer be valid. 缺省值:
CURRENT The value of uc_id is valid.
UNKNOWN The staus of of uc_id is not known.
缺省值: CURRENT
例子: <uc_id status=”CURRENT”>228435001</uc_id status>
QB-D-121-2007
29
注释:
7.3. sac
描述:
WCDMA网络中service area code
类型: Element
格式: Char String
定义值: 0-65535
缺省值: -
例子: <sac>548</sac>
注释:
7.4. client
描述:
该元素保存了业务平台相关的信息,用于隐私检查和订购关系鉴权
类型: Element
格式:
定义值: -
缺省值: -
例子: -
注释:
7.4.1. type
描述:
业务平台的类型
类型: Attribute
格式: Char String
1 业务平台
2 依法可进行监控的业务平台
定义值:
3 紧急救援服务平台
缺省值: -
例子: <client Type=”1”> <id>SomeId</id> </client>
注释:
QB-D-121-2007
30
7.5. clientname
描述:
存储在R-LSP上的SP的名称
类型: Element
格式: Char String
定义值: -
缺省值: -
例子: <clientname>MLPFriendFinder</clientname>
注释:
7.6. imsi
描述:
3GPP TS 23.003 和 ITU-T E212中制定的国际移动用户标识号码(International Mobile Subscriber Identity number)。只在漫游情况下使用该元素。
类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <imsi>2344512344565</imsi>
注释: IMSI为不多于15位的数字。
7.7. poi
描述:
隐私覆盖指示(Privacy Override Inidicator)。该元素指示在
PROVIDE_SUBSCRIBER_LOCATION 消息中是否应设置POI标志来覆盖被定位用户归属地
LSP中的隐私检查信息。该参数的细节参见[23.271] Rel 6。
类型: Element
格式: Char string
定义值: -
缺省值:
例子: <poi flag=”ON”>
注释: -
QB-D-121-2007
31
7.7.1. flag
描述:
该元素说明POI是否应该设置。
类型: Attribute
格式: Char string
ON POI必须设置 定义值:
OFF POI必须不设置
缺省值: <poi flag=”ON”>
例子:
注释: -
7.8. serving_node_action
描述:
被定位用户归属地LSP根据目的用户隐私设置选择通知操作,隐私设置包括用户是否应被通
知或是否需要用户验证。该参数的细节参见[23.271] Rel 6。
类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <serving_node_action passive_type=”POSTION_IF_ALLOWED active_type=”POSITION>
注释:
7.8.1. passive_type
描述:
如果被叫用户非发起定位的用户,隐私设置通知操作类型。
类型: Attribute
格式: Char string
POSITION_NOT_ALLOWED 不允许被定位
POSITION 允许定位,不通知用户
NOTIFY_AND_POSITION 允许定位,需要通知用户
定义值:
POSITION_IF_NOT_DISALLOWED 定位需通知用户并经用户验证。只
有在用户通过验证或对通知没有响
应的情况下,才允许定位。
QB-D-121-2007
32
POSITION_IF_ALLOWED 定位需通知用户并经用户验证。只
有在用户通过验证的情况下,才允
许定位。
缺省值:
例子: <serving_node_action passive_type=”POSITION_IF_ALLOWED”>
注: “POSITION_NOT_ALLOWED”用于active_type存在,而 passive_type不存
在。
7.8.2. active_type
描述:
The action to be used by the serving node for the LCS Notification Invoke procedure if target subscriber is originator of location request.
类型: Attribute
格式: Char string
POSITION_NOT_ALLOWED 不允许被定位
POSITION 允许定位,不通知用户
NOTIFY_AND_POSITION 允许定位,需要通知用户
POSITION_IF_NOT_DISALLOWED 定位需通知用户并经用户验证。只
有在用户通过验证或对通知没有响
应的情况下,才允许定位。
定义值:
POSITION_IF_ALLOWED 定位需通知用户并经用户验证。只
有在用户通过验证的情况下,才允
许定位。
缺省值: POSITION_NOT_ALLOWED
例子: <serving_node_action passive_type=”POSITION_IF_ALLOWED” active_type=”POSITION”>
注释: -
7.9. nmr_element
描述:
若NMR 存在,该元素需重复1-15次,视多少信道的测量数据可得而定,以信道号由高到低排
列。
类型: Element
格式: (arfcn, bsic, rxlev)
定义值: -
缺省值: -
QB-D-121-2007
33
例子: -
注释: -
7.9.1. arfcn
描述:
信道ARFCN,整数,范围0..1023
类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <arfcn>3</arfcn>
注释:
7.9.2. bsic
描述:
信道BSIC, 整数,范围0..63
类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <bsic>7</bsic>
注释:
7.9.3. rxlev
描述:
信道功率测量值,整数,范围 0..63。实际功率 X(dBm)由该值 N 推出,使用的公式为
X=N-110。 类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <rxlev>12</rxlev>
注释:
QB-D-121-2007
34
7.10. pce
描述:
Holds the address to the Privacy Checking Entity of the target subscriber.
类型: Element
格式: Char string
定义值: -
缺省值: -
例子: <pce>http://host:port/pce/</pce>
注释: -
7.11. servicetype
描述:
该元素说明了客户端的业务类型,参见3GPP 22.071 Rel 6
类型: Element
格式: Char string
定义值:
缺省值: -
例子: <servicetype>0005</servicetype>
注释: 一个业务平台可提供一个或多个业务,业务平台id和serviceid联合唯一表
示一个业务。
7.12. sgsnid
描述:
唯一标识网络中的一个SGSN
类型: Element
格式: Char string
定义值: 在GSM/WCDMA中,该元素表示一个GT地址,该GT地址与E.164号码采
用相同的格式
缺省值: -
例子: <sgsnid capability="4">861541154871</sgsnid>
注释: 该参数必须加86前缀
QB-D-121-2007
35
7.12.1. capability
描述:
定义了服务节点(这里是SGSN)的LCS能力,参见[23.271] Rel 6
类型: Attribute
格式: Char string
1 LCS能力集1:R98 和 R99 LCS (pre-Rel’4 LCS)
2 LCS能力集2:Rel’4 LCS
3 LCS能力集3:Rel’5 LCS
定义值:
4 LCS能力集4:Rel’6或后续版本LCS
缺省值: -
例子: <sgsnid capability=”4”>
<cc>46</cc>
<ndc>70</ndc>
<sgsnno>1541154871</sgsnno >
</sgsnid >
注释:
7.13. ta
描述:
Timing Advance,无线接入网的参数,可用于增强型定位。
类型: Element
格式: Char String
定义值: 0-63
缺省值: -
例子: <ta>3</ta>
注释: Further Information regarding this element can be found in the relevant GSM Specifications
7.14. requestmode
描述:
定义了SP请求的服务类型
类型: Element
格式: Void
定义值: -
缺省值: -
QB-D-121-2007
36
例子: <requestmode type="ACTIVE"/>
注释:
7.14.1. type
描述:
定义了SP请求的服务类型
类型: Attribute
格式: Char string
PASSIVE 该业务不是直接由用户请求
ACTIVE 该业务是由用户直接请求
定义值:
缺省值: PASSIVE
例子: <requestmode type="ACTIVE" />
注释: 缺省值设为PASSIVE,因为这种设置能够给用户带来最大的隐私保护
7.15. vlrid
描述:
唯一确定网络中的一个VLR
类型: Element
格式: Char String
定义值: 在GSM/WCDMA中,该元素表示一个GT地址,该GT地址与E.164号码采
用相同的格式
缺省值:
例子: <vlrid capability=”4”>
<cc>46</cc>
<ndc>70</ndc>
<vlrno>1541154871</vlrno>
</vlrid>
注释: 该参数必须加86前缀
7.15.1. capability
描述:
定义了服务节点(这里是VLR)的LCS能力,参见[23.271] Rel 6
类型: Attribute
QB-D-121-2007
37
格式: Char string
1 LCS能力集1:R98 和 R99 LCS (pre-Rel’4 LCS)
2 LCS能力集2:Rel’4 LCS
3 LCS能力集3:Rel’5 LCS
定义值:
4 LCS能力集4:Rel’6或后续版本LCS
缺省值: -
例子: <vlrid capability="4">
<cc>46</cc>
<ndc>70</ndc>
<vlrno>1541154871</vlrno>
</vlrid>
注释:
7.16. vlrno
描述:
VLR唯一标识号
类型: Element
格式: Char String
定义值: In GSM/WCDMA, defined values shall be according to ITU-T E.164.
缺省值:
例子: <vlrno>1541154871</vlrno>
注释:
7.17. v_ls
描述:
拜访地LSP的地址,即用户漫游地网络中LSP的地址
类型: Element
格式: Char String
定义值: -
缺省值: -
例子: <v_ls>http://host:port/LocationServer/</v_ls>
注释:
7.18. vmscid
描述:
QB-D-121-2007
38
唯一标识网络中的一个VMSC
类型: Element
格式: Char String
定义值: 在GSM/WCDMA中,该元素表示一个GT地址,该GT地址与E.164号码采
用相同的格式
缺省值:
例子: <vmscid capability="4">
<cc>46</cc>
<ndc>70</ndc>
<vmscno>1541154871</vmscno>
</vmscid>
注释: 该参数必须加86前缀。在归属地LSP至拜访地LSP的Lr请求中必须包含该
参数。
7.18.1. capability
描述:
定义了服务节点(这里是VMSC)的LCS能力,参见[23.271] Rel 6
类型: Attribute
格式: Char string
1 LCS能力集1:R98 和 R99 LCS (pre-Rel’4 LCS)
2 LCS能力集2:Rel’4 LCS
3 LCS能力集3:Rel’5 LCS
定义值:
4 LCS能力集4:Rel’6或后续版本LCS
缺省值: -
例子: <vmscid capability="4">
<cc>46</cc>
<ndc>70</ndc>
<vmscno>1541154871</vmscno>
</vmscid>
注释:
7.19. vmscno
描述:
VMSC唯一标识号
类型: Element
格式: Char String
QB-D-121-2007
39
定义值: In GSM/WCDMA, defined values shall be according to ITU-T E.164.
缺省值:
例子: <vmscno>1541154871</vmscno>
注释:
7.19.1. h_ls
描述:
归属地LSP地址,定义见3GPP TS 23.271
类型: Element
格式: Char string
定义值:
缺省值:
例子: <h_ls>http://host:port/LocationServer/</h_ls>
注释: -
7.20. lcs_ref
描述:
从归属地定位平台获得的LDR参考号码。详细内容请参见[3GPP 23.271 LDR reference number]。
类型: Element
格式: Char String
定义值: Two decimal digits, 00-64
默认值: -
例子: <lcs_ref>50</lcs_ref>
注释: Lcs_ref在 triggered location reporting request 消息中发送,包括位置变
化、MS_AVAIL event、周期性&MS_AVAIL的triggered location reporting request
LCS参考码为一个8位组,需要编码成00-64范围内的十进制数。
7.21. service attributes
在《中国移动位置业务 Le 接口技术规范》的定义上,再增加 recv_role 元素,提示接收 LSP应该扮演的角色(归属地 LSP 或漫游地 LSP)。
7.21.1. recv_role
描述:
QB-D-121-2007
40
提示接收LSP应该 归属扮演的角色( 地LSP或漫游地LSP)
类型: Attribute
格式: Char String
HLS Home Location Server 定义值:
VLS Visited Location Server
缺省值: N/A
例子: <srlir ver=”2.0.0” recv_role=”HLS”>…</srlir>
注释:
7.22. supported_shapes
描述:
定义LSP所支持的地理形状(定位结果的表示法),详见3GPP [23.271] 、[29.002] Rel 6. section 错误!未找到引用源。.
类型: Element
格式: Void
定义值: -
缺省值: -
例子: <supported_shapes Point="YES” Polygon=”YES” Altitude=”YES” />
注释: 若该元素不存在,根据[29.002] section 7.6.11.20表示LSP可假定某些地理形状被
支持。
7.22.1. Point
描述:
标识是否支持Point
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes Point="YES"/>
注释:
7.22.2. Linestring
描述:
标识是否支持LineString
QB-D-121-2007
41
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes LineString="YES"/>
注释:
7.22.3. Polygon
描述:
标识是否支持Polygon
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes Polygon="YES"/>
注释:
7.22.4. Box
描述:
标识是否支持 Box
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes Box="YES"/>
注释:
7.22.5. CircularArea
描述:
QB-D-121-2007
42
标识是否支持 CircularArea
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes CircularArea="YES"/>
注释:
7.22.6. CircularArcArea
描述:
标识是否支持 CircularArcArea
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes CircularArcArea="YES"/>
注释:
7.22.7. EllipticalArea
描述:
标识是否支持EllipticalArea
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes EllipticalArea="YES"/>
注释:
QB-D-121-2007
43
7.22.8. MultiLineString
描述:
标识是否支持 MultiLineString
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes MultiLineString="YES"/>
注释:
7.22.9. MultiPoint
描述:
标识是否支持 MultiPoint
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes MultiPoint="YES"/>
注释:
7.22.10. MultiPolygon
描述:
标识是否支持 MultiPolygon
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes MultiPolygon="YES"/>
注释:
QB-D-121-2007
44
7.22.11. LinearRing
描述:
标识是否支持LinearRing
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes LinearRing="YES"/>
注释:
7.22.12. Altitude
描述:
标识Altitude是否支持supported_shapes所指定的形状
类型: Attribute
格式: Char string
NO 定义值:
YES
缺省值: NO
例子: <supported_shapes Altitude="YES"/>
注释:
7.23. primaryscramblingcode
描述:
WCDMA中primary scrambling code
类型: Element
格式: Char String
缺省值: 0-511
缺省值: -
例子: < primaryscramblingcode >2345</ primaryscramblingcode>
注释:
QB-D-121-2007
45
7.24. uarfcn_ul
描述:
WCDMA, FDD上行频率.
类型: Element
格式: Char String
定义: 0-16383
缺省值: -
举例: <uarfcn_ul>2345</ uarfcn_ul >
注释:
7.25. uarfcn_dl
描述:
WCDMA, FDD下行频率
类型: Element
格式: Char String
定义: 0-16383
缺省值: -
举例: <uarfcn_dl>2345</ uarfcn_dl >
注释:
7.26. uarfcn_nt
描述:
WCDMA, TDD频率
类型: Element
格式: Char String
定义: 0-16383
缺省值: -
举例: <uarfcn_nt>2345</ uarfcn_nt >
注释:
7.27. nid
描述:
QB-D-121-2007
46
CDMA network identity
类型: Element
格式: Char String
定义: 0-65535
缺省值: -
举例: <nid>2345</ nid >
注释:
7.28. sid
描述:
CDMA system identity
类型: Element
格式: Char String
定义: 0-32767
缺省值: -
举例: <sid>2345</ sid >
注释:
7.29. base_id
描述:
CDMA base station identity
类型: Element
格式: Char String
定义: 0-65535
缺省值: -
举例: <base_id>2345</ base_id >
注释:
7.30. base_lat
描述:
CDMA Base Station Latitude
类型: Element
格式: Char String
QB-D-121-2007
47
定义: 0-41943035
缺省值: -
举例: <base_lat>2345678</ base_lat >
注释:
7.31. base_long
描述:
CDMA Base Station Longitude
类型: Element
格式: Char String
定义: 0-8388607
缺省值: -
举例: <base_long>234567</ base_long >
注释:
7.32. ref_pn
描述:
CDMA Base Station PN Code
类型: Element
格式: Char String
定义: 0-511
缺省值: -
举例: <ref_pn>2345</ ref_pn >
注释:
7.33. sgsnno
描述:
SGSN 唯一标识号
类型: Element
格式: Char String
定义: In GSM/WCDMA, defined values shall be according to ITU-T E.164.
缺省值:
举例: <sgsnno>1541154871</sgsnno>
注释:
QB-D-121-2007
48
7.34. locationserver
描述:
填写消息发起方LSP的鉴权信息,包含帐号和密码。
类型: Element
格式: Char String
定义值: -
缺省值: -
例子: <locationserver>
<id> [email protected] </id>
<pwd>thepwd</pwd>
</locationserver>
注释:
7.35. post_auth
描述:
表示是否对主叫号码进行定位后的鉴权操作。
类型: Attribute
格式: Char String
YES 定义值:
NO
缺省值:
例子: <srsaa ver="2.0.0" post_auth="NO">
注释:
7.36. posfixlspid
描述:
生成定位结果的LSP的id。
类型: Element
格式: Char String
定义值: 国家码 + 长途电话省会区号(前去零)+1位序号
默认值: -
例子: < posfixlspid>86100</ posfixlspid>
注释: LSP计算得到位置结果后,必须填写该元素。其他接收到含有该元素的消息的LSP
QB-D-121-2007
49
必须保留该元素,并将该元素记录于计费话单。
7.37. target
描述:
被定位用户的MSISDN
类型: Element
格式: Char String
定义值: -
缺省值: -
例子: <target >8613800138000</target>
注释: 该参数必须兼容有无86前缀两种格式。
7.38. collab_id
描述:
collaboration id,各LSP服务器之间、LSP服务器与AGPS服务器之间的协 号同
类型: Element
格式: Char String
定义值: “C”+ 接入地LSP ID +日期(YYYYMMDD)+10 号位序列
缺省值: -
例子: <target >8613800138000</target>
注释: 接入地LSP产生collab_id,接入地LSP与归属地LSP 归属、 地LSP与漫游地的Lr请 须求消息必 包含collab_id, 对应 应 报其 的 答消息和 告消息
须必 包含此collab_id 应,以便 答/报 请 对应告消息和 求消息 。
8. 结果码定义
RLP 结果码见《中国移动位置服务 Le 接口技术规范 V2.0.0》,增加的结果码如下: 表 错误!文档中没有指定样式的文字。-1 OMA RLP 结果码
结
果
码
文字 说明
208 TARGET MOVED TO NEW MSC/SGSN
用户归属LSP需要丢弃Trigger Location Request,因为终端目标区域在另一个MSC/SGSN辖区。该
结果码仅用于LSP之间的应答/报告消息。 表 错误!文档中没有指定样式的文字。-2 CMCC 扩展结果码
结果码 文字 说明
QB-D-121-2007
50
758 LSP MISCONFIGURATION AND AGPS POSITIONING FAILURE
LID 数据缺失且 AGPS 定位失败。该结果码仅
用于 AGPS 返回 LSP 的应答/报告消息,接收
该结果码的 LSP 不再发起 Cell ID 定位作为回
退的定位方法。 759 AGPS POSITIONING FAILURE--
NEITHER LID POSTION NOR GPS POSTION
AGPS 平台发送定位请求给终端,但终端无应
答消息或发送异常应答消息。该错误码仅用于
LSP 与 AGPS 平台之间。 760 TARGET RECORDED AS A
NON-SUPL –ENABLED-TERMINAL
AGPS 平台判断该终端非 AGPS 终端,返回错
误结果。
9. HTTP 映射
本章描述怎样使用 HTTP 传输协议(HTTP/1.1)承载 RLP。 HTTP 是一个服务器和客户端之间的请求/响应协议。在 RLP 上下文看,客户端即业务
平台,服务器即 LSP(GMLC/MPC)。更多 HTTP 信息见[RFC2616]和 http://www.w3.org。 LSP 可(MAY)提供两个 Socket 端口,一为 SSL/TLS,一为透明传输端口。透明传输
的原因为加密传输需要更多资源,若业务平台在安全领域内,则可不使用加密传输。若业务
平台非处在安全领域内,如在因特网内,可使用加密传输,以确保安全和隐私。 SSL/TLS 更多信息参见[RFC2246]。
LSP 实现 MLP 的 2 个端口号如下(这些参数已由 IANA 分配):
oma-rlp 7273/tcp OMA Roaming Location Protocol
oma-rlp 7273/udp OMA Roaming Location Protocol
oma-rlp-s 7274/tcp OMA Roaming Location Protocol Secure
oma-rlp-s 7274/udp OMA Roaming Location Protocol Secure
LSP 可(MAY)选择其他基于 Socket 或 HTTP 透明传输技术,其他技术必须(SHALL)使用其他端口号。
9.1. Location Services using HTTP
请求 LSP 必须使用 HTTP POST 请求向服务 LSP(服务 LSP 包括归属地/漫游地 LSP 或
者 AGPS 服务器)发送定位请求,HTTP POST 请求更多信息参见[RFC2616]。请求的语法如
下: Request-line: POST SP host SP HTTP/1.1 CRLF
请求必须包含 entity-header Content-length 字段,消息体必须包含 XML 格式定位请求,
且必须具备 Content-length 字段指定的长度。 如果请求是触发类定位,服务 LSP 的定位应答/报告必须使用 HTTP POST 传送给请求
LSP。即请求必须具备接收 HTTP POST 请求和应答(response)功能。 所有定位服务使用 HTTP POST 传输一个请求消息至特定 URI。URI 的例子如下:
QB-D-121-2007
51
http://host:port/LocationQueryService/
应答消息使用HTTP response消息传输。如果请求LSP使用异步通信请求标准定位服务,
或者请求触发类定位,服务 LSP 必须使用 HTTP POST 返回定位报告消息。请求 LSP 必须
指定 URI,该 URI 通过定位请求消息指定或者预先设置在服务 LSP。 定位报告消息必须含于HTTP消息体,且Content-length entity必须设成应答消息的长度。 当请求LSP请求规范中未定义的服务(service),服务LSP必须返回GEM消息使用HTTP
'404' 表示错误消息。 Status-Line: HTTP/1.1 SP 404 SP Not Found CRLF
9.2. 定位请求和应答封装
HTTP 请求消息必须包含消息头和消息体。应答消息可(MAY)包含消息头,必须包含
消息体。为使得一个定位请求包含一个 XML 文件,定位请求的消息头和消息体封装在同一
个 service initiation DTD。定位应答/报告的消息头和消息体封装在同一个 service result DTD,
消息头包含鉴权和授权信息,消息体的定义 6.3.2 – 6.3.6.。
9.2.1. Inter-Location Server Service Initiation DTD
<!-- RLP_SVC_INIT -->
<!ENTITY % extension.message "">
<!ELEMENT rlp_svc_init (rlp_hdr, (srlir | trlrr | trlrsr | erlir | srsar | ssrp
%extension.message;))>
<!ATTLIST rlp_svc_init
ver CDATA #FIXED "2.0.0">
<!ENTITY % rlp_ctxt.dtd SYSTEM "RLP_CTXT_200.DTD">
%rlp_ctxt.dtd;
<!ENTITY % mlp_id.dtd SYSTEM "MLP_ID_200.DTD">
%mlp_id.dtd;
<!ENTITY % mlp_func.dtd SYSTEM "RLP_FUNC_200.DTD">
%mlp_func.dtd;
<!ENTITY % mlp_qop.dtd SYSTEM "MLP_QOP_200.DTD">
%mlp_qop.dtd;
<!ENTITY % rlp_loc.dtd SYSTEM "RLP_LOC_200.DTD">
%rlp_loc.dtd;
<!ENTITY % mlp_shape.dtd SYSTEM "MLP_SHAPE_200.DTD">
%mlp_shape.dtd;
<!ENTITY % rlp_net.dtd SYSTEM "RLP_NET_200.DTD">
QB-D-121-2007
52
%rlp_net.dtd;
<!ENTITY % rlp_hdr.dtd SYSTEM "RLP_HDR_200.DTD">
%rlp_hdr.dtd;
<!ENTITY % rlp_srlir.dtd SYSTEM "RLP_SRLIR_200.DTD">
%rlp_srlir.dtd;
<!ENTITY % rlp_trlrr.dtd SYSTEM "RLP_TRLRR_200.DTD">
%rlp_trlrr.dtd;
<!ENTITY % rlp_trlrsr.dtd SYSTEM "RLP_TRLRSR_200.DTD">
%rlp_trlrsr.dtd;
<!ENTITY % rlp_erlir.dtd SYSTEM "RLP_ERLIR_200.DTD">
%rlp_erlir.dtd;
<!ENTITY % rlp_srsar.dtd SYSTEM "RLP_ SRSAR _200.DTD">
%rlp_ srsar.dtd;
例 1
<?xml version="1.0" ?>
<!DOCTYPE rlp_svc_init SYSTEM "RLP_SVC_INIT_200.DTD">
<rlp_svc_init ver="2.0.0">
<rlp_hdr ver="2.0.0">
...
</rlp_hdr>
<srlir ver="2.0.0">
...
</srlir>
</rlp_svc_init>
9.2.2. Inter-Location Server Service Result DTD
<!-- RLP_SVC_RESULT -->
<!ENTITY % extension.message "">
<!ELEMENT rlp_svc_result (rlp_hdr?, (srlia | srlirep | trlra | trlrep | trlrsa
| srlrep | srlra | erlia | srsaa | %extension.message;))>
<!ATTLIST rlp_svc_result
ver CDATA #FIXED "2.0.0">
<!ENTITY % rlp_ctxt.dtd SYSTEM "RLP_CTXT_200.DTD">
%rlp_ctxt.dtd;
<!ENTITY % mlp_id.dtd SYSTEM "MLP_ID_200.DTD">
QB-D-121-2007
53
%mlp_id.dtd;
<!ENTITY % mlp_func.dtd SYSTEM "RLP_FUNC_200.DTD">
%mlp_func.dtd;
<!ENTITY % mlp_qop.dtd SYSTEM "MLP_QOP_200.DTD">
%mlp_qop.dtd;
<!ENTITY % rlp_loc.dtd SYSTEM "RLP_LOC_200.DTD">
%rlp_loc.dtd;
<!ENTITY % mlp_shape.dtd SYSTEM "MLP_SHAPE_200.DTD">
%mlp_shape.dtd;
<!ENTITY % rlp_net.dtd SYSTEM "RLP_NET_200.DTD">
%rlp_net.dtd;
<!ENTITY % rlp_hdr.dtd SYSTEM "RLP_HDR_200.DTD">
%rlp_hdr.dtd;
<!ENTITY % rlp_srlia.dtd SYSTEM "RLP_SRLIA_200.DTD">
%rlp_srlia.dtd;
<!ENTITY % rlp_srlirep.dtd SYSTEM "RLP_SRLIREP_200.DTD">
%rlp_srlirep.dtd;
<!ENTITY % rlp_trlra.dtd SYSTEM "RLP_TRLRA_200.DTD">
%rlp_trlra.dtd;
<!ENTITY % rlp_trlrep.dtd SYSTEM "RLP_TRLREP_200.DTD">
%rlp_trlrep.dtd;
<!ENTITY % rlp_trlrsa.dtd SYSTEM "RLP_TRLRSA_200.DTD">
%rlp_trlrsa.dtd;
<!ENTITY % rlp_srlrep.dtd SYSTEM "RLP_SRLREP_200.DTD">
%rlp_srlrep.dtd;
<!ENTITY % rlp_srlra.dtd SYSTEM "RLP_SRLRA_200.DTD">
%rlp_srlra.dtd;
<!ENTITY % rlp_erlia.dtd SYSTEM "RLP_ERLIA_200.DTD">
%rlp_erlia.dtd;
<!ENTITY % rlp_ srsaa.dtd SYSTEM "RLP_ SRSAA _200.DTD">
%rlp_ srsaa.dtd;
例 1
<?xml version="1.0" ?>
<!DOCTYPE rlp_svc_result SYSTEM "RLP_SVC_RESULT_200.DTD">
<rlp_svc_result ver="2.0.0">
<srlia ver="2.0.0">
...
</srlia>
</rlp_svc_result>
QB-D-121-2007
54
10. 与 Lr2.0.0 的差别
Lp2.0.0消息和元素定义同Lr2.0.0,DTD文件同。
11. 编制历史
版本号 更新时间 主要内容或重大修改
V2.0.0(送审稿) 2007-3-10 基于 Lr2.0.0 的基础编制 Lp2.0.0 规范。 修改前言、范围、接口示意图。
V2.0.0(报批稿) 2007-6-29 经评审,完成报批稿。
附录 A Server side requirements (Normative)
以下术语定义参见 [IOPPROC]。
A.1 Server side requirements (Normative)
A.1.1 General Requirements
Item Function Reference Status Requirement
RLP-A-S-001 Parsing of DTDs 5.1 M
RLP-A-S-002 Invalid values 5.3 M
RLP-A-S-003 Support of EPSPG 4326
5.5 M
RLP-A-S-004 Version handling 5.2 M
RLP-A-S-005 Quality of Position 5.4 O
RLP-A-S-006 Target Identities, support of MSISDN
5.7 M
RLP-A-S-007 Priority 5.6 O
A.1.2 Inter-Location Server Service Initiation DTD
Item Function Reference Status Requirement
QB-D-121-2007
55
Item Function Reference Status Requirement
RLP-B-S-001 Inter-Location Server Service Initiation
9.2.1 M RLP-B-S-002 AND
RLP-B-S-003
RLP-B-S-002 RLP Header 9.2.1 M
RLP-B-S-003 Standard Roaming Location Immediate Request
9.2.1 M RLP-C-S-003
RLP-B-S-004 Triggered Roaming Location Reporting Request
9.2.1 O RLP-C-S-005 AND RLP-C-S-006 AND RLP-C-S-007
RLP-B-S-005 Triggered Roaming Location Reporting Stop Request
9.2.1 O RLP-C-S-007 RLP-F-S-002
RLP-B-S-006 Emergency Roaming Location Immediate Request
9.2.1 O RLP-C-S-008
RLP-B-S-007 Standard Roaming s Subscriber Authentication Request
9.2.1 O RLP-C-S-009
RLP-B-S-008 Standard Roaming s Subscriber Authentication Answer
9.2.1 O RLP-C-S-010
RLP-B-S-009 Extension Message 9.2.1 O
A.1.3 Inter-Location Server Service Result DTD
Item Function Reference Status Requirement
RLP-C-S-001 Inter-Location Server Service Result
9.2.2 M RLP-C-S-002 AND
RLP-C-S-003
RLP-C-S-002 RLP Header 9.2.2 O
RLP-C-S-003 Standard Roaming Location Immediate Answer
9.2.2 M
RLP-C-S-004 Standard Roaming Location Immediate Report
9.2.2 O RLP-F-S-002
RLP-C-S-005 Triggered Roaming Location Reporting Answer
9.2.2 O RLP-C-S-006 RLP-F-S-002
QB-D-121-2007
56
Item Function Reference Status Requirement
RLP-C-S-006 Triggered Roaming Location Report
9.2.2 O RLP-C-S-005 RLP-F-S-002
RLP-C-S-007 Triggered Roaming Location Reporting Stop Answer
9.2.2 O RLP-F-S-002
RLP-C-S-008 Standard Roaming Location Report
9.2.2 O
RLP-C-S-009 Standard Roaming Location Report Answer
9.2.2 O
RLP-C-S-010 Emergency Roaming Location Immediate Answer
9.2.2 O
RLP-C-S-09 Standard Roaming s Subscriber Authentication Request
9.2.2 O
RLP-C-S-012 Standard Roaming s Subscriber Authentication Answer
9.2.2 O RLP-B-S-008
RLP-C-S-013 Extension Message 9.2.2 M
A.1.4 Roaming Header
Item Function Reference Status Requirement
RLP-D-S-001 locationserver 6.3.1 M
RLP-D-S-002 client 6.3.1 M
RLP-D-S-003 serving_node_action 6.3.1 M
RLP-D-S-004 net_param 6.3.1 O
RLP-D-S-005 supported_shapes 6.3.1 M
A.1.5 Standard Roaming Location Immediate Request
Item Function Reference Status Requirement
RLP-E-S-001 msid 6.3.2.1 M
RLP-E-S-002 codeword 6.3.2.1 O
RLP-E-S-003 eqop 6.3.2.1 O
RLP-E-S-004 geo_info 6.3.2.1 O
QB-D-121-2007
57
Item Function Reference Status Requirement
RLP-E-S-005 loc_type 6.3.2.1 O
RLP-E-S-006 prio 6.3.2.1 O
RLP-E-S-007 pushaddr 6.3.2.1 O
RLP-E-S-008 Extension parameters
6.3.2.1 O
A.1.6 Standard Roaming Location Immediate Answer
Item Function Reference Status Requirement
RLP-F-S-001 pos 6.3.2.2 M
RLP-F-S-002 req_id 6.3.2.2 O
RLP-F-S-003 result 6.3.2.2 M
RLP-F-S-004 add_info 6.3.2.2 O
RLP-F-S-005 Extension parameters
6.3.2.2 O
A.1.7 Standard Roaming Location Immediate Report
Item Function Reference Status Requirement
RLP-G-S-001 req_id 6.3.2.3 M
RLP-G-S-002 pos 6.3.2.3 M
RLP-G-S-003 Extension parameters
6.3.2.3 O
A.1.8 Triggered Roaming Location Reporting Request
Item Function Reference Status Requirement
RLP-H-S-001 msid 6.3.3.1 M
RLP-H-S-002 codeword 6.3.3.1 O
RLP-H-S-003 interval 6.3.3.1 O
RLP-H-S-004 start_time 6.3.3.1 O
RLP-H-S-005 stop_time 6.3.3.1 O
RLP-H-S-006 duration 6.3.3.1 O
RLP-H-S-007 tlrr_event 6.3.3.1 M
RLP-H-S-008 qop 6.3.3.1 O
RLP-H-S-009 geo info 6.3.3.1 O
RLP-H-S-010 pushaddr 6.3.3.1 O
RLP-H-S-09 loc type 6.3.3.1 O
QB-D-121-2007
58
Item Function Reference Status Requirement
RLP-H-S-012 prio 6.3.3.1 O
RLP-H-S-013 Extension parameters
6.3.3.1 O
RLP-H-S-014 lcs_ref 6.3.3.1 O
A.1.9 Triggered Roaming Location Reporting Answer
Item Function Reference Status Requirement
RLP-I-S-001 req_id 6.3.3.2 M
RLP-I-S-002 lcs_ref 6.3.3.2 O
RLP-I-S-003 result 6.3.3.2 M
RLP-I-S-004 add_info 6.3.3.2 O
A.1.10 Triggered Roaming Location Report
Item Function Reference Status Requirement
RLP-J-S-001 req_id 6.3.3.3 M
RLP-J-S-002 lcs_ref 6.3.3.3 O
RLP-J-S-003 trl_pos 6.3.3.3 M
RLP-J-S-004 time_remaining 6.3.3.3 O
RLP-J-S-005 Extension parameters
6.3.3.3 O
A.1.11 Triggered Roaming Location Reporting Stop Request
Item Function Reference Status Requirement
RLP-K-S-001 req_id 6.3.3.4 M
RLP-K-S-002 Extension parameters
6.3.3.4 O
RLP-K-S-003 lcs_ref 6.3.3.4 O
A.1.12 Triggered Roaming Location Reporting Stop Answer
Item Function Reference Status Requirement
RLP-L-S-001 req_id 6.3.3.5 M
RLP-L-S-002 result 6.3.3.5 M
RLP-L-S-003 add_info 6.3.3.5 O
RLP-L-S-004 Extension 6.3.3.5 O
QB-D-121-2007
59
Item Function Reference Status Requirement
parameters
A.1.13 Emergency Roaming Location Immediate Request
Item Function Reference Status Requirement
RLP-M-S-001 msid 7.3.4.1 M
RLP-M-S-002 esrd 7.3.4.1 O
RLP-M-S-003 esrk 7.3.4.1 O
RLP-M-S-004 eqop 7.3.4.1 O
RLP-M-S-005 geo_info 7.3.4.1 O
RLP-M-S-006 loc_type 7.3.4.1 O
RLP-M-S-007 Extension parameters
7.3.4.1 O
A.1.14 Emergency Roaming Location Immediate Answer
Item Function Reference Status Requirement
RLP-N-S-001 eme_pos 7.3.4.2 M
RLP-N-S-002 result 7.3.4.2 M
RLP-N-S-003 add_info 7.3.4.2 O
RLP-N-S-004 Extension parameters
7.3.4.2 O
A.1.15 Support for Identity Elements
Item Function Reference Status Requirement
RLP-O-S-001 msid [OMA-MLP] 5.2.2.1
M
RLP-O-S-002 codeword [OMA-MLP] 5.2.2.1
O
RLP-O-S-003 esrd [OMA-MLP] 5.2.2.1
O
RLP-O-S-004 esrk [OMA-MLP] 5.2.2.1
O
RLP-O-S-005 session [OMA-MLP] 5.2.2.1
O
QB-D-121-2007
60
A.1.16 Support for Function Elements
Item Function Reference Status Requirement
RLP-P-S-001 eme_event 6.2.2 O
RLP-P-S-002 tlrr_event 6.2.2 O
RLP-P-S-003 ms_action 6.2.2 O
RLP-P-S-004 interval 6.2.2 O
RLP-P-S-005 loc_type 6.2.2 O
RLP-P-S-006 prio 6.2.2 O
RLP-P-S-007 pushaddr 6.2.2 O
RLP-P-S-008 req_id 6.2.2 O
RLP-P-S-009 lcs_ref 6.2.2 O
RLP-P-S-010 start_time 6.2.2 O
RLP-P-S-09 stop_time 6.2.2 O
RLP-P-S-012 url 6.2.2 O
RLP-P-S-013 time_remaining 6.2.2 O
A.1.17 Support for Location Elements
Item Function Reference Status Requirement
RLP-Q-S-001 pos 6.2.3 M
RLP-Q-S-002 eme_pos 6.2.3 O
RLP-Q-S-003 pd 6.2.3 M
RLP-Q-S-004 poserr 6.2.3 M
RLP-Q-S-005 time 6.2.3 M
RLP-Q-S-006 alt 6.2.3 O
RLP-Q-S-007 alt_unc 6.2.3 O
RLP-Q-S-008 direction 6.2.3 O
RLP-Q-S-009 speed 6.2.3 O
RLP-Q-S-010 lev_conf 6.2.3 O
RLP-Q-S-09 qop_not_met 6.2.3 O
RLP-Q-S-012 geo_info 6.2.3 O
A.1.18 Support for Result Elements
Item Function Reference Status Requirement
RLP-R-S-001 add_info [OMA-MLP] 5.2.2.4
O
QB-D-121-2007
61
Item Function Reference Status Requirement
RLP-R-S-002 result [OMA-MLP] 5.2.2.4
M
A.1.19 Support for Shape Elements
Item Function Reference Status Requirement
RLP-S-S-S01 shape [OMA-MLP] 5.2.2.5
M RLP-S-S-S02 OR
RLP-S-S-S03 OR
RLP-S-S-S04 OR
RLP-S-S-S05 OR
RLP-S-S-S06 OR
RLP-S-S-S07 OR
RLP-S-S-S08 OR
RLP-S-S-S09 OR
RLP-S-S-S10 OR
RLP-S-S-S9
RLP-S-S-S02 Point [OMA-MLP] 5.2.2.5
O
RLP-S-S-S03 LineString [OMA-MLP] 5.2.2.5
O
RLP-S-S-S04 Box [OMA-MLP] 5.2.2.5
O
RLP-S-S-S05 LinearRing [OMA-MLP] 5.2.2.5
O
RLP-S-S-S06 Polygon [OMA-MLP] 5.2.2.5
O
RLP-S-S-S07 CircularArcArea [OMA-MLP] 5.2.2.5
O
RLP-S-S-S08 EllipticalArea [OMA-MLP] 5.2.2.5
O
RLP-S-S-S09 MultiLineString [OMA-MLP] 5.2.2.5
O
RLP-S-S-S10 MultiPoint [OMA-MLP] 5.2.2.5
O
RLP-S-S-S9 MultiPolygon [OMA-MLP] 5.2.2.5
O
QB-D-121-2007
62
A.1.20 Support for Quality of Position Elements
Item Function Reference Status Requirement
RLP-T-S-001 eqop [OMA-MLP] 5.2.2.6
O
RLP-T-S-002 qop [OMA-MLP] 5.2.2.6
O
RLP-T-S-003 ll_acc [OMA-MLP] 5.2.2.6
O
RLP-T-S-004 hor_acc [OMA-MLP] 5.2.2.6
O
RLP-T-S-005 max_loc_age [OMA-MLP] 5.2.2.6
O
RLP-T-S-006 resp_req [OMA-MLP] 5.2.2.6
O
RLP-T-S-007 resp_timer [OMA-MLP] 5.2.2.6
O
RLP-T-S-07 alt_acc [OMA-MLP] 5.2.2.6
O
A.1.21 Support for Network Parameter Elements
Item Function Reference Status Requirement
RLP-U-S-001 net_param 6.2.7 O
RLP-U-S-002 gsm_net_param 6.2.7 O RLP-U-S-005
RLP-U-S-003 wcdma_net_param 6.2.7 O RLP-U-S-005
RLP-U-S-004 cdma_net_param 6.2.7 O
RLP-U-S-005 neid 6.2.7 O RLP-U-S-006 OR RLP-U-S-008
RLP-U-S-006 vmcscid 6.2.7 O
RLP-U-S-007 vlrid 6.2.7 O
RLP-U-S-008 sgsnid 6.2.7 O
RLP-U-S-009 imsi 6.2.7 O
RLP-U-S-010 h_ls 6.2.7 O
RLP-U-S-09 v_ls 6.2.7 O
RLP-U-S-012 pce 6.2.7 O
QB-D-121-2007
63
A.1.22 Support for Roaming Context and Privacy Elements
Item Function Reference Status Requirement
RLP-V-S-001 client 6.2.8 M
RLP-V-S-002 id 6.2.8 M
RLP-V-S-003 requestor 6.2.8 O
RLP-V-S-004 pwd 6.2.8 O
RLP-V-S-005 serviceid 6.2.8 O
RLP-V-S-006 requestmode 6.2.8 M
RLP-V-S-007 locationserver 6.2.8 M
RLP-V-S-008 clientname 6.2.8 O
RLP-V-S-009 serving_node_action 6.2.8 M
RLP-V-S-010 poi 6.2.8 M
RLP-V-S-09 pseudoid 6.2.8 M
RLP-V-S-012 servicetype 6.2.8 M
RLP-V-S-013 supported_shapes 6.2.8 O
A.1.23 Service attributes
Item Function Reference Status Requirement
RLP-W-S-001 res_type [OMA-MLP] 5.3.85
M
RLP-W-S-002 ver [OMA-MLP] 5.3.85
M
RLP-W-S-003 recv_role 8.41 M
A.1.24 Standard Roaming Subscriber Authentication
Item Function Reference Status Requirement
RLP-X-S-001 target 6.3.5 M
A.1.25 Standard Roaming Location Report Answer
Item Function Reference Status Requirement
RLP-Y-S-001 result 6.3.6.2 M
RLP-Y-S-002 add_info 6.3.6.2 O
RLP-Y-S-003 Extension parameters
6.3.6.2 O
QB-D-121-2007
64
A.1.26 Standard Roaming Location Report
Item Function Reference Status Requirement
RLP-Z-S-001 pos 6.3.6.1 M
RLP-Z-S-002 Extension parameters
6.3.6.1 O
A.1.27 Transport mechanisms
Item Function Reference Status Requirement
RLP-AA-S-001 Support of HTTP mapping
6.1
M
RLP-AA-S-002 Support of port 7273 9 O
RLP-AA-S-003 Support of port 7274 9 O
RLP-AA-S-004 Support of transfer over other ports
9 O
A.1.28 Services
Item Function Reference Status Requirement
RLP-BB-S-001 Standard Roaming Location Immediate Service
6.3.2 M RLP-B-S-003 AND RLP-C-S-003 AND RLP-C-S-004
RLP-BB-S-002 Triggered Roaming Location Reporting Service
6.3.3 O RLP-B-S-004 AND RLP-B-S-005 AND RLP-C-S-005 AND RLP-C-S-006 AND RLP-C-S-007
RLP-BB-S-002 Emergency Roaming Location Immediate Service
6.3.4 O RLP-B-S-006 AND RLP-C-S-010
RLP-BB-S-003 Standard Roaming Subscriber Authentication Service
6.3.5 O RLP-B-S-007 AND RLP-B-S-008 AND RLP-C-S-09 AND RLP-C-S-012
RLP-BB-S-004 Standard Roaming Location Reporting Service
6.3.6 O RLP-C-S-008 AND RLP-C-S-009
QB-D-121-2007
65
A.2 Client side requirements
A.2.1 General Requirements
Item Function Reference Status Requirement
RLP-A-C-001 Parsing of DTDs 5.1 M
RLP-A-C-002 Invalid values 5.3 M
RLP-A-C-003 Support of ESPG 4326
5.5 M
RLP-A-C-004 Version handling 5.2 M
RLP-A-C-005 Quality of Position 5.4 O
RLP-A-C-006 Target Identities, support of MSISDN
5.7 M
RLP-A-C-007 Priority 5.6 O
A.2.2 Inter-Location Server Service Initiation DTD
Item Function Reference Status Requirement
RLP-B-C-001 Inter-Location Server Service Initiation
9.2.1 M RLP-B-C-002 AND
RLP-B-C-003
RLP-B-C-002 RLP Header 9.2.1 M
RLP-B-C-003 Standard Roaming Location Immediate Request
9.2.1 M RLP-C-C-003
RLP-B-C-004 Triggered Roaming Location Reporting Request
9.2.1 O RLP-C-C-005 AND RLP-C-C-006 AND RLP-C-C-007
RLP-B-C-005 Triggered Roaming Location Reporting Stop Request
9.2.1 O RLP-C-C-007
RLP-B-C-006 Emergency Roaming Location Immediate Request
9.2.1 O RLP-C-C-008
RLP-B-C-007 Standard Roaming s Subscriber Authentication Request
9.2.1 O RLP-C-C-009
RLP-B-C-008 Standard Roaming s Subscriber Authentication
9.2.1 O RLP-C-C-010
QB-D-121-2007
66
Item Function Reference Status Requirement
Answer
RLP-B-C-010 Extension Message 9.2.1 O
A.2.3 Inter-Location Server Service Result DTD
Item Function Reference Status Requirement
RLP-C-C-001 Inter-Location Server Service Result
9.2.2 M RLP-C-C-002 AND
RLP-C-C-003
RLP-C-C-002 RLP Header 9.2.2 O
RLP-C-C-003 Standard Roaming Location Immediate Answer
9.2.2 M
RLP-C-C-004 Standard Roaming Location Immediate Report
9.2.2 O RLP-F-C-002
RLP-C-C-005 Triggered Roaming Location Reporting Answer
9.2.2 O RLP-C-C-006
RLP-C-C-006 Triggered Roaming Location Report
9.2.2 O RLP-C-C-005
RLP-C-C-007 Triggered Roaming Location Reporting Stop Answer
9.2.2 O
RLP-C-C-008 Standard Roaming Location Report
9.2.2 O
RLP-C-C-009 Standard Roaming Location Report Answer
9.2.2 O
RLP-C-C-010 Emergency Roaming Location Immediate Answer
9.2.2 O
RLP-C-C-09 Standard Roaming s Subscriber Authentication Request
9.2.2 O
RLP-C-C-012 Standard Roaming s Subscriber Authentication Answer
9.2.2 O RLP-B-C-008
RLP-C-C-013 Extension Message 9.2.2 O
QB-D-121-2007
67
A.2.4 Roaming Header
Item Function Reference Status Requirement
RLP-D-C-001 locationserver 6.3.1 M
RLP-D-C-002 client 6.3.1 O
RLP-D-C-003 serving_node_action 6.3.1 M
RLP-D-C-004 net_param 6.3.1 O
RLP-D-C-005 supported_shapes 6.3.1 M
A.2.5 Standard Roaming Location Immediate Request
Item Function Reference Status Requirement
RLP-E-C-001 msid 6.3.2.1 M
RLP-E-C-002 codeword 6.3.2.1 O
RLP-E-C-003 eqop 6.3.2.1 O
RLP-E-C-004 geo_info 6.3.2.1 O
RLP-E-C-005 loc_type 6.3.2.1 O
RLP-E-C-006 prio 6.3.2.1 O
RLP-E-C-007 pushaddr 6.3.2.1 O
RLP-E-C-008 Extension parameters
6.3.2.1 O
A.2.6 Standard Roaming Location Immediate Answer
Item Function Reference Status Requirement
RLP-F-C-001 pos 6.3.2.2 M
RLP-F-C-002 req_id 6.3.2.2 O
RLP-F-C-003 result 6.3.2.2 M
RLP-F-C-004 add_info 6.3.2.2 O
RLP-F-C-005 Extension parameters
6.3.2.2 O
A.2.7 Standard Roaming Location Immediate Report
Item Function Reference Status Requirement
RLP-G-C-001 req_id 6.3.2.3 O
RLP-G-C-002 pos 6.3.2.3 M
RLP-G-C-003 Extension 6.3.2.3 O
QB-D-121-2007
68
Item Function Reference Status Requirement
parameters
A.2.8 Triggered Roaming Location Reporting Request
Item Function Reference Status Requirement
RLP-H-C-001 msid 6.3.3.1 M
RLP-H-C-002 codeword 6.3.3.1 O
RLP-H-C-003 interval 6.3.3.1 O
RLP-H-C-004 start_time 6.3.3.1 O
RLP-H-C-005 stop_time 6.3.3.1 O
RLP-H-C-006 duration 6.3.3.1 O
RLP-H-C-007 tlrr_event 6.3.3.1 M
RLP-H-C-008 qop 6.3.3.1 O
RLP-H-C-009 geo info 6.3.3.1 O
RLP-H-C-010 pushaddr 6.3.3.1 O
RLP-H-C-09 loc type 6.3.3.1 O
RLP-H-C-012 prio 6.3.3.1 O
RLP-H-C-013 Extension parameters
6.3.3.1 O
RLP-H-C-014 lcs_ref 6.3.3.1 O
A.2.8 Triggered Roaming Location Reporting Answer
Item Function Reference Status Requirement
RLP-I-C-001 req_id 6.3.3.2 M
RLP-I-C-002 lcs_ref 6.3.3.2 O
RLP-I-C-003 result 6.3.3.2 M
RLP-I-C-004 add_info 6.3.3.2 O
A.2.10 Triggered Roaming Location Report
Item Function Reference Status Requirement
RLP-J-C-001 req_id 6.3.3.3 M
RLP-J-C-002 lcs_ref 6.3.3.3 O
RLP-J-C-003 trl_pos 6.3.3.3 M
RLP-J-C-004 time_remaining 6.3.3.3 O
RLP-J-C-005 Extension 6.3.3.3 O
QB-D-121-2007
69
Item Function Reference Status Requirement
parameters
A.2.11 Triggered Roaming Location Reporting Stop Request
Item Function Reference Status Requirement
RLP-K-C-001 req_id 6.3.3.4 M
RLP-K-C-002 Extension parameters
6.3.3.4 O
RLP-K-C-003 lcs_ref 6.3.3.4 O
A.2.12 Triggered Roaming Location Reporting Stop Answer
Item Function Reference Status Requirement
RLP-L-C-001 req_id 6.3.3.5 M
RLP-L-C-002 result 6.3.3.5 M
RLP-L-C-003 add_info 6.3.3.5 O
RLP-L-C-004 Extension parameters
6.3.3.5 O
A.2.13 Emergency Roaming Location Immediate Request
Item Function Reference Status Requirement
RLP-M-C-001 msid 6.3.4.1 M
RLP-M-C-002 esrd 6.3.4.1 O
RLP-M-C-003 esrk 6.3.4.1 O
RLP-M-C-004 eqop 6.3.4.1 O
RLP-M-C-005 geo_info 6.3.4.1 O
RLP-M-C-006 loc_type 6.3.4.1 O
RLP-M-C-007 Extension parameters
6.3.4.1 O
A.2.14 Emergency Roaming Location Immediate Answer
Item Function Reference Status Requirement
RLP-N-C-001 eme_pos 6.3.4.2 M
RLP-N-C-002 result 6.3.4.2 M
RLP-N-C-003 add_info 6.3.4.2 O
RLP-N-C-004 Extension 6.3.4.2 O
QB-D-121-2007
70
Item Function Reference Status Requirement
parameters
A.2.15 Support for Identity Elements
Item Function Reference Status Requirement
RLP-O-C-001 msid [OMA-MLP] 5.2.2.1
M
RLP-O-C-002 codeword [OMA-MLP] 5.2.2.1
O
RLP-O-C-003 esrd [OMA-MLP] 5.2.2.1
O
RLP-O-C-004 esrk [OMA-MLP] 5.2.2.1
O
RLP-O-C-005 session [OMA-MLP] 5.2.2.1
O
A.2.16 Support for Function Elements
Item Function Reference Status Requirement
RLP-P-C-001 eme_event 6.2.2 O
RLP-P-C-002 tlrr_event 6.2.2 O
RLP-P-C-003 ms_action 6.2.2 O
RLP-P-C-004 interval 6.2.2 O
RLP-P-C-005 loc_type 6.2.2 O
RLP-P-C-006 prio 6.2.2 O
RLP-P-C-007 pushaddr 6.2.2 O
RLP-P-C-008 req_id 6.2.2 O
RLP-P-C-009 lcs_ref 6.2.2 O
RLP-P-C-010 start_time 6.2.2 O
RLP-P-C-09 stop_time 6.2.2 O
RLP-P-C-012 url 6.2.2 O
RLP-P-C-013 time_remaining 6.2.2 O
A.2.17 Support for Location Elements
Item Function Reference Status Requirement
RLP-Q-C-001 pos 6.2.3 M
RLP-Q-C-002 eme_pos 6.2.3 O
QB-D-121-2007
71
Item Function Reference Status Requirement
RLP-Q-C-003 pd 6.2.3 M
RLP-Q-C-004 poserr 6.2.3 M
RLP-Q-C-005 time 6.2.3 M
RLP-Q-C-006 alt 6.2.3 O
RLP-Q-C-007 alt_unc 6.2.3 O
RLP-Q-C-008 direction 6.2.3 O
RLP-Q-C-009 speed 6.2.3 O
RLP-Q-C-010 lev_conf 6.2.3 O
RLP-Q-C-09 qop_not_met 6.2.3
RLP-Q-C-012 geo_info 6.2.3 O
A.2.18 Support for Result Elements
Item Function Reference Status Requirement
RLP-R-C-001 add_info [OMA-MLP] 5.2.2.4
O
RLP-R-C-002 result [OMA-MLP] 5.2.2.4
M
A.2.19 Support for Shape Elements
Item Function Reference Status Requirement
RLP-S-C-001 shape [OMA-MLP] 5.2.2.5
M RLP-S-C-002 OR
RLP-S-C-003 OR
RLP-S-C-004 OR
RLP-S-C-005 OR
RLP-S-C-006 OR
RLP-S-C-007 OR
RLP-S-C-008 OR
RLP-S-C-009 OR
RLP-S-C-010 OR
RLP-S-C-09
RLP-S-C-002 Point [OMA-MLP] 5.2.2.5
O
RLP-S-C-003 LineString [OMA-MLP] 5.2.2.5
O
RLP-S-C-004 Box [OMA-MLP] 5.2.2.5
O
RLP-S-S-005 LinearRing [OMA-MLP] O
QB-D-121-2007
72
Item Function Reference Status Requirement
5.2.2.5
RLP-S-C-006 Polygon [OMA-MLP] 5.2.2.5
O
RLP-S-C-007 CircularArcArea [OMA-MLP] 5.2.2.5
O
RLP-S-C-008 EllipticalArea [OMA-MLP] 5.2.2.5
O
RLP-S-C-009 MultiLineString [OMA-MLP] 5.2.2.5
O
RLP-S-C-010 MultiPoint [OMA-MLP] 5.2.2.5
O
RLP-S-C-09 MultiPolygon [OMA-MLP] 5.2.2.5
O
A.2.20 Support for Quality of Position Elements
Item Function Reference Status Requirement
RLP-T-C-001 eqop [OMA-MLP] 5.2.2.6
O
RLP-T-C-002 qop [OMA-MLP] 5.2.2.6
O
RLP-T-C-003 ll_acc [OMA-MLP] 5.2.2.6
O
RLP-T-C-004 hor_acc [OMA-MLP] 5.2.2.6
O
RLP-T-C-005 max_loc_age [OMA-MLP] 5.2.2.6
O
RLP-T-C-006 resp_req [OMA-MLP] 5.2.2.6
O
RLP-T-C-007 resp_timer [OMA-MLP] 5.2.2.6
O
RLP-T-C-007 alt_acc [OMA-MLP] 5.2.2.6
O
A.2.21 Support for Network Parameter Elements
Item Function Reference Status Requirement
RLP-U-C-001 net_param 6.2.7 O
RLP-U-C-002 gsm_net_param 6.2.7 O RLP-U-C-005
QB-D-121-2007
73
Item Function Reference Status Requirement
RLP-U-C-003 wcdma_net_param 6.2.7 O RLP-U-C-005
RLP-U-C-004 cdma_net_param 6.2.7 O
RLP-U-C-005 neid O RLP-U-C-006 OR RLP-U-C-008
RLP-U-C-006 vmcscid 6.2.7 O
RLP-U-C-007 vlrid 6.2.7 O
RLP-U-C-008 sgsnid 6.2.7 O
RLP-U-C-009 imsi 6.2.7 O
RLP-U-C-010 h_ls 6.2.7 O
RLP-U-C-09 v_ls 6.2.7 O
RLP-U-C-012 pce 6.2.7 O
A.2.22 Support for Roaming Context and Privacy Elements
Item Function Reference Status Requirement
RLP-V-C-001 client 6.2.8 M
RLP-V-C-002 id 6.2.8 M
RLP-V-C-003 requestor 6.2.8 O
RLP-V-C-004 pwd 6.2.8 O
RLP-V-C-005 serviceid 6.2.8 O
RLP-V-C-006 requestmode 6.2.8 M
RLP-V-C-007 locationserver 6.2.8 M
RLP-V-C-008 clientname 6.2.8 O
RLP-V-C-009 serving_node_action 6.2.8 M
RLP-V-C-010 poi 6.2.8 M
RLP-V-C-09 pseudoid 6.2.8 M
RLP-V-C-012 servicetype 6.2.8 M
RLP-V-C-013 supported_shapes 6.2.8 O
A.2.23 Service attributes
Item Function Reference Status Requirement
RLP-W-C-001 res_type [OMA-MLP] 5.3.85
O
RLP-W-C-002 ver [OMA-MLP] 5.3.85
M
RLP-W-C-003 recv_role 8.41 M
QB-D-121-2007
74
A.2.24 Standard Roaming Location Report Answer
Item Function Reference Status Requirement
RLP-Y-C-001 result 6.3.6.2 M
RLP-Y-C-002 add_info 6.3.6.2 O
RLP-Y-C-003 Extension parameters
6.3.6.2 O
A.2.25 Standard Roaming Location Report
Item Function Reference Status Requirement
RLP-Z-C-001 pos 6.3.6.1 M
RLP-Z-C-002 Extension parameters
6.3.6.1 O
A.2.26 Transport mechanisms
Item Function Reference Status Requirement
RLP-AA-C-001 Support of HTTP mapping
6.1 M
RLP-AA-C-002 Support of port 7273 9 O
RLP-AA-C-003 Support of port 7274 9 O
RLP-AA-C-004 Support of transfer over other ports
9 O
A.2.27 Services
Item Function Reference Status Requirement
RLP-BB-C-001 Standard Roaming Location Immediate Service
6.3.2 M RLP-B-C-003 AND RLP-C-C-003 AND RLP-C-C-004
RLP-BB-C-002 Triggered Roaming Location Reporting Service
6.3.3 O RLP-B-C-004 AND RLP-B-C-005 AND RLP-C-C-005 AND RLP-C-C-006 AND RLP-C-C-007
RLP-BB-C-002 Emergency Roaming Location Immediate Service
6.3.4 O RLP-B-C-006 AND RLP-C-C-010
QB-D-121-2007
75
Item Function Reference Status Requirement
RLP-BB-C-003 Standard Roaming Subscriber Authentication Service
6.3.5 O RLP-B-C-007 AND RLP-B-C-008 AND RLP-C-C-09 AND RLP-C-C-012
RLP-BB-C-004 Standard Roaming Location Reporting Service
6.3.6 O RLP-C-C-008 AND RLP-C-C-009