Download presentation
Presentation is loading. Please wait.
Published byEdwina Chapman Modified over 9 years ago
1
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 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.
2
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 5.Z.1 Successful Position Determination Gateway MPC is not Serving MPC LCS ClientH-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)
3
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG Parameter Definitions ParameterUseRelationship LCSClientIDIdentifies the external application requesting for the position. AuthKeyAuthenticates the LCS Client MDNDirectory Number of user targetted for position request PQOSPosition Quality of Service (see next slide) ApplClassType or Category of applicationLCSClientID MSIDIdentifies the mobile subscriber in the wireless network.MDN MSCIDIdentifies the serving MSC (network address) MPCIDIdentifies the serving MPC (network address) MPCAPIdentifies the capabilities of the mobile (handset), e.g. GPS or not MOBINFOCollection of mobile info required to do positioning SCELLIDIdentifies the cell the target user is currently being served from POSINFOCarries the time position pair used to locate a user GeoPositionCalling Geodetic Location – actual long/lat +others of user
4
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 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
5
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 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)
6
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 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)
7
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG Mapping LIR – Application Class Mechanics 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
8
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG Mapping LIR – Application Class Reasoning 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
9
3/7/01Alcatel/SignalSoft Contribution: TR45.2 LFG 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?…
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.