BT Wholesale B2B

BT Wholesale offer a B2B XML gateway for access to all products/technologies including FTTP, SoGEA, SOGFAST and SOADSL. The B2B gateway uses ebXML standards.

The Fibre Cafe has a connector to integrate with this gateway.

BTWHOLESALEB2B Connector (Tenant API 1.7 / Tenant Updates API 1.5)

The initial connector was created for use with the Tenant API version 1.7 and the Tenant Updates API version 1.5

Authentication

Authentication with the gateway is CPA/key based. As part of setting up the connector, we will require the following information:

• Reseller DUNS
• Buyer DUNS
• Account number AKA "SellerAssignedAccountID"
• Private key
• CPA XML file from BT
• Cert and key for BBAC (optional)
• For testing purpose, the BT Wholesale Emulator "Onramp" username/password credentials.

Address Search

Address look up will be available soon.

Service Availability

Only service specifications and information around existing lines are provided.

Additional address information, installation types, constraints, service ready date and unavailability reasons are not provided.

Information on different levels of installation type (e.g. 1 or 2 stage) are not currently returned.

Existing ONT information includes the following (as provided by BT):

• ONT Reference
• ONT Location (Floor/Room/Position)
• ONT Port Type and Status

Stopped date is given for stopped copper lines.

Appointing

When a managed install is required e.g. for a new line or ONT, appointment timeslots can be listed and reserved.

Timeslots are classified as weekday, saturday, sunday and AM/PM.

Expedited appointments and premium site visit reasons can not yet be specified.

Orders

The following service characteristics are required when placing orders:

• LINE_PROFILE : see below for values
• RETAILER_ID : unique identifier for the retailer provided by OFCOM

These service characteristics are optional according to the order:

• MINIMUM_SPEED : requested guaranteed minimum speed (real-time)
• ECC_CHARGEBAND : Excess construction charges - see below for values
• TRC_CHARGEBAND : Time related charges - see below for values
• CARE_LEVEL : see below for values

Amendment and cancellation requests can be made for inflight orders. There are limitations to what amendments can be done with BTW B2B - the following are permitted:

• Change appointment
• Update contact details
• Update order notes
• Change to ECC _ CHARGEBAND or TRC _ CHARGEBAND characteristics

Line Profiles

For BTW B2B, line profiles map to access technology and downstream/upstream speeds as follows:

(SOADSL line profiles tbc)

Excess Construction Charges

The default chargeband where not provided is 0.

Time Related Charges

The default chargeband where not provided is 0.

Care Levels

The default care level for SOGEA orders is 0; for FTTP orders is 2.

Order updates

BTW provide the SERVICE_ID or the LINE_ID as appropriate in a service characteristic:

{
  "entity": {
    "serviceOrderItem": {
      "serviceCharacteristics": [
        {
          "name": "SERVICE_ID",
          "value": "BBEU12345678"
        }
      ]
    }
  }
}

Supplier notes are attached to KCIs as received from BTW (free text). For example:

{
  "entity": {
    "supplierNotes": [
      {
        "note": "Lorem ipsum dolor sit amet...",
        "type": "Site Visit Notes",
        "created": "2024-05-21T17:02:19.652Z"
      }
    ],
    "information": {
      "type": "ADDITIONAL",
      "text": "Adhoc Note to CP",
      "supplierCode": "550"
    }
  }
}

Unsolicited Ceases

Unsolicited ceases are used by BTW and will be sent as an unsolicited cease KCI.

An initial CREATED KCI will be sent once the gateway has received the unsolicited cease, which will be followed shortly by an acknowledged KCI - and further KCIs as per the usual order flow. Once the switch is complete, a final completed KCI will be sent.

An example of an initial KCI for an unsolicited cease (some metadata fields omitted for brevity):

{
  "id": "12f59a1e-6911-478c-ad5f-12592752990a",
  "updateType": "INFORMATIONAL",
  "entityType": "UNSOLICITED_CEASE_ORDER",
  "entity": {
    "id": "1234567",
    "orderType": "UNSOLICITED_CEASE",
    "supplier": "BTWHOLESALEB2B",
    "supplierOrderNumber": "1-1124746841144665030934",
    "reason": "CHANGE_OF_CP",
    "serviceId": "BBEU12345678",
    "status": "RECEIVED_BY_GATEWAY",
    "requestedCeaseDate": "2024-01-01T09:09:33.001Z"
  },
  "information": {
    "type": "CREATED"
  }
}

Unsolicited reappoints

BTW may on occasion re-appoint the order themselves rather than request the tenant reappoints via an ACTION_REQUIRED : REAPPOINT KCI.

In this scenario, this will come through as an unsolicited reappoint: INFORMATIONAL : REAPPOINTED.

The following fields will be in populated within the KCI order:

{
  "entity": {
    "appointmentSupplierReference": "123456543",
    "appointmentTimeslot": {
      "timeslotStartDateTime": "2022-01-10T08:00:00.000Z",
      "timeslotEndDateTime": "2022-01-10T13:00:00.000Z"
    }
  },
  "information": {
    "type": "REAPPOINTED"
  }
}

• appointmentSupplierReference - new appointment reference from BTW
• appointmentTimeslot - new appointment timeslot

If this is not suitable then it can be treated as a REAPPOINT.