TRADING PARTNER PROFILE (TPP)
Purpose: The purpose of the Trading Partner Profile is to exchange contact and connectivity information
required to port with Trading Partners. There are two sections to the profile:
o Initial Set-Up: How to establish porting as a Trading Partner.
o Porting Business & Support Information: What information is required for optimal customer port
experience?
Please return Trading Partner Profile, to: Julie Rochester: jrochester@ctia.org
SECTION 1: INITIAL SET-UP
A. GENERAL TRADING PARTNER INFORMATION
O
P
E
R
A
T
I
O
N
S
Item
<Trading Partner>
Company Name
Wireless or Wireline
Operating Company No. (OCN)
Administrative OCN
Service Provider ID (SPID)
LSMS SPID (Can be SS7 provider)
LSR Version ID
FOC Version ID
WICIS Version ID
X
X
X
X
X
X
X
X
X
Monday – Saturday
When will you (Carrier) accept and
process port requests?
Sunday
When will you (Carrier) accept and
process port requests?
What Holidays will you (Carrier)
NOT accept and process port
requests?
Holidays
3/7/2016, Version 5.0
page 1 of 5
B. PORT RESOLUTION CENTER
Sprint is available to support error/reject resolution subject to the following:
Item
Port Resolution Center:
Primary contact name
Contact Description
Phone Number (Carrier Support)
Phone Number (Customer Support)
FAX Number
Email address
<Trading Partner>
Ex: Port Resolution Center
Ex: Port Resolution Center
X
X
X
X
X
X
Hours of Operations support:
Monday – Saturday
Sunday
Holidays
X
X
X
C. WLNP CARRIER ACCOUNT MANAGER
Carrier point-of-contact for establishing a porting relationship, as well as ongoing porting account
management. This contact information should NOT be shared with your Port Resolution Center.
Item
<Trading Partner>
Carrier Point of Contact
Primary Contact Name
Title
Address
City
State
Zip
Work Phone Number
Mobile Number
Fax
E-Mail Address
X
X
X
X
X
X
X
X
X
X
X
Alternate Contact Name
Title
Address
City
State
Zip
Work Phone Number
Mobile Number
Fax
E-Mail Address
X
X
X
X
X
X
X
X
X
X
3/7/2016, Version 5.0
page 2 of 5
D. SPIDs/OCNs
Trading Partner OCNs for SOA SPID of “X” and LSMS SPID of “A”:
NOTE: Please list all 4 Digit OCN’s per NPAC SOA SPID. If you have more than one SOA
SPID, please indicate which OCN’s belong to each.
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
Trading Partner OCNs for SOA SPID of “X” and LSMS SPID of “B”:
OCN:
OCN:
OCN:
OCN:
OCN:
OCN:
Trading Partner OCNs for SOA SPID of “Y” and LSMS SPID of “C”:
OCN:
OCN:
3/7/2016, Version 5.0
OCN:
OCN:
OCN:
OCN:
page 3 of 5
E. CONNECTIVITY
Do you have an agreement with a Clearinghouse vendor or Service Bureau? If YES, please
provide the vendor name and contact information. If you are using a Clearinghouse,
C
O
N
N
E
C
T
I
V
I
T
Y
Item
Vendor Name
Contact Name
Contact description
Phone number #1
Phone number #2
FAX number
Email address
Other
<Trading Partner>
Example: TSI
Network Operations Center
Network Operations Center
800-892-2888
813-273-3440
813-273-3570
Netops@tsiconnections.com
Hotline@tsiconnections.com
If NO Clearinghouse or Service Bureau, please provide contact information for Connectivity.
C
O
N
N
E
C
T
I
V
I
T
Y
Item
Contact name
Contact description
Phone number #1
Phone number #2
FAX number
Email address
Other
3/7/2016, Version 5.0
<Trading Partner>
N/A
N/A
N/A
N/A
N/A
N/A
N/A
page 4 of 5
F. TRANSPORT MODE
This following sections marked in RED are required only if Trading Partner is NOT using a Clearinghouse vendor or
Service Bureau for connectivity & transmission of port requests.
Item
C
O
R
B
A
Vendor
F
A
X
<Trading Partner>
Porting Method: Primary,
Secondary, N/A
ICP Package/Application
(“send to”)
ICP Physical Server
(“receive from”)
Failover ICP Server
Application Port Information
Naming Service / IOR
DLCI (Frame Relay usage)
LDAP Provider
Security Requirements
Security Requirements
Firewall Requirements
SSL Requirements
Proprietary Requirements
Service IDL version
Implementation OMG standard
compliant?
…OMG CORBA Standards Supported …
Product Name/Version
OMG CORBA Version
Item
IIOP Version
<Trading Partner>
Porting Method: Primary,
Secondary, N/A
FAX number
Backup FAX number
E
M
A
I
L
Item
O
T
H
E
R
Item
<Trading Partner>
Porting Method: Primary,
Secondary, N/A
Specific E-Mail Requirements
<Trading Partner>
Porting Method: Primary,
Secondary, N/A
Other Communication
Requirements
3/7/2016, Version 5.0
page 5 of 5