02 Mn2976eu03mn 0001 Loc Platf Archit Feat

  • View
    215

  • Download
    0

Embed Size (px)

Text of 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    1/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    1

    Contents

    1 Location platform architecture 31.1 The LCS interfaces 41.2 Functional blocks and interfaces 62 Location platform 3.0 features 92.1 API 1 features 112.2 SS7 network interface 202.3 Core features 222.4 Operation and maintenance features 323 Network integration 503.1

    CAMEL-based ATI positioning in GSM and UMTS 50

    3.2 LCS standard positioning in GSM and UMTS R99 514 Location platform 3.0 software components 534.1 Siemens SX framework 564.2 What is CORBA? 604.3 What is VisiBroker? 645 Location platform hardware 675.1 High availability solution 70

    Location platform architecture - features

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    2/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    2

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    3/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    3

    1 Location platform architecture

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    4/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    4

    1.1 The LCS interfaces

    GSM 03.71 describes the necessary network architecture for LCS. Siemens haschosen the BSS-centric variant where the SMLC is connected via Lb interface to theBSC instead of via Ls to the MSC/VLR. The G-MLC is implemented via the LocationPlatform and Location Enabling Server.

    Serving Mobile Location Center (SLMC)

    Lbinterface.Interface between the BSC and the SMLC

    Lpinterface.Interface between two SMLC

    Lsinterface.Interface between the SMLC and the MSC/VLR

    Location Enabling Server (LES)

    Leinterface (API2).Interface between an External LCS Client (Application) andthe LES. This interface is also called API2.

    API1.Interface between Location Platform and LES

    Location Platform

    Lginterface.Interface between the Location Platform and the MSC/VLR. Thereby,

    the Location Platform can also belong to a different PLMN. Lhinterface.Interface between the Location Platform and the HLR

    API1.Interface between Location Platform and LES

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    5/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    5

    BTS BSC MSC /

    VLR

    External

    LCS Client

    CBC S-

    MLC

    S-

    MLC

    HLRG-

    MLC

    Abis A

    Lg

    Lg

    Le/

    API2

    Lp

    Lh

    LbCBC-

    BSC

    CBC-

    SMLC

    Um

    D

    MLC Mobile Location Center (Serving/Gateway)

    Lx LCS Interfaces

    Different

    PLMN

    Ls

    G-MLC

    LES/GTB

    API1Location

    Platform

    Fig. 1

    Location Platform 3.5 main functionality and interfaces

    NMS(IP-

    Manager)

    Logging

    / Billing

    LESLocation Platform 3.5

    Provides location informationfrom mobile core or handset toIP-world

    Provides presence informationfrom mobile core to IP-world

    for 2G, 2.5G and 3G networks Standard compliant interfaces

    Location Server User planesupport (LSU)

    SNMP-integration into O&Msystem

    Electronic Data Records for

    logging of location requests

    Location Platform 3.5

    Provides location informationfrom mobile core or handset toIP-world

    Provides presence informationfrom mobile core to IP-world

    for 2G, 2.5G and 3G networks

    Standard compliant interfaces

    Location Server User planesupport (LSU)

    SNMP-integration into O&Msystem

    Electronic Data Records for

    logging of location requests

    LoggingData

    M

    OBILENETWORK

    SNMP

    FTP

    Lh / Lg

    SMS

    MPM

    API 1 V1.1/2.0

    API 1 V2.0

    ATI / PSI

    SLS (internal)

    WAP/PPG-IF

    SMLC

    WAP- /

    PP-GW(MSP)

    Fig. 2

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    6/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    6

    1.2 Functional blocks and interfaces

    The Location Platform consists of 3 main software modules:

    Common Services

    They offer services for the installation and administration of the Location Platform andits location services (e.g. tracing, logging and task management). They provideOA&M clients with access to the Location Platform via CORBA interfaces. Theyprovide external operation systems with alarms and performance data via SNMP.

    Location Services

    The Location Services module implements the handling of all supported types oflocation requests (standard, emergency) and location reports (standard, emergency).

    Message Handling Services

    The Message Handling Services implement SS#7 network communication withHLR/HSS/MSC/SGSN and IP-based communication with API-1 clients, e.g. LES.

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    7/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    7

    Location Platform Software Architecture

    Common Services Location Services

    Error and

    Performance

    Management

    License

    Service

    Trace

    Service

    UserAdministra-

    tion Service

    Configura-

    tion Service

    Backup &

    Restore

    Service

    Installation

    Service

    LoadDetection

    Service

    DB

    LCS Client

    Handling

    Service

    Cell Id

    Translation

    Service

    CacheService

    Logging

    Service

    API-1

    Adapter

    MLP

    Services

    HTTP Message Handling Sservices

    core network elements (HLR, MSC, SGSN)

    NMS

    OAM

    Console

    LES MPMDirect

    Clients

    API-1 V1.1/2.0 API-1 V2.0

    Lg/Lh, ATI, SRI/PSI, SM-MT

    Admin

    Filesftp: Cell-table upload

    Auxiliary

    Common

    Services SS7 Service

    MAP

    AdapterSMLC

    WAP-GW /

    PPG

    (MSP)

    WAP

    Adapter

    SLS

    Adapter

    Fig. 3

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    8/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    8

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    9/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    9

    2 Location platform 3.0 features

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    10/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    10

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    11/76

    Location platform architecture - features Siemens

    MN2976EU03MN_00011 2002 Siemens AG

    11

    2.1 API 1 features

    LP 3.0 offers two flavors of the external interface to LCS clients, called API-1 V1.1and API-1 V2. Both interfaces use the same connection handling provided by theinternal Message Handling Service.

    The API-1 Interface the Location Platform offers sockets based communicationchannels for LCS clients. It offers both secure (HTTPS) and insecure (HTTP)connections on different configurable port numbers. On secure connections acertificate is presented to the client on connection establishment.

    LP 3.0 offers a unique URL address and a limited configurable number of parallelconnections to be shared by all API-1 clients (LES, MPM, Direct LCS clients).

    If a client attempts to establish more connections than allowed it gets an immediate

    response indicating that no more connections are available.

    After successfully establishing a connection (secure or insecure) the client can startsending HTTP(S)/1.1 POST Requests, each one containing a single API-1 LocationRequest message. LP 3.0 allows (and expects) that the client sends more than asingle HTTP(S) Request using the same connection, although a single HTTP(S)Request per connection is possible. The client must indicate in the http(s) headerfield Connection that a connection should be kept. In this case, LP 3.0 keeps theconnection open until the client explicitly indicates a connection close or until aconnection time out occurs. In case LP 3.0 is unable to receive further HTTP(S)Requests (for whatsoever reason) it may indicate closing of a connection. In both

    cases, no further HTTP(S) Requests are allowed on a closed connection. PendingHTTP(S) Re-quests are processed and answered. In case a connection was closedabnormally on the client side the HTTP MHS is able to detect this and to actaccordingly, i.e. to close the connection and discard all pending requests andresponses.

    Authorization on http level is a configurable option on API-1 V1.1 to ensure upwardcompatibility to LR 2.0.If activated API 1 clients must provide valid authorizationinformation in the HTTP(S) Request header.

    For API-1 V2.0 no authorization is done on the level of HTTP(S) header parameters.According to the LIF MLP 3.0 specifications, API-1 V2.0 requests are authorized by

    client ID and password included in the XML message body of the request.

  • 8/12/2019 02 Mn2976eu03mn 0001 Loc Platf Archit Feat

    12/76

    Siemens Location platform architecture - features

    MN2976EU03MN_0001

    2002 Siemens AG

    12

    2.1.1 API 1 V1.1

    The API 1 V1.1 interface is based on the Mobile Location Protocol (MLP).

    It is based on HTTP and XML in order to faci