WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Administering Parlay X Terminal Location over MLP

After you deploy Parlay X Terminal Location over MLP, you can use the TWSS Administration Console to change the deployment configuration properties for the Web service and related Service Platform components.

Parlay X Terminal Location over MLP enables applications to send Web service requests to TWSS, requesting the Terminal Location services defined by the Parlay X 2.1 specification and register for Terminal Location Notifications. The Terminal Location over MLP 3.1/3.2 components are location clients to the location servers.

The component provides the Parlay X 2.1 based Web service that accepts requests for Terminal Location services, controls validity checks that are done to ensure the requests are valid, and forwards the requests to the MLP connector. This is based on MLP 3.1 and MLP 3.2 specification for downstream processing.

TWSS Administration Console settings

This Web service implementation adds the following configurable settings to the TWSS Administration Console:
  • Global: Policy values that are used for all services.
    • Common Service Settings: Use these settings to configure naming schemes for groups. The Access Gateway uses the IBM® XDMS component to resolve groups, and it can define and configure groups apart from the group scheme.
      • Country and code: The local country and code.
      • Address plan: The local address plan.
      • Enable Transaction Monitoring: Whether or not to enable transaction monitoring.
      • Supported Group Scheme: A comma-separated list of URI schemes that the service treats as a group URI. This setting must be coordinated with the Group List Manager component configuration. The default value is glmgroup.
      For more information about these settings, refer to the topic Group schema configuration.

  • Services: Default values used for Parlay X Terminal Location over MLP:
    • Terminal Location Web service: The following lists the configurable runtime properties:
      • Location Type: Type of location requested, either CURRENT, LAST, CURRENT_OR_LAST, or INITIAL (default CURRENT).
      • Altitude Requested: If true, then altitude information should be requested when location requests are made.
      • Request Priority: The priority of the location request, either HIGH or NORMAL (default NORMAL).
      • Minimum Acceptable Accuracy: The minimum possible value for acceptable accuracy, expressed as a radius in meters (default 100).
      • Minimum Requested Accuracy: The minimum possible value for requested accuracy, expressed as a radius in meters (default 100).
      • Maximum Age: Maximum acceptable age, in seconds, of the location information that is returned (default 0, meaning no maximum).
      • Response Timeout: Time, in seconds, to wait for the response from the location server, used as a backup for the response time parameter in location-based operations (default 60). A timeout value of zero is interpreted as an infinite timeout. This value is used when no socket timeout is set in the HTTP method parameters.
      • Use Extended Location: If true, extended location requests, containing target information and requesting a particular quality of service, are made (default false).
      • Maximum Location Addresses: The maximum number of addresses for which a getlocation for group request can be made (default 5).
      • Service ID: A unique ID assigned to the TWSS TL MLP SI by the MLP Location Server. When the value is a non-empty string, it is mapped to the element “client/serviceid” in the MLP Request XML. Otherwise, “client/serviceid” is not added to MLP Request XML.
      • Requestor Required: Determines whether to add a requester element to the MLP Request XML. When true, the WebSphere Application Server User Principle is mapped to the element “requestor/id” in the MLP Request XML. When false, the “requestor/id” is not included in the MLP Request XML.
      • Request Mode: Type of the request to be sent to MLP Location Server. When it is NONE, the “client/requestmode@type” element is not included in the MLP Request XML. When it is ACTIVE/PASSIVE, the “client/requestmode@type” is mapped to ACTIVE/PASSIVE.
    • Terminal Location Notification Web service: The following lists the configurable runtime properties:
      • Maximum Trigger Radius: The largest possible notification radius, in meters (default 50000).
      • Minimum Trigger Radius: The smallest possible notification radius, in meters (default 100).
      • Unlimited Notification Count Allowed: If true, then clients may request an unlimited number of notifications (default false).
      • Maximum Notifications Count: The maximum number of notifications that can be requested (default 10).
      • Maximum Notification Duration: The maximum duration, in milliseconds, of a notification request (default 100000, or 100 seconds).
      • Maximum Notification Addresses: The maximum number of addresses for which a notification can be set up (default 10).
      • Maximum Notification Frequency: The minimum time, in milliseconds, between notifications of a notification request (default 0).
      • Minimum Tracking Accuracy: The minimum possible value for tracking accuracy, expressed as a radius in meter and used in Geographical Notification requests (default 100).
      • Minimum Requested Accuracy: The minimum possible value for requested accuracy, expressed as a radius in meter and used in Periodic Notification requests (default 100).
      • Ignore Check Immediate: If false, then the terminal's location is checked while setting up the geographical notifications (default true).
      • CallbackEndpoint: A virtual callback endpoint URL, where the listener is running or a firewall is configured which routes the request. Example: http://localhost:9080/TWSS/ParlayX21/TerminalLocation/MLP/services/TerminalLocation
  • Common Components: Click the name of a Service Platform component–for example Fault Alarm Client or Usage Record Client–to configure it to work with this Web service implementation. If you leave the endpoint URI empty for a component, then the component is disabled.

You can receive additional information on specific properties from the online help in the TWSS Administration Console.

Policies

Policy attributes are retrieved from Subscription Management in the Access Gateway and are passed to the Parlay X Terminal Location over MLP Web service implementation in the SOAP headers. If the policies are not found in the TWSS SOAP header, then the Web service implementation uses the values that are defined in the TWSS Administration Console.

For information about default policy configuration, refer to the following topic: Default service policies for Parlay X Terminal Location over MLP.

URI formats

The Parlay X Terminal Location over MLP Web service implementation does not provide support for sip: URIs that include the context.

In the Parlay X Terminal Location over MLP Web service implementation for MLP 3.1, only the following URI format is supported:sip:+358-555-1234567;postd=pp22@example.com;user=phone

In the Parlay X Terminal Location over MLP Web service implementation for MLP 3.1, the following URI format is not supported:sip:+358-555-1234567;phone-context=5;tsp=a.b@example.com;user=phone

Altitude information

MLP provides the alt_acc (accuracy of the altitude returned) tag for SLIR/TLRR requests. For a potential altitude value, the parameter alt is used.

The response handles the altitude information as follows:
  • If the extended location request is being opted (where altitude is also expected) and if the response does not contain altitude information, then 0.0 is added for altitude in the response.
  • If the extended location request is being opted and the response does contain altitude information, then the actual altitude value is added in the response.
  • If the extended location is not being opted and the MLP Location server sends the altitude information, then the altitude value is not considered for the response.
  • If the extended location request is not being opted and the response does not contain altitude information, then the response contains no value for altitude.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.