3/7/01alcatel/signalsoft contribution: tr45.2 lfg abstract: this contribution provides a starting...

3/7/01 Alcatel/SignalSoft Contribution: TR45.2 LFG

TITLE: Data Flow/ definitions for LIR

PROJECT: PN-4747

WORKING GROUP: TR45.2.2

ABSTRACT: This contribution provides a starting point for discussion regarding the data flow through the wireless network, regarding LIR and

other location/ privacy/ mobility information COPYRIGHT STATEMENT: The contributor grants a free, irrevocable license to the Telecommunications Industry Association (TIA) to incorporate text or

other copyrightable material contained in this contribution and any modifications thereof in the creation of a TIA standards publication; to copyright and sell in TIA's name any TIA standards publication even though it may include portions of this contribution; and at TIA's sole discretion to permit others to reproduce

in whole or in part such contributions or the resulting TIA standards publication. This contributor will also be willing to grant licenses under such copyrights to third parties on reasonable non-discriminatory terms and conditions, if appropriate.

NOTICE: This contribution has been formulated to assist the TR-45.2 Subcommittee. The document is submitted to the Subcommittee as a basis for discussion and is not binding on Alcatel USA and SignalSoft. The contents may be subject to change in form and numerical value after further study. Alcatel

USA and SignalSoft specifically reserves the right to add to, or amend, the quantitative statements made herein.

© Copyright Alcatel USA, and SignalSoft 2001; Permission is granted to TIA Committee participants to copy any portion of this document for the legitimate purposes of the TIA. Ref: 03-074.


5.Z.1 Successful Position DeterminationGateway MPC is not Serving MPC

LCS Client H-MPC• LCSClientID• AuthKey• MDN• PQOS (Requested)

HLR

S-MPC

• MSID• PQOS• MSCID (serving)• ApplClass• MPCID (serving)

• MDN• ApplClass

• MSID• MPCID (serving)• MSCID (serving)

• MSID• PQOS

S-MSC

• MPCAP• MOBINFO• SCELLID• MSCID

• POSINFO

• Geoposition• PQOS (Achieved)


Parameter Definitions

Parameter Use Relationship

LCSClientID Identifies the external application requesting for the position.

AuthKey Authenticates the LCS Client

MDN Directory Number of user targetted for position request

PQOS Position Quality of Service (see next slide)

ApplClass Type or Category of application LCSClientID

MSID Identifies the mobile subscriber in the wireless network. MDN

MSCID Identifies the serving MSC (network address)

MPCID Identifies the serving MPC (network address)

MPCAP Identifies the capabilities of the mobile (handset), e.g. GPS or not

MOBINFO Collection of mobile info required to do positioning

SCELLID Identifies the cell the target user is currently being served from

POSINFO Carries the time position pair used to locate a user

GeoPosition Calling Geodetic Location – actual long/lat +others of user


PQOS

• Position Quality of Service– Horizontal Accuracy - Max Age Allowed

• Confidence region - Resolution Required/Alt

• Speed - Location Estimate Type

• Heading · Initial, Current,

– Vertical Accuracy Last Known

– Response Time - Position Mode• No delay · Immediate or

• Low delay Deferred

• Delay tolerant


Location Information Restriction (LIR)

• LIR Modes– Unconditionally Restricted– Restricted with Exception List (Fixed)– Restricted with Exception List (Variable)– Unrestricted

• Type of Activation– Demand (Subscriber administrable)– Permanent (Operator administrable)


Proposed Application Class

• Regulatory or Legal• Internal Network Operation• Application Subscribed to by user

– This application appears in the exception list of the user.

• Application invoked by user – This application is invoked explicitly by the

subscriber, e.g. by dialing *sushi– Or application provided by serving wireless

network (who may or may not own the HMPC)


Mapping LIR – Application ClassMechanics

• If user has LIR = Unconditionally Restricted– Only Regulatory or Legal and– Internal Network Operation are allowed.

• If user has LIR = Restricted (Fixed)– Only Regulatory or Legal and– Internal Network Operation and.– Application Subscribed to by user are allowed

• If user has LIR = Restricted (Variable)– Only Regulatory or Legal and– Internal Network Operation and.– Application Subscribed to by user – Application invoked by user are allowed


Mapping LIR – Application ClassReasoning

• We want to keep exception list of subscribers (allowed LCS Client IDs) in only the HMPC and not have to be passed around the wireless network (potentially a large list of LCS Clients per subscriber)

• HMPC can do the initial screening of LCS Client IDs.

• HLR or VLR can do screening based on LIR mode and proposed application class as seen in previous slide


Other stuff to do

• Minimize the amoutn of info that travels through network– Could POSREQTYPE and PQOS be combined?

• Do we need to send LCSClientID to the user? Verizon requirement.– Used so that the user can accpet or reject request for

position – but the user may not even know which ClientIDs (numbers) he wants.

– Maybe sending a 4 letter name or acronym would be better.

• Others?…

3/7/01alcatel/signalsoft contribution: tr45.2 lfg abstract: this contribution provides a starting...

Documents