Figure RO.06 - Resource Number - Number Portability Roles

The Resource Number Portability Role ABE contains the entity NumberPortabilityRole and the entities needed to complete the roles associated, like the clearinghouse, which is strongly related with the number portability.<br/>NumberPortabilityRole is a class that gives a specific behavior and responsibilities to the requests, depending of many factors and the source provided. It has a portabilityStatus as a specific attribute and a generalization to an existing entity called LogicalResourceRole. This entity helps with the management and tracking of the status for the portability requests, since it can be initiated, started, completed, among others. This track is made for the requests through the continuous communications with other sources, like the entity NumberPortabilityClearinghouse as a party role, since the service providers don’t communicate directly for the number portability, and use the NumberPortabilityClearinghouse as an intermediary. Therefore, NumberPortability, because of its complexity, its management of different states between its flows with other sources, works with a NumberPortabilityRole through an aggregation. <br/>All the number portability requests have a behavior with and affinity and dependency to the different parties created and added. (Number Portability Clearinghouse, Service Provider, Customer). This relation affects directly to the tracking for the portability through a status (portabilityStatus attribute).<br/>In this figure it shows the relation of PartyRole (from Party ABE) with Party (Also from Party ABE) and how it relates with the role for number portability. For instance, there is a new subclass for PartyRole in order to reach every party who participates in the process. This new entity is NumberPortabilityClearinghouse, a very relevant party when a number portability is involved. <br/>On the side for the roles, the new entity is called NumberPortabilityRole, with an aggregation of many to 0.1 with the NumberPortabilityRequest. This role entity inherits form LogicalResourceRole (from Logical Role ABE), who inherits from the main parent, ResourceRole (from Resource ABE). This last entity is the one who has the association with PartyRole, through this, the whole communication flows perfectly.<br/><br/>