Business Requirements for

Version 1.03 Issued: 04 August 2006

Confidential and Proprietary

Syniverse Technologies, Inc., 2006

Document Version 1.03 Issued: 04 August 2006

This material is the exclusive property of, and confidential to, Syniverse Technologies, Inc. Any disclosure or reproduction of this material without Syniverses express prior written consent is strictly prohibited.

The following product and service names, and the Syniverse name and logo are services, software products, service marks and/or trademarks of Syniverse Technologies, Inc.
ACCESS S&E ACCESS ACCESSibility CCNSSM CELLI Commercial Carrier Network ServicesSM CrossroadsSM EDTSM Electronic Data TransportSM Encrypt-A-Key Fleet-On-TrackSM Follow Me Roaming Plus FraudInterceptor FraudManager Fraud Resource CenterSM FraudX GSM SS7 Transport InForum inpackSM INPort INPositionSM LATALinkSM LAWBUST PageNameSM Phone Me Anywhere Plus PMA Plus RoamerXchange SmartChallenge SOLUTIONS Solutions Without Limits S.T.A.R.S. STREAMLINERTM S.T.A.R.S. STREAMLINER Terminal Access Reporting System STARS Special Thanks Awards for Remarkable Service (logo) STARS STARS (logo) StatChek STREAMLINER TransAction Manager Syniverse ConnectionsSM Syniverse DataNetSM UniRoamSM Visibility WIN4SM**

Netscape and Netscape Communicator are registered trademarks of Netscape Communications Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Office and BackOffice are trademarks of Microsoft Corporation. Used by Permission.

As used herein, denotes registration in the United States.

Copyright 2001, 2002, 2003, 2004, 2005, 2006 Syniverse Technologies, Inc. All rights reserved under U.S. and International laws.

Requirements Template V. 4.2 ()

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page i

Document Version 1.03 Issued: 04 August 2006

Revision History Version 1.03 Date 4 Aug 2006 Release Reason - Description of Changes 2.1 removed the word new from 2nd and 3rd line and modified the diagram 2.2 o Wireless Carrier/OSS added as WPR/WPRR and removed (or potentially OSS) o Syniverse Technologies added system and (not content-related fallout). Batching and timing of AS2 files (CII) o Telcordia SMG added conversion between WPR/LSR and WPRR/LSC 3.1 removed the repeated word carrier 3.1.1 modified diagram to match the corresponding use case. 3.1.2 o Step 4 removed up; added ICC and removed a period o Step 8 added that the LEC validates and prepares LSC response o Step 15 added that the Intermodal timer stops 3.1.3 o Step 20 added during business hours 3.2.1 modified diagram to match the corresponding use case 3.2.2 o Step 4 reworded sentence o Step 6 added for logging purposes o Step 7 added that Wireline carrier validates and prepares response o Step 9 added multiple LSC attachments o Step 13 added to SMG o Step 17 added that the Intermodal ICC timer stops 3.2.3 added a space between flow and when 3.2.3.1 in step 23, removed in their OSS 3.3.1 modified diagram to match the corresponding use case 3.3.2 o Step 7 added that the Intermodal ICC timer starts o Step 8 added that the wireless carrier validates and prepares WPRR response o Step 12 changed the start to stop and added ICC 3.3.3 o Added step 11 and made the old step 11 step 12 3.3.4 o Step 8 removed extra period Syniverse Technologies, Inc., 2013 Author Arleen James

Confidential & Proprietary

Page ii

Document Version 1.03 Issued: 04 August 2006

1.02 (includes revisions from 1.01) 1 Aug 2006

Step 9 removed the Wireline carrier and to o Distinguished step 11 (previously in the sentence as step 10) 3.4.1 modified diagram to match the corresponding use case 3.4.2 o Step 2 added unbatches as required. o Step 10 added that the Intermodal timer starts o Step 11 added that the carrier validates and prepares response o Step 15 changed start to stop and added ICC 3.4.3 last sentence changed step 4 to step 3 3.4.4 o Added steps 15 and 16 and changed the last sentence to state step 3 (instead of 4) Changed Wireless and Wireline Operator to be Wireless and Wireline Carrier throughout entire document Changed references to Port Center to Syniverse 1.2 o expanded definition of AS2 o added example of Level 1 Error and Level 2 error o added NSP and OSP and their definitions 1.3 added version/# and/or Date for each external reference document 1.4.1 added this section number to the release revision 2.1 added Overall description and a high-level system interface diagram 2.2 added Background information 3.1 added precondition and post conditions 3.1.1 modified entire process flow to match the steps of the corresponding use case. Figure 2 changed Diagram to Process Flow 3.1.2 o Step 4 modified to state that SMG will place LSR in queue, send ACK, and start timer o Step 5 modified to state that CII will read from queue o Step 6 modified to state that batching and timing rules are per BPWG Requirements doc. o Step 11 modified to state that CII will perform un-batching as required o Step 12 modified to state that CII will place LSC in queue o Step 13 modified to state that SMG will read LSC from queue o Syniverse Technologies, Inc., 2013

Arleen James

Confidential & Proprietary

Page iii

Document Version 1.03 Issued: 04 August 2006

o o 3.1.3 o

Step 15 added that SMG validate WPRR and finds no errors Added that Use Case 1 ends

Stated that the Alternate Flow begins after step 14 of basic flow o Step 15 ,modified to state that SMG validates the WPRR and determines error o Step 16 modified to state that SMG places NAK/NOT message into a queue o Step 17 modified to state that CII reads from queue o Step 19 modified to state that Syniverse and Wireline Carrier receives NAK/NOT o Step 20 modified to state that Synvierse contacts the carrier regarding error o Added Step 21 o Added that UC 1 ends and returns to basic flow at step 9 3.2.1 modified entire process flow to match the corresponding use case steps 3.2.2 o Step 4 modified to state that SMG places LSR in queue, sends ACK and starts timer o Step 5 modified to state that CII will read from queue o Removed step 6 CII applies batching rules per the BPWG Requirements for Intermodal Porting and renumbered the subsequent steps o Step 9 modified to include that CII unbatches LSC as required o Removed step 13 CII receives LSC via the CII GUI and renumbered the subsequent steps o Step 12 modified to clarify that LSC is processed as it was entered in the GUI o Added Step 16 SMG validate the WPRR and finds no errors. o Added that UC 2 ends and a WPRR is sent to the Wireless Carrier 3.2.3 o Modified to state that UC 2 begins after step 16 when SMG finds error in the LSC during validation o Removed step 17 SMG determines that there is an error and renumbers subsequent steps o Step 17 modified to state that SMG places NAK/NOT in queue o Step 18 modified to state that CII will read from queue o Added step 21 o Added step 23 Syniverse Technologies, Inc., 2013
Page iv

Confidential & Proprietary

Document Version 1.03 Issued: 04 August 2006

Added that alternate flow 1 ends and returns to step 11 of basic flow. Added 3.2.3.1 Alternate Sub-flow 1 for alternate flow 1 of UC 2 3.3.1 modified entire process flow diagram to match the steps of the corresponding use case. 3.3.2 o Step 4 modified to state that CII places LSR in queue o Step 5 modified to state that SMG will read from queue o Step 6 modified to state that SMG performs validations o Step 12 modified to state that SMG places LSC in queue, sends ACK and starts Intermodal timer o Step 13 modified to state that CII reads from queue o Step 14 added that CII will un-batch as required o Step 15 added where it is received by the Wireline Carrier o Added that Use Case 3 ends 3.3.3 o Modified to state that alt flow 1 because after SMG validates the LSR o Step 7 added that SMG places NAK in queue o Removed step 8 and renumbered subsequent steps o Step 8 modified to state that CII will read from queue o Removed step 12 Port center notifies Wireline Operator that there is an error and renumbered subsequent steps o Added step 11 o Added that Alt flow 1 ends and returns to step 1 of basic flow. 3.3.4 o Modified to state that alt flow 2 begins after SMG validates the LSR o Step 7 added that SMG places NOT in queue o Removed step 8 SMG places LSC and NOT in CII queue and renumbered subsequent steps o Step 8 modified to state that CII will read from queue o Step 9 modified to state that CII sends LSC to Wireline Carrier via AS2 and captures NOT information in an email and sends it to Syniverse. o Removed step 13 Port Center notifies Wireline Operator via telephone that there is o Syniverse Technologies, Inc., 2013
Page v

Confidential & Proprietary

Document Version 1.03 Issued: 04 August 2006

an error and renumbers subsequent steps Added steps 11 & 12 Added that alt flow 2 ends and returns to step 1 of basic flow 3.4.1 modified entire flow to match the steps of the corresponding use case 3.4.2 o Step 7 modified to state that CII places LSR in queue o Step 8 modified to state that SMG reads from queue o Step 9 added that SMG will perform validations o Step 15 modified to state that SMG places LSC in queue, sends ACK, and starts Intermodal timer o Step 16 modified to state that CII will read from queue o Step 17 modified to state that CII sends LSC to Wireline carrier via email o Step 18 modified to state that Wireline carrier receives LSC via email o Added that UC 4 ends. 3.4.3 o Modified to state that alternate flow 1 begins after step 9 of basic flow o Step 9 added that SMG determines level 1 error during validation o Step 10 modified to state that SMG places NAK in queue o Step 11 modified to state that CII reads from queue o Added step 16 o Added that alt flow 1 ends and returns to basic flow at step 1 or 4 3.4.4 o Modified to state that alternate flow 2 begins after step 9 of basic flow o Step 10 modified to state that SMG places LSC & NOT in queue o Step 11 modified to state that CII reads from queue o Step 13 modified to state that CII converts NOT to an email and sends to Syniverse. o Step 14 modified to state that Wireline Carrier receives LSC from CII. o Removed steps 15 & 16 and renumbered subsequent steps o Added step 15 o Added that alternate flow 2 ends and returns to basic flow at either step 1 or 4. o o Arleen James
Page vi

1.0

12 July 2006

Initial Release Syniverse Technologies, Inc., 2013

Confidential & Proprietary

Document Version 1.03 Issued: 04 August 2006

Table of Contents
1 INTRODUCTION ....................................................................................................................................8 2 OVERALL DESCRIPTION BACKGROUND INFORMATION.............................................................10 3 FEATURE REQUIREMENTS.................................................................................................................12

Figures
FIGURE 1: HIGH-LEVEL SYSTEM INTERFACES...................................................................................10 FIGURE 2: WIRELINE TO WIRELESS VIA AS2 PROCESS FLOW........................................................12 FIGURE 3: WIRELINE TO WIRELESS VIA E-MAIL PROCESS FLOW...................................................14 FIGURE 4: WIRELESS TO WIRELINE VIA AS2 PROCESS FLOW........................................................16 FIGURE 5: WIRELESS TO WIRELINE VIA E-MAIL PROCESS FLOW...................................................18

Tables
TABLE 1: TERMINOLOGY.........................................................................................................................8 TABLE 2: EXTERNAL REFERENCES.......................................................................................................8

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page vii

Document Version 1.03 Issued: 04 August 2006

1 Introduction
1.1 Purpose and Business Requirements
The purpose of this document is to capture the requirements for the Canadian Intermodal Interface (CII) in conjunction with our partner Telcordia and their SMG, based on the BPWG requirements dated April 10, 2006.

1.2

Definitions, Acronyms, and Abbreviations

Description Applicability Statement 2 is a secure protocol that makes use of keyed encryption and digital signatures to transport information over the public network.) Best Practices Working Group Canadian Data Interchange Guidelines Canadian Intermodal Interface Canadian Local Ordering Guidelines Electronic Data Transfer Graphical User Interface Local Service Confirmation Local Service Request Negative Acknowledgement Example: Missing one of the following fields: WICIS_REL_NO ONSP REQ_NO NNSP Notification Example: Bad data was entered into a field New Service Provider the carrier that is acquiring the customer via porting Old Service Provider the carrier that is losing the customer via porting Service Management Gateway Telcordia SMG Service Provider Identification Wireless Port Request Wireless Port Request Response

Table 1: Terminology

Acronyms and Abbreviations AS2 BPWG CDIG CII CLOG EDT GUI LSC LSR NAK Level 1 Error

NOT Level 2 Error NSP (NLSP/NNSP) OSP (OLSP/ONSP) SMG SPID WPR WPRR

1.3

Reference Documents
Version/# 3.0 Consolidated Release 10.0, Issue 1 5.2 Date May 3, 2006 10 April 2006 February 2006 November 1, 2003

Table 2: External References

Document Title Canadian Data Interchange Guidelines (CDIG) BPWG Requirements for Intermodal Porting SMG/ASMS ICP System Requirements CLOG v5.2 - Data Interchange Format Code Specification DI103.2

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 8

Document Version 1.03 Issued: 04 August 2006

1.4

Document Structure

This document is based on the Institute of Electrical and Electronic Engineers (IEEE Std. 830). This document is segmented into the following sections: Section 1 is an introduction to the requirements and covers the informative, non-technical aspects of the specification. Section 2 describes the general factors affecting the requirements such as product overview, interfaces, constraints, and assumptions. This section does not provide the development requirements for the specific features; instead, it provides background information for the requirements. Section 3 contains the specific software requirements and is organized by feature or function.

1.4.1

Release Revisions

Versions of this document less than 1.0 (i.e. 0.3 or 0.98) are pre-release versions. Once reviews are completed and the sign-off sheet is executed, the document will be released as Version 1.0. Subsequent changes to the document will be version controlled with the same approvals required as a release 1.0. It is recommended that the author use the release revision table to cover pre-release as well as postrelease versions. This provides an audit trail of changes and ideas considered for inclusion.

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 9

Document Version 1.03 Issued: 04 August 2006

2 Overall Description Background Information

2.1 Overall Description
The Canadian Intermodal Interface (CII) is a system that serves to mediate transactions between the Telcordia SMG and Canadian Wireline carriers. The system provides the ability to convey port requests and port request responses from a Wireline carrier to the SMG, and subsequently, to Canadian wireless carriers. Additionally, CII translates the AS2 transmission protocol utilized by certain Canadian wireline carriers for porting transaction messages destined for the SMG into a message structure the SMG can utilize. Port requests and responses (transactions) received by CII, either via e-mail (and input via the CII GUI) or via AS2, will be submitted to the Telcordia SMG for processing.
Syniverse

Wireless Operator

API

Telcordia SMG

Syniverse CII

A S 2

Wireline Operator

SMG GUI

CII GUI E-mail

Figure 1: High-level System Interfaces

2.2

Background Information
Description of Role/Use Submits port request/response as WPR/WPRR via SMG GUI Submits port request/response as LSR/LSC via OSS AS2 interface or e-mail Enters LSR/LSC that was submitted by Wireline Carrier via e-mail, via CII GUI and interacts with carriers to resolve porting system related issues (not contentrelated fallout). Batching and timing of AS2 files (CII) Processes port requests/responses between carriers received via direct OSS interface, SMG GUI, or CII interface; conversion between WPR/LSR and WPRR/LSC

The following actors apply to (have a role in) all the use cases that follow in this document. Actors: Wireless Carrier/OSS Wireline Carrier/OSS Syniverse Technologies Telcordia SMG

2.3
2.3.1

Assumptions and Dependencies

Assumptions

2.3.1.1CII is the system that makes the determination that traffic to the Wireline Carrier is AS2 or E-mail. 2.3.1.2CII will not communicate in WPR/WPRR 2.3.1.3If the error is a Wireline Carrier error, the Wireline Carrier will correct the error and then resubmit the LSR/LSC via AS2/e-mail. 2.3.1.4Level 1 errors are always a NAK and Level 2 errors are always a NOT.

2.4
2.4.1
None

Issues
Open Issues

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 10

Document Version 1.03 Issued: 04 August 2006

2.4.2
None

Closed Issues

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 11

Document Version 1.03 Issued: 04 August 2006

3 Feature Requirements
3.1 Use Case (UC) 1: Wireline to Wireless via AS2
This use case describes the process where the Wireline Carrier is porting-out a number to the Wireless Carrier. The SMG sends an LSR to the Wireline Carrier on behalf of the Wireless Carrier, and the Wireline Carrier returns an LSC via AS2. Preconditions: Wireline Carrier is configured to convey porting transaction messages via an AS2 interface Post-conditions: Port request has been processed successfully by the SMG and the Wireless Carrier has received a confirmation response (WPRR).

3.1.1

Flow of Events Use Case 1

U eC s s ae
A K C

1: W lin toW le sv A ire e ire s ia S

W EE S IR L S
S rt ta

S G M R ce s e ive W Rfro P m W le ire ss O e to p ra r 2

S G M C n rts o ve W RtoL R P S 3

S n sW R ed P toS G M 1

S G M P ce L R la s S inQ e e uu , se d ns A KtoW P C S a dsta n rts tim r e 4

C II R a sL R ed S fro Q e e m uu 5

C II Ap s p lie b tch ga d a in n tim gru s in le 6

C II Sns ed .zip fileviaA S 2 toW lin ire e O e to p ra r

S G M C n rts o ve L Cto S WR ad P R n va a s lid te 1 4

S G M Ras ed L Cfro S m Qe e uu 1 3

C II P ce la s LC S inQ e e uu 1 2

C II P ce ro ss LC S

C II R ce s e ive LC S viaA S 2 1 0

W E IN IR L E Sns ed LC S toC II viaA S 2 9

W E IN IR L E R ce s e ive .zipfile viaA S 2 fro C m II 8

1 1

S G M V lid tio a a n E rs ? rro 1 5

N o Ys e

C II / R a sN K ed A N Tfro O m Qe e uu A1 -1 7 /

C II Sns ed e-m il to a W lin ire e C rrie a d a r n S ive yn rse

E-m il a E-m il a

W E IN IR L E R ce e ive N K /N T A O e a fro m il m C II
Poe hn C ll a

W E IN IR L E C rre o cts ad n R -s b its e um LC S A1 -1 9 A1 -2 1

P ce N K la s A N Tin O Qe e uu A1 -1 6

A1 -1 8

S G M
Ed n

S ive yn rse R ce s e ive N K /N T A O e a fro m il m C II A1 -1 9

S ive yn rse N tifie o s W lin ire e C rrie a r via te p o e le h n A1 -2 0

Sn ed W R to P R W le ire ss C rrie a d a r n sto s tim r p e 1 6

Figure 2: Wireline to Wireless via AS2 Process Flow

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 12

Document Version 1.03 Issued: 04 August 2006

3.1.2

Basic Flow for UC 1: Wireline to Wireless via AS2

This use case begins when the Wireless Carrier sends a WPR to the SMG. 1. Wireless carrier sends WPR to the SMG. 2. SMG receives the WPR from the Wireless Carrier. 3. SMG converts WPR to LSR. 4. SMG places the LSR in a queue to be read by CII and sends an ACK to the Wireline Carrier and starts the Intermodal ICC timer. 5. CII reads the LSR from the queue 6. CII applies batching and timing rules per the BPWG Requirements for Intermodal Porting. 7. CII sends zip file via AS2 to the Wireline Carrier. 8. Wireline Carrier receives the LSR via AS2. The LEC validates the port request and prepares LSC response. 9. Wireline Carrier sends LSC to CII via AS2. 10. CII receives LSC from Wireline Carrier via AS2. 11. CII processes LSC and performs un-batching as required. 12. CII places LSC in queue to be read by SMG. 13. SMG reads LSC from the queue. 14. SMG converts LSC to WPRR. 15. SMG validates the WPRR, finds no errors, and stops Intermodal ICC timer 16. SMG sends WPRR to the Wireless Carrier. Use Case 1 ends

3.1.3

Alternate Flow 1 for UC 1: Validation Fails in the SMG

Alternate flow 1 for UC 1 begins after step 15 of the basic flow for UC1 when SMG converts the LSC to WPRR and determines there is a validation error. 16. SMG places a NAK/NOT message (depending on the error) in a queue for CII. 17. CII reads the NAK/NOT from the queue. 18. CII sends an e-mail which includes the content of the NAK/NOT and Wireline contact information to the Wireline Carrier and to Syniverse. 19. Syniverse and Wireline Carrier receive NAK/NOT e-mail from CII. 20. Syniverse contacts Wireline Carrier via telephone regarding the error. 21. Wireline Carrier enters a supplemental port response via an updated LSC that is re-submitted to CII via AS2. Alternate flow 1 for UC 1 ends, and returns to the basic flow at step 9.

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 13

Document Version 1.03 Issued: 04 August 2006

3.2

Use Case 2: Wireline to Wireless via E-mail

This use case describes the process where the Wireline Carrier is porting-out a number to the Wireless Carrier. The SMG sends an LSR on behalf of the Wireless Carrier and the Wireline Carrier sends an LSC via E-mail.

3.2.1

Flow of Events Use Case 2

U C se se a
A CK

2: W lin P rtin to W le s v E ire e o g ire s ia

S G M P ce L R la s S in Q e e uu se d A K ns C sta tim r rts e 4

-m il a
C II R a sL R ed S fro Q e e m uu 5 C II
S nd L R to e s S W line ire O rato a d pe r n S iverse via yn e-m il a E-m for log in ail g g E-m il a

W EE S IR L S
S tart

S G M R ce s e ive W R fro P m W le ire ss O e to p ra r 2

S G M C n rts o ve W Rto L R P S 3

W E IN IR L E R ce s e ive L Rfro S m C via e II m il a

S n sW R ed P to S G M 1

7
W E IN IR L E
E -m il a

S G M R a sL C ed S fro Q e e m uu 1 4

C II P ce L C la s S in Q e e uu 1 3

C II P ce ro ss L C S 1 2

S ive r yn rse S bm u its L C to C S II 1 1

S ive yn rse E te n rs L C S in C to II via G I U 1 0

S ive yn rse R ce s e ive L Cfro S m W lin ire e O e to via p ra r e-m il a 9

S n sL C ed S to S ive yn rse v e -m il ia a 8

S G M C n rts o ve L C to S WR a P R d va a s lid te 1 5 V lid tio a a n E rs ? rro 1 6

N o Ys e

S G M P ce la s N K /N T A O in Q e e uu A1 -1 7

C II Ras ed N K /N T A O fro Q e e m uu A1 -1 8

C II Sns ed e-m il to a W lin ire e C rrie a d a r n S ive yn rse

E-m il a

W E IN IR L E R ce s e ive N K /N T A O e-m il a fro C m II A1 -1 9 A1 -20 S ive yn rse N tifie o s W lin ire e O e to via p ra r T le h n e poe A1 -2 1

S ive yn rse
C orrects data entry error
N o

Y es

A1 -2 3

S G M
E nd

S ive yn rse R ce s e ive N K /N T A O e-m il a fro C m II A1 -2 0

Sn WR ed P R to W le ire ss O e to p ra r a d sto s n p tim r e 1 7

S ive yn rse d ta e try a n e r ? rro A1 -2 2

Figure 3: Wireline to Wireless via E-mail Process Flow

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 14

Document Version 1.03 Issued: 04 August 2006

3.2.2

Basic Flow for UC 2: Wireline to Wireless via E-mail

This Use Case begins when the Wireless Carrier sends a WPR to the SMG. 1. Wireless Carrier sends WPR to SMG. 2. SMG receives WPR from Wireless Carrier 3. SMG converts WPR to LSR. 4. SMG places LSR in queue for CII to read, sends ACK to the Wireless Carrier, and starts Intermodal ICC timer. 5. CII reads LSR from the queue. 6. CII e-mails LSR to the Wireline Carrier and to Syniverse (for logging purposes only). 7. Wireline Carrier receives LSR from CII via e-mail. Wireline carrier validates port out and prepares LSC response. 8. Wireline Carrier sends LSC to Syniverse via e-mail. 9. Syniverse receives LSC from Wireline Carrier via e-mail and un-batches as required (multiple LSC attachments). 10. Syniverse enters LSC into the CII GUI. 11. Syniverse submits LSC to CII. 12. CII processes LSC as entered in GUI 13. CII places LSC in queue to SMG 14. SMG reads LSC from queue. 15. SMG converts LSC to WPRR. 16. SMG validates the WPRR and finds no errors. 17. SMG sends WPRR to Wireless Carrier and stops Intermodal ICC timer. Use case 2 ends a WPRR is sent to the Wireless Carrier.

3.2.3

Alternate Flow 1 for UC 2: Validation Fails in the SMG

Alternate flow 1 for UC 2 begins after step 16 of the basic flow when the SMG finds errors in the LSC during validation. 17. SMG places NAK/NOT in queue. 18. CII reads the NAK/NOT from the queue. 19. CII sends an e-mail that includes the content of the NAK/NOT and the Wireline Contact Information to the Wireline Carrier and to Syniverse. 20. Wireline Carrier and Syniverse receive NAK/NOT e-mail from CII. 21. Syniverse notifies Wireline Carrier via telephone that there is an error regardless of whether it is a Wireline Carrier error or a Syniverse entry error. 22. Syniverse and Wireline Carrier determine if the error is a Wireline error or a Syniverse error. 23. When the error was determined to be a Syniverse-originated data entry error, Syniverse corrects the LSC data. Alternate flow 1 of use case 2 ends and returns to the basic flow at step 11, where the LSC is submitted to CII. Alternate Sub-flow 1 for alternate flow 1 of UC 2 Alternate sub-flow 1 begins after step 22 of alternate flow 1, when it is determined that the validation error was not originated by a data entry error by Syniverse. 23. When the error was determined not to be a Syniverse-originated data entry error, the Wireline Carrier corrects the LSC data. Alternate sub-flow 1 ends and returns to the basic flow at step 8, where the Wireline Carrier (re-) submits the (corrected) LSC to CII.
.

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 15

Document Version 1.03 Issued: 04 August 2006

3.3

Use Case 3: Wireless to Wireline via AS2

This use case describes the process where the Wireline Carrier is porting-in a number from the Wireless Carrier. The Wireline Carrier sends an LSR via AS2 and the SMG sends an LSC on behalf of the Wireless Carrier.

3.3.1

Flow of Events Use Case 3

U eC s s ae
W E IN IR L E
Sr tat

3: W e s toW e ev A ir le s ir lin ia S
C II P cse ro e s s LR S

2
C II P c sL R la e S inQ e e uu S G M R a sL R ed S fro Q e e m uu S G M Cn e o v rts L RtoW R S P ad n V lid te a a s

C II R c iv s ee e L Rfro S m W lin ire e C rrie a r v A ia S 2

S n sL R ed S (. z file ) to ip C v A II ia S 2

W E IN IR L E C rre ts o c E nos rro e u L Ra d S n R -s b its e um

A1 -1 2

W E IN IR L E R c iv s ee e N Ke -m il A a fro C m II
A1 -1 0

C II C s ns II e d e-m il to a W lin a d ire e n Sn e e y iv rs

A1 -9

C II R a sN K ed A fro Q e e m uu
A1 -8

S G M P c sN K la e A inQ e e uu
A1 -7

Lv l ee 1

Lv l ee Lvl ee

1 o r 2?

Ys e

V lid tio a a n E rs ? rro

Lv l ee

N o

Sn e e y iv rs N tifie o s W lin o ire e f E rv rro ia T le h n e poe

A11 1

Sn e e y iv rs R c iv s ee e N Ke -m il A a fro C m II
A1 -1 0

S G M C a sL C re te S a dp c s n la e LC & N T S O inQ e e uu
A2 -7

S G M S n sW R ed P toW le s ire s O e to p ra r a ds rts n ta tim r e 7 W EE S IR L S R c iv s ee e W Rfro P m S G M 8 W EE S IR L S Sn s ed W R to PR S G M 9

Sn e e y iv rs R c iv s ee e N Te -m il O a fro C fo m II r lo g g g in
A2 -1 0

C II S n sL C ed S toW lin ire e v A ia S 2 a d n e-m ilsN T a O toS n e e y iv rs

A2 -9

C II R a sL C ed S & N Tfro O m Qe e uu
A2 -8

W E IN IR L E
R -s b it e um LR S
A2 -1 2

W E IN IR L E R c iv s ee e L C (v S ia A 2) S fro C m II

C rre ts o c E nos rro e u L Ra d S n R -s b its e um

A2 -1 1

A K C

W E IN IR L E
Ed n

1 5

C II S n sL C ed S toW lin ire e v A ia S 2

1 5

C II Ap s p lie b tc in a hg ru s le

1 4

C II R a sL C ed S fro Q e e m uu

1 3

S G M P c sL C la e S inQ e e uu , S n sA K ed C toW P S , ad n S p T e to s im r

1 2

S G M Cn e o v rts W R to PR LC S

1 1

S G M R c iv s ee e W R fro PR m W le s ire s O e to p ra r

1 0

R c iv s ee e L Cv A S ia S

Figure 4: Wireless to Wireline via AS2 Process Flow

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 16

Document Version 1.03 Issued: 04 August 2006

3.3.2

Basic Flow for UC 3: Wireless to Wireline via AS2

This Use Case begins when the Wireline Carrier sends an LSR to the CII via AS2. 1. Wireline Carrier sends LSR to CII via AS2. 2. CII receives an LSR from the Wireline Carrier via AS2. 3. CII processes LSR. 4. CII places LSR in the queue. 5. SMG reads LSR from the queue. 6. SMG converts LSR to WPR and performs validation. 7. SMG sends WPR to Wireless Carrier and starts Intermodal ICC timer. 8. Wireless Carrier receives WPR from SMG. The Wireless Carrier validates port out and prepares WPRR response. 9. Wireless Carrier sends WPRR to SMG 10. SMG receives WPRR from Wireless Carrier. 11. SMG converts WPRR to LSC. 12. SMG places LSC in queue, sends ACK to Wireless Carrier and stops Intermodal ICC timer. 13. CII reads LSC from queue. 14. CII applies batching rules and un-batches as required. 15. CII sends LSC to Wireline Carrier via AS2, where it is received by the Wireline Carrier. Use case 3 ends when the Wireline Carrier receives the confirming LSC from CII.

3.3.3

Alternate Flow 1 for UC 3: Level 1 Error

Alternate flow 1 for UC 3 begins after step 6 of the basic flow of UC 3 when SMG validates the LSR. 7. SMG determines that there is a Level 1 error and places NAK in the queue for CII. 8. CII reads the NAK from the queue. 9. CII sends an e-mail that includes the content of the NAK and the Wireline Carrier contact information to the Wireline Carrier and to Syniverse. 10. Syniverse and Wireline Carrier receive NAK e-mail from CII. 11. Syniverse notifies Wireline Carrier via telephone that there is an error (during business hours only). 12. Wireline Carrier corrects LSR and re-submits. Alternate flow 1 ends and returns to the basic flow at step one where the Wireline Carrier submits the LSR via AS2.

3.3.4

Alternate Flow 2 for UC 3: Level 2 Error

Alternate flow 2 for UC 3 begins after step 6 of the basic flow when SMG validates the LSR t. 7. SMG determines that there is a Level 2 error and places NOT in the queue for CII. 8. CII reads the LSC and NOT from the queue. 9. CII sends LSC to the Wireline Carrier via AS2, and captures the NOT information in an e-mail and sends it to Syniverse. 10. Syniverse receives NOT e-mail from CII. 11. . Wireline Carrier receives LSC from CII. 12. Wireline Carrier corrects LSR and re-submits. Alternate flow 2 ends and returns to the basic flow at step one where the Wireline Carrier submits the LSR via AS2.

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 17

Document Version 1.03 Issued: 04 August 2006

3.4

Use Case 4: Wireless to Wireline via E-mail

This use case describes the process where the Wireline Carrier is porting-in a number from the Wireless Carrier. The Wireline Carrier sends an LSR via e-mail and the SMG sends an LSC on behalf of the Wireless Carrier.

3.4.1

Flow of Events Use Case 4

Use Case 4: Wireless to Wireline via E
WIRELINE Syniverse Receives LSR from Wireline carrier via e mail
A1 -16

-mail
CII Places LSR in queue 6 7 SMG Places NAK in queue
A1 -10

Syniverse Enters LSR into the CII GUI 2 3

Syniverse Submits LSR to CII 4 WIRELINE

CII Receives LSR via CII GUI 5 CII CII sends e-mail to Wireline and Syniverse

CII Processes LSR

SMG Reads LSR from queue 8

SMG Converts LSR to WPR , validating WPR

Start

Sends LSR via e -mail to Syniverse 1 WIRELINE

9 SMG

CII Reads NAK from queue

A1 -12 A1 -11

Re-submit Corrected LSR

Corrects LSR in e-mail

A2 -17

No

Syniverse Data Entry Error ?

Phone Call

Receive NAK e -mail from CII

Level 1 or Level Level 2 1 A1 error ? -9

A2 -9

Yes

Validation Errors ?

No

A1 -13

Sends WPR to Wireless carrier and starts timer

10

Syniverse Notify Wireline carrier via Telephone

Yes
A1 -15 A2 -16

Syniverse Determine if Wireline or Port Center Error

A2 -15 A1 -14

Syniverse Receives NAK e -mail from CII

Level 2 ACK
A1 -13

WIRELESS Receives WPR from from SMG 11 CII CII Reads LSC & NOT from queue SMG Creates LSC and places LSC & NOT in queue WIRELESS Sends WPRR to SMG 12 SMG Converts WPRR to LSC 15 14 SMG Receives WPRR from Wireless carrier

Syniverse
Re -submit Corrected LSR

Syniverse Receives LSC and NOT e -mails A2 from CII

A2 -12

Corrects LSR in the CII GUI

A1 -16 A2 -17

-14

Sends LSC to Wireline and LSC and NOT to Syniverse via email CII Creates batch and sends LSC to Wireline via e -mail WIRELINE

A2 -11

A2 -10

WIRELINE Receive LSC e -mail from CII

CII Reads LSC from queue 17 16

SMG Places LSC in queue , Sends ACK to WSP and stops timer

A2 -13

13

End

Receives LSC via e-mail

18

Figure 5: Wireless to Wireline via E-mail Process Flow

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 18

Document Version 1.03 Issued: 04 August 2006

3.4.2

Basic Flow for UC 4: Wireless to Wireline via E-mail

This use case begins when the Wireline Carrier sends an LSR via e-mail. 1. Wireline Carrier sends LSR via e-mail to Syniverse. 2. Syniverse receives an LSR from a Wireline Carrier via e-mail and un-batches as required. 3. Syniverse enters the LSR into the CII GUI. 4. Syniverse submits the LSR to CII. 5. CII receives the LSR via CII GUI. 6. CII processes LSR. 7. CII places LSR in queue. 8. SMG reads LSR from queue. 9. SMG converts LSR to WPR and performs validation. 10. SMG sends WPR to Wireless Carrier and starts Intermodal ICC timer. 11. Wireless Carrier receives WPR from SMG. Wireless Carrier validates and prepares WPRR response. 12. Wireless Carrier sends WPRR to SMG. 13. SMG receives WPRR from Wireless Carrier. 14. SMG converts WPRR to LSC. 15. SMG places LSC in queue and sends ACK to Wireless Carrier and stops Intermodal ICC timer. 16. CII reads LSC from queue. 17. CII sends LSC to Wireline Carrier via e-mail 18. Wireline Carrier receives LSC via e-mail from CII. Use Case 4 ends when the Wireline Carrier receives the LSC from CII.

3.4.3

Alternate Flow 1 for UC 4: Level 1 Error

Alternate Flow 1 for UC 4 begins after step 9 of the basic flow when SMG converts the LSR to a WPR. 9. SMG determines that there is a level 1 error during validation. 10. SMG places NAK in queue. 11. CII reads the NAK from the queue. 12. CII sends an e-mail that includes the content of the NAK and the Wireline Carrier contact information to the Wireline Carrier and to Syniverse. 13. Syniverse and Wireline Carrier receive NAK e-mail from CII. 14. Syniverse determines if the error is a Wireline Carrier error or a Syniverse error. 15. Syniverse notifies Wireline Carrier via telephone that there is an error regardless of whether the error is a Wireline Carrier or a Syniverse error. 16. When the error is a Wireline Carrier error, the Wireline Carrier will correct the LSC information and re-submit the LSC via e-mail; when the error is a Syniverse data entry error, Syniverse will correct the LSC information and re-submit the LSC via the CII GUI. Alternate flow 1 for UC 4 ends and returns to the basic flow either at step 1 or step 3, based on the party submitting the error correction.

3.4.4

Alternate Flow 2 for UC 4: Level 2 Error

Alternate Flow 2 for UC 4 begins after step 9 of the basic flow when SMG converts theLSR to a WPR. 9. SMG determines that there is a level 2 error. 10. SMG places LSC & NOT in queue. 11. CII reads LSC & NOT from the queue. 12. CII e-mails the LSC to the Wireline Carrier and the Syniverse. 13. CII converts the NOT to an e-mail that contains the content of the NOT and Wireline contact information and sends to Syniverse. 14. Wireline Carrier receives LSC from CII. 15. Syniverse and Wireline Carrier determine if the error is a Wireline error or a Syniverse error. 16. Syniverse notifies Wireline Carrier via telephone that there is an error regardless of whether the error is a Wireline error or a Syniverse error.
Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 19

Document Version 1.03 Issued: 04 August 2006

17. When the error is a Wireline Carrier error, the Wireline Carrier will correct the LSC information and re-submit the LSC via e-mail; when the error is a Syniverse data entry error, Syniverse will correct the LSC information and re-submit the LSC via the CII GUI. Alternate flow 2 for UC 4 ends and returns to the basic flow either at step 1 or step 3, based on the party submitting the error correction.

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 20

Document Version 1.03 Issued: 04 August 2006

Confidential & Proprietary

Syniverse Technologies, Inc., 2013

Page 21