This Section describes the technical aspects of interconnection and the associated guidelines covering:

The physical form of interconnection and network aspects including switching, transport, signalling, interfaces, numbering and quality of serviceNetwork interoperabilityOperational and maintenance aspects, including provisioning processes, network operation, fault handling, traffic and routing management billing, operational testing, and safety considerations 

The physical form of interconnection is the linking and interworking of the telecommunications networks/systems of Service Providers which permit their end-users to communicate with one another.

To facilitate the description of physical interconnection, there are two terms that are generally used: 

Access Point (A P) which identifies the location that is a part of the telecommunications infrastructure of a Service Provider which is offered for interconnectionPoint of Interconnection (POI) which is the physical or virtual point on an interconnection link between Service Providers 

There are three main forms of physical interconnection where the Point of Interconnection may be located at:

Site of the Dominant Service Provider – CollocationSite of the other Service Provider - Customer Sited InterconnectionA point in between the sites of the Service Providers - In-span Interconnection 

Interconnection between Service Providers shall be based on the principles of: 

Any- to- any connectivity whereby end-users of a Service Provider are able to communicate with the end-users of any other Service ProviderAvailability at any technically and commercially feasible point 

The RIO of a Dominant Service Provider shall include:

A list of locations and number of Access Points including maps to enable other Service Providers to make efficient choices on the selection of POIs for collection or delivery of traffic The information should include, but not be limited to:Name location and address of exchange or other points of accessType and function of exchange (Local, Service Node, International Gateway, etc.)Vendor of equipment 

The Dominant Service Provider shall maintain details of these Access Points as an annex to the RIO and keep the list and related information updated in an electronic form and make them available when requested.

Relevant technical specifications and standards for each POI:Electrical and physical characteristicsTransmission characteristicsSignallingFunctional capabilities that are being offered via the interfaceInterconnection services offered at the POIInformation on the national numbering groups hosted by each switch accessible through the Access Point or Point of InterconnectionThe option for a Service Provider to connect several Points of Interconnection to one Access Point, or one Point of Interconnection to several Access PointsThe physical form of interconnection available at any specific location, its description and specificationThe time interval for establishing, relocating or removing an Access PointProcedures for changes in the Dominant Service Provider network where alteration to existing POI(s) is expected. The Dominant Service Provider is required to provide other Service Providers with advance notice of any expected changes and seek to minimise any adverse affect on the services provided by the Dominant Service Provider 

Optimum interconnection at the switching level is one of the most significant aspect of network interconnection.

The RIO of the Dominant Service Provider shall:

Address the approach for meeting the switching capacity requirements for interconnection trafficIdentify the rules governing the level at which switching interconnection will take place, e.g. at International Gateway, Service Node or Local ExchangeIdentify interconnection rules for switch diversity 

The Network Interconnection Links connect the networks of Service Providers and facilitate the conveyance of traffic between them. These links are between an Access Point and a corresponding Point of Interconnection. 

Routing considerations for Network Interconnection Links should include: 

Route capacityRoute directionRoute dimensioningRoute segregation 

5.4.1 Route capacity

The RIO shall identify the rules for minimum and maximum capacities and increments in which capacity may be provisioned. 

Network Interconnection Links should not be less than 1 E1. 

Interconnection traffic may be spread over two or more diversely routed Network Interconnection Links in order to maintain interconnection service resilience.

The Dominant Service Provider may require other Service Providers to interconnect at more than one location or to particular location or at particular switching network hierarchy level. Any such requirements must be based on reasonable engineering principles and a justified need to provide network resilience.

5.4.2 Route direction

Network Interconnection Links should be offered with the option of being either uni-directional or bi-directional. 

5.4.3 Route dimensioning

Network Interconnection Links may be either “fully-provisioned” or “high-usage” with congestion considerations as follows:

· A “fully-provisioned” link should be dimensioned such that congestion remains within the established grade of service value during normal busy hour

· A “high-usage” link may be dimensioned such that a reasonable level of congestion (or blocking) is expected and traffic will overflow to available alternative routes

For a “fully-provisioned” link an utilization factor may also be established. Should the utilization of such a link regularly exceed the established utilization factor, then either traffic should be re-routed away from that link or the capacity of the link increased. 

A “high-usage” link should be provisioned with the capability of planned overflow through a “ fully- provisioned” link.

5.4.4 Route segregation

Network Interconnection Links with uni-directional routes segregated by traffic type can provide both protection to certain traffic streams against congestion caused by others and to differing grades of service to particular traffic streams. From a commercial and accounting perspective, it is also simpler to manage.

A Service Provider may require interconnection links not only to the network of the Dominant Service Provider but also to the networks of other Service Providers or for interconnection of its own network equipment, e.g. mobile network base stations.

The Dominant Service Provider shall provide interconnection to its Access and/or Core Transport networks to meet the requirements of other Service Providers.

5.5.1 Transport network technologies

The RIO shall specify the transmission technologies of the Access and/or Core Transport networks to be used for interconnection. 

Service Providers must provide signalling interconnection and ensure call control information is delivered for processing of calls.

Service Providers should support ITU Signalling System Number 7 (SS7) and should ensure that international standards are met and utilization of SS7 links are maintained within the ITU Recommendation.

Service Providers are responsible for the control and access to their signalling networks. Validation Testing of the signalling system should be carried out prior to interconnection.

All Service Providers should cooperate to share the necessary signalling information required for interconnection.

The Dominant Service Provider shall specify signalling interconnection options and the associated configurations.

For the transit of mobile roaming calls to and from other international operators, the Dominant Service Provider shall provide the use of SS7 signalling through its International Gateways as may be required by the other Service Providers.

If required by other Service Providers to facilitate international roaming, the Dominant Service Provider shall provide directly connection to any Signalling Transfer Point of other international operators outside of the Kingdom.

Synchronization is necessary for interconnected networks.

The RIO shall identify: 

The requirement for synchronization with the network of the Dominant Service ProviderThe interconnection links to be used for synchronizationMaximum slip rate and other measures based on ITU standards 

Service Providers should use network interfaces based on internationally accepted technical standards.

The Dominant Service Provider shall specify in the RIO the technical standards for interconnection interfaces.

Service Providers are obliged to notify any modifications in interconnection interfaces and cooperate to overcome any technical problems.

5.8.1 Network interoperability

Interoperability means the technical features of a group of interconnected systems (‘systems’ include equipment owned and operated by the customer which is attached to the public telecommunication network) that ensure end-to-end provision of a given service in a consistent and predictable way.

Interoperability can be defined in terms of the functional delivery of services across networks, it does not necessarily imply that component parts of the systems over which such services are delivered are interchangeable.

Service Providers should agree on the necessary technical features that allow their respective networks to interoperate.

Service Providers should agree on the interoperability testing procedures that verify network integrity and interoperability of functionalities and features of interconnection services.

Service Providers shall provide details of the number ranges which are hosted on each of their exchanges. This should include number ranges allocated but not yet in use.

The Dominant Service Provider shall be responsible for measuring and monitoring the quality of service for interconnection services it provides.

Quality of service indicators should be included in the Service Level Agreement of the RIO.

The Quality of service indicators should include but not be limited to the following and should be as agreed upon in the Service Level Agreement:

Grade of Service during busy hour (blocking probability)Answer - seize ratioTransmission delayTransmission loss (loudness)Noise and distortionEcho and stabilityCross-talkBit error rate​