General Service Type Properties

Table 1. General Service Type Properties
Attribute	Description
Full Name	The fully qualified name of the service type. This name is created automatically and is used to identify the service parent. You cannot set or change this value.
Type ID	The service type ID, which is generated automatically by My MATRIXX and based off of the parent service type ID. This must map to the corresponding service ID used by the GGSN. You cannot set or change the value.
Parent ID	The ID of the parent service, from which this service is a descendent. This value is derived from the type of service you create. You cannot set or change this value.
ID	The service type ID used by My MATRIXX and saved to the pricing database. You cannot set or change this value.
Name	A descriptive name for the service type. This name is added to the end of the fully qualified name of the service, after any parent service types. It is also displayed in My MATRIXX.
Event Type Name	The name of the event associated with the service type. The event type name determines the EDR to generate for usage of this service. Important: Although the ROOT value is listed as an event type, it is not valid and will result in errors if you use it for a service type.
Failed Event Type	Select usage_failure or none. If you select usage_failure, after you save the general properties, you can map the failure events in the Failed Event Field Mappings table. For information about creating a new failed event field mapping, see the discussion about failed event type mappings.
Quantity Type	The quantity type that is measured for the service usage, on which to base rates. Only price components with this quantity type are considered applicable during rating. The service type's quantity type is only a default for setting up pricing formulas. Each context type within a service type can have a different quantity type.
Quantity Units	The measurement unit of the service type. The unit is dependent on the Quantity Type and can be one of the following: in_data, out_data, and total_data: bytes, mbytes, kbytes, gbytes actual_duration and active_duration: seconds, minutes, hours, days, weeks service_specific: none. This value is also used when the quantity is 0, as with text messages.
Audit Data Container Name	(Optional) The name of the MDC in which to store audit data. This can be the base MtxAuditData MDC, which has the Aggregation ID or event ID and the raw usage quantity, or a custom MDC based off of it. If you specify an audit MDC, you must also define the Audit Field Mappings for it. This enables you to specify the fields that contain the data you want to copy to the audit data container.
Session Data Container Name	(Optional) The name of a session extension MDC in which to copy data from the incoming message MDC. This enables you to persist the field value throughout a session and use it as the basis of normalizations. The session container can be the base MtxChargingSessionExtension MDC or a custom MDC based off of it. The session extension MDC is stored in the Attr field. If you specify a Session Container Name, you must also define the Session Field Mappings for it. The destination MDC in the field mapping can be the same MDC specified here based off of that MDC.
Suppress Usage Event With No Impact	(Optional) To suppress generation of usage events when the event does not have any balance impacts, select Suppress Usage Event With No Impact. Usage events will not be generated if the rated usage quantity is zero and if there are no balance impacts. Note that aggregated usage events are always generated, even if the aggregated usage quantity is zero. Enabling this option may be helpful in scenarios where there is a high load on the mediation system due to many usage events with zero data consumption. For backwards compatibility, the default for this option is not set.
Generate Session Monitor Event	The existing open charging sessions generates Session monitor events per the configuration in Service Type definition at the time of current session start time. The new sessions use the updated information from the Service Type definition. For example, event generation is changed from every 2 hours to every 3 hours , or event generation is disabled, in the middle of the charging session, then the current charging session continues to generate events every 2 hours. Once the current session ends, subsequent charging sessions generate events every 3 hours, or will not generate any session monitor events. Select Generate Session Monitor Event and set the following fields: Session Monitor Interval — The interval at which an MtxSessionMonitorEvent EDR generates. Session Monitor Interval Unit — The measurement unit of the session monitor interval. Session Monitor Event Type — The event type for use in generating session monitor events.

Full Name

The fully qualified name of the service type. This name is created automatically and is used to identify the service parent. You cannot set or change this value.

Type ID

The service type ID, which is generated automatically by My MATRIXX and based off of the parent service type ID. This must map to the corresponding service ID used by the GGSN. You cannot set or change the value.

Parent ID

The ID of the parent service, from which this service is a descendent. This value is derived from the type of service you create. You cannot set or change this value.

ID

The service type ID used by My MATRIXX and saved to the pricing database. You cannot set or change this value.

Name

A descriptive name for the service type. This name is added to the end of the fully qualified name of the service, after any parent service types. It is also displayed in My MATRIXX.

Event Type Name

The name of the event associated with the service type. The event type name determines the EDR to generate for usage of this service.

Important: Although the ROOT value is listed as an event type, it is not valid and will result in errors if you use it for a service type.

Failed Event Type

Select usage_failure or none.

If you select usage_failure, after you save the general properties, you can map the failure events in the Failed Event Field Mappings table.

For information about creating a new failed event field mapping, see the discussion about failed event type mappings.

Quantity Type

The quantity type that is measured for the service usage, on which to base rates. Only price components with this quantity type are considered applicable during rating.

The service type's quantity type is only a default for setting up pricing formulas. Each context type within a service type can have a different quantity type.

Quantity Units

The measurement unit of the service type. The unit is dependent on the Quantity Type and can be one of the following:

in_data, out_data, and total_data:
bytes, mbytes, kbytes, gbytes
actual_duration and active_duration:
seconds, minutes, hours, days, weeks
service_specific:
none. This value is also used when the quantity is 0, as with text messages.

Audit Data Container Name

(Optional) The name of the MDC in which to store audit data. This can be the base MtxAuditData MDC, which has the Aggregation ID or event ID and the raw usage quantity, or a custom MDC based off of it.

If you specify an audit MDC, you must also define the Audit Field Mappings for it. This enables you to specify the fields that contain the data you want to copy to the audit data container.

Session Data Container Name

(Optional) The name of a session extension MDC in which to copy data from the incoming message MDC. This enables you to persist the field value throughout a session and use it as the basis of normalizations. The session container can be the base MtxChargingSessionExtension MDC or a custom MDC based off of it. The session extension MDC is stored in the Attr field.

If you specify a Session Container Name, you must also define the Session Field Mappings for it. The destination MDC in the field mapping can be the same MDC specified here based off of that MDC.

Suppress Usage Event With No Impact

(Optional) To suppress generation of usage events when the event does not have any balance impacts, select Suppress Usage Event With No Impact. Usage events will not be generated if the rated usage quantity is zero and if there are no balance impacts. Note that aggregated usage events are always generated, even if the aggregated usage quantity is zero.

Enabling this option may be helpful in scenarios where there is a high load on the mediation system due to many usage events with zero data consumption.

For backwards compatibility, the default for this option is not set.

Generate Session Monitor Event

The existing open charging sessions generates Session monitor events per the configuration in Service Type definition at the time of current session start time. The new sessions use the updated information from the Service Type definition.

For example, event generation is changed from every 2 hours to every 3 hours , or event generation is disabled, in the middle of the charging session, then the current charging session continues to generate events every 2 hours. Once the current session ends, subsequent charging sessions generate events every 3 hours, or will not generate any session monitor events.

Select Generate Session Monitor Event and set the following fields:

Session Monitor Interval — The interval at which an MtxSessionMonitorEvent EDR generates.
Session Monitor Interval Unit — The measurement unit of the session monitor interval.
Session Monitor Event Type — The event type for use in generating session monitor events.