32.3473GPPFile Transfer (FT) Integration Reference Point (IRP)SOAP Solution Set (SS)Telecommunication managementTS

4.1 General

The overall architectural feature of the File Transfer (FT) IRP is specified in 3GPP TS 32.342 [4]. This clause specifies features that are specific to the SOAP solution set.

The SOAP 1.1 specification [11] and WSDL 1.1 specification [13] are supported.

The SOAP 1.2 specification [14] is supported optionally.

This specification uses "document" style in WSDL file.

This specification uses "literal" encoding style in WSDL file.

The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [12]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex.

The FT IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.307 [10]. The IRPAgent shall support the push interface model, which means that the IRPAgent sends FT notifications to the IRPManager as soon as new events occur. The IRPManager does not need to check ("pull") for events.

Relevant definitions are imported from the FT IRP XML definitions of 3GPP TS 32.345 [5].

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

The WSDL structure is depicted in Figure 4.1 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service.

Figure 4.1: File Transfer IRP SOAP Solution Set WSDL structure