10 Operational Aspects

23.1713GPPFunctional descriptionLocation Services (LCS)Release 1999Stage 2 (UMTS)TS

10.1 Charging

Charging Information collected by the PLMN serving the LCS Client.

The following charging information shall be collected by the PLMN serving the LCS Client:

– Type and Identity of the LCS Client;

– Identity of the target UE;

– Results (e.g. success/failure, method used if known, response time, accuracy) – to be repeated for each instance of positioning for a deferred location request;

– Identity of the visited PLMN;

– LCS request type (i.e. LDR or LIR);

– State;

– Event (applicable to LDR requests only);

– Time Stamp;

– Type of co-ordinate system used.

10.2 Charging Information Collected by the Visited PLMN

The following charging information shall be collected by the visited PLMN:

– Date and time;

– Type and Identity of the LCS Client (if known)

– Identity of the target UE;

– Location of the target UE (e.g., MSC, location area ID, cell ID, location co-ordinates);

– Which location services were requested;

– Results (e.g. success/failure, positioning method used, response time, accuracy) – to be repeated for each instance of positioning for a batch location request;

– Identity of the GMLC or PLMN serving the LCS Client;

– State;

– Event (applicable to LDR requests only).

Annex A (informative):
Privacy class selection rule

If more than one privacy class are subscribed for the UE, the privacy class for an MT-LR is selected according to the following flow diagram.

Figure A.1: Privacy Class selection flow diagram

Note 1: The client type indicates PLMN Operator service, and the client is within or associated with the VPLMN.

Note 2: The client type indicates value added service; the UE originated call to the requesting LCS client is established and the address associated to the LCS client used by the UE call set up matches with that contained in the location request.

Note 3: The client type indicates value added service.

Annex B (informative):
Change history

Date

New Version

Comment

March 2000

3.0.0

Output from SA#7. Minor editorial changes compared to v.2.0.0

July 2000

3.1.0

Output from SA#8. The main change is the deletion of all the PS related material (will be re-introduced in LCS R00 in 23.271)

CR implemented:

001r1: Ensure reliable privacy verification for value added LCS MT-LR

002r1: Adding "hooks" indications in UMTS LCS stage 2, Removing PS LCS signaling procedures from R99 23.171. Note: the CR was mentioning that “Text marked within { brackets } is intended for releases later than Release 99.” : this text has not been incorporated.

All the text marked within { brackets } has been deleted (not applicable to R99).

December 2000

3.2.0

Incorporation of CR 005 on adding a chapter “MT-LR without HLR Query – applicable to North America Emergency Calls only” to 23.171

March 2001

3.3.0

Incorporation of the following CRs, approved at SA#11:

CR015 "Service Area Definition in LCS stage2",
CR016 "Stop reporting procedure for UMTS" and
CR017 "Privacy check procedure for call related MT-LR"

June 2001

3.4.0

Incorporation of the following CR, approved at SA#12:

CR 018r1 "LCS location notification messages"

October 2001

3.5.0

Incorporation of the following CR, approved at SA#13:

CR 019r1 " Applicability of Privacy Override Indicator"

December 2001

3.6.0

Incorporation of the following CR, approved at SA#14:

CR020 “Wrong node name in privacy check procedures”

CR021 “Exception procedures in the VMSC”

March 2002

3.7.0

Incorporation of the following CR, approved at SA#15:

CR023r1 Correction of information flows LCS client – GMLC

CR024r1 Removal of NA-ESRK from MT-LR request for North American Emergency call

June 2002

3.8.0

Incorporation of the following CR, approved at SA#16

CR025r2 Clarification of CS-MO-LR procedures

September 2002

3.9.0

Incorporation of the following CR, approved at SA#17:

CR026r1 Privacy class selection flow diagram

June 2003

3.10.0

Incorporation of the following CR, approved at SA#20:

CR029r2 Exception procedures in 23.171

March 2004

3.11.0

Incorporation of the following CR, approved at SA#23:

CR030 Routing of Emergency Calls based on Geographical Coordinates