• No results found

Voice Service Provider On Boarding Proposal v.1.4

N/A
N/A
Protected

Academic year: 2021

Share "Voice Service Provider On Boarding Proposal v.1.4"

Copied!
18
0
0

Loading.... (view fulltext now)

Full text

(1)

Voice Service Provider

On Boarding Proposal

(2)

Page 2 of 18

Document Revision

Prepared by KK HAN

Review By Jason Su

Approve By Jacky Duweihua

Issue Details Date Author

1.0 Initial Draft 26/4/2012 KK Han 1.1 Updated as per UFF

comment 4/5/2012 KK Han 1.2 Updated after

internal review 7/5/2012 KK Han 1.3 Updated as per UFF

comment 20/5/2012 KK Han 1.4 Minor Typos,

(3)

Page 3 of 18

1.

Table of Contents

1 Scope and Purpose ... 4

1.1 Document Purpose ... 4

1.2 Scope ... 4

2 Introduction ... 4

3 VSP On-Boarding Processes ... 5

3.1 On-Boarding Workshop ... 5

3.2 Test Facility Engagement in ITF lab ... 6

3.3 Generic Test Case Review ... 6

3.4 Custom Tailored Interoperability Test Plan ... 7

3.5 Test Facility Build ... 7

3.6 ITF Readiness Review ... 7

3.7 Interoperability Test Commencement ... 8

3.8 VSP Certification Certificate ... 8

4 E-NNI Specifications ... 9

4.4 CIR Requirement at NNI ... 12

5 UNI-V Specifications ... 13

5.1 ATA POTS ... 13

5.2 Layer 3 Connectivity ... 13

5.3 VLAN Configuration ... 14

5.4 Bandwidth Management for Voice Virtual Connection ... 14

5.5 Supported Telephony Features ... 14

5.6 Digit Map and Dial Plan Configuration ... 15

5.7 DTMF ... 15

5.8 Service Tones ... 16

6 Integration Test Facilities (ITF) ... 17

6.1 ITF NNI Connectivity Method ... 18

(4)

Page 4 of 18

1 Scope and Purpose

1.1 Document Purpose

This document describes the functional process and high level operational aspects of the Voice Service Provider (VSP) on boarding in the UFF open access network. This document sets out interoperability guidelines and procedures that are required to be undertaken by an Access Seeker (VSP in this case) in order to gain certification to connect to the UFF open access network before commencing live service to the end user.

It is intended for a technical audience, who are responsible for integrating UFF open access network infrastructure with various VSP.

1.2 Scope

This document should be read in conjunction with the following UFF publications:

• SIP ATA Interoperability Testing Technical Requirements

• EchoLife HG8240 GPON Terminal Product Description-(V100R003C00&C01_02)

2 Introduction

UFF Open Access Network is a wholesale-only Ethernet access product that delivers Layer 2 bit-stream services across a range of access technologies namely GPON/FTTH.

The product in UFF network implements the IEEE802.1ad Provider Bridges VLAN addressing scheme for the operation of point-to-point and multipoint Ethernet Virtual Circuits using Passive Optical Network (PON) access

(5)

Page 5 of 18

technologies, suitable for residential, business and infrastructure applications.

The services are constructed from a number of modular product components, each with a different set of attributes and rules. These components are structured to ensure a high degree of configurability and flexibility, to meet the needs of current and future markets. This document details these components, as well as the processes for deploying the Voice services.

3 VSP On-Boarding Processes

3.1 On-Boarding Workshop

On-boarding workshop is one of the important key points in the whole VSP on-boarding process. This workshop is essential to provide an overview of the elements in the NSP open access infrastructure as well as the end to end architecture design. The workshop helps VSP to have better

(6)

Page 6 of 18

understanding the on-boarding process especially the detailed procedure to integrate their network with the UFF infrastructure during interoperability testing. A working scope between UFF and VSP will be clearly defined in the workshop. The following key elements will be part of the main discussed topic.

a) Specifications of E-NNI and UNI-V.

b) The telephony feature supported by VSP and the testing scope

Note:

The “SIP ATA Interoperability Testing Technical Requirements” should be used as a standard reference for the VSP interoperability test.

3.2 Test Facility Engagement in ITF lab

The voice service provider must notify UFF of their intention to conduct interoperability test at least 1 week (7 days) prior to their preferred test commencement date and testing duration. This is to allow UFF to make proper arrangement to allocate a suitable time slots for the VSP to conduct the test. UFF will review the request and feedback the available dates to the VSP.

3.3 Generic Test Case Review

The interoperability test will be carried is a full functionality test in the Integrated Test Facility (ITF) located in Auckland. UFF will provide the test procedures1 to cover generic test cases to be tested in ITF. The Test Completion Sheet is included in the same document and will be filled in by VSP upon test completion, to record the test result.

1

(7)

Page 7 of 18

VSPs may have their own additional test procedures that they wish to undertake in the ITF lab. UFF will review these test plans together with VSP.

3.4 Custom Tailored Interoperability Test Plan

Upon UFF reviewing the proposed changes to the SIP ATA Interoperability Test Case, UFF will send the Custom Tailored Interoperability Test Plan (ITP) to the VSP. This ITP will contain the detailed test plan related to the services provided by VSP.

3.5 Test Facility Build

Upon receiving the Voice Service Provider Template (VSPT) from VSP, UFF will be responsible for the test facility build in the ITF lab. The build process will involve both a Physical and Logical build with collaboration from the VSP. Physical build will mainly involve the NNI and UNI connection between VSP equipment and UFF POI. UFF will work closely with VSP to resolve any physical or service issues. Logical build will focus on end to end configuration attributes and determine how VSP equipment interfaces with UFF network. These attributes are defined in the Voice Service Provider Template as part of the on-boarding phase and are designed around the VSP technical product requirements Example of the configuration attributes is Codec selection in the ONT e.g. G.711, G.729 etc.

VSP will be given an option to locate their equipment to the ITF lab for the interoperability test or they can opt for connecting their equipment remotely to the ITF lab.

3.6 ITF Readiness Review

After completing the test facility build, UFF will review the ITF build by conducting some basic tests to ensure the build environment is working as per original plan. Some of the items under review in this stage are:

(8)

Page 8 of 18

• End to End service build has been completed in accordance to the detailed ITP.

Basic testing can be performed to prove the connectivity such as PING test to the VSP gateway. Once review and testing is complete, UFF will notify the VSP about the test environment readiness in order for VSP to commence the interoperability test.

3.7 Interoperability Test Commencement

Interoperability testing will be carried out over one or more 5 day blocks based on the agreement defined earlier during ITF lab engagement

process. In the event of any test failure during the interoperability testing, the VSP can resolve the defects in the remaining time blocks. In the case where testing failure is due to the UFF infrastructure or faulty device i.e. ONT issue, UFF will be responsible to troubleshoot the problem together with VSP. However, UFF at their sole discretion may re-run the failed test item. The availability of the ITF to rebook

and retest failed items will depend on the ITF schedule and taking into consideration of the space limitation of the ITF.

In the case where certain failed items were due to incompatibility issue between VSP and UFF equipment and an additional time window is required to rectify the issue, the VSP will need to make arrangement with UFF to engage the ITF for retest purposes.

3.8 VSP Certification Certificate

Upon successfully completion of Interoperability test and submission of Interoperability test Report, VSP certification certificate will be issued to VSP.

(9)

Page 9 of 18

4 E-NNI Specifications

NNI

The Network-Network Interface (NNI) is a physical interface that is used to deliver one or more Connectivity VCs to the VSP. The NNI physical interface will be cabled to an Optical MDF within an UFF Point of Interconnect facility. The VSP is expected to interface the NNI directly to their backhaul, or local networking equipment for connection to their network.

E-NNI Requirement

There are a number of requirements which need to be predefined before the interconnection is completed at the POI interface. These requirements will be defined clearly to streamline the interoperability test process with the VSP. Some of the fundamental requirements are outlined below:

NNI interface attribute

NNI port negotiation mode

POI node resiliency

Voice CIR requirement

4.1 NNI Interface Attributes

The interface between the VSP edge equipment and the UFF Point of Interconnect (POI) may vary from one location to another and needs to be specified prior to any interconnectivity between the VSP and UFF network can be established.

These interface varieties can be one of the following:

1Gbit/s Interface Name

(10)

Page 10 of 18

1000BASELX Single mode of Multimode fiber

8B10B NRZ coded signaling, multi-mode fiber (up to 550 m) or single-mode fiber (up to 2 km; can be optimized for longer distances, up to 10 km).

1000BASET Cat5 cable Copper cabling with four twisted pairs. Each pair is used in both directions

simultaneously.

10Gbit/s

Interface Name Medium Description

10GBASELR/LW Single Mode fiber supports 10 km over single-mode fiber

10GBASEER/EW Single Mode fiber supports 40 km over single-mode fiber

4.2 NNI Port Negotiation Mode

Auto-Negotiation - The VSP selects the POI interface Line Rate to be set by auto-negotiation between the UFF POI and the VSP equipment

Fixed – The VSP specifies the desired Line Rate for the E-NNI. The fixed mode is required in the case where link aggregation is configured.

4.3 POI Node Resiliency

To maintain the high availability across the NNI, a number of resiliency options are available for VSP selection

(11)

Page 11 of 18

4.3.1 Single Chassis

Single Chassis configuration allows a VSP to logically bundle a number of physical NNI off the same POI chassis. Under this option, a number of physical links will be bundled together to form a logical links relationship, allowing a load-shared or active/standby operation. For example, if a physical link within the NNI group goes down, its load will be transferred to the remaining links within the group. In best practice, the aggregated links of the NNI group terminating across different line cards to maintain higher level of redundancy, nevertheless, this cannot be guaranteed.

4.3.2 Enhanced Trunk (E-Trunk)

Enhanced Trunk (E-Trunk or Multi-Chassis LAG), an extension from the Link Aggregation Control Protocol (LACP), is a mechanism that controls and implements link aggregation among multiple devices. E-Trunk implements device-level link reliability, instead of board-level link reliability

implemented by LACP.

For example, if an NNI group has a total of 4 physical NNI, then two will be provisioned on one chassis, and two on another. One chassis will be active, the other standby. If a failure occurs within any one of the active links, then a full switchover to the standby chassis will occur.

4.3.3 Geographical Redundancy (GR)

A NNI group may be delivered across different Point of Interconnect (POI) sites. For Geographical Redundancy, the interfaces will be grouped into an active/standby relationship (as per Multi Chassis LAG), defined at the site level. For example, if an NNI group has a total of 4 physical NNI, then two will be provisioned in one site, and two in another. One site will be active, the other standby. If a failure occurs within any one of the active links, then a full switchover to the standby site will occur.

In the GR scenario, VSP can have option to connect their edge equipments to both of the POIs in order to enhance the network reliability.

(12)

Page 12 of 18

4.4 CIR Requirement at NNI

The table below explains the bandwidth requirements for different codec’s used in compressing voice packets. The presentation of these tables only acts as a reference point for VSP bandwidth planning.

A codec (compressor/decompressor) is a module (software or hardware) that uses a mathematical algorithm to compress, and decompress, the bit stream that is the digital representation of the analog sound signal. The various codec’s output the digitized audio at different bitrates.

CODEC Bit Rate(kbps) Sampling Period (ms) Packet Size (Bytes) Bandwidth (kbps) G.711a/u 64 10 134 104.7 G.711a/u 64 20 214 83.6 Consideration Point:

The bandwidth requirement depicted from the table is a theoretical value when different codec is used.

The digitized output of the codec is carried in an Ethernet frame containing an IP/UDP and RTP packet header. Codec configured to operate with smaller sample times must send more IP packets than those configured to operate with larger sample times. More IP packets mean more overhead resulting in an overall greater bandwidth. The voice signaling in the packet will also form part of the signaling overhead which consumes bandwidth as well.

Huawei recommends 150 Kbps for single voice channel. However, in real production deployment, the total bandwidth requirement at E-NNI will depends on the contention ratio which is managed by the VSP and may vary from one VSP to another.

(13)

Page 13 of 18

5 UNI-V Specifications

5.1 ATA POTS

Each ATA POTS provides a standard analogue telephony port for the provision of POTS services via IP Telephony. Each ATA POTS port is associated with the same SIP User Agent.

5.2 Layer 3 Connectivity

The VSP is responsible for the layer 3 connectivity of the ATA WAN interface. There are a number of mechanisms to obtain IP address for the SIP user Agent on the ONT. The IP allocation can be done dynamically via DHCP or PPPoE or statically through manually assignment of a fix IP address.

Static IP address For Static IP interfaces, the IP address and CIDR mask is predefined

DHCP For DHCP interfaces, DHCP broadcast message will be sent to DHCP server to obtain the IP address on ATA. VSP shall provide DHCP server infrastructure and assign the following parameters:

L IP Address (IPv4) L Subnet Mask

L Default Router Address (IPv4)

L DNS server (required if a hostname is used for proxy server SIP URI)

(14)

Page 14 of 18

DHCP option82 will be an optional feature to obtain an IP address in a secure manner. If this feature is enabled, DHCP Option 82 fields will be populated in the DHCP packet when obtaining IP address from DHCP server.

5.3 VLAN Configuration

1: 1 VLAN scheme will be adopted at ATA POTS per ONT where a WAN connection will be configured for a transport Voice virtual connection (VC). At the NNI, this 1: 1 VLAN will be identified with SVLAN/CVLAN combination.

5.4 Bandwidth Management for Voice Virtual Connection

Each ONT will have at least one virtual connection (VC) to carry the voice service over the Layer 2 network. The bandwidth requirement for the VC will need to be dimensioned for the aggregate concurrent voice channel plus additional bandwidth for voice signaling as per the requirements of the VSP. The total bandwidth required for the VC will based on the different codec used by VSP to compress the voice channel. The bandwidth calculation will reflect the CIR requirement on the NNI at POI.

5.5 Supported Telephony Features

Most IP-based telephony features are implemented in the VSP softswitch infrastructure. However, certain telephony features involve ONT support through different electrical characteristics on the ATA POTS Interfaces. Some of the following features are supported by the ONT which comprise of:

Call Waiting

Calling Number Display

Call Blocking (Calling Number Blocking) Distinctive Ring

(15)

Page 15 of 18

5.6 Digit Map and Dial Plan Configuration

Digit map syntax definition is used by the VSP to define phone specific dialing behavior. A phone dial plan is important for the phone to know when an entered number is complete and therefore the call should be initiated. If not the phone needs to know that dialing needs to be manually initiated by pressing the Dial soft key. If the phone digit map is defined wrong, the phone might start to dial before the correct number of digits was entered.

Since numbers on the PSTN vary in length, specific patterns must be recognized to minimize post-dialing delays. Patterns are region specific and it is the VSP responsibility to ensure an appropriate dial plan is initially provisioned and, importantly, maintained for telephony End-Users. VSP may also use the dial-plan to provide “special” access numbers such as short dialing between branch offices or for internal services such as voicemail.

5.7 DTMF

The ATA integrated within the ONT supports both in-band and RFC2833 for DTMF tone detection and transmission across an IP network. UFF recommends Access Seekers implement in-band DTMF detection.

(16)

Page 16 of 18

5.8 Service Tones

The following service tones are provided by each POTS ATA:

Service Tone Description Frequency Cadence

Dialtone The dial tone

indicating the line is ready to accept digit input.

400Hz Continuous

Ringtone The tone used to

indicate the called party is in the ringing state

400 Hz 400 Hz plus 450 Hz interrupted,

Busy tone The tone which is used to indicate the called party is busy

400Hz 400 Hz interrupted, 500 ms on, 500 ms off, repeated Disconnect

tone:

The tone to indicate the call is disconnected 400 Hz 400 or 900 Hz interrupted, 250 ms on, 250 ms off, repeated Note:

Please refer to EchoLife HG8240 GPON Terminal Product Description-(V100R003C00&C01_02) for overall HG8240 ONT specifications.

(17)

Page 17 of 18

6 Integration Test Facilities (ITF)

The Integrated Test Facility (ITF), located in Auckland aims to provide a mirrored environment of the production network which will support various kinds of testing. The VSP will be given an opportunity to utilise the ITF for the interoperability test before actual service deployment in the production network. All the testing will be recorded and a test report is required to be submitted to UFF as per on boarding agreement.

(18)

Page 18 of 18

The ITF will provide facilities such as Test line, telephone, internet connectivity for VPN purposes to the VSP. The VSP may allocate their own testing resources during the testing period and UFF will allocate resources to assist the interoperability testing.

6.1 ITF NNI Connectivity Method

Depending on the VSP test requirements and cost consideration, there are a number of options available for interfacing their equipment to the UFF ITF. If the VSP opt for the option to physical place their edge equipment to the ITF, a secure facility is provided to house their equipment. In this case, direct fiber will be used to connect VSP equipment to UFF NNI interface. This option will greatly reduce the upfront provisioning cost. Alternatively, certain VSPs may choose to perform NNI connectivity testing via a remote link.

6.2 ITF Service Testing Scope

The scope of the testing in ITF has been defined earlier in the VSP on-boarding processes where an Interoperability Test Plan is produced after both UFF and VSP review the generic test case and any additional test cases. In general, the test cases covered in ITF will be completely functional for all services.

References

Related documents

March 2020 - A number of EAA chapters have contacted headquarters regarding guidance, options, and cautions regarding chapter events, in conjunction with the coronavirus.. Here is

In Section 5, we apply our method to study the determinants of economic growth in the framework of dynamic panel data models with interactive fi xed e ff ects, and fi nd that in

Pengertian Penyerapan tenaga kerja merupakan jumlah tertentu dari tenaga kerja yang digunakan dalam suatu unit usaha tertentu atau dengan kata lain penyerapan tenaga kerja

Financial savings proposed for the consolidation of all destinating mail volumes from the Beaumont TX P&DF into the North Houston TX P&DC are:.. Total First Year Savings

Fleet pilots will record the time for which they are the PIC of record on a particular aircraft by using the OAS-2 form to record the start date and start/stop meter times..

Any financial institution – be it a securities firm, an insurance company, a hedge fund, a private equity firm, or a bank holding company – which is not now subject to the

Explore the histories of key global commodities through a wide range of manuscript sources, rare books, maps, advertising memorabilia, paintings, photographs and ephemera.

To determine the physical condition abilities of taekwondo athlete who was training at a special preparation stage, it was measured: ability of leg muscles strength with