For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP Tenant in 3GPP management system:

Void.

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

As described in Figure 4.1-1 and Figure 4.1-2, for fulfilling the tenancy concept, operators' can have different options to share their management resources between multiple tenants (e.g. operator's business customers): Option 1 (Figure 4.1-1)

• Multiple tenants represented by single MnS Consumer instance
• Same management service is consumed by 3 different tenants (e.g. performance management service), from a single MnS Producer instance
• Tenancy related management data isolation is not currently provided by 3GPP management system

Option 2 (Figure 4.1-2)

• Each tenant represented by dedicated MnS Consumer
• Same management service is consumed by 3 different tenants (e.g. performance management service), from a single MnS Producer
• Tenancy related management data isolation is partially provided by 3GPP management system (e.g. by dedicated MnS Consumer)

The non-exhaustive key issues for tenant management to be addressed in the present document are as following: Issue 1. Tenancy, tenant and tenant management key concepts Study the key concepts of tenancy, tenant and tenant related management. Issue 2. Different exposure of network management capabilities for different tenants Study scenarios, contents and behaviours of management capabilities exposure for different tenants. Issue 3. Relation of tenant management, communication service management and network management, including network slicing management Study the relation of tenant management, communication service management and network management, including network slicing management.

Tenant concept can be considered as a group of user in software and virtualization context. The 3rd party consumer using 3GPP management capability can represent a tenant that use communication service (e.g. an enterprise user). In 3GPP management system, management services are produced to offer management capabilities that provide management operation and management data access for specific management purposes. The management services are supported by 3GPP management system are as following:

• provisioning service;
• performance management service; and
• fault management service.

When the 3rd party consumer is represented as group of users, identified as tenants (e.g. enterprises that consume V2X service), tenants should be able to consume management services that are exposed to them. The typical management data exposed to tenants are performance measurement KPIs and fault alarms. When 3GPP management system exposes management data to tenants, the management data should be provided by performance management service or fault management service.

The following tenant types may exist in order to provide 5G communication services, the management capability for different tenant types may be different depending on the services the tenant obtains from the provider.

• Tenant type A: an entity uses its logical network (i.e. an instance of a network) provided by NOP, and performs lifecycle management of its logical network.
  Tenant type A is categorized as below:
  • Tenant type A1: an entity uses its logical network provided by NOP to provide CSIs to its customers (e.g., verticals), and performs lifecycle management of its logical network.
  • Tenant type A2: an entity uses its logical network provided by NOP to provide CSIs to end users, and performs lifecycle management of its logical network.
• Tenant type B: an entity uses its logical network provided by NOP, and does not performs lifecycle management of its logical network. Any associated management capabilities are accessed and consumed by the NOP.
  Tenant type B is categorized as below:
  • Tenant type B1: an entity uses its logical network provided by NOP to provide CSIs to its customers (e.g., verticals), and does not performs lifecycle management of its logical network.
  • Tenant type B2: an entity uses its logical network provided by NOP to provide CSIs to end users, and does not performs lifecycle management of its logical network.

3GPP management system may provide management capabilities based on agreed requirements between a tenant and the network operator (e.g. performance report, alarm notification, provisioning service, etc.). NRM IOC represents managed resource that can be created or deleted for multiple tenants in multiple tenant environment. For example, if NOP exposes NSI provisioning services to external MnS consumer, the IOC of NetworkSlice can be associated with authorized this external MnS consumer. MOI represents the managed resource that can be used by multiple tenants in multiple tenant environment. In one of the scenario, 5G Core AMF may support AMF measurement KPI reporting related to network slice instance supporting multiple tenants. In another scenario when a network slice instance supports multiple tenants, 3GPP management system may use an MOI to represent the management resource for multiple tenants.

The tenant should be capable to consume MnS that provides management capabilities. It is proposed to use MOI (component type B) to identify the managed resource of the tenant. The 3GPP management system should be capable to authorize, identify and enforce exposure of specified management capabilities related to managed resource of a tenant.

The network slice subnet management function can provide management services that provide management capabilities in multiple tenant environment. For example, the network management function is optionally capable of handling a management data and monitor network measurement KPIs for multiple tenant. The management function supporting multiple tenant environment may act as MnS consumer and as MnS provider for tenants as shown in Figure 4.7-1.

When tenant represents a group of CSI consumers in 3GPP management system, the tenant may consume a set of management capabilities. The exposure governance management function defined in TS 28.533 may authorize the MnS consumer representing the tenant and apply exposure governance on management services.

It is illustrated in Figure 4.7-2 that exposed management services can be consumed by MnS consumers representing tenants. The MnS consumer should provide the identity information of the tenant when it consumes services provide by MnS producer. The EGMF should authenticate the identity information of the tenant and authorize the MnS consumer representing the tenant to access MnS and consume a specified set of management capabilities.

According to TR 28.805, the vertical customer is authorized to obtain the allowed management capability from CSI service provider according to the pre-defined agreements between the CSI service provider and the CSI service consumer. As described in Figure 4.8-1, CSI Consumer in CSMF can be mapped into a MnS consumer associated with tenant information in 3GPP management system. The MnS provider can provide management capabilities for this tenant by using tenant information as following:

• 5G network slice NRM IOC attribute with tenant information, used to identify managed resource for the tenant
• S-NSSAI value, additionally used by 3GPP management system to associate NF performance measurement with a tenant

When the MnS consumer subscribes or queries alarm information of managed resources, the alarm information of managed resource related to the tenant may be provided to the MnS consumer. The tenant information in Serviceprofile IOC is associated with S-NSSAI in sNSSAIList attributes or sub-attributes as defined in TS 28.541. S-NSSAI may be used for filtering the alarm information in subscribe or getAlarmList operation defined in TS 28.532.

Tenant information in NRM IOCs may be used to distinguish performance measurement for different tenants. The MnS consumer representing the tenant may get the performance measurements of the network function. If the tenant information in Network Slice IOC ServiceProfile is associated with S-NSSAI in sNSSAIList attributes of MOI, the counter per S-NSSAI defined in TS 28.552 may be set for the network function performance measurements.

It is proposed to use tenant information (e.g. tenant identifier) in NRM IOCs, for purpose of identification to managed resource for the tenant.

The alarm information of MOI may be provided to the management service consumer a tenant in multiple tenant environment. The tenant information may be used for filtering the alarm information associated with a tenant.

The use of counter per S-NSSAI associated to tenant information may be clarified for the network function performance measurements in TS 28.552.