Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.271  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.2…   7…   8…   9…   9.1.1A…   9.1.2…   9.1.5…   9.1.6…   9.1.8…   9.1.9…   9.1.12…   9.1.13…   9.1.15…   9.1.19…   9.2…   9.2.2…   9.2.3…   9.3…   9.4…   9.5…   9.6…   10…   11…   A…   B…   E   F…

 

11  Operational AspectsWord‑p. 171

11.1  ChargingWord‑p. 171

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);
  • requested Quality of Service information;
  • state;
  • type of event (applicable to LDR requests only);
  • time stamp;
  • type of co-ordinate system used.
Up

11.2  Charging Information Collected by the Visited PLMNWord‑p. 172

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, MSC Server, SGSN, MME, tracking area ID, location area ID, cell ID, location co-ordinates);
  • which location services were requested;
  • requested Quality of Service information;
  • 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;
  • type of event (applicable to LDR requests only).
Up

Up   Top   ToC