Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The UDRs in PCC.Routing store information about destinations, routing atributes attributes, and use cases.

The main objects of PCC . Routing are:



Contains the name of the workflow route to a specific Diameter Request Agent. It also contains the routing use cases to execute.


Contains the available routes for the incoming UDRs. Each route corresponds to a Hostname or Realm defined in the Diameter Routing Profile used by the Diameter Requested agent specified by the Routing_Details.


Maps message attributes to an entry in Routing_Details. If a match is found by the routing logic, it will be used to retrieve a set of destinations from Routing_Destination.


A use case triggers additional routing functions.

Overview of the Routing Data Model

The different UDRs within the Routing Control data model are connected as follows:


Field (name and type)


ID (int)

The unique id of the use case.

Misc (map<string, any>)

See the section below, Misc Field, for more information.

Use_Case (string)

The name of the use case. Acceptable values in the default workflow configurations are:
  • NULL for no additional functions

  • wfb for routing via Back-End Workflow

  • realm for realm-based routing. For information about realm-based routing see 9.16 17 Diameter Agents in the Desktop User's Guide.

The default workflow configurations can be extended to handle additional use cases.


Use Case UDR

Misc Field

Some objects in the PCC Routing Control data model includes include a field for storing miscellaneous data. The field is called Misc and has the type map<string, any>.


  • bigint
  • bitset
  • boolean
  • byte
  • bytearray
  • char
  • date
  • float/ double
  • int
  • ipaddress
  • long
  • short
  • string

Scroll pagebreak