9 Charging

22.1743GPPPush ServiceRelease 17Service aspectsStage 1TS

This paragraph specifies charging requirements for the Push service.

The Push service shall support various charging mechanisms (e.g. reverse, prepaid and reply charging etc.).

The following charging scenarios shall be supported:

  1. Charging for the push service can be subscription based.
    Different charging options shall be permissible whether the user is provisioned with the Push Service as a Push initiator or as a Push recipient.
  2. Charging for the push service can be based on the push data, the resources used and time needed to carry out the push service.
  3. Charging for the push service can be based on the size of the push data pushed to a receiver.
  4. It shall be possible to charge the Push recipient only, the Push Initiator only, or both.
  5. It shall also be possible to mix and match the various different charging scenarios outlined above.
  6. It shall be possible to charge for the initial push service activation.
  7. It shall be possible to charge a Push initiator for an attempt to send push data to a push recipient, even if the push recipient rejects the push data

It shall be possible to include the following data in the CDRs as charging information if available:

  • message types, length, storage time in the network, etc
  • delivery time, upload / download method,
  • Push service sender / -recipient
  • the amount of the push data sent
  • the amount of the push data received.
  • roaming conditions (e.g. in a visited network)
  • location conditions