Version 4.0 NOTE: For a more detailed description of each process step within these flows, please...

Version 4.0

• NOTE: For a more detailed description of each process step within these flows, please refer to the accompanying Inter-Service Provider LNP Operations Flows Narratives (Version 4.0)

• NOTE: Pursuant to FCC Order 07-188, released on November 8, 2007, and FCC Order 09-41, released on May 13, 2009, Local Number Portability (LNP) obligations are extended to interconnected Voice over Internet Protocol (VoIP) providers. The North American Numbering Council (NANC) identifies three classes of interconnected VoIP providers, defined as follows:

Class 1: A standalone interconnected VoIP provider that obtains numbering resources directly from the North American Numbering Plan Administrator (NANPA) and the Pooling Administrator (PA) and connects directly to the PSTN (i.e., not through a PSTN LEC partner’s end office switch). Class 1 standalone interconnected VoIP providers must follow the

appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Network Service Provider (NNSP) or Old Network Service Provider (ONSP), whichever is applicable.

Class 2: An interconnected VoIP provider that partners with a facilities-based Public Switched Telephone Network (PSTN) Local Exchange Carrier (LEC) to obtain numbering resources and connectivity to the PSTN via the LEC partner’s end office switch. A Class 2 interconnected VoIP provider is not considered a reseller in the context of the FCC definition of a

Simple Port (refer to FCC Order 07-188 and FCC Order 09-41 for Simple Port definition). Class 2 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable.

Class 3: A non-facilities-based reseller of interconnected VoIP services that utilizes the numbering resources and facilities of another interconnected VoIP provider (analogous to the “traditional” PSTN reseller). A Class 3 interconnected VoIP

provider is not considered a reseller in the context of the FCC definition of a Simple Port (refer to FCC Order 07-188 and FCC Order 09-41 for Simple Port definition). Class 3 interconnected VoIP providers must follow the appropriate Wireline- Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable.

North American Numbering Council (NANC)Inter-Service Provider LNP Operations Flows

End UserContact with

NLSP

End UserAgrees tochange to

NLSP

1

2

NLSP obtainsEnd User

authorization

3

Is this aWireless-Wireless

Port?

6

No

8

Proceed toFigure 3Step 1

5

Yes

Is thisa

Simple Port?No

(Optional) NLSPrequests CSR

from OLSP

Yes


97

Inter-Service Provider LNP Operations Flows - Port Type Determination -

Figure 1 Version 4.0

4


Inter-Service Provider LNP Operations Flows-Simple Wireline-Wireline and Intermodal (including Interconnected VoIP)-

-LSR/FOC Process-


NotifyInterconnected VoIP

Provider

Figure 7

8

Is additional

Non-Simple dataneeded for LSR?

9

NLSP sends LSR orLSR information to

NNSP for interconnection

service

12

Yes

No

2

NNSP sends LSRfor Simple Port

to ONSP

3

Is NLSPa Class 2 or

Class 3 InterconnectedVoIP

Provider?

Yes

(conditional) ONSPsends LSR, LSR

information, or LossNotification to OLSP

No

ONSP returns LSRto NNSP with

request forapplicable

Non-Simple data

5

(conditional) OLSPsends FOC or FOC

information to ONSP

1

Is NLSPa Class 2 or


Provider?

NNSP forwardsFOC or FOCinformation to

NLSP

6

Yes

No

13

SIMPLELSR-FOC

4

Is OLSPa Class 2 or


Provider?

Yes

11

ONSP sends FOCconfirming Simple

Port request to NNSP

DD

7

DoesONSP confirm

this as aSimple Port?

No

Yes

ONSP sends FOCwith appropriate

Due Date for Non- Simple Port to NNSP

10

EE

Inter-Service Provider LNP Operations Flows-Non-Simple Wireline-Wireline and Intermodal (including Interconnected VoIP)-

-LSR/FOC Process-


Notify Reseller orInterconnected VoIP

Provider

Figure 7

6

Is OLSPa Reseller or Class 2 orClass 3 Interconnected

VoIPProvider or is a Type 1

wireless number involved?

9

NON-SIMPLELSR-FOC

NLSP notes “notall TNs beingported” in the

remarks sectionof LSR

10

Yes

No

2

NNSP sends LSR

to ONSP

5

Is NLSPa Reseller or Class 2 orClass 3 Interconnected

VoIPProvider?

No

(conditional) ONSPsends LSR, LSR

information, or LossNotification to OLSP

NoONSP sends

FOCto NNSP

7

(conditional) OLSPsends FOC or FOC

information to ONSP

1

NNSP forwardsFOC or FOCinformation to

NLSP

8

Yes

Yes

11

NLSP sends LSR orLSR information toNNSP for resale or

interconnectionservice

4

Yes

3

Is NLSPa Reseller or Class 2 orClass 3 Interconnected

VoIPProvider?

NoIs

end-userporting all

TNs?

DD EE

Inter-Service Provider LNP Operations Flows-Wireless ICP Process-


4

Is a Type 1wireless number

involved?

5

ICP

OLSP sends WPRR orWPRR information to

ONSP

No

10

ONSP sends WPRR

to NNSP

16

Yes

ONSP sends WPRR rejectionto NNSP

NNSP forwardsWPRR or WPRR

Information to NLSP

15

Is WPRRconfirmed?

WPRR is a Resolutionresponse

Yes

No

17

Yes

1

Is NLSPa Reseller?

No

2

NLSP sends WPR orWPR information to

NNSP for resale service

ONSP sends WPR orWPR information to

OLSP

9

NNSP sends WPRto ONSP

3

Yes

Is OLSPa Reseller?

No

11 12

Yes

Is NLSPa Reseller?

13

No

14

Yes

Is WPRRa delay?

No

8

Yes

Is OLSPa Reseller?

No

NOTE: No changes were made to this flow.

Inter-Service Provider LNP Operations Flows- Main Flow -


Notify Reseller/Interconnected VoIP

Provider

NPAC notifiesNNSP and ONSP

that port is canceledFigure 7

11

Wasport requestcanceled?

Is NPACprocessingrequired?

Yes

No

NNSP coordinatesall portingactivities.

Perform intra provider port or

modify existing SV

Yes

6

3

4

No

NNSP and ONSPcreate and process

service orders

2

5

9

DidONSP placethe order in

conflict?

1

AreNNSP andONSP the same SP?

13

NPAC logs requestto place the order

in conflict,including cause

code

AA

Create

Service ProviderPort Request

Figure 6

No

Yes

Yes

7

NNSP coordinatesphysical changes

with ONSP

12

No

10

A BB

Yes

Z

No

Is theUnconditional10 digit trigger

beingused or does ONSP

query onevery call?

B

End

8

NOTE: Changes are

indicated in red.

ICP

NON-SIMPLELSR-FOC

SIMPLELSR-FOC

Inter-Service Provider LNP Operations Flows-Subscription Version Create Flow-


4

Is Create

messagevalid?

6

Create

NPACstarts T1

timer


that T2 hasexpired

Return to Figure 2Step 13

Yes

1

No

2NNSP and

(optionally) ONSPnotify NPAC withCreate message

3

No

Yes

Is Createmessage

valid?

DidNNSP send

Create?

No

7

Yes

ReceivedsecondCreate?

No

NPAC notifiesappropriate

service providerthat Create

message is invalid

8

Return to Figure 2Step 13

Yes

15

NPAC notifies theONSP that porting

proceeds underthe control of the

NNSP

20

T1expired?

5

Yes

No

HasCancel window

for pendingSVs

expired?

No

No



message is invalid

9

12T2expired?

11

Yes


that T1 hasexpired and thenstarts T2 timer

19No Is

Create messagevalid?

No13

16

YesReceivedsecondCreate?

Yes

Yes

17



Message is invalid

10

Notify Reseller/Interconnected VoIP

Provider


that port is canceledFigure 7

18

14

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Reseller/Interconnected VoIP Provider Notification-


4Is NLSP a

Reseller orClass 2 or 3

InterconnectedVoIP Provider?

NotifyReseller/

InterconnectedVoIP Provider

Yes

3

2

NNSP sends orprovides

information and/ormessage to NLSP

No

Return

Yes

7

DoesNLSP needmessage?

No

Is OLSP a



1

Yes

DoesOLSP needmessage?

ONSP sends orprovides

information and/ormessage to OLSP

5

6

No

Yes

No

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Provisioning Without Unconditional 10-Digit Trigger-


NOTE: No changes were

made to this flow.

Z

A

3 4 8 9

2

5

6

7

1

NNSP notifiesNPAC to activate

the port

NNSP activatesport (locally) NPAC downloads

(real time) to all service providers

NPAC records date and time in history

file

ONSP removes translations in

central office or switch/HLR

NPAC logs failures and non-responses

and notifies the NNSP and ONSP

All service providers update routing data (real time download)

NNSP may verify completion

NNSP and ONSPmake physical

changes (wherenecessary)

Inter-Service Provider LNP Operations Flows-Provisioning With Unconditional 10-Digit Trigger-


NOTE: No changes were

made to this flow.

Z

AA

2 4 5

9

3

6

7

1

NNSP activates central office translations

ONSP activates unconditional 10

digit trigger in the central office

NPAC downloads (real time) to all service providers

NPAC records date and time in history

file

ONSP removesappropriate translations

All service providers update routing data (real time download)

NNSP and ONSPmake physical

changes (wherenecessary)

10

NNSP may verify completion

8

NPAC logs failures and non-responses

and notifies the NNSP and ONSP

NNSP notifiesNPAC to activate

the port

Inter-Service Provider LNP Operations Flows-Conflict Flow For The Service Creation Provisioning Process-


C

9

Yes

Is conflict

restricted?No

NPAC rejects the conflict request

1

B


Provider

Figure 7

NPAC changes the subscription status

to conflict and notifies the NNSP

and ONSP

210


Provider

Figure 7



and ONSP

BB

6Notify Reseller or

Interconnected VoIPProvider

Figure 7

NPAC rejects theconflict resolution

request from NNSP

Z

3

NNSP contactsONSP to resolve

conflict. If noagreement is

reached beginnormal escalation.

4

Wasthe Conflict

Cause Code50 or 51?

No

BB

5Was

ConflictResolved within

ConflictExpiration window?

Yes

7

Did NNSPsend resolution

message during therestrictionwindow?

No

Yes

Yes

No

12

Wasport

request canceledto resolveconflict?

8

Yes

No



and ONSP

NoYes

11

Wasresolution

message fromONSP?

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Cancellation Flow For Provisioning Process-


Didend-usercontactNLSP?

End-userrequest to

cancel

8

2


Provider

Figure 7

NPAC updatessubscription to cancel

logs status changeand notifies NNSP

and ONSP

10

18

NNSP sends SUPPto ONSP notingcancellation as

soon as possibleand prior to activation

3

C

DidNPAC receive

cancel ACK fromNNSP within firstcancel window

timer?

No

Yes

No

NPAC notifiesNNSP that cancel

ACK is missing

OLSP sendscancel request

to ONSP

NLSP sendscancel request

to NNSP

ONSP sends cancelrequest to NPAC

NNSP sends cancelrequest to NPAC

5

Didthe provider

requesting cancelsend a Createmessage to

NPAC?

Yes

NPAC notifiesONSP that

cancel ACK ismissing

DidBoth NNSP and

ONSP send CreateMessage to

NPAC?

No

DidNPAC receive

Cancel ACK fromONSP within firstCancel window

timer?

No

DidNPAC receive

cancel ACK fromNNSP within second

cancel windowtimer?

DidNNSP send

cancel toNPAC?

No

OLSP obtainsend-user

authorizationNotify Reseller or

Interconnected VoIPProvider

Figure 7



and ONSP

20

NPAC rejects the cancel request


Provider

Figure 7

NPAC updatessubscription to cancelpending logs statuschange and notifiesNNSP and ONSP

22

Z

CC

Z

4

Is OLSP a



Yes

No

1

7

Is NLSP a



Yes

No

6

9

Yes

23

Yes

16

21

Yes

Yes

Yes

No

15

No 19

13

17

11

14

12

NPAC waitsfor either

cancel ACK orexpiration of

secondcancelwindowtimer

Inter-Service Provider LNP Operations Flows-Cancellation Ack Missing from New Provider Provisioning Process-


3

DidNPAC receive

Cancel messageFrom NNSP?

NNSP notifiesNPAC to cancelthe Subscription

2

cc


Provider

Figure 7

NPAC notifiesNNSP and ONSPof conflict off via

SOA BB

4


Provider

Figure 7

NPAC rejects theresolve conflict

request from NNSP

Z

1

No

6

Hasconflict

expiration windowexpired?

Yes

HasNNSP conflict

resolutionrestriction expired?

YesYes

No

10

NPAC updatessubscription to

conflict, logs conflictand notifies NNSP

and ONSP


cancel, logs canceland notifies NNSP

and ONSP


Provider

Figure 7

5

No

7

Did NPACreceive resolve

conflict message from NNSP?


cancel, logs canceland notifies NNSP

and ONSP


Provider

Figure 7

Yes

No

8

9

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Disconnect Process For Ported Telephone Numbers-

Figure 13 Version 4.0Disconnect

End-userInitiates

disconnect

Haseffective

release datebeen reached?

1

No

4

8

NNSP initiatesdisconnect

No

5

NNSP arrangesintercept

treatment whenapplicable

6

NNSP createsand processesservice order

7

NNSP notifies NPACof disconnect date

and effectiverelease date

9

NPAC broadcastssubscriptiondeletion to all

applicableproviders

Is NLSPa reseller

or Class 2 or 3InterconnectedVoIP Provider?

2

Yes

12

NPAC deletes TNfrom activedatabase


Provider

Figure 7

10

NPAC notifiescode/block holderof disconnected

TN disconnect and release dates

3

NLSP sendsdisconnectrequest to

NNSP

Yes

11

EndNOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Audit Process-

Figure 14 Version 4.0Disconnect

Are allAudits

completed?

3 5

NPAC comparesown subscriptionversion to LSMS

subscription version

No

2

NPAC issuesqueries to

appropriate LSMSsYes

7


Provider

Figure 7

6

NPAC reportsaudit completion

and discrepanciesto requestor

End

4

NPAC downloadsupdates to LSMSswith subscription

versiondifferences

1

Service providerrequests an audit

from NPAC

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Code Opening Process-

Figure 15

Version 4.0Disconnect

Firstsubscription

version activityin NPA-NXX?

3

3

NPAC comparesown subscriptionversion to LSMS

subscription version

No

2

NPAC issuesqueries to

appropriate LSMSs

Yes

4


Provider

Figure 7

4

NPAC sendsnotification of

first TN ported toall providers viaSOA and LSMS

End

1

NPAC successfullyprocesses create

request for TNsubscription version

5

End

-First TN Ported in NPA-NXX-

Figure 16

2

NPAC successfullyprocesses create

request forNPA-NXX-X

1

NPA-NXX holdernotifies NPAC of

NPA-NXX code(s)being opened for

porting

NOTE: Changes are

indicated in red.

Inter-Service Provider LNP Operations Flows-Cancel-Undo Process-

Version 4.0Disconnect

Did theprovider requesting

a cancel-undo issue acancel for thissubscription?

4

No

Yes

6


Provider

Figure 7

3


status prior to canceland notifies

NNSP and ONSP

End

Figure 17

1

NPAC rejects thecancel-undo

request

NOTE: Changes are

indicated in red.

Providerrequests a

cancel-undo

Is thesubscription incancel-pending

status?

2

No

5

Yes

Version 4.0 NOTE: For a more detailed description of each process step within these flows, please...

Documents

Transcript of Version 4.0 NOTE: For a more detailed description of each process step within these flows, please...