6 Security

22.1743GPPPush ServiceRelease 17Service aspectsStage 1TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The "Security Threats and Requirements" specified in 21.133 [1] shall not be compromised.

It shall be possible for the Push Service Operator to be assured of the identity of the Push Initiator.

It shall be possible for the Push Recipient to be assured of the identity of the Push Initiator.

Mechanisms shall be provided to ensure that the push data is sent to and accessed only by the intended addressed entity.

It shall be possible for the Push Service or the user to deny unauthorized push data.

An authorization may be based on the following:

identity of the Push Initiator
the destination user, device or user agent
push related attributes such as priority and content type

It shall be possible for the user to control acceptance of push data sent to the user based on the trust level of the Push Initiator.

The Push Service shall provide data integrity and data confidentiality of the push data.

Push Initiators must have authorization (e.g. service level agreement) with the Push Service Operator (e.g. PLMN Operators) in order to use the Push Service.