Release introduced: 23.4

Feature Description

NSP operators can provision a T-BTS L2 BH service in Service Fulfillment using a dedicated T-BTS service intent.

The service intent "tbtsbackhaul" shall be imported in NSP.

On T-BTS L2 BH service creation, the NSP operator specifies the following information:

• Template name : Template created by operator based on_ tbtsbackhaul_ intent

• Service name:

• Customer Id: selected through a pre-defined customer list

• Service description

• outer tag: VLAN ID of the service

• the list of T-BTS part of the service and for each T-BTS, the endpoints to be configured with the VLAN ID (at least two endpoints are required). All endpoints must be provided, with the final and intermediate endpoints along the path.

Notes:

• NSP operators must be aware of physical topology and shall provide final and intermediate endpoint along the physical link.

• T-BTS L2 BH service update, delete and LCM in Service Fulfillment are not supported for services deployed on the BTS.

• NSP Operators must use NetAct to update or delete T-BTS L2 BH service deployed on BTS. The new configuration is available in NSP following resynchronization with the BTS.

• On T-BTS L2 BH service creation failure, the service Deployer State is "Failed" in Service Fulfillment. NSP operators must delete and recreate the service in Service Fulfillment.

• The service creation will not be sent to BTS not configured as repeater.

Customer Benefit

Provisioning of T-BTS L2 BH service on one or several BTS repeater.

Restrictions/Limitations

None.