hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.3.2 Retrieve URI References to the Parts of a Multimedia Message | getMessageURIs(String messageRefIdentifier, out MessageURI message)
b) Behaviour:
This method will read the different parts of the message, create local files in the Parlay Gateway and return URI references to them. The application can then simply read each file or just have them presented as links to the end-user. The... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.3.3 Provide Application with a Multimedia Message as an Attachment | getMessage(String messageRefIdentifier) Attachments[out content]
b) Behaviour:
This method will read the whole message. The data is returned as a SOAP-Attachment (see note) in the return message.
NOTE: SOAP-Attachment is used because specification of the WS-Attachments standard is not yet complete. The decision to us... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.4 Message 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 Multimedia Message Web Service) are:
• notifyMessageReception |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.4.1 Notify Application of a Multimedia Message Sent to a Specific Address | a) notifyMessageReception (String registrationIdentifier, MessageRef messageRef)
b) Behaviour:
This method will have to be implemented by a web service on the client application side. The registration of the URI for this application web service is done off-line. This means that there is a registration mechanism in the... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.5 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.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 | 9.5.1.1 MessagePriority | The MessagePriority data type is an enumeration with the following values:
VALUE
DESCRIPTION
Default
This is the "NULL" value as described in subclause 4.3. This value is applicable if the parameter of type MessagePriority is tagged OPTIONAL.
Low
Low message priority
Normal
Normal message priority
High
High message pr... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.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 | 9.5.1.3 DeliveryStatusType | The DeliveryStatusType data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
destinationAddress
EndUserIdentifier
Address associated with the delivery status. The address field is coded as a URI.
deliveryStatus
DeliveryStatus
Parameter indicating the delivery status. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.5.1.4 MessageRef | The MessageRef data type is a structure containing six parameters as described below.
This data type is used to return the basic message data when polled by the application.
• If a message is a pure text message, the content will be returned in the message parameter and the messageRefIdentifier parameter will then not ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.5.1.5 MessageURI | The MessageURI data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
bodyText
String
Contains the message body if it is encoded as ASCII text.
fileReferences
Array of URI
This is an array of URI references to all the attachments in the Multimedia message. These are URIs to different files,... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 9.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 | 9.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_mm_types.xsd
• parlayx_mm_service_port.wsdl
• parlayx_mm_send_service.wsdl
• parlayx_mm_receive_service.wsdl
• parlayx_mm_notification_service_port.wsdl
• parlay... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10 Payment | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.1 Description | A vast amount of content, both information and entertainment, will be made available to subscribers. To support a business model that enables operators to offer integrated billing, a payment API is crucial. Open and inter-operable "payment APIs" are the key to market growth and investment protection. The Payment Web... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.2 Commercial & Technical Rationale | The payment process is a complex and critical component of telecom networks. The Payment Web Service:
• further enlarges the market for third party software, services and content by providing essential primitives for integrated billing
• enables charging through trusted and authenticated service or content providers
•... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.3 Relationship to Similar or Supplanted Specifications | Payment APIs are the focus of a number of industry standardisation initiatives:
• Parlay/OSA have developed powerful, carrier-grade Content-Based Charging (CBC) APIs
• PayCircle intends to provide a full, hand-crafted XML version of the Parlay/OSA CBC APIs
• Within the JCP, the JPay expert group seeks to specify a loca... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.4 Scenarios | This subclause discusses two scenarios: one where the subscriber account is directly charged and one where a subscriber uses a service for which the provider needs a reservation. Note, associated Payment API messages are shown in 'bold' format: e.g. (chargeAmount). |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.4.1 Scenario Number 1 | Assume a subscriber is interested in downloading a ring tone to his mobile (MS). The subscriber selects a ring tone and establishes a trusted relation with the ring tone provider. Essentially, the ring tone provider obtains the address (MSISDN) and other information from the subscriber. The ring tone may be download... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.1.4.2 Scenario Number 2 | Assume a subscriber is interested in receiving a stream of, say, a soccer match. The subscriber selects a match and establishes a trusted relation with the provider. Again, the provider obtains the MSISDN and other information from the subscriber. The subscriber wants to know what the service will cost and the provi... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.2 Amount Charging API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• chargeAmount
refundAmount |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.2.1 Charge Currency Amount to an Account | a) chargeAmount(EndUserIdentifier endUserIdentifier, Decimal amount, String billingText, String referenceCode)
b) Behaviour:
This message results in directly charging to the account indicated by the end user identifier. The charge is specified as a currency amount. The billing text field is used for textual informati... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.2.2 Refund Currency Amount to an Account | a) refundAmount(EndUserIdentifier endUserIdentifier, Decimal amount, String billingText, String referenceCode)
b) Behaviour:
This message results in directly applying a refund to the account indicated by the end user identifier. The refund is specified as a currency amount. The billing text field is used for textual ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.3 Volume Charging API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• chargeVolume
• getAmount
• refundVolume |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.3.1 Charge Volume to an Account | a) chargeVolume(EndUserIdentifier endUserIdentifier, Long volume, String billingText, String referenceCode)
b) Behaviour:
This message results in directly charging to the account indicated by the end user identifier. The charge is specified as a volume. The billing text field is used for textual information to appear... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.3.2 Convert a Volume to a Currency Amount | a) getAmount(EndUserIdentifier endUserIdentifier, Long volume, out Decimal amount)
b) Behaviour:
This message results in converting the given volume to a currency amount. The end user identifier is given to indicate the subscriber for whom this conversion calculation must be made. The message returns a currency amount... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.3.3 Refund Volume to an Account | a) refundVolume(EndUserIdentifier endUserIdentifier, Long volume, String billingText, String referenceCode)
b) Behaviour:
This message results in directly applying a refund to the account indicated by the end user identifier. The refund is specified as a volume. The billing text field is used for textual information ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.4 Reserved Amount Charging API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• reserveAmount
• reserveAdditionalAmount
• chargeReservation
• releaseReservation |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.4.1 Reserve a Currency Amount from an Account | c) reserveAmount(EndUserIdentifier endUserIdentifier, Decimal amount, String billingText, out String reservationIdentifier)
b) Behaviour:
This message results in directly reserving an amount for an account indicated by the end user identifier. The reservation is specified as a currency amount. Note that reservations ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.4.2 Adjust the Currency Amount of an Existing Reservation | a) reserveAdditionalAmount(String reservationIdentifier, Decimal amount, String billingText)
b) Behaviour:
This message results in the addition/reduction of a currency amount to/from an existing reservation indicated by the reservation id. The reservation is specified as a currency amount. Note that reservations do n... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.4.3 Charge a Currency Amount against an Existing Reservation | a) chargeReservation(String reservationIdentifier, Decimal amount, String billingText, String referenceCode)
b) Behaviour:
This message results in charging to a reservation indicated by the reservation id. Reservations, identified by reservation id, are established through invoking the reserveAmount message. The char... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.4.4 Release an Existing Reservation | a) releaseReservation(String reservationIdentifier)
b) Behaviour:
Returns funds left in a reservation indicated by reservation id to the account from which this reservation was made. Reservations, identified by reservation id, are established by invoking the reserveAmount message.
c) Parameters:
NAME
TYPE
DESCRIPTION
... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5 Reserved Volume Charging API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getAmount
• reserveVolume
• reserveAdditionalVolume
• chargeReservation
• releaseReservation |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5.1 Convert a Volume to a Currency Amount | a) getAmount(EndUserIdentifier endUserIdentifier, Long volume, out Decimal amount)
b) Behaviour:
Returns the amount resulting from converting the given volume. The end user identifier is given to indicate the subscriber for whom this calculation must be made. The message returns a currency amount if successful.
c) Pa... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5.2 Reserve a Volume from an Account | a) reserveVolume(EndUserIdentifier endUserIdentifier, Long volume, String billingText, out String reservationIdentifier)
b) Behaviour:
Reserves an amount of an account indicated by the end user identifier. The reservation is specified as a volume. Note that reservations do not last forever; it is assumed the default ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5.3 Adjust the Volume of an Existing Reservation | a) reserveAdditionalVolume(String reservationIdentifier, Long volume, String billingText)
b) Behaviour:
Adds/reduces a volume to an existing reservation indicated by the reservation id. The reservation is specified as a volume. Note that reservations do not last forever; it is assumed the default reservation enforcem... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5.4 Charge a Volume against an Existing Reservation | a) chargeReservation(String reservationIdentifier, Long volume, String billingText, String referenceCode)
b) Behaviour:
This message results in charging to a reservation indicated by the reservation id.. Reservations, identified by reservation id., are established through invoking the reserveVolume message. The charg... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.5.5 Release an Existing Reservation | a) releaseReservation(String reservationIdentifier)
b) Behaviour:
Returns funds left in a reservation indicated by reservation id. to the account from which this reservation was made. Reservations, identified by reservation id., are established through invoking the reserveVolume message.
c) Parameters:
NAME
TYPE
DESCR... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.6 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.6.1 Data Types | All data types are defined in clause 5.1. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 10.6.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 | 10.7 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_payment_service_port.wsdl
• parlayx_payment_amount_charging_service
• parlayx_payment_volume_charging_service
• parlayx_payment_reserve_amount_charging_service
•... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11 Account management | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.1 Description | Pre-paid subscribers, whether they have subscribed to pre-paid telephony, SMS, or data service, have credits with their service providers; the consumption of services will lead to reduction of their credit, or the credit may expire. Therefore, from time to time, subscribers may have to recharge their accounts. This o... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.2 Commercial & Technical Rationale | The recharging process is a critical component of telecom networks. At present, a number of prepaid services exist: e.g. Voice, SMS, and GPRS. The Account Management Web Service:
• further enlarges the market for third party software and outsourcing as it supports subscriber self service through re-charging, account q... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.3 Relationship to Similar or Supplanted Specifications | Parlay/OSA have developed powerful, carrier-grade Content-Based Charging (CBC) and Account Management (AM) APIs. The CBC APIs can be used to do recharging, but they also enable many other functions (e.g. debiting from accounts) as well. The AM APIs support some subscriber self-service (i.e. query functions), but they... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4 Scenarios | This subclause discusses three scenarios; one where a subscriber uses a voucher, one where the subscriber directly recharges after the payment is cleared, and one where the subscriber checks the recent transactions. Note, associated Account Management API messages are shown in 'bold' format: e.g. (getBalance). |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.1 Scenario Number 1 | The prepaid subscriber wishes to recharge their account with a voucher and query their account balance. The subscriber uses their mobile phone or other wireline phone to interact with an IVR system. In order to recharge their account, the subscriber must enter the voucher number, the MSISDN to be recharged , and PIN(... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.2 Scenario Number 2 | Directly recharging (i.e. without a voucher) works much along the same way. In this case, we assume the prepaid subscriber interacts with a web page. After providing the MSISDN, along with the PIN, the user can query the account balance (getBalance). For recharging, the subscriber must enter payment details, for exa... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.3 Scenario Number 3 | Every time a subscriber makes a telephone call the balance of their prepaid account is decremented with the cost of the call. When a recharge is done, the balance is increased either directly (balanceUpdate) or with an amount represented by a voucher (voucherUpdate). When a subscriber has doubts about the correctness... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2 Account Management API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getBalance
• getCreditExpiryDate
• balanceUpdate
• voucherUpdate
• getHistory
Note that certain parameters are negotiated off line. For example the reseller identifi... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.1 Account Balance Query | getBalance(EndUserIdentifier endUserIdentifier, String endUserPin, out Decimal amount)
b) Behaviour:
This message results in getting account balance indicated by the end user identifier and associated end user PIN. The returned amount is specified as a currency amount.
c) Parameters:
NAME
TYPE
DESCRIPTION
endUserIdent... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.2 Account Credit Expiration Date Query | a) getCreditExpiryDate(EndUserIdentifier endUserIdentifier, String endUserPin, out DateTime date)
b) Behaviour:
This message results in getting the expiration date of the credit indicated by the end user identifier and associated end user PIN. The returned date is the date the current balance will expire. Nil is retu... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.3 Account Balance Recharging | a) balanceUpdate(EndUserIdentifier endUserIdentifier, String endUserPin, String referenceCode, Decimal amount, Integer period)
b) Behaviour:
This message results in directly recharging the account indicated by the end user identifier and optional associated end user PIN. The reference code is used to uniquely identify ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.4 Account Balance Voucher Recharging | a) voucherUpdate(EndUserIdentifier endUserIdentifier, String endUserPin, String referenceCode, String voucherIdentifier, String voucherPin)
b) Behaviour:
This message results in directly recharging the account indicated by the end user identifier and optional associated end user PIN. The reference code is used to uniqu... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.5 Account Transaction History Query | a) getHistory(EndUserIdentifier endUserIdentifier, String endUserPin, DateTime date, Integer maxEntries, out DatedTransaction[] history)
b) Behaviour:
This message results in returning the transaction history of the account indicated by the end user identifier and associated optional end user PIN. The maximum number o... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.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 | 11.3.1.1 DatedTransaction | The DatedTransaction data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
transactionDate
DateTime
The date the transaction occurred.
transactionDetails
String
The transaction details. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.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 | 11.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_account_management_types.xsd
• parlayx_account_management_service_port.wsdl
• parlayx_account_management_service.wsdl
The rpc/encoded file is
• parlayx_account_m... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12 User status | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.1 Description | The Parlay X User Status Web Service will be used for getting user status information. The use of the Web Service will not require any specific telecommunication skills. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.2 Commercial & Technical Rationale | The use of a Parlay X User Status Web Service will enable fast and easy development of user status aware applications. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.3 Relationship to Similar or Supplanted Specifications | The Parlay/OSA Mobility (User Status) Service API can also provide user status information, but the Parlay X API for this Web Service is easier to use.
The Parlay/OSA Presence and Availability Management Service specifies a set of interfaces for applications that provide broader presence and availability capabilities t... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4 Scenarios | In the following, two sample Scenarios are described. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4.1 Buddy-list | This application is a mobile version of services like ICQ, MSN Messenger Service and Yahoo! Messenger, which offer text and voice chat and text conferencing. With a mobile terminal the user can be always on.
The user of the service can define one or more buddy-lists containing their friends (alternatively their family,... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4.2 Manual call routing | When a switchboard receives a call, the switchboard operator may obtain the status of a mobile terminal before trying to route the call to it. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.2 User Status API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getUserStatus |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.2.1 Get User Status | a) getUserStatus(EndUserIdentifier endUser, EndUserIdentifier requester, out UserStatusData userStatus)
b) Behaviour:
Requests the user status information of a user. Before returning the user status indicator, end-user and operator policies must be satisfied.
c) Parameters:
NAME
TYPE
DESCRIPTION
endUser
EndUserIdentif... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.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 | 12.3.1.1 UserStatusData | The UserStatusData data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
userStatusIndicator
UserStatusIndicator
It indicates the status of the end user.
additionalUserStatus
Information
String
A string to hold additional information if the userStatusIndicator is 'Other'. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.1.2 UserStatusIndicator | The UserStatusIndicator data type is an enumeration with the following values:
VALUE
DESCRIPTION
Online
User is online.
Offline
User is offline (mobile terminal switched off/other terminal not connected to the service), or wants to appear to be offline.
Busy
User is busy.
Other
Custom user status information can be ret... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.2 Exceptions | All exceptions thrown by this Web Service are Common Exceptions, as defined in clause 5.2. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.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_user_status_types.xsd
• parlayx_user_status_service_port.wsdl
• parlayx_user_status_service.wsdl
The rpc/encoded file is
parlayx_user_status_service.wsdl |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13 Terminal Location | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.1 Description | The Parlay X Terminal Location Web Service will be used for getting location information. The use of the Web Service will not require any specific telecommunication skills, but knowledge of location co-ordinates will be required. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.2 Commercial & Technical Rationale | The use of a Parlay X Terminal Location Web Service will enable fast and easy development of location aware Applications. The use of the Web Service will only require knowledge of longitude and latitude from the World Geodetic System 1984 (WGS 84), which is the reference system chosen for the coding of locations.
The m... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.3 Relationship to Similar or Supplanted Specifications | The Mobile Positioning System (MPS) offers much of the same functionality that the Parlay X Terminal Location Web Service will offer. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.4 Scenarios | In the following, a sample Scenario is described. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.4.1 Location enabled Buddy-list: | This application is a mobile version of services like ICQ, MSN Messenger Service and Yahoo! Messenger, which offer text and voice chat and text conferencing. With a mobile terminal the user can be always on, and the service can also show where buddies are located.
The user of the service can define one or more buddy-li... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.2 Terminal Location API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getLocation |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.2.1 Get Location of Terminal | a) getLocation(EndUserIdentifier endUser, EndUserIdentifier requester, LocationAccuracy accuracy, out LocationInfo location)
b) Behaviour:
Requests the location of one terminal. The location is returned if the terminal is available. Before returning the location, end-user and operator policies must be satisfied.
c) Par... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.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 | 13.3.1.1 LocationInfo | The LocationInfo data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
longitude
Float
Longitude
latitude
Float
Latitude
accuracy
LocationAccuracy
How accurate the Location information is. If the degree of accuracy wanted is available this should be given, if not the best possible accuracy... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.1.2 LocationAccuracy | The LocationAccuracy data type is an enumeration with the following values: (Each Parlay X Gateway operator must specify the uncertainty radiuses for Low, Medium and High)
VALUE
DESCRIPTION
Low
Low accuracy i.e. < 3 km radius of uncertainty.
Medium
Medium accuracy i.e. < 1 km radius of uncertainty.
High
High accuracy ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.2 Exceptions | All exceptions thrown by this Web Service are Common Exceptions, as defined in clause 5.2. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.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_terminal_location_types.xsd
• parlayx_terminal_location_service_port.wsdl
• parlayx_terminal_location_service.wsdl
The rpc/encoded file is
parlayx_terminal_locat... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 1 Scope | The present document provides an overview of the architecture and issues related to the provision of voice optimisation within the GERAN. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
[1] 3G TS 26.090, "Adaptive Multi-Rate (AMR) speech transcoding".
[2] 3G TS 26.190, "AMR Wideband speech codec, Transcoding functions".
[3] IETF AVT internet-draft "RTP, A Transport P... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3 Definitions, symbols and abbreviations | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.1 Definitions | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.1.1 Terminal integrated application | In this document the term “Terminal integrated application” is used. An application is considered to be “integrated in the terminal” when the application is co-located with the PDCP and RRC protocol entities. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.2 Symbols | Editors note: to be completed |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.