Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 28.500  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.4…   6…

 

5  Business level requirements

5.1  Requirements

5.1.1  General requirements

REQ-NFV-CON-1
Operator shall be able to manage mobile networks that include virtualized network functions and shall be able to identify whether the managed nodes are virtualized or not.
REQ-NFV-CON-2
The management of mobile networks that include virtualized network functions should reuse the 3GPP existing management solutions as much as possible.
REQ-NFV-CON-3
NM and EM in 3GPP management system managing the virtualized 3GPP entities shall be able to manage physical 3GPP entities also.
REQ-NFV-CON-4
3GPP management system shall support a capability allowing operators to manage mobile networks that include virtualized network functions with the assistance from NFV-MANO.
REQ-NFV-CON-5
The reference points between 3GPP management system and NFV-MANO shall support a capability allowing 3GPP management system to request information required for management from NFV-MANO.
REQ-NFV-CON-6
The performance of the 3GPP management system should be adequate to achieve the objective of 3GPP service time to market.
REQ-NFV-CON-7
The virtualized resources from NFVI, on which the VNF relies, should be collaboratively managed by 3GPP management system and NFV-MANO.
Up

5.1.2  FM requirementsWord‑p. 10
REQ-NFV_FM_SYS-CON-1
The Operator shall be able to manage and deal with the virtualized network function alarms and NFVI alarms, which are not related to virtualized network function, through 3GPP management system and NFV-MANO respectively.
REQ-NFV_FM_SYS-CON-2
3GPP management system shall be able to receive the virtualized network function alarm which includes the correlated virtualized resource fault information and process the alarm.
REQ-NFV_FM_SYS-CON-3
The virtualized network function alarm, which 3GPP management system acquired, shall include correct alarm type, alarm severity and possible cause information.
REQ-NFV_FM_SYS-CON-4
3GPP management system shall be able to request NFV-MANO to recover the virtualized network function when VNF automatic recovery is not enabled in NFV-MANO.
REQ-NFV_FM_SYS-CON-5
3GPP management system shall be able to receive the virtualized network function alarms when NFV-MANO performs VNF automatic recovery.
REQ-NFV_FM_SYS-CON-7
NFV-MANO shall support the subscription capability allowing 3GPP management system to subscribe to the VNF instance fault report related to virtualized resource(s) and virtualization-specific failures.
Up

5.1.3  CM requirements

REQ-NFV_CM_SYS-CON-1
3GPP management system shall be able to manage both physical and virtualized 3GPP entities with corresponding managed objects and attributes.
REQ-NFV_CM_SYS-CON-2
3GPP management system shall be able to perform necessary virtualized 3GPP entity configuration due to the VNF lifecycle management operation from NFV-MANO.
REQ-NFV_CM_SYS-CON-3
3GPP management system shall be able to re-configure involved neighbour physical and virtualized 3GPP entities if needed due to one NS or VNF LCM operation.
REQ-NFV_CM_SYS-CON-4
In order to minimize 3GPP service disruption when a VNF instance is scaled, the scaling shall not modify the existing connections with other network entities.
REQ-NFV_CM_SYS-CON-5
3GPP management system shall be able to request NFV-MANO to modify non-application information and configuration about a VNF instance managed by NFV-MANO (supported by requirements Os-Ma-nfvo.NsLcm.019 and Os-Ma-nfvo.NsLcm.020 in [9], and Ve-Vnfm-em.VnfLcm.008 and Ve-Vnfm-em.VnfCm.001 in [10]).
REQ-NFV_CM_SYS-CON-6
3GPP management system shall be able to query NFV-MANO non-application information about a VNF instance managed by NFV-MANO (supported by requirement Os-Ma-nfvo.NsLcm.015 in [9] and Ve-Vnfm-em.VnfLcm.004 in [10]).
Up

5.1.4  PM requirements

REQ-NFV_PM_SYS-CON-1
The key performance indicators which are defined for physical entities shall be applicable to virtualized entities in 3GPP core network.
REQ-NFV_PM_SYS-CON-2
3GPP management system shall support the performance measurements for virtualized 3GPP entity and 3GPP management system shall be informed of the performance measurement result of virtualized resources on which the virtualized 3GPP entity relies.
REQ-NFV_PM_SYS-CON-3
3GPP management system shall be able to request the VNF LCM operation towards NFV-MANO to mitigate the VNF performance bottleneck according to the results of the VNF performance measurements.
REQ-NFV_PM_SYS-CON-4
NFV-MANO shall be able to provide VNF PM data related to virtualized resource to 3GPP management system.
REQ-NFV_PM_SYS-CON-5
NFV-MANO shall support the subscription capability allowing 3GPP management system to subscribe to the VNF performance measurement report related to virtualized resource.
Up

5.1.5  LCM requirementsWord‑p. 11
REQ-NFV_LCM_SYS-CON-1
3GPP management system shall be able to request NFV-MANO to perform NS LCM operations (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-2
3GPP management system shall be able to request NFV-MANO to perform NSD management operations (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-3
3GPP management system shall be able to request NFV-MANO to perform VNF package/software management operations (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-4
3GPP management system shall be able to request NFV-MANO to perform VNF LCM operations (defined in ETSI GS NFV-IFA 008 [10]).
REQ-NFV_LCM_SYS-CON-5
3GPP management system shall support the capability to receive NS lifecycle change notifications from NFV-MANO (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-6
3GPP management system shall support the capability to receive the NSD management notifications from NFV-MANO (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-7
3GPP management system shall be able to request updating the NS instance (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-8
3GPP management system shall support the VNF package/software management notifications from NFV-MANO (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-9
3GPP management system shall support the capability to receive the VNF LCM change notifications from NFV-MANO (defined in ETSI GS NFV-IFA 008 [10]).
REQ-NFV_LCM_SYS-CON-10
3GPP management system shall be able to request scaling a virtualized network function to NFV-MANO (defined in ETSI GS NFV-IFA 008 [10]).
REQ-NFV_LCM_SYS-CON-11
3GPP management system shall be able to request executing the VNF Healing of a virtualized network function to NFV-MANO.REQ-NFV_LCM_SYS-CON-12 3GPP management system shall have the authority to determine the termination of a VNF instance(s).
REQ-NFV_LCM_SYS-CON-13
NFV-MANO shall have the capability allowing 3GPP management system to enable/disable the auto-scaling towards the corresponding VNF instance(s).
REQ-NFV_LCM_SYS-CON-14
NFV-MANO shall support the subscription capability allowing 3GPP management system to subscribe to the NS lifecycle change notifications (defined in ETSI GS NFV-IFA 013 [9]).
REQ-NFV_LCM_SYS-CON-15
NFV-MANO shall support the subscription capability allowing 3GPP management system to subscribe to the VNF lifecycle change notifications (defined in ETSI GS NFV-IFA 008 [10]).
REQ-NFV_LCM_SYS-CON-16
NFV-MANO shall have the capability allowing 3GPP management system to provide the affinity and anti-affinity information in the NSD.
REQ-NFV_LCM_SYS-CON-17
Operator shall be able to instantiate and manage multiple NS created using the same NSD but with specific parameterization (location, capacity, addresses).
Up

5.2  Actor rolesWord‑p. 12
See detailed actors and roles for each use case in clause 5.4.

5.3  Telecommunications resources

See detailed telecommunications resources for each use case in clause 5.4.

Up   Top   ToC