<p>Copyright TM Forum 2008<br/></p><p><br/></p><p><b>Overview</b><br/></p><p><i>To Be Added</i><br/></p><p><br/></p><p><b>Functionality</b><br/></p><p>The basic concept is to define resource domains that expose consistent services (NGOSS Implementation Contracts) to other TAM applications. Because Domains are based on the operator's policies the scope of the resource information model that they expose is based on the SP's individual policy decisions. However the basic services exposed are those necessary to support, at least, but not limited to, the other Resource Management Application Areas.<br/></p><p>The Resource Domain Management applications are responsible for providing a completely encapsulated interface to network technology domains by:<br/></p><p><ul><li>hiding vendor specific idiosyncrasies e.g. for network s  through the use of mTOP/MTNM/MTOSI template mechanisms.</li><br/></p><p><li>presenting a standards based interfaces e.g.  for networks mTOP/MTOSI/MTNM specifications using a standard data model.</li><br/></p><p><li>providing in-domain activation.</li><br/></p><p><li>providing in-domain alarm collection, filtering (and non data based correlation) to supplement that done by <b>Correlation & Root Cause Analysis</b>.</li><br/></p><p><li>providing in-domain QoS activation .</li><br/></p><p><li>providing in-domain inventory discovery to supplement that done by <b>Resource Inventory Management.</b></li><br/></p><p><li>containing limited distributed copies of logical network inventory sufficient to support atomic operation rollback, element manager selection and network auto-discovery. Domain Managers are <b>not</b> the masters of this data. Where keys need to be assigned (e.g. IP addresses, VLAN IDs, PortIDs, telephone numbers) this will be undertaken by other applications in the Resource Management Layer.</li><br/></p><p></ul><br/></p><p>The Resource Domain Management applications are <b><u>NOT</u></b> responsible for:<br/></p><p><ul><li>cross-domain anything (activation, fault correlation and RCA, QoS, testing, orchestration - all done in <b>Resource Configuration / Provisioning</b>, <b>Correlation & Root Cause analysis</b>, <b>Resource Performance Monitoring</b>, <b>Resource Testing Management</b>).</li><br/></p><p><li>planning (done in <b>Resource Planning/Optimization</b>)</li><br/></p><p><li>design (done in <b>Resource Design/Assign</b>)</li><br/></p><p><li>assignment/ allocation of anything (e.g. ports, IP addresses) (done in <b>Resource Design/Assign</b>)</li><br/></p><p><li>managing the engineering work for physical network equipment (outside plant), fiber or copper (done in <b>Resource Logistics</b> and <b>Workforce Management</b>).</li><br/></p><p><li>providing in-domain performance monitoring - this is generally conducted by specialist tools and probes in <b>Resource Testing Management</b>.</li><br/></p><p><li>being the database of record (Network inventory database of record is in <b>Resource Inventory Management</b>)</li><br/></p><p><li>naming network resources (done in <b>Resource Planning/Optimization and Resource Design/Assign)</b></li><br/></p><p><li>workflow (done in <b>Resource Configuration / Provisioning</b>,)</li><br/></p><p><li>B2B ordering (done in the <b>Partner/Supplier Management Applications</b>)</li><br/></p><p></ul><br/></p><p><b>Replication of Resource Domains</b><br/></p><p>Resource Domain Management may be replicated by Service Providers to cover any specific policies that they have for organizing resource domains e.g. e2E technologies such as SDH and ATM, Legacy PDH networks, narrow band voice networks, Application Servers containing IT Application and Content - IPTV, and Next Generation Networks where domains need to be formed based on network roles.<br/></p><p>Domains may also be replicated to cover different vendors and different equipment types at the choice of the Service Provider.<br/></p><p><br/></p><p><b>Impact on Element Management</b><br/></p><p>With Next Generation Networks there will be an evolution away from complex and expensive Element Management Systems towards Resource Domain Managers that have common features that directly connect to the network or Application Server elements themselves. This evolution is also needed to compress the number of systems in any stack to reduce complexity, increase agility and improve end to end process performance.<br/></p><p><br/></p><p>The use of a Resource Domain Manager means that this can happen whilst shielding all the other TAM applications areas from these detailed implementation changes.<br/></p><p><br/></p><p><b>Relationship to mTOP/ MTNM/MTOSI</b><br/></p><p>In this analysis it is assumed that that the services exposed by the Domain Managers for Networks will be based on the MTOSI Specifications. This is shown as a red vertical bar in the figure. This sets a critical SP expectation on the position of the procurement boundary for basic Resources Management Functionality (Service interfaces).<br/></p><p><br/></p><p>It also shows a clear relationship between the TAM as an Application Architecture and actual conformance testable interfaces that have been developed by the TMF.<br/></p><p><br/></p><p>Note that MTOSI is not limited to just this boundary and may be used by other application areas in the Resource Management and Service Management layers.<br/></p><p>Resource Domain Management for IT computing and applications will be defined in a future version.<br/></p><p><br/></p><p><b>Supported Contracts</b><br/></p><p><i>To Be Added</i><br/></p>