Process and system/function supporting service provision&activation in current network environment

The figure below shows the process and system/function supporting service provision&activation in current network environment:

Open

Two classes of service provision?

• Short workflow service: when a customer requests this kind of service, BSS sends service activation instruction to the corresponding NE

• Long workflow service: when a customer requests this kind of service, BSS sends service order ticket to OSS, service provision system/function of OSS schedules three main function/system to achieve: (1)resource request; (2)workforce scheduling; (3)service activation

In NFV/SDN network environment,  based the original workflow for service provision, one function “service orchestration” must be added

In NFV/SDN network environment,  based the original workflow for service provision, one function “service orchestration” must be added, “service orchestration” function apply VM resource\deploy NS/VNF\config NS/VNF\etc..., especially for vCPE\eBOD\etc… services

Open

The new service provision system/function schedules four main function/system:

• (1)resource request

• (2)workforce scheduling

• (3)service Orchestration: newly added

• (4)service activation

Why suggest ONAP implements these functions?

These functions are implemented in BSS/OSS traditionly, then why suggest ONAP implements these functions? (1)BSS is confused about which service is provioned by OSS or ONAP; (2)Some requirements require ONAP to interface with PNF(for example: 5G slicing); (3)Along with more PNFs transformation to VNFs, all functions of OSS will be merged in ONAP.

Proposal about service provision system/function architecture

Proposal about service provision system/function architecture:

Proposal about service activation system/function architecture

Proposal about service activation system/function architecture: