3GPP TS 32.409 V9.2.0

3GPP TS 32.409 V9.2.0 (2011-03)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Telecommunication management;
Performance Management (PM);
Performance measurements;
 IP Multimedia Subsystem (IMS)
(Release 9)
	 EMBED Word.Picture.8  

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. 
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.	 
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.



Keywords
GSM, UMTS, management, performance

3GPP
Postal address

3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org

Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

Contents
 TOC \o "1-9" Foreword	 PAGEREF _Toc288664764 \h 9
Introduction	 PAGEREF _Toc288664765 \h 9
1	Scope	 PAGEREF _Toc288664766 \h 10
2	References	 PAGEREF _Toc288664767 \h 10
3	Measurement family and abbreviations	 PAGEREF _Toc288664768 \h 12
3.1	Measurement family	 PAGEREF _Toc288664769 \h 12
3.2	Abbreviations	 PAGEREF _Toc288664770 \h 12
4	Functionality related measurements	 PAGEREF _Toc288664771 \h 15
4.1	Measurements related to CSCF	 PAGEREF _Toc288664772 \h 15
4.1.1	Registration related measurements	 PAGEREF _Toc288664773 \h 15
4.1.1.1	Initial registration	 PAGEREF _Toc288664774 \h 15
4.1.1.1.1	Attempted initial registration procedures	 PAGEREF _Toc288664775 \h 15
4.1.1.1.2	Successful initial registration procedures	 PAGEREF _Toc288664776 \h 15
4.1.1.1.3	Failed initial registration procedures	 PAGEREF _Toc288664777 \h 15
4.1.1.1.4	IMS initial registration set-up time (Mean)	 PAGEREF _Toc288664778 \h 16
4.1.1.1.5	Attempted initial registration procedures per access technology	 PAGEREF _Toc288664779 \h 17
4.1.1.1.6	Successful initial registration procedures per access technology	 PAGEREF _Toc288664780 \h 17
4.1.1.2	Re-registration	 PAGEREF _Toc288664781 \h 17
4.1.1.2.1	Attempted re-registration procedures	 PAGEREF _Toc288664782 \h 17
4.1.1.2.2	Successful re-registration procedures	 PAGEREF _Toc288664783 \h 18
4.1.1.2.3	Failed re-registration procedures	 PAGEREF _Toc288664784 \h 18
4.1.1.2.4	Attempted re-registration procedures per access technology	 PAGEREF _Toc288664785 \h 19
4.1.1.2.5	Successful re-registration procedures per access technology	 PAGEREF _Toc288664786 \h 19
4.1.1.3	De-registration	 PAGEREF _Toc288664787 \h 20
4.1.1.3.1	De-registrations initiated by UE	 PAGEREF _Toc288664788 \h 20
4.1.1.3.1.4	Attempted de-registrations initiated by UE per access technology	 PAGEREF _Toc288664789 \h 21
4.1.1.3.1.5	Successful de-registrations initiated by UE per access technology	 PAGEREF _Toc288664790 \h 21
4.1.1.3.2	De-registration initiated by HSS	 PAGEREF _Toc288664791 \h 21
4.1.1.3.3	De-registration initiated by service platform	 PAGEREF _Toc288664792 \h 23
4.1.1.4	Third party registration	 PAGEREF _Toc288664793 \h 24
4.1.1.4.1	Attempted third party registration procedures	 PAGEREF _Toc288664794 \h 24
4.1.1.4.2	Successful third party registration procedures	 PAGEREF _Toc288664795 \h 24
4.1.1.4.3	Failed third party registration procedures	 PAGEREF _Toc288664796 \h 24
4.1.1.5	User registration status query	 PAGEREF _Toc288664797 \h 25
4.1.1.5.1	Attempted user registration status query procedures	 PAGEREF _Toc288664798 \h 25
4.1.1.5.2	Successful user registration status query procedures	 PAGEREF _Toc288664799 \h 25
4.1.1.5.3	Failed user registration status query procedures	 PAGEREF _Toc288664800 \h 25
4.1.1.6	S-CSCF registration/deregistration notification	 PAGEREF _Toc288664801 \h 26
4.1.1.6.1	Attempted S-CSCF registration/deregistration notification procedures	 PAGEREF _Toc288664802 \h 26
4.1.1.6.2	Successful S-CSCF registration/deregistration notification procedures	 PAGEREF _Toc288664803 \h 26
4.1.1.6.3	Failed S-CSCF registration/deregistration notification procedures	 PAGEREF _Toc288664804 \h 27
4.1.2	Session control related measurements	 PAGEREF _Toc288664805 \h 28
4.1.2.1	Attempted session establishments	 PAGEREF _Toc288664806 \h 28
4.1.2.2	Successful session establishments	 PAGEREF _Toc288664807 \h 28
4.1.2.3	Answered session establishments	 PAGEREF _Toc288664808 \h 28
4.1.2.4	Failed session establishments	 PAGEREF _Toc288664809 \h 29
4.1.2.5	Simultaneous online and answered sessions (Maximum)	 PAGEREF _Toc288664810 \h 29
4.1.3	User location query related measurements	 PAGEREF _Toc288664811 \h 30
4.1.3.1	Attempted user location query procedures	 PAGEREF _Toc288664812 \h 30
4.1.3.2	Successful user location query procedures	 PAGEREF _Toc288664813 \h 30
4.1.3.3	Failed user location query procedures	 PAGEREF _Toc288664814 \h 30
4.1.4	Inter-network domain calling related measurements	 PAGEREF _Toc288664815 \h 32
4.1.4.1	Attempted session establishments from users of other network domains	 PAGEREF _Toc288664816 \h 32
4.1.4.2	403 (Forbidden) generated for sessions from users of other network domains	 PAGEREF _Toc288664817 \h 32
4.1.4.3	Attempted session establishments to users of other network domains	 PAGEREF _Toc288664818 \h 33
4.1.4.4	403 (Forbidden) received for sessions to users of other network domains	 PAGEREF _Toc288664819 \h 33
4.1.5	Roaming users related measurements	 PAGEREF _Toc288664820 \h 34
4.1.5.1	Initial registrations of visiting users from other IMS network domains	 PAGEREF _Toc288664821 \h 34
4.1.5.2	Number of SIP 403 (Forbidden) messages for the roamers	 PAGEREF _Toc288664822 \h 34
4.1.5.3	Roaming users to other IMS network domains	 PAGEREF _Toc288664823 \h 34
4.1.6	Authentication related measurements	 PAGEREF _Toc288664824 \h 36
4.1.6.1	Attempted Authentication procedures	 PAGEREF _Toc288664825 \h 36
4.1.6.2	Successful Authentication procedures	 PAGEREF _Toc288664826 \h 36
4.1.6.3	Failed Authentication procedures	 PAGEREF _Toc288664827 \h 36
4.1.7	HSS initiated update of User Profile related measurements	 PAGEREF _Toc288664828 \h 38
4.1.7.1	Attempted HSS initiated User Profile Update procedures	 PAGEREF _Toc288664829 \h 38
4.1.7.2	Successful HSS initiated User Profile Update procedures	 PAGEREF _Toc288664830 \h 38
4.1.7.3	Failed HSS initiated user profile update procedures	 PAGEREF _Toc288664831 \h 38
4.1.8	Subscription procedure related measurements	 PAGEREF _Toc288664832 \h 40
4.1.8.1	Number of attempted Subscription procedures	 PAGEREF _Toc288664833 \h 40
4.1.8.2	Number of successful Subscription procedures	 PAGEREF _Toc288664834 \h 40
4.1.8.3	Number of failed Subscription procedures	 PAGEREF _Toc288664835 \h 40
4.1.9	Notify procedure related measurements	 PAGEREF _Toc288664836 \h 41
4.1.9.1	Number of emitted Notify procedures	 PAGEREF _Toc288664837 \h 41
4.1.9.2	Number of successful Notify procedures	 PAGEREF _Toc288664838 \h 41
4.1.9.3	Number of failed Notify procedures	 PAGEREF _Toc288664839 \h 41
4.1.10	 Immediate Messaging related measurements	 PAGEREF _Toc288664840 \h 42
4.1.10.1	Attempted Immediate Messaging procedures	 PAGEREF _Toc288664841 \h 42
4.1.10.2	Successful Immediate Messaging procedures	 PAGEREF _Toc288664842 \h 42
4.1.10.3	Failed Immediate Messaging procedures	 PAGEREF _Toc288664843 \h 42
4.2	Measurements related to HSS	 PAGEREF _Toc288664844 \h 43
4.2.1	HSS database usage related measurements	 PAGEREF _Toc288664845 \h 43
4.2.1.1	Provisioning related measurements	 PAGEREF _Toc288664846 \h 43
4.2.1.1.1	Number of provisioned IMS subscriptions currently stored in a HSS	 PAGEREF _Toc288664847 \h 43
4.2.1.1.2	Number of provisioned Private User Identity stored in a HSS	 PAGEREF _Toc288664848 \h 43
4.2.1.1.3	Number of provisioned Public User Identities with SIP URI format stored in a HSS	 PAGEREF _Toc288664849 \h 43
4.2.1.1.4	Number of provisioned Public User Identities with TEL URI format stored in a HSS	 PAGEREF _Toc288664850 \h 44
4.2.1.1.5	Number of Private Service Identities stored in a HSS	 PAGEREF _Toc288664851 \h 44
4.2.1.1.6	Number of Public Service Identities with SIP URI format stored in a HSS	 PAGEREF _Toc288664852 \h 44
4.2.1.1.7	Number of Public Service Identities with TEL URI format stored in a HSS	 PAGEREF _Toc288664853 \h 44
4.2.1.2	Registration Status related measurements	 PAGEREF _Toc288664854 \h 45
4.2.1.2.1	Number of Public User Identities in registered state	 PAGEREF _Toc288664855 \h 45
4.2.1.2.2	Number of Public User Identities in unregistered state	 PAGEREF _Toc288664856 \h 45
4.2.1.2.3	Number of Private User Identities in registered state	 PAGEREF _Toc288664857 \h 45
4.2.2	User registration status query related measurements	 PAGEREF _Toc288664858 \h 47
4.2.2.1	Attempted user registration status queries	 PAGEREF _Toc288664859 \h 47
4.2.2.2	Successful user registration status queries	 PAGEREF _Toc288664860 \h 47
4.2.2.3	Failed user registration status queries	 PAGEREF _Toc288664861 \h 48
4.2.3	S-CSCF registration/de-registration notification related measurements	 PAGEREF _Toc288664862 \h 49
4.2.3.1	Attempted S-CSCF registration/de-registration notifications	 PAGEREF _Toc288664863 \h 49
4.2.3.2	Successful S-CSCF registration/de-registration notifications	 PAGEREF _Toc288664864 \h 49
4.2.3.3	Failed S-CSCF registration/de-registration notifications	 PAGEREF _Toc288664865 \h 49
4.2.4	Network initiated de-registration by the HSS related measurements	 PAGEREF _Toc288664866 \h 51
4.2.4.1	Attempted network initiated de-registrations by HSS	 PAGEREF _Toc288664867 \h 51
4.2.4.2	Successful network initiated de-registrations by HSS	 PAGEREF _Toc288664868 \h 51
4.2.4.3	Failed network initiated de-registrations by HSS	 PAGEREF _Toc288664869 \h 51
4.2.5	User location query related measurements	 PAGEREF _Toc288664870 \h 53
4.2.5.1	Attempted user location queries	 PAGEREF _Toc288664871 \h 53
4.2.5.2	Successful user location queries	 PAGEREF _Toc288664872 \h 53
4.2.5.3	Failed user location queries	 PAGEREF _Toc288664873 \h 53
4.2.6	HSS initiated update of user profile related measurements	 PAGEREF _Toc288664874 \h 55
4.2.6.1	Attempted HSS initiated updates of user profile	 PAGEREF _Toc288664875 \h 55
4.2.6.2	Successful HSS initiated updates of user profile	 PAGEREF _Toc288664876 \h 55
4.2.6.3	Failed HSS initiated updates of user profile	 PAGEREF _Toc288664877 \h 55
4.2.7	Authentication procedure related measurements	 PAGEREF _Toc288664878 \h 57
4.2.7.1	Attempted authentication procedures	 PAGEREF _Toc288664879 \h 57
4.2.7.2	Successful authentication procedures	 PAGEREF _Toc288664880 \h 57
4.2.7.3	Failed authentication procedures	 PAGEREF _Toc288664881 \h 57
4.2.8	Data read (Sh-Pull) procedure related measurements	 PAGEREF _Toc288664882 \h 59
4.2.8.1	Attempted data read (Sh-Pull) procedures	 PAGEREF _Toc288664883 \h 59
4.2.8.2	Successful data read (Sh-Pull) procedures	 PAGEREF _Toc288664884 \h 59
4.2.8.3	Failed data read (Sh-Pull) procedures	 PAGEREF _Toc288664885 \h 59
4.2.9	Data update (Sh-Update) procedure related measurements	 PAGEREF _Toc288664886 \h 61
4.2.9.1	Attempted data update (Sh-Update) procedures	 PAGEREF _Toc288664887 \h 61
4.2.9.2	Successful data update (Sh-Update) procedures	 PAGEREF _Toc288664888 \h 61
4.2.9.3	Failed data update (Sh-Update) procedures	 PAGEREF _Toc288664889 \h 61
4.2.10	Subscription to notifications (Sh‑Subs‑Notif) procedure related measurements	 PAGEREF _Toc288664890 \h 63
4.2.10.1	Attempted subscription to notifications (Sh-Subs-Notif) procedures	 PAGEREF _Toc288664891 \h 63
4.2.10.2	Successful subscription to notifications (Sh-Subs-Notif) procedures	 PAGEREF _Toc288664892 \h 63
4.2.10.3	Failed subscription to notifications (Sh-Subs-Notif) procedures	 PAGEREF _Toc288664893 \h 63
4.2.11	Notification (Sh-Notif) procedure related measurements	 PAGEREF _Toc288664894 \h 65
4.2.11.1	Attempted notification (Sh-Notif) procedures	 PAGEREF _Toc288664895 \h 65
4.2.11.2	Successful notification (Sh-Notif) procedures	 PAGEREF _Toc288664896 \h 65
4.2.11.3	Failed notification (Sh-Notif) procedures	 PAGEREF _Toc288664897 \h 65
4.3	Measurements related to BGCF	 PAGEREF _Toc288664898 \h 67
4.3.1	Session Control related measurements	 PAGEREF _Toc288664899 \h 67
4.3.1.1	Overview	 PAGEREF _Toc288664900 \h 67
4.3.1.2	Attempted sessions at BGCF	 PAGEREF _Toc288664901 \h 67
4.3.1.3	Attempted sessions forwarded to MGCF	 PAGEREF _Toc288664902 \h 67
4.3.1.4	Attempted sessions forwarded to BGCF	 PAGEREF _Toc288664903 \h 68
4.3.1.6	Successful sessions forwarded to BGCF	 PAGEREF _Toc288664904 \h 69
4.4	Measurements related to MGCF	 PAGEREF _Toc288664905 \h 71
4.4.1	Call control related measurements	 PAGEREF _Toc288664906 \h 71
4.4.1.1	Call control related measurements, CS network originated	 PAGEREF _Toc288664907 \h 71
4.4.1.1.1	Overview	 PAGEREF _Toc288664908 \h 71
4.4.1.1.2	Attempted calls, CS network originated	 PAGEREF _Toc288664909 \h 72
4.4.1.1.3	Successful calls, CS network originated	 PAGEREF _Toc288664910 \h 72
4.4.1.1.4	Answered calls, CS network originated	 PAGEREF _Toc288664911 \h 72
4.4.1.1.5	Failed calls, CS network originated	 PAGEREF _Toc288664912 \h 72
4.4.1.1.6	Call set-up time (Mean), CS network originated	 PAGEREF _Toc288664913 \h 73
4.4.1.2	Call control related measurements, IM CN originated	 PAGEREF _Toc288664914 \h 73
4.4.1.2.1	Overview	 PAGEREF _Toc288664915 \h 73
4.4.1.2.2	Attempted calls, IM CN originated	 PAGEREF _Toc288664916 \h 74
4.4.1.2.3	Successful calls, IM CN originated	 PAGEREF _Toc288664917 \h 74
4.4.1.2.4	Answered calls, IM CN originated	 PAGEREF _Toc288664918 \h 75
4.4.1.2.5	Failed calls, IM CN originated	 PAGEREF _Toc288664919 \h 75
4.4.1.2.6	Call set-up time (Mean), IM CN originated	 PAGEREF _Toc288664920 \h 75
4.4.1.3	Call control related measurements, call release	 PAGEREF _Toc288664921 \h 76
4.4.1.3.1	Overview	 PAGEREF _Toc288664922 \h 76
4.4.1.3.2	Call release initiated by CS network	 PAGEREF _Toc288664923 \h 76
4.4.1.3.3	Call release initiated by IM CN subsystem	 PAGEREF _Toc288664924 \h 76
4.4.1.3.4	Call release initiated by MGCF	 PAGEREF _Toc288664925 \h 77
4.4.1.3.5	Call release initiated by MGW	 PAGEREF _Toc288664926 \h 78
4.4.1.4	Number of simultaneous online and answered calls (Maximum)	 PAGEREF _Toc288664927 \h 78
4.4.1.5	Number of simultaneous online and answered calls (mean)	 PAGEREF _Toc288664928 \h 78
4.5	Measurements related to IM-MGW	 PAGEREF _Toc288664929 \h 79
4.6	Measurements related to MRFC	 PAGEREF _Toc288664930 \h 79
4.6.1	Session control related measurements	 PAGEREF _Toc288664931 \h 79
4.6.1.1	Attempted session establishments	 PAGEREF _Toc288664932 \h 79
4.6.1.2	Successful session establishments	 PAGEREF _Toc288664933 \h 79
4.6.1.3	Answered session establishments	 PAGEREF _Toc288664934 \h 80
4.6.1.4	Failed session establishments	 PAGEREF _Toc288664935 \h 80
4.6.2	Multi-party sessions related measurements	 PAGEREF _Toc288664936 \h 80
4.6.2.1	Attempted session establishments for multi-party sessions	 PAGEREF _Toc288664937 \h 80
4.6.2.2	Successful session establishments for multi-party sessions	 PAGEREF _Toc288664938 \h 81
4.6.2.3	Answered session establishments for multi-party sessions	 PAGEREF _Toc288664939 \h 81
4.6.2.4	Failed session establishments for multi-party sessions	 PAGEREF _Toc288664940 \h 81
4.6.2.5	Attempted event subscription procedures for multi-party sessions	 PAGEREF _Toc288664941 \h 82
4.6.2.6	Successful event subscription procedures for multi-party sessions	 PAGEREF _Toc288664942 \h 82
4.6.2.7	Failed event subscription procedures for multi-party sessions	 PAGEREF _Toc288664943 \h 83
4.6.3	Announcement service related measurements	 PAGEREF _Toc288664944 \h 83
4.6.3.1	Attempted session establishments for announcements	 PAGEREF _Toc288664945 \h 83
4.6.3.2	Successful session establishments for announcements	 PAGEREF _Toc288664946 \h 83
4.6.3.3	Answered session establishments for announcements	 PAGEREF _Toc288664947 \h 84
4.6.3.4	Failed session establishments for announcements	 PAGEREF _Toc288664948 \h 84
4.6.4	Transcoding service related measurements	 PAGEREF _Toc288664949 \h 85
4.6.4.1	Attempted session establishments for transcoding service	 PAGEREF _Toc288664950 \h 85
4.6.4.2	Successful session establishments for transcoding service	 PAGEREF _Toc288664951 \h 85
4.6.4.3	Answered session establishments for transcoding service	 PAGEREF _Toc288664952 \h 86
4.6.4.4	Failed session establishments for transcoding service	 PAGEREF _Toc288664953 \h 86
4.7	Measurements related to MRFP	 PAGEREF _Toc288664954 \h 87
4.7.1	RTP related measurements	 PAGEREF _Toc288664955 \h 87
4.7.1.1	Number of incoming RTP packets	 PAGEREF _Toc288664956 \h 87
4.7.1.2	Number of outgoing RTP packets	 PAGEREF _Toc288664957 \h 87
4.7.1.3	Number of octets of incoming RTP packets	 PAGEREF _Toc288664958 \h 87
4.7.1.4	Number of octets of outgoing RTP packets	 PAGEREF _Toc288664959 \h 88
4.7.1.5	Number of lost incoming RTP packets	 PAGEREF _Toc288664960 \h 88
4.8	Measurements related to PCRF	 PAGEREF _Toc288664961 \h 89
4.8.1	Authorization of QoS resources related measurements	 PAGEREF _Toc288664962 \h 89
4.8.1.1	Overview	 PAGEREF _Toc288664963 \h 89
4.8.1.2	Attempted resource authorization procedures at session establishment	 PAGEREF _Toc288664964 \h 90
4.8.1.3	Attempted resource authorization procedures at session modification	 PAGEREF _Toc288664965 \h 90
4.8.1.4	Successful resource authorization procedures at session establishment	 PAGEREF _Toc288664966 \h 90
4.8.1.5	Successful resource authorization procedures at session modification	 PAGEREF _Toc288664967 \h 91
4.8.1.6	Failed resource authorization procedures	 PAGEREF _Toc288664968 \h 91
4.8.2	Resource reservation related measurements	 PAGEREF _Toc288664969 \h 92
4.8.2.1	Void	 PAGEREF _Toc288664970 \h 92
4.8.2.2	Attempted resource reservation procedures	 PAGEREF _Toc288664971 \h 92
4.8.2.3	Successful resource reservation procedures	 PAGEREF _Toc288664972 \h 92
4.8.2.4	Failed resource reservation procedures by PDF	 PAGEREF _Toc288664973 \h 92
4.8.2.5	Failed resource reservation procedures by GGSN	 PAGEREF _Toc288664974 \h 93
4.8.3	IP-CAN session modification related measurements	 PAGEREF _Toc288664975 \h 94
4.8.3.1	Attempted IP-CAN session modification	 PAGEREF _Toc288664976 \h 94
4.8.3.2	Successful IP-CAN session modification	 PAGEREF _Toc288664977 \h 94
4.8.3.3	Failed IP-CAN session modification	 PAGEREF _Toc288664978 \h 94
4.8.3	PDP context modification related measurements	 PAGEREF _Toc288664979 \h 96
4.8.3.1	Attempted authorization of PDP context modification	 PAGEREF _Toc288664980 \h 96
4.8.3.2	Successful authorization of PDP context modification	 PAGEREF _Toc288664981 \h 96
4.8.3.3	Failed authorization of PDP context modification	 PAGEREF _Toc288664982 \h 96
4.8.3.4	Indication of PDP context modification	 PAGEREF _Toc288664983 \h 97
4.9	Measurements related to SLF	 PAGEREF _Toc288664984 \h 98
4.9.1	All routing information interrogations related measurements	 PAGEREF _Toc288664985 \h 98
4.9.1.1	Attempted routing information interrogation procedures	 PAGEREF _Toc288664986 \h 98
4.9.1.2	Successful routing information interrogation procedures	 PAGEREF _Toc288664987 \h 98
4.9.2	Routing information interrogation from CSCF related measurements	 PAGEREF _Toc288664988 \h 99
4.9.2.1	Overview	 PAGEREF _Toc288664989 \h 99
4.9.2.2	Attempted routing information interrogation procedures from CSCF	 PAGEREF _Toc288664990 \h 99
4.9.2.3	Successful routing information interrogation procedures from CSCF	 PAGEREF _Toc288664991 \h 100
4.9.3	Routing information interrogation from AS related measurements	 PAGEREF _Toc288664992 \h 101
4.9.3.1	Overview	 PAGEREF _Toc288664993 \h 101
4.9.3.2	Attempted routing information interrogation procedures from AS	 PAGEREF _Toc288664994 \h 101
4.9.3.3	Successful routing information interrogation procedures from AS	 PAGEREF _Toc288664995 \h 101
4.10	Measurements related to AS	 PAGEREF _Toc288664996 \h 103
4.10.1	Session control related measurements	 PAGEREF _Toc288664997 \h 103
4.10.1.1	IM CN originated session establishments	 PAGEREF _Toc288664998 \h 103
4.10.1.1.1	Attempted IM CN originated session establishments	 PAGEREF _Toc288664999 \h 103
4.10.1.1.2	Successful IM CN originated session establishments	 PAGEREF _Toc288665000 \h 103
4.10.1.1.3	Answered IM CN originated session establishments	 PAGEREF _Toc288665001 \h 103
4.10.1.1.4	Failed IM CN originated session establishments	 PAGEREF _Toc288665002 \h 104
4.10.1.2	AS originated session establishments	 PAGEREF _Toc288665003 \h 104
4.10.1.2.1	Attempted AS originated session establishments	 PAGEREF _Toc288665004 \h 104
4.10.1.2.2	Successful AS originated session establishments	 PAGEREF _Toc288665005 \h 105
4.10.2	Messaging service related measurements	 PAGEREF _Toc288665006 \h 105
4.10.2.1	Message related measurements, Page-Mode	 PAGEREF _Toc288665007 \h 105
4.10.2.1.1	Attempted incoming messages, Page-Mode	 PAGEREF _Toc288665008 \h 105
4.10.2.1.2	Successful incoming messages, Page-Mode	 PAGEREF _Toc288665009 \h 105
4.10.2.1.3	Attempted outgoing messages, Page-Mode	 PAGEREF _Toc288665010 \h 106
4.10.2.1.4	Successful outgoing messages, Page-Mode	 PAGEREF _Toc288665011 \h 106
4.10.2.2	Message related measurements, Session-Mode	 PAGEREF _Toc288665012 \h 106
4.10.2.2.1	Overview	 PAGEREF _Toc288665013 \h 106
4.10.2.2.2	Attempted messaging session establishments, Session Mode	 PAGEREF _Toc288665014 \h 107
4.10.2.2.3	Successful messaging session establishments, Session-Mode	 PAGEREF _Toc288665015 \h 108
4.10.3	Conference service related measurements	 PAGEREF _Toc288665016 \h 108
4.10.3.1	Overview	 PAGEREF _Toc288665017 \h 108
4.10.3.2	Attempted creations of conference	 PAGEREF _Toc288665018 \h 116
4.10.3.3	Successful creations of conference	 PAGEREF _Toc288665019 \h 116
4.10.3.4	Attempted joining of conference	 PAGEREF _Toc288665020 \h 117
4.10.3.5	Successful joining of conference	 PAGEREF _Toc288665021 \h 117
4.10.3.6	Attempted invitations for another user to join conference	 PAGEREF _Toc288665022 \h 117
4.10.3.7	Successful invitations for another user to join conference	 PAGEREF _Toc288665023 \h 118
4.10.3.8	Attempted subscriptions for the conference event	 PAGEREF _Toc288665024 \h 118
4.10.3.9	Successful subscriptions for the conference event	 PAGEREF _Toc288665025 \h 118
4.10.3.10	Number of simultaneous online users (Maximum)	 PAGEREF _Toc288665026 \h 119
4.10.3.11	Number of simultaneous online conferences (Maximum)	 PAGEREF _Toc288665027 \h 119
4.10.3.12	Number of simultaneous online users (Mean)	 PAGEREF _Toc288665028 \h 119
4.10.3.13	Number of simultaneous online conferences (Mean)	 PAGEREF _Toc288665029 \h 119
4.10.4	Presence service related measurements	 PAGEREF _Toc288665030 \h 121
4.10.4.1	Number of simultaneous online watchers (Maximum)	 PAGEREF _Toc288665031 \h 121
4.10.4.2	Number of simultaneous online presentities (Maximum)	 PAGEREF _Toc288665032 \h 121
4.10.4.3	Number of simultaneous online watchers (Mean)	 PAGEREF _Toc288665033 \h 121
4.10.4.4	Number of simultaneous online presentities (Mean)	 PAGEREF _Toc288665034 \h 122
4.10.4.5	Attempted subscriptions for presence	 PAGEREF _Toc288665035 \h 122
4.10.4.6	Successful subscriptions for presence	 PAGEREF _Toc288665036 \h 122
4.10.4.7	Attempted notifications for presence	 PAGEREF _Toc288665037 \h 123
4.10.4.8	Successful notifications for presence	 PAGEREF _Toc288665038 \h 123
4.10.4.9	Attempted publications for presence	 PAGEREF _Toc288665039 \h 123
4.10.4.10	Successful publications for presence	 PAGEREF _Toc288665040 \h 123
4.10.5	PoC service related measurements	 PAGEREF _Toc288665041 \h 125
4.10.5.1	Attempted creations of PoC session	 PAGEREF _Toc288665042 \h 125
4.10.5.2	Successful creations of PoC session	 PAGEREF _Toc288665043 \h 125
4.10.5.3	Attempted joining of PoC session	 PAGEREF _Toc288665044 \h 125
4.10.5.4	Successful joining of PoC session	 PAGEREF _Toc288665045 \h 125
4.10.5.5	Attempted invitations for another user to join PoC session	 PAGEREF _Toc288665046 \h 126
4.10.5.6	Successful invitations for another user to join PoC session	 PAGEREF _Toc288665047 \h 126
4.10.5.7	Number of simultaneous online users (Maximum)	 PAGEREF _Toc288665048 \h 126
4.10.5.8	Number of simultaneous online PoC session (Maximum)	 PAGEREF _Toc288665049 \h 127
4.10.6	Measurements related to XDM Enabler	 PAGEREF _Toc288665050 \h 128
4.10.6.1	XCAP operation related measurements	 PAGEREF _Toc288665051 \h 128
4.10.6.1.1	Overview	 PAGEREF _Toc288665052 \h 128
4.10.6.1.2	Attempted HTTP PUT procedures	 PAGEREF _Toc288665053 \h 128
4.10.6.1.3	Successful HTTP PUT procedures	 PAGEREF _Toc288665054 \h 129
4.10.6.1.4	Attempted HTTP GET procedures	 PAGEREF _Toc288665055 \h 129
4.10.6.1.5	Successful HTTP GET procedures	 PAGEREF _Toc288665056 \h 129
4.10.6.1.6	Attempted HTTP DELETE procedures	 PAGEREF _Toc288665057 \h 130
4.10.6.1.7	Successful HTTP DELETE procedures	 PAGEREF _Toc288665058 \h 130
4.10.6.2	SIP related measurements	 PAGEREF _Toc288665059 \h 130
4.10.6.2.1	Overview	 PAGEREF _Toc288665060 \h 130
4.10.6.2.2	Attempted Subscription procedures	 PAGEREF _Toc288665061 \h 131
4.10.6.2.3	Successful Subscription procedures	 PAGEREF _Toc288665062 \h 131
4.10.6.2.4	Attempted Notification procedures	 PAGEREF _Toc288665063 \h 132
4.10.6.2.5	Successful Notification procedures	 PAGEREF _Toc288665064 \h 132
4.11	Measurements related to IBCF	 PAGEREF _Toc288665065 \h 132
4.11.1	Attempted session establishments from users of other network domains	 PAGEREF _Toc288665066 \h 132
4.11.2	403 (Forbidden) generated for sessions from users of other network domains	 PAGEREF _Toc288665067 \h 133
4.11.3	Attempted session establishments to users of other network domains	 PAGEREF _Toc288665068 \h 133
4.11.4	403 (Forbidden) received for sessions to users of other network domains	 PAGEREF _Toc288665069 \h 134
5	Equipment related measurements	 PAGEREF _Toc288665070 \h 135
5.1	Processor usage	 PAGEREF _Toc288665071 \h 135
5.1.1	Mean processor usage	 PAGEREF _Toc288665072 \h 135
5.1.2	Peak processor usage	 PAGEREF _Toc288665073 \h 135
Annex A (normative):	Use case of Immediate Messaging procedure related measurements at CSCF	 PAGEREF _Toc288665074 \h 136
Annex B (informative):	Use case of IP-CAN Session Establishment related measurements	 PAGEREF _Toc288665075 \h 137
Annex C (informative):	Change history	 PAGEREF _Toc288665076 \h 138

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x	the first digit:
1	presented to TSG for information;
2	presented to TSG for approval;
3	or greater indicates TSG approved document under change control.
y	the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z	the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; as identified below:
TS 32.401:	Performance Management (PM); Concept and requirements
TS 52.402:	Performance Management (PM); Performance measurements - GSM
TS 32.404:	Performance Management (PM); Performance measurements - Definitions and template
TS 32.405:	Performance Management (PM); Performance measurements UTRAN
TS 32.406:	Performance Management (PM); Performance measurements Core Network (CN) PS domain
TS 32.407:	Performance Management (PM); Performance measurements Core Network (CN) CS domain
TS 32.408:	Performance Management (PM); Performance measurements Teleservice
TS 32.409:	Performance Management (PM); Performance measurements IMS
The present document is part of a set of specifications, which describe the requirements and information model necessary for the standardised Operation, Administration and Maintenance (OA&M) of a multi-vendor 3G-system.
During the lifetime of a 3G network, its logical and physical configuration will undergo changes of varying degrees and frequencies in order to optimise the utilisation of the network resources. These changes will be executed through network configuration management activities and/or network engineering, see 3GPP TS 32.600 [3].
Many of the activities involved in the daily operation and future network planning of a 3G network require data on which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to produce this data performance measurements are executed in the NEs, which comprise the network. The data can then be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation. The purpose of the present document is to describe the mechanisms involved in the collection of the data and the definition of the data itself.
1	Scope
The present document describes the measurements of IMS.
3GPP TS 32.401 [5] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an IMS network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor specific measurement types.
Only measurement types that are specific to IMS network are defined within the present documents. I.e. vendor specific measurement types and measurements related to "external" technologies used in IMS network, such as ATM or IP, are not covered. Instead, these could be applied as described by the other, "external" standards bodies (e.g. ITU-T or IETF) or according to manufacturer's documentation.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
-	Header 1: Network Element (e.g. measurements related to CSCF);
-	Header 2: Measurement function (e.g. Registration related measurements);
-	Header 3: Measurements.
2	References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication and/or edition number or version number) or non‑specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]	3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]	3GPP TS 32.102: "Telecommunication management; Architecture".
[3]	3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[4]	3GPP TS 32.632: "Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[5]	3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
[6]	3GPP TS 23.003: "Numbering, addressing and identification".
[7]	3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[8]	3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[9]	3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message".
[10]	3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details".
[11]	3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks".
[12]	3GPP TS 32.404: "Performance Management (PM); Performance measurements - Definitions and template".
[13]	3GPP TS 29.207: "Policy control over Go interface".
[14]	3GPP TS 29.208: "End-to-end Quality of Service (QoS) signalling flows".
[15]	IETF RFC 3588: "Diameter Base Protocol".
[16]	3GPP TS 23.008: "Organization of subscriber data".
[17]	3GPP TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents".
[18]	3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
[19]	ITU-T Recommendation Q.850: "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part".
[20]	ITU-T Recommendation H.248.1: "Gateway control protocol: Version 3".
[21]	ITU-T Recommendation H.248.8: "Gateway control protocol: Error code and service change reason description".
[22]	IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification".
[23]	IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications".
[24]	3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[25]	3GPP TS 23.141: "Presence service; Architecture and functional description; Stage 2".
[26]	3GPP TR 23.979: "3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2".
[27]	OMA-TS-XDM_Core: "XML Document Management Specification".
[28]	3GPP TS 33.203: "3G security; Access security for IP-based services".
[29]	3GPP TS 32.407: "Performance Management (PM); Performance measurements Core Network (CN) Circuit Switched (CS) domain".
[30]	3GPP TS 32.732: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[31]	3GPP TS 23.203: "Policy and charging control architecture".
[32]	3GPP TS 29.212: "Policy and charging control over Gx reference point".
[33]	3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
[34]	IETF RFC 3261: "SIP: Session Initiation Protocol".

3	Measurement family and abbreviations
3.1	Measurement family
The measurement names defined in the present document are all beginning with a prefix containing the measurement family name (e.g. UR.AttInitReg, SC.AttOrigSession). This family name identifies all measurements which relate to a given functionality and it may be used for measurement administration (see 3GPP TS 32.401 [5]).
The list of families currently used in the present document is as follows:
-	CC (measurements related to Call Control).
-	CONF (measurements related to conference service).
-	DBU (	measurements related to Database Usage).
-	DTR (measurements related to Data Read).
-	DTU (measurements related to Data Update).
-	EQPT (measurements related to Equipment).
-	IDS (measurements related to Inter-network Domain Session).
-	LIQ (measurements related to Location Information Query).
-	MA (measurements related Multimedia Authentication).
-	NOTIF (measurements related to Notification).
-	PoC (measurements related to PoC service).
-	PRES (measurements related to Present service).
-	QoS (measurements related to Quality of Service).
-	RII (measurements related to Routing Information Interrogation).
-	RU (measurements related to Roaming Users).
-	SC (measurements related to Session Control).
-	SUB (Measurements related to Subscription to notifications).
-	UP (measurements related to User Profile).
-	UR (measurements related to UE registration).
-	XDM (measurements related to XDM enabler).
3.2	Abbreviations
For the purposes of the present document, the following abbreviations apply:
3G	3rd Generation
3GPP	3G Partnership Project
BGCF	Breakout Gateway Control Function
CS	Circuit switched
CN	Core Network
CSCF	Call Session Control Function
HSS	Home Subscriber Server
IM	IP Multimedia
IMS	IP Multimedia Subsystem
IBCF	Interconnection Border Control Function
I-CSCF	Interrogating CSCF
NE	Network Element
NM	Network Manager
OA&M	Operation, Administration and Maintenance
OS	Operations System (EM, NM)
PCC	Policy and Charging Control
PCEF	Policy and Charging Enforcement Function
PCRF	Policy and Charging Rule Function
PM	Performance Management
P-CSCF	Proxy CSCF
QoS	Quality of Service
S-CSCF	Serving CSCF
UMTS	Universal Mobile Telecommunications System
You can find below a list of abbreviations used within the measurement types for field E of the measurement template (see 3GPP TS 32.404 [12]).
Ans	Answer(ed)
Att	Attempted
Auth	Authorization
CCR	Credit-Control-Request
CCA	Credit-Control-Answer
Cs	Circuit switched
DER	Discrete Event Registration
DeReg	De-Registration
Dmn	Domain
Estab	Establish(ment)
Fail	Failed(/Failure)
Fwd	Forwared(ed)
Glb	Global
Info	Information
Im	IP Multimedia
Inc	Incoming
Ind	Indication
Init	Initial
Interop	Interoperator
LIA	Location-Info-Answer
LIR	Location-Info-Request
MAA	Multimedia-Authentication-Answer
MAR	Multimedia-Authentication-Request
Max	Maximum
Modf	Modify/Modification
Nbr	Number
Ntwk	Network
Orig	Originated 
Outg	Outgoing
PM	Page-Mode
PNA	Push-Notification -Answer
PNR	Push-Notification-Request
PPA	Push-Profile-Answer
PPR	Push-Profile-Request
Pri	Private
PUA	Profile-Update-Answer
Pub	Public
PUR	Profile-Update-Request
Reg	Registration
Rej	Rejected
Req	Request
Rel	Release
ReReg	Re-Registration
Res	Resource
Rsv	Reserve/Reservation
Rmg	Roaming
RTA	Registration-Termination-Answer
RTR	Registration-Termination-Request
SAA	Server-Assignment-Answer
SAR	Server-Assignment-Request
SNA	Subscribe-Notifications-Answer
SNR	Subscribe-Notifications-Request
Simul	Simultaneous
SM	Session-Mode
Srv	Service
Succ	Successful
Term	Terminated
UAA	User-Authorization-Answer
UAR	User-Authorization-Request
UDA	User-Data-Answer
UDR	User-Data-Request
4	Functionality related measurements
The measurements defined in this clause are related to the functionality aspect performance. The detailed measurements for each function are defined in the following subclauses.
4.1	Measurements related to CSCF
4.1.1	Registration related measurements
4.1.1.1	Initial registration
The measurements defined in subclauses 4.1.1.1.1, 4.1.1.1.2 and 4.1.1.1.3 are subject to the "2 out of 3 approach".
4.1.1.1.1	Attempted initial registration procedures
This measurement provides the number of attempted initial registrations at the P-CSCF or S-CSCF. 
CC.
On receipt by the P-CSCF or S-CSCF of a SIP_REGISTER message for the initial registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.AttInitReg.
PCSCFFunction. 
	SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.1.2	Successful initial registration procedures
This measurement provides the number of successful initial registrations at the P-CSCF or S-CSCF. 
CC.
On transmission by the P-CSCF or S-CSCF of a SIP_200_OK message for the initial registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.SuccInitReg.
PCSCFFunction.
	SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.1.3	Failed initial registration procedures
This measurement provides the number of failed initial registration procedures at the P-CSCF or S-CSCF. The measurement is split into subcounters per response status codes. 
CC.
On transmission by the P-CSCF or S-CSCF of a response message (e.g. SIP_4xx) indicating a failed initial registration, each failed initial registration procedure is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed initial registration procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of measured status codes plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.FailInitReg.Cause
where Cause identifies the status code.
PCSCFFunction 
	SCSCFFunction
Valid for packet switched traffic.
IMS
4.1.1.1.4	IMS initial registration set-up time (Mean)
This measurement provides the mean setup time of the successful IMS initial registrations at P-CSCF.
DER (n=1).
This measurement is obtained by accumulating the time intervals for every successful IMS initial registration between the receipt by the P-CSCF from the UE of a SIP_REGISTER message and the corresponding SIP_200_OK message for the initial registration over a granularity period using DER. The end value of this time will then be divided by the number of successful IMS initial registrations observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period. See 3GPP TS 23.228 [7].
EMBED Word.Picture.8
Figure 1: UE registration procedure
A single integer value. (in milliseconds).
UR.MeanInitRegSetupTime.
PCSCFFunction.
Valid for packet switched traffic.
IMS.
This measurement is mainly dedicated to Vendor Performance Modelling, Operator Traffic Engineering and Vendor Development Engineering communities.
4.1.1.1.5	Attempted initial registration procedures per access technology
This measurement provides the number of attempted initial registrations from the UE belonging to a given access technology. (Note: The P-Access-Network-Info header is extended to include specific information relating to particular access technologies. The UE shall populate the P-Access-Network-Info header, with the following access-type tokens: "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP2-1X", "IEEE-802.11a" or "IEEE-802.11b", etc., as appropriate to the access technology in use.). This measurement is only valid for the P-CSCF.
CC.
On receipt by the P-CSCFof a SIP_REGISTER message for the initial registration. Each Register message with different access-type token in the P-Access-Network-Info header for the initial registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
Each measurement is an integer value.
The measurement name has the form UR.AttInitReg.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.1.6	Successful initial registration procedures per access technology
This measurement provides the number of successful initial registrations from the UE belonging to a given access technology. This measurement is only valid for the P-CSCF.
CC.
On transmission by the P-CSCFof a SIP_200_OK message for the initial registration, corresponding to the SIP_REGISTER message with different access-type token in the P-Access-Network-Info header for the initial registration, each successful initial registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
A single integer value.
The measurement name has the form UR.SuccInitReg.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.2	Re-registration
The measurements defined in subclauses 4.1.1.2.1, 4.1.1.2.2 and 4.1.1.2.3 are subject to the "2 out of 3 approach".
4.1.1.2.1	Attempted re-registration procedures
This measurement provides the number of attempted re-registrations at the P-CSCF or S-CSCF.
CC.
On receipt by the P-CSCF or S-CSCF of a SIP_REGISTER message for the re-registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.AttReReg.
PCSCFFunction.
	SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.2.2	Successful re-registration procedures
This measurement provides the number of successful re-registrations at the P-CSCF or S-CSCF. 
CC.
On transmission by the P-CSCF or S-CSCF of a SIP_200_OK message for the re-registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.SuccReReg.
PCSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.2.3	Failed re-registration procedures
This measurement provides the number of failed re-registration procedures at the P-CSCF or S-CSCF. The measurement is split into subcounters per response status codes. 
CC.
On transmission by the P-CSCF or S-CSCF of a response message(e.g. SIP_4xx) indicating a failed re-registration, each failed re-registration procedure is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed re-registration procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of measured per status code plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.FailReReg.Cause
where Cause identifies the status code.
PCSCFFunction.
       SCSCFFunction
Valid for packet switched traffic.
IMS
4.1.1.2.4	Attempted re-registration procedures per access technology
This measurement provides the number of attempted re-registrations from the UE belonging to a given access technology. (Note: The P-Access-Network-Info header is extended to include specific information relating to particular access technologies. The UE shall populate the P-Access-Network-Info header, with the following access-type tokens: "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP2-1X", "IEEE-802.11a" or "IEEE-802.11b", etc., as appropriate to the access technology in use.). This measurement is only valid for the P-CSCF.
CC.
On receipt by the P-CSCF of a SIP_REGISTER message for the re-registration. Each Register message with different access-type token in the P-Access-Network-Info header for the re-registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
Each measurement is an integer value.
The measurement name has the form UR.AttReReg.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.2.5	Successful re-registration procedures per access technology
This measurement provides the number of successful re-registrations from the UE belonging to a given access technology. This measurement is only valid for the P-CSCF.
CC.
On transmission by the P-CSCF of a SIP_200_OK message for the re-registration, corresponding to the SIP_REGISTER message with different access-type token in the P-Access-Network-Info header for the re-registration, each successful re-registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
A single integer value.
The measurement name has the form UR.SuccReReg.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.3	De-registration
4.1.1.3.1	De-registrations initiated by UE
The measurements defined in subclauses 4.1.1.3.1.1, 4.1.1.3.1.2 and 4.1.1.3.1.3 are subject to the "2 out of 3 approach".
4.1.1.3.1.1	Attempted de-registration procedures initiated by UE
This measurement provides the number of attempted de-registrations initiated by UE at the P-CSCF or S-CSCF. 
CC.
On receipt by the P-CSCF or S-CSCF of a SIP_REGISTER message for the de-registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.AttDeRegUe.
PCSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.3.1.2	Successful de-registration procedures initiated by UE
This measurement provides the number of successful de-registrations initiated by UE at the P-CSCF or S-CSCF. 
CC.
On transmission by the P-CSCF or S-CSCF of a SIP_200_OK message corresponding to SIP_REGISTER message for the de-registration (see 3GPP TS 23.228 [7]).
A single integer value.
UR.SuccDeRegUe.
PCSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.3.1.3	Failed de-registration procedures initiated by UE
This measurement provides the number of failed de-registration procedures initiated by UE at the P-CSCF or S-CSCF. The measurement is split into subcounters per response status codes..
CC.
On transmission by the P-CSCF or S-CSCF of a response message (e.g. SIP_4xx) indicating a failed de-registration procedure initiated by UE, each failed de-registration procedure initiated by UE is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed de-registration procedures initiated by UE. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of measured status codes plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.FailDeRegUe.Cause
where Cause identifies the status code.
PCSCFFunction.
       SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.1.3.1.4	Attempted de-registrations initiated by UE per access technology
This measurement provides the number of attempted de-registrations from the UE belonging to a given access technology. (Note: The P-Access-Network-Info header is extended to include specific information relating to particular access technologies. The UE shall populate the P-Access-Network-Info header, with the following access-type tokens: "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP2-1X", "IEEE-802.11a" or "IEEE-802.11b", etc., as appropriate to the access technology in use.). This measurement is only valid for the P-CSCF.
CC.
On receipt by the P-CSCF of a SIP_REGISTER message for the de-registration. Each Register message with different access-type token in the P-Access-Network-Info header for the de-registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
Each measurement is an integer value.
The measurement name has the form UR.AttDeRegUe.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.3.1.5	Successful de-registrations initiated by UE per access technology
This measurement provides the number of successful de-registrations from the UE belonging to a given access technology. This measurement is only valid for the P-CSCF.
CC.
On transmission by the P-CSCF of a SIP_200_OK message for the de-registration, corresponding to the SIP_REGISTER message with different access-type token in the P-Access-Network-Info header for the de-registration, each successful de-registration is added to the relevant measurement according to access technology (see 3GPP TS 24.229 [8]).
A single integer value.
The measurement name has the form UR.SuccDeRegUe.AT
where AT identifies the access technology the UE is belonging to.
PCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.1.3.2	De-registration initiated by HSS
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.1.3.2.1	Attempted de-registration procedures initiated by HSS
This measurement provides the number of attempted de-registrations initiated by HSS at the S-CSCF. 
CC.
On receipt by the S-CSCF of a Cx-Deregister message for the de-registration initiated by HSS (see 3GPP TS 29.228 [9]).
A single integer value.
UR.AttDeRegHss.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.3.2.2	Successful de-registration procedures initiated by HSS
This measurement provides the number of successful de-registrations initiated by HSS at the S-CSCF.
CC.
On transmission by the S-CSCF of a "Cx-Deregister Resp" message indicating a successful de-registration initiated by HSS (see 3GPP TS 29.228 [9]).
A single integer value.
UR.SuccDeRegHss.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.3.2.3	Failed de-registration procedures initiated by HSS
This measurement provides the number of failed de-registration procedures initiated by HSS at the S-CSCF. The measurement is split into subcounters per diameter result codes.
CC.
On transmission by the S-CSCF of a response message(e.g. SIP_4xx) indicating a failed de-registration procedure initiated by HSS, each failed de-registration procedure initiated by HSS is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed de-registration procedures initiated by HSS. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of measured result code plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.FailDeRegHss.Cause
where Cause identifies the Diameter result code.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.3.3	De-registration initiated by service platform
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.1.3.3.1	Attempted de-registration procedures initiated by service platform
This measurement provides the number attempted of de-registrations initiated by service platform at the S-CSCF.
CC.
On transmission by the S-CSCF of a SIP_NOTIFY message indicating a de-registration initiated by service platform (see 3GPP TS 24.229 [8]).
A single integer value.
UR.AttDeRegSrvPlatform.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.3.3.2	Successful de-registration procedures initiated by service platform
This measurement provides the number of successful de-registrations initiated by service platform at the S-CSCF. 
CC.
On receipt by the S-CSCF of a SIP_200_OK message corresponding to the SIP_NOTIFY message indicating a de-registration initiated by service platform (see 3GPP TS 24.229 [8]).
A single integer value.
UR.SuccDeRegSrvPlatform.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.3.3.3	Failed de-registration procedures initiated by service platform
This measurement provides the number of failed de-registration procedures initiated by service platform at the S-CSCF. The measurement is split into subcounters per response status codes. 
CC.
On receipt by the S-CSCF of a response message(e.g. SIP_4xx) indicating a failed de-registration procedure initiated by service platform, each failed de-registration procedure initiated by service platform is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed de-registration procedures initiated by service platform. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of the measured status codes plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.FailDeRegSrvPlatform.Cause
where Cause identifies the status code.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.4	Third party registration
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.1.4.1	Attempted third party registration procedures
This measurement provides the number of attempted third-party registrations triggered by S-CSCF..
CC.
On transmission by the S-CSCF of a SIP_REGISTER message for the third party registration (see 3GPP TS 24.229 [8]).
A single integer value.
UR.Att3rdPartyReg.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.4.2	Successful third party registration procedures
This measurement provides the number of successful third-party registrations triggered by S-CSCF. 
CC.
On receipt by the S-CSCF of a SIP_200_OK message for the third party registration (see 3GPP TS 24.229 [8]).
A single integer value.
UR.Succ3rdPartyReg.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.4.3	Failed third party registration procedures
This measurement provides the number of failed third-party registrations triggered by S-CSCF.
CC.
On receipt by the S-CSCF of a response message(e.g. SIP_4xx) indicating a failed third party registration procedure, each failed third party registration procedure is added to the relevant measurement according to the status code. Possible status codes are included in 3GPP TS 29.229 [10]. The sum of all supported per status code measurements shall equal the total number of failed third party registration procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of the measured status codes plus a possible sum measurement identified by the .sum suffix.
A single integer value. The number of measurements is equal to the number of the measured status codes plus a possible sum measurement identified by the .sum suffix.
The measurement name has the form UR.Fail3rdPartyReg.Cause.
where Cause identifies the status code.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.5	User registration status query
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.1.5.1	Attempted user registration status query procedures
This measurement provides number of attempted User registration status query procedures at the I-CSCF. 
CC.
On transmission by the I-CSCF of a User-Authorization-Request Diameter command to the HSS (see 3GPP TS 29.229 [9]).
A single integer value.
-	UR.AttUAR.
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.5.2	Successful user registration status query procedures
This measurement provides number of successful user registration status query procedures at the I-CSCF.
CC.
On receipt by the I-CSCF of a User-Authorization-Answer Diameter command from HSS indicating that the User Authorization Request is successful with the specific result code, each successful user registration status query procedure is added to the relevant measurement according to the successful result code. Possible successful result codes are included in 3GPP TS 29.229 [10]. The sum of all supported per result code measurements shall equal the total number of successful User registration status query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of result codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.SuccUAA.ResultCode
where ResultCode identifies the successful Result Code.
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.5.3	Failed user registration status query procedures
This measurement provides number of user registration status query procedures rejected by HSS for the specific causes. The measurement is split into subcounters per failure cause. This measurement is only valid for the I-CSCF.
CC.
On receipt by the I-CSCF of a User-Authorization-Answer Diameter command from HSS indicating that the User Authorization Request is rejected for the specific cause, each failed user registration status query procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed User registration status query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.FailUAA.Cause
where Cause identifies the failure cause. The following subcounters with specific failure causes (see 3GPP TS 29.229 [10]) are required:
-	UR.NbrFailUAA.5002	Result-Code: DIAMETER_ERROR_IDENTITIES_DONT_MATCH;
-	UR.NbrFailUAA.5004	Result-Code: DIAMETER_ERROR_ROAMING_NOT_ALLOWED;
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.6	S-CSCF registration/deregistration notification
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.1.6.1	Attempted S-CSCF registration/deregistration notification procedures
This measurement provides number of attempted S-CSCF registration/deregistration notification procedures. 
CC.
On transmission by the S-CSCF of a Server-Assignment-Request Diameter command to the HSS (see 3GPP TS 29.228 [9]).
A single integer value.
UR.AttSAR.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.6.2	Successful S-CSCF registration/deregistration notification procedures
This measurement provides number of successful S-CSCF registration/deregistration notification procedures. 
CC.
On receipt by the S-CSCF of a Server-Assignment-Answer Diameter command from the HSS indicating a successful S-CSCF registration/deregistration notification procedure (see 3GPP TS 29.228 [9]).
A single integer value.
UR.SuccSAA.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.1.6.3	Failed S-CSCF registration/deregistration notification procedures
This measurement provides number of failed S-CSCF registration/deregistration notification procedures. The measurement is split into subcounters per failure cause. 
CC.
On receipt by the S-CSCF of a Server-Assignment-Answer Diameter command from HSS indicating the S‑CSCF registration/deregistration notification procedure is failed for the specific cause, each failed S-CSCF registration/deregistration notification procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed S-CSCF registration/deregistration notification procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.FailSAA.Cause
where Cause identifies the failure cause.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.2	Session control related measurements
The measurements defined in subclauses 4.1.2.1, 4.1.2.2 and 4.1.2.4 are subject to the "2 out of 3 approach".
4.1.2.1	Attempted session establishments
This measurement provides the number of attempted session establishments at P-CSCF or S-CSCF.
CC.
On receipt by the P-CSCF or S-CSCF of an initial SIP_INVITE message (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSession.
PCSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.2.2	Successful session establishments
This measurement provides the number of successful session establishments at the P-CSCF or S-CSCF. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful session establishments.
CC.
On transmission by the P-CSCF or S-CSCF of the first response message (e.g. SIP_180) indicating a successful session establishment corresponding to the initial SIP_INVITE message (see 3GPP TS 23.228 [7]), each successful session establishment is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful session establishments. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.SuccSession.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
-	SC.SuccSession.180	Message type: SIP_180;
-	SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this 	session.
PCSCFFunction.
      SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.2.3	Answered session establishments
This measurement provides the number of answered session establishments at the P-CSCF or S-CSCF.
CC.
On transmission by the P-CSCF or S-CSCF of a SIP_200_OK response message corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AnsSession.
PCSCFFunction.
      SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.2.4	Failed session establishments
This measurement provides the number of failed session establishments at the P-CSCF or S-CSCF. The measurement is split into subcounters per response status codes.
CC.
On transmission by the P-CSCF or S-CSCF of a response message (e.g. SIP_430) indicating a failed session establishment corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]), each failed session establishment is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailSession.Cause
where Cause identifies the status code.
PCSCFFunction.
       SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.2.5	Simultaneous online and answered sessions (Maximum)
This measurement provides the maximum number of simultaneous online sessions which have been answered at the P-CSCF or S-CSCF.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online sessions which have been answered and then taking the maximum.
A single integer value.
SC.NbrSimulAnsSessionMax.
PCSCFFunction.
      SCSCFFuntion
Valid for packet switched traffic.
IMS.
4.1.3	User location query related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.3.1	Attempted user location query procedures
This measurement provides number of attempted user location query procedures at I-CSCF. 
CC.
On transmission by the I-CSCF of a Location-Info-Request Diameter command to the HSS (see 3GPP TS 29.228 [9]).
A single integer value.
LIQ.AttLIR.
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.3.2	Successful user location query procedures
This measurement provides number of successful user location query procedures at I-CSCF. 
CC.
On receipt by the I-CSCF of a Location-Info-Answer Diameter command from the HSS indicating a successful location information query procedure (see 3GPP TS 29.228 [9]).
A single integer value.
LIQ.SuccLIA.
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.3.3	Failed user location query procedures
This measurement provides number of failed user location query procedures at I-CSCF. The measurement is split into subcounters per failure cause. 
CC.
On receipt by the I-CSCF of a Location-Info-Answer Diameter command from HSS indicating the user location query is failed for the specific cause, each failed user location query procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed user location query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form LIQ.FailLIA.Cause
where Cause identifies the failure cause.
ICSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.4	Inter-network domain calling related measurements
4.1.4.1	Attempted session establishments from users of other network domains
This measurement provides the number of attempted session establishments originated from the users (regardless of whether the user is roaming or not) who are belonging to other network domains at the I-CSCF or S-CSCF in the terminating network. The measurement is split into subcounters per network domain. 
CC.
On receipt by the I-CSCF or S-CSCF of a SIP_ INVITE message, and the calling party is belonging to other network domains (i.e. the domain name information of the calling party retrieved from the SIP_INVITE message is different from the domain of this I-CSCF or S-CSCF). Each session whose calling party recognized by the CSCF as belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of attempted session establishments from users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IC.AttSessionFromOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
ICSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.4.2	403 (Forbidden) generated for sessions from users of other network domains
This measurement provides the number of SIP_403 (Forbidden) response messages at the I-CSCF or S-CSCF in the terminating network generated for the sessions from users of other network domains. The measurement is split into subcounters per network domain. 
CC.
On transmission by the I-CSCF or S-CSCF of SIP_403 message corresponding to the SIP_ INVITE message of which the calling party is belonging to other network domains received by the I-CSCF or S-CSCF. Each SIP_403 message generated by the I-CSCF or S-CSCF for the session whose calling party is belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of 403 (Forbidden) generated for sessions from users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IC.403SessionFromOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
ICSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.4.3	Attempted session establishments to users of other network domains
This measurement provides the number of attempted session establishments towards users (regardless of whether the user is roaming or not) who are belonging to other network domains at the I-CSCF or S-CSCF in the originating network. The measurement is split into subcounters per network domain. 
CC.
On transmission by the I-CSCF or S-CSCF of a SIP_ INVITE messages, and the called party is belonging to other network domains (i.e. the domain name information of the called party retrieved from the SIP_INVITE message is different from the domain of this I-CSCF or S-CSCF). Each session whose called party recognized by the CSCF as belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network measurements shall equal the total number of attempted session establishments to users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IC.AttSessionToOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
ICSCFFunction.
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.4.4	403 (Forbidden) received for sessions to users of other network domains
This measurement provides the number of SIP_403 (Forbidden) response messages received for sessions to users of other network domains at the I-CSCF or S-CSCF in the originating network. The measurement is split into subcounters per network domain. 
CC.
On receipt by the I-CSCF or S-CSCF of SIP_403 message corresponding to the SIP_ INVITE message corresponding to the SIP_ INVITE message of which the called party is belonging to other network domains transmitted by the I-CSCF or S-CSCF. Each SIP_403 message received by the I-CSCF or S-CSCF for the session whose called party is belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of 403 (Forbidden) received for sessions to users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IC.403SessionToOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
ICSCFFunction
     SCSCFFunction
Valid for packet switched traffic.
IMS.
4.1.5	Roaming users related measurements
4.1.5.1	Initial registrations of visiting users from other IMS network domains
This measurement provides number of initial registrations of users accessing the visited IMS network but are belonging other IMS network domains at P-CSCF. The measurement is split into subcounters per IMS network domain. 
CC.
On receipt by the P-CSCF of the SIP_REGISTER message from the UE who is belonging to other network domains (i.e. the domain name information of the roamer retrieved from the SIP_REGISTER message is different from the domain of this CSCF) for the initial registration. Each roamer recognized by the P-CSCF as belonging to a given IMS network domain is added to the relevant per IMS network domain measurement. The sum of all supported per IMS network domain measurements shall equal the total number of visiting users. In case only a subset of per IMS network domain measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of IMS network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form RU.AttInitRegOfVisitUsers.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
PCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.5.2	Number of SIP 403 (Forbidden) messages for the roamers
This measurement provides the number of 403-Forbidden response messages generated to UEs who are belonging to other IMS network domains with whom there are roaming agreements for the registration procedures at P-CSCF. The measurement is split into subcounters per network domain. 
CC.
On transmission by the P-CSCF of a SIP_403 (Forbidden) response message to the UE who is belonging to other IMS networks for the initial registration procedure.  Each SIP_403 message transmitted by the P-CSCF for the roamer who is belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of 403 (Forbidden) generated for the roamers who are belonging to other IMS network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of IMS network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form RU.Nbr403InitRegOfVisitUsers.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
PCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.5.3	Roaming users to other IMS network domains
This measurement provides the number of the roamers visiting other IMS network domains at S-CSCF. 
CC.
On receipt by the S-CSCF of a SIP_REGISTER message from the P-CSCF which is belonging to other IMS network domains.
A single integer value.
RU.RmgUsersOut.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.6	Authentication related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.6.1	Attempted Authentication procedures
This measurement provides number of attempted Authentication procedures at S-CSCF. 
CC.
On transmission by the S-CSCF of a Multimedia-Authentication-Request Diameter command to the HSS (see 3GPP TS 29.228 [9]).
A single integer value.
MA.AttMAR.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.6.2	Successful Authentication procedures
This measurement provides number of successful Authentication procedures at S-CSCF. 
CC.
On receipt by the S-CSCF of a Multimedia-Authentication-Answer Diameter command from the HSS indicating a successful authentication procedure (see 3GPP TS 29.228 [9]).
A single integer value.
MA.SuccMAA.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.6.3	Failed Authentication procedures
This measurement provides number of failed Authentication procedures at S-CSCF. The measurement is split into subcounters per failure cause. 
CC.
On receipt by the S-CSCF of a Multimedia-Authentication-Answer Diameter command from HSS indicating the authentication procedure is failed for the specific cause, each failed authentication procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10].
And each expected Multimedia-Authentication-Answer Diameter command not received by the S-CSCF is added into failure cause 'No Reply' (not specified in 3GPP TS 29.229 [10]).
The sum of all supported per cause measurements shall equal the total number of failed authentication procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form MA.FailMAA.Cause
where Cause identifies the failure cause.
The cause 'No Reply' is identified by the .NoReply suffix.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.7	HSS initiated update of User Profile related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.7.1	Attempted HSS initiated User Profile Update procedures
This measurement provides number of attempted HSS initiated user profile update procedures at S-CSCF. 
CC.
On receipt by the S-CSCF of a Push-Profile-Request Diameter command from the HSS (see 3GPP TS 29.228 [9]).
A single integer value.
UP.AttPPR.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.7.2	Successful HSS initiated User Profile Update procedures
This measurement provides number of successful HSS initiated user profile update procedures at S-CSCF. 
CC.
On transmission by the S-CSCF to the HSS of a Push-Profile-Answer Diameter command indicating a successful user profile update procedure (see 3GPP TS 29.228 [9]).
A single integer value.
UP.SuccPPA.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.7.3	Failed HSS initiated user profile update procedures
This measurement provides number of failed HSS initiated user profile update procedures at S-CSCF. The measurement is split into subcounters per failure cause. 
CC.
On transmission by the S-CSCF to the HSS of a Push-Profile-Answer Diameter command indicating the user profile update procedure is failed for the specific cause, each failed user profile update procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed user profile update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form UP.FailPPA.Cause
where Cause identifies the failure cause.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.8	Subscription procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.8.1	Number of attempted Subscription procedures 
This measurement provides the number of initial subscriptions attempted at the S-CSCF. 
CC.
On receipt by the S-CSCF of an initial SIP_SUBSCRIBE message (see TS 24.229 [8]).
A single integer value.
SUB.AttSubscribe.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.8.2	Number of successful Subscription procedures
This measurement provides the number of successful subscription establishments received at the S-CSCF.
CC.
On transmission by the S-CSCF of a response message with a response code (e.g. SIP_200_OK) indicating a successful subscription setup corresponding to the initial SIP_SUBSCRIBE message (see TS 24.229 [8]).
A single integer value.
SUB.SuccSubscribe.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.8.3	Number of failed Subscription procedures
This measurement provides the number of failed subscription establishments at the S-CSCF. The measurement is split into subcounters per response codes.
CC.
On transmission by the S-CSCF of a response message with a response code (e.g. SIP_430) indicating a failed subscription establishment corresponding to the initial SIP_SUBSCRIBE message (see TS 24.229 [8]), each failed subscription establishment trial is added to the relevant measurement according to the message type. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
The measurement name has the form SUB.FailedSubscribe.Cause
where Cause identifies the response code. 
SCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.9	Notify procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
4.1.9.1	Number of emitted Notify procedures
This measurement provides the number of emitted Notify SIP messages at the S-CSCF.
CC.
On transmission by the S-CSCF of a SIP_NOTIFY message (see TS 24.229 [8]).
A single integer value.
NOTIF.EmittedNotify.
SCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.9.2	Number of successful Notify procedures
This measurement provides the number of successful Notify messages at the S-CSCF.

CC.
On receipt by the S-CSCF of a response message with response code (e.g. SIP_200_OK) indicating a successful response corresponding to the emited SIP_NOTIFY message (see TS 24.229 [8]).
A single integer value.
NOTIF.SuccNotify.
SCSCFFunction.
Valid for packet switched traffic.
IMS.
4.1.9.3	Number of failed Notify procedures
This measurement provides the number of failed Notify messages at the S-CSCF. The measurement is split into subcounters per response codes.
CC.
On receipt by the S-CSCF of a response message with response code (e.g. SIP_430) indicating a failed response corresponding to the SIP_NOTIFY message (see TS 24.229 [8]), each failed Notify message trial is added to the relevant measurement according to the message type. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
The measurement name has the form NOTIF.FailedNotify.Cause
where Cause identifies the response code. 
SCSCFFunction. 
Valid for packet switched traffic.
IMS.
4.1.10	 Immediate Messaging related measurements
 The three measure types defined in this subclause are subject to the “2 out of 3 approach”.
4.1.10.1	Attempted Immediate Messaging procedures
This measurement provides the number of attempted immediate messaging procedures at S-CSCF.
CC.
On receipt by the S-CSCF of a SIP_MESSAGE request message for the Immediate Messaging (see 3GPP TS 23.228 [7]).
A single integer value.
SC. AttImMsg.
SCSCFFunction.
Valid for packet switching.
IMS.
4.1.10.2	Successful Immediate Messaging procedures
This measurement provides the number of successful immediate messaging procedures at S-CSCF.
CC.
On transmission by the S-CSCF of a response message with a response code (e.g. SIP_200_OK) indicating a successful response corresponding to the SIP_MESSAGE request message (see TS 24.229 [8]).
A single integer value.
SC. SuccImMsg.
SCSCFFunction.
Valid for packet switching.
IMS.
4.1.10.3	Failed Immediate Messaging procedures 
This measurement provides the number of failed immediate messaging procedures at S-CSCF.
CC
On transmission by the S-CSCF of a response message with response code (e.g. SIP_430) indicating a failed response corresponding to the SIP_MESSAGE request message (see TS 24.229 [8]), each failed SIP_MESSAGE request message trial is added to the relevant measurement according to the response message type. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
SC.FailImMsg.Cause	
where Cause identifies the cause of failure.
SCSCFFunction
Valid for packet switching.
IMS.
4.2	Measurements related to HSS
4.2.1	HSS database usage related measurements
4.2.1.1	Provisioning related measurements
4.2.1.1.1	Number of provisioned IMS subscriptions currently stored in a HSS
This measurement provides the number of provisioned IMS subscriptions currently stored in a HSS.
Gauge.
Incremented when a  IMS subscription (3GPP TS 23.228 [7]) is provisioned in the HSS and decremented when a subscription is  removed from the HSS.
A single integer value.
DBU.NbrImsSubscription.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.2	Number of provisioned Private User Identity stored in a HSS
This measurement provides the number of provisioned Private User Identity currently stored in a HSS.
Gauge.
Incremented when a Private User Identity is provisioned in the HSS and decremented when a Private User Identity is removed from the HSS (3GPP TS 23.008 [16]).
A single integer value.
DBU.NbrPriUserId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.3	Number of provisioned Public User Identities with SIP URI format stored in a HSS
This measurement provides the number of provisioned Public User Identities with SIP URI format stored in a HSS.
Gauge.
Incremented when a Public User Identity with SIP URI format (3GPP TS 23.008 [16]) is provisioned in the HSS and decremented when a Public User Identity with SIP URI format is  removed from the HSS.
A single integer value.
DBU.NbrSipPubUserId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.4	Number of provisioned Public User Identities with TEL URI format stored in a HSS
This measurement provides the number of provisioned Public User Identities with TEL URI format stored in a HSS.
Gauge.
Incremented when a Public User Identity with TEL URI format (3GPP TS 23.008 [16]) is provisioned in the HSS and decremented when a Public User identity with TEL URI format is removed from the HSS.
A single integer value.
DBU.NbrTelPubUserId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.5	Number of Private Service Identities stored in a HSS
This measurement provides the number of Private Service Identities currently stored in a HSS.
Gauge.
Incremented when a Private Service Identity (3GPP TS 23.008 [16]) is provisioned in the HSS and decremented when a Private Service Identity is removed from the HSS.
A single integer value.
DBU.NbrPriSrvId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.6	Number of Public Service Identities with SIP URI format stored in a HSS
This measurement provides the number of Public Service Identities with SIP URI format stored in a HSS.
Gauge.
Incremented when a Public Service Identity with SIP URI format (3GPP TS 23.008 [16]) is provisioned in the HSS and decremented when a Public Service Identity with SIP URI format is removed from the HSS.
A single integer value.
DBU.NbrSipPubSrvId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.1.7	Number of Public Service Identities with TEL URI format stored in a HSS
This measurement provides the number of Public Service Identities with TEL URI format stored in a HSS.
Gauge.
Incremented when a  Public Service Identity with TEL URI format (3GPP TS 23.008 [16]) is provisioned in the HSS and decremented when a Public Service Identity with TEL URI format is removed from the HSS.
A single integer value.
DBU.NbrTelPubSrvId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.2	Registration Status related measurements
4.2.1.2.1	Number of Public User Identities in registered state
This measurement provides the number of Public User Identities in registered state stored in a HSS. The measurement is split into subcounters per visited network domain.
Gauge.
Incremented when a Public User Identity's Registration Status changes to "registered", and decremented when a Public User Identity's Registration Status changes from "registered".
An integer value.
DBU.NbrRegPubUserId.RoamingDomain
where RoamingDomain identifies  the Domain Name of the visited network that a registration is initiated from.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.2.2	Number of Public User Identities in unregistered state
This measurement provides the number of Public User Identities in unregistered state stored in a HSS.
Gauge.
Incremented when a Public User Identity's Registration Status changes to "unregistered" and decremented when a Public User Identity's Registration Status changes from "unregistered".
An integer value.
DBU.NbrUnregPubUserId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.1.2.3	Number of Private User Identities in registered state
This measurement provides the number of Private User Identities that have been used in the registration of one or more currently registered Public User Identities stored in a HSS.
Gauge.
Incremented on the emergence of the first registered Public User Identity associated with a Private User Identity and  decremented on the deregistration of the last registered Public User Identity associated with a Private User Identity.
An integer value.
DBU.NbrRegPriUsrId.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.2	User registration status query related measurements
The measurements defined in this subclause are subject to the “2 out of 3 approach”.
 EMBED Word.Picture.8  
Figure 2
4.2.2.1	Attempted user registration status queries
This measurement provides the number of attempted user registration status queries received by a HSS from the I-CSCF.
CC.
On receipt of a Diameter command User-Authorization-Request (UAR) by the HSS from the I-CSCF. (3GPP TS 29.228 [9]).
A single integer value.
UR.AttUAR.
HSSFunction.
Valid for Circuit Switching traffic and packet switching traffic.
IMS.
4.2.2.2	Successful user registration status queries
This measurement provides the number of successfully performed user registration status queries by a HSS. The measurement can be split into subcounters per the success cause.
CC.
On transmission by HSS of Diameter command User-Authorization-Answer (UAA) with Result Code of either DIAMETER_SUCCESS, DIAMETER_SUBSEQUENT_REGISTRATION or DIAMETER_FIRST_REGISTRATION to the I-CSCF (3GPP TS 29.228 [9], 3GPP TS 29.229 [10]), each failed user registration status query procedure is added to the relevant measurement according to the success cause. The sum of all supported per cause measurements shall equal the total number of successful User registration status query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
A single integer value per measurement type defined in e).
The measurement name has the form UR.SuccUAA.Cause
where Cause identifies the successful cause. The Cause shall be the cause code of one of the three success causes defined in bullet c) when constructing the measurement name, 
HSSFunction.
Valid for Circuit Switching traffic and packet switching traffic.
IMS.
4.2.2.3	Failed user registration status queries
This measurement provides the number of failed user registration status query procedures processed by a HSS. The measurement is split into subcounters per the failure cause.
CC
On transmission by the HSS of Diameter command User-Authorization-Answer (UAA) with a Result Code other than DIAMETER_SUCCESS, DIAMETER_SUBSEQUENT_REGISTRATION or DIAMETER_FIRST_REGISTRATION (3GPP TS 29.228 [9]) to the I-CSCF, each failed user registration status query procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed User registration status query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.FailUAA.Cause
where Cause identifies the failure.cause.
HSSFunction.
Valid for Circuit Switching traffic and packet switching traffic.
IMS.
4.2.3	S-CSCF registration/de-registration notification related measurements
The measurements defined in this subclause are subject to the “2 out of 3 approach”.
 EMBED Word.Picture.8  
Figure 3
4.2.3.1	Attempted S-CSCF registration/de-registration notifications
This measurement provides the number of attempted S-CSCF registration/deregistration notifications received by a HSS.
CC.
On receipt of Diameter command Server-Assignment-Request (SAR) by the HSS from the S-CSCF (3GPP TS 29.228 [9]).
A single integer value.
UR.AttSAR.
HSSFunction.
Valid for circuit switching traffic and packet switching traffic.
IMS.
4.2.3.2	Successful S-CSCF registration/de-registration notifications
This measurement provides the number of successfully performed S-CSCF registration/deregistration notifications by a HSS.
CC.
On transmission by HSS of Diameter command Server-Assignment-Answer (UAA) with Result Code of DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the S-CSCF.
A single integer value.
UR.SuccSAA.
HSSFunction.
Valid for circuit switching traffic and packet switching traffic.
IMS.
4.2.3.3	Failed S-CSCF registration/de-registration notifications
This measurement provides the number of failed S-CSCF registration/deregistration notification procedures by a HSS with the S-CSCF. The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command Server-Assignment-Answer (UAA) with a Result Code other than DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the S-CSCF, each S-CSCF Registration/Deregistration notification procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed S-CSCF Registration/Deregistration notification procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.FailSAA.Cause
where Cause identifies the failure cause.
HSSFunction.
Valid for circuit switching traffic and packet switching traffic.
IMS.
4.2.4	Network initiated de-registration by the HSS related measurements
The measurements defined in this subclause are subject to the  “2 out of 3 approach”.
 EMBED Word.Picture.8  
Figure 4
4.2.4.1	Attempted network initiated de-registrations by HSS
This measurement provides the number of attempted network initiated de-registration procedures by a HSS.
CC.
On transmission of Diameter command Registration-Termination-Request (RTR) by the HSS to the S-CSCF (3GPP TS 29.228 [9]).
A single integer value.
UR.AttRTR.
HSSFunction.
Valid for circuit switching traffic and packet switching traffic.
IMS.
4.2.4.2	Successful network initiated de-registrations by HSS
This measurement provides the number of successfully performed network initiated de-registration by a HSS.
CC.
On receipt by HSS of Diameter command Registration-Termination-Anser (RTA) with Result Code of DIAMETER_SUCCESS (3GPP TS 29.228 [9]) from the S-CSCF.
A single integer value.
UR.SuccRTA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.4.3	Failed network initiated de-registrations by HSS
This measurement provides the number of failed network initiated de-registration procedures perceived by a HSS from the S-CSCF. The measurement is split into subcounters per the failure cause.
CC.
On receipt by the HSS of Diameter command Registration-Termination-Answer (RTA) with Result Code other than DIAMETER_SUCCESS (3GPP TS 29.228 [9]) from the S-CSCF, each failed network initiated de-registration by HSS is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10].
And each expected Diameter command Registration-Termination-Aswer (RTA) not received by the HSS is added into failure cause 'No Reply' (not specified in 3GPP TS 29.229 [10]).
The sum of all supported per cause measurements shall equal the total number of failed network initiated de-registrations. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form UR.FailRTA.Cause:
where Cause identifies the failure cause.
The cause 'No Reply' is identified by the .NoReply suffix.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.5	User location query related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 5
4.2.5.1	Attempted user location queries
This measurement provides the number of attempted user location queries received by a HSS from the I-CSCF.
CC.
On receipt of Diameter command Location-Info-Request (LIR) by the HSS from the I-CSCF (3GPP TS 29.228 [9]).
A single integer value.
LIQ.AttLIR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.5.2	Successful user location queries
This measurement provides the number of successfully performed user location queries by a HSS from the I‑CSCF.
CC.
On transmission by HSS of Diameter command Location-Info-Answer (LIA) with Result Code of DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the I-CSCF.
A single integer value.
LIQ.SuccLIA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.5.3	Failed user location queries
This measurement provides the number of failed user location queries procedures by a HSS with the I-CSCF. The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command Location-Info-Answer (LIA) with a Result Code other than DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the I-CSCF, each failed user location query procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed user location query procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form LIQ.FailLIA.Cause
where Cause identifies the failure cause.
HSSFunction
Valid for Circuit switching traffic and packet switching traffic
IMS
4.2.6	HSS initiated update of user profile related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 6
4.2.6.1	Attempted HSS initiated updates of user profile
This measurement provides the number of attempted HSS initiated update of User Profile by a HSS to the S‑CSCF.
CC.
On transmission of Diameter command Push-Profile-Request (PPR) by the HSS to the S-CSCF (3GPP TS 29.228 [9]).
A single integer value.
UP.AttPPR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.6.2	Successful HSS initiated updates of user profile
This measurement provides the number of successfully performed HSS initiated update of User Profile by a HSS to the S-CSCF.
CC.
On receipt by HSS of Diameter command Push-Profile-Answer (PPA) with Result Code of DIAMETER_SUCCESS (3GPP TS 29.228 [9]) from the S-CSCF.
A single integer value.
UP.SuccPPA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.6.3	Failed HSS initiated updates of user profile
This measurement provides the number of failed HSS initiated update of User Profile procedures by a HSS with the S-CSCF. The measurement is split into subcounters per the failure cause.
CC.
On receipt by the HSS of Diameter command Push-Profile-Answer (PPA) with a Result Code other than DIAMETER_SUCCESS (3GPP TS 29.228 [9]) from the S-CSCF, each failed HSS initiated updates of User Profile procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10].
And each expected Diameter command Push-Profile-Answer (PPA) not received by the HSS is added into failure cause 'No Reply' (not specified in 3GPP TS 29.229 [10]).
The sum of all supported per cause measurements shall equal the total number of failed HSS initiated updates of User Profile procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form UP.FailPPA.Cause
where Cause identifies the failure cause.
The cause 'No Reply' is identified by the .NoReply suffix.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.7	Authentication procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 7
4.2.7.1	Attempted authentication procedures
This measurement provides the number of attempted authentication procedures received by a HSS from the S‑CSCF.
CC.
On receipt of Diameter command Multimedia-Auth-Request (MAR) by the HSS from the S-CSCF (3GPP TS 29.228 [9]).
A single integer value.
MA.AttMAR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.7.2	Successful authentication procedures
This measurement provides the number of successfully performed authentication procedures by a HSS with the S-CSCF (3GPP TS 33.203 [28]).
CC.
On transmission by HSS of Diameter command Multimedia-Auth-Answer (MAA) with Result Code of DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the S-CSCF.
A single integer value.
MA.SuccMAA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.7.3	Failed authentication procedures
This measurement provides the number of failed authentication procedures by a HSS with the S-CSCF (3GPP TS 33.203 [28]). The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command Multimedia-Auth-Answer (MAA) with a Result Code other than DIAMETER_SUCCESS (3GPP TS 29.228 [9]) to the S-CSCF, each failed authentication procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.229 [10]. The sum of all supported per cause measurements shall equal the total number of failed authentication procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a sum value identified by the .sum suffix.
The measurement name has the form MA.FailMAA.Cause
where Cause identifies the failure cause.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.8	Data read (Sh-Pull) procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 8
4.2.8.1	Attempted data read (Sh-Pull) procedures
This measurement provides the number of attempted Data read (Sh-Pull) procedures by a HSS from the AS.
CC.
On receipt of Diameter command User-Data-Request (UDR) by the HSS from the AS. (3GPP TS 29.328 [17]).
A single integer value.
DTR.AttUDR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.8.2	Successful data read (Sh-Pull) procedures
This measurement provides the number of successfully Data read (Sh-Pull) procedures by a HSS with the AS.
CC.
On transmission by HSS of Diameter command User-Data-Answer (UDA) to the AS with the result code indicating successful execution of a Data read (Sh-Pull) procedure (3GPP TS 29.329 [18]).
A single integer value.
DTR.SuccUDA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.8.3	Failed data read (Sh-Pull) procedures
This measurement provides the number of failed Data read (Sh-Pull) procedures by a HSS with the AS. The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command User-Data-Answer (UDA) to the AS with the result code indicating a failure (3GPP TS 29.328 [17]), each failed data read procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.329 [18]. The sum of all supported per cause measurements shall equal the total number of failed data read procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form DTR.FailUDA.Cause
where Cause identifies the failure cause.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.9	Data update (Sh-Update) procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 9
4.2.9.1	Attempted data update (Sh-Update) procedures
This measurement provides the number of attempted Data update (Sh-Update) procedures by a HSS from the AS.
CC.
On receipt of Diameter command Profile-Update-Request (PUR) by the HSS from the AS (3GPP TS 29.328 [17]).
A single integer value.
DTU.AttPUR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.9.2	Successful data update (Sh-Update) procedures
This measurement provides the number of successfully Data update (Sh-Update) procedures by a HSS with the AS.
CC.
On transmission by HSS of Diameter command Profile-Update-Answer (PUA) to the AS with the result code indicating successful execution of a data update (Sh-Update) procedure (3GPP TS 29.329 [18]).
A single integer value.
DTU.SuccPUA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.9.3	Failed data update (Sh-Update) procedures
This measurement provides the number of failed data update (Sh-Update) procedures by a HSS with the AS. The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command Profile-Update-Answer (PUA) to the AS with the result code indicating a failure (3GPP TS 29.328 [17]), each failed data update procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.329 [18]. The sum of all supported per cause measurements shall equal the total number of failed data update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form DTU.FailPUA.Cause
where Cause identifies the failure cause.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.10	Subscription to notifications (Sh‑Subs‑Notif) procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 10
4.2.10.1	Attempted subscription to notifications (Sh-Subs-Notif) procedures
This measurement provides the number of attempted subscription to notifications (Sh-Subs-Notif) procedures by a HSS from the AS.
CC.
On receipt of Diameter command Subscribe-Notifications-Request (SNR) by the HSS from the AS (3GPP TS 29.328 [17]).
A single integer value.
SUB.AttSNR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.10.2	Successful subscription to notifications (Sh-Subs-Notif) procedures
This measurement provides the number of successfully subscription to notifications (Sh-Subs-Notif) procedures by a HSS with the AS.
CC.
On transmission by HSS of Diameter Subscribe-Notifications-Answer (SNA) to the AS with the result code indicating successful execution of a subscription to notifications (Sh-Subs-Notif) procedure (3GPP TS 29.329 [18]).
A single integer value.
SUB.SuccSNA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.10.3	Failed subscription to notifications (Sh-Subs-Notif) procedures
This measurement provides the number of failed subscription to notifications (Sh-Subs-Notif) procedures by a HSS with the AS. The measurement is split into subcounters per the failure cause.
CC.
On transmission by the HSS of Diameter command Subscribe-Notifications-Answer (SNA) to the AS with the result code indicating a failure (3GPP TS 29.328 [17]), each failed subscription to notifications procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in 3GPP TS 29.329 [18]. The sum of all supported per cause measurements shall equal the total number of failed subscription to notifications procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form SUB.FailSNA.Cause
where Cause identifies the failure cause.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.11	Notification (Sh-Notif) procedure related measurements
The measurements defined in this subclause are subject to the "2 out of 3 approach".
 EMBED Word.Picture.8  
Figure 11
4.2.11.1	Attempted notification (Sh-Notif) procedures
This measurement provides the number of attempted notification (Sh-Notif) procedures by a HSS to the AS.
CC.
On transmission of Diameter command Push-Notification-Request (PNR) by the HSS to the AS (3GPP TS 29.328 [17]).
A single integer value.
NOTIF.AttPNR.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.11.2	Successful notification (Sh-Notif) procedures
This measurement provides the number of successfully performed Notification (Sh-Notif) procedures by a HSS to the AS.
CC.
On receipt by HSS of Diameter command Push-Notification -Answer (PNA) with the result code indicating successful execution of a notification (Sh-Notif) procedure (3GPP TS 29.329 [18]) from the AS.
A single integer value.
NOTIF.SuccPNA.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.2.11.3	Failed notification (Sh-Notif) procedures
This measurement provides the number of failed notification (Sh-Notif) procedures by a HSS with the AS. The measurement is split into subcounters per the reject cause failure cause.
CC.
On receipt by the HSS of Diameter command Push-Notification-Answer (PNA) with the result code indicating a failure (3GPP TS 29.328 [17]) from the AS, each failed notification procedure is added to the relevant measurement according to the failure cause. Possible failure causes are included in TS 29.329 [18].
And each expected Diameter command Push-Notification-Answer (PNA) not received by the HSS is added into failure cause 'No Reply' (not specified in 3GPP TS 29.329 [18]).
The sum of all supported per cause measurements shall equal the total number of failed notification procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form NOTIF.FailPNA.Cause:
where Cause identifies the failure cause.
The cause 'No Reply' is identified by the .NoReply suffix.
HSSFunction.
Valid for Circuit switching traffic and packet switching traffic.
IMS.
4.3	Measurements related to BGCF
4.3.1	Session Control related measurements
4.3.1.1	Overview
The performance measurements defined in subclause 4.3.1 are related to the procedures that BGCF forwards session to the selected network. 
Based on the procedures described in 3GPP TS 23.228 [7] and 3GPP TS 24.229 [8], when the BGCF receives a request, the BGCF shall forward the request: 
-	to an MGCF within its own network for calls routing to PSTN/CS domain in the same network; or
-	to another BGCF in the selected network for calls routing to PSTN/CS domain in another network; or
-	to an I-CSCF in the selected network for sessions routing to another IMS network ; or 
-	to an IBCF in its own network for sessions routing to another IMS network or other SIP-based multimedia networks, if local policy requires IBCF capabilities towards another network.
4.3.1.2	Attempted sessions at BGCF
This measurement provides the number of attempted sessions at the BGCF when network breakout is to occur.
CC.
On receipt by the BGCF of an initial SIP_INVITE message (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSession.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.3	Attempted sessions forwarded to MGCF
This measurement provides the number of attempted sessions forwarded to the MGCF within the same network at the BGCF for calls routing to PSTN/CS domain in the same network.
CC.
On transmission by the BGCF of an initial SIP_INVITE message to the MGCF within the same network (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSessionFwdToMGCF.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.4	Attempted sessions forwarded to BGCF
This measurement provides the number of attempted sessions forwarded to the BGCF in  the selected network for calls routing to PSTN/CS domain in another network.
CC.
On transmission by the BGCF of an initial SIP_INVITE message to the BGCF in a different network (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSessionFwdToBGCF.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.4a	Attempted sessions forwarded to I-CSCF
This measurement provides the number of attempted sessions forwarded to the I-CSCF in the selected network for sessions routing to another IMS network.
CC.
On transmission by the BGCF of an initial SIP_INVITE message to the I-CSCF in a different network (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSessionFwdToCSCF.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.4b	Attempted sessions forwarded to IBCF
This measurement provides the number of attempted sessions forwarded to the IBCF in its own network for sessions routing to another IMS network or other SIP-based multimedia networks, if local policy requires IBCF capabilities towards another network.
CC.
On transmission by the BGCF of an initial SIP_INVITE message to the IBCF in a different network (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSessionFwdToIBCF.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.5	Successful sessions forwarded to MGCF
This measurement provides the number of successful sessions forwarded to the MGCF at the BGCF for calls routing to PSTN or CS domain in the same network.
CC.
On receipt by the BGCF of a response message (e.g. SIP_180 or SIP_200) indicating a successful session from the MGCF in the same network, corresponding to the transmitted initial SIP_INVITE message (see 3GPP TS 23.228 [7]). Each successful session forwarded to MGCF is added to the relevant measurement according to the message type. The sum of all supported per message type measurements shall equal the total number of successful sessions forwarded to MGCF. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionFwdToMGCF.type
where type identifies the message type.
The following subcounters  with specific message types are the samples of this measurement:
SC.SuccSessionFwdToMGCF.180	Message type: SIP_180
SC.SuccSessionFwdToMGCF.200	Message type: SIP_200_OK only if the SIP_180 has not been received 	for this session.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.6	Successful sessions forwarded to BGCF
This measurement provides the number of successful forwarded sessions to the BGCF in the selected network for calls routing to PSTN/CS domain in another network.
CC.
On receipt by the BGCF of a response message (e.g.SIP_180 or SIP_200）indicating a successful session from the BGCF in another network, corresponding to the transmitted initial SIP_INVITE message (see 3GPP TS 23.228 [2]). Each successful session forwarded to BGCF is added to the relevant measurement according to the message type. The sum of all supported per message type measurements shall equal the total number of successful sessions forwarded to BGCF. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionFwdToBGCF.type
where type identifies the message type
The following subcounters  with specific message types are the samples of this measurement:
SC.SuccSessionFwdToBGCF.180	Message type: SIP_180
SC.SuccSessionFwdToBGCF.200	Message type: SIP_200_OK only if the SIP_180 has not been received 	for this session.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.7	Successful sessions forwarded to I-CSCF
This measurement provides the number of successful sessions forwarded to the I-CSCF in the selected network for sessions routing to another IMS network.
CC.
On receipt by the BGCF of a response message (e.g. SIP_180 or SIP_200) indicating a successful session from the I-CSCF in a different network, corresponding to the transmitted initial SIP_INVITE message (see 3GPP TS 23.228 [7]). Each successful session forwarded to I-CSCF is added to the relevant measurement according to the message type. The sum of all supported per message type measurements shall equal the total number of successful sessions forwarded to I-CSCF. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionFwdToCSCF.type
where type identifies the message type.
The following subcounters  with specific message types are the samples of this measurement:
SC.SuccSessionFwdToCSCF.180	Message type: SIP_180
SC.SuccSessionFwdToCSCF.200	Message type: SIP_200_OK only if the SIP_180 has not been received 	for this session.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.3.1.8	Successful sessions forwarded to IBCF
This measurement provides the number of successful forwarded sessions to the IBCF in its own network for sessions routing to another IMS network or other SIP-based multimedia networks, if local policy requires IBCF capabilities towards another network..
CC.
On receipt by the IBCF of a response message (e.g.SIP_180 or SIP_200）indicating a successful session from the IBCF in another network, corresponding to the transmitted initial SIP_INVITE message (see 3GPP TS 23.228 [7]). Each successful session forwarded to IBCF is added to the relevant measurement according to the message type. The sum of all supported per message type measurements shall equal the total number of successful sessions forwarded to IBCF. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionFwdToIBCF.type
where type identifies the message type
The following subcounters  with specific message types are the samples of this measurement:
SC.SuccSessionFwdToIBCF.180	Message type: SIP_180
SC.SuccSessionFwdToIBCF.200	Message type: SIP_200_OK only if the SIP_180 has not been received 	for this session.
BGCFFunction.
Valid for packet switched traffic.
IMS.
4.4	Measurements related to MGCF
4.4.1	Call control related measurements
4.4.1.1	Call control related measurements, CS network originated
The measurements defined in subclauses 4.4.1.1.2, 4.4.1.1.3 and 4.4.1.1.5 are subject to the "2 out of 3 approach".
4.4.1.1.1	Overview
The performance measurements defined in this subclause are related to the CS network originated call that is intentionally routed to IM CN subsystem.
 EMBED Visio.Drawing.11  
Figure 14: CS network originated, IM CN terminated call procedure
4.4.1.1.2	Attempted calls, CS network originated
This measurement provides the number of attempted calls from CS network.
CC.
On receipt by the MGCF of an "IAM" message(see 3GPP TS 29.163 [11]).
A single integer value.
CC.AttCallCsOrig.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.1.3	Successful calls, CS network originated
This measurement provides the number of successful calls from CS network.
CC.
On transmission by the MGCF of an "ACM" or "CON" message (see 3GPP TS 29.163 [11]).
NOTE:	If ACM message is not sent, the "CON" message shall be the trigger.
A single integer value.
CC.SuccCallCsOrig.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.1.4	Answered calls, CS network originated
This measurement provides the number of answered calls from CS network.
CC.
On transmission by the MGCF of an "ANM" or "CON" message (see 3GPP TS 29.163 [11]).
A single integer value.
CC.AnsCallCsOrig.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.1.5	Failed calls, CS network originated
This measurement provides number of failed calls (the calls are originated from CS network).
CC.
Before MGCF sends “ACM" or "CON" message (see 3GPP TS 29.163 [11]), the call is released..
A single integer value.
CC.FailCallCsOrig.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.1.6	Call set-up time (Mean), CS network originated
This measurement provides the mean setup time of the successful CS network originated calls.
DER (n=1).
This measurement is obtained by accumulating the time intervals for every successful CS network originated calls between the receipt of "IAM" message and the transmission of  the corresponding "ACM" message or "CON" message if the "ACM" message is not sent over a granularity period using DER (see 3GPP TS 29.163 [11]). The end value of this time will then be divided by the number of successful CS network originated calls observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.
A single integer value (in milliseconds).
CC.SetupTimeCsOrigMean.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.2	Call control related measurements, IM CN originated
The measurements defined in subclauses 4.4.1.2.2, 4.4.1.2.3 and 4.4.1.2.5 are subject to the "2 out of 3 approach".
4.4.1.2.1	Overview
The performance measurements defined in this subclause is related to the IM CN subsystem originated call that is intentionally routed to CS network.
 EMBED Visio.Drawing.11  
Figure 15: IM CN originated, CS network terminated call procedure
4.4.1.2.2	Attempted calls, IM CN originated
This measurement provides the number of attempted calls from IM CN subsystem.
CC.
On receipt by the MGCF of an initial SIP_INVITE message (see 3GPP TS 29.163 [11]).
A single integer value.
CC.AttCallImOrig.
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.2.3	Successful calls, IM CN originated
This measurement provides the number of successful calls from IM CN subsystem. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful IM CN originated call.
CC.
On transmission by the MGCF of a response message (e.g. SIP_180) indicating a successful IM CN subsystem originated call corresponding to the initial SIP_INVITE message (see 3GPP TS 29.163 [11]), each successful IM CN originated call is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful IM CN subsystem originated calls. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
The measurement name has the form CC.SuccCallImOrig.type
where type identifies the message type. 
The following subcounters with specific message types are the samples of this measurement:
CC.SuccCallImorig.180	Message type: SIP_180. MGCF sends SIP_180.
CC.SuccCallImorig.200	Message type: SIP_200. MGCF sends SIP_200_OK after receiving CON 	message instead of ACM message.
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.2.4	Answered calls, IM CN originated
This measurement provides the number of answered calls from IM CN subsystem.
CC.
On transmission by the MGCF of a SIP_200_OK message corresponding to an initial SIP_INVITE message. (see 3GPP TS 29.163 [11]).
A single integer value.
CC.AnsCallImOrig.
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.2.5	Failed calls, IM CN originated
This measurement provides number of failed calls (the calls are originated from IM CN subsystem).
CC.
Before MGCF sends SIP 180 or SIP 200 without 180 (see 3GPP TS 29.163 [11]), the call is released..
A single integer value.
CC.FailCallImOrig.
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.2.6	Call set-up time (Mean), IM CN originated
This measurement provides the mean setup time of the successful IM CN subsystem originated calls.
DER (n=1).
This measurement is obtained by accumulating the time intervals for every successful IM CN subsystem originated calls between the receipt of an initial SIP_INVITE message and the transmission of corresponding SIP_180 or SIP_200_OK without SIP_180 message over a granularity period using DER (see 3GPP TS 29.163 [11]). The end value of this time will then be divided by the number of successful IM CN subsystem originated calls observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.
A single integer value (in milliseconds).
CC.SetupTimeImOrigMean.
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.3	Call control related measurements, call release
4.4.1.3.1	Overview
The performance measurements defined in this subclause are related to the call release initiated by CS network, IM CN subsystem, MGCF itself and MGW respectively.
4.4.1.3.2	Call release initiated by CS network
This measurement provides the number of call release initiated by CS network with "REL" or "RSC" or "GRS" message. The measurement is split into subcounters per release message type, and per cause for the REL message.
CC.
On receipt by the MGCF of an ISUP/BICC "REL" or "RSC" or "GRS" message (see 3GPP TS 29.163 [11]).
Each measurement is an integer value. The number of measurements is equal to the number of supported causes in ISUP/BICC "REL" message, plus two values for ISUP/BICC "RSC" and "GRS" message respectively and a possible sum value identified by the .sum suffix.
CC.RelCallCsInit.CauseOrMsg.
Where CauseOrMsg identifies the cause in ISUP/BICC "REL" message if the call is released by ISUP/BICC "REL" message (see ITU-T Recommendation Q.850 [19]), or the message type ISUP/BICC "RSC" or "GRS" respectively if the call is released by ISUP/BICC "RSC" or "GRS" message. If the call is released by ISUP/BICC "RSC" or "GRS" message, the CauseOrMsg shall be the constant string "RSC" or "GRS" respectively when constructing the measurement name.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.3.3	Call release initiated by IM CN subsystem
This measurement provides the number of call release initiated by IM CN subsystem. The measurement is split into subcounters per message type.
CC.
On receipt by the MGCF of a SIP_BYE or SIP_CANCEL or SIP_3XX or SIP_4XX or SIP_5XX or SIP_6XX message (see 3GPP TS 29.163 [11]).
6 single integer values.
CC.RelCallsImInit.BYE
CC.RelCallsCsInit.CANCEL
CC.RelCallsCsInit.3XX
CC.RelCallsCsInit.4XX
CC.RelCallsCsInit.5XX
CC.RelCallsCsInit.6XX
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.3.4	Call release initiated by MGCF
This measurement provides the number of autonomous call release initiated by MGCF itself. The measurement is split into subcounters per message type.
CC.
On transmission of call release message by MGCF due to autonomous call releases (see 3GPP TS 29.163 [11]).
NOTE:	MGCF sends call release message to CS network and IM CN subsystem respectively for one call, just count once.
8 single integer values.
CC.RelCallsMgcfInit.484Imgcf
CC.RelCallsMgcfInit.480Imgcf
CC.RelCallsMgcfInit.488Imgcf
CC.RelCallsMgcfInit.500Imgcf
CC.RelCallsMgcfInit.CotOmgcf
CC.RelCallsMgcfInit.47Omgcf
CC.RelCallsMgcfInit.IsupBiccOmgcf
CC.RelCallsMgcfInit.SipOmgcf.
The corresponding scenario for these 2 measurements are:
CC.RelCallsMgcfInit.484Imgcf	I-MGCF initiates call release by sending SIP 484 Address Incomplete.
CC.RelCallsMgcfInit.480Imgcf	I-MGCF initiates call release by sending SIP 480 Temporarily 	Unavailable.
CC.RelCallsMgcfInit.488Imgcf	I-MGCF initiates call release by sending SIP 488 Not Acceptable Here.
CC.RelCallsMgcfInit.500Imgcf	I-MGCF initiates call release by sending SIP 500 Server Internal Error.
CC.RelCallsMgcfInit.CotOmgcf	O-MGCF initiates call release on reception of COT with the Continuity 	Indicators parameter set to "continuity check failed" or expiry of 	ISUP/BICC T8.
CC.RelCallsMgcfInit.47Omgcf	O-MGCF initiates call release by sending ISUP/BICC "REL" with 	cause value (resource unavailable or unspecified).
CC.RelCallsMgcfInit.IsupBiccOmgcf	O-MGCF initiates call release by ISUP/BICC procedure.
CC.RelCallsMgcfInit.SipOmgcf	O-MGCF initiates call release by SIP procedure.
MGCFFunction.
Valid for circuit switched and packet switched traffic.
IMS.
4.4.1.3.5	Call release initiated by MGW
This measurement provides the number of call release initiated by MGW. The measurement is split into subcounters per H248 error code and H248 service change reason.
CC.
On receipt by the MGCF of a H248 message which triggers call release (see ITU-T Recommendation H.248.1 [20]).
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
CC.RelCallsMgwInit.Cause.
Where Cause identifies the H248 error code or H248 service change reason.(see ITU-T Recommendation H.248.8 [21]).
MGCFFunction.
Valid for packet switched traffic.
IMS.
4.4.1.4	Number of simultaneous online and answered calls (Maximum)
This measurement provides the maximum number of simultaneous online calls which have been answered in the MGCF.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online calls which have been answered and then taking the maximum.
A single integer value.
CC.NbrAnsCallMax.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.4.1.5	Number of simultaneous online and answered calls (mean)
This measurement provides the mean number of simultaneous online calls which have been answered in the MGCF.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online calls which have been answered and then taking the arithmetic mean.
A single integer value.
CC.NbrAnsCallMean.
MGCFFunction.
Valid for circuit switched traffic.
IMS.
4.5	Measurements related to IM-MGW
The measurements related to IM-MGW is the same with CS MGW defined in 3GPP TS 32.407[29].
4.6	Measurements related to MRFC
4.6.1	Session control related measurements
The measurements defined in subclauses 4.6.1.1, 4.6.1.2 and 4.6.1.4 are subject to the "2 out of 3 approach".
4.6.1.1	Attempted session establishments
This measurement provides the number of attempted session establishments at MRFC.
CC.
On receipt by the MRFC of an initial SIP_INVITE message (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSession.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.1.2	Successful session establishments
This measurement provides the number of successful session establishments at the MRFC. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful session establishments.
CC.
On transmission by the MRFC of a response message (e.g. SIP_180) indicating a successful session establishment corresponding to the initial SIP_INVITE message (see 3GPP TS 23.228 [7]), each successful session is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful session establishments. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSession.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this session.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.1.3	Answered session establishments
This measurement provides the number of answered session establishments at the MRFC.
CC.
On transmission by the MRFC of a SIP_200_OK response message corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AnsSession.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.1.4	Failed session establishments
This measurement provides the number of failed session establishments at the MRFC. The measurement is split into subcounters per response status codes.
CC.
On transmission by the MRFC of a response message (e.g. SIP_430) indicating a failed session establishment corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]), each failed session establishment is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of status codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailSession.Cause
where Cause identifies the status code.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2	Multi-party sessions related measurements
The measurements defined in subclauses 4.6.2.1, 4.6.2.2 and 4.6.2.4 are subject to the "2 out of 3 approach".
The measurements defined in subclauses 4.6.2.5, 4.6.2.6 and 4.6.2.7 are subject to the "2 out of 3 approach".
4.6.2.1	Attempted session establishments for multi-party sessions
This measurement provides the number of attempted session establishments for multi-party sessions at MRFC.
CC.
On receipt by the MRFC of an initial SIP_INVITE message for the multi-party sessions service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttMultipartySession.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.2	Successful session establishments for multi-party sessions
This measurement provides the number of successful session establishments for multi-party sessions at the MRFC. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful session establishments for multi-party sessions.
CC.
On transmission by the MRFC of a response message (e.g. SIP_180) indicating a successful session establishment corresponding to the initial SIP_INVITE message for the multi-party sessions service (see 3GPP TS 23.228 [7]), each successful session is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful session establishments for multi-party sessions. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccMultipartySession.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this session.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.3	Answered session establishments for multi-party sessions
This measurement provides the number of answered session establishments for multi-party sessions at the MRFC.
CC.
On transmission by the MRFC of a SIP_200_OK response message corresponding to the initial SIP_INVITE messages for the multi-party sessions service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AnsMultipartySession.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.4	Failed session establishments for multi-party sessions
This measurement provides the number of failed session establishments for multi-party sessions at the MRFC. The measurement is split into subcounters per response status codes.
CC.
On transmission by the MRFC of a response message (e.g. SIP_430) indicating a failed session establishment corresponding to the initial SIP_INVITE message for the multi-party session service (see 3GPP TS 23.228 [7]), each failed session establishment is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments for the multi-party sessions. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of status codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailMultipartySession.Cause
where Cause identifies the status code.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.5	Attempted event subscription procedures for multi-party sessions
This measurement provides the number of attempted event subscription procedures for multi-party sessions at MRFC.
CC.
On receipt by the MRFC of a SIP_SUBSCRIBE message for the multi-party sessions service (see 3GPP TS 23.228 [7] and RFC3265[22]).
A single integer value.
SC.AttSubscribe.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.6	Successful event subscription procedures for multi-party sessions
This measurement provides the number of successful event subscription procedures for multi-party sessions at MRFC.
CC.
On transmission by the MRFC of a SIP_200_OK message corresponding to the SIP_SUBSCRIBE message for the multi-party sessions service (see 3GPP TS 23.228 [7] and RFC3265[22]).
A single integer value.
SC.SuccSubscribe.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.2.7	Failed event subscription procedures for multi-party sessions
This measurement provides the number of failed event subscription procedures for multi-party sessions at MRFC. The measurement is split into subcounters per response status codes.
CC.
On transmission by the MRFC of a response message (e.g. SIP_430) indicating a failed event subscription procedure corresponding to the initial SIP_SUBSCRIBE message for the multi-party session service (see 3GPP TS 23.228 [7] and RFC3265[22]), each failed event subscription procedures is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed event subscription procedures for the multi-party sessions. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of status codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailSubscribe.Cause
where Cause identifies the status code.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.3	Announcement service related measurements
The measurements defined in subclauses 4.6.3.1, 4.6.3.2 and 4.6.3.4 are subject to the "2 out of 3 approach".
4.6.3.1	Attempted session establishments for announcements
This measurement provides the number of attempted session establishments for announcements at MRFC.
CC.
On receipt by the MRFC of an initial SIP_INVITE message for the announcement service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttAnnounce.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.3.2	Successful session establishments for announcements
This measurement provides the number of successful session establishments for announcements at the MRFC. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful session establishments for announcements.
CC.
On transmission by the MRFC of a response message (e.g. SIP_180) indicating a successful session establishment corresponding to the initial SIP_INVITE message for the announcement service (see 3GPP TS 23.228 [7]), each successful session is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful session establishments for announcements. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccAnnounce.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this session.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.3.3	Answered session establishments for announcements
This measurement provides the number of answered session establishments for announcements at the MRFC.
CC.
On transmission by the MRFC of a SIP_200_OK response message corresponding to the initial SIP_INVITE messages for the announcement service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AnsAnnounce.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.3.4	Failed session establishments for announcements
This measurement provides the number of failed session establishments for announcements at the MRFC. The measurement is split into subcounters per response status codes.
CC.
On transmission by the MRFC of a response message (e.g. SIP_430) indicating a failed session establishment corresponding to the initial SIP_INVITE message for the announcement service (see 3GPP TS 23.228 [7]), each failed session establishment is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments for the announcements. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of status codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailAnnounce.Cause
where Cause identifies the status code.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.4	Transcoding service related measurements
The measurements defined in subclauses 4.6.4.1, 4.6.4.2 and 4.6.4.4 are subject to the "2 out of 3 approach".
4.6.4.1	Attempted session establishments for transcoding service
This measurement provides the number of attempted session establishments for transcoding service at MRFC.
CC.
On receipt by the MRFC of an initial SIP_INVITE message for the transcoding service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttTranscoding.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.4.2	Successful session establishments for transcoding service
This measurement provides the number of successful session establishments for transcoding service at the MRFC. The measurement is split into subcounters per message type (e.g. SIP_180) indicating the successful session establishments for transcoding service.
CC.
On transmission by the MRFC of a response message (e.g. SIP_180) indicating a successful session establishment corresponding to the initial SIP_INVITE message for the transcoding service (see 3GPP TS 23.228 [7]), each successful session is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful session establishments for transcoding service. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccTranscoding.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this session.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.4.3	Answered session establishments for transcoding service
This measurement provides the number of answered session establishments for transcoding service at the MRFC.
CC.
On transmission by the MRFC of a SIP_200_OK response message corresponding to the initial SIP_INVITE messages for the transcoding service (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AnsTranscoding.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.6.4.4	Failed session establishments for transcoding service
This measurement provides the number of failed session establishments for transcoding service at the MRFC. The measurement is split into subcounters per response status codes.
CC.
On transmission by the MRFC of a response message (e.g. SIP_430) indicating a failed session establishment corresponding to the initial SIP_INVITE message for the transcoding service (see 3GPP TS 23.228 [7]), each failed session establishment is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments for the transcoding service. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of status codes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailTranscoding.Cause
where Cause identifies the status code.
MRFCFunction.
Valid for packet switched traffic.
IMS.
4.7	Measurements related to MRFP
4.7.1	RTP related measurements
Performance Measurement definitions in this subclause are only valid if the RTP protocol is used at the MRFP.
4.7.1.1	Number of incoming RTP packets
This measurement provides the number of incoming RTP packets at MRFP.
CC.
On receipt by the MRFP of a RTP packet (see RFC 3550 [23]).
A single integer value.
RTP.IncPacket.
MRFPFunction.
Valid for packet switched traffic.
IMS.
4.7.1.2	Number of outgoing RTP packets
This measurement provides the number of outgoing RTP packets at MRFP.
CC.
On transmission by the MRFP of a RTP packet (see RFC 3550 [23]).
A single integer value.
RTP.OutgPacket.
MRFPFunction.
Valid for packet switched traffic.
IMS.
4.7.1.3	Number of octets of incoming RTP packets
This measurement provides the number of octets of incoming RTP packets at MRFP.
DER (n=1).
This measurement is obtained by accumulating the number of incoming RTP packet octets (bytes) on receipt by the MRFP of a RTP packet (see RFC 3550 [23]).
A single integer value.
RTP.IncOctet.
MRFPFunction.
Valid for packet switched traffic.
IMS.
4.7.1.4	Number of octets of outgoing RTP packets
This measurement provides the number of octets of outgoing RTP packets at MRFP.
DER (n=1).
This measurement is obtained by accumulating the number of outgoing RTP packet octets (bytes) on transmission by the MRFP of a RTP packet (see RFC 3550 [23]).
A single integer value.
RTP.OutgOctet.
MRFPFunction.
Valid for packet switched traffic.
IMS.
4.7.1.5	Number of lost incoming RTP packets
This measurement provides the number of lost incoming RTP packets.
CC.
On detection of loss of an incoming RTP packet by the MRFP (see RFC 3550 [23]).
A single integer value.
RTP.LostIncPacket.
MRFPFunction.
Valid for packet switched traffic.
IMS.
4.8	Measurements related to PCRF
The measurements related to PDF are restricted to R6 network architecture.
Editor's note: PCRFFunction used in following text is a subject for further study of IMS NRM modelling for R7 requirements and working 3GPP/3GPP2 IMS NRM alignment.
4.8.1	Authorization of QoS resources related measurements
The five measurement types defined in this subclause are subject to the "4 out of 5 approach".
4.8.1.1	Overview
The measurements defined in subclause 4.8.1 are related to procedures of QoS resource authorization. AF initiates a Diameter transaction to PCRF for authorizing the resources in the session establishment or modification. PCRF authorizes the resources based on binding mechanism and service information.
The procedure is shown in figure 16.
 EMBED Word.Picture.8   EMBED Word.Picture.8  
Figure 16: Resource authorization procedure
4.8.1.2	Attempted resource authorization procedures at session establishment
This measurement provides the number of attempted resource authorizations initiated by AF to PCRF when establishing new sessions.
CC.
On receipt by the PCRF of an AAR Diameter command from AF with a new session ID (see 3GPP TS 29.213[33]).
A single integer value.
QoS.EstabAttAARSession.
PCRFFunction.
Valid for packet switched traffic.
IMS
4.8.1.3	Attempted resource authorization procedures at session modification
This measurement provides the number of attempted resource authorizations initiated by AF to PCRF when modifying the existing sessions.
CC.
On receipt by the PCRF of an AAR Diameter command from AF to modify an existing session (see 3GPP TS 29.213 [33]).
A single integer value.
QoS.ModfAttAARSession.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.1.4	Successful resource authorization procedures at session establishment
This measurement provides the number of successful resource authorizations initiated by AF to PCRF when establishing new sessions.
CC.
On transmission by the PCRF of an AAA Diameter command to AF with a new stored session ID and "2xxxx" result-code (see 3GPP TS 29.213[33], RFC 3588 [15]).
A single integer value.
QoS.EstabSuccAAASession.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.1.5	Successful resource authorization procedures at session modification
This measurement provides the number of successful resource authorizations initiated by AF to PCRF when modifying the existing sessions.
CC.
On transmission by the PCRF of an AAA Diameter command to AF with an existing session ID and "2xxxx" result-code (see 3GPP TS 29.213[33], RFC 3588 [15]).
A single integer value.
QoS.ModfSuccAAASession.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.1.6	Failed resource authorization procedures
This measurement provides the number of failed resource authorizations initiated by AF to PCRF.
CC.
On transmission by the PCRF of an AAA Diameter command to AF with non-2xxx result-code (see 3GPP TS 29.213 [33], RFC 3588 [15]). Each failed resource authorization procedure will be added to the relevant measurement according to the failure cause. Possible failure causes are included in RFC 3588 [15]. The sum of all supported per cause measurements shall equal the total number of failed resource authorization procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form QoS.FailAAA.Cause
where Cause identifies the failure cause.
PCRFFunction.
Valid for packet switched traffic.
IMS.	
4.8.2	Resource reservation related measurements
4.8.2.1	Void
4.8.2.2	Attempted resource reservation procedures
This measurement provides the number of attempted resource reservation procedures initiated by GGSN to PDF.
CC.
On receipt by the PDF of COPS REQ message from GGSN (see 3GPP TS 29.207[13]).
A single integer value.
QoS.AttResRsv.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.2.3	Successful resource reservation procedures
This measurement provides the number of successful resource reservation procedures initiated by GGSN to PDF.
CC.
On receipt by the PDF of a COPS RPT message from GGSN indicating a successful resource reservation procedure (see 3GPP TS 29.207[13]).
A single integer value.
QoS.SuccResRsv.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.2.4	Failed resource reservation procedures by PDF
This measurement provides the number of resource reservation failures caused by the authorization failure in PDF. This measurement is split into subcounters per failure cause.
CC.
On transmission by the PDF of a COPS DEC message containing both an INSTALL and a REMOVE decisions to GGSN (see 3GPP TS 29.207[13]).
Three integer values.
QoS.FailResRsvPdf.1	Failure cause "NoCorrespondingSession".
QoS.FailResRsvPdf.2	Failure cause "InvalidBundling".
QoS.FailResRsvPdf.3	Failure cause "AuthorisationFailure".
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.2.5	Failed resource reservation procedures by GGSN
This measurement provides the number of resource reservation failures caused by the enforcement failure in GGSN.
CC.
On receipt by the PDF of a COPS RPT message with a failure result from GGSN, corresponding to the transmission of the COPS DEC message containing only an INSTALL decision to GGSN (see 3GPP TS 29.207 [13]).
A single integer value.
QoS.FailResRsvGgsn.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.3	IP-CAN session modification related measurements
The measurements defined in subclauses 4.8.3.1, 4.8.3.2 and 4.8.3.3 are subject to the "2 out of 3 approach".
4.8.3.1	Attempted IP-CAN session modification
This measurement provides the number of attempted IP-CAN session modifications procedures initiated by UE.
CC.
On receipt by the PCRF of a Credit-Control-Request(CCR) Diameter command from PCEF to modify an existing  IP-CAN session initiated by UE (PCC Rule Provisioning in PULL Mode) (see 3GPP TS 29.213 [33], 3GPP TS 29.212[32]).
A single integer value.
QoS.ModfAttCCR.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.3.2	Successful IP-CAN session modification
This measurement provides the number of successful IP-CAN session modifications procedures initiated by UE.
CC.
On transmission by the PCRF of a Credit-Control-Answer(CCA) Diameter command to PCEF with an existing session ID and "2xxx" result-code in the UE-Initiated IP-CAN session modification procedures(PCC Rule Provisioning in PULL Mode) (see 3GPP TS 29.212[32], 3GPP TS 29.213[33], RFC 3588 [15]).
A single integer value.
QoS.ModfSuccCCA.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.3.3	Failed IP-CAN session modification
This measurement provides the number of failed IP-CAN session modifications procedures initiated by UE. The measurement is split into subcounters per the reject cause.
CC.
On transmission by the PCRF of a Credit-Control-Answer(CCA) Diameter command to PCEF with non-2xxx result-code in the UE-Initiated IP-CAN session modification procedures (PCC Rule Provisioning in PULL Mode) (see 3GPP TS 29.212 [32], 3GPP TS 29.213[33], RFC 3588 [15]). Each failed IP-CAN session modification will be added to the relevant measurement according to the failure cause. Possible failure causes are included in RFC 3588 [15]. The sum of all supported per cause measurements shall equal the total number of failed resource authorization procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
QoS.ModfFailCCA.Cause
where Cause identifies the failure cause.
PCRFFunction.
Valid for packet switched traffic.
IMS.
4.8.3	PDP context modification related measurements
The measurements defined in subclauses 4.8.3.1, 4.8.3.2 and 4.8.3.3 are subject to the "2 out of 3 approach".
4.8.3.1	Attempted authorization of PDP context modification
This measurement provides the number of attempted authorizations of PDP context modifications initiated by GGSN.
CC.
On receipt by the PDF of a COPS REQ message from GGSN to authorize a PDP context modification request (see 3GPP TS 29.207 [13]).
A single integer value.
QoS.AttPdpContextModfAuth.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.3.2	Successful authorization of PDP context modification
This measurement provides the number of successful authorizations of PDP context modifications initiated by GGSN.
CC.
On transmission by the PDF of a COPS DEC message containing only an INSTALL decision to GGSN, in response to a PDP context modification request from GGSN, indicating a successful authorization of PDP context modification (see 3GPP TS 29.207 [13]).
A single integer value.
QoS.SuccPdpContextModfAuth.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.3.3	Failed authorization of PDP context modification
This measurement provides the number of failed authorizations of PDP context modifications initiated by GGSN.
CC.
On transmission by the PDF of a COPS DEC message containing an INSTALL decision and a REMOVE decision to GGSN, corresponding to the receipt of the PDP context modification request from GGSN (see 3GPP TS 29.207 [13]).
A single integer value.
QoS.FailPDPContextModfAuth.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.8.3.4	Indication of PDP context modification
This measurement provides the number of PDP context modifications to/from 0kbps initiated by GGSN.
CC.
On receipt by the PDF of a COPS RPT message indicating the PDP context modification to/from 0kbps from GGSN (see 3GPP TS 29.207 [13]).
A single integer value.
QoS.IndPdpContextModf.
PDFFunction.
Valid for packet switched traffic.
IMS.
4.9	Measurements related to SLF
4.9.1	All routing information interrogations related measurements
4.9.1.1	Attempted routing information interrogation procedures
This measurement provides the number of all routing information interrogation requests received by the SLF via all diameter application interfaces. The diameter interfaces can be Dx interface, Dh interface or Dw interface.
CC.
On receipt by the SLF of a routing information interrogation request diameter message from all diameter interfaces (see 3GPP TS 23.228 [7] and RFC 3588[15]).
A single integer value.
RII.AttAll.
SLFFunction.
Valid for packet switched traffic.
IMS.
4.9.1.2	Successful routing information interrogation procedures
This measurement provides the number of all successful routing information interrogation responses sent by the SLF via all diameter application interfaces. The diameter interfaces can be Dx interface, Dh interface or Dw interface.
CC.
On transmission by the SLF of a routing information interrogation response diameter message with the Result-Code AVP set to DIAMETER_REDIRECT_INDICATION via all diameter interfaces, indicating a successful routing information interrogation (see 3GPP TS 23.228 [7] and RFC 3588 [15]).
A single integer value.
RII.SuccAll
SLFFunction.
Valid for packet switched traffic.
IMS.
4.9.2	Routing information interrogation from CSCF related measurements
4.9.2.1	Overview
The performance measurements defined in subclause 4.9.2 are related to routing information interrogations at the SLF from CSCF.
 EMBED Word.Picture.8  
Figure 18: Routing information interrogation procedure from CSCF
4.9.2.2	Attempted routing information interrogation procedures from CSCF
This measurement provides the number of routing information interrogation requests received from CSCF by the SLF.
CC.
On receipt by the SLF of a DX_SLF_QUERY message from CSCF via Dx interface (see 3GPP TS 23.228 [7]).
A single integer value.
RII.AttFromCSCF.
SLFFunction.
Valid for packet switched traffic.
IMS.
4.9.2.3	Successful routing information interrogation procedures from CSCF
This measurement provides the number of successful routing information interrogation responses sent to CSCF by the SLF.
CC.
On transmission by the SLF of a DX_SLF_RESP message with the Result-Code AVP set to DIAMETER_REDIRECT_INDICATION to CSCF via Dx interface (see 3GPP TS 23.228 [7] and RFC 3588[15]).
A single integer value.
RII.SuccFromCSCF.
SLFFunction.
Valid for packet switched traffic.
IMS.
4.9.3	Routing information interrogation from AS related measurements
4.9.3.1	Overview
The performance measurements defined in subclause 4.9.3 are related to routing information interrogations at the SLF from AS.
 EMBED Word.Picture.8  
Figure 19: Routing information interrogation procedure from AS
4.9.3.2	Attempted routing information interrogation procedures from AS
This measurement provides the number of routing information interrogations requests received from AS by the SLF.
CC.
On receipt by the SLF of a DH_SLF_QUERY message from AS via Dh interface (see 3GPP TS 23.228 [7]).
A single integer value.
RII.AttFromAS.
SLFFunction.
Valid for packet switched traffic.
IMS.
4.9.3.3	Successful routing information interrogation procedures from AS
This measurement provides the number of successful routing information interrogation responses sent to AS by the SLF. 
CC.
On transmission by the SLF of a DH_SLF_RESP message with the Result-Code AVP set to DIAMETER_REDIRECT_INDICATION to AS via Dh interface (see 3GPP TS 23.228 [7] and RFC 3588[15]).
A single integer value.
RII.SuccFromAS.
SLFFunction.
Valid for packet switched traffic.
IMS.
4.10	Measurements related to AS
4.10.1	Session control related measurements
4.10.1.1	IM CN originated session establishments
For the IM CN originated session establishments AS may act as terminating UA, redirect server, a SIP proxy, routeing B2BUA or initiating B2BUA. See 3GPP TS 24.229 [8] or 3GPP TS 23.228 [7]. The measurements defined in subclauses 4.10.1.1.1, 4.10.1.1.2 and 4.10.1.1.4 are subject to the "2 out of 3 approach".
4.10.1.1.1	Attempted IM CN originated session establishments
This measurement provides the number of attempted session establishments originated from the IM CN.
CC.
On receipt by the AS of an initial SIP_INVITE message from the IM CN (see 3GPP TS 23.228 [7]).
A single integer value.
SC.AttSessionImOrig.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.1.1.2	Successful IM CN originated session establishments
This measurement provides the number of successful session establishments originated from the IM CN.
CC.
On transmission by the AS of the first response message (e.g. SIP_180, SIP_200 or SIP_302 etc. relating with the role of the AS) indicating a successful IM CN originated session establishment corresponding to the initial SIP_INVITE message, each successful session establishment is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful IM CN originated session establishments.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionImOrig.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been sent for this session.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.1.1.3	Answered IM CN originated session establishments
This measurement provides the number of answered session establishments originated from the IM CN.
CC.
On transmission by the AS of a SIP_200_OK response message indicating an answered IM CN originated session establishment corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]).
A single integer value. 
SC.AnsSessionImOrig.
ASFunction.
Valid for packet switched traffic
IMS.

4.10.1.1.4	Failed IM CN originated session establishments
This measurement provides the number of failed session establishments originated from the IM CN. The measurement is split into subcounters per response status codes.
CC.
On transmission by the AS of a response message (e.g. SIP_430) indicating a failed session establishment originated from the IM CN corresponding to the initial SIP_INVITE messages (see 3GPP TS 23.228 [7]), each failed session establishment originated from the IM CN is added to the relevant measurement according to the status code. The sum of all supported per status code measurements shall equal the total number of failed session establishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form SC.FailSessionImOrig.Cause
where Cause identifies the status code.  (see 3GPP TS 24.229 [8] and RFC3261 [34])
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.1.2	AS originated session establishments
For the AS originated session establishments, AS may act as originating UA, routeing B2BUA or initiating B2BUA. See 3GPP TS 24.229 [8] or 3GPP TS 23.228[7]. The measurements defined in subclauses 4.10.1.2.1, 4.10.1.2.2 and 4.10.1.2.4 are subject to the "2 out of 3 approach".
4.10.1.2.1	Attempted AS originated session establishments
This measurement provides the number of attempted session establishments originated from the AS.
CC.
On transmission by the AS of an initial SIP_INVITE message indicating the AS originated session establishment, each initial SIP_INVITE message originated by the AS shall be counted as one attempted AS originated session establishment.
If the AS acts as originating UA, it initiates a session by sending a SIP_INVITE message.
If the AS acts as routeing B2BUA, it terminates the request from IM CN and initiates a new session by sending a SIP_INVITE message.
If the AS acts as initiating B2BUA, it may initiates two new sessions by sending two SIP_INVITE messages, or initiates one new session in the case of receiving the request from the IM CN and the new session is logically connected but unrelated to the incoming request (see 3GPP TS 24.229 [8]).
A single integer value.
SC.AttSessionAsOrig.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.1.2.2	Successful AS originated session establishments
This measurement provides the number of successful session establishments originated from the AS.
CC.
On receipt of the first response message (e.g. SIP_180, SIP_200, etc.) indicating a successful AS originated session establishment corresponding to the initial SIP_INVITE message originated by the AS, each successful session establishment is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful AS originated session establishments.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
SC.SuccSessionAsOrig.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.180	Message type: SIP_180
SC.SuccSession.200	Message type: SIP_200_OK only if the SIP_180 has not been received for this session.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2	Messaging service related measurements
4.10.2.1	Message related measurements, Page-Mode
4.10.2.1.1	Attempted incoming messages, Page-Mode
This measurement provides number of attempted incoming messages received by the messaging enabler with page-mode at the AS.
CC.
On receipt by the AS (messaging enabler) of an initial SIP_MESSAGE message (see 3GPP TS 23.228 [7]).
A single integer value.
MSG.AttIncMessagePM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2.1.2	Successful incoming messages, Page-Mode
This measurement provides number of successful incoming messages with page-mode at the AS.
CC.
On transmission by the AS (messaging enabler) of a response SIP_2XX message (see 3GPP TS 24.229 [8]) indicating the incoming message is successfully forwarded.
A single integer value.
MSG.SuccIncMessagePM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2.1.3	Attempted outgoing messages, Page-Mode
This measurement provides number of attempted outgoing messages transmitted by the messaging enabler with page-mode at the AS.
CC.
On transmission by the AS (messaging enabler) of a SIP_MESSAGE message (see 3GPP TS 23.228 [7]).
A single integer value.
MSG.AttOutMessagePM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2.1.4	Successful outgoing messages, Page-Mode
This measurement provides number of successful outgoing messages transmitted by the messaging enabler with page-mode at the AS.
CC.
On receipt by the AS (messaging enabler) of a response SIP_2XX message (see 3GPP TS 24.229 [8]) indicating the message transmitted by the AS is successfully processed.
A single integer value.
MSG.SuccOutMessagePM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2.2	Message related measurements, Session-Mode
4.10.2.2.1	Overview
The performance measurements defined in this subclause are related to message sending with session mode. The following procedure shows the session based messaging with an intermediate AS node. See 3GPP TS 23.228 [7].
 EMBED Visio.Drawing.6  
Figure 20: Session based messaging with an intermediate AS node scenario
4.10.2.2.2	Attempted messaging session establishments, Session Mode
This measurement provides number of attempted messaging session establishments for the two participants received by the messaging enabler with session-mode at the AS.
CC.
On receipt by the AS (messaging enabler) of an initial SIP_INVITE message initiated by a participant which requests to establish sessions just for the two participants for the messaging service (see 3GPP TS 29.228 [9]).
A single integer value.
MSG.AttSesssionSM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.2.2.3	Successful messaging session establishments, Session-Mode
This measurement provides number of successful messaging session establishments by the messaging enabler for the two participants with session-mode at the AS.
CC.
On transmission by the AS (messaging enabler) of a SIP_200_OK message indicating a successful messaging session establishment for the two participants of Messaging Service (see 3GPP TS 29.228 [9]).
A single integer value.
MSG.SuccSessionSM.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3	Conference service related measurements
4.10.3.1	Overview
The performance measurements defined in this subclause are related to the conference service (see 3GPP TS 24.147 [24]).
The following procedures are of interest for this purpose:
-	User creating a conference;
-	User joining a conference;
-	AS inviting a user to a conference;
-	User subscribing to the conference event package.
 EMBED Visio.Drawing.6  
Figure 21: User automatically creating a conference - MRFC/AS is located in user's home network
 EMBED Visio.Drawing.6  
Figure 22: User automatically creating a conference - MRFC/AS is not located in user's home network
 EMBED Visio.Drawing.6  
Figure 23: User calling into a conference - network MRFC/AS is not located in user's home network - conference URI resolved by the terminating home network
 EMBED Visio.Drawing.6  
Figure 24: User calling into a conference - MRFC/AS is not located in user's home network - conference URI can be resolved by the originating home network
 EMBED Visio.Drawing.6  
Figure 25: User inviting another user to a conference by sending a REFER request to MRFC/AS
 EMBED Visio.Drawing.6  
Figure 26: MRFC/AS inviting a user to a conference - MRFC/AS routes directly to I-CSCF
 EMBED Visio.Drawing.6  
Figure 27: MRFC/AS inviting another user to a conference by sending a REFER request to UE#2
 EMBED Visio.Drawing.6  
Figure 28: User subscribing to conference event package -
MRFC/AS is not located in user's home network
4.10.3.2	Attempted creations of conference
This measurement provides the number of attempted creations of conference.
CC.
On receipt by the Conference AS of a SIP_INVITE message to create the conference (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.AttCreation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.3	Successful creations of conference
This measurement provides the number of successful creations of conference.
CC.
On transmission by the Conference AS of a SIP_200_OK message indicating the conference is successfully created (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.SuccCreation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.4	Attempted joining of conference
This measurement provides the number of attempted joining of conference.
CC.
On receipt by the Conference AS of a SIP_INVITE message indicating the requests by the user to join the conference (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.AttJoining.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.5	Successful joining of conference
This measurement provides the number of successful joining of conference.
CC.
On transmission by the Conference AS of a SIP_200_OK message indicating the user has successfully joined the conference (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.SuccJoining.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.6	Attempted invitations for another user to join conference
This measurement provides the number of attempted invitations for another user to join conference.
CC.
On transmission by the Conference AS of a SIP_INVITE message to invite a user to join a conference (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.AttInvitation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.7	Successful invitations for another user to join conference
This measurement provides the number of successful invitations for another user to join conference.
CC.
On receipt by the Conference AS of a response message (e.g. SIP_183 or SIP_200_OK) indicating the invited user has successfully joined the conference (see 3GPP TS 24.147 [24]), each successful invitation is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful invitations. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
CONF.SuccInviJoinConf.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
CONF.SuccInvitation.183	Message type: SIP_183
CONF.SuccInvitation.200	Message type: SIP_200_OK only if the SIP_183 has not been received for this 	session.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.8	Attempted subscriptions for the conference event
This measurement provides the number of attempted subscriptions for the conference event.
CC.
On receipt by the Conference AS of SIP_SUBSCRIBE message initiated by the conference participant (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.AttSubscription
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.9	Successful subscriptions for the conference event
This measurement provides the number of successful subscriptions for the conference event.
CC.
On transmission by the AS of a SIP_200_OK message indicating the successful subscription for the conference event, corresponding the SIP_SUBCRIBE request message initiated by the conference participant (see 3GPP TS 24.147 [24]).
A single integer value.
CONF.SuccSubscription.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.10	Number of simultaneous online users (Maximum)
This measurement provides the maximum number of simultaneous online conference users.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online users on the conference and then taking the maximum.
A single integer value.
CONF.OnlineUserMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.11	Number of simultaneous online conferences (Maximum)
This measurement provides the maximum number of simultaneous online conferences.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online conferences and then taking the maximum.
A single integer value.
CONF.OnlineConfMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.12	Number of simultaneous online users (Mean)
This measurement provides the mean number of simultaneous online users.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online users on the conference and then taking the arithmetic mean.
A single integer value.
CONF.OnlineUserMean.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.3.13	Number of simultaneous online conferences (Mean)
This measurement provides the mean number of simultaneous online conferences.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online conferences and then taking the arithmetic mean.
A single integer value.
CONF.OnlineConfMean.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4	Presence service related measurements
4.10.4.1	Number of simultaneous online watchers (Maximum)
This measurement provides the maximum number of simultaneous online watchers at the presence enabler/AS.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online watchers which have been registered and then taking the maximum.
A single integer value.
PRES.OnlineWatcherMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.2	Number of simultaneous online presentities (Maximum)
This measurement provides the maximum number of simultaneous online presentities in the presence enabler/AS.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online presentities which have been registered and then taking the maximum.
A single integer value.
PRES.OnlinePresentityMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.3	Number of simultaneous online watchers (Mean)
This measurement provides the number of mean number of simultaneous online watchers in the presence enabler/AS.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online watchers which have been registered and then taking the arithmetic mean.
A single integer value.
PRES.MeanOnlineWatcher.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.4	Number of simultaneous online presentities (Mean)
This measurement provides the number of mean number of simultaneous online presentities in the presence enabler/AS.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online presentities which have been registered and then taking the arithmetic mean.
A single integer value.
PRES.MeanOnlinePresentity.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.5	Attempted subscriptions for presence
This measurement provides the number of attempted subscriptions received by the presence enabler/AS.
CC.
On receipt by the AS (presence enabler) of a SIP_SUBSCRIBE message (see 3GPP TS 23.141[25]).
A single integer value.
PRES.AttSubscribe.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.6	Successful subscriptions for presence
This measurement provides the number of successful subscriptions at the presence enabler/AS.
CC.
On transmission by the AS (presence enabler) of a response message (e.g. SIP_200_OK or SIP_202_Accepted) for the subscription request from the IM CN (See 3GPP TS 23.141 [25]), each successful subscription is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful subscriptions. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
PRES.SuccSubscribe. type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
SC.SuccSession.200	Message type: SIP_200_OK
SC.SuccSession.202	Message type: SIP_202 only if the SIP_200_OK has not been sent for this session.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.7	Attempted notifications for presence
This measurement provides the number of attempted notifications sent by the presence enabler/AS.
CC.
On transmission by the AS (presence enabler) of a SIP_NOTIFY message to the IM CN (see 3GPP TS 23.141 [25]).
A single integer value.
PRES.AttNotify.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.8	Successful notifications for presence
This measurement provides the number of successful notifications send by the presence enabler/AS.
CC.
On receipt by the AS (presence enabler) of a SIP_200_OK message indicating the successful notification corresponding to the SIP_NOTIFY message sent by the AS (see 3GPP TS 23.141 [25]).
A single integer value.
PRES.SuccNotify.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.9	Attempted publications for presence
This measurement provides the number of attempted publications received by the presence enabler/AS.
CC.
On receipt by the AS (presence enabler) of a SIP_PUBLISH message (see 3GPP TS 23.141 [25]).
A single integer value.
PRES.AttPublish.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.4.10	Successful publications for presence
This measurement provides the number of successful publications at the presence enabler/AS.
CC.
On transmission by the AS (presence enabler) of a SIP_200_OK message indicating the successful publication, corresponding to received SIP_PUBLISH message (see 3GPP TS 23.141 [25]).
A single integer value.
PRES.SuccPub.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5	PoC service related measurements
4.10.5.1	Attempted creations of PoC session
This measurement provides the number of attempted creations of PoC session.
CC.
On receipt by the PoC AS of SIP_INVITE message for creation of PoC session (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.AttCreation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.2	Successful creations of PoC session
This measurement provides the number of successful creation ofPoC session.
CC.
On transmission by the PoC AS of a SIP_200_OK message indicating the PoC session is successfully created (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.SuccCreation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.3	Attempted joining of PoC session
This measurement provides the number of attempted joining PoC session requests which means that the user calls into the PoC session.
CC.
On receipt by the PoC AS of PoC session SIP_INVITE message indicating the requests by the user to join the PoC session (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.AttJoining.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.4	Successful joining of PoC session
This measurement provides the number of successful joining of PoC session.
CC.
On transmission by the PoC AS of a SIP_200_OK message indicating the user has successfully joined the PoC session (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.SuccJoining.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.5	Attempted invitations for another user to join PoC session
This measurement provides the number of attempted invitations for another user to join PoC session.
CC.
On transmission by the PoC AS of a SIP_INVITE message to invite a user to join a PoC session (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.AttInvitation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.6	Successful invitations for another user to join PoC session
This measurement provides the number of successful invitations for another user to join PoC session.
CC.
On receipt by the PoC AS of a SIP_200_OK message indicating the invited user has successfully joined the PoC session (see 3GPP TR 23.979 [26]).
A single integer value.
PoC.SuccInvitation.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.7	Number of simultaneous online users (Maximum)
This measurement provides the maximum number of simultaneous online PoC users.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online users that have been joined and then taking the maximum.
A single integer value.
PoC.OnlineUserMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.5.8	Number of simultaneous online PoC session (Maximum)
This measurement provides the maximum number of simultaneous online PoC sessions.
SI.
This measurement is obtained by sampling at a pre-defined interval the number of simultaneous online PoC sessions and then taking the maximum.
A single integer value.
PoC.OnlineSessionMax.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6	Measurements related to XDM Enabler
4.10.6.1	XCAP operation related measurements 
4.10.6.1.1	Overview
The performance measurements defined in this subclause are related to the XCAP operation request from the XDMC for document manipulation (e.g. retrieving/adding/deleting elements/attributes, etc.) stored in XDMS. See "XML Document Management (XDM) Specification", OMA-TS-XDM_Core-V1_0 [27].
The procedures are shown in figure 29.
 EMBED Visio.Drawing.11  
Figure 29: XCAP operation request procedures
4.10.6.1.2	Attempted HTTP PUT procedures
This measurement provides the number of attempted HTTP PUT procedures.
CC.
On receipt by the XDMS of a HTTP_PUT request from the aggregation proxy (see OMA-TS-XDM_Core-V1_0 [27]).
A single integer value.
XDM.AttHttpPut.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.1.3	Successful HTTP PUT procedures
This measurement provides the number of successful HTTP PUT procedures.
CC.
On transmission by the XDMS of a response message (e.g. HTTP_200_OK) indicating a successful HTTP PUT procedure, each successful HTTP PUT procedure is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful HTTP PUT procedures. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
XDM.SuccHttpPut.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
XDM.SuccHttpPut.200	Message type: SIP_200_OK.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.1.4	Attempted HTTP GET procedures
This measurement provides the number of attempted HTTP GET procedures.
CC.
On receipt by the XDMS of a HTTP_GET request from the aggregation proxy (See OMA-TS-XDM_Core-V1_0 [27]).
A single integer value.
 XDM.AttHttpGet.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.1.5	Successful HTTP GET procedures
This measurement provides the number of successful HTTP GET procedures.
CC.
On transmission by the XDMS of a response message (e.g. HTTP_200_OK) indicating a successful HTTP GET procedure, each successful HTTP GET procedure is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful HTTP GET procedures. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
XDM.SuccHttpGet.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
XDM.SuccHttpGet.200	Message type: SIP_200_OK.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.1.6	Attempted HTTP DELETE procedures
This measurement provides the number of attempted HTTP DELETE procedures.
CC.
On receipt by the XDMS of a HTTP_ DELETE request from the aggregation proxy (see OMA‑TS‑XDM_Core‑V1_0 [27]).
A single integer value.
 XDM.AttHttpDel.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.1.7	Successful HTTP DELETE procedures
This measurement provides the number of successful HTTP DELETE procedures.
CC.
On transmission by the XDMS of a response message (e.g. HTTP_200_OK) indicating a successful HTTP DELETE procedure, each successful HTTP DELETE procedure is added to the relevant measurement according to the message type, the possible response message types are identified in 3GPP TS 24.229 [8]. The sum of all supported per message type measurements shall equal the total number of successful HTTP DELETE procedures. In case only a subset of per message type measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of message types plus a possible sum value identified by the .sum suffix.
XDM.SuccHttpDel.type
where type identifies the message type.
The following subcounters with specific message types are the samples of this measurement:
XDM.SuccHttpDel.200	Message type: SIP_200_OK.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.2	SIP related measurements
4.10.6.2.1	Overview
The performance measurements defined in this subclause are related to SIP procedures for subscribing and notifying the changes in the XML documents stored in the XDMS. See "XML Document Management (XDM) Specification", OMA‑TS-XDM_Core-V1_0 [27].
The procedures are shown in figure 30.

Figure 30: XDM Client subscribes to changes in XDMS Procedures
4.10.6.2.2	Attempted Subscription procedures
This measurement provides the number of attempted subscription procedures.
CC.
On receipt by the XDMS of a SIP_SUBSCRIBE message (See OMA-TS-XDM_Core-V1_0 [27]).
A single integer value.
XDM.AttSubscibe.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.2.3	Successful Subscription procedures
This measurement provides the number of successful subscription procedures.
CC.
On transmission by the XDMS of a response SIP_200_OK message indicating a successful subscription procedure (see OMA-TS-XDM_Core-V1_0 [27]).
A single integer value.
XDM.SuccSubscribe.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.2.4	Attempted Notification procedures
This measurement provides the number of attempted notification procedures.
CC.
On sending by the XDMS of a SIP_NOTIFY message (see OMA-TS-XDM_Core-V1_0 [27]).
A single integer value.
XDM.AttNotify.
ASFunction.
Valid for packet switched traffic.
IMS.
4.10.6.2.5	Successful Notification procedures
This measurement provides the number of successful notification procedures.
CC.
On receipt by the XDMS of a response SIP_200_OK message indicating the successful XDMS originated notification procedures.
A single integer value.
XDM.SuccNotify.
ASFunction.
Valid for packet switched traffic.
IMS.
4.11	Measurements related to IBCF
Editor's note: IBCFFunction used in following text is a subject for further study of IMS NRM modelling for R8 requirements and will align with IMS NRM defined in 3GPP TS 32.732 [30].
4.11.1	Attempted session establishments from users of other network domains
This measurement provides the number of attempted session establishments originated from the users (regardless of whether the user is roaming or not) who are belonging to other network domains at the IBCF in the terminating network. The measurement is split into subcounters per network domain. 
CC.
On receipt by the IBCF of a SIP_ INVITE message, and the calling party is belonging to other network domains (i.e. the domain name information of the calling party retrieved from the SIP_INVITE message is different from the domain of this IBCF). Each session whose calling party recognized by the IBCF as belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of attempted session establishments from users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IDS.AttSessionFromOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
IBCFFunction.
Valid for packet switched traffic.
IMS. 
4.11.2	403 (Forbidden) generated for sessions from users of other network domains
This measurement provides the number of SIP_403 (Forbidden) response messages at the IBCF in the terminating network generated for the sessions from users of other network domains. The measurement is split into subcounters per network domain. 
CC.
On transmission by the IBCF of SIP_403 message corresponding to the SIP_ INVITE message of which the calling party is belonging to other network domains received by the IBCF. Each SIP_403 message generated by the IBCF for the session whose calling party is belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of 403 (Forbidden) generated for sessions from users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IDS.403SessionFromOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
IBCFFunction.
Valid for packet switched traffic.
IMS.
4.11.3	Attempted session establishments to users of other network domains
This measurement provides the number of attempted session establishments towards users (regardless of whether the user is roaming or not) who are belonging to other network domains at the IBCF in the originating network. The measurement is split into subcounters per network domain. 
CC.
On transmission by the IBCF of a SIP_ INVITE messages, and the called party is belonging to other network domains (i.e. the domain name information of the called party retrieved from the SIP_INVITE message is different from the domain of this IBCF). Each session whose called party recognized by the IBCF as belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network measurements shall equal the total number of attempted session establishments to users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IDS.AttSessionToOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
IBCFFunction.
Valid for packet switched traffic.
IMS.
4.11.4	403 (Forbidden) received for sessions to users of other network domains
This measurement provides the number of SIP_403 (Forbidden) response messages received for sessions to users of other network domains at the IBCF in the originating network. The measurement is split into subcounters per network domain. 
CC.
On receipt by the IBCF of SIP_403 message corresponding to the SIP_ INVITE message of which the called party is belonging to other network domains transmitted by the IBCF. Each SIP_403 message received by the IBCF for the session whose called party is belonging to a given network domain is added to the relevant per network domain measurement. The sum of all supported per network domain measurements shall equal the total number of 403 (Forbidden) received for sessions to users of other network domains. In case only a subset of per network measurements is supported, a sum subcounter will be provided first (see 3GPP TS 23.228 [7]).
Each measurement is an integer value. The number of measurements is equal to the number of network domain plus a possible sum value identified by the .sum suffix.
The measurement name has the form IDS.403SessionToOtherNtwkDmn.Domain
where Domain identifies the network domain, and it is in the format of the domain name information in the SIP messages.
IBCFFunction
Valid for packet switched traffic.
IMS.

5	Equipment related measurements
The measurements defined in this subclause are related to the equipment aspect performance. The measurements defined in the following subclauses are common for all of the equipments in IMS and shall be applied to all of the network elements in IMS.
5.1	Processor usage
5.1.1	Mean processor usage
This measurement provides the mean usage of each key processor during the granularity period. Each equipment may have more than one key processors, the measurement is split into subcounters per key processor.
SI.
This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking the arithmetic mean for each key processor.
Each measurement is an integer value (Unit: %).
The measurement name has the form EQPT.MeanProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
ManagedElement.
Valid for circuit switched and packet switched traffic.
IMS.
5.1.2	Peak processor usage
This measurement provides the peak usage of each key processor during the granularity period. Each equipment may have more than one key processors, the measurement is split into subcounters per key processor.
SI.
This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking the maximum for each key processor.
Each measurement is an integer value (Unit: %).
The measurement name has the form EQPT.PeakProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
ManagedElement.
Valid for circuit switched and packet switched traffic.
IMS.
Annex A (normative):
Use case of Immediate Messaging procedure related measurements at CSCF
IMS users shall be able to exchange immediate messages with each other by using the Immediate Messaging procedure. CSCF may delivery successfully the immediate messages, also may refuse the immediate messages or respond to the sender with fail indications.If the Immediate Messaging procedure at CSCF is fail, the users’ subjective feel to the network will be bad.So it is necessary to define Immediate Messaging procedure related measurements for operator to evaluate the rate of success and failure at CSCF in IMS network.
Annex B (informative):
Use case of IP-CAN Session Establishment related measurements 
IP-CAN session is a main procedure in policy and charging control architecture (see 3GPP TS 29.213 [33]). If IP-CAN session establishment is failed, it means that PCEF cannot get PCC rules from PCRF and PCEF shall reject the attempt for UE-initiated resource request. So it is necessary to define IP-CAN session establishment related measurements to monitor or evaluate session performance of PCC procedures.
Annex C (informative):
Change history
Change history
DateTSG #TSG Doc.CRRevSubject/CommentCatOldNewMar 2007SP-35SP-070067----Submitted to SA#35 for for Information----1.0.0Mar 2007--------Editorial clean-up --1.0.01.0.1May 2007SP-36SP-070287----Submitted to SA#36 for Approval--2.0.07.0.0Sep 2007SP-37SP-0706130001--Update IMS Performance Measurements With Missing Granularity And Incorrect CC Performance Measurement TypesF7.0.07.1.0Sep 2007SP-37SP-0706140002--Add performance measurements on SIP subscription and notificationB7.1.08.0.0Mar 2008SP-39SP-0800580006--Correction to the registration measurements in CSCFA8.0.08.1.0Mar 2008SP-39SP-0800690003--Correction of BGCF related measurements - Align with 23.228F8.0.08.1.0Mar 2008SP-39SP-0800690004--Add registration related measurement per access technologyB8.0.08.1.0Dec 2008SP-42SP-0808450008--Correction of de-registration related measurementsA8.1.08.2.0Dec 2008SP-42SP-0808460009--Add IBCF related measurementsB8.1.08.2.0Sep 2009SP-45SP-0905340010--Correction of measurement names for RTP related measurementsF8.2.08.3.0Sep 2009SP-45SP-0905340013--Correction measurements related to PDF - align with 29.213F8.2.08.3.0Sep 2009SP-45SP-0906270011--Addition of Immediate Messaging related measurementsB8.3.09.0.0Sep 2009SP-45SP-0906270012--Addition of PCRF IP-CAN Session Establishment related measurementsB8.3.09.0.0Dec 2009SP-46SP-0907190014--Addition of AS Session control related measurementsB9.0.09.1.0Apr 2010--------Addition of missing change history--9.1.09.1.1Mar 2011SP-51SP-1100940025--Correct measurements object classes - Align with 32.732 IMS NRM IRP Information ServiceF9.1.19.2.0








 STYLEREF ZA 3GPP TS 32.409 V9.2.0 (2011-03)
 PAGE 3
 STYLEREF ZGSM Release 9

3GPP