ÐÏࡱá > þÿ : c þÿÿÿ 5 6 7 8 9 ó € ô ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿì¥Á '` ø¿ áá bjbj{P{P tL : : ô× m ÿÿ ÿÿ ÿÿ ¤ 4( 4( 4( 4( `( `( `( $ ‚+ D^ Ö Ö Ö P & Ä ê ä Ɖ ‘n ‚ Ú – p
: ª
ª
ª
½
Ç Ô › l øm úm úm úm úm úm úm $ r h {t ¸ n - `( ê ¹ ½ ê ê n 4( 4( ª
ª
Kn * * * ê t 4( ª
`( ª
øm * ê øm * * [ % R( `( Ð` ª
Î àÁð‡üËÊ Ö ^# 4^ @ ta „ an 0 ‘n t^ \ 3u p' n 3u | Ð` 3u `( Ð` ¤ " ) * A U • n n Þ) . ‘n ê ê ê ê Ɖ ¤ jŠ ¤ Œ ¿ K Ä· Ɖ jŠ Œ K „( Ô X* & ~+ 4( 4( 4( 4( 4( 4( ÿÿÿÿ 3GPP TS 32.307 V8.2.0 (2010-03)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Telecommunication management;
Configuration Management (CM);
Notification Integration Reference Point (IRP);
SOAP Solution Set (SS)
(Release 8)
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
UMTS, management, SOAP
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.
© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
U M T S "! i s a T r a d e M a r k o f E T S I r e g i s t e r e d f o r t h e b e n e f i t o f i t s m e m b e r s
3 G P P "! i s a T r a d e M a r k o f E T S I r e g i s t e r e d f o r t h e b e n e f i t o f i t s M e m b e r s a n d o f t h e 3 G P P O r g a n i z a t i o n a l P a r t n e r s L T E "! i s a T r a d e M a r k o f E T S I c u r r e n t l y b e i n g r e g i s t e r e d f o r t h e b e n e f i t 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 _Toc257275778 \h 5
Introduction PAGEREF _Toc257275779 \h 5
1 Scope PAGEREF _Toc257275780 \h 7
2 References PAGEREF _Toc257275781 \h 7
3 Definitions and abbreviations PAGEREF _Toc257275782 \h 8
3.1 Definitions PAGEREF _Toc257275783 \h 8
3.2 Abbreviations PAGEREF _Toc257275784 \h 8
4 Architectural features PAGEREF _Toc257275785 \h 8
5 Mapping PAGEREF _Toc257275786 \h 10
5.1 Operation mapping PAGEREF _Toc257275787 \h 10
5.2 Filter language PAGEREF _Toc257275788 \h 10
5.3 Common datatype definition PAGEREF _Toc257275789 \h 10
5.3.1 NotificationCategorySetType PAGEREF _Toc257275790 \h 10
5.3.2 SubscriptionStateType PAGEREF _Toc257275791 \h 10
5.4 Operation parameter mapping PAGEREF _Toc257275792 \h 11
5.4.1 Operation subscribe PAGEREF _Toc257275793 \h 11
5.4.1.1 Input parameters PAGEREF _Toc257275794 \h 11
5.4.1.2 Output parameters PAGEREF _Toc257275795 \h 11
5.4.1.3 Fault definition PAGEREF _Toc257275796 \h 11
5.4.2 Operation unsubscribe PAGEREF _Toc257275797 \h 12
5.4.2.1 Input parameters PAGEREF _Toc257275798 \h 12
5.4.2.2 Output parameters PAGEREF _Toc257275799 \h 12
5.4.2.3 Fault definition PAGEREF _Toc257275800 \h 12
5.4.3 Operation getSubscriptionIds PAGEREF _Toc257275801 \h 13
5.4.3.1 Input parameters PAGEREF _Toc257275802 \h 13
5.4.3.2 Output parameters PAGEREF _Toc257275803 \h 13
5.4.3.3 Fault definition PAGEREF _Toc257275804 \h 13
5.4.4 Operation getSubscriptionStatus PAGEREF _Toc257275805 \h 14
5.4.4.1 Input parameters PAGEREF _Toc257275806 \h 14
5.4.4.2 Output parameters PAGEREF _Toc257275807 \h 14
5.4.4.3 Fault definition PAGEREF _Toc257275808 \h 14
5.4.5 Operation changeSubscriptionFilter PAGEREF _Toc257275809 \h 15
5.4.5.1 Input parameters PAGEREF _Toc257275810 \h 15
5.4.5.2 Output parameters PAGEREF _Toc257275811 \h 15
5.4.5.3 Fault definition PAGEREF _Toc257275812 \h 15
5.4.6 Operation suspendSubscription PAGEREF _Toc257275813 \h 15
5.4.6.1 Input parameters PAGEREF _Toc257275814 \h 15
5.4.6.2 Output parameters PAGEREF _Toc257275815 \h 16
5.4.6.3 Fault definition PAGEREF _Toc257275816 \h 16
5.4.7 Operation resumeSubscription PAGEREF _Toc257275817 \h 16
5.4.7.1 Input parameters PAGEREF _Toc257275818 \h 16
5.4.7.2 Output parameters PAGEREF _Toc257275819 \h 16
5.4.7.3 Fault definition PAGEREF _Toc257275820 \h 17
5.4.8 Operation getNotificationCategories PAGEREF _Toc257275821 \h 17
5.4.8.1 Input parameters PAGEREF _Toc257275822 \h 17
5.4.8.2 Output parameters PAGEREF _Toc257275823 \h 17
5.4.8.3 Fault definition PAGEREF _Toc257275824 \h 17
5.5 Parameter mapping PAGEREF _Toc257275825 \h 17
5.6 NotificationIRPNotification Interface definition PAGEREF _Toc257275826 \h 18
5.6.1 Input parameters PAGEREF _Toc257275827 \h 18
5.6.2 Output parameters PAGEREF _Toc257275828 \h 18
6 IRPAgent's Behaviour PAGEREF _Toc257275829 \h 18
6.1 Subscription PAGEREF _Toc257275830 \h 18
Annex A (normative): WSDL specifications PAGEREF _Toc257275831 \h 19
Annex B (normative): Notification WSDL specifications PAGEREF _Toc257275832 \h 27
Annex C (informative): Notification IRP WSDL/XML schema electronic files PAGEREF _Toc257275833 \h 28
Annex D (informative): Change history PAGEREF _Toc257275834 \h 29
Foreword
This Technical Specification (TS) 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:
32.301: Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements
32.302: Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)
32.303: Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
32.305: Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition
32.307: Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs.
The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [6] and 3GPP TS 32.102 [7].
Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in 3GPP TS 32.111-2 Alarm IRP: Information Service [5], is one possible kind of event, an object creation as specified in 3GPP TS 32.602 Basic CM IRP: Information Service [15] is another possible kind of event.
Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to IRPAgent for receiving notifications.
This IRP bases its design on work captured in ITU-T Recommendation X.734 [2], The central design ideas are:
Separation of notification Consumers (IRPManagers) from Producers (IRPAgents);
Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications.
Common characteristics related to notifications in all other IRPs are gathered in one IRP.
1 Scope
The present document specifies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [4]).
This Solution Set specification is related to 3GPP TS 32.302 V8.0.X.
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, edition number, version number, etc.) nonspecific.
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] ITU-T Recommendation X.736: "Information technology - Open Systems Interconnection - Systems Management: Security alarm reporting function".
[2] ITU-T Recommendation X.734 (1992): "Information technology - Open Systems Interconnection - Systems management: Event report management function".
[3] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
[4] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
[5] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
[6] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[7] 3GPP TS 32.102: "Telecommunication management; Architecture".
[8] 3GPP TS 32.301: "Telecommunication Management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements".
[9] 3GPP TS 32.317: "Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solution set".
[10] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
[11] 3GPP TS 32.172: "Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service".
[12] W3C SOAP 1.1 specification ( HYPERLINK "http://www.w3.org/TR/2000/NOTE-SOAP-20000508/" http://www.w3.org/TR/2000/NOTE-SOAP-20000508/)
[13] W3C XPath 1.0 specification (HYPERLINK "http://www.w3.org/TR/1999/REC-xpath-19991116"http://www.w3.org/TR/1999/REC-xpath-19991116)
[14] W3C WSDL 1.1 specification (HYPERLINK "http://www.w3.org/TR/wsdl"HYPERLINK "http://www.w3.org/TR/2001/NOTE-wsdl-20010315"http://www.w3.org/TR/2001/NOTE-wsdl-20010315)
[15] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
[16] 3GPP TS 32.305: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition".
[17] WS-I Basic Profile Version 1.1 ( HYPERLINK "http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html" http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html)
[18] W3C SOAP 1.2 specification ( HYPERLINK "http://www.w3.org/TR/soap12-part1/" http://www.w3.org/TR/soap12-part1/)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [6], 3GPP TS 32.102 [7] and 3GPP TS 32.301 [8] and the following apply:
IRP document version number string (or "IRPVersion"): See 3GPP TS 32.311 [10].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CM Configuration Management
EM Element Manager
IS Information Service
NE Network Element
NV Name and Value pair
QoS Quality of Service
SS Solution Set
WSDL Web Service Description Language
WS-I Web Services Interoperability Organization
4 Architectural features
The overall architectural feature of Notification IRP is specified in 3GPP TS 32.302 [4]. This clause specifies features that are specific to the SOAP solution set.
The SOAP 1.1 specification [12] and WSDL 1.1 specification [14] are supported.
The SOAP 1.2 specification [18] is supported optionally.
This specification uses "document" style in WSDL file.
This specification uses "literal" encoding style in WSDL file.
The IRPAgent shall support the push interface model that means IRPAgent sends notifications to IRPManager as soon as new events occur. IRPManager does not need to check ("pull") for events.
The “Notification” definition is imported from Notification IRP XML Definition [16].
This specification uses a number of namespace prefixes throughout that are listed in Table 4.1.
Table 4.1: Prefixes and Namespaces used in this specification
PREFIXNAMESPACEhttphttp://schemas.xmlsoap.org/wsdl/http/soaphttp://schemas.xmlsoap.org/wsdl/soap/SOAP-ENVhttp://schemas.xmlsoap.org/soap/envelope/SOAP-ENC or soapenchttp://schemas.xmlsoap.org/soap/encoding/xs or xsdhttp://www.w3.org/2001/XMLSchemaxsihttp://www.w3.org/2001/XMLSchema-instancentfIRPSystemhttp://www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/NotificationIRPSystemntfIRPDatahttp://www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/NotificationIRPDatantfIRPNtfSystemhttp://www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfSystemntfIRPNtfDatahttp://www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfDatagenericIRPSystemhttp://www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem
The WSDL structure is like Figure 4.1:
Figure 4.1: Notification IRP SOAP Solution Set WSDL structure
Figure 4.2: Notification IRP SOAP Solution Set Notification WSDL structure
5 Mapping
5.1 Operation mapping
Notification IRP: IS (3GPP TS 32.302 [5]) defines semantics of operations visible across this IRP. These operations are the operations of the IOCs defined in 3GPP TS 32.302 [5].
Table 5.1 maps the operations defined in Notification IRP: IS (3GPP TS 32.302 [5]) to their equivalents (methods) in this Solution Set (SS). Specifically, the table 5.1 maps the operations of the IOCs defined in 3GPP TS 32.302 [5] to their equivalents in this SS. Since one of the IOCs, the NotificationIRP IOC, inherits from the ManagedGenericIRP IOC [4], the table 5.1 also maps the operations of ManagedGenericIRP IOC to their equivalents (methods) in this SS.
Table 5.1 also qualifies if a method is Mandatory (M) or Optional (O).
Table 5.1: Mapping from IS Operation to SS Equivalents
IS Operations in 3GPP TS 32.302 [5] SS OperationsQualifiersubscribesubscribeMunsubscribeunsubscribeMgetSubscriptionIdsgetSubscriptionIdsOgetSubscriptionStatusgetSubscriptionStatusOchangeSubscriptionFilterchangeSubscriptionFilterOsuspendSubscriptionsuspendSubscriptionOresumeSubscriptionresumeSubscriptionOgetNotificationCategoriesgetNotificationCategoriesOgetIRPVersion (see note.)getIRPVersionMgetOperationProfile (see note.)getOperationProfileOgetNotificationProfile (see note.)getNotificationProfileONOTE: These 3 operations are operations of ManagedGenericIRP IOC specified in 3GPP TS 32.312 [4]. The NotificationIRP IOC of 3GPP TS 32.302 [5] inherits from it.
5.2 Filter language
The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [13]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex.
5.3 Common datatype definition
5.3.1 NotificationCategorySetType
5.3.2 SubscriptionStateType
5.4 Operation parameter mapping
3GPP TS 32.302 [5] defines semantics of parameters carried in operations across the Notification IRP. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
5.4.1 Operation subscribe
5.4.1.1 Input parameters
Table 5.4.1.1: Mapping from IS subscribe input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiermanagerReferenceanyURI managerReferenceMtimeTicklong timeTickOnotificationCategoriesntfIRPData:NotificationCategorySetType notificationCategoriesOfilterstring filter (see note 1)OanyURI ntfTransServiceNS (see note 2)MNOTE1: The grammar of the filter string is XPath defined by W3C XPath 1.0 specification [12].
NOTE2: This parameter is used to specify the name space of the Web Notification Transmission Service that will be used for sending notification. The “http://www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification” URIshould be supported.
Here is the XML schema fragment of the subscribe request:
5.4.1.2 Output parameters
Table 5.4.1.2: Mapping from IS subscribe output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdstring subscriptionIdMstatusntfIRPData:subscribeFaultM
Here is the XML schema fragment of the subscribe response:
5.4.1.3 Fault definition
5.4.2 Operation unsubscribe
5.4.2.1 Input parameters
Table 5.4.2.1: Mapping from IS unsubscribe input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiermanagerReferenceanyURI managerReferenceMsubscriptionIdstring subscriptionIdO
Here is the XML schema fragment of the unsubscribe request:
5.4.2.2 Output parameters
Table 5.4.2.2: Mapping from IS unsubscribe output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifierStatusntfIRPData:unsubscribeFaultM
Here is the XML schema fragment of the unsubscribe response:
5.4.2.3 Fault definition
5.4.3 Operation getSubscriptionIds
5.4.3.1 Input parameters
Table 5.4.3.1: Mapping from IS getSubscriptionIds input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiermanagerReferenceanyURI managerReferenceM
Here is the XML schema fragment of the getSubscriptionIds request:
5.4.3.2 Output parameters
Table 5.4.3.2: Mapping from IS getSubscriptionIds output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdSetsequence of string subscriptionIdSetMstatusntfIRPData:getSubscriptionIdsFaultM
Here is the XML schema fragment of the getSubscriptionIds response:
5.4.3.3 Fault definition
5.4.4 Operation getSubscriptionStatus
5.4.4.1 Input parameters
Table 5.4.4.1: Mapping from IS getSubscriptionStatus input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdstring subscriptionIdM
Here is the XML schema fragment of the getSubscriptionStatus request:
5.4.4.2 Output parameters
Table 5.4.4.2: Mapping from IS getSubscriptionStatus output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiernotificationCategoriesntfIRPData:NotificationCategorySetType notificationCategoriesCfilterInEffectstring filterInEffect (see note)OSubscriptionStatentfIRPData:SubscriptionStateType SubscriptionStateOtimeTicklong timeTickOstatusntfIRPData:getSubscriptionStatusFaultMNOTE: The grammar of the filter string is XPath defined by W3C XPath 1.0 specification [12].
Here is the XML schema fragment of the getSubscriptionStatus response:
5.4.4.3 Fault definition
5.4.5 Operation changeSubscriptionFilter
5.4.5.1 Input parameters
Table 5.4.5.1: Mapping from IS changeSubscriptionFilter input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdstring subscriptionIdMfilterstring filter (see note)ONOTE: The grammar of the filter string is XPath defined by W3C XPath 1.0 specification [12].
Here is the XML schema fragment of the changeSubscriptionFilter request:
5.4.5.2 Output parameters
Table 5.4.5.2: Mapping from IS changeSubscriptionFilter output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifierstatusntfIRPData: changeSubscriptionFilterFaultM
Here is the XML schema fragment of the changeSubscriptionFilter response:
5.4.5.3 Fault definition
5.4.6 Operation suspendSubscription
5.4.6.1 Input parameters
Table 5.4.6.1: Mapping from IS suspendSubscription input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdstring subscriptionIdM
Here is the XML schema fragment of the suspendSubscription request:
5.4.6.2 Output parameters
Table 5.4.6.2: Mapping from IS suspendSubscription output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifierstatusntfIRPData:suspendSubscriptionFaultM
Here is the XML schema fragment of the suspendSubscription response:
5.4.6.3 Fault definition
5.4.7 Operation resumeSubscription
5.4.7.1 Input parameters
Table 5.4.7.1: Mapping from IS resumeSubscription input parameters to SS equivalents
IS Operation parameterSS Method parameterQualifiersubscriptionIdstring subscriptionIdM
Here is the XML schema fragment of the resumeSubscription request:
5.4.7.2 Output parameters
Table 5.4.7.2: Mapping from IS resumeSubscription output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifierstatusntfIRPData:resumeSubscriptionFaultM
Here is the XML schema fragment of the resumeSubscription response:
5.4.7.3 Fault definition
5.4.8 Operation getNotificationCategories
5.4.8.1 Input parameters
None.
Here is the XML schema fragment of the getNotificationCategories request:
5.4.8.2 Output parameters
Table 5.4.8.2: Mapping from IS getNotificationCategories output parameters to SS equivalents
IS Operation parameterSS Method parameterQualifierNotificationCategoryListntfIRPData:NotificationCategorySetType NotificationCategoryListMstatusntfIRPData:getNotificationCategoriesFaultM
Here is the XML schema fragment of the getNotificationCategories response:
5.4.8.3 Fault definition
5.5 Parameter mapping
Notification IRP: IS (3GPP TS 32.302 [5]) defines the semantics of common attributes carried in notifications. This SS does not provide the mapping of these attributes to their SOAP SS equivalents. Other IRPs such as Alarm IRP: IS (3GPP TS 32.111-2 [6]) identify and qualify these common attributes for use in their environment. Their corresponding SS documents define the mapping of these attributes to their SS equivalents.
5.6 NotificationIRPNotification Interface definition
The operation name is defined as “notify”.
5.6.1 Input parameters
Table 5.6.1: notify input parameters
IS Operation parameterSS Method parameterQualifier-xe:Notification notificationM
The notifications of the various IRPs extend the input parameter above.
Here is the XML schema fragment of the notify request:
5.6.2 Output parameters
None.
6 IRPAgent's Behaviour
This clause describes some IRPAgent's behaviour not captured by WSDL.
6.1 Subscription
IRPManager can invoke multiple subscribe operation using different managerReference(s). As far as IRPAgent is concerned, the IRPAgent will emit notifications to multiple "places" with their independent filter requirements. IRPAgent will not know if the notifications are going to the same IRPManager.
If IRPManager invokes multiple subscribe using the same managerReference and with an already subscribed notificationCategory, IRPAgent shall raise AlreadySubscribedFault fault to all invocations except one.
IRPManager can invoke multiple subscribe using the same managerReference and with one or more not-yet-subscribed notificationCategories. In this case, if IRPAgent supports all the notification categories requested, IRPAgent shall accept the invocation; otherwise, it raises AtLeastOneNotificationCategoryNotSupportedFault fault.
Annex A (normative):WSDL specifications
Annex B (normative):Notification WSDL specifications
Annex C (informative):Notification IRP WSDL/XML schema electronic files
The electronic files corresponding to the normative WSDL/XML schema defined in the present document are available in native form in the following archive:
http://www.3gpp.org/ftp/Specs/archive/32_series/32307/schema/32307-820-wsdl.zip
Annex D (informative):Change history
Change historyDateTSG #TSG Doc.CRRSubject/CommentCatOldNewMar 2006SA_31SP-060096----Submitted to TSG SA#31 for Information--1.0.0Dec 2006SA_34SP-060740----Submitted to TSG SA#34 for Approval--2.0.07.0.0Mar 2007--------Delete reference to the 32.304 CMIP SS. Reason: SA#35 endorsed the SA5 decision to not propagate the CMIP Solution Sets to Rel-7 (TS 32.3x4, TS 32.4x4, TS 32.6x4)--7.0.07.0.1Jun 2007--------Changed TS Title. Reason: SOAP does not stand anymore for "Simple Object Access Protocol"--7.0.17.0.2Dec 2008SA_42SP-0808450001-Incorrect URI specified in TS 32.307 (both word document and corresponding wsdl file)F7.0.27.1.0Dec 2008SA_42------Upgrade to Release 8--7.1.08.0.0Mar 2009SA_43SP-0902070002--Correction of notifyF8.0.08.1.0Mar 2010SA_47SP-10000004--Incorrect direction for message notifyRequestF8.1.08.2.0
STYLEREF ZA 3GPP TS 32.307 V8.2.0 (2010-03)
PAGE 28
STYLEREF ZGSM Release 8
3GPP
— Ô Õ
% & úïàï×Î׿ױ¦±›•‘‰€‘|‘sjaV‘PJ
häyh 0J
hugÁ 0J h– hugÁ nHtH hA9 h nHtHh‘R? h nHtHhäyh h nHtHh‘R? hugÁ h mHsHhugÁ mHsH hugÁ
hugÁ CJ h¡! CJ mH nH u hAC€ CJ mH nH u hugÁ CJ mH nH u h‹1 mH nH u hAC€ mH nH u häyh mH nH u hugÁ mH nH u hugÁ CJ@ mH nHo(tHu hugÁ CJ@ mH nH u
hugÁ CJ@ 8 \ — µ Õ ( F G ™ š › ¤ » ý û ò ò ò ò ò ò ò ä ä Ø Ö Ô ¸ ¦ - $„„„‹&@#$]„^„a$- $„„¤ð „‹&@#$&d PÆ ÿ ]„^„a$ K $„;&P#$+Dda$
: $
Æ Þ'+DAa$ gdÛfß 9 „"„E&+DU 8 7 rá ßá àá ýýý & ' ( ) * + B C D E G { } ¢ ¥ ¿ Þ -
.
¬
? B ™ ¤ º » À Ï Ð ì ( W ` t üõíå×ͼ®×ª¤¤¤—¤¤¤¤ü‚wüoaü hugÁ CJ OJ QJ mHsH hugÁ mHsH hugÁ 56OJ QJ *hugÁ CJ OJ QJ hugÁ CJ OJ QJ
h³Nœ CJ
hugÁ CJ H*
hugÁ CJ hÛfß jb hÛfß UmH nH sH!jÉ‚ÆL
hÛfß UVmH nH tHhÛfß mH nH sH j hÛfß UmH nH sHhÛfß B*ph ÿ j hÛfß U
hugÁ 6CJ hugÁ "» À Ï Ð ì ( W ` t ‹ "
ë Ñ ¿ £ ¿ ¿ £ ¿ v g - $„=1&P#$+Dña$gdÛfß - $¤ð „=1&P#$&d +DñPÆ ÿ a$gdÛfß - $„„¤ „øÿ&@#$]„^„a$- $„„¤ð „øÿ&@#$&d PÆ ÿ ]„^„a$ - $„„„øÿ&@#$]„^„a$- $„„„øÿ&@#$&d PÆ ÿ ]„^„a$ - $„„¤ð „øÿ&@#$]„^„a$ t ‹ #
'
)
} ‡ ˆ – — ¡ » ¼ ½ ¾ ¿ À Í Î è é ê ë ì í î ï õ ö " # = > ? ïæÛÐÛ̽¹±¹¦±¹±–¹±¹‹±¹±–¹¹±¹v±¹±–¹¹±¹k±jBl h[y¸ UjÅk h[y¸ Uh[y¸ CJ PJ aJ jHk h[y¸ Uh[y¸ CJ PJ aJ mH nH tH jËj h[y¸ Uj h[y¸ Uh[y¸ *h[y¸ j *h[y¸ U hugÁ hAC€ CJ mH nH uhÛfß CJ mH nH uhÛfß mH nH uhÛfß 56OJ QJ mH nH u *"
#
l
‚
7 } ‡ À í B ‚ ² ä H ´ ô 7 t µ ð * ð ð ð ä ä ä Ú Ø Ø Ø Ø Ø Ö Ö Ø Ø Ö Ö Ö Ô Ô Ö Ô Ò „ „ ^„ `„ - „=1&P#$+DñgdÛfß - $„=1&P#$+Dña$gdÛfß ? @ A B C D b c } ~ € ‚ … † ’ “ ® ¯ ° ± ² µ ¶ Ä Å ß à á â ã ä å æ ý þ ' ( B C D F G H K L ^ _ y z { üôäüÚüôüÏôüôäüÚüôüÄôüôäüÚüôü¹ôüôäüÚüôü®ôüôäüÚüôü£ôüôäüÚüôü˜ôj0o h[y¸ Uj³n h[y¸ Uj6n h[y¸ Uj¹m h[y¸ Uj