Enterprise Scenarios August 2018

TN Proof of Possession (TN-PoP) Use Case This scenario represents the primary TN-PoP use case considered when developing the architecture SP-A Analytics SHAKEN PoP AS PoP VS STI AS STI VS … SP-B SP-X SP-Y SP-Z SHAKEN PoP VS STI AS STI VS … SP-C SP-X1 SP-Y1 SP-Z1

TN Proof of Possession (TN-PoP) SP-A Analytics SHAKEN PoP AS PoP VS STI AS STI VS … SP-B SP-X SP-Y SP-Z SHAKEN PoP VS STI AS STI VS … SP-C SP-X1 SP-Y1 SP-Z1

TN Proof of Possession (TN-PoP) AS SP-A SP-B SP-D SP-C

TN-PoP: BPO Originating Carrier BPO SP-D SP-C SP-B

TN-PoP: Solutions PBX (TCPA) BPO Dialer BPO BPO BPO Originating Carrier BPO SP-D SP-C BPO SP-B BPO BPO

TN-PoP: Originating Carrier PBX (TCPA) Originating Carrier IP-based IXC BPO Dialer SP-D SP-C PBX (TCPA) BPO Dialer SP-B BPO Dialer Dialer BPO PBX (TCPA)

TN-PoP: Originating Carrier Terminating Carrier Analytics SHAKEN PoP VS STI AS STI VS … SP-B SP-X SP-Y SP-Z Analytics SHAKEN PoP VS STI AS STI VS … SP-C SP-X SP-Y SP-M

TN-PoP: Challenges Key Questions: Who obtains the TN? PBX (TCPA) Originating Carrier Key Questions: Who obtains the TN? Who generates the PASSporT token and determines the level of attestation? How do we insure that all the other elements (3rd party and outsourced) do not contaminate the attestation? BPO Dialer SP-D SP-C PBX (TCPA) BPO Dialer SP-B BPO Dialer Dialer BPO IP-based IXC PBX (TCPA)

A Real-World Example Brand A (Tkmtg) 36M/ 11K Vendor to Deliver Calls Originating Carrier VendorA (1M/62#) Carrier A (1M/62#) 12 Carriers X Y Z VendorB (3M / 228#) Brand A (Tkmtg) 36M/ 11K VendorC (14M/8,171#) Carrier B (14M/8,171#) VendorD (1M/1600#) Carrier C (2M/1694#) VendorE (1M/94#)

Service Provider (IMS) A Real-World Example STI - VS Service Provider (IMS) STI - AS SHAKEN Attestation

Summary The TN-PoP framework was based on a relatively simple enterprise architecture. Reality is rather more complex. Next Steps => for discussion…