Where SBC-13STATE is the 911 service provider and Carrier deploys a CAS or Hybrid-CAS Solution utilizing SBC-13STATE E911 DBMS:
Where SBC-13STATE is the ALI Database Provider all ALI queries will be directed to the SBC database for ALI lookup.
Where SBC-13STATE is the 911 service provider, Carrier will transport 911 calls from each Carrier MSC to the SR office of the E911 system.
Where SBC-13STATE is the 911 service provider, and Carrier deploys an NCAS solution:
Where SBC-13STATE manages the DBMS, SBC-13STATE shall establish a process for the management of NPA splits by populating the DBMS with the appropriate NPA codes.
Where SBC-13STATE is performing a transiting function as defined in Section 10.0 below, SBC-13STATE will pass the Signaling Data if it is received from the originating third party. If the Signaling Data is not received from the originating third party, SBC-13STATE can not forward the Signaling Data and will not be billed as the default originator.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE shall store the Carrier's ALI records in the electronic data processing database for the E911 DBMS.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE shall coordinate access to the SBC-13STATE E911 DBMS for the initial loading and updating of Carrier ALI Records.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE's ALI database shall accept electronically transmitted files that are based upon NENA standards.
Where SBC-13STATE is the 9-1-1 service provider, and AWS deploys an NCAS solution: AWS’ designated third-party provider shall perform the above database functions to the extent required for an NCAS solution. AWS’ designated third party shall be responsible for ensuring AWS' Host ALI Records are submitted to SBC-13STATE, for inclusion in SBC-13STATE’s DBMS, on a timely basis. AWS ’s third-party provider shall provide initial and ongoing updates of AWS' Host ALI Records that are in electronic format based upon established NENA standards.
