February 20, 2007 LBS Roaming Settlement Conference Call May 7th, 2007

2 LBS Roaming Initiative Update LBS roaming initiative quickly nearing completion “PDE transaction method” identified as industry solution for user plane user Still need to finalize settlement component Need to capture all work in a CDG reference document Two conference calls and Tampa meeting planned –LBS Roaming Settlement Conference Call, May 7th, 2pm Pacific, (ID=3333, PW=3333) –LBS Roaming Solution Document Review, June 7th 2pm Pacific, (ID=9999, PW=9999) –Final Face to Face Meeting, June 15th :45 p.m. (Tampa Bay Area)

3 Review of Transaction-Based Solution Home operator Visited operator Network connection AAA RAN PDSN PCF AAA RAN PDSN FA H-PDE HA V-PDE IS-801 traffic H-PDE detects the MS is roaming and sends IS-801 primitive service requests to V-PDE. RPC-like interface CRX or Internet CRX or Internet RPC-like interface that enables a transaction-based service MIP/L2TP tunnel PCF

4 Overview of Settlement Refers to financial settlement between operators Remuneration for services provided to inbound roamers Currently performed between operators for packet data roaming. Settlement charges are calculated by the kilobyte. Operators indicated this will be a requirement for LBS roaming –LBS roaming will consume V-PDE resources –In many cases, LBS roaming volumes between operators will be asymmetrical This slide deck investigates LBS roaming settlement for the “remote transaction solution” for user plane LBS roaming

5 Status of Settlement Solution General agreement on LBS usage record solution Open questions: –Will CRX be used for settlement? –Create general usage record for multiple applications? (raised in Macau) –Use existing billing records, e.g. UDRs or DIAMETER billing records (raised in Macau)

6 Will CRXs be used in settlement? Home operator Visited operator AAA RAN PDSN PCF AAA RAN PDSN FA H-PDE HA V-PDE CRX or Internet CRX or Internet PCF Recommendation: Make CRX generation/settlement optional in CDG reference document

7 Strawman Location Billing Record (LBR) Strawman specifically designed for remote transaction solution Strawman is based on proposed inter-PDE protocol Assumes: –Billing/Settlement are performed on a per transaction basis –Operators want details of each PDE transaction –Summaries can be generated using LBRs on a periodic basic, e.g. monthly –No LBR generated for keep alive messages –Detailed logs will also be available on PDEs – possible that LBRs are generated from logs

8 LBR fields FieldSize (Bytes) Description V-PDE Carrier ID5Unique ID for operator of V-PDE (MCC + IMSI_11_12 ) H-PDE Carrier ID5Unique ID for operator of H-PDE (MCC + IMSI_11_12) V-PDE IP Address4Public IPv4 address of V-PDE H-PDE IP Address4Public IPv4 address of H-PDE V-PDE ID2Unique ID for V-PDE (specified in transaction protocol) H-PDE ID2Unique ID for H-PDE (specified in transaction protocol) Date and Time4UTC (Universal time code), seconds since 1/1/70 Session ID2Associates transactions with a single IS-801 session (specific in transaction protocol) Transaction ID2Unique transaction ID for the individual transaction (specified in transaction protocol) Message Type1Request Assistance Data or Request Location Estimate (specified in transaction protocol) Response1Request Assistance Data, Request Location Estimate, or Reject (specified in transaction protocol). Likely no billing applied to rejected requests.

9 Modify LBS to be application billing record? Do we expect other applications to need similar billing records? (normally MS accesses home server) Can we anticipate the need of future applications? Would we compromise the LBR record by trying to accommodate future unknown applications?

10 ABR – Application Billing Record? FieldSize (Bytes) Description Application2Type of application being used (LBS = 1?) V-PDE Carrier ID5Unique ID for operator of V-PDE (MCC + IMSI_11_12 ) H-PDE Carrier ID5Unique ID for operator of H-PDE (MCC + IMSI_11_12) V-PDE IP Address4Public IPv4 address of V-PDE H-PDE IP Address4Public IPv4 address of H-PDE V-PDE ID2Unique ID for V-PDE (specified in transaction protocol) H-PDE ID2Unique ID for H-PDE (specified in transaction protocol) Date and Time4UTC (Universal time code), seconds since 1/1/70 Session ID2Associates transactions with a single IS-801 session (specific in transaction protocol) Transaction ID2Unique transaction ID for the individual transaction (specified in transaction protocol) Message Type1Request Assistance Data or Request Location Estimate (specified in transaction protocol) Response1Request Assistance Data, Request Location Estimate, or Reject (specified in transaction protocol). Likely no billing applied to rejected requests.

11 RADIUS/DIAMETER UDRs for LBS billing UDRs normally for general data access by users LBS records only needed for settlement Desirable to have LBS billing records in normal billing stream? UDR well suited for information required for LBS billing?

12 Used RADIUS/DIAMETER UDRs?

13 UDR continued…

14 UDR continued…