12.053GPPSubscriber Related Call and Event DataTS
This annex contains the formal description of the information model for the present document. It consist of a simplified Entity-Relationship (ER) model by way of introduction, together with an object model specified in terms of the templates defined in CCITT X.722  "Guidelines for the Definition of Managed Objects".
The ER model consist of the following diagrams:
– tariff administration, the service and distance view;
– tariff administration, the date and time view;
– the call recording view.
These diagrams are intended to be an aid to understanding and, as a result, only the most important entities and relationships are shown. Some of the entities are present to resolve "many-to-many" relationships and are modelled via attributes rather than object classes. Such entities are explicitly marked.
A.1.1 Tariff administration, the service and distance view
Figure A.1 illustrates the most important service and distance relationships.
The "AoC Service" entity represents one or more services combined with a number of additional charging relevant parameters to form a customised service definition for the purpose of advice of charge. If a number of services are charged in the same way then they may be combined into a single "AoC Service" definition.
Each network contains a finite number of charging origins, nominal reference points defining the point of origin of a connection. The allocation of charging origins to cell identities, MSC areas, incoming trunk groups etc. is a network-specific matter and outside the scope of the present document. For the purpose of tariff administration it is sufficient to know the identities of the origins available.
Similarly, the derivation of charging destinations from, for example, the called address or number dialled is outside the scope of the present document. For the purpose of tariff administration it is sufficient to have a definitive list of the destinations available.
The combination of a charging origin with a charging destination provides a nominal measure of the distance factor involved in a connection. It should be noted that both the origin and destination within the "origin/ destination combination" are optional and that either of them may be omitted e.g. international connections may be purely destination dependent.
The combination of one or more such origin/ destination pairs defines a charging zone. The charging zone groups together those pairs belonging to the same distance class, typical examples include "local" and "long distance" zones.
The "Service Distance Dependency" combines an AoC service with a charging zone in order to apply a particular tariff class. Again, the charging zone is optional, if the charging of the service is not distance dependent then the zone is omitted.
Finally, a tariff class groups together those service distance dependencies to which the same tariff switching pattern is applied. The tariff switching pattern (see subclause A.1.2) determines the tariff to be applied at any particular point in time.
Figure A.1: Tariff administration, the service and distance view
A.1.2 Tariff administration, the date and time view
In general, the tariffs to be applied are dependent on a number of time-based factors including day, date and time of day. Figure A.2 illustrates the major entities involved and the relationships between them.
Each tariff class contains a number of tariff switching patterns defining the tariff to be applied over a complete 24 hour period (calendar day). The tariff switching pattern to be applied on a particular day depends on the day class of the day in question. Typical day classes include "weekday", "weekend" and "holiday". Each tariff class contains one, and only one, tariff switching pattern for each day class defined. However, the tariff switching pattern applied to a number of day classes may be the same.
A charging calendar contains a number of both "day" and "date" definitions assigning a day class to days of the week and days of the year respectively. Whereas a day class shall be defined for each day of the week, only those dates explicitly requiring a day class (e.g. holidays) are included in the charging calendar. It should be noted that the "date" definitions take precedence over the "day" definitions. For the avoidance of doubt, each day of the year belongs to one, and only one, day class.
Each tariff switching pattern contains one or more tariff periods. A tariff period is a continuous period of time during which the same tariff is applied. A tariff period is characterised by a tariff switch-over time and a reference to the tariff to be applied after that time. If the tariff does not vary over the 24 hour period covered by the switching pattern then a single tariff period shall be created with a switch-over time of midnight (00:00).
A tariff system (not shown) is defined as a complete and consistent set of tariff classes, tariff switching patterns and tariffs. There can be only one "active" tariff system at any one point in time and this system may not be altered. Alterations to tariff classes, tariff switch-over patterns and tariffs are prepared in advance by either copying the active tariff system or creating a new one. When the modifications are complete, a changeover between tariff systems may occur.
Figure A.2: Tariff administration, the date and time view
A.1.3 The call recording View
The call recording entities illustrated in figure A.3 control the generation and transfer of call and event records within a particular NE. The network element itself is represented by the managed element object. Each managed element may contain a call recording function. The call recording function represents the management view of the record generation process within the NE.
The generation of call records is controlled by the record class object. A record class defines the records to be produced for a particular purpose and the conditions under which those records are produced. A record class contains one or more record type control objects each of which controls the generation of records of a particular record type.
The record class also contains a number of supplementary service control objects. These objects determine which supplementary services (or groups thereof) are recorded. Each supplementary service control object contains one or more supplementary service action control objects each of which in turn determines whether or not a particular action (registration, invocation, etc.) is recorded.
The record class objects, together with the objects contained within them, define the call record generation control algorithm for normal usage. This includes both the records to be stored in the local NE filestore as well as those that are sent to the OS in the form of event reports. Additional call and event record event report filters may also be defined by employing the standard event forwarding discriminator object class. These filters are more suitable for temporary recording requirements as well as those containing more complicated filter constructs.
The notifications generated by the call recording function and presented to both the record classes and EFDs, may also be logged locally within the NE. Each managed element may contain one or more instances of the log managed object class.
Each log may contain one or more log entries each of which in turn contains a call and event record notification, an emergency call indication report or an observed IMEI ticket report.
Figure A.3: The call recording view