e-based manage- ment architecture (see Section 3.2 for details of using the same approach in 5GC). In this approach, the reference model with fixed roles, such as NE or EM, was replaced by the con- cept of management service (MnS), with basic roles being the management service provider and management service consumer. Sometimes the provider is referred to as "producer." An MnS of an MnS provider may have multiple consumers. 3GPP specifies only the management capabilities provided via the MnS, which is com- posed of individually specified components. 3GPP TS 28.533 defines three components of the management service referred to as type A, B, and C as follows: Management service component type A is a group of management operations and/or notifi- cations. In standardized management services, a set of operations and set of notifications are typically uniform across a wide range of management services, SO the services are differentiated only by the information models (see component type B). Definitions of spe- cific instances of the component type A can be found in 3GPP TS 28.531 clause 6. Some of them are mentioned below. Management service component type B is the information model of managed entities. Spe- cific information models are defined in 3GPP TS 28.541. In 3GPP, the information models are also referred to as Network Resource Models (NRMs). Some examples are provided below. Management service component type C is defined as the performance and fault informa- tion of the managed entity. Figure 6.5.1 3G and 4G network management model (Source: Reproduced by permission of © 3GPP). 6 Enabling Technologies 6.5.3.1 Examples of Management Services One family of the management services described in 3GPP TS 28.531 is the provisioning ser- vices; this family covers configuration management and LCM. It includes provisioning of: Table 6.5.1 Operations and notifications for the provisioning MnSs for the NSI and NSSI. Provisioning For NSI and NSSI createMOI operation operations deleteMOI operation getMOIAttributes operation 