virtual field
Virtual fields are intended to support MATRIXX environments that accept both Diameter and 5G messages. Each virtual field has a unique
name, and includes a Diameter container and field name, and an equivalent 5G container and
field name. The Charging Server selects
the appropriate valid field to use for normalization, field mapping, and so on. Any pricing
object (such as service type objects or event type objects) that normally use a container
name and a field name to specify a field in a 3G network message, can now use a Virtual
Field instead. You manage virtual fields using My MATRIXX.