Zxme Lbs Product Description(Gsm & Wcdma)_200809_en

8/17/2019 Zxme Lbs Product Description(Gsm & Wcdma)_200809_en

1/59

ZXME LBS Product Description

运营商LOGO


2/59


3/59


ZTE Confidential Proprietary © 2008 ZTE Corporation. All rights reserved. I


Version Date Author Approved By Remarks

V1.00 2008-06-18ShanLiang

Ding Zhen, HuangHaibo

Not open to the Third Party

© 2008 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to bedisclosed or used without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information of the document issubjected to change without notice.


4/59


II © 2008 ZTE Corporation. All rights reserved. ZTE ConfidentialProprietary

TABLE OF CONTENTS

1

Overview ..................................................................................................................... 1

2 Highlight Features ...................................................................................................... 2 2.1 Smooth Evolution ......................................................................................................... 2 2.2 Easy Installation ........................................................................................................... 2 2.3 Evolution to IP RAN ..................................................................................................... 3 2.4 Smooth Expansion ....................................................................................................... 3 2.5 Green Power ................................................................................................................ 3 2.6 Rich Interfaces ............................................................................................................. 4 2.7 Flexible Dual-mode Networking ................................................................................... 4

3 Functionality ............................................................................................................... 6 3.1 Basic Function ............................................................................................................. 7

3.1.1

Le Interface .................................................................................................................. 7 3.1.2 Signaling processing .................................................................................................... 8

3.1.3 MAP ATI in GSM ......................................................................................................... 8 3.1.4 Standard 3GPP MT-LR .............................................................................................. 10 3.1.5 SUPL v1.0 NI Location .............................................................................................. 11 3.1.6 SUPL v1.0 SI Location ............................................................................................... 12 3.1.7 Fetch Coarse Position through Lr in SUPL roaming ................................................. 14 3.1.8 Network based Periodical Location ........................................................................... 14 3.1.9 Position Cache ........................................................................................................... 14 3.1.10 Position Calculation and Conversation ...................................................................... 15 3.1.11 Time Synchronization ................................................................................................ 15 3.1.12 GPS Reference Network Interface ............................................................................ 15 3.1.13 CP/SP Authentication ................................................................................................ 16

3.1.14

User Privacy Management ........................................................................................ 16 3.1.15 Base Station Position Data Management .................................................................. 17

3.1.16 CDR Function ............................................................................................................ 17 3.1.17 Provisioning Function ................................................................................................ 18 3.2 Service Functions ...................................................................................................... 18 3.2.1 Choice of Location Procedure ................................................................................... 18 3.2.2 Flow Control ............................................................................................................... 19 3.2.3 Location Procedure Handover ................................................................................... 19 3.2.4 Roaming Interface ..................................................................................................... 19 3.2.5 Request Queuing Function ........................................................................................ 20 3.2.6 Restriction of Roaming .............................................................................................. 20 3.2.7 Standard 3GPP Deferred MT-LR .............................................................................. 20 3.2.8 Standard 3GPP NI-LR Report ................................................................................... 22

3.2.9

Network Management Interface ................................................................................ 23

3.2.10 Performance Statistic ................................................................................................. 24

4 System Architecture ................................................................................................ 25 4.1 Networking Architecture ............................................................................................. 25 4.2 Hardware Architecture ............................................................................................... 27 4.2.1 Signaling Gateway ..................................................................................................... 28 4.2.2 Service Processing Server ........................................................................................ 29 4.2.3 IP Gateway ................................................................................................................ 29 4.2.4 OMM Server............................................................................................................... 30 4.2.5 Integrated Interface Server ........................................................................................ 30 4.3 Software Architecture ................................................................................................ 30 4.3.1 Service Processing Subsystem ................................................................................. 31


5/59


ZTE Confidential Proprietary © 2008 ZTE Corporation. All rights reserved. III

4.3.2 OMM Subsystem ....................................................................................................... 31 4.3.3 Interface Subsystem .................................................................................................. 32 4.4 Security Solution ........................................................................................................ 33 4.4.1 OS Security Solution .................................................................................................. 33

4.4.2

System Security Architecture ..................................................................................... 34 4.4.3 Equipment Security Solution ...................................................................................... 35

4.4.4 Network Security Solution .......................................................................................... 35 4.4.5 Service Security Solution ........................................................................................... 36 4.4.6 Content Security Solution .......................................................................................... 36 4.4.7 Protocol Security Solution .......................................................................................... 37 4.4.8 Network Management Security Solution ................................................................... 37 4.4.9 Environment Security Solution .................................................................................. 37 4.4.10 Disaster Redundancy Solution .................................................................................. 39

5 Technical Specifications ......................................................................................... 40 5.1 Physical Indices ......................................................................................................... 40 5.1.1 Mechanical Dimension ............................................................................................... 40

5.1.2

Weight ........................................................................................................................ 40 5.1.3 Color .......................................................................................................................... 41

5.2 Capacity ..................................................................................................................... 41 5.3 Performance .............................................................................................................. 41 5.4 Power ......................................................................................................................... 41 5.5 Transmission ............................................................................................................. 42 5.6 Working Environment ................................................................................................ 42 5.7 Environmental Classes .............................................................................................. 43 5.8 Reliability .................................................................................................................... 43

6 Operation and Maintenance .................................................................................... 44 6.1 Fault Management System ........................................................................................ 44 6.2 Performance Management System ........................................................................... 44

6.3

Signaling Trace System ............................................................................................. 44

6.4 Service Observation System ..................................................................................... 45 6.5 Configuration Management System .......................................................................... 45 6.6 Right Management System ....................................................................................... 45 6.7 Logging Management System ................................................................................... 46

7 Acronyms and Abbreviations ................................................................................. 46

8 Reference .................................................................................................................. 50

9 Annex A ..................................................................................................................... 51 9.1 Precision of Control Plane CellID in GSM/WCDMA/CDMA networks ....................... 51 9.2 Precision of 3GPP standard location method ............................................................ 52

9.3

Precision of User Plane SUPL in GSM/WCDMA networks ....................................... 53

FIGURES

Figure 1 MAP ATI location procedure in GSM/UMTS network .................................................... 9

Figure 2 GSM/UMTS standard MT-LR location procedure ........................................................ 10

Figure 3 SUPL AGPS NI location procedure ............................................................................. 11

Figure 4 SUPL AGPS SI location procedure ............................................................................. 13

Figure 5

3G control plane deferred MT-LR location procedure ................................................. 21


6/59


IV © 2008 ZTE Corporation. All rights reserved. ZTE ConfidentialProprietary

Figure 6 3G control plane cancel deferred MT-LR location procedure ...................................... 22

Figure 7 3G control plane NI-LR location procedure ................................................................. 23

Figure 8 ZXME LBS network architecture diagram ................................................................... 25

Figure 9 ZXME LBS hardware structure diagram ...................................................................... 27

Figure 10

ZXME LBS signaling gateway concept diagram .......................................................... 28

Figure 11 ZXME LBS software architecture diagram .................................................................. 31

Figure 12 ZXME LBS software interface diagram........................................................................ 32

Figure 13 CELLID + TA location procedure of 2G control plane ................................................. 53

TABLES

Table 1 Table of services supported by Le interface with different location methods ................ 7

Table 1

Table of SS7 transmission methods of different location methods ............................... 8 Table 2 The dimensions of the units of V3 cabinet ................................................................... 40

Table 3 ZXME LBS typical capacity .......................................................................................... 41

Table 4 ZXME LBS typical performance ................................................................................... 41

Table 5 ZXME LBS INTERFACES STANDARDS AND SUPPORTED CABLE TYPES .......... 42

Table 6 ZXME LBS Temperature and Humidity Requirements ................................................ 42

Table 7 reliability indices of the ZXME LBS .............................................................................. 43


7/59


ZTE Confidential Proprietary © 2008 ZTE Corporation. All rights reserved. 1

1 Overview

ZTE provide highly integrated LBS enabler ZXME LBS. This enabler can providelocation function for many type mobile networks concurrently. The function includescontrol plane/user plane location function for CDMA/CDMA 2000, and control plane/userplane location function for GSM/WCDMA/TD-SCDMA network. ZXME LBS can providestandard and open interface for external entities and it follow and support relativestandards/specifications defined by 3GPP/3GPP2/OMA. ZXME LBS can provide areliable, convenient, effective location platform to many mobile carriers.

In the control plane location mode for GSM/WCDMA/TD-SCDMA network, ZXME LBSwill act as GMLC which has been defined in specification of 3GPP. In this mode, ZXMELBS will support CELLID positioning technology by MAP ATI method. Detailed, ZXMELBS uses CAMEL Phase 2 or 3 type MAP ATI (Any Time Interrogation) signaling to find

the current serving CELLID of target from HLR, and ZXME LBS will provide positionaccording to this ID.

Additionally, ZXME LBS can support standard position procedure defined in 3GPPTS23.271 in GSM/WCDMA/TD-SCDMA network. In this mode, ZXME LBS will act asGMLC and the actual positioning calculation will be performed at RNC or SMLC. So, inthis mode, the positioning technology which can be supported will depend on thefunction of RNC.

In user plane mode location, ZXME LBS will support different specifications in differentnetwork such as CDMA and GPRS/WCDMA/TD-SCDMA. In CDMA type network, ZXMELBS supports gpsOne which is Qualcomm‟s patent technology. And in GPRS or other3GPP type 3G networks, ZXME LBS support OMA SUPL AGPS technology. Additionally,

in CDMA network, it is needed of ZXME LBS P100 or other PDE to implementpositioning calculation according to gpsOne specification. It is worth noting that userplane location technology requires the packet switch capability of bear network and itrequires the terminal supports special protocol of that user plane specification. Normally,the high accuracy AGPS technology will be adopted in user plane location, so a GPSreference network will be needed in this case, and it will connect to ZXME LBS P100 ingpsOne mode or connect to ZXME LBS in SUPL mode.


8/59


2 © 2008 ZTE Corporation. All rights reserved. ZTE ConfidentialProprietary

2 Highlight Features

It had been full consideration of many standards and specification in designation ofZXME LBS and technology development trend and the requirement of carriers are alsoconsidered. So the ZXME LBS has many highlight features as mentioned in nextsections.

2.1 Smooth Evolution

For external LCS Client, ZXME LBS will provide standard location interface which is incompliance with the OMA MLP specification, the v3.0/v3.1/v3.2 verison of thisspecification will be supported.

For target user in evoluting network, the service will not be interrupted. It is because thatthe ZXME LBS is a highly integrated location enabler, it can support location service fortarget user in different networks concurrently, and it follows the international standard orspecification. So, for control plane location service, carriers can keep available oflocation service in evolution of core network or radio access network. For example,ZXME LBS can support location for GSM/3G target in same time, additionally, it alsosupports the choice of positioning procedure for dual-mode terminal and supports theswitch of positioning procedure when one has failed.

For user plane location service, the focus currently is the evolution of OMA SUPLstandard, and ZTE take part into the development/revision/test actively. This type actionwill ensure the full supporting capability for SUPL terminals of ZXME LBS.

Additionally, ZXME LBS product use all-IP V3 platform of ZTE to act as its signalinggateway, it can support TDM SS7 and SIGTRAN concurrently, so it will be no problemwhen carriers perform evolution in transmission network mode.

2.2 Easy Installation

The runtime enviorment of ZXME LBS is the ZTE certified standard and general proposehardware platform. For example, ZXME LBS can run at PC Server, blade PC Server(ATCA) or Sun Server and it can use SCSI diskarray, etc. And ZXME LBS will use manyopen and standard operation system and software, like Suse Linux, Solaris, Oracle

Databas, HA cluster software, etc. The compatibility of all these hardware and softwarehas been full tested in certification. Either the professional person of ZTE or theadministrator of carreris can install ZXME LBS software in these open platforms easily.

ZXME LBS has been developed in ZTE general software platform, and the installationand operation is similar with other ZTE production. So it is possible for professionalperson of ZTE or administrators which has experience for other ZTE productions toinstall and operation ZXME LBS by their experience.

The hardware used in ZXME LBS production including signaling gateway rack andgeneral server rack are full coincident with the general standard of telecommunicationcarriers and the physical interface used in ZXME LBS are also coincident with thestandard, so ZXME LBS can be installed into standard telecom room with no problem.


9/59



ZXME LBS will support various installation and operation manual, it can provide detaildescription for these action.

2.3 Evolution to IP RAN

ZXME LBS support standard control plane location procedure defined in 3GPPspecification and SUPL AGPS user plane location, so that not only normal terminal inPS domain but also SUPL enabled terminal can all be supported by ZXME LBS forlocation service.

In general, ZXME LBS can provide high accuracy location service through standard userplane location technology within the evolution for all-IP mobile network of carriers. AndZXME LBS can take advantage of this type network to provide location service.

2.4 Smooth Expansion

The designation of module units of ZXME LBS has adopted method like using buildingblocks in construction, so it is easily to expansion capacity and function of ZXME LBS.For example, service processor unit and IP gateway unit can be put into one physicalserver; also they can be deployed into different servers. Other units has similarcharacteristic. Carrier can configure the combination relationship between these units inreal solution according to actual requirement flexiblely.

The primary element of ZXME LBS can be deployed as single physical module as wellas multiple physical modules to balance the service load. This feature is mainlyconcerning about two logical modules: the service processor and IP gateway. These two

modules can be one to one relationship or one to more relationship. This means that ifone IP gateway and more than one service processor are deployed, the service load canbe balanced between the service processors. Furthermore, if more than one IP gatewaywill be deployed, the level-four switcher should be used at the front and to balance theload between them. For the primary board used in the signaling gateway like SPB andCMP board, it is also possible to expansion the performance and capability of itsmoothly through add the physical board number. And the number of E1 logical interfaceon the SPB board can be added through two type methods: one is add physical E1cable and the other is use change from 64K link to 2M high-speed link.

The interfaces between the primary modules of ZXME LBS are coupled loosely; andthey can be upgraded separately. Also, they can be managed separately throughcentralized portal.

2.5 Green Power

For ZXME LBS has been designed to use many open and general propose platform, it ispossible to take advantage of many advanced technical solution to reduce the powerconsumption. For example, the blade server can be used for ZXME LBS to reduce thepower consumption effectively, or new type low power-consumption server can be usedas well.

Additionally, ZXME LBS can reduce the total power consumption by some mergemethod within self modules or with other project. For example, ZXME LBS can deploysome function modules in one shared server and it can use network-based storage


10/59



solution to reduce the physical number this type device, or it can share the signalinggateway with Short Message Project, etc.

2.6 Rich Interfaces

ZXME LBS support the OMA MLP specification at interface between it and external LCSClient, and version 3.0, 3.1 and 3.2 of MLP can be supported. In additional, ZXME LBSsupport the interface with other LBS system, and it follow the OMA RLP specification,the v1.0 version can be supported.

ZXME LBS follow the control plane signaling specification of many mobile networksstrictly, including GSM/GPRS/WCDMA/TD-SCDMA/CDMA. For 3GPP type 2G/3Gnetwork, ZXME LBS support many version of MAP signaling which are defined in TS09.02 and TS 29.002 specification document to implement the interface with HLR, MSCand SGSN..

For user plane SUPL AGPS location service, ZXME LBS support the OMA SUPL v1.0specification, and support SUPL 1.0 terminal in current market. In near future, ZXMELBS will support SUPL 2.0 after the specification be published formally. The interfacebetween ZXME LBS and terminal is Lup defined by OMA, the protocol using in it is ULP. And in SUPL AGPS solution, ZXME LBS can use PAP protocol to send SUPL INITmessage through interface between it and WAP PPG.

Besides these standard interfaces, ZXME LBS has designed many custormizedinterfaces for the actual operation requirement of carriers:

Attributes Data Provisioning Interface: It is for management of basic and advance

attributes of CP/SP, for example, ID, PWD, white list of SP, many type access

limitation parameters, etc. It is also for management of privacy setting of target user.

For example, it can provision global white/black list, global privacy setting rule,

special privacy setting for one target user, etc. This interface will be provided

through HTTP+XML mode.

NMS interface: Implement the centerlized maintenance, monitor and management

function of ZXME LBS. It is SNMP-based interface.

CDR Interface: ZXME LBS will transfer custormized format CDR file to specified

device using FTP like method.

Optional interface between with SMSC or SMGW: ZXME LBS may need to send

notification or verification SMS to target user concerning with privacy checking.

These SMS will send using this interface. The protocol of this interface may be

SMPP v3.3 or other extended versions for SMGW.

2.7 Flexible Dual-mode Networking

Many methods have been adopted in designation of ZXME LBS to ensure its stability.The essential part like service processing module, signaling gateway module andswitcher device of ZXME LBS are all working in hot-backup master/slaver mode. All


11/59



board working in signaling gateway can be inserted or take off with power on. And theycan cut off from slave mode to master mode when master board is failure to ensure thecontinue of service. All these method help ZXME LBS to be a teleco-grade stablesystem.

The IP local network used in deploying ZXME LBS is dual-mode network. All devicesincluding 2/3 level switcher, router and firewall are redundancy and have redundancylink to be used. All devices have backup power. These devices can cut off automaticallywhen some one becomes failure, and the solution can ensure the unblockedcommunication.


12/59



3 Functionality

ZXME LBS act as the core of location service system, take charge with providinglongitude and latitude of target user according to relative protocol and specification, andit should meet the requirement from carriers, service provider and end user. For thesepropose, ZXME LBS will provide basic functions list below:

Le Interface

Signaling processing

MAP ATI in GSM

Standard 3GPP MT-LR

SUPL v1.0 NI Location

SUPL v1.0 SI Location

Fetch Coarse Position through Lr in SUPL roaming

Network based Periodical Location

Position Cache

Position Calculation and Conversation

Time Synchronization

GPS Reference Network Interface

CP/SP Authentication

User Privacy Management

Base Station Position Data Management

CDR Function

Provisioning Function

In additional, ZXME LBS can provide following extension or customerized function tomeet the requirement about operation, management, and so on.

Choice of Location Procedure

Flow Control


13/59



Location Procedure Handover

Roaming Interface

Request Queuing Function

Restriction of Roaming

Standard 3GPP Deferred MT-LR

Standard 3GPP NI-LR Report

Network Management Interface

Performance Statistic.

3.1 Basic Function

3.1.1 Le Interface

ZXME LBS has implemented Le interface which was defined in 3GPP specificationaccording to OMA MLP protocol. The interface helps the external LCS Client to obtaintarget user ‟s position information (using longitude/latitude and shape) by securitymethod. The external LCS Client can send message with many service relativeparameters through this interface, like requestor ID, target user ID, response type, QoS,delay time, etc. ZXME LBS can support version 3.0/3.1/3.2 of OMA MLP. ZXME LBSsupport synchronous or asynchronous type MLP request, and it can support normalHTTP or HTTPS concurrently.

The services supported by Le interface with different location methods in differentnetworks are listed in the following table:

Table 1 Table of services supported by Le interface with different location methods

LocationMethods

Standardimmediatelocation

Emergentimmediatelocation

Periodicaltriggeredloction

Networktriggerloctation

Emergencylocationreport

Standardlocationreport

GSM/3G MAP ATI

√ √ √ ╳ ╳ ╳

3GPP MT-LR √ √ √ √ ╳ ╳

3GPP MO-LR ╳ ╳ ╳ ╳ ╳ √

3GPP NI-LR ╳ ╳ ╳ ╳ √ ╳

GSM/WCDMASUPL AGPS

√ √ ╳ ╳ ╳ ╳


14/59



3.1.2 Signaling processing

ZXME LBS provide many signaling processing and interface functions. It can not onlyprocess SS7 signaling in 3GPP type network but also those in CDMA network. In

additional, ZXME LBS can support multiple signaling point code function, so it can bedeploy into more than one network concurrently.

ZXME LBS support two type of signaling transmission methods, TDM SS7 andSIGTRAN; it support two type physical interface, E1/T1 and 100Base T. ZXME LBS cansupport 64k low-rate link and 2M high-rate link when it use TDM SS7.

ZXME LBS support full protocol function in every protocol level, such as MTP, SCCP,SCTP, M3UA, and so on. The networking method can be very flexible through powerfulconfiguration function, and it can make the best of SS7 signaling.

For the MAP signaling which can be supported in ZXME LBS, there are CAMELPh2/Ph3 ATI,CAMEL Ph3 PSI,SRI for SM,MT Forward SM,SRI for LCS,PSL,SLR in

3GPP type network.

The signaling gateway of ZXME LBS can provide OMM function/tool with powerful clientinterface, and administrator can use the OMM system to perform task such as versionmanagement, parameter configuration, performance statistic, alarm, debug , backup andrestore, and so on.

In different location procedures in different networks, the SS7 transmission methodssupported by ZXME LBS are as follows, among which there is no need of connectionwith SS7 network in SUPL AGPS solution:

Table 1 Table of SS7 transmission methods of different location methods

Locationmethods

E1 TDM SIGTRAN

M3UA+SCTP

GSM/3G MAP ATI

√ √

3GPP MT-LR √ √

3GPP MO-LR √ √

3GPP NI-LR √ √

GSM/WCDMASUPL AGPS

－－

3.1.3 MAP ATI in GSM

ZXME LBS can provide CELLID location function by MAP ATI in GSM/UMTS network.The location procedure is show below:


15/59



LCS Client ZXME LBS HLR MSC MS

LCS Service Request

Send Routing Info For SM

Send Routing Info For SM Ack

MT Forword Short Message

PAGING

MT Forword Short Message Ack

Any Time Interrogation

Provide Subscriber Info

Provide Subscriber Info Ack

Any Time Interrogation Ack

LCS Service Response

AB

C

D

F

E

G

H

I

J

K

Figure 1 MAP ATI location procedure in GSM/UMTS network

1 LCS Client initiates a positioning request of target user to the ZXME LBS via a MLP(or L1 interface message) message. The ZXME LBS authenticates positioningauthorities of LCS Client and the positioning user and judges whether to use the ATIpositioning technology;

2 ZXME LBS sends MAP SEND ROUTING INFO FOR SM to HLR and query theaddress of the MSC of the user;

3 HLR returns the address of the MSC via MAP SEND ROUTING INFO FOR SM ACK;

4 ZXME LBS sends MAP MT FORWARD SHORT MESSAGE to MSC. This messagedelivers an invisible empty SM to GSM MSC. The empty SM is used to initiate aradio paging to the user at the switching side so that phone position informationsaved on the switching side will be timely updated;

5 MSC sends an invisible paging message to the idle target phone to update itslocation information on the core network (see GSM 04.08);

6 MSC sends an “MAP MT FORWARD SHORT MESSAGE ACK” message to theZXME LBS, indicating the invisible page has been completed;

7 ZXME LBS asks HLR about the location information of target phone via the AnyTime Interrogation signaling, mainly involving cell related information;


16/59



8 HLR sends MAP Provide Subscriber Information to MSC/VLR and query the CELLID of the target user;

9 MSC returns the current CELL ID of the target user via MAP Provide Subscriber

Information ack to HLR;

10 HLR sends information about the current location of target phone to the ZXME LBSvia the “Any Time Interrogation ack” message. The ZXME LBS calcula tes thelocation using its location calculation function to obtain location information of thecalled user. The location information is saved in the ZXME LBS database;

11 ZXME LBS returns the positioning results of target phone to LCS Client (ServiceProvider).

3.1.4 Standard 3GPP MT-LR

ZXME LBS can support immediate location procedure, including standard immediatelocation, emergent immediate location and periodical location. The MT-LR locationprocedure for GSM/UMTS network is show below:

LCS Client(SP) ZXMLS VMSC/SGSN UERAN

4. MAP Provide Subscriber Location

6. MAP Provide Subscriber Location Ack

7. LE slia

1. LE slir SYNC)

HLR/HSS

2. MAP Send Routing Info for LCS

3. MAP SRI Ack

5. Positioning

Figure 2 GSM/UMTS standard MT-LR location procedure

1 LCS Client initiates a positioning request of target user to the ZXME LBS via anMLP message;


17/59



2 ZXME LBS sends MAP SEND ROUTING INFO FOR LCS to HLR and query theaddress of the MSC/SGSN of the user;

3 HLR returns the address of the MSC/SGSN via MAP SEND ROUTING INFO FOR

LCS ACK to ZXME LBS;

4 ZXME LBS sends MAP PROVIDE SUBSCRIBER LOCATION to MSC/SGSN andquery the location estimate of the user according to address in last signalingresponse;

5 The core network and RAN will cooperate to perform positioning of target user.

6 MSC/SGSN returns the location estimate via MAP PROVIDE SUBSCRIBERLOCATION ACK to ZXME LBS.

7 ZXME LBS returns the positioning results of target phone to LCS Client.

3.1.5 SUPL v1.0 NI Location

ZXME LBS support SUPL v1.0 user plane high accuracy location function, supportRRLP v5.12.0 positioning protocol. The network initiated location procedure is shownbelow and it can support SET Based and SET Assisted two type of terminal; it cansupport either standard immediate location or emergency immediate location service.

SUPL UEWAP PPGZXME LBS(SLP)LCS Client(SP)

4. TCP Connection Setup

1. LCS Request

2. SUPL INIT

5. SUPL POS INIT

6. SUPL POS

7. SUPL END

8. LCS Response

3. SUPL INIT

Figure 3 SUPL AGPS NI location procedure


18/59



1 The SP sends user plane high accuracy position request to the position platform viaMLP message ;

2 AGPS positioning process should be adopted after position platform judges the

position precision requirement, then SUPL INIT message will be sent to thedestination user through WAP PPG. And the protocol used in interface betweenZXME LBS and WAP PPG is PAP.

3 SUPL application is triggered by SUPL INIT message which sent by the WAPPUSH Gateway through air interface ;

4 After receiving the message, the mobile phone sets up a data connection with theposition platform (the data connection may be normal TCP connection or TLSconnection);

5 Firstly, the mobile phone sends SUPL POS INIT message to the position platform;

6 The position platform calculates the coarse position and GPS assistant data byCELLID and sends the result to the mobile phone through SUPL POS message. And terminal will interact with ZXME LBS using one or more than one successiveSUPL POS message to finish the entire positioning process. The payload in SUPLPOS is RRLP message. ZXME LBS support to transfer assistance data by Assistance Data/Assistance Data Ack RRLP message and using Measure PositionRequest/Measure Position Response to fetch position fix from terminal when MSBcase.

7 Accomplishing positioning, the position platform will inform the mobile phonethrough SUPL END message about that the session is over;

The position platform returns SP the longitude and latitude coordinate through Le

interface. During positioning, via the roaming interface, the positioning platform acquiresthe subscriber's rough-precision position information from the subscriber's visitinglocation for roaming subscriber.

3.1.6 SUPL v1.0 SI Location

ZXME LBS support SUPL v1.0 user plane high accuracy location function, supportRRLP v5.12.0 positioning protocol. The terminal (SET) initiated location procedure isshown below and it can support SET Based and SET Assisted two type of terminal.


19/59



SUPL UE Bear Network/GGSN ZXME LBS(SLP)

1. TCP Connection Setup

2. SUPL START

3. SUPL RESPONSE

4. SUPL POS INIT

5. SUPL POS

6. SUPL END

Figure 4 SUPL AGPS SI location procedure

1 The subscriber starts a position application to obtain the location information of thismobile phone. The application sends the connection request to set up dataconnection with home position platform;.

2 The terminal sends position platform a SUPL START message;

3 The platform returns SUPL RESPONSE message following SUPL specification;

4 The mobile phone makes a response to SUPL POS INIT message with CELL ID bywhich the positioning platform calculates the low precision location of the mobilephone. If the subscriber is in roaming status, the low precision positioninginformation will be obtained by the roaming positioning request message which is

sent to the visiting platform of the roaming subscriber;

5 According to AGPS positioning method consulted between two parties andtransmitting protocol, AGPS positioning process is accomplished by RPLP carriedby SUPL POS;

6 The longitude and latitude information of the subscriber is encapsulated in SUPLEND messages and returned to the mobile phone by the positioning platform. (It isright for MSA, but for MSB, ZXME LBS may not known the result)


20/59



3.1.7 Fetch Coarse Position through Lr in SUPL roaming

ZXME LBS support SUPL proxy mode and using H-SLP calculation for roaming case.When the LocationID of target terminal current visiting CELL can not be translated by

ZXME LBS using location base station position data, ZXME LBS can fetch this data fromproper SLP according to configuration. The procedure for this action will follow therequirement defined in SUPL specification.

For example, in the GPRS or UMTS network, ZXME LBS will find the URL of visitingSLP for target terminal according to LAC or RNC ID in LocationID parameter of upgoingSUPL message. Also, the ID and password and other parameter for authentication invisiting SLP have been found. Then ZXME LBS will use these parameter to make a RLPrequest and send it to the URL, and ZXME LBS can obtain the coarse position from RLPresponse message.

This function could be implemented in GSM and WCDMA Networks.

3.1.8 Network based Periodical Location

ZXME LBS support network based periodical location function in control plane. It isdifferent from the periodical location function in user plane. The difference is that thefunction in user plane will need the help of terminal, that means terminal open theperiodical parameter and interact with ZXME LBS in time to obtain position and reportthe result to ZXME LBS. But in control plane, ZXME LBS will face to normal terminal, innormal, they can not support the function of opening periodical parameter, thus the moregeneral method is ZXME LBS will take charge of the opening job and use the standard

single immediate location procedure to obtain current position of target terminal in thetime. After finish of single positioning, ZXME LBS will push location report to externalLCS Client.

ZXME LBS support the periodical trigger location request in MLP specification, and canstart local timer according to characteristic of control plane, and perform actiondescripted in above.

ZXME LBS support stop trigger location request in MLP specification. It can stop theperiodical location session according to request by external LCS Client and release alllocal resource about this session.

This function could be implemented in MAP ATI, 3GPP MT-LR, CDMA CellID and

CDMA EFLT location methods.

3.1.9 Position Cache

The ZXME LBS can save the last subscriber position in memory and database withtimestamp and other attributes in security method. LCS Client can request and getsubscriber history position from ZXME LBS by standard MLP request.

The LCS Client can send MLP request with „NO_DELAY‟ attribute or „LAST /Current orLAST‟ mask which means it want to get subscriber history position immediate or after


21/59



failure location session. And it can set valid interval using „max_loc_age‟ mask. ZXMELBS can return user recent position according to these request parameters. In userplane protocol, there are also some field can take advantage of these function. ZXMELBS can also return cached position unilaterally when the requests against same target

are coming in short time interval. And this time interval can be configurable. With thisfunction, ZXME LBS can reduce the signaling volume towards the core network andincrease the successful ratio of location.

This function could be implemented in MAP ATI, 3GPP MT-LR, CDMA CellID, CDMAEFLT, CDMA gpsOne and GSM/WCDMA SUPL AGPS location methods.

3.1.10 Position Calculation and Conversation

Under GSM/UMTS A network environment, ZXME LBS can translate CELLID intocoarse position by matching base station position data in local database. This typefunction will not only be used in CELLID type control plane location procedure but also

be useful to gpsOne and SUPL AGPS. In normally, the data station data provided bycarriers only contains longitude and latitude of antenna, ZXME LBS can calculate thecenter of sector and store it in database by additional parameters such as radius,direction and field angle. It will help the improvement of accuracy of position achiving byZXME LBS.

In location procedure of SUPL AGPS, ZXME LBS can provide GPS assistance dataeither for MSA or for MSB type terminals, and can calculate the high accuracy positionaccording to measurement report for MSA type terminal.

ZXME LBS will store the position data in local database using WGS84 reference system,but some LCS Client may need result in other reference system. In that case, ZXMELBS can convert the result according to configured default attribute of the client orparameter in MLP request. The default result is for WGS84.

3.1.11 Time Synchronization

To ensure the successful of periodical location and the time accuracy requirement in AGPS type location calculation, ZXME LBS need time synchronization by more than onemethod. ZXME LBS can use the NTP sever provided by carriers, or it can use local GPSreceiver to act as the source of time signal. Otherwise, ZXME LBS can use public NTPserver through Internet to implement time synchronization. When it use local NTP Serveror GPS receiver to perform time synchronization, the accuracy of time can achieve 20ms.

All servers of ZXME LBS can use NTP or SNTP protocol to perform time synchronization.

3.1.12 GPS Reference Network Interface

ZXME LBS can use many GPS reference network solution according to the realrequirement of carriers and environment. These solutions include using local GPSreceiver, construct GPS reference network by receivers or rent commercial GPSreference network service from the third party. ZXME LBS can access GPS referencenetwork using proprietary interface. The interface is based on raw TCP connection andcan be deployed in normal IP network through firewall or VPN.


22/59



This function is necessary only in CDMA gpsOne and GSM/WCDMA SUPL AGPSprocedures.

3.1.13 CP/SP Authentication

The authentication of location request from CP/SP is the basic function of ZXME LBS.MLP messages sent by the CP are first authenticated in third-party services with CP IDand password and other control parameter. The system performs authentication controlupon requesting the location of the registered LCS Client to prevent illegal LCS Clientfrom accessing the location platform. The system also verifies the authorization list andbarred list of LCS Client to prevent unauthorized users from using the LCS Client toensure each locating request accessing the LCS Client is valid.

Other control parameter may include client IP address, client type, privacy overrideindication, maximal target number in one request, flow control parameter, QoSrestriction, expire date and so on.

Except these parameters, ZXME LBS can customize parameter for special user toperfom authentication function.

The authentication function against CP/SP will not only be performed before locationprocedure but also after some step. This function will be used in roaming restriction andother cased.


3.1.14 User Privacy Management

The success of positioning service depends on protection for target user privacy. Userposition privacy may be threatened by unauthorized positioning, unauthorized positionpublication, commercial service, irrational use, illegal use, trace, or harassment.

In the ZXME LBS system, default privacy rules for all target users, privacy rules forspecific users can be set. Privacy rules can be set against requestor id, client id orcombination of them or as default rule. Privacy rules are generally divided into five types:

Positioning is allowed unconditionally.

Positioning is allowed as long as a notification is given before.

Positioning is allowed as long as a notification is given before even without

permission.

Positioning is allowed only after a notification is given and permission is gotten.

Positioning is unconditionally refused.

The notification can be carried by short message or dedicated IP message defined insome user plane location protocol.


23/59



Privacy rules can also include time segments during which positioning are allowed, andprivacy protection password.

The ZXME LBS provides privacy setting WEB portals for operator administrators.

Otherwise, ZXME LBS provides HTTP + XML kind privacy setting interface tosynchronize data from external entities.


3.1.15 Base Station Position Data Management

The base station position data will be used in many location functions such as CellID,EFLT, gpsOne, SUPL AGPS, so that it is a very important basic data in ZXME LBS.ZXME LBS provide batch file processing script to synchronize base station position datafrom external entities. The transfer protocol of data file will be FTP. Also, ZXME LBS hasa perfect BSA data maintenance tool to provide GUI function. Administrator can use theGUI tool to perform backup / recovery / export / import function.

ZXME LBS can stores the following base station data: base station name, area shape,country code, network code, LAC code, cell No., antenna latitude / longitude, sectorcenter latitude / longitude, antenna azimuth, antenna field angle, antenna coverage,antenna height, position precision, average sector topographic height (meter), repeatorindication, indoor indication, timestamp, etc.

This function could be implemented in GSM, WCDMA and CDMA networks.

3.1.16 CDR Function

When position service is provided to subscriber, ZXME LBS is one element insideintegrated service to present longitude and latitude information. Operator needs carefulanalysis before deciding billing to subscriber or recording this charging in integratedbilling. Services which are initiated from UE or network are not completed even aftergetting longitude and latitude information, and subscriber has paid for data flow, so it isnot perfect to get money from subscriber.

For service initiated from network, Operator can get money for data flow and informationwhen subscribers access the position service. External client, such as CP/SP providessuch function, so billing can be got from this client by sharing or other method.

For services initiated from UE, Operator can not get money from subscriber because itcan not make sure whether subscriber has got the position information. Except billingfrom data flow, when subscriber visits WAP or other services provided by SP/CPOperator can get related information fee.

The ZXME LBS provides detailed CDR for all successful and failure location service(consists of positioning start time, positioning end time, originating positioning client ID,ID of the target mobile stations, position result, positioning precision, etc), for thepurpose of charging CP/SP and statistics analysis. Or it can be used to check correctlocation information.

ZXME LBS can provide internal format CDR file or input these data into database. Also,ZXME LBS can provide customerized CDR file according to carriers ‟ special


24/59



specification. The generation condition of CDR files can be in time or in size, and theparameter can be configurable.

ZXMS LBS can support FTP protocol to send or push CDR files to BOSS of carriers.

ZXME LBS can store at least 3 month CDR file in local. It support offline backup and soon.


3.1.17 Provisioning Function

ZXME LBS has many parameters which should be configured. Part of them areconcerning with signaling gateway, like linked element routing, GT configuration and soon. The others are concerning with service processing, and they can be configured inB/S mode through OMM system.

Also, ZXME LBS supports querying, addition, deletion, and modification of the userprivacy setting and CP/SP information through HTTP+XML kind real time interface.


3.2 Service Functions

3.2.1 Choice of Location Procedure

For ZXME LBS is a multiple location mode integrated system, it can support manylocation procedure of different network concurrently, so it is an important function tochoose a location procedure according to the parameter of location request.

Normally, ZXME LBS will choose different location for different network by range oftarget user ID. For example, one range of user ID for GSM network and another forCDMA can be a simple solution.

For choice in same network, such as choice between coarse CDMA control planelocation procedure and gpsOne high accuracy one, the accuracy requirement andresponse time limitation in the MLP request will be used. In additional, the terminalattribute must be considered when choose the gpsOne location procedure. That is to

say, if the attribute of terminal show that the user does not support gpsOne, ZXME LBSwill use alternative coarse one to perform positioning.

It is similar for choose MAP ATI and SUPL AGPS in GSM/UMTS network. Furthermore,for it is no possible to get CGI from MAP ATI response but only SAI in UMTS network,ZXME LBS will choose alternative MAP PSL procedure when one SAI includes morethan one cell.


25/59


26/59



ZXME LBS supports standard roaming immediate location service defined in RLPspecification. And this service can be supported in GSM/WCDMA control plane locationprocedure and OMA SUPL AGPS location procedure.


3.2.5 Request Queuing Function

When ZXME LBS receive location request for same target in same time, it can queuesthe request in waiting list, and only send one request to core network to fetch subscribercurrent position. If previous location has just finished in short time, the latter one mayalso use the cached result; it will base on the configuration parameter.

The above description is mainly for single location in control plane. But for user planeperiodical location, it becomes complex. In the case, ZXME LBS must consider morethan one factor, and choose from refusing new request to queuing new request.

With this function, ZXME LBS can decrease the signaling flow towards the core networkand increase the successful ratio of location.


3.2.6 Restriction of Roaming

An agreement must be achieved for control plane location service about user in roaming

status. And base station position data of visiting cell is needed for user plane roamingservice. For these reasons, ZXME LBS provides restriction of roaming function.

ZXME LBS can provide restriction aim at SP and target user.

For example, administrator can config which SP can locate user in roaming status, andhe can config if one target user can be located in roaming status and which can performthis action.

This function could be implemented in MAP ATI location method.

3.2.7 Standard 3GPP Deferred MT-LR

ZXME LBS can provide 3GPP standard deferred location function and correspondingcancel function in GSM/UMTS network. And this function is only used for user availableservice. For area change service, the special terminal to support this function is needed,so it is impossible to perform this type service. The deferred MT-LR location procedure isshow below:


27/59



LCS Client(SP) ZXME LBS VMSC/SGSN UERAN



6. LE tlra

1. LE tlrr MS_AVAIL)

HLR/HSS

2. MAP Send Routing Info for LCS

3. MAP SRI Ack

7. "Requested event is detected"

8. Positioning

9. MAP Subscriber Location Report

10. MAP Subscriber Location Report Ack

11. LE tlrep

Figure 5 3G control plane deferred MT-LR location procedure

1 LCS Client send user available triggered location request to ZXME LBS through

standard MLP message;

2 ZXME LBS receive the request message and query the routing information abouttarget user from HLR, the signaling is MAP SRI for LCS;

3 HLR return the SRI for LCS Ack to ZXME LBS, including the MSC/SGSN ID of usercurrent visiting area;

4 ZXME LBS send MAP PSL signaling to user current visiting MSC or SGSN;

5 If the MSC or SGSN accept this request, it will return a success response to ZXMELBS;

6 ZXME LBS then return a success response to LCS Client using MLP message, withthe unique ID which used in this location session;

7 If core network detect the available of target user, it will invoke a location procedurelike in normal immediate location service;

8 MSC or SGSN will get position information from RAN similar to in normal MT-LRprocedure;

9 MSC or SGSN will push the position information to ZXME LBS using MAP SLR;

10 ZXME LBS will return SLR Ack to MSC or SGSN after receiving the position report;


28/59



11 ZXME LBS will push the position report to external LCS Client through triggeredlocation report, with the unique ID as same as that in previous MLP answer.

The corresponding cancel deferred location procedure is shown below:

LCS Client ZXME LBS VMSC/SGSN



4. LE tlrsa

1. LE tlrsr

Figure 6 3G control plane cancel deferred MT-LR location procedure

1 LCS Client send stop triggered location request to ZXME LBS through standardMLP message, with the unique ID allocated by ZXME LBS. This ID may be receivedby LCS Client through previous MLP answer message;

2 ZXME LBS will send the MAP PSL signaling to involving MSC or SGSN for thetriggered location session with the indication to cancel the session;

3 If MSC or SGSN want to accept this cancel request, it will return a successresponse and release local resource related to the session;

4 ZXME LBS will also release local related resource and return success response to

LCS Client.

3.2.8 Standard 3GPP NI-LR Report

ZXME LBS can provide 3GPP standard NI-LR location report function in GSM/UMTSnetwork. It can push emergency location report to appointed LCS Client throughdedicate MLP message. The NI-LR location report procedure is show below:


29/59



LCS Client ZXME LBS VMSC/SGSN UERAN

1. Emergency Call Origination

5. MAP Subscriber Location Report

7. MAP Subscriber Location Report Ack

6. LE emerep

2. Location Request

3. positioning

4. Location Report

Figure 7 3G control plane NI-LR location procedure

1 UE initiates an emergency calling and MSC/SGSN initiates positioning procedure ofthe UE. The procedure is similar to that in standard immediate location service;

2 MSC/SGSN send location control signaling to RAN;

3 RAN perform normal positioning procedure and calculate the position estimate ofUE;

4 RAN send the position estimate to MSC/SGSN;

5 After getting position from RAN, The MSC/SGSN sends MAP SUBSCRIBERLOCATION REPORT to ZXME LBS to report the location estimate of the UE;

6 ZXME LBS push the positioning results of target phone to appointed LCS Client byemerep message.

7 ZXME LBS returns MAP SUBSCRIBER LOCATION REPORT ACk to MSC/SGSN.

3.2.9 Network Management Interface

ZXME LBS either support local OMM function, such as alarm, performance statistic, etc,or can report this parameter to network management server through SNMP protocol.

ZXME LBS adopt uniform MIB definition, and can provide many performance statisticparameters to performance management system.

The existing alarm parameters of ZXME LBS are: failure alarm for every software

modules (uplevel NMS can detect the failure of whole ZXME LBS by SNMP heartbeat


30/59



function), overload alarm, memory overused alarm, IP link broken, data base link broken,GPS receiver failure, SP overflow, base station position data synchronization failure, etc.

The existing performance statistic parameters of ZXME LBSare: whole service volume,

success ratio and average response time.

ZXME LBS can customerize alarm and performance statistic parameters based onrequirement of carriers.


3.2.10 Performance Statistic

ZXME LBS support statistic function in local OMM, administrator can use browser to seestatistic result in value or in diagram.

Also, ZXME LBS provides multi-format statistical information through a dedicated reportserver. The statistical information can be browsed through a web page or be saved asan Excel file in a local computer. The statistical report may be a bar chart, broken linechart, or pie chart with explainations and examples.

The existing statistical reports are:

detail record for user positioning service;

detail record for SP positioning service and an account report for SP positioning

service ;

It provides operators with detail report, positioning account report, statistical report

(daily report, monthly report) for amount of positioning service subscription,

statistical report (daily report, monthly report) for amount of positioning service

usage, statistical report for number of positioning service users, and other statistical

analysis reports.

ZXME LBS is capable of customizing all kinds of statistics according to requirement ofoperators. This function could be implemented in GSM, WCDMA and CDMA networks.


31/59



4 System Architecture

4.1 Networking Architecture

ZXME LBS is an integrated location system that can support many networks andmultiple location mode concurrently, so it can be mapped to different network elementwhich definied in different network specification. From the whole viewpoint, the networkarchitecture of ZXME LBS can be shown in below diagram:

CDMA Network

CDMA

MSC

CDMA

HLR

MS

ZXME

LBS

M100

LCS

Client

MLP

Signaling

Link

ZXME

LBS

P100

GPS

Reference

Network

RLP

IP Link

GIS

PDSN

GSM/3G Network

GGSN2/3G

MSC/SGSN

2/3G

HLR

UE

Other

LBS

WAP

PPG

BOSS NMS

SNMP

PAP

SMSC /

SMGWSMPP

gpsOne

MS

SUPL

UE

Figure 8 ZXME LBS network architecture diagram

In one actually location solution, all elements in above diagram should not be present inone time. It is true especially in case where ZXME LBS only be deployed in CDMAnetwork or in GSM/UMTS network. For example, when the gpsOne or SUPL AGPS highaccuracy solution are not needed, ZXME LBS will not connect to GPS reference networkand PDSN, GGSN and WAP PPG; when the function that fetch user position by roaminginterface is not needed, ZXME LBS will not connect to other LBS through RLP protocol;and so on. The follow sections descripte function of every interface in the system briefly.


32/59


33/59



from the third party. ZXME LBS can access GPS reference network using

proprietary interface. The interface is based on raw TCP connection and can be

deployed in normal IP network through firewall or VPN.

4.2 Hardware Architecture

ZXME LBS consists of signaling gateway, service processing server, IP gateway,operation and maintenance module (OMM Server) and integrated interface server. Eachof its function units adopts a modular structure to conveniently expand its capacity andfunction. All components in ZXME LBS are linked using Ethernet. The physical ZXMELBS will adopt dual-network structure to ensure the stability of system. The diagram ofZXME LBS hardware structure is shown below:

Service

Processing

Function

WAP

PPG

Interface

gpsOne PDE

Interface

Le Interface

Reference

Network

Interface

Roaming

Interface

Signaling

OMMgpsOne

Terminal

Interface

SUPL

Terminal

Interface

CDR

Interface

Short

Message

Interface

External

Provisioning

Interface

Network

Management

Interface

OMM

Signaling

GW

Integrated

InterfaceServer

Signaling

OMM

Server

Signaling

Gateway

OMM

Server

Service

Processing

Server

IP

Gateway

Figure 9 ZXME LBS hardware structure diagram

Follow section will descript function and corresponding hardware for each module ofZXME LBS simply.


34/59



4.2.1 Signaling Gateway

The signaling gateway module is for processing TDM SS7 signaling and SIGTRAN SS7signaling. It is the interface between ZXME LBS and mobile core network. It will

implement function defined by each SS7 protocol level, such as MTP, IP, SCTP, M3UA,SCCP, TCAP, MAP, etc.

The hardware of signaling gateway is designed based on ZTE V3 switcher platform,named ZXMSG 9000. It adopts full decentralized structure. The internal structure ofsignaling gateway which used in ZXME LBS will be shown in below:

MOMP

SPB 1

SPB n

MIPI

USI

.

.

.

MCMP 1

MCMP n

.

.

.

High

Speed

IP

Switch

TDM SS7

SIGTRAN

Signal GW

OMM

Server

Service

Processor

Figure 10 ZXME LBS signaling gateway concept diagram

The whole signaling gateway is based on BCTC backboard, and it is consist of systemcontrol management board MOMP, service control processing board MCMP, mastercontrol unit universal interface module MUIMC, IP side network interface board MIPI and

some back plug-in board PCB.

Each board used in signaling gateway will be explained here:

1 BCTC backboard

It can provide interconnect function for control plane Ethernet data flow of each board inwhole system. BCTC backboard can bear service board such as MUIMC, MOMP andMCMP, and it can provide interconnection function between GE and FE network socketfor these boards.

2 Signaling Interface Unit (SPB)


35/59



It can provide SS7 socket, support 64K and 2M link. It provide function according toMTP1, MTP2 protocol level in SS7 architecture.

3 IP side network interface board (MIPI)

Network interface board can process packet protocol data, each MIPI board provide 1FE socket, each socket can support 40M bit per second IP signaling.

4 Universal interface module for BCTC (MUIMC)

Universal interface module MUIMC has many function and can configured flexible, and itcan be used in different environment. In ZXME LBS, it provide the interconnect functionfor all boards in BCTC frame.

5 System control management board (MOMP)

System control management board MOMP is the core of signaling gateway, it

implements the operation and maintenance function for whole system. And it takescharge of transfer commands and data between front end and back end. It canimplement the management of master / slaver status of boards. It can provide 4 100MEthernet socket for interconnect with control, data channels of MUIMC.

6 Service control processing board (MCMP)

The physical of Service control processing board MCMP is as same as MOMP. MCMPis mainly used to process control protocol and service signaling flow.

4.2.2 Service Processing Server

Service processing server is the core component of ZXME LBS. It communicates with IPGateway, Signaling Gateway and other internal component wth internal format message.It can implement many functions, such as authentication, privacy checking, sessioncontrol, location procedure choice for different network and different location mode,priortity control, system level and sp level flow control, position calculation, and so on.

Service processing server module can be deployed as single physical module ormultiple physical modules. This will depend on the capacity requirement of real targetsystem.

For single physical module mode, a dual-server cluster should be used to implementService processing server. If the Service processing server is deployed combined with

database module, a SCSI diskarray should be added to the dual-server cluster. Thedual-server cluster may select PC Server or Sun Server. OS can select Linux or Solaris.DataBase will use Oracle.

4.2.3 IP Gateway

The primary function of IP gateway is conversation message format in processingprocedure. The IP gateway server is used to connect the ZXME LBS with LCS Client,PDE, gpsOne terminal or SUPL terminal through TCP/IP network.

Normally in ZXME LBS, a dual-server cluster or single server can be used to implementIP gateway. The server may select PC Server or Sun Server; OS can select Linux or


36/59



Solaris. IP Gateway may be deployed with Service Processing Server in one physicalserver. But in separating case, the server type should be same as it used in ServiceProcessing module.

4.2.4 OMM Server

OMM module is used to manage ZXME LBS with such function: Fault Management,Performance Management, Signaling Trace, Service Observation, ConfigurationManagement and Right Management, etc. OMM module also supports the SNMPinterface so it can be connect to up level NMS.

The archecture of OMM module is B/S mode. It makes the possible for administrator toperform maintenance work in remote site and through firewall smoothly. So theadministrator needs not to install special OMM client in local and it is in line with lasttrends of OMM software.

Normally in ZXME LBS, a single PC server can be used to implement OMM server, andOS can select Windows.

4.2.5 Integrated Interface Server

Integrated Interface module is used in ZXME LBS with such function: Send and receiveshort message, CDR processing and external provisioning function, etc. Normally inZXME LBS, a single PC server can be used to implement Integrated Interface server,and OS can select Windows.

4.3 Software Architecture

ZXME LBS mobile location center software strict follows the software design standards.The architecture follows the design idea of hierarchical, modularization. The coarseviewpoint of software architecture can be shown as below diagram:


37/59



OMM

Service

Processing

Function

Interface

Layer

Function

Interface

Layer

Function

Interface

Layer

Function

Interface

Layer

Function

Figure 11 ZXME LBS software architecture diagram

From the coarse viewpoint, the whole ZXME LBS software can be splitted into threemain parts: Service Processing Subsystem, OMM Subsystem and Interface Subsystem.

4.3.1 Service Processing Subsystem

Service processing subsystem is the core of ZXME LBS software. It can implementmany functions, such as authentication, privacy checking, session control, locationprocedure choice for different network and different location mode, priortity control,system level and sp level flow control, position calculation, and so on.

4.3.2 OMM Subsystem

The operation and maintenance Subsystem is used for operation and maintenance ofthe ZXME LBS system, including the following functions:

Configuration Management: The configuration management system provides

centralized configuration and management of the different kinds of parameters for

service processing server and IP gateway.

Performance Management: The performance management system provides

statistic data about some performance parameters and traffic data of the ZXME LBS

for reference by operation departments.


38/59



Service Observation: The service observation system, a part of the O&M system, is

used to check ZXME LBS service operation status for analysis and processing in

accordance.

Signaling Trace: The signaling trace system is used to trace the signaling data

between service processing module, IP gateway and other network entities, and it

can be used to analyze the service operation.

Logging Management: The service handling/operation log records all operations

made by the service handling persons/operators. The log can be filtered or

displayed according to the operator name, functional module and operation duration.

4.3.3 Interface Subsystem

The interface subsystem performs interaction with all external entities, process standardand proprietary protocol message. The detail description of interface subsystem is asbelow diagram:

OMM

Service

Processing

Function

Le Interface

Roaming

Interface

CDRInterface

SignalingGW

GGSN

Signaling

OMM

Reference

Network

Inetrface

Nertwork

Management

Interface

SUPL

Terminal

Interface

gpsOne PDEInterface

External

Provisioning

Interface

WAP PPG

Interface

Short

Message

Interface

PDSNNMS

HLR /

MSC /

SGSN

LCS Client PDE

Other LBS

GPS RN

BOSS

CRM

SMSC /

SMGW

MLP

SNMP

HTTP /

XML

SMPP

IS801

PAP

ULPgpsOne

Terminal

Interface

WAP PPG

IS801

FTP

RLP

MAP / SS7 /

SIGTRAN

Figure 12 ZXME LBS software interface diagram


39/59



The signaling processing part of interface subsystem is mapped to signaling gateway.The provisioning function, SM interface function and CDR function are mapped tointegrated interface server. Network management function assigned to OMM server.Other interface functions, including Le/L1 interface, roaming interface, PDE interface,

gpsOne terminal interface, SUPL terminal interface, GRN interface are all assigned to IPGateway.

There are some special functions need to be explained for IP gateway:

Conversion function for message based on TCP: it performs the conversion

between external TCP message and internal message and encoding/decoding

function.

Conversion function for message based on HTTP: it performs the conversion

between external HTTP message and internal message and encoding/decoding

function.

Message delivery function: IP Gateway select proper service processing module

when there are more than one module exist, and send the internal message to it.

All subsystems of ZXME LBS are running above one operation support subsystem. TheOperation Support Subsystem includes operating system, control system, loadingsystem, file management system. It provides a virtual environment for uplevelapplication as that they can ignore the different between hardware platform and actualOS. It can support following functions:

Schedule and timing function: provide a process-originated message-drived virtual

development environment.

Communication function: provide communication function for every application, it is

based on TCP/IP and internal format message.

System control function: provide the control function for startup of the system, and

runtime status of function units.

Exception processing function: capture and process soft/hardware exception.

File management function: provide FIFO-based mutually exclusive file read-write

function; provide many other file abstract operation function.

4.4 Security Solution

4.4.1 OS Security Solution

The parts of ZXME LBS which need to connect to public network are all designed to runat Linux or Unix OS. The Linux and UNIX have been proven to be more secure as othersystem. ZXME LBS also have been designed to run at user level but not root level. Forthose parts which need to run at Windows OS, ZTE certified Anti-virus production will beinstalled in it. In additional, the database used in ZXME LBS is mature commercial


40/59



production, such as Oracle. The design of ZXME LBS make it possible to fit manysecurity standard required by carriers, for example, it can be migrated to hardware andOS environment appointed by carriers and it can meet the internal security specificationdefined by carriers, etc.

ZXME LBS use normative file directory structure, it make the backup/restore actionbecome easy.

It is possible to configure alarm threshold in OMM subsystem of ZXME LBS to protectsystem from danger such as overload, lack of resource, link broken, etc. ZXME LBS canreport these alarm through SNMP interface to uplevel NMS.

4.4.2 System Security Architecture

There are three hierarchy of safety designation in whole ZXME LBS safety architecture:

safety designation for hardware

safety designation for system software

safety designation for application software

For hardware hierarchy, ZXME LBS only use the hardware which has been pass thesecurity certication of ZTE, and they should be in compliance with teleco-grade securitystandard. ZXME LBS has adopted full redundancy solution for all important hardwarecomponents to avoid single point failure. These components include power of signalinggateway, boards (each of them is hot-swappable), service processor, IP gateway,database server and so on. All important data will be saved at diskarray, and the disks inthe array have been configured to RAID 0+1 or RAID 5, and they are also hot-swappable.

ZXME LBS is indoor type production, and it should be installed in the central equipmentroom of good conditions. Air-conditioning is required. Therefore, the product is notrequired to be moisture proof, smoke proof, mould proof, burglar proof and water proof.It is not necessary to do “3Proof” processing to the boards.

For system software hierarchy, ZXME LBS use certified Cluster software to ensurebackup server can handover to provide service when master server is failure. Insignaling gateway, master board keeps heartbeat checking with slave board. When oneboard becomes failure, the other can displace it to provide service in time. The supportsoftware of ZXME LBS can provide watchdog function; it can restart the failureapplication software.

For application software hierarchy, ZXME LBS can provide alarm information for manyfailure modules. It can also provide overload alarm information and providecustomerized and parametered alarm information. It can record detail running log andCDR for both success and fail. ZXME LBS can provide backup and restore tools. Theservice processor of ZXME LBS can run in multiple modules mode. In the case, IPgateway can keep heartbeat checking with these service processor modules. So that IPgateway can deliver message to health module when some become failure.


41/59



4.4.3 Equipment Security Solution

On the one hand, ZXME LBS use server which can meet teleco security standard; onthe other hand, it will use signaling gateway which producted by ZTE self. The EMC

design of the ZXME LBS signaling gateway is on filtering, grounding, overlapping andcabinet electromagnetic shielding. The EMI power filter and lightening arrestor are usedfor the power cables of the overall system. Filters are recommended at the input/outputterminals of power modules of boards.

Boards and parts must satisfy Grade B requirements of ESD air discharge ± 8KV andtouch discharge ± 6KV. To satisfy the requirements, the following measures should betaken in addition to overlapping and shielding:

Grounding points should be plenty and well distributed. They are well distributed on

the in-board sockets.

Components (except indicators and switches) should be kept at a proper distancefrom the panel (>10mm), away from panel edge.

Holes for indicators and switches should be of proper size and there should be no

excessive gap.

There is no wire alongside the panel edge. Any wire (except the indicator wire)

should be at least 5~10mm away from the panel edge.

The clock cable runs inside, not on the top or the bottom and should be as short as

possible.

The devices to be used should be of high ESD protection level. Normally the ESD of

a device should be at least 2000V.

The grounding wire layer should be larger than the boundary of the wires and

components. At the panel side, the grounding wires should be installed with at least

5mm spacing.

Wires on the backplane should undergo crosstalk emulation. Signal lines of high

working frequency should be suppressed and shielded as necessary.

Boards and parts should bear anti-static labels.

4.4.4 Network Security Solution

The components in ZXME LBS are linked with local Ethernet, and they should beconnected to switcher or router of carriers to provide interface functions and service.

For ensure the function of these network, ZXME LBS follow special design idea fornetwork construction: keep clear hierarchy, make effective isolation, leave redundancylink. This can guarantee safety requirement of service function.


42/59



Firstly, in hardware configuration, switcher and firewall will use two set, select model withenough ports, and select commercial product which can support standard protocol.These devices can support the dual-network redundancy designation.

Normally, only 2 level switcher or 3 level switcher should be used in ZXME LBS. Thefirewall for whole ZTE VAS product can be used to provide access protection function.For some projects which have no other ZTE VAS product, firewall of carriers or ZXMELBS may used.

4.4.5 Service Security Solution

ZXME LBS adopts many methods to ensure the security of software.

Firstly, for system level security, ZXME LBS ca

Zxme Lbs Product Description(Gsm & Wcdma)_200809_en

Documents

Transcript of Zxme Lbs Product Description(Gsm & Wcdma)_200809_en