5.4.4 SOA elements within the Management reference model

32.1013GPPPrinciples and high level requirementsRelease 17Telecommunication managementTS

This clause shows the placement of SOA basic elements SPs and SCs within the Management reference model (see Figure 1).

Figure 2d: Placement of SOA elements on Management reference model

For example, the right-hand side DM (a Management reference model construct) of Figure 2d shows an entity that is an aggregation of SOA basic elements (see clause 5.4.2). This entity produces and consumes services (see Figure of clause 5.4.2). It has two SPs and three SCs. In addition, it has an F function that mediates between services DM provides and the services DM requires. The DM services are provided to one SC of the neighboring DM and to two SCs of two NMs. The DM requires services from two SPs of the two NEs. One of the SPs of this DM provides a network management service via the Type 2 interface. One of the SPs supports the peer-to-peer protocol by offering services to its neighboring DM via Interface 4a. Three SCs of this DM are consumer of network management services offered by two NEs via the Type 1 interface.

To avoid cluttering the figure, SDs are not shown in Figure 2d. Conceptually, SDs can be positioned anywhere in the Management reference model. For example, the most likely configuration is to have SDs placed within the Operations Systems boundary. They can either be embedded inside NM and/or DM and/or stand-alone. Note that an SD embedded, say in DM-1, does not imply that this particular SD would/could only register services provided by DM-1. To avoid cluttering the figure, F function is only shown in one DM but all DMs and NMs can have F function as well.

The question if the protocols supporting the locateService and registerService (see Figure 2a) are of Type 1 or Type 2 or Type 4, etc can only be answered if the placement of SD and its clients (i.e. SC and SP) in the Management reference model are known.