Network Operations

Service Provisioning:

The broadband utility operator shall receive service requests from retail service providers (RSP) for network services through MEF LSO standard APIs. The operator shall validate the service request and ensure that the requested service is available based on the data models defined under the NGSI-LD data formats of the operational digital twin.

  • The operator shall provision the service based on the validated request and ensure that it meets the SLA requirements of the RSP.

  • The operator shall use the OSS/BSS system or NetOps (DevOps) orchestration tools such as Ansible to perform all configuration and updates to provisioning.

  • The operator shall keep all configurations and states of the network provisioning in version control.

  • The operator shall not allow any manual configuration of devices directly performed by personnel.

  • The operator shall provide regular reports to the PCG on service provisioning activities.

The procedures may include the following tasks:

  1. Service request validation:

    • The operator shall receive service requests from RSPs through MEF LSO standard APIs.

    • The operator shall validate the service request based on the data models defined under the NGSI-LD data formats of the operational digital twin.

    • The operator shall ensure that the requested service is available and that the RSP has the necessary permissions to access the network.

  2. Service provisioning:

    • The operator shall provision the requested service based on the validated service request and the SLA requirements of the RSP.

    • The operator shall use the OSS/BSS system or NetOps (DevOps) orchestration tools such as Ansible to perform all configuration and updates to provisioning.

    • The operator shall keep all configurations and states of the network provisioning in version control.

  3. SLA management:

    • The operator shall ensure that the provisioned service meets the SLA requirements of the RSP.

    • The operator shall monitor the service to identify any SLA breaches and take corrective action.

  4. Reporting:

    • The operator shall provide regular reports to the PCG on service provisioning activities, including the number of services provisioned, the SLA compliance, and any issues or challenges faced during the provisioning process.

By following these procedures and utilizing MEF LSO standard APIs and NGSI-LD data formats, as well as utilizing the OSS/BSS system or NetOps (DevOps) orchestration tools such as Ansible, the broadband utility operator can ensure efficient, standardized, and automated service provisioning processes for its RSP customers.

Billing and customer relationship management

The broadband utility operator shall manage all billing and customer relationship management activities as per the agreement with the RSPs. The operator shall:

  1. Generate monthly billing reports for each RSP based on the services consumed by their customers.

  2. Validate the billing reports to ensure accuracy and compliance with the SLA requirements.

  3. Invoice the RSP based on the billing reports and the agreed-upon pricing.

  4. Manage customer relationships on behalf of the RSP, including handling customer inquiries, complaints, and service requests.

  5. Provide regular reports to the PCG on billing and customer relationship management activities.

By following these procedures, the broadband utility operator can ensure accurate and timely billing for RSPs, effective management of customer relationships, and compliance with SLA requirements.

Operation of Layer 2 systems

The broadband utility operator shall be responsible for the operation of Layer 2 systems, including:

  1. Monitoring Layer 2 systems to ensure their availability, performance, and security.

  2. Managing Layer 2 systems using NetOps (DevOps) orchestration tools such as Ansible to ensure consistency and reduce manual errors.

  3. Troubleshooting and resolving issues related to Layer 2 systems, including connectivity, performance, and security issues.

  4. Performing regular maintenance and upgrades of Layer 2 systems to ensure they remain secure and up-to-date.

  5. Documenting all configuration changes and updates to Layer 2 systems in the OSS/BSS system or via NetOps (DevOps) orchestration tools, and maintaining these changes in version control.

  6. Providing regular reports to the PCG on the operation of Layer 2 systems.

By following these procedures, the broadband utility operator can ensure the efficient and effective operation of Layer 2 systems, including their availability, performance, and security.

Product and service development

The broadband utility operator shall be responsible for the product and service development, including:

  1. Developing new products and services based on market trends, customer needs, and the capabilities of the network infrastructure.

  2. Defining the technical requirements for new products and services, including service level agreements, performance targets, and security requirements.

  3. Coordinating with vendors and suppliers to source equipment, software, and services needed to support new products and services.

  4. Integrating new products and services into the OSS/BSS system or via NetOps (DevOps) orchestration tools to enable service provisioning and billing.

  5. Conducting pilot tests of new products and services to validate technical requirements and customer acceptance.

  6. Providing training to customer service representatives, field technicians, and other staff on new products and services.

  7. Documenting all new products and services in the service catalog and updating the catalog as needed to reflect changes to the offerings.

  8. Providing regular reports to the PCG on the development and implementation of new products and services.

Service management and operations

The broadband utility operator shall be responsible for the service management and operations of the network, including:

  1. Monitoring the network and ensuring that all services are functioning properly.

  2. Troubleshooting any issues that arise and resolving them in a timely manner.

  3. Implementing changes to the network as needed to improve performance or to add new services.

  4. Coordinating with vendors and suppliers to obtain necessary equipment, software, and services to support the network.

  5. Ensuring that all network equipment is maintained and upgraded as necessary to maintain optimal performance.

  6. Developing and maintaining procedures for service provisioning, billing, and customer support.

  7. Coordinating with the service desk to ensure that customer issues are resolved in a timely and satisfactory manner.

  8. Providing regular reports to the PCG on the status of the network and the services being provided.

5.6 Resource management and operations

The broadband utility operator shall be responsible for the management and operation of all resources related to the network, including:

  1. Managing the inventory of network equipment, software, and supplies.

  2. Ensuring that all equipment is properly maintained and upgraded as necessary.

  3. Managing the use of network resources to ensure optimal performance and avoid overloading.

  4. Coordinating with vendors and suppliers to obtain necessary resources to support the network.

  5. Developing and maintaining procedures for resource management, including procurement, allocation, and disposal.

  6. Ensuring that all resource-related activities are properly documented and tracked.

  7. Providing regular reports to the PCG on the status of resource management activities.

Network Surveillance Methodology

The network surveillance methodology is the process by which the network is monitored, and any anomalies or issues that arise are identified and resolved. The following steps outline the process for conducting network surveillance:

  • Identify the scope of the network surveillance. This should include the devices, protocols, and services that will be monitored. The scope may vary depending on the size and complexity of the network.

  • Select and configure network surveillance tools. This may include software such as Nagios, Zabbix, or SolarWinds. The tools should be configured to monitor the selected devices, protocols, and services.

  • Monitor the network. The network should be monitored continuously to detect any anomalies or issues that may arise. This includes monitoring for network traffic, device availability, and service availability.

  • Analyze network data. The data collected by the network surveillance tools should be analyzed to identify any anomalies or issues. This may involve comparing current data to historical data to identify trends.

  • Create a ticket for each anomaly or issue identified. A ticket should be created in the ticketing system for each anomaly or issue identified. The ticket should include a description of the issue, the device or service affected, and any relevant data collected by the surveillance tools.

  • Assign the ticket to the appropriate team or personnel. The ticket should be assigned to the team or personnel responsible for resolving the issue.

  • Monitor the ticket. The ticket should be monitored to ensure that it is resolved in a timely manner. The ticket should be updated with any relevant information or actions taken to resolve the issue.

  • Escalate the issue if necessary. If an issue is not resolved in a timely manner or if it requires additional resources, the issue should be escalated to the appropriate team or personnel.

  • Conduct regular reviews of the network surveillance methodology. The network surveillance methodology should be reviewed regularly to ensure that it is effective and efficient. This may involve identifying areas for improvement and implementing changes to the methodology as necessary.

By following this methodology, the network surveillance process can be conducted efficiently and effectively, ensuring that any issues or anomalies are detected and addressed in a timely manner.