MTAS Target Handling Management Guide

MTAS

1	Introduction
1.1	Prerequisites
2	Overview
2.1	Subfunctions
2.2	Target Handling Interaction with Other Services
3	Target Handling Configuration
3.1	Service Data Configuration
3.2	Terminal Selector Prefix Used in Network Signaling Configuration
3.3	AS Controlled Forking Administrative State Configuration
4	Performance Management
5	Fault Management

1 Introduction

This document describes how to configure the Target Handling function in the MTAS.

1.1 Prerequisites

It is assumed that the user of this document is familiar with the O&M area, in general.

1.1.1 Licenses

To enable basic services in the MTAS, the MMTel license must be installed.

For more information about licensing, refer to MTAS Licenses

1.1.2 Documents

Before starting any procedure in this document, ensure that the following documents are available:

1.1.3 Conditions

The following condition must apply:

An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2 Overview

The Target Handling function is part of the User Common Data. The User Common Data is a "quasi" service holding user data common for more than one service.

The Target Handling function allows provisioning of target lists that can be used by several services.

The following target lists are provided by the Target Handling function:

Common target list, holding user-defined names, and the related URIs, that can be used as a target (referred by the name) in more than one service.
Common device list, holding user-defined names, and the related terminal selectors, identifying the served terminals of the user. The terminals can be used as a target (referred by the name) in more than one service. The addressing of specific terminals of the served user by the MTAS is called AS Controlled Forking.

A valid AS Controlled Forking license must be present for using the common device list.

Note:: The actual use of the common target list and the common device list (AS Controlled Forking) is described in the relevant service user guides.
Another flavor of AS Controlled Forking in MTAS is the Flexible Communication Distribution to Primary User’s Devices function. This alternative allows for “dynamic” addressing of all (mobile and fixed) currently registered terminals of a served user or a mobile terminal only, which eliminates a need to manually configure a "static" list of individual device targets. AS Controlled Forking license is not required by FCD to Primary User’s devices. For more information on FCD to Primary User’s devices, refer to MTAS Flexible Communication Distribution Management Guide.

For information of the deployment-specific network configuration for using the AS Controlled Forking feature, refer to MTAS External Network Configuration

2.1 Subfunctions

There are no subfunctions included in the Target Handling function.

2.2 Target Handling Interaction with Other Services

The Target Handling function has no interaction with other services.

3 Target Handling Configuration

The MtasMmt MO contains attributes that are used by the Target Handling function as illustrated in Figure 1.

Figure 1 Target Handling MO Structure

There is no configuration needed in the Target Handling function.

3.1 Service Data Configuration

This section describes how to configure the service data.

3.1.1 Operator Subscription Level Service Configuration

The operator can do the following:

Activate/deactivate the User Common Data subscription for the subscriber.
Set the maximum number of targets in the common target list and in the common device list for the user.
Allow and disallow the use of the common device list for the user.
Enable the auto-answer avoidance feature for the served user in the Flexible Communication Distribution and Session Transfer to Own Device services.

A valid AS Controlled Forking license must be present for using the common device list.

For more information about the formal XML definition of the service over the CAI3G interface, refer to MTAS CAI3G Interface

3.1.2 Subscriber Subscription Level Service Configuration

The user part of the User Common Data includes the following data:

Common target list, holding user-defined names, and the related URIs, that can be used as target in more than one service.
- Fixed target list (true/false, changeable only by the operator). When fixed-targets is set to "true" then the target identities are set by the operator and cannot be changed by the user, only the name.
- User-defined name
- URI
- Activate auto-answer avoidance for the target
Common device list, holding user-defined names, and the related terminal selectors, identifying the served terminals of the user.
- Fixed target list (true/false, changeable only by the operator) When fixed-targets is set to "true" then the target identities are set by the operator and cannot be changed by the user, only the name.
- User-defined name
- Terminal selector (For information on feature tag, refer to IETF RFC 3840)

Example 1 User Common Data

<mmt-serv:user-common-data>
<mmt-serv:target-device-list fixed-targets="true">
<mmt-serv:target-device name="mobile" terminal-selector="my-mobile"/>
<mmt-serv:target-device name="landline" terminal-selector="my-home" />
</mmt-serv:target-device-list>
<mmt-serv:target-list fixed-targets="true">
<mmt-serv:target auto-answer-avoidance=”true” id="tel:+446666100005" name="Elin"/>
<mmt-serv:target id="tel:+446666100006" name="Fredrik"/>
</mmt-serv:target-list>
</mmt-serv:user-common-data>

3.2 Terminal Selector Prefix Used in Network Signaling Configuration

The CM attribute mtasMmtTerminalSelectorPrefix indicates that the prefix added in front of each provisioned feature parameter used for selecting a single terminal (terminal selector). The prefix is for appending such elements of the feature parameter that are not relevant for the end user. The leading ‘+’ indicates non-RFC 3840 base parameters, or tags for operator or vendor-specific namespace, for example, ‘+g.operator.xxx.’.

So, if the prefix is +g.operator.xxx. and the provisioned terminal selector is my-mobile, then the terminal selector used in signaling is +g.operator.xxx.my-mobile.

The actual use of the terminal selectors defined in the common device list is described in the relevant service user guides. For more information about the deployment-specific network configuration for using the terminal selectors in relation with the AS Controlled Forking feature, refer to MTAS External Network Configuration

3.3 AS Controlled Forking Administrative State Configuration

This attribute indicates the administrative state of the AS Controlled Forking feature. This attribute determines if MTAS can address single terminal clients of the served user by inserting terminal selector in the INVITEs sent to the served user.

The AS Controlled Forking function is enabled by setting the mtasMmtAscfAdministrativeState attribute in the MtasMmt MO to 1 (Unlocked). If the mtasMmtAscfAdministrativeState is set to 0 (Locked), no AS Controlled Forking function is provided by the MTAS.

Note:: This setting applies to AS Controlled Forking understood as addressing individual devices based on static configuration in the User Common Data. Flexible Communication Distribution to Primary User’s Devices, an alternative AS Controlled Forking in MTAS, is enabled independently using mtasFcdDistributeToPrimaryUserDevices attribute.

4 Performance Management

For measurements, related to the Target Handling function, refer to Managed Object Model (MOM).

5 Fault Management

For alarms, related to the Target Handling function, refer to MTAS Alarm List.