hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.6.2 Occupied Bandwidth / Out of Band Emissions | Single carrier testing with WDS output power of 43dBm show that there is negligible impact on the occupied bandwidth or output emissions due to the inclusion of WDS. |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.6.3 Conclusions | The simulations results show the impact of WDS from an RF perspective on most critical downlink parameters, with certain requirements at BS interface point.
Any effects can be measured over a range of different power classes and implementation scenarios in order to define the interface conditions required to satisfy th... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 7 Operation & Maintenance | In order to identify any possible impact of a communication interface between WDS and other network elements R3-011933 [Ref. 2] and R5-010481 [Ref. 3] were discussed within RAN 3 and SA5 respectively.
Either working group said that no impact was found on existing specs because of WDS, and it appeared that existing spec... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 8 Location Services (LCS) | In order to assess any impact of WDS on location services, the co-existence between WDS and location services (LCS) is discussed in this section. Three methods for location services are currently specified in TS 25.305 – Stage 2 Functional Specification of Location Services in UTRAN. These are OTDOA, Cell ID based posi... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 8.1 OTDOA/IPDL | The OTDOA/IPDL methods are based on the measurements of the UTRA pilot signal (CPICH) made by the UE and the Location Measurement Unit (LMU). The position of the UE is estimated by using the observed time difference of arrival from three or more base stations.
As measurements are made by the UE who then reports them t... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 8.3 Network Assisted GPS | These methods make use of UE, which are equipped with radio receivers capable of receiving signals from the Global Positioning System (GPS). Therefore there are no implications to a WDS enhanced network. |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 8.4 Summary of WDS impact on LCS | From the above discussion it is clear that no impact on LCS is envisaged due to inclusion of WDS
The system calculations required in order to accommodate the provision of LCS information to the network rely primarily on the UE or high level network systems specifically dedicated to LCS.
The only provision for inclusion... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 9 WDS Positioning on Existing 3GPP TS and WI | The present structure of 3GPP UTRAN FDD specifications includes BS (TS 25.104 [ref.1] / TS 25.141 [ref.2]) and Repeaters (TS 25.106 [ref.3]/ TS 25.143 [ref.4]).
TS25.104 relates to Macro BS and its performance. Ongoing work on Base Station Classification WI (TR25.951).
TS25.106 relates to RF Repeater and its performa... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 9.1 WDS positioning discussion | Following points highlight specific technical positioning for WDS, starting from simulations results.
1. WDS are physically connected to BS according to capacity and coverage planning requirements. They are NOT used to complement radio coverage of a BS (so-called simulcasting), and therefore provide consistent and reli... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 9.2 Potential Impact of WDS Standardisation | The Feasibility Study has highlighted the potential impact of WDS standardisation based on existing BS specifications TS25.104/TS25.141, with specific reference to the interface point between BS and WDS, where a more stringent performance than that of compliant BS may be required in order to guarantee full compliance t... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 10 Conclusions and Way Forward | The Feasibility Study has shown how WDS performance may impact on a 25.104 compliant generic BS, on a limited number of basically important parameters and, more in general, in the network configuration.
A new set of compliance parameters should be investigated as a consequence of BS classification and further definitio... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 1 Scope | The present document specifies an initial set of Parlay X Web Services. For each selected Web Service, this document describes the motivation for its inclusion, the commercial and technical rationale, and an illustrative usage scenario(s). This document also specifies the message(s) exchanged during invocations of eac... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 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.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 3 Definitions and abbreviations | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 22.101 [2] and the following apply.
(Parlay X) Application: unless otherwise specified, the document will be using the term (Parlay X) application to refer to software that invokes or can invoke a Parlay X Web Service.
Parlay X Gateway... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply.
A/IN (Advanced) Intelligent Network
AAA Authorization, Authentication, and Accounting
AM Account Management
API Application Programming Interface
APP Application
CBC Content Based Charging
CC Call Control
DI... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4 Parlay X Web Services | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4.1 Selection Criteria | Each Parlay X Web Service should be abstracted from the set of telecommunications capabilities exposed by the Parlay APIs, but may also expose related capabilities that are not currently supported in the Parlay APIs where there are compelling reasons. These tiered levels of abstraction, and the Parlay – Parlay X relat... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4.2 Implementation Considerations | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4.2.1 Versioning | The namespace will contain a version number as a suffix for the service name. The suffix will be a separate path element consisting of: the letter 'v' followed by a major version number followed by an underscore and a minor version number.
• The major version number will reflect the version of Parlay X for the last ch... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4.3 Optional Parameters | Some parameters are defined as OPTIONAL. Within a message signature, the XML schema type definition for an optional parameter may use the nillable attribute to allow the actual value of the parameter to be "NULL" (or "NIL"). Since this approach is dependant upon the industry adoption of WS-I's Basic Profile 1.0, whic... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 4.4 Document Structure | The present document has the following clauses:
4) Parlay X Web Services
5) Common Data Definitions
6) Third Party Call
7) Network-Initiated Third Party Call
8) SMS
9) Multimedia Message
10) Payment
11) Account Management
12) User Status
13) Terminal Location
Apart from this clause and clause 5, each of the remaining c... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5 Common Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5.1 Common Data Type Definitions | Where possible standard XML Schema data types are used, as defined in http://www.w3.org/TR/xmlschema-2/#built-in-datatypes.
Other data types that are common to multiple Parlay X Web Services are defined in the following subclauses.
5.1.1 EndUserIdentifier
The EndUserIdentifier data type is specified as a URI: [scheme]:... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5.1.2 ArrayOfEndUserIdentifier | A collection of elements where each element is of data type EndUserIdentifier. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5.1.3 ArrayOfURI | A collection of elements where each element is of data type URI. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5.2 Common Exception Definitions | All of these exceptions are common to multiple Parlay X Web Services. Each exception is assigned an eight character identifier, where:
• The first 3 characters "GEN" identify the exception as generic: i.e. common to multiple Parlay X services. The "GEN" string shall not be assigned to any Parlay X Web Service-specific... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 5.3 Common Data Definitions Syntax – WSDL | The rpc/literal files include two common files
• parlayx_common_types.xsd
• parlayx_common_faults.wsdl
The rpc/encoded files contain these definitions within each service file. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6 Third Party Call | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.1.1 Description | Currently, in order to perform a third party call in telecommunication networks we have to write applications using specific protocols to access Call Control functions provided by network elements (specifically operations to initiate a call from applications). This approach requires a high degree of network expertise. ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.1.2 Commercial & Technical Rationale | The basic commercial rationale for developing the Third Party Call Web Service is:
• to increase the use of Call Control capabilities in software applications
• to empower traditional IT developers to produce large numbers of such applications
• to lower the development cost and time for such applications. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.1.3 Relationship to Similar or Supplanted Specifications | In the PSTN/Internet Interworking (PINT) working group a "request to call" scenario has been defined (RFC 2848 [8]). A request is sent to an IP host that cause a phone call to be made, connecting party A to some remote party B.
The PINT approach is not API-based but instead it proposes an extension to SIP to implement ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.1.4 Scenarios | shows an scenario using the Third Party Call Web Service to handle third party call functions. The application invokes a web service to retrieve stock quotes and a Parlay X Interface to initiate a third party call between a broker and his client.
In the scenario, whenever a particular stock quote reaches a threshold va... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.2 Call API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• makeACall
• getCallInformation
• endCall
• cancelCallRequest |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.2.1 Attempt Immediate Call Set-Up Between Two Addresses | a) makeACall(EndUserIdentifier callingParty, EndUserIdentifier calledParty, String charging, out String callIdentifier)
b) Behaviour:
The invocation of makeACall requests to set-up a voice call between two addresses, callingParty and calledParty, provided that the invoking application is allowed to connect them. Option... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.2.2 Get Current Status of a Call | a) getCallInformation(String callIdentifier, out CallInformationType callInformation)
b) Behaviour:
The invocation of getCallInformation retrieves the current status, callInformation, of the call identified by callIdentifier. This method can be invoked multiple times by the application even if the call has already end... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.2.3 End a Call | a) endCall(String callIdentifier)
b) Behaviour:
The invocation of endCall terminates the call identified by callIdentifier. If the call is still in the initial state this method has the same effect as the cancelCallRequest method.
c) Parameters:
NAME
TYPE
DESCRIPTION
callIdentifier
String
It identifies a specific call ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.2.4 Cancel a Call Request | a) cancelCallRequest(String callIdentifier)
b) Behaviour:
The invocation of cancelCallRequest cancels the previously requested call identified by callIdentifier. Note that this method differs from the endCall method since it only attempts to prevent the call from starting but it does not have any effect if the call has... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3.1 Data Types | In addition to the Common Data Types defined in clause 5, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3.1.1 CallInformationType | The CallInformationType data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
callStatus
CallStatus
It indicates the current status of the call (see possible values below)
startTime
DateTime
When applicable (callStatus <> CallInitial), it indicates the time of the beginning of the call
dur... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3.1.2 CallStatus | The CallStatus data type is an enumeration with the following values:
VALUE
DESCRIPTION
CallInitial
The call is being established
CallConnected
The call is active
CallTerminated
The call was terminated |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3.1.3 CallTerminationCause | The CallTerminationCause data type is an enumeration with the following values:
VALUE
DESCRIPTION
CallingPartyNoAnswer
Calling Party did not answer
CalledPartyNoAnswer
Called Party did not answer
CallingPartyBusy
Calling Party was busy
CalledPartyBusy
Called Party was busy
CallingPartyNotReachable
Calling Party was not... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.3.2 Exceptions | In addition to the Common Exceptions defined in clause 5.2, there are exceptions specific to this Web Service. Similar to the Common Exceptions, each Web Service-specific exception is assigned an eight-character identifier. This identifier is interpreted as described in clause 5.2, except that the first 3 characters u... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 6.4 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_third_party_calling_types.xsd
• parlayx_third_party_calling_service_port.wsdl
• parlayx_third_party_calling_service.wsdl
The rpc/encoded file is
• parlayx_third_... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7 Network-Initiated Third Party Call | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.1 Description | Currently, in order to determine the handling of a subscriber initiated call in telecommunication networks we have to write applications using specific protocols to access Call Control functions provided by network elements. This approach requires a high degree of network expertise. We can also use the OSA gateway appr... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.2 Commercial & Technical Rationale | The basic commercial rationale for developing the Network-Initiated Third Party Call Web Service is:
• to increase the use of Call Control capabilities in software applications
• to empower traditional IT developers to produce large numbers of such applications
• to lower the development cost and time for such applicat... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.3 Relationship to Similar or Supplanted Specifications | All the capabilities of the Network-Initiated Third Party Call Web Service (and more) can also be achieved with the Parlay/OSA generic call control or multiparty call control services. The Network-Initiated Third Party Call Web Service can be seen as a very limited subset of the network initiated call control functiona... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.4 Scenarios | This subclause gives some possible scenarios using the Network-Initiated Third Party Call Web Service to handle network-initiated calls. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.4.1 Incoming call handling | A subscriber receives a call while he is logged-on to the Internet. Since this occupies his telephone connection, he is regarded as busy by the network. The subscriber has an application that is invoked when somebody tries to call him while he is busy. The application provides the subscriber with a list of choices on h... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.1.4.2 Service numbers | An application is triggered whenever a certain service number is dialled. This number is used to connect the caller to one of the maintenance personnel. The application redirects the call to the appropriate maintenance person based on, e.g., calling party number, time, location and availability of the maintenance perso... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2 Call API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• handleBusy
• handleNotReachable
• handleNoAnswer
• handleCalledNumber
• handleOffHook
These messages are initiated by the Network-Initiated Third Party Call Web Servi... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2.1 Request Application Handling of a 'Busy' Condition | a) handleBusy(EndUserIdentifier callingParty, EndUserIdentifier calledParty, out Action action)
b) Behaviour:
The invocation of handleBusy requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is busy when the call is re... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2.2 Request Application Handling of a 'Not Reachable' Condition | a) handleNotReachable(EndUserIdentifier callingParty, EndUserIdentifier calledParty, out Action action)
b) Behaviour:
The invocation of handleNotReachable requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is not reach... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2.3 Request Application Handling of a 'No Answer' Condition | a) handleNoAnswer(EndUserIdentifier callingParty, EndUserIdentifier calledParty, out Action action)
b) Behaviour:
The invocation of handleNoAnswer requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty does not answer the... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2.4 Request Application Handling of a 'Called Number' Condition | a) handleCalledNumber(EndUserIdentifier callingParty, EndUserIdentifier calledParty, out Action action)
b) Behaviour:
The invocation of handleCalledNumber requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty. The method is invoked when the ca... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.2.5 Request Application Handling of an 'Off Hook' Condition | a) handleOffHook(EndUserIdentifier callingParty, out Action action)
b) Behaviour:
The invocation of handleOffHook requests the application to inform the gateway how to handle the fact that the callingParty tries to initiate a call. The application returns the action, which directs the gateway to perform one of the foll... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.3.1 Data Types | In addition to the Common Data Types defined in clause 5.1, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.3.1.1 Action | The Action data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
actionToPerform
ActionValues
Indicates the action as described below
routingAddress
EndUserIdentifier
The address to be used in case the action indicates 'Route'
charging
String
OPTIONAL. If present, represents the name of a... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.3.1.2 ActionValues | The ActionValues data type is an enumeration with the following values:
VALUE
DESCRIPTION
Route
Request to (re-)route the call to the address indicated with routingAddress.
Continue
Request to continue the call without any changes. This will result in normal handling of the event in the network
EndCall
Request to end ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.3.2 Exceptions | All exceptions thrown by this Web Service are Common Exceptions, as defined in clause 5.2. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 7.4 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_network_initiated_call_types.xsd
• parlayx_network_initiated_call_service_port.wsdl
• parlayx_network_initiated_call_service.wsdl
The rpc/encoded file is
• parla... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8 SMS | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.1.1 Description | Currently, in order to programmatically receive and send SMS it is necessary to write applications using specific protocols to access SMS functions provided by network elements (e.g., SMS-C). This approach requires a high degree of network expertise. Alternatively it is possible to use the Parlay/OSA approach, invoking... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.1.2 Commercial & Technical Rationale | The basic commercial rationale for developing the SMS Web Service is:
• to increase the use of SMS capabilities in software applications
• to empower traditional IT developers to produce large numbers of such applications
• to lower the development cost and time for such applications. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.1.3 Relationship to Similar or Supplanted Specifications | Published web services exist that allow transmission of SMS messages, ring-tones and operator logos. For example, the Xmethods site (http://www.xmethods.com/) hosts more than one web service to handle SMS. These web services provide basic SMS capabilities, each using a different interfaces. The SMS Web Service aims to ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.1.4 Scenarios | Figure 3 shows a scenario using the SMS Web Service to send an SMS message from an application. The application invokes a web service to retrieve a weather forecast for a subscriber (1) & (2) and a Parlay X Interface (3) to use the SMS Web Service operations (i.e. to send an SMS). After invocation, the SMS Web Service ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.2 Send SMS API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations (i.e. of the SMS Web Service by the application) are:
• sendSms
• sendSmsLogo
• sendSmsRingtone
• getSmsDeliveryStatus. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.2.1 Send an SMS Message | a) sendSms (EndUserIdentifier[] destinationAddressSet, String senderName, String charging, String message, out String requestIdentifier)
b) Behaviour:
The invocation of sendSms requests to send an SMS, specified by the String message to the specified address (or address set), specified by destinationAddressSet. Optiona... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.2.2 Send an SMS Logo | a) sendSmsLogo(EndUserIdentifier[] destinationAddressSet, String senderName, String charging, Base64Binary image, SmsFormat smsFormat, out String requestIdentifier)
b) Behaviour:
The invocation of sendSmsLogo requests to send an SMS logo, specified by the byte array image to the specified address (or address set), spec... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.2.3 Send an SMS Ringtone | a) sendSmsRingtone(EndUserIdentifier[] destinationAddressSet, String senderName, String charging, String ringtone, SmsFormat smsFormat, out String requestIdentifier)
b) Behaviour:
The invocation of sendSmsRingtone requests to send an SMS ringtone, specified by the String ringtone (in RTX format) to the specified addres... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.2.4 Get Current Status of an SMS Delivery | a) getSmsDeliveryStatus(String requestIdentifier, out DeliveryStatusType[] deliveryStatus)
b) Behaviour:
The invocation of getSmsDeliveryStatus requests the status of a previous SMS delivery request identified by requestIdentifier. The information on the status is returned in deliveryStatus, which is an array of status... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.3 SMS Notification API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations (i.e. of a notification web service by the SMS Web Service) are:
• notifySmsReception |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.3.1 Notify Application of an SMS Message Sent to a Specific Address | a) notifySmsReception(String registrationIdentifier, String smsServiceActivationNumber, EndUserIdentifier senderAddress, String message)
b) Behaviour:
The notifySmsReception method must be implemented by a Web Service at the application side. It will be invoked by the Parlay X server to notify the application of the re... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.4 Receive SMS API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations (i.e. of the SMS Web Service by the application) are:
• getReceivedSms. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.4.1 Retrieve All SMS Messages Sent to a Specific Address | a) getReceivedSms(String registrationIdentifier, out SmsType[] receivedSms)
b) Behaviour:
The invocation of getReceivedSms retrieves all the SMS messages received that fulfil the criteria identified by registrationIdentifier. The method returns only the list of SMS messages received since the previous invocation of the... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.1 Data Types | In addition to the Common Data Types defined in clause 5.1, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.1.1 DeliveryStatusType | The DeliveryStatusType data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
destinationAddress
EndUserIdentifier
It indicates the destination address to which the notification is related
deliveryStatus
DeliveryStatus
Indicates the delivery result for destinationAddress. Possible values ar... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.1.2 DeliveryStatus | The DeliveryStatus data type is an enumeration with the following values:
VALUE
DESCRIPTION
Delivered
Successful delivery
DeliveryUncertain
Delivery status unknown: e.g. because it was handed off to another network.
DeliveryImpossible
Unsuccessful delivery; the message could not be delivered before it expired.
MessageW... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.1.3 SmsType | The SmsType data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
message
String
Text received in SMS
senderAddress
EndUserIdentifier
It indicates address sending the SMS |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.1.4 SmsFormat | The SmsFormat data type is an enumeration with the following values:
VALUE
DESCRIPTION
Ems
Enhanced Messaging Service, standardized in 3GPP TS 23.040 [3], which defines a logo/ringtone format
SmartMessagingTM
Defines a logo/ringtone format |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.5.2 Exceptions | In addition to the Common Exceptions defined in clause 5.2, there are exceptions specific to this Web Service. Similar to the Common Exceptions, each Web Service-specific exception is assigned an eight-character identifier. This identifier is interpreted as described in clause 5.2, except that the first 3 characters u... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 8.6 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_sms_types.xsd
• parlayx_sms_service_port.wsdl
• parlayx_sms_send_service.wsdl
• parlayx_sms_receive_service.wsdl
• parlayx_sms_notification_service_port.wsdl
• p... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9 Multimedia Message | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.1.1 Description | Currently, in order to programmatically receive and send Multimedia Messages, it is necessary to write applications using specific protocols to access MMS functions provided by network elements (e.g., MMS-C). This approach requires application developers to have a high degree of network expertise.
This contribution def... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.1.2 Commercial & Technical Rationale | The scope of this Web Service is much more than an enhancement of the Parlay X SMS Web Service. The purpose is not to add more SMS features, but to form a generic multimedia adapted messaging API. The reason to incorporate SMS in the API is mainly to create one set of APIs for messaging instead of one set per network. ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.1.3 Relationship to Similar or Supplanted Specifications | This Web Service includes functions implemented in the SMS Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.1.4 Scenarios | Figure 5 shows an example scenario using sendMessage and getMessageDeliveryStatus to send data to subscribers and to determine if the data has been received by the subscriber. The application invokes a web service to retrieve a stock quote (1) & (2) and sends the current quote - sendMessage - using the Parlay X Interf... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.2 Send Message API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations (i.e. of the Multimedia Message Web Service by the application) are:
• sendMessage
• getMessageDeliveryStatus |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.2.1 Send a Multimedia Message | a) sendMessage(EndUserIdentifier [] destinationAddressSet, String senderAddress, String subject, MessagePriority priority, String charging, out String requestIdentifier) Attachment[content]
b) Behaviour:
Request to send a Message to a set of destination addresses, returning a requestIdentifier to identify the message.... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.2.2 Get Current Status of a Multimedia Message Delivery | a) getMessageDeliveryStatus(String requestIdentifier, out DeliveryStatusType[] deliveryStatus)
b) Behaviour:
This is a poll method used by the application to retrieve delivery status for each message sent as a result of a previous sendMessage message invocation. The requestIdentifier parameter identifies this previous ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.3 Receive Message API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations (i.e. of the Multimedia Message Web Service by the application) are:
• getReceivedMessages
• getMessageURIs
• getMessage |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.3.1 Provide Application with Multimedia Messages Sent to the Application | a) getReceivedMessages(String registrationIdentifier, MessagePriority priority, out MessageRef [] messageRef)
b) Behaviour:
This method enables the application to poll for new messages associated with a specific registrationIdentifier. If the registrationIdentifier is not specified, the Parlay X server will return refe... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.