hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 14c The WI is a Work Task: parent Building Block | Trace Management (BB: OAM7-Trace)
WI
Unique_ID
OAM7-Trace
35039 |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 32.307 Notification IRP SOAP SS | |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 32.317 Generic IRP Management SOAP SS | |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 32.607 Basic CM IRP SOAP SS | |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 32.617 Bulk CM IRP SOAP SS | |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 32.667 Kernel CM IRP SOAP SS | 5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 1 3GPP Work Area | Radio Access
X
Core Network
Services
2 Linked work items
OAM&P (Operations, Administration, Maintenance & Provisioning) (Feature: OAM7)
WI
Unique_ID
OAM7
35041
Network Infrastructure Management (BB: OAM7-NIM)
WI
Unique_ID
OAM7-NIM
35042
3 Justification
Circuit is a logic link between two exchange network nodes which ... |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 3.2 Principle of radio channel power monitoring | The transport channels and physical channels have mapping relations. The following is mapping of transport channels onto physical channels.
25.211
From the figure above, the mapping from transport channel to physical channel is mostly one to one. So, in most cases, we just need to monitor the physical channels.
It is p... |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 14b The WI is a Building Block: parent Feature | (one Work Item identified as a feature)
OAM&P (Operations, Administration, Maintenance & Provisioning) (Feature: OAM7)
Acronym
Unique_ID
OAM7
35041
Technical Specification Group Services and System Aspects TSGS#29(05)0627
Meeting #29, Tallinn, ESTONIA, 26-28 September 2005
Source: SA5 (Telecom Management)
Title: WID W... |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 3 Open Work item status and approval time frame | This list reflects the open work items running under the responsibility of TSG SA WG5.
Work items in this colour are closed or building blocks. |
566267d8c54c8da6ca65b0a2ce396207 | 32.807 | 4 Completed or Terminated Work items | This list reflects work items that have been completed or terminated.
Annex A:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
Nov 2005
S5_44
S5-050529
--
--
Initial draft agreed by SA5#44
Dec 2005
SA_30
SP-050734
--
--
Submitted to SA#30 for Information
Mar 2006
SA_31
SP-060073
--
--
C... |
f4da59af4d170d3da6097a508a147acf | 50.099 | 45.005 New frequency ranges | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 45.050 Scenarios for new frequencies | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 24.008 Classmark information elements | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 45.008 Add frequency ranges | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 45.001 Add frequency and channels | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 43.030 Add frequency ranges | |
f4da59af4d170d3da6097a508a147acf | 50.099 | 43.022 Add channels to be searched | 2080%
Dec 2002
StartedOngoing
Addition of frequency bands to GSM – Changes for conformance tests
GP-022074
51.010-1 Add testing
0%
Dec 2002
Started
Enhanced Power Control
GP-012748
Realization of Enhanced power control and signaling support
GP-012749
Concept
Changes to 43.051
Changes to 44.004
Changes to 44.018
Changes... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 1 Scope | This technical report defines methods for supporting push services by 3GPP bearers. The mechanisms defined apply to existing bearers for the 3GPP Packet Switched Domain (PS domain), Circuit-Switched Domain (CS Domain), and the IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast Multicast Service, and Wirel... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 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... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 3 Definitions, symbols and abbreviations | |
e43c8396f49910c64271dab0534b85fe | 23.876 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 22.174 [3] and the following apply.
delivery network: a network that supports connectionless or connection oriented push services. A delivery network may simply be a GPRS network.
application server: a server that provides push service... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
e43c8396f49910c64271dab0534b85fe | 23.876 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
NAT Network Address Translator
NRPCA Network Requested PDP Context Activation
OTA Over The Air delivery protocol
PP Push Proxy
PI Push Initiator |
e43c8396f49910c64271dab0534b85fe | 23.876 | 4 Architecture Requirements | |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5 Push Architecture Overview | The Push Service Architecture overview is shown in figure 1. This includes the push application servers Push Function (or Push Proxy) and Push Initiator as well as the bearer services available as the delivery network and the Push Recipient or UE. The definition of functions in the Push Function (Push Proxy) and Push I... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5.1 Push Bearers in the PS Domain | This section describes the use of various mechanisms in the PS Domain to establish and/or maintain a bearer service connection to the UE over which Push services may be delivered.
Editors Note: the following bullets provide guidance for further work
• Push using Long Lived PDP Context
◦ This section describes the use o... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5.2 Push Bearers in the CS Domain | This section describes the use of various mechanisms in the CS Domain to establish and/or maintain a bearer service connection to the UE over which Push services may be delivered.
Editors Note: the following bullets provide guidance for further work
• Push over Circuit-Switched Data Bearer
◦ This section describes the ... |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5.3 Push in the IP Multimedia Subsystem | Editors Note: the following bullets provide guidance for further work
• Push using SIP
◦ The solution described in this section defines a method using the SIP protocol in IMS to carry Push services to a UE. |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5.4 Push using MBMS | |
e43c8396f49910c64271dab0534b85fe | 23.876 | 5.5 Push using WLAN | |
e43c8396f49910c64271dab0534b85fe | 23.876 | 6 Analysis and Conclusion | Annex <A> (normative):
<Normative annex title>
Annex <B> (informative):
<Informative annex title>
Annex <X> (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
200301
Created at SA2#29 San Francisco
0.0.0
2003-01
Revised at SA2#29 San Francisco
0.0.1 |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 1 Scope | The present document summarises the results of the feasibility study about inclusion of Wideband Distribution Systems, or WDS, as part of third generation networks in 3GPP standards.
It covers the history of the proposal, shows and discusses the results of relevant analysis and simulation activities, highlights the po... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 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.
• F... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 3 Definitions, symbols and abbreviations | |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 3.1 Definitions | |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 3.2 Symbols | |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
3GPP Third Generation Partnership Project
ACLR Adjacent Channel Leakage Ratio
ACS Adjacent Channel Sensitivity
ALC Automatic Level Control
BS Base Stations
CPICH Common PIlot CHannel
DL Downlink
FDD Frequency Division Duplex... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 4.2 WDS Architecture | The key attribute of WDS is its capability to enable the radio interface of a number of BS to be remote, and hence support a distributed multi-carrier and multi-operator network.
WDS is in general an active device and includes, but is not limited to, one or multiple RF front-end (LNA, MCPA) and RF transmission interfac... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 4.3 Practical Deployment Examples of WDS | Two examples are given only for information and topology understanding purposes of practical deployment for WDS, with reference to previous functions listing in Table 1. Additional indications will require further study on a dedicated Technical Report on WDS Deployment Scenario.
4.3.1 In-building Deployment
A sta... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 4.4 Benefits of WDS | |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 4.4.1 Technical and Deployment Aspects | Because of its very principle, WDS may bring technical and economical advantages as summarised here:
1. Possible BS and RNC co-location in centralised equipment locations allowing shared facilities, increased implementation flexibility and trunking efficiency.
2. Distributed RF wideband microcellular heads, with lower ... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 4.4.2 Standardisation Aspects | A standardisation process of WDS in the UMTS UTRA scenario is envisaged for:
1. Removing technical uncertainty risks from Operators and prevent from integration surprises
2. Reducing the burden of additional responsibility for Operators in defining their own specifications for WDS
3. Enabling fulfilment of EU recommend... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5 RF Feasibility Study | 5.1 RF Performance Discussion
Starting from reference [5], the RF feasibility study addresses the technical analysis of WDS performance based on its non-linear characteristics that may affect RF transmission through it, and derived as a function of a set of RF parameters at its interface with BS.
The following t... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.5 Simulation Results | |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.5.1 ACLR Testing | The simulations are carried out over a range of ACLR levels in order to assess the degradation attributable to the inclusion of a WDS and to attain the minimum ACLR input values to achieve the current specified output levels according to TS 25.104.
The performance of the BS was adjusted in order to achieve the range of... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.5.2 Multicarrier ACLR | In order to assess the impact of a multi-operator environment where multiple BS’s were connected to WDS, a test simulation was carried out with two BS, transmitting on adjacent carrier frequencies, connected to WDS Test Model 2 and the ACLR was measured. The test setup is shown in Figure 16 below.
Figure 16 Test setup ... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.5.3 Measurement of Occupied Bandwidth | WDS test model 2 was used to measure the occupied bandwidth resulting from the inclusion of the WDS. The occupied bandwidth containing 99.5% of the integrated transmitted power (43dBm) was measured at 3.855MHz (see figure 17).
Figure 17 Measurement of the occupied bandwidth.
Results from Figure 17.
Lower Side %
Upper S... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.5.4 Spectrum Emission Mask ( Out of Band Emissions ) | The out of band emissions were measured as specified in TS25.141 for a single carrier scenario with output power of 43dBm using WDS model 2.
The result found is shown in the graph below (figure 18) along with the relevant mask for Power Out greater than or equal to 43dBm (reference TS25.141 6.2.5.1)
Figure 18 Measureme... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.6 Simulation Summary | The simulation programme and hence the results set out to demonstrate two specific areas of interest.
1. The range of input levels available to a system which would feed a WDS system and its relationship to current specifications.
2. The margin required with the introduction of WDS over a number of output power classes... |
198feca7a70995985a5cc7f203dbedb2 | 25.867 | 5.6.1 ACLR | It was found that a 3dB margin is typically required to accommodate the effects of the inclusion of a WDS to an existing Base Station set-up.
There is a minor difference in performance which is dependent on WDS input signal level. With low input power signal levels, as demonstrated in the example with 20dBm output powe... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.