7 Subscription authorisation policies

23.1413GPPArchitecture and functional descriptionPresence serviceRelease 15TS

Subscription authorisation policies shall define the watchers who can access the presence information of the presentity. In addition to the watcher identities, the subscription authorisation policies shall contain the presence information or reference to the presence information that is allowed to be accessed by the listed watchers. The subscription authorisation lists can be logically arranged to be part of the presence server or a separate entity in the network.

In case of presence information fetch or subscription from a watcher that has not been authorised by the subscription authorisation policies, the presence server shall put the fetch or subscription on hold until the watcher has been authorised, added to the subscription authorisation lists or until a preconfigured timer has expired.

Subscription authorisation lists can be divided into three different categories: personal subscription authorisation lists, public subscription authorisation lists and blocking subscription authorisation lists.

Personal and general subscription authorisation lists shall define which watchers can access which information. Personal subscription authorisation lists shall explicitly identify watchers, while general subscription authorisation lists relate to groups of watchers whose exact identities are not necessarily known by the presentity e.g. "all watchers".

Blocking subscription authorisation lists shall define watchers that are not allowed to access any presence information related to the presentity.

A presentity shall be able to manage several personal and general subscription authorisation lists as well as blocking subscription authorisation lists.

The three subscription authorisation list categories shall be evaluated in the following order: blocking subscription authorisation lists, personal subscription authorisation lists and general subscription authorisation lists.

The following shows an example where the presentity has defined a single subscription authorisation list for each category.

In this particular example, once the hit is found the evaluation is halted and presence information according to access is delivered.

1. Is the watcher on the blocking subscription authorisation list?

2. Is the watcher on the personal subscription authorisation list?

3. Is the watcher on the general subscription authorisation list (created e.g. by service provider containing all watchers)?

4. Send a notification to the presentity of pending subscription authorisation request.

Figure 7-1: Example of subscription authorisation list evaluation order for presence service