2009年12月9日

Protocol OV: (4F) Diameter Command Description

Protocol OV: (4F) Diameter Command Description

5-17). UDR/UDA; 5-18). PUR/PUA; 5-19). SNR/SNA; 5-20). PNR/PNA


Sh Message: UDR / PUR / SNR / PNR
(in 3GPP HSS with AS)
§
Sh message to Diameter command mapping

Sh message

Source

Destination

Command-Name

Abbreviation

Sh-Pull

AS

HSS

User-Data-Request

UDR

Sh-Pull Resp

HSS

AS

User-Data-Answer

UDA

Sh-Update

AS

HSS

Profile-Update-Request

PUR

Sh-Update Resp

HSS

AS

Profile-Update-Answer

PUA

Sh-Subs-Notif

AS

HSS

Subscribe-Notifications-Request

SNR

Sh-Subs-Notif Resp

HSS

AS

Subscribe-Notifications-Answer

SNA

Sh-Notif

HSS

AS

Push-Notification-Request

PNR

Sh-Notif Resp

AS

HSS

Push-Notification-Answer

PNA


5.17. (306) User-Data-Request / Answer (UDR and UDA):


Sh: UDR/UDA between AS and HSS (ASàHSS)

User data handling procedures: Data read (Sh-Pull) (via UDR)

§ This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:

§ To read transparent and/or non-transparent data for a specified user from the HSS.

§ User data read (Data read thru Sh-Pull operation)

§ Request direction: from AS to HSS

The AS downloads data needed for providing service from HSS, by means of UDR (Sh-Pull).

§ If UDR read Loc/User status info and If HSS is standalone, HSS will send ATI to external HLR to get Loc/User status info

§ If UDR read Loc/User status info and If HSS integrates with UMTS HLR, HSS will send PSI to VLR through UMTS HLR to get Loc/User status info

§ HSS sends data to AS


5.18. (307) Profile-Update-Request / Answer (PUR and PUA):


Sh: PUR/PUA between HSS and AS (HSS à AS)

User data handling procedures: User data update (Data Update (Sh-Update)) (via PUR)

§ This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:

§ Request direction: from AS to HSS

§ To allow the AS to update the transparent (repository) data stored at the HSS for a specified each IMS Public User Identity or Public Service Identity.

Data Update (Sh-Update) (via PUR)

§ To allow the AS to update the transparent (repository) data stored at the HSS for

- each IMS Public User Identity (for Public User Identities matching a Wildcarded Public User Identity, the transparent data shall be stored per Wildcarded Public User Identity, and not for each specific Public User Identity matching that Wildcarded Public User Identity) or

- Public Service Identity (for Public Service Identities matching a Wildcarded PSI, the transparent data shall be stored per Wildcarded PSI, and not for each specific Public Service Identity matching that Wildcarded PSI).

§ To allow the AS to update the PSI Activation State of a distinct Public Service Identity in the HSS.

§ To allow the AS to update the Dynamic Service Activation Info stored at the HSS.


5.19 (308) Subscribe-Notifications-Request / Answer (SNR and SNA):


Sh: SNR/SNA between AS and HSS (ASàHSS)

User data handling procedures: (via SNR)

§ This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:

§ Request direction: from AS to HSS

Subscription to notifications (Sh-Subs-Notif) (via SNR)

§ To subscribe to Notifications for when particular transparent and/or non-transparent data for a specified IMS Public User Identity or Public Service Identity is updated, from the HSS.

§ Optionally to request the user data from the HSS in the same operation.


5.20. (309) Push-Notification-Request / Answer (PNR and PNA):


Sh: PNR/PNA between S-CSCF and HSS (HSS à AS)

§ User data handling procedures: Notification (Notifications (Sh-Notif))

§ This procedure is used between the HSS and the AS. The procedure is invoked by the HSS and is used:

§ Request direction: from HSS to AS

§ Notifications (Sh-Notif) (via PNR)

§ To inform the AS of changes in transparent and/or non-transparent data to which the AS has previously subscribed to receive Notifications for, using Sh-Subs-Notif




沒有留言:

張貼留言