mismatch is end-user porting all telephone numbers? new service provider notifies old service...

9
mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old Service Provider provides Firm Order Confirmation (FOC) to New Service Provider within 24 hours. Old and New Service Providers create and process service orders End-user Contact End-user agrees to change to New Service Provider New Service Provider obtains end-user Authorization New Service Provider notes “not all TNs being ported” in remarks field on LSR Old (optionally) and New Service Providers notify NPAC. NPAC performs data validation on each individual message. Did NPAC receive both and matching create messages within 9 business hours (t1)? Does NPAC receive create message within 9 business hours (t2)? Is create message missing from New or Old Service Provider? Did Old SP place order in Conflict? NPAC logs no response NPAC notifies appropriate Service Provider that create message is missing. NPAC notifies both Service Providers that transaction is cancelled and change is rejected. New Service Provider coordinates Physical changes with Old Service Provider yes no END timer expired timer expired match no match yes New Old INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS - PROVISIONING - Is data valid? yes Return data to Service Provider Data corrected & forwarded no 4/25/97 NANC ISSUE 1.0 A Is the unconditional 10 digit trigger being used? no yes AA B 1 2 4 6 7 8 3 5 9 10 11 14 18 24 12 16 19 17 13 22 21 20 figure 1 NPAC notifies Old Service Provider that porting proceeds under control of the New Service Provider NPAC logs request to place order into Conflict including cause code. 23 25 BB NPAC notifies appropriate Service Provider that create message is mismatched. 15 26

Upload: miranda-carter

Post on 14-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

mismatch

Is end-user

porting alltelephonenumbers?

New Service Providernotifies Old ServiceProvider of changeusing Local ServiceRequest (LSR)

Old Service Providerprovides Firm Order Confirmation (FOC) to New Service Providerwithin 24 hours.

Old and New ServiceProviders create and process service orders

End-user Contact

End-user agrees tochange to New Service Provider

New Service Provider obtains end-user Authorization

New Service Provider notes “not all TNs being ported” in remarks field

on LSROld (optionally) and New Service Providers

notify NPAC.

NPAC performs data validation on each individual message.

Did NPAC receive both and matching create messages within 9 businesshours (t1)? Does

NPAC receive create message within 9 business hours(t2)?

Is create message

missing from New or Old Service

Provider?

Did Old SP place order in Conflict?

NPAC logs no response

NPAC notifies appropriate Service Provider that create message is missing.

NPAC notifies bothService Providers thattransaction is cancelledand change is rejected.

New Service Provider coordinates Physical changes with Old Service Provider

yes

no

END

timer expired

timer expiredmatch

no

match

yes

New Old

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- PROVISIONING -

Is datavalid?

yes

Return data toService Provider

Data corrected &forwarded

no

4/25/97NANC

ISSUE 1.0

A

Is theunconditional 10 digit trigger

being used?

no

yes

AA

B

1

2

46

7 8

3

5

9

10

11

14

18

24

12

1619

17

13

22

21

20

figure 1

NPAC notifies Old Service Provider that

porting proceedsunder control of the New Service

Provider

NPAC logs requestto place order into Conflict including

cause code.

23

25

BBNPAC notifies appropriate

Service Provider thatcreate message is mismatched.

15

26

Page 2: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

NPAC SMSdownloads (real time)

to all Service Providers

NPAC SMS recordsdate and time in

history file

Old Service Providerremoves translations

in Central Office

NPAC SMS logsfailures and

non-responses, andnotifies Old and New Service Providers of

failures

New Service Provideractivates its C.O.

translations

Old and New Service Providers make physical changes (where necessary)

New Service Providernotifies NPAC to

activate subscription

A

All Service Providersupdate routing data

bases (real-timedownload).

END

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- PROVISIONING WITHOUT UNCONDITIONAL 10-DIGIT TRIGGER -

4/25/97NANC

ISSUE 1.0

figure 2

1 2

3

4

5

6

7

8

New Service Providermay

verify completion9

10

Page 3: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

NPAC SMSdownloads (real time)

to all Service Providers

NPAC SMS recordsdate & time in history

file

NPAC SMS logsfailures and

non-responses, andnotifies Old and New Service Providers of

failures

Old and New Service Providers make

Physical Changes (where necessary)

New Service Providernotifies NPAC to

activate subscription

All Service Providers update routing data bases

(real-time download)

New Service Providermay

verify completion END

4/25/97NANC

ISSUE 1.0

AA

Old Service Provideractivates unconditional 10 digittriggerin Central Office

figure 3

1

New Service Provider activates

C.O. translations.2

3

4

5

6

7

8

10

11

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- PROVISIONING WITH UNCONDITIONAL 10-DIGIT TRIGGER -

Old Service Providerremoves appropriate

translations.

9

Page 4: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

New Service Provider contacts the Old Service Provider to resolveConflict . If no agreement is reached, begin normal escalation.

no

Was conflict resolved

within 30 calendar days ?

yes

4/25/97NANC

ISSUE 1.0

figure 4

Cancel Orders

How was Conflict

resolved?

B

7

9

First time into conflict?

yes

NPAC rejectsconflict request.

6

NPAC initiates cancellation and

notifies bothService Providers

2

Is Conflict

initiated prior to noon the business day

before Due Date?

no

no

yes3

5

NPAC changes the subscription to Conflict Status and notifies both Service Providers

4

8

END

NPAC notifies both Service Providers of conflict off

via SOA 10

“Timeout”

If conflict was resolved within 6 business hours, only the Old Service Provider may notify NPAC of “conflict off” . If conflict was resolved after 6 business hours, either New or Old Service Provider may notify NPAC of “conflict off”.

11

Revert to porting process

BB

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- CONFLICT FLOW FOR THE SERVICE CREATION PROVISIONING PROCESS -

C

BB

12

Page 5: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

End-user

Did end-usercontact Old or NewService Provider?

Old Service Providerobtains end-user

authorization

Old Service Providersends notification toNew Service Provider

New Service Providersends LSR to

Old Provider notingcancellation as soon as

possible prior to activation time.

New Service Providersends notification of

cancellation to NPACif appropriate.

Old

New

Old Service Provider sends cancellation to NPAC, if

appropriate.)

DidNPAC receivenotification(s) within 9 businesshours

NPAC logsinformation,

cancels subscription,and notifies bothService Providers

of cancellation

END

DoesNPAC receive

concurring notification within

9 businesshours?

NPAC notifiesappropriate Service

Provider that information is missing.

no

yes

yes

F

F

4/25/97NANC

ISSUE 1.0

figure 5

1

2

3

4

6

7

9

5

8

10

11

C

H

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- CANCELLATION FLOW FOR PROVISIONING PROCESS -

no

12

Page 6: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

Old

NPAC logs information, place subscription in“conflict status” with proper conflict causecode and notifies both Service Providers.

H

IsOld or New

Service Providercancellation notification

missing or inaccurate?

NPAC logs information, cancels subscription, and notifies both ServiceProviders of cancellation with proper

cause code

New Service Provider notifies NPAC to cancel subscription

NPAC logs information, cancels subscription, and notifies both

Service Providers of cancellationEND

How does New ServiceProvider wish to

continue?

NPAC waits for 30 calendar days, cancels subscription, and

notifies both Service Providers of timeout

New Service Provider notifies NPAC to remove subscription

from Conflict Status

NPAC notifies both Service Providers of conflict off

via SOABB

Cancel Subscription

Ignore

Revert to Pending(Proceed with porting process)

New

4/25/97NANC

ISSUE 1.0

figure 6

1

2

8

7

10

6

5

4

3

9

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- CANCELLATION CONFLICT FLOW FOR PROVISIONING PROCESS -

Page 7: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

Current Service Providerarranges intercept

treatment.

Current Service Providercreates and processesservice order.

NPAC broadcastssubscription deletion

to all applicable Service Providers

NPAC deletes telephonenumber from its active database oneffective release date.

END

4/25/97NANC

ISSUE 1.0

figure 7

End-user1

4

6

9

Current ServiceProvider initiated

disconnect. 2

Current Service Provider

notifies NPAC of disconnect date

and indicateseffective release date.

5

3

NPAC notifies NPA/NXX owner/holder of the disconnected

telephone number(s), effective release and disconnect

dates 7

8

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- DISCONNECT PROCESS FOR PORTED TELEPHONE NUMBERS -

Page 8: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- AUDIT PROCESS -

4/25/97NANC

ISSUE 1.0

Service Providerrequests NPAC for

audit1

NPAC SMS issuesqueries to

appropriateLSMSs 2

NPAC SMS comparesown SubscriptionVersion to LSMS

Subscription Version3

NPAC SMSupdates appropriate

LSMS withSubscription Version

updates 4

All auditscompleted

?5

figure 8

NPAC reportsaudit completion

to requestingService Provider 6

END 7

No

Yes

Page 9: Mismatch Is end-user porting all telephone numbers? New Service Provider notifies Old Service Provider of change using Local Service Request (LSR) Old

INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS- CODE OPENING PROCESSES-

4/25/97NANC

ISSUE 1.0

NPA-NXX Code Opening

NPA-NXX holdernotifies NPAC/SMS

of NPA-NXXCode(s) being opened

for porting1

NPAC SMSupdates itsNPA-NXXdatabases

2

NPAC SMS sendsnotification ofcode opening

to allService Providers

via LSMS 3

First TN Ported in NPA-NXX

NPAC SMS receivessubscription Create

request for first TN inNPA-NXX

1

NPAC SMS sendsnotification of first TN

ported to allService Providers

via SOAand LSMS 2

figure 9