WO2023288076A2

WO2023288076A2 - Telecommunications call validation platform

Info

Publication number: WO2023288076A2
Application number: PCT/US2022/037326
Authority: WO
Inventors: Jason David Kempson; Justen James Davis; Ryan Patrick Karnas
Original assignee: Somos, Inc.
Priority date: 2021-07-16
Filing date: 2022-07-15
Publication date: 2023-01-19
Also published as: CA3226750A1; WO2023288076A3

Abstract

A method for generating a list of telecommunication identifiers is provided. The method includes interpreting, via at least one processor, telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The method further includes generating the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The method further includes transmitting the list.

Description

TELECOMMUNICATIONS CALL VALIDATION PLATLORM

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 63/222,838 (SMS8-0009-P02), filed July 16, 2021, and titled “TELECOMMUNICATIONS CALL VALIDATION PLATFORM”.

[0002] This application also claims priority to, and is a continuation-in-part of, U.S. Application Serial No. 17/226,313 (SMS8-0009-U01), filed April 9, 2021, and titled “TELECOMMUNICATIONS CALL VALIDATION PLATFORM”.

[0003] U.S. Application Serial No. 17/226,313 claims the benefit of priority to U.S. Provisional Patent Application Serial. No. 63/008,175, filed April 10, 2020, and titled “TELECOMMUNICATIONS CALL VALIDATION PLATFORM” (SMS8-0009-P01).

[0004] All of the above patent documents are incorporated herein by reference in their entirety for all purposes.

FIELD OF INVENTION

[0005] This disclosure is related to the operation, control and management of telecommunication lines.

BACKGROUND

[0006] Businesses increasingly use toll-free telephone numbers for providing customers with a convenient and cost-free means of communicating with them and their various departments, such as customer service and technical support representatives. With the proliferation of toll-free numbers and advanced business analytics for receiving, routing, and logging, the use of such numbers has come increased complexity in managing toll-free numbers. Traditional toll-free number platforms have been susceptible to abuse by unauthorized entities, e.g., spoofing attacks, whereby an authorized entity is able to make an outbound call appear to originate from an authorized source for the purpose of deceiving the called party.

SUMMARY

[0007] Embodiments of the current disclosure may provide for a system for validating a telephone service request. The system includes a phone number database and a controller. The phone number database includes a data record that pairs a managing entity to a phone number. The controller communicates with the phone number database and is operative to: receive an authentication code request corresponding to the managing entity and identifying the phone number; validate the phone number is registered to the managing entity via querying the phone number database; responsive to validating the phone number is registered to the managing entity, generate an authentication code corresponding to the phone number; and transmit the authentication code. In certain embodiments, the controller is further operative to: store the generated authentication code in the data record; receive a validation request corresponding to a service provider, the validation request including an authentication code; validate that the authentication code in the validation request matches the authentication code stored in the data record via querying the phone number database; and responsive to validating that the authentication code in the validation request matches the authentication code in the data record, transmit an authentication message. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM. In certain embodiments, the validation request identifies one or more services corresponding to the phone number; and the authentication message indicates the authentication code in the validation request provides access to the one or more services. In certain embodiments, the managing entity is a local number administrator· In certain embodiments, the managing entity is a Responsible Organization. In certain embodiments, the phone number database is a number registry. In certain embodiments, the number registry is a toll-free number registry.

[0008] Embodiments of the current disclosure may provide for a method for validating a telephone service request. The method includes receiving, from a managing entity, an authentication code request that identifies a phone number; and validating that the phone number is registered to the managing entity via querying a phone number database including a data record that pairs the managing entity to the phone number. The method further includes: responsive to validating that the phone number is registered to the managing entity, generating an authentication code corresponding to the phone number; and transmitting the authentication code to the managing entity. In certain embodiments, the method further includes: storing the generated authentication code in the data record; receiving, from a service provider, a validation request, that includes an authentication code; validating that the authentication code in the validation request matches the authentication code stored in the data record; and responsive to validating that the authentication code in the validation request matches the authentication code stored in the data record, transmitting an authentication message to the service provider. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM. In certain embodiments, the validation request identifies one or more services corresponding to the phone number; and the authentication message indicates the authentication code in the validation request provides access to the one or more services. In certain embodiments, the managing entity is a local number administrator. In certain embodiments, the managing entity is a Responsible Organization. In certain embodiments, the phone number database is a number registry. In certain embodiments, the number registry is a toll-free number registry.

[0009] Embodiments of the current disclosure may provide for a non-transitory computer-readable medium storing instructions. The stored instructions adapt at least one processor to: receive, from a managing entity, an authentication code request that identifies a phone number; and validate that the phone number is registered to the managing entity via querying a phone number database including a data record that pairs the managing entity to the phone number. The stored instructions further adapt the at least one processor to, responsive to validating that the phone number is registered to the managing entity, generate an authentication code corresponding to the phone number; and transmit the authentication code to the managing entity. In certain embodiments, the stored instructions further adapt the at least one processor to: store the generated authentication code in the data record; receive, from a service provider, a validation request, that includes an authentication code; validate that the authentication code in the validation request matches the authentication code stored in the data record; and responsive to validating that the authentication code in the validation request matches the authentication code stored in the data record, transmit an authentication message to the service provider. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM.

[0010] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller in communication with an enterprise validation server and operative to: transmit an authentication code request to the validation server, the authentication code request identifying a phone number; receive an authentication code from the enterprise validation server; and transmit the authentication code. In certain embodiments, the controller is further operative to: receive the authentication code request prior to transmitting the authentication code request to the validation server.

[0011] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes transmitting an authentication code request to an enterprise validator, the authentication code request identifying a phone number. The method further includes receiving an authentication code from the enterprise validator; and transmitting the authentication code to an enterprise. In certain embodiments, the method further includes receiving the authentication code request from an enterprise prior to transmitting the authentication code request to the enterprise validator. [0012] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller operative to: receive an authentication code corresponding to a phone number; and transmit a service request to a service provider server, the service request including the authentication code and identifying a service corresponding to the phone number. In certain embodiments, the controller is further operative to transmit, to a responsible organization server, an authentication code request identifying the phone number; and the authentication code is received from the responsible organization server. In certain embodiments, the service is: a call request; SMS; RCS; and/or CNAM.

[0013] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes: receiving, from a responsible organization, an authentication code corresponding to a phone number; and transmitting, to a service provider, a service request that includes the authentication code and identifies a service corresponding to the phone number. In certain embodiments, the method further includes transmitting, to a responsible organization, an authentication code request identifying the phone number. In certain embodiments, the service is: a call request; SMS; RCS; and/or CNAM.

[0014] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller in communication with an enterprise validation server and operative to: receive a service request corresponding to an enterprise, the service request including an authentication code and identifying a service and a phone number; transmit a validation request to the enterprise validation server, the validation request including the authentication code and identifying the phone number; and receive an authentication message from the enterprise validation server. Upon receipt of the authentication message, the controller provides the service to the enterprise for the phone number. In certain embodiments, the validation request further identifies the service. In certain embodiments, the authentication message indicates the enterprise is authorized to access the service for the identified phone number.

[0015] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes receiving, from an enterprise, a service request that includes an authentication code and identifies a service corresponding to a phone number; transmitting, to an enterprise validator, a validation request that includes the authentication code and identifies the phone number; receiving an authentication message from the enterprise validator; and responsive to receiving the authentication message, providing the service to the enterprise for the phone number. In certain embodiments, the validation request further identifies the service. In certain embodiments, the authentication message indicates the enterprise is authorized to access the service for the identified phone number. [0016] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes transmitting, by a responsible organization to an enterprise validator, an authentication code request that identifies a phone number; and upon receiving the authentication code request at the enterprise validator, validating, by the enterprise validator, that the phone number is registered to the responsible organization via querying a phone number database. The method further includes responsive to validating that the phone number is registered to the responsible organization, generating, by the enterprise validator, an authentication code corresponding to the phone number. The method further includes transmitting, by the enterprise validator, the authentication code to the responsible organization; storing, by the enterprise validator, the generated authentication code in the phone number database; and transmitting, by the responsible organization, the authentication code to an enterprise. The method further includes upon receiving the authentication code at the enterprise, transmitting, by the enterprise to a service provider, a service request including the authentication code and identifying a service corresponding to the phone number. The method further includes upon receiving the service request at the service provider, transmitting, by the service provider to the enterprise validator, a validation request including the authentication code and identifying the phone number. The method further includes upon receiving the validation request at the enterprise validator, validating, by the enterprise validator via querying the phone number database, that the authentication code in the validation request matches the authentication code stored in the phone number database. The method further includes responsive to validating that the authentication code in the validation request matches the authentication code stored in the phone number database, transmitting, by the enterprise validator to the service provider, and authentication message; and in response to receiving the authentication message at the service provider, providing, via the service provider, a service to the enterprise for the phone number.

[0017] Embodiments of the current disclosure may provide for a method for generating a list of telecommunication identifiers. The method includes interpreting, via at least one processor, telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The method further includes generating the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The method further includes transmitting the list.

[0018] Embodiments of the current disclosure may provide for another method for generating a list of telecommunication identifiers. The method may include interpreting, via at least one processor, telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The method may further include generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include transmitting the list.

[0019] Embodiments of the current disclosure may provide for an apparatus for generating a list of telecommunication identifiers. The apparatus may include a telecommunications data processing circuit structured to interpret telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The apparatus may further include a list generating circuit structured to generate the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The apparatus may further include a list provisioning circuit structured to transmit the list.

[0020] Embodiments of the current disclosure may provide for another apparatus for generating a list of telecommunication identifiers. The apparatus may include a telecommunications data processing circuit structured to interpret telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The apparatus may further include a list generating circuit structured to generate the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The apparatus may further include a list provisioning circuit structured to transmit the list.

[0021] Embodiments of the current disclosure may provide for a method for routing a telecommunication message. The method may include interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein the telecommunications data includes available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The list may include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include determining whether to route the telecommunications message based at least in part on the list.

[0022] Embodiments of the current disclosure may provide for another method for routing a telecommunication message. The method may include interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein the telecommunications data includes available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The list may include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include determining whether to route a telecommunications message based at least in part on the list.

[0023] Embodiments of the current disclosure may provide for a method for mitigating telecommunications fraud. The method may include identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between available telecommunication identifiers and in-use telecommunication identifiers. The method may further include penalizing, via the at least one processor, the entity.

[0024] Embodiments of the current disclosure may provide for another method for mitigating telecommunications fraud. The method includes identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and reserved telecommunication identifiers. The method further includes penalizing, via the at least one processor, the entity.

[0025] The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be appreciated, however, the following description and drawings are intended to be exemplary in nature and non-limiting.

BRIEF DESCRIPTION OF THE FIGURES

[0026] Various features will become apparent to those skilled in the art from the following detailed description of the disclosed non-limiting embodiments. The drawings that accompany the detailed description can be briefly described as follows:

[0027] Fig. 1 depicts a high-level view of a toll-free management platform, in accordance with an embodiment of the current disclosure;

[0028] Fig. 2 depicts a simplified illustration of a toll-free management platform, in accordance with an embodiment of the current disclosure; [0029] Fig. 3 depicts a schematic view for a decision tree for the Customer Record Template Builder (CRTB), in accordance with an embodiment of the current disclosure;

[0030] Fig. 4 depicts a schematic of an example conceptual Call Processing Record (CPR) Routing Tree, in accordance with an embodiment of the current disclosure;

[0031] Fig. 5 depicts a simplified flow diagram for constructing a call routing template based at least part on natural language inputs from a user, in accordance with an embodiment of the current disclosure;

[0032] Fig. 6 depicts a schematic view of a routing tree based disaster recovery and performance statistic structure, in accordance with an embodiment of the current disclosure;

[0033] Fig. 7 depicts a schematic view of a customer dashboard structure, in accordance with an embodiment of the current disclosure;

[0034] Fig. 8 depicts a schematic view of a whitelist management for toll-free spam control system, in accordance with an embodiment of the current disclosure;

[0035] Fig. 9 depicts a schematic view of a Toll-Free Number (TFN) abuse reporting database for whitelist management for toll-free spam control system, in accordance with an embodiment of the current disclosure;

[0036] Fig. 10 depicts a toll-free smart services central registry deployed in conjunction with an existing toll-free voice registry, in accordance with an embodiment of the current disclosure;

[0037] Fig. 11 depicts a candidate service enablement workflow deployed via a toll-free smart services central registry, in accordance with an embodiment of the current disclosure;

[0038] Fig. 12 depicts a schematic view of a systems page on a hard-flashed phone with a toll-free number, in accordance with an embodiment of the current disclosure;

[0039] Fig. 13 depicts a schematic view of a hard- flashed phone to a toll-free number that may be used for a customer or tech support call related to the phone, in accordance with an embodiment of the current disclosure;

[0040] Fig. 14 depicts a schematic view of a Toll-Free Service Provider ID (TSPID), in accordance with an embodiment of the current disclosure;

[0041] Fig. 15 depicts a schematic view of real time machine based routing tree enhancements, in accordance with an embodiment of the current disclosure;

[0042] Figs. 16-20 depict simplified schematic architecture views of toll-free Management Architectures, in accordance with embodiments of the current disclosure;

[0043] Fig. 21 depicts a schematic view of a system for predictive analytics based on toll-free number utilization, in accordance with an embodiment of the current disclosure; [0044] Figs. 22-26 depict a schematic view of a system for search result population based on customer profile/behavior, in accordance with embodiments of the current disclosure;

[0045] Fig. 27 depicts a simplified view of a toll-free Management Architecture, in accordance with an embodiment of the current disclosure;

[0046] Fig. 28 depicts a North American Numbering Plan Administration (NANPA) format, in accordance with an embodiment of the current disclosure;

[0047] Fig. 29 depicts a schematic of an SS7 architecture, in accordance with an embodiment of the current disclosure;

[0048] Fig. 30 depicts a schematic of toll-free call processing, in accordance with an embodiment of the current disclosure;

[0049] Fig. 31 depicts a schematic of toll-free business interactions, in accordance with an embodiment of the current disclosure;

[0050] Fig. 32 depicts a schematic of a toll-free IP Future State, in accordance with an embodiment of the current disclosure;

[0051] Fig. 33 depicts a schematic of a Number Administration future state, in accordance with an embodiment of the current disclosure;

[0052] Fig. 34 depicts a schematic view of a system for tagging toll-free numbers, in accordance with an embodiment of the current disclosure;

[0053] Fig. 35 depicts a schematic of a call routing future state, in accordance with an embodiment of the current disclosure;

[0054] Figs. 36-39 are schematic views of a one-click activation system, in accordance with embodiments of the current disclosure;

[0055] Fig. 40 is a schematic of a current system flow, in accordance with an embodiment of the current disclosure;

[0056] Fig. 41 depicts a Customer Record Status State Diagram, in accordance with an embodiment of the current disclosure;

[0057] Fig. 42 depicts a Customer Record Status State Diagram, in accordance with an embodiment of the current disclosure;

[0058] Fig. 43 depicts a schematic of a Carrier Identification Code (CIC) validations abbreviated summary flow from a service provider perspective, in accordance with an embodiment of the current disclosure;

[0059] Fig. 44 depicts a schematic of a Carrier Identification Code (CR) validations flow, in accordance with an embodiment of the current disclosure; [0060] Fig. 45 depicts a schematic of Service Control Point (SCP) interactions, in accordance with an embodiment of the current disclosure;

[0061] Fig. 46 depicts a schematic of an API interface used by Customer Record Administration and Number Administration components, in accordance with an embodiment of the current disclosure; [0062] Fig. 47 depicts a schematic representation of a disaster recovery scenario, in accordance with an embodiment of the current disclosure;

[0063] Fig. 48 is an example of hourly Responsible Organization Search activity, in accordance with an embodiment of the current disclosure;

[0064] Fig. 49 is an example of hourly Responsible Organization Reservation activity, in accordance with an embodiment of the current disclosure;

[0065] Fig. 50 is an example of hourly Responsible Organization Spare activity, in accordance with an embodiment of the current disclosure;

[0066] Fig. 51 depicts a graphical representation of daily customer records updates, in accordance with an embodiment of the current disclosure;

[0067] Fig. 52 presents a simplified call flow diagram showing the relationship between the TFMP, Responsible Organizations, and SCPs, in accordance with an embodiment of the current disclosure; [0068] Fig. 53 depicts mobile network operators and local exchange carriers that have networks established with national communication carriers, such as inter exchange carriers, in accordance with an embodiment of the current disclosure;

[0069] Fig. 54 depicts the toll-free management platform in associated with simplified call flows, in accordance with an embodiment of the current disclosure;

[0070] Fig. 55 shows an example embodiment of the Smart Toll-Free Aggregation providing a small footprint wiretap that is collocated within an SCP network, in accordance with an embodiment of the current disclosure;

[0071] Fig. 56 depicts the toll-free aggregation cloud that may be comprised of toll-free intelligence, and a reporting functionality for trend analysis and prediction, in accordance with an embodiment of the current disclosure;

[0072] Fig. 57 shows an example embodiment in which a call may originate in the Carrier Network Local Exchange, in accordance with an embodiment of the current disclosure;

[0073] Fig. 58 depicts distribution of toll-free routing data from the TFMP to SCPs in Service Provider networks, in accordance with an embodiment of the current disclosure;

[0074] Fig. 59 depicts the high-level architecture of the Data Distribution Hub, in accordance with an embodiment of the current disclosure; [0075] Fig. 60 shows the high-level architecture corresponding to alternate route provisioning, in accordance with an embodiment of the current disclosure;

[0076] Fig. 61 depicts a distribution channel that includes at least in part network operators and RaaS providers, in accordance with an embodiment of the current disclosure;

[0077] Fig. 62 depicts a certified distributor distribution channel, in accordance with an embodiment of the current disclosure;

[0078] Fig. 63 depicts a distribution channel using a certified routing database, in accordance with an embodiment of the current disclosure;

[0079] Fig. 64 depicts this distribution channel, in accordance with an embodiment of the current disclosure;

[0080] Fig. 65 depicts a sample Data Distribution Hub system architecture, in accordance with an embodiment of the current disclosure;

[0081] Fig. 66 depicts Data Distribution Hub system interfaces, in accordance with an embodiment of the current disclosure;

[0082] Fig. 67 depicts a sample Data Distribution Hub System virtual machine view, in accordance with an embodiment of the current disclosure;

[0083] Fig. 68 depicts a sample SCP application architecture, in accordance with an embodiment of the current disclosure;

[0084] Fig. 69 depicts a sample Data Distribution Hub software architecture, in accordance with an embodiment of the current disclosure;

[0085] Fig. 70 depicts a sample SCP and Data Distribution Hub interface interaction, in accordance with an embodiment of the current disclosure;

[0086] Fig. 71 depicts a Data Distribution Hub server, in accordance with an embodiment of the current disclosure;

[0087] Fig. 72 depicts a sample Data Distribution Hub process flow, in accordance with an embodiment of the current disclosure;

[0088] Fig. 73 depicts a system for validating a telephone service request, in accordance with an embodiment of the current disclosure;

[0089] Fig. 74 depicts another system for validating a telephone service request, in accordance with an embodiment of the current disclosure;

[0090] Fig. 75 depicts a method of validating a telephone service request utilizing the system of Fig. 74, in accordance with an embodiment of the current disclosure;

[0091] Fig. 76 depicts data structures utilized by the system of Fig. 74, in accordance with an embodiment of the current disclosure; [0092] Fig. 77 depicts a system for validating a telephone service request, in accordance with an embodiment of the current disclosure;

[0093] Fig. 78 depicts a system for delegated authentication code generation, in accordance with an embodiment of the current disclosure;

[0094] Fig. 79 depicts a process for uploading a letter of authorization by a delegated code requestor, in accordance with an embodiment of the current disclosure;

[0095] Fig. 80 depicts a process of a letter of authorization request being transmitted, in accordance with an embodiment of the current disclosure;

[0096] Fig. 81 depicts a process for a get status request, in accordance with an embodiment of the current disclosure;

[0097] Fig. 82 depicts an approval and/or rejection for numbers and authorization codes, in accordance with an embodiment of the current disclosure;

[0098] Fig. 83 depicts a process for requesting and/or retrieving an authentication code, in accordance with an embodiment of the current disclosure;

[0099] Fig. 84 depicts a number verification process, in accordance with an embodiment of the current disclosure;

[00100] Fig. 85 depicts a submission request for generation and/or regeneration of a number authentication code, in accordance with an embodiment of the current disclosure;

[00101] Fig. 86 depicts a process for Do Not Originate (DNO) batching, in accordance with an embodiment of the current disclosure;

[00102] Fig. 87 is a flowchart depicting a method for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure;

[00103] Fig. 88 is a flowchart depicting another method for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure;

[00104] Fig. 89 is a block diagram depicting an apparatus for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure;

[00105] Fig. 90 is a block diagram depicting another apparatus for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure;

[00106] Fig. 91 is a flowchart depicting a method for routing a telecommunication message, in accordance with embodiments of the current disclosure;

[00107] Fig. 92 is a flowchart depicting another method for routing a telecommunication message, in accordance with embodiments of the current disclosure;

[00108] Fig. 93 is a flowchart depicting a method for mitigating telecommunications fraud, in accordance with embodiments of the current disclosure; and [00109] Fig. 94 is a flowchart depicting another method for mitigating telecommunications fraud, in accordance with embodiments of the current disclosure.

[00110] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the methods and systems disclosed herein.

DETAILED DESCRIPTION

[00111] The present disclosure will now be described in detail by describing various illustrative, non-limiting embodiments thereof with reference to the accompanying drawings and exhibits. The disclosure may, however, be embodied in many different forms and should not be construed as being limited to the illustrative embodiments set forth herein. Rather, the embodiments are provided so that this disclosure will be thorough and will fully convey the concept of the disclosure to those skilled in the art. The claims should be consulted to ascertain the true scope of the disclosure.

[00112] With reference to Fig. 1, a Toll-Free Management Platform (TFMP) 100 includes methods and systems for number administration 102, customer administration 104, call management services 108, texting services 110 and text registry, and a smart services registry 112, as described herein.

The TFMP may allow users to search for, receive recommendations for, and make reservations of toll-free numbers 114. A user interface may allow activating a toll-free number, for example through a one-click activation function 118, as described herein. Users may access the TFMP to create and access existing templates 120 of toll-free call routing templates, and utilize a routing tree engine 122 to create customized call routing trees for the toll-free numbers of interest to the user. A Toll-Free Service Provider ID “TSPID,” 124 may provide an aggregate identifier for Service Registrars, who provide services such as, but not limited to, SMS, MMS, video conferencing, and streaming content. Predictive analytic services 128 may be provided that allow a user 154 through a customizable user interface, or “dashboard,” 132 to access third party data sources 144 and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers 140, service control points 144, call centers 142, or other parties affiliated with a toll-free telecommunication network 138. Access to third party data sources 146 outside of the TFMP 100 may be, for example, through the Internet 150, a cloud computing environment 148, a virtual private network, or some other connectivity. A user 154 may access the reporting capabilities of the TFMP through a client device 152, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration (Figure 2). [00113] With reference to Fig. 2, the main functional components of the TFMP 100, illustrating examples of the functionality provided by the TFMP and interfaces 204 to the TFMP 100. The NA function 102 may allow toll-free providers to search a pool of toll-free numbers using specified criteria and reserve numbers that will be used by toll-free subscribers, and perform CR administration 104. This functionality may include, but is not limited to, storing toll-free provider and telecommunications data 210, reporting processes 212, billing, and service control point (SCP), and management functionality 220 for the coordination with SCPs 222.

[00114] Responsible organizations, also referred to herein as “RespOrgs,” 202, may utilize the TFMP 100. In embodiments, a RespOrg may be a telephone number service provider. Reporting from the TFMP 100 may be back to RespOrgs or to other systems and platforms 124 that are external to the TFMP 100. The TFMP enables searching for any random number or to search for a plurality of numbers that are consecutive and/or include an indicated combination of digits. Since certain toll- free number codes (e.g. 800) and combinations of digits (e.g. repeating digits, digits whose corresponding telephone keypad letter values spell a word or phrase) may be considered most desirable, the NA function 102 includes capabilities for searches and reservations to be handled so that a toll-free provider does not gain an advantage to reserve a given toll-free number.

[00115] The TFMP 100 also enables tracking the overall assignment of numbers for each toll-free provider to enforce regulations for toll-free number allocation specified by a tariff. NA may maintain a status for each number that reflects whether it has been reserved and whether a customer record has been created and sent to SCPs. It is possible to query the TFMP 100 for status and reservation information associated with a toll free number.

[00116] A view of the main functional components which is intended to illustrate the functionality provided by embodiments of the system and is not intended to reflect design or implementation of the current system or a potential replacement system. In addition to the functional components embodiments may alternatively or additionally provide Operations, Administration, Maintenance, and Provisioning (OAM&P) capabilities to configure, maintain, monitor and audit the system. [00117] The NA function 102 facilitates toll-free service providers to search the pool of toll-free numbers using specified criteria and reserve numbers that can be used by toll-free subscribers. It is possible to search for any random number or to search for a number or numbers that may be consecutive and/or include an indicated combination of digits. Numbers may be reserved on a First In — First Out basis. It is also necessary to track the overall assignment of numbers for each toll-free service provider in order to enforce regulations for toll-free number allocation specified by a tariff. [00118] The NA function 102 may maintain a status for each number that reflects whether it has been reserved and whether a customer record has been created and sent to SCPs. It is possible to query embodiments of the system for status and reservation information associated with a number. [00119] A reserved toll-free number becomes active when routing information for the number, specified in a CR, is uploaded into SCPs. The CR administration 104 function facilitates toll-free service providers to create a CR and to specify when the information should be sent to SCPs.

Records can be updated or deleted and the send time can be updated prior to sending. Once a CR has been sent, a record can be created to update or delete the routing specified by the previous record.

The routing information specified in a customer record may typically includes: a. An Area of Service (AOS) that specifies from where the toll-free number can receive calls; b. The carrier that can route calls to the toll-free number; c. The terminating number that can receive calls to the toll-free number; and d. Optionally, a set of rules that specifies different routing based on criteria like time of day and area from where the call originated.

[00120] Carriers who have arrangements to carry calls for a toll-free service provider may approve the CR when routing for a toll-free number has been assigned to the carrier. The CR administration 104maintains a list of carriers and preferences for whether approval is required when a toll-free service provider indicates the carrier in a CR. A notification is sent carrier when approval of a CR is required. Each CR has an associated status. CRs can be queried to view the status and information contained in the record, based on the permissions of the user.

[00121] The user interface function facilitates manual access for human users and mechanized access for systems to make use of the NA and CR functions. The mechanized interface provided by a current system is known as Mechanized Generic Interface (MGI). Capabilities may be required for external users to establish data connectivity with embodiments of the system and gain access to the available functions. In embodiments, the system can maintain logins and passwords to provide security to limit system access to only authorized users. Permission levels that restrict access to system functions and to proprietary data may be assigned for each authorized user. In addition, the user interface function may provide notifications and other information to external users using mechanisms such as email and File Transfer Protocol (FTP).

[00122] In embodiments, interfaces are maintained to send routing information from CRs to SCPs. The SCP Management Function manages interactions with SCPs, including maintaining data connectivity, sending CR information at the specified date and time and monitoring responses in order to update customer record status. The SCP interface is specified by TM-STS-00798, CMSDB/SMS Interface Specification Manual and Interface Message Manual.

[00123] The SCP Administration functions allow users to establish and modify SCP-related reference data in embodiments of the system and send messages to the SCP node and the Call Management Services Database (CMSDB) within the SCP to manage data tables at the SCP.

[00124] Network management functions for toll-free database service involves the management of various automatic capabilities intended to monitor and control toll-free query traffic and calling volumes at the Service Control Points, Service Switching Points, terminating switches and terminating subscriber lines. When various call volume thresholds may be exceeded, the SCPs trigger Automatic Code Gapping (ACG) controls at the originating SSPs. The Network Management functions allow network managers to configure and adjust the relevant control parameters. Data collection at the SCPs can be requested to provide network managers with relevant surveillance information useful to monitor traffic and analyze problems, such as the detection of SCP overloads and excessive calling or excessive ineffective attempts to dialed codes.

[00125] To track user actions, system events, and performance statistics and format the information into reports for toll-free service providers and system administrators, embodiments of the system may provide capabilities for users to request reports and for delivery of report results in various formats. Reports may be requested online by users as per the assigned permissions and delivered over the interface on which the report was requested. It is also possible for users to request reports offline. Offline reports may be compiled in embodiments by the system administrator using information provided by the system. It should be appreciated that other requests may be performed. [00126] The disclosed embodiment may track and report on events that can result in charges to toll-free service providers. A tariff specifies the rate elements that can result in charges on a monthly bill and the rate to be charged. A tariff specifies the rate elements that can result in charges on a monthly bill and the rate to be charged. These include establishment of a system logon ID, monthly access to the system, reservation of a toll-free number, and report requests. Information provided by embodiments of the system is needed to calculate monthly charges and create monthly bills that may be sent to each toll-free service provider.

[00127] The user interface function facilitates manual access for human users and mechanized access for systems to make use of the NA and CR functions provided by the disclosed embodiment. The mechanized interface provided by the current system is known as Mechanized Generic Interface (MGI). Capabilities may be required for external users to establish data connectivity with the system and gain access to the available functions. The system maintains logins and passwords to provide security to limit system access to only authorized users. Permission levels that restrict access to system functions and to proprietary data may be assigned for each authorized user. In addition, the user interface function provides notifications and other information to external users using mechanisms such as email and File Transfer Protocol (FTP).

[00128] The security function defines a security framework that identifies the aspects of a system or service that require security and the methods available to address the security threats for each. From a security perspective, a system or service can be viewed as consisting of user, control and Management planes. Each plane includes infrastructure, services, and application layers.

[00129] Toll free may have unique IP requirements. The North American Numbering Plan Administration (NANPA) administers geographic numbers. Number portability is handled through the Number Portability Administration Center (NPAC). Toll-free numbers require enhanced number management capabilities for the following primary reasons: a. The significantly higher search load on NPAC due to unique toll-free search patterns diluting and distracting from its core purpose. b. Toll-free numbers have strict rules around hoarding, bartering, auctioning and fair trade practices. c. Toll-free numbers differ in their access patterns compared to geographic numbers: d. Toll-free numbers have to go through an allocation process for assignment and sparing, as specified by the FCC. e. Toll-free numbers have strict rules around hoarding, bartering, auctioning and fair trade practices.

[00130] Prior to assigning toll-free numbers, owners traverse a validation and vetting process to establish identity compared to straight number allocation for a geographic number. Vanity toll-free numbers typically may be searched millions of times during a day compared to 100s of searches for a geographic number in an entire year.

[00131] Toll-free number portability has its own set of rules that may be more strict and different from geographic numbers. Relying solely on the geographic number NPAC would be inadequate since toll-free numbers differ in their use and management from geographic numbers.

[00132] The NA function 102 may allow toll-free providers to search a pool of toll-free numbers using specified criteria and reserve numbers that will be used by toll-free subscribers, and perform CR administration 218. This functionality may include, but is not limited to, storing toll-free provider and telecommunications data 210, reporting processes 212, billing, service control point (SCP), and management functionality 220 for the coordination with SCPs 222. Responsible organizations, also referred to herein as “RespOrgs,” 202, may utilize the TFMP 100. Reporting from the TFMP 100 may be back to RespOrgs or to other systems and platforms 224 that are external to the TFMP 100. The TFMP 100 facilitates searching for any random number or to search for a plurality of numbers that are consecutive and/or include an indicated combination of digits. Since certain toll-free number codes (e.g. 800) and combinations of digits (e.g. repeating digits, digits whose corresponding telephone keypad letter values spell a word or phrase) may be considered most desirable, the NA function 102 includes capabilities for searches and reservations to be handled so that a toll-free provider does not gain an advantage to reserve a given toll-free number. The TFMP also enables tracking the overall assignment of numbers for each toll-free provider in order to enforce regulations for toll-free number allocation specified by a tariff. The NA function 102 may maintain a status for each number that reflects whether it has been reserved and whether a customer record has been created and sent to SCPs. It is possible to query the TFMP 100 for status and reservation information associated with a number.

[00133] The TFMP 100 enables customer record administration, allowing toll-free providers to create a customer record and to specify when the information should be sent to SCPs. A reserved toll-free number may become active when routing information for the number, specified in a customer record, is uploaded into SCPs. Customer records may be updated or deleted and the send time updated prior to sending. Once a customer record has been sent, a new record may be created to update or delete the routing specified by the previous record. The routing information specified in a customer record may include, but is not limited to:

• An Area of Service (AOS) that specifies from where the toll-free number can receive calls

• The carrier that will route calls to the toll-free number

• The terminating number that will receive calls to the toll-free number

• A set of rules that specifies different routing based on criteria like time of day and area from where the call originated

[00134] Carriers who have arrangements to carry calls for a toll-free provider may wish to approve customer records when routing for a toll-free number has been assigned to the carrier. The customer record function may maintain a list of carriers and preferences for whether approval is required when a toll-free provider indicates the carrier in a customer record. A notification may be sent to a carrier when approval of a customer record is required. In embodiments, each customer record may have an associated status. Customer records may be queried to view the status and information contained in the record, based on the permissions of the user.

[00135] In another disclosed non-limiting embodiment, the TFMP may include a user interface functionality that allows manual access for human users and mechanized access for systems (such as an application programming interface) to make use of the NA and CR functions provided by the TFMP. The user interface functionality may be embodied in a distributed computing environment, such as a “cloud” based computing network. In another embodiment, the user interface functionality may be embodied in hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks). The mechanized interface provided by the TFMP may also allow external users to establish data dynamic connectivity with the platform and gain access to its available functions. The TFMP may maintain logins, passwords, encryption, authentication, and the like to provide security to limit system access to only authorized users. Permission levels that restrict access to TFMP’s functions and to proprietary data may be assigned for each authorized user, and stored locally or remotely to an enterprise utilizing the TFMP, including within a computing storage facility that is remote to, but operatively coupled, with the TFMP. In embodiments, the user interface functionality may provide real time notifications and other information to external users using mechanisms such as email and File Transfer Protocol (FTP).

[00136] In another disclosed non-limiting embodiment, the TFMP may provide an interface to send routing information from CRs to SCPs. The SCP Management Function of the TFMP may enable management of interactions with SCPs, including maintaining data connectivity, sending CR information at the specified date and time, and monitoring responses in order to update customer record status. The SCP interface may include an interface that is based on the specification provided by TM-STS-00798, CMSDB/SMS Interface Specification Manual and Interface Message Manual. [00137] In another disclosed non-limiting embodiment, the SCP administration functions of the TFMP may allow users to establish and modify SCP-related reference data in the system and send messages to the SCP node and the Call Management Services Data Base (CMSDB) within the SCP to manage data tables at the SCP. Network management functions for toll-free database services may involve the management of various automatic capabilities intended to monitor and control toll- free query traffic and calling volumes at the SCPs, Service Switching Points, terminating switches, terminating subscriber lines, and the like. When various call volume thresholds are exceeded, the SCPs may trigger Automatic Code Gapping (ACG) controls at the originating SSPs. The TFMP’s management functions may allow network managers to configure and adjust relevant control parameters. Data collection at the SCPs may be requested through the TFMP to provide network managers with surveillance information that is useful to monitor traffic and analyze problems, such as the detection of SCP overloads and excessive calling or excessive ineffective attempts to dialed codes. [00138] In another disclosed non-limiting embodiment, the TFMP may enable reporting functionalities that allow tracking user actions, system events, performance statistics, and other events and formatting the information into reports for toll-free providers and system administrators· The TFMP may provide capabilities for users to request reports and for delivery of report results in a plurality of formats. Reports may be requested online by users as per the assigned permissions and delivered over the interface on which the report was requested. Requests may be made from any computing facility, including, but not limited to, a personal computer, laptop computer, tablet, mobile communication facility (such as a smart phone), or some other type of computing device. It may also be possible for users to request reports off-line using the TFMP. For example, a system administrator using information provided by the platform may dynamically compile off-line reports. In embodiments, the TFMP may track and report on real time events that will result in charges to toll-free providers. A tariff specifies the rate elements that may result in charges on a monthly bill and the rate to be charged. These may include, but are not limited by, establishment of a system logon ID, monthly access to the system, reservation of a toll-free number, report requests, or some other type of element. Information provided by the TFMP may be needed to calculate monthly charges and create monthly bills that are sent to each toll-free provider.

[00139] The current practice of managing toll-free numbers and activities, and the tools currently available to users for building a complex customer record, are very often single threaded and cumbersome. In addition, the current industry practices do not provide the ability to define a default customer record for a user, in part because it may not be intuitive to build a complex customer record. According to the methods and systems presently disclosed, the TFMP may provide tools that work intelligently with the user, allowing a natural language input, such as English words, to translate and map such language to signifiers that may be less familiar to a user, such as call routing codes. This translation and mapping of natural language to toll-free number management information and data may produce a dynamic, complex customer record, including using existing user records and usage data, to populate information for the user. This may speed the creation of complex routing and other metadata that is associated with a toll-free line, based at least in part on the TFMP enabling the dynamic querying of the real time status of data that is associated with a toll- free number, guide the user in providing the necessary natural language information that allows the TFMP to map such language to toll-free number metadata (e.g., routing codes), and store and implement a complex decision tree describing the actions to take for a given toll-free number.

[00140] In an example, the TFMP may provide a user interface in which a user types a command such as “Route all incoming calls made to toll-free numbers having the extension 571 to the technical support staff.” The TFMP may take this natural language input and map it to routing codes or other data corresponding to the natural language. In another example, the natural language may be selected from a menu that is provided in the user interface of the TFMP, provided via voice command using voice recognition software, via scanned text that is input to the TFMP, or using some other means of conveying natural language. The Customer Record Template Builder (CRTB) of the TFMP may allow building a complex customer record template using a user interface, enabling that record to be designated as the default customer record. Using the TFMP, a toll-free provider may build multiple complex customer record templates for their use and define a record as the default customer record, allowing the user to select the default with a single click, thus reducing their work effort.

[00141] In another disclosed non-limiting embodiment, the CRTB may lead a user through an initial customer data population (known as the Customer Administrative Data (CAD) portion), and also the call routing logic (Call Processing Record; known as the CPR portion) that is associated with a toll- free number, by utilizing the TFMP user interface to construct a decision tree logic structure with defined data nodes derived from the user’s natural language inputs.

[00142] Based upon the decisions at the nodes in the decision tree that is constructed by the TFMP, the user interface may drive down a branch to a new decision node ultimately driving the customer record decision logic to the lowest level. In embodiments, decision trees constructed by the TFMP based on a user’s input may represent a series of decision points. Each decision point may be called a node and off of each node may be one of more branches. The point at which there are no more decisions to be made may be referred to as a leaf and used as the “end point" of a branching structure.

[00143] Figure 3 illustrates an example generic visualization of one possible decision tree structure 300 created by the TFMP 100. For example, a call to a particular toll-free number may initially have a node 302 based on the area code from which the toll-free number is called, to segregate an East Coast or West Coast technical support staff. Then, the next node may be a time node to segregate the time of day between business hours where the call is routed to the technical support staff, or after business hours where the call is routed to a voice-mail system. The decision tree may further branch into “leaves” 304, 308 to indicate additional routing rules, such as specifying a single termination number for a received call to be routed to, a particular department within an organization, or some other routing tree rule. The TFMP performs such routing essentially instantaneously or near instantaneously.

[00144] In another disclosed non-limiting embodiment, the CAD portion of the CRTB may logically lead a user to populate information including, but not limited to, the following: • Administrative data about the toll-free customer o Toll-Free Number o Effective Date and Time o Control Toll Free Provider Identifier o End Customer Name o End Customer Address

• Area of Service (AOS)

• List of destination telephone number(s)

• Carrier Identification Codes (CICs) for IntraLATA and InterLATA traffic [00145] In another disclosed non-limiting embodiment, complex customer record (CPR) decision nodes that may be supported by the TFMP include, but are not limited to, the following:

• Originating State

• Originating Numbering Plan Area (NPA)

• Originating LATA

• Originating Plain Old Telephone System (POTS) Central Office Exchange (NXX)

• Originating POTS NPANXX

• Originating POTS number

• Specific date

• Day(s) of the week

• Time-of-day range

• Percent load share, which may be used to automatically direct different percentages of processed queries (calls) to different branches below the node.

[00146] In another disclosed non-limiting embodiment, the “leaves” that may be supported by the TFMP data model at the ends of a given branch include, but are not limited to, the following:

• Destination Telephone Number

• Carrier

• Announcement Treatment

[00147] With reference to Fig. 4, a simplified depiction of a customer record routing, created using the TFMP, is provided. In this simple example, starting from the left-most branched path, the three decision paths corresponding to the decision trees branched paths may be represented as a routing from a toll-free number 400, detecting an area code 402, an exchange 404, carrier 408, and terminating telephone number 410, as in the following example: 1. Area Code = 732, NXX={699,494},Camer=ATX-0288, Tel#=800-234-5678

2. Area Code = 732, NXX=Other, Carrier=MCI-0222, Tel#=800-234-5678

3. Area Code = Other, NXX=<null>, Carrier=MCI-0222, Tel#=800-234-5678. [00148] Continuing the example of Fig. 4 using the TFMP, the CRTB toll may be built in such a manner to allow a user to work though the decision tree and anticipate / prepopulate information based upon the information already provided in this build or also information provided in previous customer record entries. Once a default customer record template is built, the TFMP may invoke this template when creating a customer record for a new number, thus reducing the time and effort for a subsequent customer record to be built. Invocation of the default customer record template by the TFMP may also serve to reduce human error associated with the manual creation of such records insofar as the template may already embody necessary data, thereby not requiring a user to remember or retrieve the same.

[00149] With reference to Fig. 5, the methods and systems of the present disclosure may provide for pre-populating a call routing template based on natural language inputs including, associating a natural language element 500 with a telecommunications routing code 502, the telecommunications routing code associated with decision tree logic associating routing of incoming calls to a toll-free number 504; storing the association in a database 508 that is associated with a toll-free telecommunications system; receiving a natural language input 512 from a user 510, the natural language input 512 may include the natural language element 500; selecting the telecommunications routing code 514 based at least in part on the stored association 504; populating the telecommunications routing code 518 at a node of a call routing decision tree 520 to generate a populated call routing decision tree 522; and storing the populated call routing decision tree as a call routing template 524 that may be identified and presented to a user interface based at least in part on the natural language input.

[00150] In embodiments, a natural language input may be a text or voice element. A text element may be a scanned text element. A voice element may be obtained by voice recognition software. [00151] In embodiments, the decision tree logic may determine the call path taken by an incoming toll-free call to a termination number, the call path taken by an incoming toll-free call based at least in part on the time of day the incoming call is received, the call path taken by an incoming toll-free call based at least in part on the geographic location of the device from which the incoming call is received, the call path taken by an incoming toll-free call within a business entities telecommunications system, or some other call path outcome.

[00152] Further provided herein are methods and systems for creating a call routing decision tree, the system comprising a user device of a user configured to receive a natural language input from a user; select a stored call routing template, wherein the selection is based at least in part on a stored association of the call routing template and a natural language element that is included in the natural language input; present the stored call routing template to the user within a graphic user interface; receive a command from the user, through the graphic user interface, to associate the selected call routing template with a toll-free number indicated by the user; and store the association between the call routing template and the toll-free number.

[00153] In embodiments, the command from the user may be text-based, such as a text-based item that is presented within the graphic user interface in a menu or other location. In embodiments, the command may be a voice command.

[00154] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00155] A method of pre-populating a call routing template based on natural language inputs comprising: associating a natural language element with a telecommunications routing code, the telecommunications routing code associated with decision tree logic associating routing of incoming calls to a toll-free number; storing the association; receiving a natural language input from a user, wherein the natural language input includes the natural language element; selecting the telecommunications routing code based at least in part on the stored association; populating the telecommunications routing code at a node of a call routing decision tree to generate a populated call routing decision tree; storing the populated call routing decision tree as a call routing template that may be identified and presented to a user interface based at least in part on the natural language input.

[00156] A system for creating a call routing decision tree, the system comprising: a user device of a user configured to: receive a natural language input from a user; select a stored call routing template, wherein the selection is based at least in part on a stored association of the call routing template and a natural language element that is included in the natural language input; present the stored call routing template to the user within a graphic user interface; receive a command from the user, through the graphic user interface, to associate the selected call routing template with a toll-free number indicated by the user; and store the association between the call routing template and the toll-free number.

[00157] In embodiments, and with reference to Fig. 6, the TFMP may facilitate determining toll- free network congestion in real-time. The TFMP system may include a subsystem, referred to as a “node,” and in this example embodiment called the Percent (%) Node 602. This node may be used to build a decision tree that is downloaded to the SCPs. The Percent Node may allow a tree to be built so that a certain percentage of the calls are routed to different branches on the call tree. The Percentage may be whole numbers and can range from 0% to 100%, with the total percentage for all sibling branches not to exceed 100%. This may allow Resp Orgs to use the TFMP as their disaster recovery routing for a toll-free number. In an example, a call routing tree may be built with multiple branches to different locations, such as terminating numbers. In a normal situation, 100% of the calls may go to a main location 604. In a disaster, which could be a carrier system failure, for example, and which may originate outside of the carrier itself, a call routing table created according to the Percent Node and related rules may allow that all calls are diverted to another branch 608, 610 on the tree that uses a different carrier.

[00158] In embodiments, real time network data may be used by the TFMP to create, and allow Resp Orgs to use, a “congestion threshold” node in the call routing tree. This may allow a Resp Org to determine with an end subscriber the appropriate congestion threshold for each branch in a call routing table. For example, if one call center can only handle 200 calls per minute before calls are placed in queue, and statistics show for this end subscriber that wait times start to creep up to 20 minutes when 1000 calls per minutes are received, and they do not want this to occur, the ability to obtain real time call counts/congestion will allow the SCP to route the calls using call counts/congestion in addition to all the other possible call decision nodes. Call counts may be very specific to an end subscriber, and congestion thresholds may differ and depend on congestion on the line as a whole. The congestion measurement and threshold value may allow detecting congestion issues and routing to another branch, including one that may be in a different area, should a congestion threshold be reached. This may occur in real-time without a need to change the routing tree. The TFMP may confirm real-time call count information that is available from SCPs and use such data to confirm real-time network congestion. Call count information may be further organized and analyzed by TSPID to permit tracking, for example, by service provider.

[00159] In embodiments, nodes in a call routing table may be mapped to real-time information in the SCPs from the network. With the decision nodes embedded in the call tree and loaded into the SCPs, real-time routing may be provided by the TFMP. In embodiments, a call routing table may be a crowd-sourced translation table associated with the TSS that may enable mapping of service providers to unique identifiers, as described herein. Such a mapping would enable a registry that may be used by third parties to locate the plurality of identifiers that may be associated with a service provider or plurality of service providers.

[00160] In embodiments, nodes in a call routing table may be used to facilitate predictive analytic services that may be provided to allow a user, through the customizable user interface, or “dashboard,” to access third party data services, sponsored data and information derived from toll- free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll-free telecommunication network. Nodes in a call routing table may also be utilized with origination data that may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trends and prices on an interactive map via the TFMP.

[00161] In embodiments, nodes in a call routing table may be used to facilitate reporting capabilities of the TFMP through a client device, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration.

[00162] In embodiments, the TFMP may determine accessibility among VoIP and tandem calls.

For example, with VoIP the TFMP may ping an IP address at regular intervals to determine status. Using real-time network information and static call routing information, the TFMP may create a real- time call path score. SCPs may also be a source of real-time call routing data. SCPs are in the call path of every toll-free call. The ability to collect real-time data about every call, and every carrier, based on dates, times, day of week, and locations are available to SCPs. Using this information it is possible to extrapolate and determine uptime, downtime, congestion, geographical movement and economic movement of people communicating via calls. Based on real-time data that can be obtained from the SCPs and from the network, the TFMP may create a score that can be assigned to each call decision node. Similar to a mapping algorithm that uses distance and speed limit, given a starting point and a destination, the quickest or shortest map may be mapped. Changes in the call routing tree may be dependent upon an update to the routing tree that is then validated by the TFMP and then downloaded to the SCPs. With the use of real-time data, and more network decisions nodes added to a call routing tree based on the needs of the end subscriber, the TFMP may provide the ability to allow an end subscriber to have real-time business continuity for their toll-free number instead of having to contact their service provider, or getting a ticket opened to update their routing tree, and then having it download to all the SCPs for the new routing to take place. [00163] In embodiments, a call path score and real-time routing may be based on the best possible availability score. This may also be modified by the TFMP to allow for lowest cost score, based on the per-call and per-minute cost for particular carrier. The call score may be updated during low activity periods with a date/time stamp associated with it. This may allow real-time, or near real time, detection of a path’s status. Upon completion of a call down a particular path, the TFMP may also update the call path score, thereby keeping the score up-to-date.

[00164] In embodiments, nodes in a call routing table may be used to facilitate determination of the call path score such that real-time routing may be displayed via a distributed computing environment, such as a cloud-based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub- combination of such networks).

[00165] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00166] A method comprising: creating at least two toll-free call routing tables based on a congestion threshold criterion, wherein the first of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are below the congestion threshold, and the second of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are equal to or above the congestion threshold; providing the call routing tables to at least one service control point that is associated with the toll-free telecommunications carrier network; monitoring toll-free call volumes and durations occurring within a toll-free telecommunications carrier network; receiving at least one of a call count datum or call duration datum from the toll-free telecommunications carrier network wherein the call count datum or call duration datum indicates a change in call volumes over the toll-free telecommunications carrier network from below the congestion threshold to above the congestion threshold; and instructing the service control point to switch from using the first call routing table to the second call routing table.

[00167] A method comprising: associating a toll-free telecommunications network congestion threshold criterion with a first rule regarding the usage of a plurality of call routing tables, and a second rule regarding the usage of a plurality of telecommunications carriers, wherein the congestion threshold criterion indicates a level of toll-free call volumes occurring within the toll-free telecommunications network; and switching toll-free calls across the telecommunications carriers based at least on the congestion threshold criterion, wherein the switched calls are further routing according to at least one of the plurality of call routing tables.

[00168] A method comprising: creating at least two toll-free call routing tables based on a congestion threshold criterion, wherein the first of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are below the congestion threshold, and the second of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are equal to or above the congestion threshold; providing the call routing tables to at least one service control point that is associated with the toll-free telecommunications carrier network; monitoring toll-free call volumes and durations occurring within a toll-free telecommunications carrier network; receiving at least one of a call count datum or call duration datum from the toll-free telecommunications carrier network wherein the call count datum or call duration datum indicates a change in call volumes over the toll-free telecommunications carrier network from below the congestion threshold to above the congestion threshold; creating a second congestion threshold criterion based on the data received from the toll-free telecommunications network; and creating a third call routing table based on the second congestion threshold criterion. [00169] In the current industry practice, updates and additions to toll-free providers numbers are not available through conventional platform reporting capabilities for up to 24 hours. This makes it difficult for end users to call up information about work done on the current day. If a toll-free number is reserved and for whatever reason the user does not record the actual number, there is often no way to find it, or a laborious search is required to assemble the necessary data elements for retrieval. One reason for the delay in the ability to report is that reporting is sourced from a Report History Data Base (RHDB) that is only populated with updates once a day. Additionally, most reporting from the RHDB is run in the background, thus in some cases, still further delaying the response.

[00170] With reference to Fig. 7, in another disclosed non-limiting embodiment, the TFMP 100 provides the user with the ability to report on its number portfolio in real time or near real time via an online customer dashboard 132. The online customer dashboard 132 may display simulated gauges and dials, business graphics such as pie charts, bar charts and graphs to provide overview that summarizes all pertinent data in one or two screens or views. The gauges and dials may be based upon real time data that is stored within the TFMP. The TFMP may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs for use with the dashboard. The decision tree may be used in various manners as otherwise described to facilitate call efficiency.

[00171] The online customer dashboard may allow the user to see all its customer data and drill down in the details in near real time. To do so, a data source for the dashboard may maintain the data in real time or near real time. The online customer dashboard may also be associated with a user profile and security administration that grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The platform or system can implement a role-based access control mechanism.

[00172] The online customer dashboard 132 may provide the user with a view into the user portfolio of toll-free number information. This may allow a user to see basic number information about the toll-free numbers the user has the authority to view. Predictive analytic services may also be provided that allow a user, through the customizable user interface, or dashboard, to access third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll-free telecommunication network. As elsewhere described, origination data may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trends and prices on an interactive map via the TFMP.

[00173] A user may also access the reporting capabilities of the TFMP through a client device, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’ s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration. Such systems may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00174] The online customer dashboard may utilize real time network statistics, sourced from carriers and the public domain, within an algorithm that provides a call path score. This call path score may be provided to LCR and SCPs to determine the net value of a route for display.

[00175] The online customer dashboard may also provide an alert system similar to Internet alerts for toll-free numbers. Numbers, or groups of numbers, may be tagged based on tag groups. The alert system for toll-free numbers may use a subscription prioritization engine and offer premium services for service prioritization.

[00176] The online customer dashboard for a toll-free voice registry may share reserved, assigned, and working numbers with the Toll-Free Texting and Smart Services Registry (TSS)

[00177] The online customer dashboard may initially provide a main dashboard screen from which the user may drill down within a specific toll-free number to investigate more detailed information thereof. In one example, the main dashboard screen may provide a base set, or minimum list of data elements that are available, including, but not limited to, the following:

• User Information o Toll Free Provider o User Id o Last Login o Amount of numbers reserved

• Number Information (a list of all toll free numbers associated with this provider) o Toll Free Number o Number Status o Date Reserved o Date Last Updated o Customer Name

[00178] The user can then drill down into the particular toll free number by clicking on that particular number to find more detailed information such as, Area of Service, Carrier(s), Call Routing, Reserve numbers, or other information associated with a toll-free number.

[00179] A user may also view the history of the number i.e. “the life of a toll-free number.” By selecting a particular toll free number, the history of use of the toll free number may be readily viewable. Various charts, timelines, and usage data may be included therein. This functionality may allow a user to view and report on the status and activities of an entire RespOrg in real time, rather than parts of a RespOrg’s activity and/or only at predefined time intervals (e.g., once per day). [00180] In another disclosed non-limiting embodiment, the online customer dashboard is not a view only tool, but may provide additional or alternative features to be customized by the user. That is individual users may select their desired types of information available via their dashboard.

[00181] Such features may include, but are not limited to, the following:

• Customer information updates from the dashboard.

• System alerts pertaining to all users

• Historical customer usage information and populate information to the user such as suggestions of available numbers

• Alerts announcing the upcoming availability of numbers that the customer has previously searched for

• Billing alerts and notification of payments made

[00182] Overall, the online customer dashboard may provide a single starting point for any user working with toll free numbers. Having a single location may allow a user of the system to use a single user interface (the dashboard) to view the entirety of activity that is associated with a plurality of toll-free numbers.

[00183] With reference to Figs. 8 and 9, the TFMP may include a toll-free number rating registry (TFRR) 802, that functions as a service to provide customers an indication of how often a toll-free number is abused, such as by fraudulent, frequent calling to increase billing costs. The rating may be calculated based on input from users, automated systems and/or proprietary algorithms that are collecting, storing and analyzing call data from throughout the toll-free system.

[00184] In embodiments, the system may collect toll-free number abuse information 804 from a plurality of sources including, but not limited to, a telephone service provider 808, toll-free number operators and Resp Orgs. The abuse information may be collected and processed in real-time to provide timely rating information for entities. In embodiments, the TFMP may publish standard interfaces that reporting parties can invoke to register abuse. Such interfaces may allow clients to connect synchronously and asynchronously. Interfaces may include, but are not limited to:

• A web page

• RestFul API

• Mobile application

[00185] In embodiments, the abuse reporting interfaces that are associated with the TFMP may be invoked in a manual or automated manner. In the case of service providers, the reporting of abuse may occur during call setup. This may necessitate that the reporting is automated and introduces the least load on the device reporting the abuse. In an example, an asynchronous API may be made available to service providers for this purpose. In another example, for call centers where toll-free numbers terminate, such as a technical support department of a company, call-center processing software may be enhanced to include a module to detect and report abuse.

[00186] Additionally, the TFMP may also provide a mobile or other application that small business and single toll-free number users can use to report abuse. The TFMP may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs.

The decision tree may be used in various manners to facilitate operation of the service as otherwise described to facilitate call efficiency. The service may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00187] In embodiments, to automate the processing of toll-free calls and reduce abuse, the TFMP system may be enhanced to allow customers to provision an abuse route. This route may be distributed to the SCPs along with current information being shared. When a service provider determines that a call being setup is an abuse call, they can use the abuse route specified by the customer.

[00188] With reference to Fig. 9, an example abuse reporting interface architecture 900 that is associated with the TFMP is provided. This abuse reporting interface may permit toll-free customers to report when a toll-free number abuse event occurs. The interface may allow for abuse to be reported manually and/or programmatically in an automated fashion. In embodiments, the abuse collection system described herein may collect information that includes, but is not limited to, the following:

• TFN 904

• Resp Org 908

• Date/time of abuse Date/time of report 909

• Originating number 910

• Has the originating number been verified as authentic (i.e., not spoofed) 912

• Geographic location of the originating number 920

• Geographic location of the terminating number 922 [00189] The abuse database 924 may also collect information about Resp Orgs and other industry details in an offline mode. The abuse information may be captured in the toll-free number abuse database 924. This information may then be processed using a rating engine 928 to compute the toll- free number rating. The rating engine 928 may take into account a plurality of factors including, but not limited to, input provided by Resp Orgs 928, TSPID’s associated with service providers, frequency of abuse 930, identified source of abuse, and the like, to compute a rating for the toll-free number. In the absence of specific reports of abuse, predictive analytics methods of the TFMP, as described herein, may be used to infer abuse or unusual call activity, the results of which may be used in computing a rating. In an embodiment, the identification of abuse may be an inference of an abuse event produced by a predictive analytics engine that is associated with the TFMP based on at least a call history and metadata relating to calls placed over the toll-free telecommunications number. In an example, 100 calls may be placed over a toll-free number, each of which by itself does not appear to be abusive. For example the calls may be placed from locations that do not appear suspicious. However, an inference of abuse, based at least in part on the totality of calls placed over the toll-free number, may be used by the predictive analytics engine that is associated with the TFMP to infer that abuse is occurring or has occurred. For example, the totality of the calls may indicate a pattern indicative of abuse, or a call frequency that is indicative of abuse or some other criterion that may be used by the predicative analytics engine to infer that an abuse event, or plurality of abuse events is occurring or has occurred. In embodiments, a toll-free number rating may be a number between “0” and “100” that provides an indication of how often the number is abused and/or how severe the abuse is. A number with “0” rating may indicate a number that is never abused, and a number with a “100” rating may indicate a number for which the majority of activity is abusive in nature. The toll-free number rating may be made available to users of the TFMP, and may be used to make routing and other decisions about the toll-free number.

[00190] Based on the rating of a toll-free number, the service provider may take a specific action to ensure legitimacy of a toll-free call. In addition to the number rating, the rating engine may also generate routing rules to be shared with service providers. These rules may be imported by the service provider into their call routing engine to automatically route abusive calls in a manner that is consistent with the routing rules. These rules may also be used in combination with user profiles and security administration may grant permissions to different groups of users to access the toll-free number rating to create, view, update and activate certain functions. The system can implement a role-based access control mechanism. Predictive analytic services may be provided that allow a user, through the customizable user interface, or “dashboard,” to access third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll- free telecommunication network. Origination data may also be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trend and prices on an interactive map via the TFMP.

[00191] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00192] A method comprising: storing a taxonomy of abuse events that may occur regarding the usage of a toll-free number; storing a rule regarding an action to take upon receipt of a reported abuse event, wherein the rule specifies a routing rule defining how a call that is associated with the abuse event is to be routed over a toll-free telecommunications system; receiving a report of abuse of a toll-free number; identifying at least one abuse event within the stored taxonomy and routing rule that is related to content of the abuse report; and automatically routing a call that is the subject of the abuse report according to the routing rule.

[00193] A method comprising: receiving a report of abuse of a toll-free number; identifying an absence of an abuse event definition within a stored taxonomy that is related to the type of abuse reported; storing a new definition of the abuse event within the taxonomy; and creating a routing rule defining how a call that is associated with the abuse event is to be routed over a toll-free telecommunications system.

[00194] A method comprising: storing a taxonomy of abuse events that may occur regarding the usage of a toll-free number; associating the abuse events in the taxonomy with a toll-free number rating action; receiving a report of abuse of a toll-free number; identifying at least one abuse event within the stored taxonomy and rating action that is related to content of the abuse report; automatically computing a rating for the toll-free number based on the rating action; and reporting the rating to an entity. [00195] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00196] A user device for presenting data to a user in real time regarding changes in metadata associated with a toll-free number, the user device configured to: receive an indication of a change in status of a toll-free communications number, wherein the telecommunications number is associated with a responsible organization that processes toll-free telecommunications; update a metadatum associated with the toll-free communications number based at least in part on the change in status; store the metadatum; receive a status request from a user relating to the responsible organization; present the user with a graphic representation of the telecommunications number’s status

[00197] A method of toll-free telecommunications data visualization comprising: presenting a data visualization dashboard to a mobile application on a client device, wherein the presentation includes a selectable listing of toll-free telecommunications data parameters; receiving a selection from the client device of the toll-free telecommunications data parameters to analyze and at least one type of data analysis to perform; retrieving, in substantially real time, data relating to the selected toll-free telecommunications data parameters; analyzing the data according to the at least one type of data analysis; and presenting to the mobile application a summary of an analytic result.

[00198] In another disclosed non-limiting embodiment, the TFMP may provide a click-to-chat tool. The click-to-chat tool enables users to quickly contact a support representative through the user interface, dashboard, or other interface. The click-to-chat tool may integrate with existing web based access, provides an immediate channel to a support representative, and may facilitate support training.

[00199] In another disclosed non-limiting embodiment, the TFMP may provide a simplified two- factor authentication tool for maintaining identity and access security (e.g. dual factor authentication). This may eliminate the need to use hard tokens and improve VPN accessibility. [00200] In another disclosed non- limiting embodiment, the TFMP may provide a password self- service tool that provides the ability for self-service passwords and unlock logon IDs. This may be automated via structured email processes. [00201] In another disclosed non-limiting embodiment, the TFMP may provide a real-time status update tool that provides number counts and tasks within the application. This may facilitate a real- time view of number counts and status (i.e. reserved, assigned, etc.)

[00202] In another disclosed non- limiting embodiment, the TFMP may provide integrated data stores and a reporting tool that integrates data stores for consolidated reporting. This may facilitate the creation of a single operational data store to eliminate separate software as a service licenses and consolidated reporting for responsible organizations.

[00203] In another disclosed non- limiting embodiment, the TFMP may provide a single sign-on tool for Web Based Access (WBA), mechanized generic interface (API), Website/Billing, Web-based Reporting System (WRS), Virtual Private Networks (VPNs), IP Multimedia Subsystem (IMS), or some other network type.

[00204] In another disclosed non- limiting embodiment, the TFMP may provide an enhanced configurability tool that allows administrators to configure the limit of TFN that can be reserved in a single request, for example, more than 10. This may provide, for example, up to 5000 (would then do 500 batch calls).

[00205] The present disclosure includes a toll-free management platform (TFMP) for providing services to toll free subscribers and providers, enabling them to manage a plurality of toll-free numbers and tasks associated with such numbers. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration.

[00206] The TFMP enables searching for any number, random number or to search for a plurality of numbers that are consecutive and/or include an indicated combination of digits. Since certain toll- free number codes (e.g. 800) and combinations of digits (e.g. repeating digits, digits whose corresponding telephone keypad letter values spell a word or phrase) may be considered most desirable, the NA function includes capabilities for searches and reservations to be handled so that a toll- free provider does not gain an advantage to reserve a given toll-free number. The TFMP also enables tracking the overall assignment of numbers for each toll-free provider in order to enforce regulations for toll-free number allocation specified by a tariff. NA may maintain a status for each number that reflects whether it has been reserved and whether a customer record has been created and sent to service control points (SCPs). It is possible to query the TFMP for status and reservation information associated with a number.

[00207] The TFMP enables customer record administration, allowing toll-free providers to create a customer record and to specify when the information should be sent to SCPs. A reserved toll-free number may become active when routing information for the number, specified in a customer record, is uploaded into SCPs. Customer records may be updated or deleted and the send time updated prior to sending. Once a customer record has been sent, a new record may be created to update or delete the routing specified by the previous record. The routing information specified in a customer record may include, but is not limited to:

• The carrier that will route calls to the toll-free number

• The terminating number that will receive calls to the toll-free number

[00208] Carriers who have arrangements to carry calls for a toll-free provider may wish to approve customer records when routing for a toll-free number has been assigned to the carrier. The customer record function may maintain a list of carriers and preferences for whether approval is required when a toll-free provider indicates the carrier in a customer record. A notification may be sent to a carrier when approval of a customer record is required. In embodiments, each customer record may have an associated status. Customer records may be queried to view the status and information contained in the record, based on the permissions of the user.

[00209] In another disclosed non- limiting embodiment, the TFMP may include a user interface functionality that allows manual access for human users and mechanized access for systems (such as an application programming interface) to make use of the NA and CR functions provided by the TFMP. Such systems may be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks). The mechanized interface provided by the TFMP may allow external users to establish data dynamic connectivity with the platform and gain access to its available functions. The TFMP may maintain logins, passwords, encryption, authentication, and the like to provide security to limit system access to only authorized users. Permission levels that restrict access to TFMP’s functions and to proprietary data may be assigned for each authorized user, and stored locally or remotely to an enterprise utilizing the TFMP, including within a computing storage facility that is remote to, but operatively coupled, with the TFMP. In embodiments, the user interface functionality may provide real time notifications and other information to external users using mechanisms such as email and File Transfer Protocol (FTP). [00210] In another disclosed non- limiting embodiment, the TFMP may provide an interface to send routing information from CRs to SCPs. The SCP Management Function of the TFMP may enable management of interactions with SCPs, including maintaining data connectivity, sending CR information at the specified date and time, and monitoring responses in order to update customer record status.

[00211] In another disclosed non- limiting embodiment, the SCP administration functions of the TFMP may allow users to establish and modify SCP-related reference data in the system and send messages to the SCP node and the Call Management Services Data Base (CMSDB) within the SCP to manage data tables at the SCP. Network management functions for toll-free database services may involve the management of various automatic capabilities intended to monitor and control toll- free query traffic and calling volumes at the SCPs, Service Switching Points, terminating switches, terminating subscriber lines, and the like. When various call volume thresholds are exceeded, the SCPs may trigger Automatic Code Gapping (ACG) controls at the originating SSPs. The TFMP’s management functions may allow network managers to configure and adjust relevant control parameters. Data collection at the SCPs may be requested through the TFMP to provide network managers with surveillance information that is useful to monitor traffic and analyze problems, such as the detection of SCP overloads and excessive calling or excessive ineffective attempts to dialed codes.

[00212] With reference to Fig. 10, in embodiments, the TFMP may provide a Toll-Free Texting and Smart Services Registry (TSS) 1000 to support toll-free telephone numbers and related services, such as SMS, MMS and streaming media. The TSS 1000 may include several components such as, but not limited to, number administration, call control and route provisioning, as well as number status assessment. The number administration function may provide number assignment for toll-free subscribers as well as provide services to manage the toll-free numbering plan. This component may provide for toll-free number portability as well as managing the mapping of toll-free numbers to geographic numbers. The number administration function may also open new number plan administration codes. The number administration function may forecast the exhaustion of codes and demand for codes for use by organizations such as the FCC.

[00213] The call control and routing function may be responsible for providing intelligent routing for calls made to toll-free numbers. Toll-free subscribers may have the ability to configure call routing to include multiple carriers, time of day rules, and rules based on the caller’s proximity, among others. These rules may be downloaded to real-time network routing databases or Service Control Points (SCPs) 1008. The number status assessment function may determine the availability of certain numbers. Numbers may be reserved and assigned according to activation date and then are deployed. The number status function may assess whether numbers are spare, reserved, assigned, or currently deployed.

[00214] Providers of various smart services, such as voice, media, or texting services, may be able to access the TSS that can be text enabled from a list of reserved, assigned, and working numbers. After numbers are identified, an automated online letter of authorization/agency may be executed. The letter of authorization/agency may independently demonstrate authorization to a responsible organization that maintains the registration for individual toll-free numbers in a distributed database. The distributed database may be associated with a distributed computing network, as described herein. Upon execution of the letter of authorization/agency, the information may then be provisioned to industry routing databases for delivering various services, such as SMS (text) messaging, MMS messaging 1010, and content streaming, including but not limited to video content as well as future services 1012.

[00215] Letter of authorization/agency, as used herein, may include but is not limited to communication used by a toll-free end subscriber, such as during the provisioning phase of a toll-free number engagement, to enable that end subscriber to switch providers for a given telephone, messaging service, and the like. In an example, an end subscriber may wish to change its long distance provider so that a local company need not be used. The long distance provider to whom the end subscriber wishes to do business would typically walk the end subscriber through an authorization process to enable the end subscriber to switch long distance carriers from the local company to the new company. This authorization may manifest in the carrier’s system as a letter of authorization/agency that documents the needed approvals from the end subscriber.

[00216] In an embodiment of the present disclosure, the TSS may enable a letter of authorization/agency process for a provider to authorizing texting and other services on a toll-free number or plurality of toll-free numbers that are used by an end subscriber. The letter of authorization/agency may be electronically stored and presented to the responsible organization or owner of record for a given number or service. The letter of authorization/agency may further define a time frame during which certain actions, such as the turning on of texting services for a toll-free number, are permitted. Such letters of authorization, as defined herein, may be further associated with stored profiles of an owner of record and/or end subscriber. A letter of authorization/agency may allow a toll-free number end-user, or toll-free number subscriber, to authorize service enablement for services not covered by their existing responsible organization. In this way, consumers can have multiple services enabled on a single telephone number, across multiple service providers. In an example, a letter of authorization/agency may authorize a responsible organization or other entity to take a plurality of actions so that additional communication with, for example, an end subscriber is unnecessary and actions may be taken more quickly and efficiently. This may enable service registrars, and others, to activate new services, such as toll-free texting services or bandwidth increases on a shorter timeline, which may have commercial benefits as speed activation of needed telecommunications services.

[00217] With reference to Fig. 11, in an embodiment of the present disclosure, the TSS may facilitate the enablement of a letter of authorization/agency process 1100 used to enable toll-free texting capability and capture basic data such as customer name, responsible organization, service registrar, toll free number, service enablement date, and letter of authorization/agency, status of services, or some other type of data associated with toll-free telephone numbers and services. The TSS may facilitate the letter of authorization/agency process by programmatically sending a notification to the responsible organization of record to memorialize the transaction. A timer may be set that will give the responsible organization a limited period of time to dispute the transaction. If no action is taken, the transaction may proceed and texting service enablement, or some other service type, may be fulfilled in the TSS Registry. Continuing the example, this letter of authorization/agency process may be provided for each toll-free number that is provisioned 1102 in the TSS registry, or only a subset of numbers depending on the wishes of the end users.

[00218] In order to streamline the letter of authorization/agency process, a “blanket” letter of authorization/agency may be used whereby the customer of record may authorize a specific service registrar to provision, update, and deactivate records in the TSS as needed 1104. In such cases, a notification may be sent to the responsible organization to memorialize each transaction. In order to further streamline the letter of authorization/agency process, responsible organization’s may choose to put a “blanket” authorization on specific service registrar’s which will allow the transaction to take place in real time 1108.

[00219] In embodiments, the TSS may allow electronic documentation to be stored and managed, providing a library of legal documentation that may be used by the system in real time to facilitate transactions more efficiently, and to provide more concrete evidence of formal authorization through a physical electronic document proving, for example, the end user’s identity and validity.

[00220] In embodiments, the TSS may operate in conjunction with current toll-free services, including a toll-free voice registry. In order to establish unambiguous authority for the use of a toll- free number, a controlling organization for a toll-free number may be the responsible organization of record in the toll-free voice registry. Number administration may be the exclusive function residing only in the authoritative toll-free voice registry.

[00221] In embodiments, the TSS may be flexible and extensible to support a plurality of toll-free services such as SMS or MMS messaging services, and content provisioning. The TSS may additionally provide toll-free numbers for services such as videos, mobile device applications, games, or any other software, products or services that may be important to an organization to anchor their identity and brand. To support this environment, in embodiments, the TSS may reside on a stand-alone platform using hardware, software, and support systems independent of those used today in the toll-free voice registry. The TSS may be able to connect to a toll-free voice registry to obtain number information, such as availability and reservation status, as well as control responsible organization information, such as the responsible organization contact information, but may remain otherwise separate in its operation.

[00222] A responsible organization may maintain a toll-free voice registry that provides number administration, route provisioning, toll-free database services to various service control points, or some other type of toll-free service. The TSS, as described herein, may incorporate the services from a toll-free voice registry to provide smart services enablement, route provisioning, and smart services registry to existing SMS/MMS routing databases as well as other smart services requiring toll-free numbers, such as mobile device applications or games.

[00223] With reference to Fig. 12, in another embodiment, a mobile device 1200 may utilize an unambiguous support identifier along with a toll-free data, message, and voice service. In this embodiment, the mobile device may be assigned a unique Toll-Free ID (TFID) 1202 at the time of manufacturing. That is, the TFID may be agnostic of type of device and may be hard flashed into the mobile device to identify a customer with a toll free provider that is providing the toll free communication. The TFID may be associated with the carrier identifier such as IMEI, MEID if GSM phone, CDMA, a service provider identifier such as a TSPID, as described herein, or to another identifier associated with a mobile device. In another embodiment, the TFID may be associated with other systems, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub- combination of such networks).

[00224] A standard support app that is natively installed, such as a “setting” 1208 app distributed as part of the device, or separately though an app store, facilitates a consumer’ s ability to talk, message, view, browse support related features of merchandise, devices or other issues that the consumer may have. The standard support app may further interact with a user profile and security administration that grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The system can implement a role-based access control mechanism. [00225] When consumers buy a device, the device manufacturers and retailers may "auto register" the device to the support application at the Point of Sale (POS). The TFID may be embedded in the hardware of the device and cannot be changed to provide a definitive way to identify a device when using toll-free services.

[00226] With reference to Fig. 13, in another embodiment, the TFID may permit a customer who is purchasing an appliance, a device, or other merchandise to be presented with an opportunity to associate one or more mobile devices to the merchandise purchased 1300. For example, this can be performed at the POS or after the sale as a registration and/or warranty process 1302. The process of registration is thereby automated to simplify these somewhat otherwise bothersome processes for the customer.

[00227] In one example, a TFID Mobile App is operable to permit the mobile device to read QR codes, Barcodes, RFIDs, serial numbers, or other merchandise identifiers and then communicate with the manufacturer via toll free service provided by the manufacturer 1304. For example, a user may need only point a camera of the mobile device toward the merchandise to capture the merchandise identify and thereby complete a registration, warranty, support or other process.

[00228] On the backend, a TFID Mobile App registry 1308 may be updated with the added mobile device TFID to merchandise association. Via a separate mechanism, merchandise manufactures 1310 can then update the registry with the contact information associated with the TFID for registration and user association. The TFID Mobile App registry may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00229] Once the merchandise is associated with the particular mobile device - the TFID Mobile App may present or otherwise store the various information about the merchandise, e.g., product documentation, upgrades, manufacture contact information, etc. This permits the user to readily communicate with the manufacturer via the toll free service provided by the manufacturer and accessed via the TFID. For example, once the merchandise is associated with the mobile device, a support call registry may be made readily available from the manufacturer via a toll free service. Support such as repair and troubleshooting for the merchandise may then be more readily provided as the initial validation of the merchandise to the particular user, e.g., warranty registration and confirmation has already been automatically provided by the registry. That is, the registry facilitates more direct access to support from the manufacturer via a toll free communication provided by the manufacturer as supported by the support application on the device.

[00230] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00231] A mobile device, comprising: a unique toll-free ID (TFID) present in the mobile device, the TFID operable to facilitate toll-free communication between the mobile device and a manufacturer. [00232] A method of communication via a toll-free service, comprising: associating at least one mobile device to merchandise purchased from a manufacturer via a unique toll-free ID (TFID) present in the mobile device, the TFID operable to facilitate toll-free communication between the mobile device and the manufacturer. [00233] A toll-free voice registry may share reserved, assigned, and working numbers with the TSS. The TSS may then establish available numbers for service enablement. As described herein, a service registrar may identify toll-free numbers to be provisioned to an organization and may complete a letter of authorization/agency and provide “owner of record” documentation. The TSS may then request approval for service enablement from a responsible organization. The responsible organization may review the service enablement request. If approved, the TSS may change the service status of the toll-free number from “available” to “assigned.” The service registrar may then assign a unique identifier to number such as a Service Provider Identifier (SPID) or eSPID. The TSS may then provision the service and change the number status from “assigned” to “active.” The routing database associated with the TFMP may then provision the toll-free number with the unique identifier.

[00234] With reference to Fig. 14, a toll-free voice registry may share reserved, assigned, and working numbers with the Toll-Free Texting and Smart Services Registry (TSS). The TSS may then establish available numbers for service enablement. As described herein, a service registrar may identify toll-free numbers to be provisioned to an organization and may complete a letter of authorization/agency and provide “owner of record” documentation. The TSS may then request approval for service enablement from a responsible organization. The responsible organization may review the service enablement request. If approved, the TSS may change the service status of the toll- free number from “available” to “assigned.” The service registrar may then assign a unique identifier to number such as a Service Provider Identifier (SPID) or eSPID. The TSS may then provision the service and change the number status from “assigned” to “active.” The routing database associated with the TFMP may then provision the toll-free number with the unique identifier. [00235] Additionally, the TFMP may also provide a mobile or other application that small business and single toll-free number users can use to report abuse in combination with the TSS. The TFMP may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs. The decision tree may be used in various manners to facilitate operation of the service as otherwise described to facilitate call efficiency. The TFMP may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, the TFMP may include hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00236] Telecommunication service providers are required by industry guidelines to have a unique company code assigned to them. This unique company code identifies carriers as they interconnect with each other and allows for rating, guiding, billing and routing functionality. Historically, when service providers provided voice only services, each service provider was identified by a company code termed an Operating Company Number (OCN). With the evolution of the communications industry, service providers started introducing additional voice services, for example number portability. As these services were introduced, the need for uniquely identifying the carriers became of paramount importance. Registries and organizations were set up to facilitate the integration and interactions required to fulfill these services. Such developments prompted service organizations’ need for additional context-based metadata to support these interactions (for example number portability). One result was the adding of additional identifiers to each service provider that required integration. These are sometimes referred to as the SPID or Alternate Service Provider Identifier (Alt-SPID).

[00237] With the introduction of over-the-top (OTT) providers, for example Skype, and Internet Protocol-based vendors (IP Vendors) selling traditional communication services over a full Internet Protocol (IP) network, the activities between software and the traditional telecommunications industry become more interactive. IP allowed for a new breed of vendors to integrate with traditional communication service provider networks for delivery and exchange of consumer data. This created a new set of challenges for the unique identification of service providers since the IP Vendors were not traditional carriers and did not meet industry guidelines for OCNs. Additional, sometimes proprietary metadata were created to support these new service providers, for example an eSPID, as described herein. The preponderance of different identifiers from eclectic industry organizations lead to lack of a consistent, unique way to identify and interact with service providers, with no centralized industry provider, organization or registry having a complete view of service provider community. [00238] In an example embodiment of a service provider routing text messages though the network, as the text messages are processed the TSS may obtain metadata associated with the messages that includes coding data. By reading these codes, the TSS may confirm that a given message is derived from a service provider such as Skype for delivery to an AT&T subscriber. Such metadata may be obtained, for example, in a header file. Fields in the header file may be associated with a SPID. This may allow the TSS to determine that the text message is coming from Skype en route to ATT. If it were the case that many texts were originating from Skype at a particular time or day, the TSS may utilize this data to assist third parties in providing targeted advertising content. The TSS may also utilize this data to identify the unnecessary usage of intermediaries in processing communications such as text messages and assist users in avoiding the excess charges for intermediaries by routing messages without using intermediaries. The TSS may utilize a context-based unique identifier to distinguish specific services associated with the TSS Registry. The TSPID 1402 may be enabled in TSS and applies to such multimedia services such as but not limited to SMS, MMS, video conferencing, and streaming data. Resp Org IDs may also be associated with any toll free number enabled in TSS. The TSPID may further facilitate the value chain of a multimedia service for toll- free numbers in order for that service to be delivered.

[00239] The Toll-Free Service Provider ID “TSPID,” provides an aggregate identifier for Service Registrars, who provide services such as, but not limited to, SMS, MMS, video conferencing, and streaming content that may be registered and distributed by the TSS Registry. That is, the TSPID provides a single unified identifier that may include other identifiers 1404 over a broad distribution of data, to include, but not be limited to, traditional voice services. The TSPID may also be utilized as an authoritative identifier of the service provider of record for toll-free numbers, and/or ultimately local 10 digit numbers. The TSPID may be enabled by a user profile and security administration that grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The system can implement a role-based access control mechanism.

[00240] Telecommunication service providers are required by industry guidelines to have a unique company code assigned to them. This unique company code identifies carriers as they interconnect with each other and allows for rating, guiding, billing and routing functionality. Historically, when service providers provided voice only services, each service provider was identified by a company code called as Operating Company Number or (OCN). With the evolution of the communications industry, service providers started introducing additional voice services, for example number portability. As these services were introduced, the need for uniquely identifying the carriers became of paramount importance. Registries and organizations were set up to facilitate the integration and interactions required to fulfill these services. Such developments prompted service organizations’ need for additional context-based metadata to support these interactions (for example number portability). One result was the adding of additional identifiers to each service provider that required integration. These are sometimes referred to as the SPID or Alternate Service Provider Identifier (Alt-SPID).

[00241] The SPID is the authoritative identifier for telephone number ownership in the Number Portability Administration Center, which includes “ported” numbers associated with Local Number Portability as well as “pooled” numbers, which are associated with assigned pool blocks as administered by the Pooling Administration. Over time, many companies may map various identifiers such as the SPIDs to a broader table for use with the TSPID to still further aggregate such data. Further, traditional voice services may be mapped as well.

[00242] With the introduction of value added mobile services (for example SMS), exchanges and hubs set up by Inter Carrier Vendors (ICV) provide communication between multiple mobile network operators. Route tables are stored in industry proprietary databases that provided a call path service to determine, in real time, the destination service provider for an incoming mobile service. These ICVs further add additional metadata to identify carriers and facilitate integration. This process may have added complexity insofar as countries have their own local and regional authorities and naming conventions.

[00243] With the introduction of over-the-top (OTT) providers, for example Skype, and Internet Protocol-based vendors (IP Vendors) selling traditional communication services over a full Internet Protocol (IP) network, the activities between software and the traditional telecommunications industry become more interactive. IP allowed for a new breed of vendors to integrate with traditional communication service provider networks for delivery and exchange of consumer data. This created a new set of challenges for the unique identification of service providers since the IP Vendors were not traditional carriers and did not meet industry guidelines for OCNs. ICVs created additional, sometimes proprietary metadata to support these new service providers, for example an eSPID, as described herein. The preponderance of different identifiers from eclectic industry organizations lead to lack of a consistent, unique way to identify and interact with service providers, with no centralized industry provider, organization or registry having a complete view of service provider community.

[00244] In embodiments of the present disclosure, the TSS may provide an inclusive view of industry identifiers, enabling a single system of record for identifying service providers, whether traditional telecommunications provider, OTT provider, or some other type of service provider. During the on-boarding process (e.g., toll-free number reservation and provisioning), service registrars may be required to provide their unique identifiers (UIds) with the various organizations they interact.

[00245] In embodiments, the TSS may establish a baseline of UIds by public domain information gathering. Data gathered through the public domain may be further validated through crowd sourcing, where a global, potentially mechanical human process can be used to identify, validate and confirm UIds to create a baseline for the registry. In another embodiment, latent sematic indexing may be used to associate data and metadata associated with communications to the actual owner, provider, or responsible party that is associated with a communication, such as a text message. This crowd-sourced translation table associated with the TSS may enable mapping of service providers to unique identifiers. Such a mapping would enable the registry that may be used by third parties to locate the plurality of identifiers that may be associated with a service provider or plurality of service providers.

[00246] In order to facilitate proper content delivery, service providers may be required by the TSS to periodically update their UIds. A validation, verification and certification process may be used to ensure integrity and validity of data entering the TSS. This may provide the industry with a single resource that may be used to identify and validate the identity of service providers. In an example usage scenario, a communications company that intends to optimize its network and manage traffic, may wish to identify where its end traffic (original source) is located by looking at packet headers and identifying service providers. In another example, a consumer reports-based rating service may use the TSS to provide consumers with message or delivery metrics. Bulk-advertising (pam) management companies may use the TSS look at detailed metadata and associate a name to a code. ICVs may use the TSS to streamline establishment and setup of their recipients without requiring expensive and costly set up. Ad agencies may use data derived from the TSS to customize ads to end users by understanding the source and destination (as opposed to area codes), and personalize content based on the service provider(s), for example if the content originated on an IP network. [00247] In an example embodiment of a service provider routing text messages though the network, as the text messages are processed the TSS may obtain metadata associated with the messages that includes coding data. By reading these codes, the TSS may confirm that a given message is derived from a service provider such as Skype for delivery to an AT&T subscriber. Such metadata may be obtained, for example, in a header file. Fields in the header file may be associated with a SPID. This may allow the TSS to determine that the text message is coming from Skype en route to AT&T. If it were the case that many texts were originating from Skype at a particular time or day, the TSS may utilize this data to assist third parties in providing targeted advertising content. The TSS may also utilize this data to identify the unnecessary usage of intermediaries in processing communications such as text messages and assist users in avoiding the excess charges for intermediaries by routing messages without using intermediaries.

[00248] With reference to Fig. 15, in embodiments, the TSS (Texting and Smart Services) Registry 1500 may establish a baseline of UIds by public domain information gathering for messages 1508 sent from a client device 1504. Data gathered through the public domain may be validated through crowd sourcing, where a global, potentially mechanical human process can be used to identify, validate and confirm UIds to create a baseline for the registry. Every Service Provider has a set of unique UIds by which its customers are reached by various methods such as, but not limited to, voice, short messaging service (SMS), multimedia messaging service (MMS), video conferencing, and streaming content. When any of these Service Providers signs up to be a TSS user 1502, it has a unique UId, called a TSPID, which is assigned. This TSPID provides the baseline for which many other UIds can be mapped. Many Data Providers, Messaging Hubs, Aggregators, and others who are in the business of routing and providing services such as voice, SMS, MMS, video conferencing, streaming content, and other multimedia services, to sign on to consume TSS Data. Each of these entities that consume data will have a unique identifier to which the TSPID will be mapped. Data Providers that consume TSS data will be required to provide to TSS a new toll-free specific UId for each established TSPID. The end result is a mapping that extends to any data provider that is consuming TSS data. As distribution widens, a fairly comprehensive routing table 1514 for each Service Provider is created.

[00249] Furthermore, each TFN that is enabled in the TSS Registry, has the Resp Org ID and Resp Org Entity associated with it, and thus is also mapped to the TSPID. The result is the most comprehensive routing table specific to toll-free numbers that will map toll-free numbers to their voice provider, messaging provider, as well as the routing information across a plurality of data providers. Once this comprehensive Toll-Free routing table 1514 is established, it can be further extended to layer in other identifiers, such as, but not limited to local ten digit numbers (also known as “long codes”), SPID, LRN, OCN, and LATA.

[00250] In another embodiment, latent semantic indexing may be used to associate data and metadata associated with communications to the actual owner, provider, or responsible party that is associated with a communication, such as a text message. This crowd-sourced translation table associated with the TSS may enable mapping of service providers to unique identifiers. Such a mapping would enable a registry that may be used by third parties to locate the plurality of identifiers that may be associated with a service provider or plurality of service providers. In embodiments, toll-free number abuse information, as described herein, from a plurality of sources including, but not limited to, a telephone service provider, toll-free number operators and Resp Orgs may also be used for the purposes of creating translation tables, including but not limited to crowd-sourced translation tables. The TSS routing table, once sufficiently established, may be used for services such as value added predictive analytics, as described herein, that service providers can use to gain valuable insights about their customers. Service Providers and other consumers of the data in the routing table would access the information using either an application programming interface (API) for automated integration into their own analytics engines, or a web-based GUI for simpler one-time lookups. Below are some examples of probable use-cases for the routing table.

[00251] In order to facilitate proper content delivery, service providers may be required by the TSS to periodically update their UIds. A validation, verification and certification process may be used to ensure integrity and validity of data entering the TSS. This may provide the industry with a single resource that may be used to identify and validate the identity of service providers. In an example usage scenario, a communications company that intends to optimize its network and manage traffic, may wish to identify where its end traffic (original source) is located by looking at packet headers and identifying service providers.

[00252] In another embodiment, a consumer reports-based rating service may use the TSS to provide consumers with message or delivery metrics. Bulk-advertising (spam) management companies may use the TSS to look at detailed metadata and associate a name to a code to streamline establishment and setup of their recipients without requiring expensive and costly set up. Ad agencies may use data derived from the TSS to customize ads to end users by understanding the source and destination (as opposed to area codes), and personalize content based on the service provider(s), for example if the content originated on an IP network.

[00253] In another embodiment of a service provider routing text messages though the network, as the text messages 1508 are processed, the TSS may obtain metadata associated with the messages that includes coding data. By reading these codes, the TSS may confirm that a given message is derived from a service provider such as Skype for delivery to an AT&T subscriber. Such metadata may be obtained, for example, in a header file. Fields in the header file may be associated with a SPID. This may allow the TSS to determine that the text message is coming from Skype en route to AT&T. If it were the case that many texts were originating from Skype at a particular time or day, the TSS may utilize this data to assist third parties in providing targeted advertising content. The TSS may also utilize this data to identify the unnecessary usage of intermediaries in processing communications such as text messages and assist users in avoiding the excess charges for intermediaries by routing messages without using intermediaries.

[00254] In embodiments, the TFMP may provide a Toll-Free Texting and Smart Services Registry (TSS) to support toll-free telephone numbers and related services, such as SMS, MMS and streaming media. The TSS may comprise several components such as, but not limited to, number administration, call control and routing, as well as number status assessment. The number administration function may provide number assignment for toll-free subscribers as well as provide services to manage the toll-free numbering plan. This component may provide for toll-free number portability as well as managing the mapping of toll-free numbers to geographic numbers. The number administration function may also open new number plan administration codes. The number administration function may forecast the exhaustion of codes and demand for codes for use by organizations such as the FCC. The call control and routing function may be responsible for providing intelligent routing for calls made to toll-free numbers.

[00255] Toll-free subscribers may have the ability to configure call routing to include multiple carriers, time of day rules, and rules based on the caller’s proximity, among others. These rules may be downloaded to real-time network routing databases or Service Control Points (SCPs). The number status assessment function may determine the availability of certain numbers. Numbers may be reserved and assigned according to activation date and then are deployed. The number status function may assess whether numbers are spare, reserved, assigned, or currently deployed. Providers of various smart services, such as voice, media, or texting services, may be able to access the TSS that can be text enabled from a list of reserved, assigned, and working numbers. After numbers are identified, an automated online letter of agency may be executed. The letter of agency may independently demonstrate authorization to a responsible organization that maintains the registration for individual toll-free numbers in a distributed database. The distributed database may be associated with a distributed computing network, as described herein. Upon execution of the letter of agency, the information may then be provisioned to industry routing databases for delivering various services, such as SMS (text) messaging, MMS messaging, and content streaming, including but not limited to video content.

[00256] Letter of agency, as used herein, may include but is not limited to communication used by a toll-free end subscriber, such as during the provisioning phase of a toll-free number engagement, to enable that end subscriber to switch providers for a given telephone, messaging service, and the like. In an example, an end subscriber may wish to change its long distance provider so that a local company need not be used. The long distance provider to whom the end subscriber wishes to do business would typically walk the end subscriber through an authorization process to enable the end subscriber to switch long distance carriers from the local company to the new company. This authorization may manifest in the carrier’s system as a letter of agency that documents the needed approvals from the end subscriber. In an embodiment, the TSS may enable a letter of agency process for a provider to authorize texting and other services on a toll-free number or plurality of toll-free numbers that are used by an end subscriber. The letter of agency may be electronically stored and presented to the responsible organization or owner of record for a given number or service. The letter of agency may further define a time frame during which certain actions, such as the turning on of texting services for a toll-free number, are permitted. Such letters of agency, as defined herein, may be further associated with stored profiles of an owner of record and/or end subscriber. A letter of agency may allow a toll-free number end-user, or toll-free number subscriber, to authorize service enablement for services not covered by their existing responsible organization. In this way, consumers can have multiple services enabled on a single telephone number, across multiple service providers. In an example, a letter of agency may authorize a responsible organization or other entity to take a plurality of actions so that additional communication with, for example, an end subscriber is unnecessary and actions may be taken more quickly and efficiently. This may enable service registrars, and others, to activate new services, such as toll-free texting services or bandwidth increases on a shorter timeline, which may have commercial benefits as speed activation of needed telecommunications services.

[00257] In an embodiment, the TSS may facilitate the enablement of a letter of agency process used to enable toll-free texting capability and capture basic data such as customer name, responsible organization, service registrar, toll free number, service enablement date, and letter of authorization/agency, status of services, or some other type of data associated with toll-free telephone numbers and services. The TSS may facilitate the letter of agency process by programmatically sending a notification to the responsible organization of record to memorialize the transaction. A timer may be set that will give the responsible organization a limited period of time to dispute the transaction. If no action is taken, the transaction may proceed and texting service enablement, or some other service type, may be fulfilled in the TSS Registry. Continuing the example, this letter of agency process may be provided for each toll-free number that is provisioned in the TSS Registry, or only a subset of numbers depending on the wishes of the end users. In order to streamline the letter of agency process, a “blanket” letter of agency may be used whereby the customer of record may authorize a specific service registrar to provision, update, and deactivate records in the TSS as needed. In such cases, a notification may be sent to the responsible organization to memorialize each transaction. In order to further streamline the letter of agency process, responsible organization’s may choose to put a “blanket” authorization on specific service registrar’s which will allow the transaction to take place in real time.

[00258] In embodiments, the TSS Registry, as described herein may be an authoritative database of all, or some subset of, text-enabled toll-free numbers in North America. It may also contain the top- level routing information, in the form of a toll-free service provider identifier (TSPID), used by the texting ecosystem to send messages to the proper toll-free subscriber. Since a letter of agency is required for each toll-free number that is enabled in the TSS, the TSPID may become a centralized and authoritative source identifier and may be used in the provisioning of additional services associated with toll-free numbers such as, but not limited to MMS, video conferencing, and streaming data. Furthermore, since part of the enablement process includes Responsible Organization authorization and/or notification, coupled with the direct connection to a voice telecommunications platform associated with the TFMP, the TSPID may also serve to validate the authority of a call routing table.

[00259] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00260] A method of identifying and storing an identifier associated with a toll-free-communication entity, comprising: locating an identifier within the header portion of an SMS text message routed over a toll-free telecommunications line, the identifier located based at least in part through latent semantic indexing; comparing the located identifier with metadata stored on a server, the metadata associated with a plurality of entities; selecting an entity from among the plurality of entities based at least in part on the comparison; and storing a code associated with the entity within a translation table associated with a toll-free telecommunications management platform.

[00261] A method of creating and storing an identifier associated with a toll-free-communication entity, comprising: locating data within the header portion of an SMS text message routed over a toll-free telecommunications line, the data located based at least in part through latent semantic indexing; creating an entity identifier based at least on the data; storing a code associated with the entity identifier and an entity within a translation table associated with a toll-free telecommunications management platform; and associating the entity and entity identifier with a call routing table.

[00262] A method of identifying and storing an identifier associated with a toll-free-communication entity, comprising: identifying a toll-free call route trend among a plurality of toll-free calls taking place within a toll-free telecommunications network; wherein the call route trend is identified at least in part by call routings among toll-free numbers sharing an attribute; creating a call route template based at least in part on the trend; identifying an entity using at least one toll-free number with the shared attribute; prepopulating a call route tree for the entity based on the call route template.

[00263] With reference to Figs. 16-20, a system according to various embodiments, and which may be referred to in some instances herein as an intelligent platform, platform, or an architecture, is operable to support the ever evolving toll-free industry through the use of modem technologies which may include enhanced functionality and deliver improved cost efficiencies and quality of service.

[00264] The architecture depicted in Figs. 16-20 may include aspects such as: a. Number searches return suggestions b. Scheduled number search c. One-click number search to activate d. Number search based on history e. Smart number search f. Bulk search g. Spare number availability notification h. Enhanced number configurability i. Enhanced route management j. Self-service administration k. Additional user roles l. Customer record builder m. Customer record template transfer n. Dashboard o. Customer access p. Open API q. Bulk Processing r. Improved Search s. Workflow t. Customer records/Template u. System Performance v. Reporting and Analytics

[00265] The architecture depicted in Figs. 16-20 may include the components in the following table:

[00266] With reference to Fig. 21, in embodiments, the TFMP may include a subsystem that enables distributed call collectors to collect data from various sources including service control points (SCPs), toll-free service providers, interexchange carriers, and others. Data may be real-time grouped, aggregated and reduced based on toll-free numbers and relevant parameters, including but not limited to origination location, originating area of service, originating NPA, ANI, or some other criterion.

Call counts may be calculated for high priority numbers. Data may be enriched with call duration information when it is available. This process may assist in reducing the overall data set size and speeding processing. A local NoSQL data store may be used to aggregate local trends and pre- process raw data.

[00267] In embodiments, once pre-processing completes, data may be shared in real time, or near real time, to a centralized analytics data store 2102 that is associated with the TFMP for more real time mapping and reduction. The analytics NoSQL datamart may combine data feeds from various service providers from the network and further reduce information to call counts, call completion rates and call duration for high priority numbers. This subsystem of the TFMP may gather historical macroeconomic data from market sources 2104 like Bloomberg TM and Reuters TM and create a reference data store that groups and summarizes economic trends month over month. This subsystem may serve as a reference data source for the analysis, inference and indexing system.

[00268] In embodiments, this subsystem may collect historical call completion and call count data from high priority numbers and apply mapping and data reduction techniques to create historical baselines for calls. Calls may be sourced from market data sources, data purchases, data bartering from call sources, or through some other type of data source. Call sampling and aggregation may be iteratively performed until a statistically significant dataset is created (e.g., over a tuning period). Multi-factor models may be created for correlating toll-free call activity with selected macroeconomic trends, backed by high priority numbers tied to businesses. For example, calls to toll-free numbers for employment commissions in the 50 states may be tied to a forward-looking indicator for unemployment and consumer sentiment.

[00269] In another example, historical changes in macroeconomic data may be plotted with changes in call metrics like call volume, call duration, or some other data related to toll-free data. This may provide a correlation between telemetry and economic indicators. Financial modeling techniques may be applied, and additional factors may be analyzed, including but not limited to consumer sentiment, including sentiment that is sourced by social media comments and online behaviors related to relevant topics (e.g., questions regarding unemployment benefits or questions regarding food stamps). Interrelationships between indicators may also be analyzed. Credit card spending data may be an additional factor analyzed. These underlying factors may drive stochastic probabilities to determine a prediction model that may be utilized by the TFMP. The TFMP system may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs to facilitate the stochastic probabilities to determine a prediction model. The decision tree may be used in various manners as otherwise described to facilitate call efficiency. The output of the model may be a prediction trend 2108 that can forecast the probability of a relative positivity or negativity of the upcoming indicator. Data from the analytics data store and the historical trends data store may be analyzed through a multi-factor model for deriving a macro economic trend indicator and a relative level of confidence with the trend.

[00270] In embodiments, a client device 2110 such as an online and/or a mobile application may allow users to filter, search and sort trend data, increase or reduce granularity, include or exclude factors and zone in or drill down based on dimensions. For example, a user may choose to include or exclude a state from the model to derive a trend prediction and a prediction confidence indicator. Alternatively or in addition, a customizable user interface, or “dashboard,” may be utilized to provide access for third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll-free telecommunication network. As elsewhere described, origination data may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trends and prices on an interactive map via the TFMP. Further, the user profile and security administration grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The system can implement a role-based access control mechanism. [00271] In embodiments, this analytic subsystem of the TFMP may provide a flexible mapping interface for a user 2112 to enter their own data as part of an analysis. Once configured, additional data sources may be added in real time, or near real time, through an API or a web interface to further refine the model based on customer specific data sets to make intelligent business decisions. The system may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, such systems may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00272] The system may also provide a marketplace for data trading where subscribers can choose and buy data sources that are of interest to them to include in their analysis to further refine their predictive model. The system may facilitate the sale of data sources and assist in ensuring that the data uploaded and made available on the data market is scrubbed of personally identifiable or other sensitive data. For facilitating the data sale, the system may charge a percentage of the sale proceeds in addition to an annual or monthly subscription fees. For consumers interested in a monthly subscription, overall sentiment data may be made available through a number trend report. Alerts may be presented to users, such as to a client device. The user may also access the reporting capabilities of the TFMP through a client device, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’ s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration.

[00273] In embodiments, the TFMP may provide macroeconomic data trend over a network to a remote client device, by providing a user interface dashboard to a user for installation on the remote client device; receiving third party social media data; modeling at least one of call duration or call count data with the third party social media data to derive a macroeconomic trend; receiving a request from the remote client device to present the macroeconomic data trend; generating an alert from the macroeconomic data trend that contains a stock name, stock price and a universal resource locator (URL), which specifies the location of the data source; and transmitting the alert over a communication channel to the remote client device associated with the user based upon a destination address and transmission schedule that is associated with the remote client device, wherein the alert activates the user interface dashboard to cause the alert to display on the remote client device and to enable connection with the user interface dashboard when the remote client device is activated. [00274] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00275] A method comprising: receiving data relating to toll-free number call activity from a toll-free telecommunications system, wherein the data includes at least one of call duration or call count data; receiving third party data relating to macroeconomic activity; modeling at least one of call duration or call count data with the third party data to derive a macroeconomic trend; receiving a request from a client device to present the macroeconomic trend; and presenting a representation of the macroeconomic trend to a user interface on the client device. [00276] A method comprising: receiving data relating to toll-free number call activity from a toll-free telecommunications system, wherein the data includes at least one of call duration or call count data; receiving metadata about the toll-free numbers that are the subject of the call activity, wherein the metadata includes data pertaining to at least one of business type or location; modeling at least one of call duration or call count data with the metadata to derive a macroeconomic trend; receiving a request from a client device to present the macroeconomic trend; and presenting a representation of the macroeconomic trend to a user interface on the client device.

[00277] A method of distributing a macroeconomic data trend over a network to a remote client device, the method comprising: providing a user interface dashboard to a user for installation on the remote client device; receiving third party social media data; modeling at least one of call duration or call count data with the third party social media data to derive a macroeconomic trend; receiving a request from the remote client device to present the macroeconomic data trend; generating an alert from the macroeconomic data trend that contains a stock name, stock price and a universal resource locator (URL), which specifies the location of the data source; and transmitting the alert over a communication channel to the remote client device associated with the user based upon a destination address and transmission schedule that is associated with the remote client device, wherein the alert activates the user interface dashboard to cause the alert to display on the remote client device and to enable connection with the user interface dashboard when the remote client device is activated.

[00278] With reference to Fig. 22, in another embodiment, a toll-free management platform (TFMP) may refine a recommendation for a toll-free number search via a recommendation engine that utilizes a searcher's profile to improve the search. The toll-free management platform (TFMP) may utilize other assets of a toll-free system generally, such as carrier data, location information regarding call origination, payment data and so forth. The TFMP system may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs. The decision tree may be used in various manners as otherwise described to facilitate call efficiency. In one example, the toll-free number search may be based upon a customer’ s historical data such as prior search criteria and existing toll-free numbers, and thereby provide the customer suggestions or notification of toll-free numbers that are available for use. This toll-free number search may be based upon previous searches by either that customer and alternatively or in addition, upon other customer searches.

[00279] The toll-free number predictive search is operable to utilize multiple sources of data to extrapolate possible toll-free numbers and those included in a Resp Org and/or user’s search history to include, but not be limited to, a current Resp Org inventory, an overall search history, lists of upcoming available numbers, or some other type of data. Predictive analytics is an area of data mining that deals with extracting information from data and using it to predict trends and behavior patterns. The toll-free number predictive search is operable for the user profile and security administration grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The system can implement a role-based access control mechanism.

[00280] Predictive analytics utilized for the predictive search may encompass a variety of statistical techniques from predictive modeling, machine learning, and data mining that analyze current and historical facts to make predictions about future, or otherwise unknown, events. Predictive analytics can be applied to any type of unknown whether it be in the past, present or future. Predictive analytic services may also be provided that allow a user, through the customizable user interface, or dashboard, to access third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll-free telecommunication network. As elsewhere described, origination data may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trends and prices on an interactive map via the TFMP.

[00281] The toll-free number predictive search may check on the availability of a suggested toll-free number before making a particular suggestion and may otherwise automatically reserve that toll-free number, based upon the customer selecting an “automatically reserve” option. That is, the toll-free number may be automatically reserved if it meets particular search criteria to essentially automate the reservation thereof. Further, the automatic reservation may be a fee-based function in which particular bidders are able to prioritize the choice of toll free numbers via particular fee based arrangements.

[00282] In embodiments, initially, a user may be provided the option to opt into the toll-free number predictive search feature as well as the option to automatically reserve toll-free numbers determined to be available based upon the predictive search. That is, rather than wait for a request, a customer- desired number is predicted, offered, and potentially reserved. The user may also access the reporting capabilities of the TFMP through a client device, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration. It should be appreciated that other options may be alternatively or additionally provided.

[00283] In one disclosed non- limiting embodiment of a method 2200 for operation of a toll-free number predictive search is initiated via accessing a Resp Org‘s search history (step 2202; Figs. 23, 24, 25, and 26). Numerous criteria may be used when searching for toll-free numbers including the use of wildcards, words translated to numbers, and the like. The search may be performed at both a Resp Org level and broken down by a user as well. This history may be one of the factors used in providing suggestions. Typically, an inventory of toll-free numbers associated with a particular Resp Org as well as an inventory of available toll-free numbers is accessible. Next, the toll-free number predictive search feature may utilize an algorithm that would, for example using the data noted above, produce a list of customer desired toll-free numbers for the customer (step 2204). For example, the algorithm may use any and/or all of the following information to make a search recommendation:

• Previous search number history (what numbers has a user / Resp Org searched for recently and how many times has the search been performed).

• Current inventory of toll-free numbers managed by this particular Resp Org. For example, if 888-234-CARS is managed perhaps 800-234-CARS may be predicted as being desired.

• Numbers that are to be spared (made available). Examine numbers that are going to become available and determine if they meet any patterns in which a user has expressed interest.

• Search histories from this or other Resp Orgs as it relates to a number this Resp Org has searched for. [00284] The predictive search results may facilitate a standing willingness for a customer to pay for a particular toll-free number and thus automatically reserve the predicted toll-free number (step 2206). For example, once a toll-free number is identified, various offers may be made available via an auction, payment to be first in line, subscription offerings, and others. Finally, a plurality of options may be provided when the customer receives the predictive search results (step 2208), such as, but not limited to:

• At every logon;

• Emailed at a specific time of the day. In one example, coordinated around the TFN Spare activity.

[00285] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00286] A method of searching for a toll-free number, comprising: identifying a previous search number history for a user; and offering a toll free number associated with the previous search number history to the user. [00287] A method of searching for a toll-free number, comprising: predicting a customer-desired toll free number for a user; reserving a toll free number in response to the predicting; and offering the reserved toll free number to the user.

[00288] A method of searching for a toll-free number, comprising: identifying a previous search number history for a user; predicting a customer-desired toll free number for a user from the previous search number history; and offering the predicted toll free number to the user.

[00289] One disclosed embodiment of the system can support future and the ever-evolving toll-free industry through the use of modern technologies, enhanced functionality, and improved cost efficiencies and quality of service. The system can provide additional and enhanced system capabilities that meet or exceed the performance of the existing legacy system on all parameters such as response time, capacity, scalability and cost. The system can improve core services, lower operational expenses, and enable innovations for customers.

[00290] More specifically, embodiments of the system can facilitate: a. Modernization of core technologies b. Relevance with transition to IP. c. Use cloud, mobile, and leading-edge technologies to enable new business opportunities and facilitate customer innovation. d. Meet/Exceed current service levels. e. Optimize processes and data. f. Make it easier for customers to do business thereby building stronger relationships. g. Increase customer satisfaction and perceived value h. Enable business process automation to optimize cycle time i. Make data more valuable and accessible for both internal and external use. j. Optimize functionality and system access methods to the minimum required. Increase ability to change. k. Be more flexible to quickly add/enhance products and services. l. More easily adapt to and support business/industry change over time. m. Simplify in everything to optimize and reduce costs. n. Broaden pool of available talent by leveraging current technologies and leading concepts.

[00291] Embodiments of the disclosed system may include the integration of one or more of the following capabilities: a. Number searches return suggestions. b. Scheduled number search. c. One-click number search to activation. d. Number search based on history. e. Smart number search. f. Bulk search. g. Spare number availability notification. h. Enhanced number configurability. i. Enhanced route management. j. Self-service administration. k. Additional user roles. l. Customer record builder. m. Customer record template transfer. n. Dashboard. o. Customer access. [00292] Additionally, the capabilities listed herein may include the following features in its integration such as Minimal Feature Sets (“MFS”), New Feature Sets (“NFS”) and Non-Functional Requirements. Additionally, the capabilities listed in the MFS, NFS, and Non-Functional Requirements may include the following: a. Ease of Use. b. Open API. c. Bulk Processing. d. Improved Search. e. Workflow. f. Customer records/Template. g. System Performance. h. Reporting and Analytics.

[00293] With reference to Fig. 27, a high performance Agile and DevOps application delivery organization 2700 permits each vendor to examine the organization and sample toolset to see if it fits within their idea of a delivery organization. The system can be built on a Web-Scale infrastructure capable of delivering continuous availability and continuous delivery. The Web-Scale infrastructure can enable developers and administrators to easily provision and deploy environments on-demand. The infrastructure and application services can scale up and down based on external factors (i.e., current load, performance requirements). Integrated teams, process and tools that provide increased agility, transparency and ease of governance, and effective allocation of resources [00294] A subscriber to basic telephone service is assigned a telephone number that identifies the service and is billed for calls originated from the telephone line associated with the service. In contrast, with toll-free service the subscriber is assigned a toll-free telephone number and is billed for all calls terminated to that number. There is no charge to the originator of the toll-free call.

[00295] Toll-free number portability made it possible for any company to provide service for any available toll-free number. FCC Tariff No. 1 x, 800 Service Management system functions specified the functionality of a Service Management system that would be operated by the Bell Operating Companies (BOCs). One embodiment of a tariff is Tariff F.C.C. No. 1 x, 800 Service Management System Functions, Issued January 31, 2013, Effective February 15, 2013. A disclosed embodiment, originally developed and maintained by Bellcore, facilitates a company that wishes to provide toll- free service (referred to as a Responsible organization/Resp Org/toll-free service provider) to obtain control of toll-free numbers and provision of the information in the network needed to route calls to a designated terminating number. (This information is sometimes referred to as a Customer Record.) This tariff outlines the requirements for becoming a toll-free service provider, the capabilities required of the disclosed embodiment to allow toll-free service providers to search for and reserve toll-free numbers and provision Customer Record information, and how toll-free service providers may be to be billed for use of the disclosed embodiment and control of toll-free numbers.

[00296] With geographic portability made possible through the use of centralized routing databases, it became possible for the same toll-free number to be dialed from anywhere in the country and for the toll-free call to be delivered to different destinations based on routing criteria specified in the Customer Record. Toll-free service quickly grew in popularity, and the supply of available 800 numbers neared exhaustion. The toll-free code 888 was opened in 1996, followed by 877 in 1998,

866 in 2000, and 855 in 2010. Plans may be underway for opening of the 844 code in the near future and the FCC tariff has designated the future use of the 833 and 822 codes. As the value of toll-free service and the advantages to having a meaningful combination of digits in a toll-free number (referred to as a vanity number) became increasingly apparent, numerous companies became toll-free service providers and established businesses selling toll-free service. Today, there may be more than 450 toll-free service providers, including telecommunications network providers, resellers, and independent organizations.

[00297] To understand routing of toll-free calls, it may be useful to understand how routing is performed for standard (i.e., not toll-free) calls.

[00298] With reference to Fig. 28, the North American Numbering Plan (NANP) 2800, introduced in the 1940s, established the 10-digit telephone number format used in the United States, Canada, and neighboring countries in the Caribbean. The format, shown in Fig. 28 consists of a three-digit Numbering Plan Area (NPA) code, and a seven-digit telephone number that includes three digits that identify an office code or local exchange and four digits that identify the individual number within the office code. The NPA, or area code, uniquely identifies a geographic area, the office code uniquely identifies a central office switching system (historically referred to as an exchange) within an NPA, and the line number points to the service components and dedicated resources in the switching system that provide the service instance identified by the line number.

[00299] When toll-free service was introduced in 1967, telephone calls were routed using information provisioned in each Public Switched Telephone Network (PSTN) local switching system. A routing table specified how the switch should process an originating call based on the digits dialed by the calling party and the arrangement of facilities that connected the switch to other switches. A switch has direct connections to other switches in the same area and connections to intermediate switches called tandems that provide the next hop toward other switches operated by the same company. Additional connections to specialized tandems provide access to long distance networks to transport calls to switches outside the local area. The local area where a company provides services is known as a Local Access and Transport Area (LATA).

[00300] The NPA or NPA-NXX of the dialed called party number identifies an entry in the routing table that points to the route needed to transport the call toward the terminating switch that serves the dialed line number. Initially, calls within a local area only required 7-digit dialing (just the NXX and the final 4 digits), but as the demand for telephone numbers grew, additional area codes were opened within a local area, and it became necessary to dial 10 digits for both local and long distance calls. If the digits dialed may be for an NPA-NXX served by the same switch, the routing table can indicate that a call should be offered to the subscriber identified by the telephone number. If the digits dialed indicate a NPA-NXX not served by the switch, the routing table can point to a route to a neighboring local switch, a local tandem, or a long-distance tandem.

[00301] Unlike a typical NPA, the 800 code introduced to identify toll-free numbers does not identify a unique area to which a call can be routed. To support toll-free service, additional entries had to be made in each local switch routing table to indicate the route for an 800-NXX code. Calling a particular 800 number was limited to the local switches that had been provisioned with routing information for that number. Additionally, further routing information was required at a terminating switch to map the 800 number to the terminating line.

[00302] In the early 1980s, AT&T introduced centralized call routing databases to handle routing of 800 calls. With a centralized database, it was not necessary to provision routing information for toll- free numbers in every local switch. Instead, switches were configured to query the database for routing information when it was recognized that an 800 number had been dialed. The database can be provisioned with routing information to direct a call to a route based on many factors, providing flexibility and removing the association of an 800 number to a specific local switch. This made it possible for a company to own a national 800 number and for calls to that number to be routed to a different local switch depending on where the call originated or the time of day. The flexibility provided by centralized call routing databases also enabled any carrier to provide service for any 800 number. Both geographic and carrier portability for toll-free service had become possible.

[00303] Today, in addition to toll-free calling, services like local number portability, operator services, and Advanced Intelligent Network (AIN) features, make use of advanced routing capabilities enabled by signaling system 7 (SS7).

[00304] With reference to Fig. 29, in the SS7 network 2900, the local switch is known as a Service Switching Point (SSP). A Signal Transfer Point (STP) 2902 provides routing of SS7 messages, and databases with call routing and feature information may be known as Service Control Points (SCP) 2904. To enable advanced routing via a centralized database, local switch routing tables may be configured to trigger a query to a database for additional call processing instructions based on various criteria.

[00305] In the case of a toll-free call origination, the switch can recognize the 8XX code in the dialed digits and launch a query to an SCP for routing information using the SS7 Signaling Connection Control Part (SCCP) protocol to transport a Transaction Capabilities Application Part (TCAP) query.

[00306] As shown in Fig. 30, the query may be routed by an STP to an SCP that has been provisioned with the information that describes how to route the toll-free call. In some cases the initial SCP that is queried by the local switch can return information that can cause the call to be routed to a switch operated by another carrier where a subsequent query to a different SCP can be performed to obtain the routing information needed to direct the call to the destination.

[00307] The routing information, consisting of a carrier code and terminating number, is returned in a TCAP response to the originating switch. The switch uses the information to select a route from its routing database and continues processing 3000 of the toll-free call.

[00308] Toll-free number administration includes management of number assignment and provisioning of customer records. This section describes the toll-free business, the key stakeholders, roles and responsibilities, and disclosed embodiment capabilities.

[00309] Key aspects of the toll-free number business may be described by the FCC tariff. This tariff, describing “regulations, rates and charges applying to the provisioning of functions and support services” was first released in 1993. Updates have occurred since, with the latest released January, 2013, becoming effective in February, 2013. This tariff describes the undertakings of the company responsible for the disclosed embodiment and the capabilities required of embodiments of the system itself. It defines key terminology and specifies the responsibilities of toll-free service providers, who may be the primary users of the disclosed embodiment. It also provides a schedule of rates and charges with regulations for billing toll-free service providers for disclosed embodiment access and usage. System requirements defined by this, or any other, tariff may be provided in “Business Rules” Section.

[00310] Some key participants in the toll-free business 3100 and the interactions between them may be illustrated in Fig. 31. Note that a primary geographic area for the toll-free business is the United States, Canada, and other areas where the NANP is used.

[00311] A toll-free subscriber contacts a toll-free service provider to order toll-free service. The toll-free service provider may be a carrier who operates a network or may have a relationship with a network provider in order to enable service. The toll-free service provider has an interface to the disclosed embodiment to search the pool of unassigned toll-free numbers and reserve one or more for use by the toll-free subscriber. Working with the toll-free subscriber, the Resp. Org determines how calls to the toll-free number should be routed.

[00312] On behalf of the toll-free subscriber, the toll-free service provider enters a Customer Record in the disclosed embodiment that specifies routing and carrier information for the toll-free number. The disclosed embodiment sends this information to the SCPs that control real-time routing of calls in the network. When the SCPs have received the routing information in the customer record, toll-free service is enabled for the toll-free number.

[00313] The toll-free subscriber has a business relationship with the toll-free service provider 3102 to pay for toll-free service. The toll-free service provider has a relationship with the TFMP to pay for access to the disclosed embodiment and use of the toll-free number assigned to the toll-free subscriber.

[00314] There may be a number of stakeholders that play key roles in the toll-free business, which may include those that follow:

[00315] FCC 3108 - The FCC is the federal agency that has responsibility for the FCC tariff that specifies the need for a toll-free number Service Management system and defines the regulations, rates, and charges applicable for the use of system functions and support services. The FCC may approve changes to rates or other aspects of the FCC tariff.

[00316] The TFMP 100 - The TFMP is responsible for the administration and operations of the disclosed embodiment and enforcement of the regulations outlined by a tariff. The TFMP may retain a number of contractors to assist with the activities required to manage the disclosed embodiment and related functions, including maintaining the disclosed embodiment software, running the data centers that house the disclosed embodiment, performing routine and corrective maintenance activities on the disclosed embodiment hardware, handling billing for access and use of the disclosed embodiment, and running the help desk to handle questions and requests from disclosed embodiment users.

[00317] Administrators and the TFMP Help Desk personnel can access the disclosed embodiment. Administrators can enter and maintain configuration and reference information needed for operation of the disclosed embodiment. Help Desk personnel can assist with troubleshooting access and Customer Record issues, complete TFMP Requests, and submit trouble reports.

[00318] Toll-Free Subscribers - Toll-free subscribers may be the end users of toll-free service. Toll- free service includes a toll-free telephone number and the network capabilities that enable calls to a toll-free number to be delivered to a designated terminating number according to conditions specified by the toll-free subscriber. Toll-free service is obtained from a toll-free service provider. [00319] Toll-free service providers (aka Resp Orgs) - Toll-free service providers may be responsible for the overall coordination required to provision, maintain, and test toll-free service. A toll-free service provider may be a carrier that operates a network or instead could be an independent company or organization that interfaces with a carrier to arrange toll-free service. Toll-free service providers may be the primary users of disclosed embodiment. In embodiments, the system may be used to search for and reserve toll-free numbers for subscribers and provision Customer Records that provide the network with the information needed to route toll-free calls. Toll-free service providers may be billed for access and use of the disclosed embodiment and control of toll-free numbers on a monthly basis as described by a tariff.

[00320] Toll-free service providers often maintain sub-organizations based on geography or other organization classifications. The toll-free service provider entity is the top-level organization against which reservation limits may be imposed (represented by the first 2 digits of toll-free service provider ID in the current system). The sub- organization within a toll-free service provider entity (represented by the full 5 digit toll-free service provider ID in the current system) is referred to as a toll-free service provider unit. The toll-free service provider users who access the disclosed embodiment can be associated with a toll-free service provider unit and the corresponding toll-free service provider entity. A toll-free service provider entity may manage many toll-free service provider units, each having a unique toll-free service provider ID.

[00321] SCP Owners/Operators (SCP O/O) - SCPs may be the databases in the SS7 network that contain the information used to route toll-free calls. SCP Owners/Operators contract with the TFMP to receive updates from the disclosed embodiment. An interface is established between the disclosed embodiment and the SCPs so Customer Record information can be provisioned to SCPs to enable the real-time routing of toll-free calls. SCP O/Os may be billed for this service.

[00322] At SCP O/O companies, the SCP administrator is responsible for establishing reference data about the SCPs and their corresponding SS7 networks. The administrator also manages tables at the SCP node and the Call Management Services Database (CMSDB) within the SCP to set controls and limits for SCP operations. They may be permitted to access and change data only for the O/O’s SCPs in the SS7 network.

[00323] A network manager is a member of Network Management Center (NMC) or Network Operations Center (NOC) at the SCP O/O company staff responsible for managing mass calling surveillance and control capabilities in its managed SS7 networks.

[00324] SCP O/O SCP administrators and SCO O/O Network managers may be users of the disclosed embodiment. [00325] Billing Administrator - This function coordinates the Billing of all customers, using information provided in the disclosed embodiment.

[00326] Industry and Regulatory Liaison - This function uses information in the disclosed embodiment to respond to inquiries or to make inquiries to the regulatory bodies.

[00327] Carriers - Actual telephone entity that carries the toll-free call. Carriers operate networks that process telephone calls. Local-Exchange Carriers (LECs) operate end office switches that provide access service to subscribers and carry calls within a local area, known as a LATA. Interexchange carriers (IC) carry calls between local areas. A subscriber receives service from a local-exchange carrier and designates the default IC to carry calls between LATAs. Historically, local carriers and ICs were distinct, but today a carrier can be both a LEC and an IC. A carrier may also be an SCP O/O, or a carrier may obtain SS7 signaling and database services from a separate SCP O/O.

[00328] With reference to Fig. 32, in one disclosed embodiment, the architecture 3200 for a solution for toll-free with key enhancements to support the unique requirements for toll-free number administration and call routing is illustrated.

[00329] With reference to Fig. 33, in one disclosed embodiment, the architecture 3300 provides number administration capabilities for toll-free numbers facilitating integration between PSTN and an IP network. This unified platform can serve both PSTN and IP enabled numbers.

[00330] Toll-free subscribers work with Resp Orgs to search and reserve toll-free numbers. Responsible organizations continue to populate the disclosed architecture with CICs for PSTN numbers and an NS Records for IP-enabled numbers.

[00331] The disclosed embodiments of the architecture can store additional metadata (for example: toll-free CNAM, industry code, description, license status, trade group affiliations, BBB ratings and such) for the toll-free organization as the transition completes, toll-free calls would provide consumer assurance through a validated neutral third party trust chain to significantly improve consumer confidence and prevent identity fraud.

[00332] In addition to the NS Record for the iSCP, Resp Orgs can choose to configure aspects of the routing logic with the disclosed architecture (second dip). They can map a SIP URI to a toll-free record. In this example scenario, a Resp Org would copy over that information with the iSCPs. In addition to the enhanced aspects of the iSCP, the iSCP may also facilitate direct IP interconnects between RespOrgs and their service providers, if desired, through sharing additional metadata about a route.

[00333] With reference to Fig. 34, Toll-free numbers 3414 (unlike mobile and landline numbers) have evolved to be a branding and identity vehicle. Companies are increasingly using their toll-free numbers along with their online assets to provide an integrated customer experience. With this growth, availability of vanity numbers has become sparse and demand is increasing. In embodiments, a toll-free tagging service may be provided that includes a subscription-based service that is made available to Responsible Organizations (Resp Orgs), consumers and businesses. The toll-free tagging service may provide the ability to tag a toll-free number (or group of numbers), and once a number is tagged, to track updates to that number (e.g., a change in ownership, change in availability, increase in search statistics) that may then be distributed (“pushed”) to customers through emails/text messages or other means. Subscribers of the toll-free tagging service may also have the ability to create, view, update and delete tags through a web application, mobile application, or some other user interface.

[00334] The toll-free tagging service may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, the toll- free tagging service may be utilized via hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks). The toll-free tagging service may permit the user to access the reporting capabilities of the TFMP through a client device, such as a personal computer, mobile phone, tablet computer, or some other computing facility, and receive data, including multimedia to the user’ s client device. Functionalities of the TFMP include, but are not limited to, Number Administration (NA) and Customer Record (CR) administration.

[00335] In embodiments, subscribers may be provided options to create custom toll-free number tags based on keywords, using a website. Subscribers may have the option to choose, for example:

• Keywords that spell a number (for example 800-Success)

• Category based tagging (for example “Laundry”)

• Location based tagging (for example “California Numbers”)

• Popularity (suggestions based on search engine metrics)

• Social Media mentions (Facebook and twitter feeds)

• Suggestive Tags (based on peer user behavior)

[00336] In embodiments, the system may ingest data from a plurality of sources, including but not limited to the following:

• Number popularity sourced from number searches from the toll-free management platform (TFMP) 3402

• Number dips sourced from SCPs and network elements 3404 • Facebook, Linkedin and twitter mentions of key words based on categories 3408

• Location information from fuzzy location parameters (including network location elements like NPA-NXX, ANI, JIP) and such

• Tag trend report based on tags that are most frequently indexed 3410

• News and Current event tags

• User contact sourcing (tag generation from subscribers address book)

• User social feed sourcing (tag generation based on users social media feeds)

• Seasonal tag sourcing (for example, Thanksgiving ads)

[00337] In embodiments, the TFMP 100 may allow for differentiated services based on subscriptions through a user interface 3420. For example, service offerings may be tiered:

• Regular Tier: May allow for tag alerting based on acceptable latency. Alerts maybe available through a non-guaranteed delivery mechanism like email, and allows for basic subscription services with a cap on subscribers.

• Plus Tier: May allow for low latency alerting based on multiple mechanisms. Premium customer support and access to artificial intelligence based indexing may be provided to see popular tags. This may allow for extended customer bases.

• Premium Tier: May allow for premium access to see search patterns from others, unlimited tags, high speed and high frequency alerting, and the like. May also allow for an “auto reserve” function.

[00338] In embodiments, the tagging service of the TFMP may provide an unbiased valuation for a number or group of numbers based on several factors including, but not limited to:

• Tag popularity

• Industry financial metrics

• Call completion, dip status

• Average call duration

• Vanity-ness

In embodiments, the tagging service of the TFMP may source data from distributed data sniffers that reside in networks to see dip rate and dip volume for popular numbers. This data may be compiled with other data sources including, for example, Google TM and Alexa TM trends (or other web traffic data and analytics) for tags and provide a heat map that shows “hot spots” for where the numbers are in demand and who is calling these numbers, nationally and internationally. In another example, a view may be provided that is a near real time valuation trend (e.g., analogous to a stock ticker) for, say, the top 10 tags/numbers by state/city. Current methods are limited in that they cannot combine call origination data, with social media and other public domain data, and near real- time, apply a valuation model to display a trends and prices on an interactive map, however the methods and systems of the TFMP enable such functionality.

The toll-free tagging service may alternatively or additionally utilize the TFMP system and may include a subsystem, referred to as a “node,” that may be used to build a decision tree that is downloaded to the SCPs. The decision tree may be used in various manners as otherwise described to facilitate call efficiency. Tagging data associated with toll-free numbers may be used, including with real-time network information and static call routing information, to create a real-time call path score. In an example, a toll-free number that is associated with spoofing or other fraudulent call activity may be tagged as a problematic number and a call route assigned to it to minimize the financial impact of receiving a high volume of fraudulent calls to the toll-free number. SCPs may also be a source of real-time call routing data and data used for tagging purposes. Using this information facilitates extrapolation and determination of uptime, downtime, congestion, geographical movement and economic movement of people communicating via calls. Based on real- time data that can be obtained from the SCPs and from the network, the TFMP may create a score that can be assigned to each call decision node. Such a score may also be used for the purposes of tagging. Similar to a mapping algorithm that uses distance and speed limit, given a starting point and a destination, the quickest or shortest map may be mapped. Changes in the call routing tree may be dependent upon an update to the routing tree that is then validated by the TFMP and then downloaded to the SCPs. With the use of real-time data, and more network decisions nodes added to a call routing tree based on the needs of the end subscriber, the TFMP may provide the ability to allow an end subscriber to have real-time business continuity for their toll-free number instead of having to contact their service provider, or getting a ticket opened to update their routing tree, and then having it download to all the SCPs for the new routing to take place. In embodiments, a call path score and real-time routing may be based on the best possible availability score. This may also be modified by the TFMP to allow for lowest cost score, based on the per-call and per-minute cost for particular carrier. The call score may be updated during low activity periods with a date/time stamp associated with it. This may allow real-time, or near real time, detection of a path’s status. Upon completion of a call down a particular path, the TFMP may also update the call path score and the data used for the purposes of tagging. Further, real time status changes in a telecommunications network, the performance of a given call route, or some other status change, may be used as additional tagging data. In an example, a toll-free number that may experience a season high- demand may begin to operate less efficiently, this metadata 3412 may be tagged to the toll-free number for use in, for example, predictive analytics provided by the TFMP regarding temporal changes in call activities and the optimization of certain call routes. Toll-free numbers tagged as having significant seasonal variation in call volume, or some other criterion, may have additional enhanced routing trees created for the purpose of handling peak seasonal call demands. A plurality of tagged numbers may be further associated with a TSPID so that a common entity associated with the toll-free numbers may be identified.

[00339] In embodiments, number trend optimization 3410 may be provided by the TFMP in order to provide recommendations to target the right audience for a number. Recommendations may include marketing a number on a certain media within a certain geography to promote calls to the right customer. Call origination data (in partnership with the call originators and service control points (SCPs)) will be sources to provide effectiveness metrics to users based on, for example, originating numbers and derived call success rates (based on average call duration) and call completion. The toll- free tagging service may alternatively or additionally be utilized with predictive analytic services that allow a user, through the customizable user interface, or “dashboard,” to access third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll-free telecommunication network. As elsewhere described, origination data may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trend and prices on an interactive map via the TFMP.

[00340] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

[00341] A method comprising: receiving data relating to at least one of a dip rate or dip volume that is associated with a toll-free number; receiving social media data relating to usage of the toll-free number; analyzing the combined data and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the demand associated with the toll-free number; and distributing a communication to an entity regarding the current valuation of the toll-free number.

[00342] A method comprising: analyzing data relating to a toll-free number and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the inferred economic activity associated with the toll-free number; inferring a rating of a second toll-free number based at least in part on the valuation metadata, wherein the toll-free number and the second toll-free number share an attribute; and storing the inferred rating of the second toll-free number.

[00343] A method comprising: receiving data relating to at least one of a dip rate or dip volume that is associated with a toll-free number; receiving social media data relating to usage of the toll-free number; analyzing the combined data and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the demand associated with the toll-free number; and initiating a toll-free number reservation based on the current valuation of the toll-free number.

[00344] With reference to Fig. 35, routing information in NS records 3500 may be downloaded to originating service provider (SP) ENUM or similar directory for call control. PSTN Call originations can continue existing PSTN 8xx call flow.

[00345] IP call originations can use an intelligent ENUM-like and SIP enabled intelligent Service Control Point (iSCP). In embodiments, many geographically redundant, highly available iSCP servers can reside in the originating service providers or provided by independent third parties. iSCPs can operate in mixed mode (SIP and PSTN) or be exclusively SIP. iSCPs provide ENUM like functionality enhanced with intelligent routing capabilities required for toll-free routing.

[00346] For IP call originations, the originating service provider queries its local naming (ENUM- like capability) server for call routing. The SP ENUM or similar service delegates the 8xx number queries to the iSCPs (similar to level 2 DNS). iSCPs execute intelligent call routing logic, and return a SIP Redirect with a URI for the SIP gateway of the toll-free service provider. The originating service provider can then route the SIP INVITE to the terminating toll-free subscriber’ s service provider.

[00347] For IP calls terminating to the PSTN network, the originating service provider queries its ENUM server similar to IP termination as described above, with the iSCP returning the URI for a PSTN gateway.

[00348] Toll-free numbers follow the NANP 10-digit format (NPA-NXX-XXXX) used for all telephone numbers in North America. A toll-free NPA designated by the FCC, such as 800 or 888, identifies a number as a toll-free number. Toll-free numbering may follow the E.164 format for identifying telephone numbers. The disclosed embodiment maintains status and associated information for the complete pool of toll-free numbers.

[00349] The Number Administration function provides the ability for a user to perform any of the following capabilities: a. Number Query: the ability to find out information such as availability, toll-free provider ownership, and status about a specific toll-free number. b. Number Search: the ability to look for one or many toll-free numbers. c. Number Reserve: the ability to reserve one or many toll-free numbers for his/her toll-free provider based upon the results of a search. d. Number Search & Reserve: the ability to search for one or many toll-free numbers and reserve them in the same single user action.

[00350] Except when noted otherwise, all number reservations may be taken and processed on a first come/first served basis. In embodiments, this may be due to a tariff requirement and true regardless of the source of the request.

[00351] A status is associated with each toll-free number that changes based on user actions to search for and reserve numbers and to provision and delete Customer Records for a number. Other status changes may be made automatically by embodiments of the system based on rules specified by a tariff.

[00352] The business rules around status change may include: a. Spare — Number is available to be reserved. No toll-free service provider entity has control of the number. b. Reserved — Toll-free service provider entity has taken control of the number, but a

Customer Record has not yet been provisioned. c. Assigned — Customer Record has been provisioned in the disclosed embodiment, but has not been sent to SCPs. d. Working — Customer Record has been sent to SCPs and accepted by at least one

SCP. e. Disconnect — Toll-free service has ended and intercept treatment, such as an announcement, is provided; a Customer Record may be needed to specify routing for intercept treatment. f. Transitional — Toll-free service and intercept service, if provided, have ended; there is no longer routing information in SCPs for the number and therefore no active Customer Record reflecting current information in an SCP associated with the number g. Unavailable — Number cannot be reserved by a toll-free service provider. h. Suspend — Number has been disconnected but has a Customer Record to restore service, or number is the subject of a billing dispute.

[00353] For all statuses except usually SPARE and UNAVAILABLE, a toll-free service provider entity may be associated with the number. This association begins when the toll-free service provider entity takes control of the number by completing a reservation. Except when noted otherwise, all number reservations may be taken on a first come/first served basis.

[00354] With reference to Fig. 36, in another embodiment for one click activation 118, a widget 3602 may be embedded within a webpage 3604 to facilitate reservation of a toll-free number via a user interface 1806. The term widget as used herein may refer to a client side, browser based application which displays data coming from different sources. In an embodiment, the widget 3602 may also be used on a mobile device as a mobile app. The embedded widget 3602 may communicate with a server 3608 using an API 3608 such as secure Restful API.

[00355] The widget 3602 may be embedded within a webpage 3604 with HTML tags. The complexity and logic may thus be hidden in the Javascript that resides on the server 3608. Loading the widget 3602 on to the hosting webpage 3604 may be performed through a bootstrap script that, for example, may be written as a Javascript file, or in some other language, that resides in the server 3608. A script tag can then be used to invoke loading this, thereby loading the bootstrap.

[00356] Generally, there are two ways to embed the content on the hosting webpage 3604, using IFrame, or using DOM in Javascript, and placing it within the host site or a combination thereof.

The host page may be a client website within which the widget 3602 is embedded.

[00357] Communication technology may include HTML5, JavaScript, CSS, JSON and Restful API and services. The client may utilize HTML5, Javascript, or CSS whereas the server may provide the Restful API and services. In order for the widget to communicate with the host page or if the widget needs to send data to the server, based on what is being used, it can be performed using Normal Post, AJAX (asynchronously), or some other process. In order for cross domain communication between the host page, embedded code or IFrame, HTML 5’s API called postMessage may be used. JSON is a file format that is understood by both client and server and hence may be also be readily used for data representation and transfer.

[00358] With reference to Fig. 37, various methods may be utilized to secure this communication. The widget 3602 may include a login feature 3902 in order to use the services. After initial credential validation with username and password, tokens may be provided to users. This may be used in the subsequent communication back to the server. In the alternative, API keys may be used. On authentication and authorization, various search 3904, reserve 3906, activation 3910, and confirmation 3912 elements may be provided.

[00359] With reference to Fig. 38, one disclosed non-limiting embodiment of a method 3800 may be initiated by loading the webpage 3604 (step 3802) then lazy loading the widget 3608 (step 3804). That is, the lazy loading may be utilized to minimize any effect upon the loading speed of the webpage 3604. Once the widget 3608 is loaded (step 3804) the login and search features (step 3808) are provided such that reservation/activation may be initiated.

[00360] The widget 3602 may be particularly beneficial to a business owner and/or Resp Org /Toll Free Service Provider. The business owner who visits a web page may view the widget 3602 that includes a statement such as, for example, “Reserve your Toll Free Number or “Do you have your Toll Free Number?” with a ready presented text field to search for a desired Toll Free Number or to enter their business name. A list of appropriate or related toll free numbers and an option to reserve and activate is thereby provided in a one-click or relatively one-click manner.

[00361] For a Resp Org /Toll Free Service Provider, the widget 3602 can be embedded in their portal. The widget 3602 provides a login page such that the widget 3602 provides a text field to reserve toll-free numbers along with a drop down list of numbers that expire in the next month and a popup link to extend. A popup link may also provide historical information such as their last 10 actions. The widget 3602 may also display a popup link to display status of the toll-free numbers in which a user previously indicated interest.

[00362] In the toll-free industry, it currently is a multi-step process to obtain a toll-free number and submit a request to active that number. It requires the user to first search and reserve a number and then in a separate transaction, often on a separate user screen, input the information to create a toll- free number routing record that is sent to the service control points (SCPs), thus activating the number for use. According to embodiments of the present disclosure, users may complete such a request related to activation of a toll-free number in a single user interaction with the system, providing minimal information. This process may provide a one-click-type functionality, hereinafter referred to as one-click activate, to activate the number, and will, in the same single-step user activation search for the toll-free number based upon user criteria. Initiation of the one-click activation may be facilitated by the use of a widget, as described herein, such as a widget operating on a client device. In embodiments, a one-click activate request may be a request from a user to 1) search for a number, or multiple numbers, that fit a provided search criteria, 2) reserve the number(s) matching the criteria, and 3) activate the number(s) using a selected customer record template, as described herein, and producing a pointer record. The final result of this request will be a toll-free number assigned to the user’s Resp Org that has a customer pointer record assigned to it. [00363] In embodiments, a user may utilize a new user interface screen, including but not limited to a customizable dashboard, as described herein, that may be accessed from a landing page of the user interface that is associated with the TFMP. The new screen may be referred to as the “Search - Reserve - Active,” also referred to herein as the S-R-A, from the landing page. A user may be required to have the correct permissions to be able to perform these actions, such as:

• The user must have Update in NUS_PERMISSIONS

• The user must have Update in PAD_PERMISSIONS

[00364] The S-R-A may also provide for predictive analytic services that may be provided to a user, through the customizable user interface, or dashboard, to access third party data services, sponsored data and information derived from toll-free telecommunications networks, including but not limited to telecommunications carriers, service control points, call centers, or other parties affiliated with a toll- free telecommunication network. As elsewhere described, origination data may be combined with social media and other public domain third party data, and near real-time, apply a valuation model to display a trends and prices on an interactive map via the TFMP.

[00365] In embodiments, the S-R-A screen may be a clone of a number search screen that is associated with the TFMP, and have, but not be limited to, the following screen design elements:

• Present an action button called “Activate New Number”

• Provide an action for the user to select a template record to be used for activation from a drop down list of template records

• Provide an action for the user to specify information necessary to be supplied in order to active a number, including but not limited to the following: o Effective date & time - A future date and time or “now.” Now may indicate that the record should go directly to an activated state, o Service order number o Number of lines to validate

[00366] With reference to Fig. 39, a sample UI design 3900 is provided. The UI may alternatively or additionally be embodied in a distributed computing environment, such as a cloud based computing network. In another embodiment, the UI may be hybrid networks, including usage of a cellular telephone network (and associated mobile communication devices, such as smart phones), a distributed, cloud network and an enterprise network associated with a carrier or other business organization (and any combination or sub-combination of such networks).

[00367] In embodiments, when a user selects the S-R-A function of the landing page, the system may retrieve a list of customer template records that have been defined for a Resp Org. If this Resp Org does not have any customer template records defined, the user may receive a message notifying the user of a lack of required definition, such as Έ205: Search, Reserve, & Activate functionality requires the users Resp Org to have at least one customer template record defined. Your Resp Org does not.” The user may then be returned to the Landing page. If the Resp Org does have customer template records defined, the customer template record names may be displayed in a scrolling list on the screen. The user may then select one of the customer template records for use in the request. [00368] In embodiments, a user may select a number search criterion that provides the ability to specify a specific number, a number with wildcard selection, or the NPA, NXX, and line number selections. The user may elect to have a set of default information (template, effective date, and service order number and so forth) associated with their Resp Org and/or user ID. Rather than select these items, the user may elect to use default values that are provided, thus expediting the process even further. The user may also elect not to use the default values, and may then supply the values. The search process may also include utilizing predictive analytics of the TFMP, as described herein, in order to learn more about the history and metadata that is associated with a number. Toll-free numbers, including those that are reserved and/or activated using the one-click activation may be tagged, using the methods and systems described herein, according to criteria of interest to a user. In an example, a user may search for toll-free numbers based on a predictive analytic result of toll-free numbers the TFMP has determined are active in the New England area. Predictive analytic results may also relate to specific populations of interest to a user (e.g., New York residents), behavioral data, or some other data parameter.

[00369] In embodiments, a number may then be reserved and/or activated and tagged by the user as a number that is relevant to the New England marketplace. Prior to reserving or activating a number, a user may also check a TFMP registry to determine if there is a history of reports of abuse associated with the number, for example frequent fraudulent calls (i.e., “spoofing”). The user may tag toll-free numbers in order to note this history of abuse, or other factor of interest, for future searches, and reserved or activated numbers may be associated with a toll-free service provider identifier (TSPID). The TSPID may be an existing TSPID that the user has, or as part of the one-click to activate method and system, a new TSPID may be created for the user. The user may select a customer template record from a list to be used when creating a pointer record used to active toll free number(s). The user may select only one customer template record to be used and that template record may be used with every number requested in this particular request. The user may select an effective date and time for the request. The user may further specify a future date and time or select “now” for immediate processing. Formatting and validation criteria may also be provided. The user may complete additional fields as necessary for a pointer record to be created: • Service Order number

• Number of Lines

[00370] In embodiments, once all the required fields are populated, the user may select the “Activate New Number” button to start the process. The process may include the search of, and reservation for, the toll-free number(s), and the submission of a request to create a pointer record for the number(s). Errors encountered along the way may result in an error being reported back to the user for that number. In an example, requests of more than ten numbers may be processed in the background, from the perspective of the user. The user’ s request may be validated and the user provided a request ID. Control of the one-click activate function may be given back to the user with a notice that they will be informed when the request completes. In another example, requests for ten or fewer numbers may be processed in real time and the results are returned to the user when the request completes.

[00371] In embodiments, the one-click activate function may perform a search and reserve function for all the requested numbers in blocks of up to ten numbers, depending upon how many numbers are requested. The activation function of the process may require a separate system request for each number being activated. The one-click activate function may control the processing of the individual requests so that, from a user standpoint, it appears as a single user interaction with the system, and a response does not go back to the user until the process has been completed. Once the request has completed processing, the one-click activate function may display back to the user in the search results area of the screen (e.g., ten or fewer numbers) the list of numbers and information about them similar to how it is done with the search and reserve functionality, as described herein. For more than, for example, ten numbers, the results may be made available in the communication area off the landing page.

[00372] In embodiments, a parking lot functionality may allow a user to go through a similar one- click activate process, but instead of establishing specific routing for a number via a customer record template, the user may define the routing for this number as “parked.” Parked in this context means that the number may have a default routing to a pre-defined customer announcement so the number can be activated without a final determination of the routing and when called, the user may be presented with this announcement stating the service this number provides is not currently available. [00373] The following are illustrative clauses demonstrating non-limiting embodiments of the inventions described herein:

A method comprising: receiving a one-click activate request from a user, wherein the request includes at least a customer record template reference and an indication of when to active a toll-free number associated with the request; searching a responsible organization record to determine the presence of a defined customer template record relating to the user request, wherein the responsible organization is associated with toll-free telecommunications; retrieving at least one customer template record, wherein the customer template record is a defined customer template record for the responsible organization; and activating the user request, wherein the activation includes at least one of activating or reserving the toll-free number.

A user interface, comprising: a webpage; and a widget operable to reserve a toll free number embedded within the webpage.

A method to secure user interface, comprising: lazy loading a widget operable to reserve a toll free number embedded within a webpage.

[00374] A representative flow operation showing the current system common number status transitions for activation of a toll-free service, starting with a number in SPARE status 4002, is shown in Fig. 40. Transitions that may not be part of the typical flow may not be illustrated in Fig. 40, including transition from WORKING 4004 to ASSIGNED 4008 and ASSIGNED 4008 to RESERVED 4010, as well as transitions to and from UNAVAILABLE status. SUSPEND 4012, DISCONNECT 4014 and TRANSITIONAL 4016 features may be provided. This flow is shown to facilitate understanding of system status transitions as may be understood by the customers.

[00375] A description of possible number status transitions is provided in the below table. This flow is shown to facilitate understanding of system status transitions as is understood by the customers and is not a dictate of limitations thereto.

[00376] The below delineated example use cases may be generic in showing the flow for multiple specific cases as defined in the particular example use case.

[00377] Examples: Number Search Using Starting Point

[00378] Example Number Search with Mask Characters

[00379] In addition to the existing number search and reserve functionality noted above, embodiments of the disclosed architecture may support search and reserve features. Description of at least some of these is provided at a relatively high level describing the business functionality required as follows:

[00380] As an example use case, to update Information such as dates, contact info, etc. for number(s) associated with a toll-free service provider may be provided as follows:

[00381] Change the toll-free service provider information for one or more numbers

[00382] Number Administration: Additional User New Features

[00383] Additional features in the embodiments of the disclosed architecture may be supported such as:

[00384] There may be a number of tasks where a system administrator enters values for configuration parameters that control an aspect of system functionality. A pre-condition is that the user is a system administrator with permissions to perform the specific administrative task.

[00385] For each administrative use case, the following sequence of steps applies: a. Step 1 : The user enters values b. Step 2: In embodiments, the system verifies the user input c. Step 3: In embodiments, the system accepts the parameter values and notifies the user of success

[00386] If the user input is not valid or some other condition prevents successful completion of the use case, embodiments of the system can inform the user of an error.

[00387] An example use case to open a Toll-Free NPA and NXXs is as follows:

[00388] An example use case to Specify Number Reservation Limits is as follows:

[00389] There may be additional features the embodiments of the disclosed architecture may include those that follow:

[00390] The Customer Record Administration (CRA) functions may be those concerned with the input, validation, processing, and management of the toll-free Customer Records (CRs). These may also include the processes by which embodiments of the system can upload relevant customer record data to the SCP toll-free databases in the public network, to enable their processing of SS7 toll-free database queries. Multi-number and mass change capabilities impacting CRs may also be included in CRA functionality.

[00391] The system’s CRA functions support interactions with external users or systems at the toll- free service provider to create and update the customer records. Additional interactions may be supported with telecommunications carriers, to approve and/or be notified of CR updates that impact toll-free calling traffic in their respective networks, i.e., Carrier Notification and Approval (CNA) functions. Further interactions may be supported with respect to the Local-Exchange Carriers (LECs), including Incumbent Local-Exchange Carriers (ILECs), Competing Local-Exchange Carriers (CLECs), other IntraLATA carriers, and CCS network operators whose networks may be involved in terminating the toll-free calls to the toll-free subscriber lines, and whose reference data, and others can be used to validate certain call routing instructions in the CRs. These latter capabilities may be referred to as IntraLATA Carrier Management (ICM) functions.

[00392] After a toll-free number (TFN) is reserved by a toll-free service provider’ s toll-free service provider, it should be assigned to a customer, and Customer Records (CRs) for that TFN may be created in the disclosed embodiment, ultimately resulting in their downloading to Service Control Points (SCPs) and the activation of service for the toll-free subscriber (the customer) in the public network.

[00393] A CR contains both customer administrative data and call routing information for a customer’ s toll-free service. In particular, it defines important aspects of the service, including the originating Area of Service (AOS) - the geographic area from which calls to the toll-free number can be allowed, and the rules for translation of the toll-free number to call routing instructions. The call routing instructions may include Destination Telephone Number(s) to which the toll-free calls may be routed, the Carrier Identification Code (CICs) of telecommunications carriers whose networks may be used for IntraLATA and InterLATA calls, and call announcement treatment instructions for those cases in which the toll-free calls should not be routed further.

[00394] Each TFN may have several CRs associated with it, each containing the toll-free service information to take effect at a given date and time (i.e., the Effective Date and Time of the CR).

Once established, service for a customer may be modified or disconnected via subsequent future- dated CRs. Future pending CRs then replace the active CR when their effective dates and times may be reached.

[00395] At the effective date and time, a subset of the active CR’ s data applicable to toll-free database query processing is then downloaded to the applicable SCPs in the public network, replacing (overwriting) any previous SCP customer record in effect for that TFN. Only one CR may be the active CR in embodiments of the system reflecting the current toll-free service for a given TFN.

[00396] Customer Records can be considered either one of two types: a. Regular Customer Records: Define the call routing for a toll-free number and define the final toll-free-to-TN destination number translations and what carrier can carry the call. These may be simple or complex. b. Turnaround Records: The originating toll-free calls may be routed only via the TFNs and CICs. The routing is deferred to the interexchange carrier networks, which may be responsible for the final toll-free-to-TN destination number translations. The term “turnaround routing” refers to the CR’s instruction to the SCP to “turn around” the TFN received in the SS7 query message as the routing number (Destination Telephone Number) in the SCP response, and the call is then routed onward to a carrier network based on the TFN and obtained CIC. It is then the responsibility of the carrier network to provide the final translation to the POTS Destination Telephone Number for final call routing. A TR can therefore contain only the TFN as a DTN or intercept treatment in its call routing instructions, and always without final routing to POTS destination numbers.

[00397] The disclosed embodiment administers 3 types of CRs: a. Customer Records: each pertaining to a single TFN and containing all of its service parameters; b. Pointer Records: each pertaining to a single TFN but pointing to a “reusable” “template record,” for much of its more complex service data, which it may share with other TFNs, and c. Template records: a record with service information that can be referenced (shared) by multiple Customer Records and referenced via Pointer Records (TFNs). Template records are valuable as a single complex record can be created and then referenced by multiple Pointer records. This saves space in the SCPs

[00398] Each type of CR may have a required common administrative data portion, and more complex, optionally populated Call Processing Record (CPR) data portions for more complex routing scenarios. The CPR portion facilitates a tree structure for the specification of variable (branching) call routing logic based on various decision criteria (decision nodes) and the resulting translations to destination numbers and carriers or announcement treatments (action nodes). CPRs may be used within Regular CRs and Template Records.

[00399] Creation/Updating of Customer Records to Reflect Call Routing

[00400] In embodiments, the platform may include a customer record template builder. The process and tools currently available for building a complex customer record may be single threaded and cumbersome. In addition, a tool may be required that works intelligently with the user to interpret natural language input to produce a complex customer record while using existing user records and usage data to prepopulate information for the user. This tool may be intuitive such that a first time user could build a complex record without hours of training.

[00401] The Customer Record Template Builder (CRTB) can allow toll-free providers to easily build a complex customer record template using a simple UI that can then let that record be designated at the default customer record. A toll-free provider can build multiple complex customer record templates for their use and to define a record as the default customer record, allowing the user to select the default with a single click, thus significantly reducing their work effort.

[00402] The CRTB can lead the user thru both the initial customer data population (known as the CAD portion) but also the call routing logic (known as the CPR portion) utilizing a simple UI using a decision tree logic structure with defined data nodes. Based upon the decisions at those nodes the UI can drive down a branch to a new decision node ultimately driving the customer record decision logic to the lowest level.

[00403] A decision tree can represent a series of decision points. Each decision point is called a node and off each node is one of more branches. The point at which there may be no more decisions to be made is called a leaf and is used as 'the “end point" of a branching structure. See Fig. 3 for a generic visualization of this structure.

[00404] The CAD portion of the CRTB can logically lead the user to populate the example following pieces of information: a. Administrative data about the toll-free customer b. Toll-free number c. Effective date and time d. Control toll-free provider identifier e. End customer name f. End customer address g. Area Of Service (AOS), h. List of destination telephone number(s)

[00405] Carrier Identification Codes (CICs) for IntraLATA and InterLATA traffic [00406] The complex customer record (CPR) decision nodes are supported as follows: a. Originating State b. Originating NPA c. Originating LATA d. Originating POTS NXX e. Originating POTS NPANXX f. Originating POTS number g. Specific date h. Day(s) of the week i. Time-of-day range j. Percent load share, which may be used to automatically direct different percentages of processed queries (calls) to different branches below the node.

[00407] The “leaves” supported by the data model at the ends of a given branch may include: a. Destination Telephone Number; b. Carrier; and c. Announcement Treatment.

[00408] A simple example of Customer Record routing would be as in Fig. 4.

[00409] In this relatively simple example, starting from the left-most branched path, the 3 decision paths corresponding to the decision trees branched paths can be represented as: a. Area Code = 732, NXX={ 699,494], Carrier=ATX-0288, Tel#=800-234-5678 b. Area Code = 732, NXX=Other, Carrier=MCI-0222, Tel#=800-234-5678 c. Area Code = Other, NXX=<null>, Carrier=MCI-0222, Tel#=800-234-5678.

[00410] The CRTB toll can be built in such a manner to allow a customer works his/her way down the decision tree and anticipate / pre-populate information based upon the information already provided in this build or also information provided in previous customer record entries. Once a default customer record template is built, the system can build the capability to invoke this template when creating a customer record for a new number, thus reducing the time and effort for a customer record to be built. [00411] The CPR portion of the CR may provide a mechanism for users to specify branching call routing and call treatment logic involving multiple destination numbers and multiple carriers based on one or more decision criteria. The decision criteria include aspects of the toll-free call, such as its originating geographic area (the originating state, CCS network, NPA, LATA, NPANXX etc.) to be mapped by the SCP, based on the calling party number and other attributes of the query), and the date, time-of-day and day-of week of the query, among other variables.

[00412] The CPR is linked to the CAD portion of a regular customer record by the referenced TFN and the Effective Date and Time. The CPR portion is also used in Template Records. When used in a Template record, the CPR portion is linked to the Template Record by the referenced Template Name and Effective Date and Time in the equivalent TAD portion of the Template Record.

[00413] The logical branch points of the CPR decision tree may be specified within one or more “decision nodes” along each traversable branched path. The resulting call processing actions, including the translation of the toll-free number to specific destination numbers, call routing via specific carriers, or the announcement treatment for non-routed calls may be specified in “action nodes” at the ends of each path. Each path logically begins at the dialed toll-free number being translated, progresses through one or more decision nodes that define the call criteria, and ends at one or more action nodes. Each possible path through the decision tree from root to the end of each branched path may be conceived of as a “row” in a logical data table or matrix. Each row may contain numerous decision nodes defining the set of criteria to be matched by the call attributes for a call routing case (path) and may end with one or two action nodes.

[00414] The CPR decision nodes supported by the data model according to one embodiment can include one or more of the following: a. Originating State (STATE) b. Originating NPA (AREA CODE) c. Originating LATA (LATA) d. Originating POTS NXX (NXX) e. Originating POTS NPANXX (6-DIGIT#) f. Originating POTS number (10-DIGIT#) g. Specific date (DATE) h. Day(s) of the week (DAY) i. Time-of-day range (TIMES) j. Binary Switch (SWITCH) - an on-or-off binary switch, which may be used to manually redirect call processing onto an alternate branched path. k. Percent load share (PERCENT), which may be used to automatically direct different percentages of processed queries (calls) to different branches of the node.

[00415] The action nodes supported by the data model according to one embodiment at the ends of a given branch can include: a. Destination Telephone Number (TEL#) b. Carrier (CARRIER) c. Announcement Treatment (ANNOUNCE) d. Go-To (GOTO) a pointer to another decision tree (CPR subsection) within the CPR, which defines further (refining) decision criteria.

[00416] Logically, decision nodes can have more than one argument for their included decision criteria (e.g., a list of more than one originating NPA, or more than 1 day of the week), and there may be multiple decision nodes used in combination to define each branched path (row). Each action node may have, at most, one outcome in the call routing logic. Null (empty) values for a decision node within a row convey its decision criteria is not to be part of the matched criteria defining the decision case for that row (i.e., that any value for that call parameter can suffice). A conceptual view of a CPR routing tree example is illustrated in Fig. 3.

[00417] Sample of Main Flow Customer Record Use Cases

[00418] This section has a sample of some of the many use cases that may be covered in this functionality. It does not represent every possible use case and should be a base for determining CRA functionality.

[00419] An example use case for Create a New CR for a Reserved toll-free number (New Service Connect) is as follows:

[00420] An example use case for Query /Retrieve/View an Existing CR is as follows:

[00421] An example use case to Create a New CR (Update Active or Pending toll-free service) is as follows:

[00422] An example use case to Delete an Existing (Future) CR is as follows:

[00423] An example use case for Query/View the List of CRs for a given TFN is as follows:

[00424] An example use case for Disconnect Toll-Free Service is as follows:

[00425] An example use case to Create a New Template Record is as follows:

[00426] An example use case to Convert a Regular Customer Record to a Pointer Record is as follows:

[00427] There may be additional features the embodiments of the disclosed architecture may support such as the examples that follow.

[00428] Customer Record Administration: Record Processing/SCP Downloads

[00429] The Customer Record (CR) Status indicates the status of the Customer Record with respect to its validation in embodiments of the system and its activation status at the SCPs. The CR Status is automatically generated by the current system. Because these states, as used by the legacy system, may be well known to the user community and may be regarded as fundamental to CR processing, they may be preserved as much as possible in the next generation system.

[00430] With reference to Figs. 41 and 42, customer record state diagrams for activation and output 4100, 4200, refer to the processes by which CRs can be translated and transmitted to the appropriate SCPs after they may be validated and receive any necessary carrier approvals through various nodes such as invalid, saved, hold, pending, and must check. This can occur when their Effective Dates and Times may be reached, or immediately in the case of CRs for which and Effective Date and Time of “now” has been specified by the user at input, and no carrier approvals may be required. Note that the standard processing of CR output (download) to SCPs is done via TM-798 data links. [00431] In embodiments, the system may translate the information in the Customer record (either a CR, a TR (template record), or a PR (Pointer Record)) to the TM-798 format for transmission to the SCPs.

[00432] The CR SCP Resend function may be used to resend a single CR to specific SCPs and use the SCP’s CR update confirmation responses to update the CR’s activation status. At the end of the CR resend process for a CR, embodiments of the system may update the CR’ s activation status and time as maintained for each SCP on the CR’s Active SCP list. An example use case is as follows:

[00433] There may be a number of tasks where a system administrator enters values for configuration parameters that control an aspect of system functionality. A pre-condition is that the user is a system administrator with permissions to perform the specific administrative task.

[00434] For each administrative use case, the following sequence of steps applies: a. Step 1: The user enters values; b. Step 2: The system verifies the user input; and c. Step 3: The system accepts the parameter values and notifies the user of success.

[00435] If the user input is not valid or some other condition prevents successful completion of the use case, embodiments of the system inform the user of an error.

[00436] IntraLata (CIC 0110) Routing Support

[00437] With reference to Fig. 43, the CIC 0110 validations 4300 from the perspectives of each of the involved service providers, including the Incumbent LEC (ILEC)/CCS Network Provider that operates the SSP, the terminating CCS network (the “Network Provider”), the ILEC or CLEC that has been assigned the NPA-NXX code and offers service to the terminating subscriber lines (the “Carrier”), and their relationship to the CR’s toll-free service provider Control toll-free service provider, which may all be the same or different entities.

[00438] With reference to Fig. 44, the series of reference data lookups that may be performed to validate the use of CIC code OTC-0110 with specified POTS destination telephone numbers in the CPR may be depicted. Functional requirements for the specifics of validation processing then follow.

[00439] The Carrier notification function facilitates authorized carrier users to receive and review notifications about CR changes affecting their CICs. The Carrier Notification and Approval (CNA) functions allow telecom carriers to define business agreements with toll-free service providers, set up permissions for the use of their Carrier Identification Codes (CICs) in toll-free service CRs, receive notifications of when their CICs may be used or modified on CRs, and approve when their codes may be used on specific CR’s controlled by other service providers.

[00440] In embodiments, the system can validate the CICs used in CRs to specify call routing, based on carrier permissions and restrictions specified in carrier and CNA reference data, generate notifications to the carriers, and correlate those against carrier approvals before the CRs containing the carrier’ s CICs may be activated.

[00441] The toll-free service providers’ View of Carrier Approval Status facilitates toll-free service providers to query carrier approval status information for their CRs at both a summary level and a detailed level (per-carrier), when multiple carriers may be involved.

[00442] An example use case to notify an affected carrier of CIC routing or toll-free service provider change is as follows

[00443] Carrier Submits Approval or Denial of CR Update

[00444] In embodiments, the system can be required to provide various logs of detailed CRA activity in order to support a number of key reports. In embodiments, the system can also provide a variety of measurements of CRA activity and associated resource usage, both in aggregate for the system, and where attributable to the respective toll-free service providers whose CRs may be being processed.

[00445] There may be certain items that may be validated in embodiments of the system as a result of outside carriers or partner’s rules. One such rule is:

[00446] A Mass Change is an event that requires embodiments of the system to perform a large volume of changes in a short period of time. Depending on the Mass Change event, it may be necessary to update system reference data and a large number of impacted AoS labels and customer records. In embodiments, the system thus provides functionality for management and administration of Mass Changes. [00447] The setup of Mass Changes may, for example, be performed online and the execution of the job processing the Mass change is done in the background.

[00448] This section has a sample of some of the many use cases that may be covered in this functionality. It does not represent every possible use case and should be but an example base for determining CRA functionality.

[00449] Example Set Criteria for a NPA Code Opening/Overlay Mass Change is as follows:

[00450] Example Set Criteria for a mass carrier change is as follows:

[00451] In embodiments, the system may identify records impacted by a mass change. Using the mass change criteria, embodiments of the system can search for records that may be impacted by the mass change and determine if the record can be updated for the mass change information or if manual intervention is required. The identification process can be repeated after verification of the results and manual action has been taken for those records that cannot be updated automatically. [00452] In embodiments, the system can identify and update records that are impacted by a mass change. Updated records may be assigned an appropriate effective date and time.

[00453] An example use case that updates customer records impacted by a mass change is as follows:

[00454] SCP administration and network management may be two important functions defined under SCP management. SCP administration functions in embodiments allow users to establish and modify SCP-related reference data in embodiments of the system and send messages to the SCP nodes and their Call Management Services Database (CMSDB) subsystems to manage data tables that reside there.

[00455] Network management functions for the toll-free Service involve the management of various parameters for automatic capabilities intended to monitor and control toll-free query traffic and calling volumes at the Service Control Points (SCPs), Service Switching Points (SSPs), terminating switches and terminating subscriber lines. When various call volume thresholds may be exceeded, the SCPs trigger Automatic Call Gapping (ACG) code controls at the originating SSPs.

[00456] The disclosed embodiment of the Network Management functions allow network managers to configure and adjust the relevant control parameters on SCP. Data collection at the SCPs can be configured through the disclosed embodiment to provide network managers with relevant surveillance information useful to monitor traffic and analyze problems, such as the detection of SCP overloads and excessive calling or excessive ineffective attempts to dialed codes.

[00457] The SCP Management (SCP-M) functions may be used by SCP administrators at the SCP Owner/Operator (SCP O/O) companies and by network managers for the SS7/CCS networks, which may be typically operated by the same SCP O/O entities or otherwise affiliated with them. SCP-M functions may interact directly with the SCPs via the SCP Interface as defined in TM-798. An example of these interactions is illustrated in Fig. 45.

[00458] There may be additional features supported by the disclosed architecture such as the examples which follow:

[00459] SCP administration functions of the disclosed embodiment allow users to establish and modify SCP-related reference data in embodiments of the system and send messages to the SCP nodes.

[00460] The principal users of SCP-M functionality may be assumed to be SCP administrators at the SCP Owner Operator (SCP O/O) companies and network managers at Network Management Centers (NMCs) or Network Operations Center (NOCs) at the telecom network providers who operate the SS7/Common Channel Signaling (CCS) networks. Secondary users may be administrators, who have global privileges to access the data and facilitate administrative and control actions of the SCP administrators and network managers.

[00461] The current system SCP Administration supports the management of SCP data tables or similar data structures. Functionality provided by a current system may be supported in embodiments of a new system. Design of disclosed embodiments may vary. These may include the following:

[00462] A common practice among SCP owner-operators is the running of periodic (typically annual) batch audits of extracted files of SCP customer records against the database in order to detect outdated or missing SCP CRs. The process is known as a reverse audit, because it uses the extracted SCP records as a basis for the audit comparison instead of the database. The typical practice for each SCP O/O has been to periodically audit each toll-free NPA’s range of CRs by extracting a SCP- generated CR audit file for that NPA.

[00463] The audit file is not a complete view of the CRs, but is rather an extracted listing of each loaded CR’s Customer Record Number (CRN), i.e., the TFN or numeric Template ID in NPA-NXX- XXXX format, Effective Date and Time, and toll-free service provider ID. The audit file is then loaded to the TFMP administration. The reverse audit process then compares the records to the corresponding CRs. The discrepancies may then trigger CR resends to the target SCP via the TM- 798 interface, or may be written to file for a subsequent batch resend.

[00464] The SCP Administration function supports actions performed by SCP administrators and disclosed embodiment administrators· The following may be sample use cases addressing SCPs, SCP mates, SSP lists and SCP-NPA NXX lists, among other administrative controls and limits for SCP Operations. These do not cover every possible action.

[00465] An example use case to define a SCP ID in the disclosed embodiment is as follows:

[00466] An example use case to Update the SCP ID data is as follows:

[00467] Establish or Update SCP mated pair inside the disclosed embodiment is as follows:

[00468] The disclosed embodiment may interface with all the SCPs using the TM-798 standard interface protocol. The embodiments of the disclosed architecture can maintain that interface standard as have each SCP change the interface may not be a viable approach.

[00469] The SCP interface is a dedicated Wide-Area Network (WAN) link supporting the establishment of TCP/IP socket connections between embodiments of the system and each SCP. In embodiments, the system may maintain a set of data related to the interface for each SCP, such as an IP address and TCP port number, as described by SR-4959, SCP-TFMP TCP/IP Interface Specification.

[00470] The embodiments of the disclosed architecture may need to translate the necessary information from its internal data stores into a standard interface for transmission to the SCPs. [00471] Network management is performed automatically by the SCP implementing overload controls whenever call volume thresholds may be exceeded. The disclosed embodiment defines the controls and sets thresholds. Data collection at the SCPs can be requested through disclosed embodiment to provide network managers with information to analyze problems.

[00472] Mass Calling Thresholds may be used to provide the SCPs with surveillance and control thresholds for each of 15 destination threshold level classes defined by the disclosed embodiment. Each of these thresholds is expressed in terms of the number of call attempts during, for example, a 2.5-minute period.

[00473] The disclosed embodiment automatically assigns a threshold level class to a particular destination telephone number of a toll-free-number, based on the number of lines associated with it, as specified on the Customer Record (CR).

[00474] The SCP detects focused overloads by counting call attempts for each destination number and comparing the accumulated count to the surveillance and control thresholds for the threshold level class assigned to the destination number.

[00475] If the call attempts during an example 2.5-minute measurement period exceed the surveillance threshold for a destination telephone number, then the number is placed on a surveillance list.

[00476] A destination telephone number remains on the surveillance list until it either does not exceed its surveillance threshold during a full 2.5-minute measurement period or it exceeds its control threshold when it’ s moved to the control list.

[00477] An example use case to Change the Mass Calling Threshold Data is as follows:

[00478] The Excessive Calling Controls may be used to set and change the calling thresholds for 6- digit and 10-digit vacant toll-free and out of area numbers. These excessive calling thresholds may be expressed in terms of the number of call attempts in a defined time interval (for e.g., 5 minute period). When the thresholds may be met, the numbers may be added to the control list and the calling rate is automatically limited by the SCP. In addition, a threshold is defined to automatically take these numbers off of the control list, when the calling rate decreases sufficiently.

[00479] The disclosed embodiment does not enforce the ACG (Automatic Call Gapping). A set of control parameter thresholds may be used to invoke the ACG. Once the thresholds may be reached, the ACG is triggered at the SCP-SSP level.

[00480] The Special Studies Request is done when a potential problem is suspected in the network and is done by sampling traffic to a specific number, Telecom Owner Operator Network or an SSP (Service Switching Point). A toll-free service provider, administrator, or a network manager can request an SCP owner operator for a special study into their SCP and they can either accept or reject the request to enable the study.

[00481] The study is conducted to allow a maximum of 100 calls in a maximum duration of 168 hours (7 days), which ever limit is reached first i.e., the collection of data can end when the specified number of call attempts have been monitored, or when the specified time limit is reached first. [00482] The special study can be requested for a toll-free number, Destination Telephone Number, carrier, or for an SSP. A toll-free number or a Destination Telephone Number of either 6-digit (NPA- NXX) or a full 10-digit number (NPA-NXX-XXXX) can be requested for the study.

[00483] An example use case to Create a Special Study Request is as follows:

[00484] In embodiments, the system is operable to generate a billing event record whenever an event occurs that results in a charge to toll-free service provider entity in control of a toll-free number. Billing event records may be collected and transferred to an external billing system. Currently, not all billable events result in a billing event record being generated by embodiments of the system and a manual Billing event record may be generated external to the current system. It may be desirable to automate the creation of as many of the billing event records as possible. [00485] In embodiments, the system generates a record when an event related to a billable function occurs. The event record can provide the information needed to calculate a bill for the charges incurred by each organization that makes use of the embodiments of the disclosed architecture according to embodiments. The event record can include the identification of the user, the action performed, and the date and time of the occurrence.

[00486] The interface to the billing system should remain intact and require minimal changes to the current billing system to support disclosed embodiments. The current Billing system Interface format of the file and the records it contains is described in TM-NWT-021766, and TFMP — Bill/800 Interface Requirements.

[00487] A summary of the current Billing Event record data elements may be as follows:

[00488] Billing Event records illustrate changes to toll-free service provider entity control of toll- free numbers that may be used to calculate charges to toll-free service provider Entities. On a periodic basis and in response to an on-demand request, embodiments of the system can compile a list of toll-free numbers with the controlling toll-free service provider entity, current status, and date the number entered that status and transfer the data to an external billing system. Only numbers with a controlling toll-free service provider entity may be included.

[00489] In one example, a system administrator can specify when billing audit data is to be collected and transferred. It is also possible to make an on-demand request for data to be collected and transferred as in the example use case as follows.

[00490] Due to the localized nature of call routing prior to the introduction of centralized routing databases, the same toll-free number may need to be controlled by a different toll-free service provider and provide service to a different toll-free subscriber in different geographic regions. In some instances arrangements still exist where the same number supports different toll-free service in different U.S. states and different service in the U.S. and Canada and other jurisdictions. A number involved in this type of arrangement is referred to as a duplicate number. The terms toll-free number, toll-free system, toll-free telecommunications network, toll-free carrier, and related terms as used herein are not limited to the United States or North America, but have equivalents throughout the world in other political, geographic, and technological regions. The methods, systems and functionalities, as described herein, are applicable to and operable within such equivalent jurisdictions.

[00491] On a periodic basis, embodiments of the system can compile a list of duplicate numbers and transfer the data to an external billing system. The data consists of the toll-free number providing duplicate service, the toll-free service provider entity for the number, the current status of the number, and data related to the Customer Record for the number. The CR data includes the status of the CR and the effective date and time of the CR. For the current system, this also includes indications if the CR includes Call Processing Record (CPR) and Label Definition (LAD) structures. Additional data is included from remarks entered in the CR that indicates the actual toll-free service provider that controls the number for each area where service is provided.

[00492] In embodiments of the disclosed architecture a subset of the series of reports can be provided. The system will provide a warehouse of data for reporting and analytics. The warehouse will enable a user to pull either standard (aka canned) reports or to generate user specific reports. Listed below are a series of reports that the current TFMP system provides. As an example of what reporting may be required, is a high level description of the reporting of the disclosed embodiment provides the following types of reports:

[00493] Most scheduled reports can also be accessed on-demand. The differences are how the report is kicked off and where the results of the report are sent/stored. The reports below are required at a minimum, but the Provider is expected to propose additional reports, for example:

[00494] The Exception reports may be automatically generated by embodiments of the system when exclusive events occur either in the disclosed embodiment or in an SCP. For example, the Misrouted Queries Exception Report is sent each time an SCP receives a call processing query for a toll-free number having NXX not in the SCP’s database.

[00495] The user can query the database tables and extract information, as mentioned in the following examples: a. In embodiments, the system logs specific number administration events as history records e.g., status change and ownership changes. The users can access this data to create their own reports. b. In embodiments, the system logs specific customer record events as history records e.g., status change and ownership changes. The users can access this data to create their own reports. c. In embodiments, the system logs logon ID locking history that the administrator can access and query reports from. d. In embodiments, the system logs specific template record events as history records e.g., status change and ownership changes. The users can access this data to create their own reports.

[00496] There may be additional features that the embodiments of the disclosed architecture may support such as the examples which follow:

[00497] The system will provide a platform for Analytics of TFMP data and usage. The Analytics platform should be flexible in providing some canned analytics as well as to allow the user to define and produce analytics on an ad hoc basis. The analytics should be able to be reports on current day actions as well as historical actions. Categories of analytic reports are: a. Individual toll-free Provider specific information on usage, TFNs, activity b. All or multiple selected toll-free providers information on usage, TFNs, activity c. SCP activity d. System performance information

[00498] In embodiments, the system is architected, designed, and implemented with security as a key attribute. The system shall ensure the confidentiality, integrity, and availability of information assets. Controls will be implemented that protect IP and data against unauthorized use, disclosure, transfer, modification, or destruction. Measures will be implemented such that legitimate users continue to have access to the system for the expected services levels. The security functionality will address two perspectives. One is the potential security threats and types of attacks that may be targeted at the system or service. The other is a framework for a systematic analysis of the measures available to protect the system or service from attack. One is the potential security threats and types of attacks that may be targeted at embodiments of the system or service. The other is a framework for a systematic analysis of the measures available to protect embodiments of the system or service from attack.

[00499] All aspects of a system, including the physical plant and facilities, operating system and application software, signaling interfaces and protocols, operations interfaces for configuration, surveillance, and administration, and data storage and processing functions, have security vulnerabilities that could potentially be exploited.

[00500] At a high-level, the security threats include: damage or destruction of information and/or other system or service resources, corruption or modification of information, illicit use, theft, or removal of information and/or other system or service resources, disclosure of information, and denial or interruption of services.

[00501] A security framework identifies the aspects of a system or service that require security and the methods available to address the security threats for each. From a security perspective, a system or service can be viewed as consisting of User, Control and Management planes. Each plane includes infrastructure, services, and application layers.

[00502] Security services provide capabilities to prevent attacks. At each plane and layer, one or more of the following example security services may be applicable:

00503] There may be additional features the embodiments of the disclosed architecture may support such as the examples that follow:

[00504] Some primary functions provided by the embodiments of the disclosed architecture include the ability to search for and reserve toll-free numbers and provision customer records that may be uploaded to SCPs to enable toll-free service. This can be done via an online interface (HUI) as well as by a machine-to-machine (API) interface. These interfaces allow manual and mechanized access to embodiments of the system for these functions such as those that follow:

[00505] The embodiments of the disclosed architecture may include a Web Services API for functionality supported in the Human User Interface (HUI).

[00506] The Human User Interface (HUI) provides user interface functions to the human users to access the system. The HUI may be accessed by many types of users. For example, a user can be administrator, a toll-free service provider user, SCP administrator, and network manager. Access to the HUI functions by a user can depend on the security permissions that have been assigned for the user by the administrator·

[00507] The HUI provides the following logical groups of functions which can be accessed by a user: User Profile and Security Administration; Number Administration Customer Record Administration; SCP Management; Reports; and Administration

[00508] The administrator and/or others may use the user profile and security administration functions provided by the HUI to protect embodiments of the system data from being viewed or updated/deleted by unauthorized users. The user profile and security administration grants permissions to different groups of users to access embodiments of the system to create, view, update and activate certain functions. The system can implement a role-based access control mechanism. [00509] The HUI provides functions to perform number search, reserve or cancel reservation for one or more toll-free numbers, change parameters associated with already reserved numbers, and query numbers for determining the number status and other number administration parameters. The HUI interacts with the “Number Administration Requirements” functional area to perform the number administration functions. [00510] The HUI interacts with the “Customer Record Administration” functional area to perform the functions described in this section.

[00511] The CAD function is used to enter the date and time for the toll-free number service, subscriber/customer information for the toll-free number, the Areas of Service (AOS) to be supported for the toll-free number, the carriers that, and others can be used to route calls to the toll- free number, and other associated service data for the toll-free number.

[00512] An example CAD can be associated with a Call Processing Record (CPR) for complex call routing data and can be associated with a Labels Definition (LAD) record for additional complex call routing data that is entered on the CPR.

[00513] The HUI interacts with the “SCP Management Requirements” functional area to perform the Service Control Point administration and network management functions.

[00514] The administrator or other toll-free service provider’s users can request the Scheduled and On-demand reports via the Report Request function of the HUI. The HUI interacts with the “Reporting Requirements” functional area to perform RRR request.

[00515] The disclosed embodiment Administration functions of the HUI may be used for Bulletin Board Messages, System Processing Options (SPO) and Downtime/Default Effective Time for CR (DDT). An Administrative Console may facilitate the system administrators and Help Desk personnel administrative functions for managing the system.

[00516] There may be additional features the embodiments of the disclosed architecture may support such as the examples that follow:

[00517] The API interface 4600 operates as a liaison between the toll-free service provider client systems (CS) 4602 and the disclosed embodiment (disclosed embodiments), thereby providing a mechanism through which interactions between the client systems 4604 and embodiments of the architecture can take place. The API interface 4612 may, for example, be used by Customer Record Administration 4608 and Number Administration 4610 components of the disclosed embodiment on one end, and the toll-free service provider client systems on the other end. This interaction is schematically illustrated in Fig. 46.

[00518] It is expected that disclosed embodiments can define a REST/SOAP API for machine interfaces. There is a current Mechanized Generic Interface (MGI) interface that supports many of our customers today and the embodiments of the disclosed architecture according to embodiments. The MGI interface is being used across the network by all client systems and there has to be backward compatibility. The move from MGI to an API interface cannot be overnight and has to be phased accordingly. The MGI Interface specification is available in SR 4592 MGI Interface specification.

[00519] In embodiments, the system provided alerts for certain situations. These alerts can be in the form of emails or via a logon notification or a console alert. Examples of these alerts may include:

[00520] This section provides a summary of characteristics of reference data. This need not define the absolute data needs, but can provide some insight into the data stored and used.

[00521] Reference Data may fall into the following categories: a. Network Administration reference data - primarily used to construct and/or validate Customer Records b. CCS Network Information is used to identify the CCS network served by the SCPs c. LATA to CCS Network Mapping is used to determine which networks and their SCPs can receive customer records for a specified LATA as the area-of-service d. NPA to CCS Network Mapping is used to determine which CCS networks and their SCPs can receive customer records for a specified NPA as the area-of-service e. Network Allowed Carriers is used to identify a subset of CICs that may be supported by a CCS network f. NPA-NXX to LATA Information is used as reference data of NPA-NXXs in LATAs and the association with an Operating Company Number (OCN) code, Company Code (CO), and Effective Date

[00522] General reference data about each telecommunications carrier that may be involved in carrying toll-free calls and might thus be an involved carrier included in the CRs of various toll-free service providers: a. Carrier Information b. Toll-free service providers and associated carriers c. Carrier Agreements with Entities For CR Input d. Entity Agreements with Carriers for CR Input

[00523] IntraLATA carrier management reference data — Used to support Local-Exchange Carriers (LECs) and other network service providers with the capability to control and/or manage the use of their networks for IntraLATA toll-free calls to a destination POTS number that terminates on their network include: a. Carrier Operating Company Numbers b. Network Provider-SCP Owner/Operator Company Codes c. Network Provider-SCP Owner/Operator Carrier Agreements d. Network Provider-SCP Owner/Operator IntraLATA Agreements e. Network Provider-SCP Owner/Operator IntraLATA Exceptions f. Carrier IntraLATA Agreements g. Carrier IntraLATA Exceptions h. Toll-free Service Providers Allowed Carriers i. Toll-free Service Providers Disallowed Carriers j. Non-Functional Requirements

[00524] In order to run a system, there is a need to understand the performance requirements of embodiments of the system and the processing throughput. This includes embodiments of the system availability needs as well as the capacity and performance requirements. The performance of the system must meet or exceed the performance of the existing legacy system for all parameters described in this section.

[00525] This section addresses the expected availability of the disclosed embodiment. The approach used for this section is based on industry standards related to availability.

[00526] This section establishes an understanding of terminology and establish context in this area in order to provide clear requirements regarding the reliability of the disclosed embodiment. A defined time period is needed to support an availability measurement. A typical calculation involves setting an availability objective or determining the actual availability of a system or service over a year. It may be necessary to identify exclusions from the time period, such as planned periods when it is known that embodiments of the system or service cannot be available. It can also be specified that unexpected circumstances that would impact availability, such as excessive demand, unusual operating conditions, or unexpected or disastrous events (e.g., earthquake, fire etc.) may be to be excluded from availability calculations.

[00527] Discussion related to availability often involves a number of 9s, i.e., “five 9s” availability. This refers to an availability objective or measurement of 99.999%. Applied for a year, this means the availability subject can provide the expected functionality across the given domain for 525594.744 minutes and therefore not be available to provide the expected functionality across the given domain for 5.256 minutes during the year.

[00528] When considering availability requirements, it is necessary to understand the functions it provides and its overall role in supporting toll-free service. Certain functions of the system, namely Number Administration, Customer Record Administration, and SCP Management, may be essential for supporting toll-free service. More specifically, the expected functions of embodiments of the system when it is available may be to: a. Receive and process number search/reserve requests and customer record input and update requests; b. Administer statuses for toll-free numbers and customer records based on user actions, effective dates and process rules applied by the system; and c. Download customer record information to SCPs.

The disclosed embodiment may be considered an operations system. Unlike an SCP, it is not involved in real-time routing of toll-free calls. If this were not functioning, callers would still be able to make toll-free calls and the calls would be routed to the correct toll-free service subscriber. In embodiments, the system does, however, provide “real-time” services (such as toll-free number and customer record administration) to toll-free service providers. An additional consideration is that access to toll-free numbers may be provided to all users equally so that one toll-free service provider entity does not gain a competitive advantage over others for reserving desirable numbers. This underscores the importance of consistent availability across user interfaces.

[00529] In embodiments, the system may also allow time and processing for the loading of industry reference data during routine maintenance windows.

[00530] Business continuity encompasses the strategic and tactical capability of the organization to plan for and respond to incidents and business disruptions in order to continue business operations at an acceptable predefined level.

[00531] Disaster recovery capabilities include the strategies and plans for recovering and restoring the organizations technological infrastructure and capabilities after a major system failure.

[00532] It may be necessary to establish objectives for unusual external events like earthquake or fire and non-routine activities like major infrastructure upgrades or transitions to new platforms. Overall solution design, including operations processes and procedures, may be needed to maintain business continuity during unusual circumstances and recover from disasters. Solution design considerations for business continuity and disaster recovery include geographic redundancy for solution components, deployment of backup systems and capabilities, and selection of the sites where equipment and operating personnel may be located.

[00533] A pictorial view of a disaster recovery scenario is illustrated in Fig. 47 at 4700.

[00534] In embodiments, the system can facilitate the required optimal use of disaster recovery sites and expenses such that analytics or other non-critical workloads can be run out of a warm/hot DR site, thus avoiding “Cold DR.” Redundant/disaster recovery site may be greater than 100 miles away (range listed in ISO 27001 as 30 to 100 miles)

[00535] Capacity planning involves a judgment regarding the anticipated usage of the functions of a system and a correlation to embodiments of the system resources needed to support the anticipated usage of a function. Based on the usage forecast, the quantity of each system resource needed to meet the demand is determined. Capacity is directly related to performance. If load or demand surpasses the level used to plan capacity, system resources can become overloaded and the ability of embodiments of the system to provide its intended function is likely to degrade. Once a system is operational, capacity management is a continuous operational process. Usage and performance may be monitored to recognize trends and capacity resource quantities may be adjusted accordingly. The objective is to maintain system performance and efficient use of resources as usage and demand change.

[00536] There may be a number of components that provide the resources needed to support the functionality provided by a system. Depending on embodiments of the system resource, capacity is expressed as a fixed size or quantity, or in terms of the demand, load, or usage the resource is expected to support. Capacity related to system usage is generally planned based on the average period of largest usage of the system, taking into account the cost of system resources, the probability of excessive usage beyond the average peak, and the impact of degraded performance when the anticipated peak is exceeded. For example, there may be three main areas for which the capacity may be considered as indicated in the following table:

[00537] In order to understand the system capacity requirements some current metrics having to do with capacity and utilization are provided (Figures 48-51).

[00538] Capacity related to system usage is generally planned based on the average period of largest usage, taking into account the probability of excessive usage beyond the average peak, as well as the impact of degraded performance when the anticipated peak is exceeded. The following assumptions were made when developing the capacity and performance requirements. In embodiments, the performance of the system may meet or exceed the performance of the current system for parameters: a. The initial processing capacity for the system can be engineered to include capacity for growth of 20% YOY. b. The system must be able to deliver burstable capacity. c. Assuming 7,988,500 usable toll-free numbers per NPA and 8 toll-free NPAs, the system must be engineered to maintain data for roughly 64 million usable toll-free numbers. d. During peak usage periods, assume 25% of user logins are logged in. e. It is assumed the system will have the capacity to support interfaces to 30 SCPs minimally.

*** Because a large volume of toll-free numbers are spared in hour 23, many toll-free service providers execute automated scripts to search and reserve for numbers that have just been spared.

[00539] Usage measurement and monitoring is required to provide fair and equal system access to all toll-free service providers. In order to do that, the system may measure, monitor, and alert the system usage for any instances where one provider’ s utilization is at a point where it is impacting the other provider’s use of the system. The measurements must be on a toll-free service provider level.

[00540] Reference data may be required to represent routing and numbering in the POTS network and the service areas supported by SCP O/O networks. The information provides the relationships between SCP O/O CCS networks and the LATAs, NPAs and NPA-NXXs each network serves and is used to validate the information in customer records. There may be 8 CCS networks supported by the system.

[00541] There are 164 LATAs in the NANP, roughly 380 NPAs in use or planned for use for POTS call routing, and roughly 160,000 NPA-NXXs assigned to central offices for call routing.

[00542] The system can provide memory capacity for the reference data needed to capture the relationships between States, LATAs, NPAs, and NPA-NXXs required to represent the POTS network.

[00543] The system can provide memory capacity for the reference data required to represent the network relationships supported by each SCP O/O CCS network.

[00544] The system must also allow time and processing for the loading of industry reference data during routine maintenance windows.

[00545] In embodiments of the system, functional data is the data required by each function supported by the system. The system maintains functional data for each NPA-NXX within a toll-free NPA and each toll-free number with each NPA-NXX. Currently, the toll-free NPAs 800, 888, 877, 866, 855, and 844 are open and NPA 833 is anticipated to open in 2017, making a total of 7 toll-free NPAs. Note that 822 and 889 are also reserved as a potential future toll-free NPAs. [00546] For each toll-free NPA, NXXs 000 — 199, 911, and 555 are not used. Additionally, in NXX 250, XXXX numbers 0000 — 1499 are not used. This results in 7,988,500 toll-free numbers per NPA. Assuming 8 toll-free NPA, the system will need to maintain data for roughly 64 million toll-free numbers.

[00547] In embodiments of the system, initial minimum memory capacity for the data required to support 64 million toll-free numbers. Toll-free service is enabled when a toll-free number is reserved by a toll-free service provider, a customer record is provisioned against the number, and information from the record is downloaded to SCPs. Numbers that are not currently controlled by a toll-free service provider (i.e., numbers in SPARE status) and numbers not available for toll-free service (i.e., numbers in UNAVAILABLE status) do not have customer records. Customer records are provisioned in advance of an effective date, and the system maintains current and pending customer records, so it is possible for multiple customer records to be associated with a number. [00548] A percentage of toll-free numbers will be in SPARE status and therefore not have an associated customer record. Additionally, many working numbers have not had changes to the provided toll-free service and therefore have a single active customer record. However, some numbers may have an active and pending customer record, and old records are stored by the system for a period of time. For the purposes of capacity planning and to account for the differences in size between simple and complex customer records, it is assumed that there is an average of 2 customer records per toll-free number. Therefore, the system will need to maintain 128 million customer records.

[00549] The system can provide initial minimum memory capacity for the data required to support 128 million customer records.

[00550] During peak usage periods, 25% of user logins are logged into the system. The system must provide capacity for 16,250 login IDs and anticipating 30% peak concurrent usage, capacity for 4,875 concurrent HUI sessions. Note that not all users who are logged into the system will be actively and continuously sending requests to the system.

[00551] During a time of extreme usage, such as the opening of a new toll-free NPA, there will a significant increase in the number of concurrent sessions. In the event of an extreme system usage situation the system should be able to quickly scale up to handle up to four times (4X) the normal peak usage period.

[00552] Instantaneous response time is the time for a response when performing an action regarding objects on the screen, such as using a mouse to select on an on-screen object or drag a scroll bar. [00553] When a human user takes an action related to an object on a screen, the system can provide an initial acknowledgment response in 0.1 - 0.2 seconds. [00554] When a human user takes action to request an operation or execute a command requiring system process of the request, the system can provide a response in 0.5 - 1 second.

[00555] A feedback response provides information regarding the progress or completion of a requested action.

[00556] For transactions that take longer than 5 seconds - the system will provide the user feedback that the transaction has been accepted and that the response will be available at a later time.

[00557] In embodiments, the system can provide an API interface for machine-to-machine transaction processing. The system can provide resources to support having API connections from each toll-free Providers (number of expected providers defined above).

[00558] The system can minimally have the capacity to support interfaces to 30 SCPs at launch with the ability to add more as the number of users grow.

[00559] The table below presents example minimum data rates for the SCP interface as stated in Section 4.2.2 of TM-798. The performance of the system may meet or exceed the performance of the current system for all parameters described in this section.

[00560] The system can provide the resources to support the data rate and message frequency for each SCP interface as specified.

[00561] There are four main areas of data integrity that may need to be addressed and monitored.

They are: a. Latency: The time between when information is expected and when it is readily available for use. b. Accuracy: Data accuracy refers to the degree with which data correctly represents the “real-life” objects they are intended to represent. c. Timeliness: Refers to the time expectation for accessibility and availability of information. Timeliness can be measured as the time between when information is expected and when it is readily available for use. d. Consistency: Two data values drawn from separate data sets must not conflict with each other, although consistency does not necessarily imply correctness.

[00562] Acronyms & Glossary

[00563] The toll-free telecommunications ecosystem, similar to traditional mobile and landline networks, is evolving to employ greater usage of Internet Protocol (IP) communications. With this transformation, there exist opportunities to facilitate a delegated and managed network between toll- free service providers (referred to as Responsible Organizations or “ROs”) and extend it to their customers to create a peer-to-peer toll-free network for exchanging voice, text and data.

[00564] In embodiments of the present disclosure, a trusted peer-to-peer network is provided for toll-free communications (TFN-P2P) that allows carriers to engage in managed communication with each other directly to exchange toll-free communications traffic. The Toll-free Management Platform (TFMP) 100 and its central registry, as described herein, may facilitate the setup, establishment and approval (“trust”) for a peer-to-peer communication channel, and may manage authorization, validation and approval of the peer-to-peer toll-free communication process. [00565] In embodiments, the TFMP 100 may include methods and systems for number administration 102, customer administration 104, call management services 108, texting services 110 and text registry, and a smart services registry 112, as described herein, for the management and operation of toll-free communications over IP. The TFMP may allow users to search for, receive recommendations for, and make reservations of toll-free numbers 114 to be implemented and utilized in IP-based toll-free communications. A user interface may allow activating a toll-free number, for example through a one-click activation function 118, as described herein. Users may access the TFMP to create and access existing templates 120 of toll-free call routing customer records, and utilize a routing tree engine 122 to create customized call routing trees for the toll-free numbers of interest to the user, where such call routing templates, call routing trees, and the like include IP- based communications options. The centralized TFMP 100 may provide routing information for toll- free calls. This information may be broadly referred to as call processing records (CPRs) and commonly referred to in the industry as customer records, as described herein.

[00566] Figure 52 presents a simplified call flow diagram showing the relationship between the TFMP, Responsible Organizations, and SCPs. A toll-free call may be initiated by a call originator, which is then handled by a service provider network. The service provider network may communicate with an SCP in part to determine information relating to call control and call routing. The SCP may communicate with the TFMP for further information regarding number administration, such as that provided by responsible organizations in call processing records and customer records. The TFMP may return to the SCP data relating to route provisioning or other toll-free communication channel data to assist in routing the call to its termination point. In embodiments, the originator of toll-free calls (often a communication carrier) queries (also referred to as “dips,” as described herein) a network service control point (SCP) to determine the destination of the call.

These SCPs are network resources that act as proxies to the number route information (customer records) from the TFMP. Customer records may be broadly grouped into two categories: 1) Direct Records. These are also referred to as turn around records. These are basic queries that map a toll- free number to a carrier identifier, usually referred to as a Carrier Identification Code (CIC Code)., and 2) Complex Records. These are more complex routing instructions that allow for toll-free subscribers and service providers to create a decision tree based on vertical features. Examples of vertical features include time of day routing, Numbering Plan Area codes (NPA) based restrictions, area of service filters and carrier diversity features. Carrier diversity features would include, for example, the ability to have different service providers service the call based on call origination area of service or the ability to switch service providers due to network service events like heavy call traffic, congestion, outage or disaster. [00567] During a typical call flow, calls originate from a local exchange carrier (LEC) or a mobile network operator (MNO). As shown in Fig. 53, MNOs and LECs have networks established with national communication carriers (referred to as inter exchange carriers (iXCs)). iXCs act as a call facilitator to deliver calls to the destination network, or termination service provider, and the final call termination point. Since it becomes an arduous task for every LEC to have a cross connect with every destination network, the iXCs act as intermediaries or a façade for call delivery. However, with the merging of the software and communications industries and emerging IP communication landscape, ROs now have tools to work directly with each other, which were not available to them previously. The TFN P2P, as described herein, facilitates direct connectivity between ROs and extends the concept to connect ROs directly with their end customers, without compromising the integrity and trust of toll-free communications because it is managed and secured by the functionalities of the TFMP, as described herein.

[00568] In embodiments of the present disclosure, there are two main components of the TFN P2P. The first may be referred to as TFP Peer Management & Metadata Enrichment. This system may allow for adding additional metadata to current call processing records that tag numbers with the type of endpoint, and the support for direct connections. This information may be added to the CPRs for numbers as an optional parameter. The information that may be added may include, but is not limited to:

• RO ID

• Session Initiation Protocol / Internet Protocol Support (SIP/ IP Support) Flag - A Boolean indicator that shows the terminating service provider and endpoint’s ability to accept IP packets

• SIP/IP Uniform Resource Locator (SIP /IP URI) - A E.164 or similar numbering plan compliant resource identifier for the terminating end point.

• SIP /IP Name Authority Pointer (NAPTR) - Resource record in the DNS system that is used to map end point or service provider servers and user addresses.

• Peer Dip Life

• Peer Rating

[00569] In embodiments, the peer rating indicator may be calculated based on information provided by ROs including, but not limited to, an average cost factor, comparative peer performance, ease of connectivity, accounting reconciliation requirements and call quality. This information may be further enriched with TFMP performance data derived from, for example, trouble tickets and help desk information. Data obtained from public domain (e.g., BBB ratings, DUNS information, social media scores) may be added to the computation used to infer an overall peer rating. Additionally, a peer management and approval process may be provided that tracks, manages, approves and activates peers in the toll-free IP-based communications ecosystem.

[00570] In embodiments, a second component of the TFN P2P may include an Intelligent SCP. The Intelligent SCP, as used herein, may allow for a smart dip service. Smart dips may be structured as a series of sequential dips with increasing fidelity in the information provided relating to the terminating carrier. The originating carrier, can incrementally request for additional information from the TFMP, as shown in Fig. 54, based on their desire and confidence level in directly peering with the terminating carrier. This may result in a dip cycle such as the following:

• Dip 1 - Traditional Route: During the first dip, the SCP may return a CIC code or CPR associated with the request. It may also return a flag that informs originating carrier networks that there is a possibility for a direct connect. The originating carrier may then validate its possibility of a bilateral channel with the terminating carrier and initiate a second dip (referred to here as “Dip 2”).

• Dip 2 - Peer Meta Data: During the second dip, the smart SCP may provide the requestor with peer metadata that facilitates basic direct peering with the terminating service provider.

• Dip 3 - Peering Success Indicator: During the third dip, the smart SCP may provide an average cost and quality metric based on an algorithm for determining success probability that includes various factors including data obtained from the TFMP (type of connectivity supported, network based quality data, peer rating), historical information gathered from dips (Peer Meta data dip frequency and re-dips, dip1/dip2/dip3 ratios).

[00571] In embodiments, in order to preserve the integrity of toll-free numbers, a time to live parameter may be added to the peer metadata that indicates how long this dip is valid for direct connections. By analogy, this may be thought of as the “shelf life” of a given connection, during which time it is approved as having sufficient integrity for use in completing toll-free communications. Originator SCPs may enforce dip life and ensure that local cache busting occurs at the end of dip life. The SCPs may also ensure that data refreshes occur post dip life.

[00572] In embodiments of the present disclosure, the TFMP, as described herein, may provide a smart data sampling and aggregation device and aggregation cloud for toll-free call routing, or Self Learning Toll-free Aggregator (the “STFA”). The STFA may provide a non-blocking sampling of the network element exhaust data that includes logs and other metadata that is logged by Service Control Points in Service Provider Networks based at least in part on a machine learning and/or a self-throttling algorithm. Routing information for toll-free calls may be provided by the centralized TFMP, as described herein. This information may be broadly referred to as a call processing records (CPRs) and commonly referred to in the industry as customer records.

[00573] Figure 52 presents a simplified call flow diagram showing the relationship between the TFMP, Responsible Organizations, and SCPs. A toll-free call may be initiated by a call originator, which is then handled by a service provider network. The service provider network communicates with an SCP in part to determine information relating to call control and call routing. The SCP may communicate with the TFMP for further information regarding number administration, such as that provided by responsible organizations in call processing records and customer records. The TFMP may return to the SCP data relating to route provisioning or other toll-free communication channel data to assist in routing the call to its termination point. In embodiments, the originator of toll-free calls (usually a communication carrier) queries (also referred to as “dips,” as described herein) a network service control point (SCP) to determine the destination of the call. These SCPs are network resources that act as proxies to the number route information (customer records) from the TFMP. During a typical call flow, calls originate from a local exchange carrier (LEC) or a mobile network operator (MNO). As shown in Figs. 53 and 54, call flows are depicted included those in which MNOs and LECs have networks established with national communication carriers (referred to as inter exchange carriers (iXCs)). iXCs act as a call facilitator to deliver calls to the destination network, or termination service provider, and the final call termination point.

[00574] In embodiments, network SCPs may be optimized to provide fast response times for requests and may be central to call delivery and completion. Typically, SCPs produce passive logging information in a standard format similar to Call Data Records (CDR) that is stored either locally or in a remote log server and aggregated, primarily for billing and charge back purposes by SCP owner/operators. This data may be referred to as the SCP CDR exhaust feed and may include large data sets that typically contain:

• Request information such as the originating Automatic Number Identification (ANI), the originating carrier, the request type, time stamps, and the like.

• Response information such as a Carrier Identification Code and response status.

[00575] By analyzing SCP exhaust feeds, carriers and service providers may gain valuable insights about their network performance, call completion status and call origination metrics. Service providers may also gain insight to prevent toll-free fraud and malicious traffic pumping and fortify their network from threats. Due to the distributed nature of the SCP and fragmented network operations, SCPs often work in silos and are restricted to operate within the carrier network. However, further high service quality requirements, coupled with the large data sets, make it challenging to read, interpret and correlate SCP exhaust data in real time.

[00576] In embodiments of the present disclosure, the Smart Toll-Free Aggregation (STFA), as shown in Fig. 55, may provide a small footprint wiretap that is collocated within an SCP network. The STFA may acts as a data sniffer by sampling data that is spit out from the SCP data exhaust. Components of the STFA include, but are not limited to:

• Smart Wiretap & data queue

• Local Analytics Agent

• Machine Learning Sampling Algorithm

• Cloud aggregation network

[00577] In embodiments, the first three components may run locally in an SCP network and/or collocated with the SCP as shown in Fig. 55. In embodiments, the Smart Wiretap may act as an external interface for the SFTA. This component may either be integrated into the core libraries that make up an SCP or may be a device that is collocated with the SCP. It may consume SCP log messages (e.g., raw data) near real time, and stores this data within a distributed data queue. The Smart Wiretap may select log messages using selectors. These selectors may be dynamically created in real time by the Machine Learning Sampling Algorithm. In embodiments, a Local Analytics Agent (LAA) may be a consumer of the sampled wiretap data. Local analytics agents may perform stream pre-processing using advanced analytics functions like map/reduce techniques and correlation to group SCP dips by various dimensions, including, but not limited to, dimensions such as:

• Aggregate dips by originating number

• Aggregate dips by originating AOS

• Aggregate dips by destination number

• Aggregate dips by originating device type

[00578] The sampling algorithm may determine the type and frequency of summarization. Once the local summarization is complete, the machine learning algorithm may determine the time to live for sampled raw data. The Local Analytic Agent may store the summarization in a local store and/or compress and share anonymized/masked summary information with a cloud aggregation network. [00579] In embodiments, the Machine Learning Sampling Algorithm (MLSA) and Local Store may perform real time computation to determine statistical sufficiency of incoming data and to forecast trends and patterns in analytic usage. The amount of data and level of sampling required for statistical significance may be determined by the MLSA using factors that include, but are not limited to:

• Data Intelligence provided by the toll-free aggregation cloud.

• Real time toll-free metrics: The MLSA may measure the network load and resource utilization and dynamically adjust the collection frequency and sampling rate by the LA As.

• Historical Toll-free Trending: The MLSA’s local in-memory database may track a graph of various SCP activities, including but not limited to, call volume, traditional call volume spikes (e.g., April 30^th), seasonality (e.g., the week of Christmas), customer events (e.g., toll-free NPA new code release), and throttle sampling to account, and adjust for spikes.

[00580] In embodiments, the toll-free aggregation cloud may act as a task manager for distributed LAAs in carrier SCP networks as well as an integrated intelligence and reporting platform. The toll- free aggregation cloud may be comprised of toll-free intelligence, and a reporting functionality for trend analysis and prediction, as shown in Fig. 56. The toll-free aggregation cloud may collect and share toll-free intelligence from a LAA network to ensure intelligent collection and collective sampling. Depending on data needs, sufficiency issues or user configuration, the toll-free aggregation cloud may throttle up collection for an individual SCP, a cluster of SCPs in a network or a network of SCPs within an area of service. The aggregation cloud may use a smart learning algorithm similar to the LAAs to plan for spikes and seasonality and ensure optimal sampling with no degradation in performance of the SCPs. In embodiments, the aggregation cloud may receive call path information from LAAs and provide further aggregation to determine trends and patterns for toll-free call volume. By leveraging statistical models, it may compute the statistical sufficiency of data received. Historical data may also be leveraged to predict additional trends. Post processing, indexing and visualization provide an interactive dashboard to customers, as described herein. The toll-free aggregation cloud may also provide real-time visibility into trends, problems, threats and abuse with up to the minute dashboards presented to users.

[00581] Referring to Fig. 57, in an example embodiment, a call may originate in the Carrier Network Local Exchange (“Carrier Infrastructure”). Calls may be handled by a carrier switching point (SSP), which identifies calls destined for a toll-free number for additional processing. For toll- free calls, the SSP queries the SCP to get call routing information. This information is called a customer record. The SCP may execute service logic and return information to route the call including carrier identification code (CIC), billing information and any special processing. After returning the information, the SCP forwards the SSP Query along with the SCP response to the Smart Wiretap for Sampling. The SSP may continue call processing and route the call to the carrier (identified by the CIC). Call routing and processing may resume, resulting in 8xx termination to the destination. A Smart Wiretap may receive the call for call information for processing. The Smart Wiretap may send call information to the Machine Learning and Sampling Algorithm (MLSA) to decide if the call information should be sampled, processed and stored. The MLSA may determine if the call should be sampled based on input received from, for example, network load and volume information received from the carrier infrastructure real-time, global SCP sampling needs and administrator configuration information received from the Toll-free Aggregation Cloud, and/or call data received from the Smart Wiretap. The MLSA may return sampling rate and configuration information along with response for call sampling. The Smart Wiretap may select call data for sampling if specified by the MLSA, or resume to standard call management and routing processes. The Smart Wiretap may store the raw data in a distributed highly available queue for processing.

The Queue may work in a publish-subscribe model. Processing agents may subscribe to new messages for processing. On receipt of a new message, the first free analytics agent (LAA) may evaluate the message from the queue, process the data based on Map-Reduce techniques and create summarization information based on predetermined dimensions. For example, aggregating all calls by NPA (area code). Aggregated data may be periodically shared with the toll-free aggregation cloud for producing reports and creating trends.

[00582] The present disclosure provides a modernized service, or Toll-Free Data Distribution Hub (DDH) that enables a low-cost solution for distributing toll-free call routing information to network operators and other providers of call routing services, including telecommunications operators, carriers, networks and the like that are operating or providing services within a communications system other than a toll-free telecommunications system. Historically, toll-free routing data was distributed to Service Control Points (SCPs) that are controlled by SCP Owner/Operators. SCPs are costly to build and maintain and support an outdated network infrastructure. As a result of these factors, the number of SCP Owner/Operators has diminished, particularly over the past ten years. Toll-free numbers (TFNs) were introduced in the mid-1960s to allow called parties (businesses, primarily) to accept financial responsibility for long distance voice calls. Over the years, TFNs have become part of the corporate identity for many companies in conjunction with their web addresses, logos, and branding. Many value-added services have been developed using TFNs as a primary access method for users (i.e., conference calling) and marketers rely on TFNs to evaluate ad campaigns and track consumer behavior. In the past 50 years, TFNs have been used to facilitate voice-based communication and the number of Network Operators receiving a direct feed of authoritative toll-free routing data is swiftly declining due to a combination of the interface being technically outdated and costly. Network Operators are no longer investing in legacy network elements, instead focusing investment on next generation IP-based networks. Furthermore, while most other call routing is getting cheaper, toll-free call routing continues to be costly and Network Operators are looking for ways to reduce these transport costs.

[00583] In embodiments, the toll-free management platform (TFMP), as described herein, may be a distribution point for authoritative network routing information for toll-free phone calls. The TFMP may distribute toll-free routing data to SCPs in Service Provider networks (see Fig. 58). However, the amount of SCP Owner/Operators is dwindling, with only a limited number receiving authoritative toll-free routing information. There are multiple reasons why this number is rapidly decreasing. First, it is difficult to connect to a platform, such as the TFMP, for authoritative toll-free routing data. The connection may be a legacy, proprietary interface. Third party service offerings may be based on an SCP architecture, and many off-the-shelf offerings may be expensive and nearing end-of-life. Furthermore, there are increasingly fewer developers with prior experience with legacy interfaces, and carriers are reluctant to invest in legacy network elements. Not only is it technically difficult to build a SCP to a legacy interface, it is also costly from both a capital and operating expense perspective. Further, once the SCP has been built and certified, there are operating expenses that may include subscription fees, and maintenance and operating costs. Therefore, it doesn’t make financial sense for the majority of Network Operators to receive a direct feed of authoritative toll-free routing data. Most rely on Routing as a Service (RaaS) providers who provide a query (or “dip”) service to provide toll-free routing information on a per call basis. For most Network Operators the per query cost is cheaper on an annualized basis as compared to the annual SCP operational cost.

[00584] Carrier networks are designed to terminate calls using the lowest cost and most efficient route available. However, to do so, the terminating (or receiving) carrier needs to be identified. Databases may not identify the terminating carrier, but instead provide the long distance carrier based on the caller’s location. Toll-free numbers usually have at least two routes - the long distance network of the terminating carrier, and the long distance network of a partner carrier, typically either AT&T or Verizon (legacy MCI).

[00585] Consider an example of a San Diego-based consumer calling a toll-free number located in Tampa Bay. When the Network Operator in San Diego queries for the toll-free routing information, they will receive information indicating to send it to the long distance network of the terminating carrier. If the terminating carrier does not have a long-distance network in San Diego, the query will tell them to route it to a partner who has a long distance network with access in San Diego. Many of today’s Network Operators either do not have long distance access networks or have only built these facilities where it makes the most economic sense. More often, they end up partnering with a Network Operator that can provide ubiquitous long distance access, typically AT&T or Verizon.

Resp Orgs, CLECs, and Toll-Free Subscribers must rely on legacy networks to connect to each other. Due to the ubiquitous reach of their networks and their common carriage facilities, an estimated 70% to 80% of all toll-free calls are routed by legacy long distance providers like AT&T and MCI (now part of Verizon).

[00586] In embodiments of the present disclosure, a DDH is provided to modernize the distribution of toll-free routing information by translating a legacy interface to an open- standards based Application Programming Interface (API). In doing so, the TFMP may provide a toll-free data distribution service to a broader set of Network Operators at a fraction of the cost of owning and operating a SCP, and broaden distribution & availability of toll-free data, modernize access to toll- free routing information, make access to toll-free routing information less expensive, help Network Operators reduce the cost of toll-free calls, and provide the technology blueprint for the future of toll-free.

[00587] In embodiments, the DDH API may have a mechanism by which the data distribution subscriber can download a complete replica of a toll-free database and store it locally in their network. Once the data is loaded into their local data store, they may then utilize a local API client to communicate with the DDH API and pull down data updates in near-real time. The simplicity of the API may reduce the cost of obtaining authoritative toll-free routing data while shortening the implementation period from many months to weeks or even days. A reference code may be provided to help customers build an API client and drive early market adoption. 58ure 2 depicts the high level architecture.

[00588] In embodiments, the DDH may be enhanced to include a policy layer for alternate route provisioning, as well as an open-standards API for automated route provisioning. Data Distribution subscribers and Resp Orgs alike may provision alternate routing information, such as an IP route or alternate Carrier Identification Code (CIC), to improve the efficiency and lower costs of routing a call to a TFN. Fig. 60 shows the high level architecture corresponding to this functionality.

[00589] Having a local copy of an entire toll-free database may have several advantages over using a RaaS provider. Importantly, it can significantly reduce routing charges to toll-free numbers. Since the Resp Org ID is included in the local copy, carriers can often identify the terminating carrier and utilize the least cost route if one is available rather than using the legacy long distance route predetermined by the Resp Org. This can help lower the network cost of routing to Toll-Free Numbers. A local copy of toll-free routing information can also help improve the end-user experience. When a local copy of toll-free routing information resides inside a carrier’s network, it significantly reduces call setup latency. By eliminating the need for an external query, or “dip”, call setup time is shorter thus improving end-user satisfaction. Disaster recovery may become much less impactful with a local data store. Should an outage occur, the carrier has a local copy that is still usable to route calls until the issue is resolved. Conversely, if a carrier is relying on a RaaS provider and they have an outage, calls are unable to be routed until the issue is resolved or a disaster recovery service is spun up.

[00590] In embodiments, the DDH channels of distribution may consist of Network Operators and RaaS providers. Network operators can access the data either directly from the TFMP, via Certified Distributors or via Certified Routing Database providers. RaaS providers can only access the data directly from the TFMP and are only permitted to distribute routing information via a query-based service. In an example embodiment, Network Operators may contract directly with the TFMP with a dedicated connection to the DDH API. In this setup, the Network Operator may be limited to replicating toll-free routing data within their own network only. There is no resale permitted, nor is a query service permitted. Fig. 61 depicts this distribution channel. Target markets for this channel may include, but are not limited to, current SCP Owner/Operators who are Network Operators, such as Sprint, AT&T, Verizon and CenturyLink.

[00591] In embodiments, Network Operators may also receive toll-free routing data through Certified Distributors. Certified distributors may have a centralized network appliance, through which they would distribute the Toll-Free routing data to satellite appliances deployed in the network of the Operators. The Certified Distributor may enter into a reseller licensing agreement with the TFMP, allowing them to distribute copies of the toll-free routing database to their customers. The Certified Distributor may be required to provide a revenue share/royalty fee to the TFMP for each connected customer. Fig. 62 depicts this distribution channel. The target market for this channel may be existing RaaS SCP Owner/Operators, for example TNS and Tel-Lingua. This model may enable toll-free data distribution through companies who offer routing databases and softswitches.

[00592] In embodiments, Network Operators may also access toll-free routing data via a Certified Routing Database. This channel may be similar to the Certified Distributor, except the Network Operator may contract with and be billed by the TFMP. The Routing Database Provider may “certify” their network appliance software with the DDH API. The network appliance may then be deployed in the Operator’s network, and receive updates via a dedicated connection to the Toll-Free DDH API. Fig. 63 depicts this distribution channel.

[00593] In embodiments, RaaS providers offer a query -based, or dip, service to Network Operators. They currently serve the majority of Network Operators who do not own and operate a SCP. The RaaS model may be a premium service. Fig. 64 depicts this distribution channel. This model may apply to current RaaS providers such as TNS, Teliax, Sprint, AT&T, and Telus.

[00594] In embodiments, business analytics may also be included as part of the DDH service, including but not limited to providing LCR/peering recommendations based on call record analysis. This may provide intelligence that can be used to scale peering, improve routing, and prevent fraud. The API may also be used for other types of communications data. In an example, currently there is no central source of Caller ID or CNAM data for Toll-Free. By adding this data as a field in either the TFMP and/or the DDH, an authoritative source for toll-free CNAM may be provided. This authoritative data source may help reduce the spoofing of calls from toll-free numbers, and Resp Orgs may update what they want called parties to see when contacted by a toll-free subscriber, possibly including visual information such as logos and other branding elements.

[00595] In embodiments, the Data Distribution Hub may provide toll-free number call routing details to downstream customers. As toll-free number information changes, the data may be made available to downstream customers, in chronological order, via a First-In-First-Out (FIFO) queue that a customer accesses and depletes through a Data Distribution Hub API.

[00596] Referring to Fig. 65, the major architectural pieces of the Data Distribution Hub System are provided for reference. Note that throughout this document the terms toll-free number and call routing number (CRN) are used interchangeably.

[00597] Figure A depicts one embodiment of the major components of the Data Distribution Hub System: Service Control Point (SCP) API Manager, Data Distribution Hub, ApacheMQ, WS02 (or other open source software, such as broker/message software), Web Browser, and the Databases. In embodiments, the Data Distribution Hub may technology that includes, but is not limited to:

• Java

• Spring Framework (JPA, Spring Security, Spring MVC)

• Hibernate ORM

• MySQL Database

• Oracle Database

• REST Based API

• APIGateway for API traffic, throttling, denial of service, analytics

• Application Monitoring

• Development Environment & Tools

• Robot Framework for test automation

• Bitbucket Version Control

• JIRA Agile • Sonarqube code analysis

• Gradle Build Tool

• Jenkins Continuous Integration

[00598] Figure 66 depicts a simplified representation of the Data Distribution Hub System interfaces, placing the SCP and Data Distribution Hub components into a single “Data Distribution Hub System” (the dashed-box depicted, and depicting the interfaces into that system. The “Data Distribution Hub System” box may encompass many applications and hardware, including all of SCP and the Data Distribution Hub. The components surrounding the central box may be external systems that integrate with the system.

[00599] The Data Distribution Hub System may collect information from the TFMP, the API Manager, and Web Interface and provides the information to “downstream” Data Distribution Hub Customers. The TFMP interface may provide data (e.g., call routing information) to the Data Distribution Hub System. The Data Distribution Hub System may be a client of this interface. Using the TFMP interface, the Data Distribution Hub System may learn if a toll-free number is active and record the toll-free number’s call processing record (CPR) in a database. One message type that may be conveyed on this interface, for the Data Distribution Hub System, is the UPD-UCR, which provides toll-free number “add/update” and “delete” information for the toll-free number and its CPR. [00600] In embodiments, an API manager may be provided within the Data Distribution Hub System and provide a self-service API, usable by the front-end GUI. The Data Distribution Hub may access the API Manager to provide and retrieve customer information as needed.

[00601] In embodiments, a web browser interface may be provided for Data Distribution Hub users and administrators to perform configuration and monitoring tasks that cannot be handled by the Data Distribution Hub API. For example, the web browser interface may provide access to user profile information and other data. A web application may be provided, such as an application written using Javascript. In an example, when a user types the Data Distribution Hub URL into a browser, the browser may access the Data Distribution Hub system and download a combination of HTML, CSS, and JavaScript. Subsequent interactions by the user may result in REST based calls to the Data Distribution Hub backend to retrieve data needed to satisfy the customer action.

[00602] In embodiments, a Data Distribution Hub API may provide similar information as legacy systems to the downstream Data Distribution Hub customers using REST and JSON. The Data Distribution Hub API may provide messages such as adding, updating, and deleting toll-free numbers, and provide CPR information for each active toll-free number (aka CRN).

[00603] In embodiments, the Data Distribution Hub System may be composed of several virtual machines (VMs), as shown in Fig. 67. [00604] SCP, the Data Distribution Hub, and the database servers may each be a virtual machine (VM) in a cloud deployed solution. High availability (HA) may include redundant VMs.

[00605] In embodiments, a database server may provide access to a database via a specific database API. In an example, Oracle may be used for SCP. MySQL may be used for the Data Distribution Hub. The pieces of the Data Distribution Hub System may access their respective database servers via configurable IP addresses and ports, so their final location may be flexible. Oracle and MySQL may be provided on individual, geographically redundant, VMs provided by the cloud for HA. Additionally, the architecture may allow for the use of Amazon RDS as a replacement for running Oracle and MySQL database servers on Data Distribution Hub VMs.

[00606] In embodiments, the SCP host may run on its own VM and communicate with the TFMP interface. A local copy of the downloaded data may be kept in an Oracle database, or some other database type. As toll-free numbers are added, modified, or deleted, events may be saved in a FIFO queue and consumed by the Data Distribution Hub so that it can maintain the state of the toll-free numbers for use by the downstream Data Distribution Hub customers (via the Data Distribution Hub API). The Data Distribution Hub may receive information from a SCP event queue, an API Manager (REST/JSON), and Web Browsers using HTTPS for customer configuration. The information (state) may be stored, for example, in a MySQL database on the database server. The messages downloaded by Data Distribution Hub customers may be stored in a single database table in the MySQL database along with an index into that table for each user. This may allow the Data Distribution Hub to save a single copy of data to support any number of users. Each user may maintain a pointer (index) to the last row in the table that they downloaded. As a client consumes messages, the last index read may be updated in the database.

[00607] In embodiments, the SCP software architecture, as described herein, may support the TFMP interface. An application on the Data Distribution Hub Server may access an Oracle or other database to drain SCP's event queue, one event at a time, in FIFO order. Fig. 68 depicts a simplified schematic of the SCP software components.

[00608] In embodiments, the SCP application may communicate with the TFMP following a specification. The application may populate the FIFO queue with the needed information for the Data Distribution Hub. FIFO Queues may be used to support communication between SCP and the Data Distribution Hub. A database FIFO queue may contain events destined for the Data Distribution Hub Server. For example, when a 798 UPD-UCR “delete” occurs, this event is communicated between SCP and Data Distribution Hub via this queue. As requests are processed, the results may be added to the SCP FIFO queue by the TFMP Interface application. The Data Distribution Hub may then read from the FIFO queue. The event may be removed from the FIFO queue when the Data Distribution Hub has confirmed receipt and storage of the event, one event at a time. This queue may be necessary when the Data Distribution Hub is down in that it may allow the TFMP Interface to acknowledge the UDP-UCR events (and other events) arriving and still queue the events for later transmission to the Data Distribution Hub once it is running again.

[00609] Figure 69 depicts the major software components of the Data Distribution Hub Server, including the software that communicates with SCP, the API Manager, Web Browsers, and Data Distribution Hub customers via the Data Distribution Hub API.

[00610] The Data Distribution Hub may use an Apache Web Server and Spring/MVC and wait for HTTP requests to act upon.

[00611] In embodiments, a Data Distribution Hub Interface may run in java and exchange information with the Data Distribution Hub "add/delete business logic" regarding the state of toll-free numbers (including their call processing records, Resp Orgs, and secure hash algorithm- 1 hashesj.The Data Distribution Hub Interface may act as a client for queued events and periodically wake up (configurable in seconds) and inspect, for example, the Oracle FIFO queue. When there are events in the queue, the Data Distribution Hub Interface may send REST/JSON messages (such as an "add toll- free number") to the Data Distribution Hub "add/delete business logic", which is acting as the REST/JSON server. The Data Distribution Hub add/delete business logic may save the data (for example, in its MySQL database as well as in the API download queue) and send back a REST confirmation to the Data Distribution Hub Interface when its work is completed. In embodiments, the Data Distribution Hub Interface may not remove any data from the Oracle FIFO queue until the Data Distribution Hub add/delete business logic has confirmed that the event was successfully processed. If the message to the Data Distribution Hub add/delete business logic was not successfully processed, a failure reply may occur and/or no reply at all may be generated. In failure cases, the Data Distribution Hub Interface may leave the event in the Oracle FIFO queue and retry sending the event later. When a failure occurs, the Data Distribution Hub Interface may return to its "sleeping" mode and wait for the next cycle to try again, and keep trying and sleeping until it is successful. Once successful, the event may be removed from the Oracle FIFO queue and the Data Distribution Hub Interface may move to the next event. Each event may be processed completely, in order, to maintain the integrity of the MySQL database on the Data Distribution Hub host. Therefore, the Data Distribution Hub Interface may not continue (or skip events) when a failure occurs. The entire Oracle FIFO queue may be blocked until the failed event is successful. In embodiments, GUI business logic may store Data Distribution Hub customer information in a database, in the API Manager, and may support health, status, user profile, or maintenance logic. [00612] In embodiments, the Data Distribution Hub add/delete business logic may process events received from the Data Distribution Hub interface (such as toll-free number "add" and "delete"). The events may ultimately result in queueing of information to be sent to Data Distribution Hub customers over the Data Distribution Hub Routing API. This component may use the MySQL database to save the state associated with the toll-free numbers, and use the MySQL database to store the resulting events in a single FIFO that is consumed independently for each downstream Data Distribution Hub API client.

[00613] In embodiments, Data Distribution Hub API business logic may access and transmit the FIFO queued events that resulted from the Data Distribution Hub business logic, as described herein, and read messages stored in the database table FIFO. The FIFO may reflect the results from the Data Distribution Hub add/delete business logic (e.g., information from SCP about toll-free numbers). The events may be read in order and provided to downstream Data Distribution Hub customers.

[00614] In embodiments, the Data Distribution Hub Routing API FIFO queue may have a producer (Data Distribution Hub add/delete business logic) and a consumer (Data Distribution Hub download business logic). A single queue may exist for API clients along with an index into the queue for each user. The queue may contain the events, in order, to be consumed by the Data Distribution Hub Customer. The events may be add (and update) and delete among potentially other events. As the add/delete requests are processed from SCP's FIFO queue, the results may be sent to an API client when the client issues an HTTP GET request to the Data Distribution Hub /download URL. Then, the download business logic may read events from the FIFO queue and provide the add/delete events to the associated downstream Data Distribution Hub customer. The “last message read” index may then be updated in the MySQL database for the specific API client.

[00615] In embodiments, an asynchronous process may ran to remove messages that are older than a configurable date. This may prevent the database table / FIFO from growing too large and affecting performance. In an example, up to 45 days’ worth of data (based on an expected load of 57,000 message a day) may be stored in a database table.

[00616] In embodiments, the Data Distribution Hub may use MySQL, or some other format, for storage of user and toll-free number data used by the applications. The MySQL database may provide a server, listening on a well-known port for incoming database clients. This may allow the server to be placed on any host to accommodate the HA architecture.

[00617] In embodiments, a front-end web application of the Data Distribution Hub may consist of CSS, HTML, and JavaScript. The web front end may be static content that includes JavaScript that runs in a client browser to perform REST based calls to the Data Distribution Hub back-end application. When a user accesses the login URL of the web front end, the user may be presented with an initial screen that allows the user to login or to sign up as a new customer. When a user attempts to login, they may be required to enter a username and password into fields on the screen and hit a login button. When the user presses the button, JavaScript logic embedded with the web page may capture the values from the username and password fields (as well as any additional fields included in the design) and pass them to the Data Distribution Hub using a “login” web service. If the user is successfully authenticated by the Data Distribution Hub, a web token may be returned to the web browser and the JavaScript logic may transition to the user profile page or any one of the “secured” screens that exist as part of the web application. When a new user attempts to sign up, they may be required to create a username and password and enter any relevant information required by this application. When the user presses the sign-up button (link), JavaScript logic embedded with the web page may capture the values and pass them to the Data Distribution Hub using a “sign up” web service. If the user is successfully added, a web token may be returned to the web browser and the JavaScript logic may transition to the user profile page or any one of the “secured” screens that exist as part of the web application like the login flow.

[00618] In embodiments, when a user successfully logs in to the Data Distribution Hub, they may be presented a token. Once the web browser has the token, it may be authorized to access any of the secured pages of the web application by providing the token in subsequent REST calls to the Data Distribution Hub. If a valid token is provided to any Data Distribution Hub server, the Data Distribution Hub server may process the REST call from the browser. This behavior may be sufficient to satisfy the requirements that the Data Distribution Hub application is stateless and allows for flexibility in the HA architecture. A token may be created as a JSON Web Token (JWT), an industry standard mechanism for token creation. The token may consist of a series of tags created by the Data Distribution Hub application that are used to encode information to uniquely identify the user and any other data that the application may require to operate. The tags may be hashed and signed with a secret known only to the Data Distribution Hub. This may protect against a user creating their own tokens and masquerading as another user. In addition, an expiration field may be embedded in the token to expire the token.

[00619] In embodiments, a High Availability architecture may be associated with the Data Distribution Hub and may include a primary site as well as a Disaster recovery site. This may include regionally redundant VMs provided by a cloud service for SCP and the Data Distribution Hub. This redundancy may allow for both HA and upgrades (to minimize downtime to achieve the 99.99% uptime requirement during upgrade). As an example, the Data Distribution Hub may be deployed using Amazon Web Services including EC2 and MySQL and Oracle RDS in a multi- AZ configuration. The Disaster recovery systems may run in a separate region as the primary systems. [00620] In embodiments, the Data Distribution Hub Routing API may provide an efficient "audit" of toll-free number data. An audit may be forced by the Data Distribution Hub after a failover (or outage), if desired, for any customer, or it may come as part of the Data Distribution Hub Routing API. The audit may use message digests against the expected data to determine the accuracy of the Data Distribution Hub customer's local data store. The audit may use, for example, a recursive 10- prong-tree (a branch for each digit, 0 ’..’9’) and message digests to identify and correct invalid toll- free number data.

[00621] In embodiments, VMs may run the Data Distribution Hub download business logic and access the customer API download queue in a MySQL database. These VMs may be deployed in an auto-scaling pool configuration, such as that provided by Amazon Web Services. As an example, a performance and scalability solution of the Data Distribution Hub may be:

1. Many VMs may be deployed, each able to perform the Data Distribution Hub download business logic. a. Each of these VMs may have an Apache web server ready to service the well- known Data Distribution Hub Routing API Port for inbound REST/JSON messages.

2. The Data Distribution Hub Routing API load may be balanced across the set of VMs.

3. Data may be stored in a centralized database that may be accessed by any Data Distribution Hub server.

4. Since the Data Distribution Hub Routing API is stateless, the Data Distribution Hub download business logic running on any VM may access the database to retrieve Data Distribution Hub customer metadata, including the location (IP address/port) of any FIFO queue.

[00622] In summary, performance and scalability may be achieved via a stateless architecture that uses identical VMs as more customers sign up for the service. Each VM "type" may be generic to allow any number of them to be quickly brought online in a cloud environment. Automated scaling may also be applied to enable self-scaling: including dynamically adding and removing VMs based on offered load.

[00623] Figure 70 shows the possible generalized interactions between SCP and the Data Distribution Hub Interface.

[00624] In embodiments, the Data Distribution Hub Interface application may be a REST/JSON client doing the following: It may periodically wake up (e.g., configurable in seconds, defaulting to one minute) and check for events in the Oracle FIFO queue. When the Data Distribution Hub Interface reads an "add" or "update" event from the SCP FIFO queue, it may translate them both to an "add" event for the JSON to send to the Data Distribution Hub. In an example, the Data Distribution Hub may not distinguish an Update Customer Record (UPD-UCR) from a Update Resp. Org (UPD-ROR) since they both show up as "add" events. An "add" event may also mean "replace if it already exists". The reason a UPD-UCR and UPD- RORs may be treated the same is for simplicity of the downstream interfaces (both for the Data Distribution Hub server and the Data Distribution Hub clients). When the Data Distribution Hub Interface reads an "add" (or "update") event from the queue, it may find the associated CPR hash for the toll-free number (CRN) from the CRN table. This hash may be sent as part of the "add" event to the Data Distribution Hub server. In an example, only the hash may be sent, and not the CPR - the Data Distribution Hub server may request the CPR specifically. When the Data Distribution Hub Interface reads a "delete" event from the queue, it may send the event to the Data Distribution Hub (there may be no need for a CPR hash in the "delete" case). When a successful response is received from the Data Distribution Hub server, the event may be removed from the queue. If a failure response (or no response) occurs, then the event may remain in the queue to be retransmitted when the Data Distribution Hub Interface tries again. In the Data Distribution Hub add/delete business logic, when it receives the "add" and "delete" events from SCP, the business logic may perform the following: 1) It may add the events to the API download shared queue, and 2) the MySQL tables may be updated to reflect the event. This database may mirror the SCP database. After the updates are committed (to the shared queue and DB) a successful response may be returned to the Data Distribution Hub Interface.

[00625] In embodiments, when the Data Distribution Hub add/delete business logic receives the "add" event from SCP, the hash may not be in the CPR table yet (on the first occurrence of the hash). When this happens, the Data Distribution Hub server may reply by rejecting the add and asking for the CPR to be included when the add is resent. When the Data Distribution Hub Interface receives the rejection, it may query the CPR from its CPR table and post a new "add" with both the hash and CPR. Since the CPR contains binary (non-printable) data, it may be encoded in, for example, base64 before it is transmitted within JSON. The Data Distribution Hub may also send a failure indication to Data Distribution Hub Interface to indicate a problem.

[00626] Tables associated with storage of CRNs and CPRs in a database may be stored on the Data Distribution Hub (in addition to SCP) to avoid a dependency on the SCP Oracle database, and to allow quick audits, and ease of new customer queue initialization. This may also allow SCP to be removed if a new interface is provided to the TFMP that the Data Distribution Hub can directly connect to.

[00627] In embodiments, information may be collected and stored that is related to tracking users (API Clients) that utilize the Data Distribution Hub service. The Data Distribution Hub may implement the pattern of a company, wherein multiple users may exist. Each user may be associated with an API client application and may be required to pass certification before the user will be able to access the production environment. To track company information, the Data Distribution Hub may implement a company database table. The Data Distribution Hub may also implement a user table. Each row in the company table may define a unique company and each user in the user table may contain a foreign key to exactly one row in the company table. Multiple users may map to a single company. A user status table may also exist that tracks information for a single user such as certification status and last audit/download time. Each row in the user status table may contain a foreign key to one row in the user table.

[00628] In embodiments, each Data Distribution Hub customer (aka client) may have a series of events to be downloaded that are identical events for all clients. Exceptions can be for queue initialization and CRN updates that result from an audit. Queues may be used to satisfy the clients' needs. While the Data Distribution Hub server may be using more than one queue, the client is unaware since the queues may be hidden from the client behind a single "logical" concept managed by the Data Distribution Hub API Business Logic. This means that as far as the client is concerned, events are being downloaded without any queue concept being required for the client to understand. Fig. 71 depicts this process for a single customer/client's sandbox or live data.

[00629] Figure 72 depicts a time-oriented interaction of the entities that may be involved in a queue operation.

[00630] Referring now to Fig. 73, an embodiment of a system 6500 for validating a telephone service request, also referred to herein simply as a “service request,” is shown. Embodiments of the system 6500 may provide for “A-Level”, “B-Level” and/or “C-Level” attestation by one or more telecommunication entities, e.g., service providers. In embodiments, A-Level attestation by an entity may indicate that the entity has authenticated a calling party and attests that the calling party is authorized to use one or more calling numbers. As will be appreciated, A-Level attestation may provide an enterprise with the ability to improve its brand trust in the marketplace and/or improve the number of successful completed outbound calls. In embodiments where the attesting entity is an originating service provider (OSP), the OSP may be required to check that the following conditions have been satisfied: 1) the OSP is responsible for the origination of the call into an IP-based service provider network; 2) the OSP has a direct authenticated relationship with the customer and can identify the customer; and 3) the OSP has established a verified association with the calling telephone number. In embodiments, B-Level attestation by an entity may indicate that the entity has authenticated the call originating trunk group but may be unable to authenticate whether the call source is authorized to use the calling number. In embodiments, C-Level attestation by an entity may indicate that the entity has authenticated from where it received the call but may be unable to authenticate the call source. Embodiments of the current disclosure may provide for A-Level attestation by an OSP to an enterprise associated with the calling telephone number in scenarios where the telephone number service provider (TNSP) and the OSP are not the same entity, such as the typical case of a toll-free subscriber.

[00631] As will be understood, the system 6500 may be in accordance with and/or implement the Secure Telephony Identity Revisited (STIR) / Signature-based Handling of Asserted Information Using toKENs (SHAKEN) framework/suite of protocols and/or the service request may be a request for access to a service corresponding to a phone number. The service may be the completion of a phone call, transmission of a text message (e.g., Short Message Service (SMS) and/or Rich Communication Service (RCS)), Caller ID Name (CNAM), and/or authentication of the right to use a particular phone number. As shown in Fig. 73, the system 6500 may include a certificate repository 6510, an OSP 6512 and/or a terminating telephone service provider (TSP) 6514. As will be understood, upon receipt of a Session Initiation Protocol (SIP) invite/service request 6516 from a calling party 6518, the OSP 6512 may utilize an authentication service 6520 to check the following when determining how to attest the validity of: 1) the call source; and/or 2) the calling number. The OSP 6512 may then create a SIP header 6522 for the SIP invite 6516 which is then transmitted to the TSP 6514. The TSP 6514 may then transmit the SIP invite 6516 to a verification service 6524 which obtains a certificate 6526 from the certificate repository 6510 via a verification process. In embodiments, the certificate 6526 may be a delegated certificate. Upon receiving the certificate 6526, the TSP 6514 may then fulfill/complete the SIP invite 6516, e.g., complete a call to a called party 6528.

[00632] As will be understood, the certificate repository 6510 may be implemented as a computer database operated by an entity other than the calling party 6518, the OSP 6512, the TSP 6514, and/or the called party 6528. For example, as will be explained in greater detail below, in embodiments, the certificate repository 6510 may be operated by an enterprise validator.

[00633] Illustrated in Fig. 74 is another embodiment of a system 6600 for validating a telephone service request. As will be appreciated, the system 6600 may implement one or more of the features of the system 6500 shown in Fig. 73. Accordingly, in embodiments, the system 6600 may include a responsible organization (also referred to herein as a “RespOrg”) 6610, an enterprise validator 6612 a service provider 6614 and/or an enterprise 6616. While Fig. 74 depicts the system 6600 as having a RespOrg, it will be understood that, in embodiments, the system 6600 may include any type of entity that manages a number registration, e.g., an administrator of a local number. As will be explained in greater detail below, the enterprise validator 6612 validates the authority of the enterprise 6616 to request services from the service provider 6614 with respect to a telephone number. In embodiments, the enterprise validator 6612 may be uniquely positioned within the system 6500 such that it provides data for OSP authentication and/or attestation indications. In embodiments, the enterprise validator 6612 may provide such services via a scalable and/or authoritative embodiment that may be ATIS STIR/SHAKEN compliant.

[00634] In embodiments, the RespOrg 6610 may be an entity who has the authority to use and/or grant access to services for a phone number. For example, in embodiments, the RespOrg 6610 may be a company that maintains or owns the registration for individual toll-free telephone numbers in the distributed Service Management System/800 database and/or phone numbers in another registration system, including, but not limited to, databases within and/or associated with the TFMP. The services may include those discussed herein with respect to the system 6500.

[00635] In embodiments, the enterprise 6616 is an entity which has been granted the authority by the RespOrg 6610 to use one or more services for one or more numbers registered to the RespOrg 6610. For example, in embodiments, the enterprise 6616 may be an individual or organization who purchased and/or leased the right to use a phone number from a RespOrg 6610 to place phone calls, texts, or invoke other services on the phone number.

[00636] In embodiments, the service provider 6614 is the entity with the ability to provide, fully or in part, a requested service for a phone number (e.g., complete a requested phone call, send a text message, etc.). The service provider 6614 may be a single entity and/or include multiple entities, for example an OSP 6512 (such as in Fig. 73) and/or a TSP 6514 (such as in Fig. 73). In embodiments, the RespOrg 6510 may also be and/or form part of the service provider 6614.

[00637] In embodiments, the enterprise validator 6612 is the entity that maintains and/or has access to a phone number database 6618 (e.g., the TFN registry within and/or associated with the TFMP), that maintains registrations of phone numbers to RespOrgs 6610. As will be understood, the phone number database 6618 may include one or more data records 6620 that pair one or more phone numbers to one or more RespOrgs 6610. It will be understood that the phone number database 6618 may be implemented as a unitary server and/or across multiple servers. In embodiments, the database 6618 may be a fully managed and/or NOSQF database that may have an on-demand options so as to provide for flexibility and efficiencies. In embodiments, the database 6618 may be optimized for processing and/or predictable scaling. As will be understood, optimization of the database and/or accompanying models may be based on access patterns and/or the design of short keys, secondary indexes and/or global indexes. Non-limiting examples of such key access patterns are provided in the following tables.

[00638] Further, in embodiments, the database 6618 may be multiple databases, in other words, the data disclosed herein as being stored within database 6618 may, in embodiments, be stored in multiple databases.

[00639] In embodiments, various metrics and events emitted or produced by lambda circuits, API gateways, databases, and/or web access logs may be captured, e.g., via Datadog. The metrics may be monitored and used to generate alerts.

[00640] As will be further understood, while Fig. 74 depicts a single enterprise 6616, service provider 6614 and RespOrg 6610, embodiments of the disclosure may include multiple enterprises, service providers and/or RespOrgs.

[00641] Referring now to Figs. 74-76, embodiments of the system 6600 may operate in accordance with method 6700. For example, the RespOrg 6610 may desire to provide authority to one or more enterprises 6616 to utilize services on one or more phone numbers registered to the RespOrg 6610.

As such, the RespOrg 6610 may transmit 6710 an authentication code request 6622 to the enterprise validator 6612. In embodiments, the authentication code 6622 may identify the one or more phone numbers 6810 and/or one or more services 6812 that the RespOrg 6610 desires to grant the enterprise 6616 access to. In certain aspects, the authentication code request 6622 may originate with the enterprise 6616 and be forwarded to the enterprise validator 6612 by the RespOrg 6610. In such embodiments, the RespOrg 6610 may first validate that the authentication code request 6622 did, in fact, originate from an enterprise known to the RespOrg 6610. In embodiments, a phone number may have different authentication codes 6622 for different services, e.g., one code 6622 for SHAKEN/STIR and a different code 6622 for texting and smart services (TSS). In embodiments, the authentication code 6622 may expire after a certain date. In embodiments, authorization codes 6622 associated with a number may be invalidated if the number is spared or moved to a different RespOrg 6610.

[00642] Upon receipt 6712 of the authentication code request 6622, the enterprise validator 6612 may validate 6714 that the one or more phone numbers 6810 identified in the authentication code request 6622 are registered and/or owned by the RespOrg 6610 that sent, or otherwise corresponds to, the authentication code request 6622. As will be appreciated in embodiments, an authentication code request 6622 may be sent to the enterprise validator 6612 by an entity other than the RespOrg 6610 (e.g., an intermediate party). Upon validating 6714 that the identified one or more phone numbers 6810 are registered to the RespOrg 6610 corresponding to the authentication code request 6622, the enterprise validator 6612 may then generate 6716 an authentication code 6624 which is transmitted 6718 to the RespOrg 6610. The authentication code 6624 may be generated via a cryptographic hashing function (e.g., Message-Digest Algorithm Five (MD5), Secure Hash Algorithm (SHA)-O, SHA-1, SHA-2, SHA-3), and/or other suitable hashing functions and/or with other protection. In embodiments, the authentication code 6624 may be a passphrase assigned by either the RespOrg 6610, the service provider 6614 and/or the enterprise validator 6612. Upon receiving 6720 the authentication code 6624, the RespOrg 6610 may then transmit 6722 the authentication code 6624 to the enterprise 6616. In embodiments, an authentication code 6624 may have a one-to-many and/or a one-to-one correspondence with services and/or phone numbers. For example, a first authentication code may authorize multiple services on a single phone number, a second authentication code may authorize a single service on a single phone number, a third authentication code may authorize a single service on multiple phone numbers, and/or a fourth authentication code may authorize multiple services on multiple phone numbers.

[00643] Upon receiving 6724 the authentication code 6624, the enterprise 6616 may then transmit 6726 a service request 6626 to the service provider 6614. The service request 6626 may include the authentication code 6624, one or more requested services 6812 and/or one or more phone numbers 6810. After receiving 6728 the service request 6626, the service provider 6614 may then transmit 6730 a validation request 6628 to the enterprise validator 6612. In embodiments, the validation request 6628 may include the authentication code 6624 and identify the one or more phone numbers 6810 and/or the one or more requested services 6812 from the received service request 6626.

[00644] Upon receiving 6732 the validation request 6628, the enterprise validator 6612 may validate 6734 that the authentication code 6624 in the validation request 6628 matches the authentication code 6624 previously transmitted 6718 to the RespOrg 6610 by the enterprise validator 6612. In embodiments, the enterprise validator 6612 may have stored the generated 6716 authentication code 6624 in the phone number database 6618 (e.g., in the data record 6620). In other words, the enterprise validator 6612 may create a mapping of authentication codes 6624 to phone numbers 6810 and services 6812. Accordingly, validation 6734 may include verifying that the authentication code 6624 in the validation request 6628 corresponds to the phone numbers 6810 and/or the services 6812 identified by the validation request 6628 by querying the database 6618 and comparing the data in the validation request 6628 to the data in the data record 6620. In other words, in embodiments, the enterprise validator 6612 will check the service request 6626 against the information in the database 6618 to determine whether the RespOrg 6610 has granted the enterprise 6616 access to the requested service(s) on the identified phone number(s) 6810. After validating 6734 the authentication code 6624, the enterprise validator 6612 may then transmit 6736 an authentication message 6630 to the service provider 6614.

[00645] Responsive to receiving 6738 the authentication message 6630, the service provider 6614 may then provide 6740 the requested service to the enterprise 6616. As will be understood, in embodiments the authentication message 6630 may indicate whether or not the authentication code 6614 in the validation request 6628 provides authorization for the services 6812 on the identified phone numbers 6810. In such embodiments, the service provider 6614 may provide the services 6812 requested in the service request 6626 where the authentication code 6624 provided by the enterprise 6616 was validated 6734 as authorizing access to the requested services 6812 and deny access to the requested services 6812 where the provided authentication code 6624; was determined, as part of the validation process 6734, as not authorizing access to the requested services 6812; was not validated 6734 due to system and/or network connection issues; and/or where no authentication code 6624 is provided in the service request 6626. In certain aspects, the service provider 6614 may attest to the enterprise’s 6616 right to use the requested service(s) 6812 on the identified phone number(s) 6810. For example, in embodiments, the service provider 6614 may provide an indication to the recipient of the service request (e.g., a called party), that the enterprise 6616 (e.g., the calling party), is authorized to use the service on the calling phone number. Such an indication may be a text message, a symbol and/or other suitable method of conveying the attesting message to the recipient of the service request.

[00646] In embodiments, the authentication code request 6622 may be generated, and/or generally managed, via an electronic interface (e.g., a web portal that is associated with the TFMP), provided by the enterprise validator 6612. For example, the web portal may allow the RespOrg 6610, or another party with whom the RespOrg 6610 has shared its login credentials with, to view: currently live/active authentication codes 6624, such as authentication codes which are currently valid and provide access to services; and dead/inactive authentication codes 6624, such as authentication codes that are no longer valid (such as expired) and do not provide access to services. The electronic interface may also allow the RespOrg 6610 to request for the renewal of an authentication code 6624. For example, in embodiments, an authentication code 6624 stored in the record 6620 may have a defined life span, such as the period and/or length of time within which the authentication code 6624 is alive. As will be understood, renewing an authentication code means to extend the life span of the authentication code 6624. For example, on May 28, 2020, the electronic interface may indicate that a particular authentication code 6624 has a life span from January 1, 2020 to June 1, 2020 whereby renewing the activation code 6624 may extend the life span of the authentication code 6624 from June 1 , 2020 to December 1, 2020.

[00647] As will be understood, other periods and/or units of time may be used to manage the life span of an authentication code 6624. For example, in embodiments, the life span of an authentication code may be limited by number of uses (e.g., a one-time use by an enterprise; a five-time use, etc.). [00648] Further, while the electronic interface has been described above as a web portal, it is to be understood that in embodiments, other types of electronic interfaces may be employed. For example, in embodiments, the enterprise validator 6612 may provide an application programming interface (API) that provides access (which may be indirect and/or restricted) to the phone database 6618. As will be understood, restricted access to the phone database 6618 means access that has less permission than an “owner” of the database as the term is used by those of ordinary skill in the art; and indirect access to the phone database 6618 means that a request/query must be relayed through an intermediate party (e.g., through the enterprise validator 6612).

[00649] Further still, in embodiments, the status of an authentication code may be modified by events related to a change in registration of the phone number and/or a change in ownership of the RespOrg. For example, if a phone number is transferred from one RespOrg to another, or the ownership of a RespOrg changes, any corresponding activation codes may be temporarily (or permanently) deactivated/killed.

[00650] Certain embodiments of the systems and methods described herein, e.g., 6500 (Fig. 73) and 6600 (Fig. 74) may also provide for the prevention and/or mitigation of fraudulent and/or unwanted calls via Do Not Originate (DNO) features. For example, some embodiments may maintain one or more lists and/or other types of records identifying one or more telephone numbers which may be local numbers (TNs), toll-free numbers (TFNs) and/or other types of phone and/or messaging system numbers utilized in different telecommunication systems across the world. The DNO lists can then be used to take various actions, as described herein, to prevent the completion of calls originating from a number on a DNO list and/or to take other actions, e.g., penalize a carrier who did (or attempted) to route the call. [00651] Accordingly, embodiments of the systems and methods described herein may receive and/or have access to data sources for one or more of the following for both TNs and TFNs: country level numbering plan data inputs for routing; exchange level data, e.g., Local Exchange Routing Guide (LERG), inputs for both mobile and wireline exchanges; in country service provider assignment data; and/or line level porting data and disconnect data. Such embodiments may then utilize the data available from these sources to determine which phone numbers are unallocated and/or unassigned and therefore can be designated as belonging to one or more DNOs. In embodiments, the foregoing determination may be performed as a real-time automated process. Embodiments may have access to data sources identifying non-working numbers, closed codes, RespOrg Set TFNs, e.g., TFNs that have been set by a RespOrg as belonging on a DNO list as their intended use case does not include outbound dialing, unassigned codes and/or blocks of phone numbers, US Telecom DNO Numbers, Service provider set TNs, etc. As will be understood, embodiments of the systems and methods, described herein, may compile, generate, and/or maintain one or more DNO lists based on the data from the foregoing listed data sources and/or other types of data. In embodiments, an enterprise validator, e.g., 6612 (Fig. 74) may have access to the foregoing listed data sources and compile, generate, and/or maintain the one or more DNO lists. Thus, as will be appreciated, certain embodiments may take country level numbering plan data inputs for both toll and non-toll routing, exchange level data inputs for both mobile and wireline exchanges, in country service provider assignment data, line level porting data and disconnect data for use in a real-time automated process to determine which phone numbers are unallocated and/or unassigned and therefore can be designated as phone numbers that do not originate phone calls.

[00652] In embodiments, a DNO list for TNs may be generated based at least in part on the following relationship:

(All Available [Allocated] TNs - Codes Assigned - TNs/Blocks in Use) + All Currently Disconnected TNs = UnAllocated TNs wherein All Available TNs is the grouping of all TNs that are available in a telecommunication system, Codes Assigned is the grouping of TNs in the telecommunication system for which routing codes (or other properties) have been assigned, TNs/Blocks in Use is the grouping of TNs within the telecommunication system known to be in use, and All Currently Disconnected TNs is the grouping of all TNs in the telecommunication system known to be disconnected. As can be seen above, in such embodiments, a DNO list may include the group of unallocated and/or unassigned TNs which can be determined by subtracting the group of TNs which are currently in use and the group of TNs which have been assigned from all available TNs and adding in the group of all disconnected TNs, which are assumed to be included in the DNO list by default as, generally, no calls should be initiated from disconnected numbers. Thus, embodiments of the current disclosure may generate a DNO list of TNs by subtracting out TNs, that are known to either be in use or assigned/allocated to an entity or individual, from a known baseline of TNs, e.g., all the TNs in a particular network, while adding back in TNs known to be unallocated or not in use. As will be appreciated, embodiments of the current disclosure for determining a DNO list for TNs may be utilized in the US and/or Canadian telecommunication networks, e.g., phone networks, and/or in any other telecommunication network across the globe. As such, embodiments of the current disclosure may provide for the generation of a global DNO list for TNs.

[00653] With respect to TFNs, in embodiments, a DNO list for TFNs may be generated based at least in part on the following relationship:

All Available TFNs - As signed/ Allocated TFNs - Reserved TFNs + Spared/Disconnected TFNs = Unallocated/Unassigned TFNs As can be seen above, in such embodiments, a DNO list may include the group of unallocated and/or unassigned TFNs which can be determined by subtracting the group of assigned/allocated TFNs, e.g., numbers that are available for use by a RespOrg, and the group of reserved TFNs from the group of all available TFNs in a network, and adding in the group of all spared, e.g., numbers returned to available status by a RespOrg, and/or disconnected TFNs, which are assumed to be included in the DNO list by default as these numbers should not be in use. Thus, similar to the generation of a DNO list for TNs, as disclosed herein, embodiments of the current disclosure may generate a DNO list of TFNs by subtracting out TFNs, that are known to either be in use or assigned/allocated to an entity or individual, from a known baseline of TFNs, e.g., all the TFNs in a particular network, while adding back in TFNs known to be unallocated or not in use. As will be appreciated, embodiments of the current disclosure for determining a DNO list for TFNs may be utilized in the US and/or Canadian telecommunication networks, e.g., phone networks, and/or in any other telecommunication network across the globe.

[00654] In embodiments, a DNO list may include numbers, e.g., TNs and/or TFNs, which are intended to only receive inbound calls. Embodiments may also provide for the automatic inclusion and/or exclusion of numbers into and out of a DNO list, e.g., via one or more processes based in part on the above relationships. Embodiments may also provide for manual inclusion and/or exclusion of numbers into and out of a DNO list.

[00655] In embodiments, telecommunication identifiers, e.g., numbers, on a DNO list, as described herein, may be tagged in a database with a tag indicating that such telecommunication identifiers are not to originate calls. Non-limiting examples of tagging include setting a data field in a database record storing a telecommunication identifier and/or in a lookup table associated with the telecommunication identifier. In embodiments, numbers may be tagged to indicate that they should not originate calls from outside a particular region, e.g., the United States, Canada, North America, Europe, etc. For example, telecommunication identifiers in a database may be tagged to indicate that they should not originate telecommunications traffic outside of the United States. As will be appreciated, the tagging of such telecommunication identifiers may assist in reducing fraudulent telecommunications traffic, e.g., fraudulent calls, from outside one or more geographic regions, e.g., the United States. For example, the tagging of telecommunication identifiers to indicate that they should not originate traffic from outside the United States may provide for the identification of fraudulent, or likely fraudulent, telecommunications traffic by a switch and/or other telecommunications traffic handling device.

[00656] In embodiments, a DNO list may be used by one or more switches within a call routing network to prevent completion of calls initiated by numbers on the DNO list. For example, a switch may decide to not forward/route a call from an originating number on the DNO list and/or to route the call away from the original intended recipient, e.g., the switch may route the call to a honeypot network. In such embodiments, the switch may be preprogrammed with one or more DNO lists and/or send queries to an entity, e.g., the enterprise validator that manages a DNO list.

[00657] In embodiments, a DNO list may be used after the completion of a call, that originated from a number on a DNO list, to identify one or more carriers (and/or other entities) who initiated, routed, and/or completed the call. The identified carriers may then be penalized, e.g., fined, for failing to prevent completion of the call despite the original number being included on the DNO list. As will be appreciated, such penalization may incentivize carriers (and/or other entities) to utilize the DNO list (or other measures) to reduce the amount of fraudulent calls.

[00658] As will be understood, in embodiments, the RespOrg 6610, enterprise 6616, service provider 6614 and/or the enterprise validator 6612 may communicate with one another, as disclosed herein, via one or more networkable computing devices. Such communications may occur over private and/or public networks (e.g., intranets and/or the Internet). The networks may be circuit based and/or packet switching based.

[00659] As will be appreciated, by requiring an enterprise to provide an authentication code in order to access a service for a phone number, some embodiments of the disclosure mitigate the likelihood of unauthorized use of the phone number and/or corresponding services. In other words, some embodiments of the disclosure reduce the likelihood of a phone number being used in a spoofing attack by a malicious actor. Accordingly, some embodiments of the disclosure improve the trust relationship between a call recipient and the call source (e.g., an enterprise), thereby increasing the likelihood that the call recipient will respond to a service, such as a call or text message, initiated by the call source.

[00660] Further, by providing for the coordination and exchange of authentication codes among RespOrgs, enterprises and service providers in some embodiments of the disclosure may provide for full attestation (A-Level) and/or partial attestation (B-Level) under the SHAKEN/STIR framework. For example, validation 6734 of the authentication code 6624 provided in the service request 6626 may allow the service provider 6614 to confidently attest that the enterprise 6616 has been authorized by the RespOrg 6610 to use the requested phone number. Accordingly, embodiments of the disclosure may provide for the service provider 6614 to: assume responsibility for the origination of a call (or other service request); provide a direct relationship with the customer (e.g., the enterprise 6616), that allows for the identification of the customer; and/or verify an established association with the requested phone number and the call (service).

[00661] Further still, by using an authentication code to control access to a service on a phone number, some embodiments of the disclosure may provide for the ability of a RespOrg to easily hire/spin up enterprises (e.g., contracting third parties) during marketing campaigns; and, upon completion of the marketing campaign, provide for the RespOrg to quickly revoke the right of the enterprises to use the phone numbers.

[00662] Embodiments of the disclosure may also provide for and/or supplement a Do Not Originate Registry (DNO), e.g., the database 6618 operated by the enterprise validator 6612 may serve as a DNO. For example, in embodiments, service requests 6516 that fail one or more of the authentication checks described herein, e.g., via the authentication service 6520, may not be provided the requested service. Thus, as will be appreciated, embodiments of the current disclosure may provide for an improved DNO registry with improved accuracy and/or confidence by relying on RespOrgs 6610 and/or service providers 6614 to set DNO on their numbers. Embodiments of the current disclosure may also provide for auto-set DNO registries where unassigned, spare and/or disconnected numbers are not provided requested services. Embodiments of the current disclosure may also provide for manual control over a DNO registry wherein in-bound numbers are published to the registry to allow subscribers of the registry to quickly spot fraud.

[00663] As will be further appreciated, embodiments of the current disclosure may bridge the attestation gap in scenarios where an entity has third-party call centers that use the entity’s telephone number, in scenarios where an entity has several carriers but just one telephone number, e.g., a toll- free number, and/or where an entity may be required to provide A-Level attestation. [00664] Embodiments of the current disclosure may provide for interaction with and/or management of the records 6620 in the database 6618 (Fig. 74) via a graphical user interface, e.g., a web interface, and/or via one or more application programing interfaces. In embodiments, the graphical user interface and/or the APIs may be provided by the enterprise validator 6612 (Fig. 74). In such embodiments, the graphical user interface and/or the APIs may be integrated with a TFN registry which may be managed by the enterprise validator 6612. The TFN registry may manage the RespOrgs 6610 as described herein. In embodiments, the RespOrgs 6610 may delegate request 6622 of the authentication code 6624 to one or more delegated code requestors, e.g., OSPs. In such embodiments, the graphical user interface and/or the APIs may provide for management of the delegated code requestors. In embodiments, the enterprise validator 6612 may provide a subscriber verification service that allows service providers and/or other third parties to verify a number/service/authentication code combination. Such verification may be provided in real-time (or near real-time). In embodiments, the enterprise validator 6612 may provide for service providers to cache local copies of the verification results. In embodiments, the cached verification results may not include the authentication codes 6622.

[00665] Referring now to Fig. 77, another embodiment of a system 7700 for validating a telephone service request is shown, in accordance with the current disclosure. The system 7700 includes a RespOrg 7712, an enterprise customer 7714, an OSP 7716 and an enterprise validator 7718. The enterprise customer 7714 may request a SHAKEN/STIR attestation for a telephone number, e.g., a TFN, from the OSP 7716. The OSP 7716 may then instruct the enterprise customer 7714 to initiate number verification by getting an authentication code from the enterprise validator 7718 via the RespOrg 7712. the enterprise customer 7714 may then request the RespOrg 7712 to get an authentication code for the number they wish to use a service on. The RespOrg 7712 then relays the request to the enterprise validator 7718. The enterprise validator 7718 verifies that the number is registered and identifies the RespOrg of record. If the number is registered to the RespOrg 7712, then the enterprise validator 7718 sends the authentication code to the RespOrg 7712 who then relays the authentication code to the enterprise customer 7714. The enterprise customer 7714 then provides the authentication code to the OSP 7716. The OSP 7716 may then verify the authentication code with the enterprise validator 7718. If the provided authentication code is verified, then the OSP 7716 may attest 7720 to the enterprise customer’s 7714 right to use one or more services on the number. [00666] Turning to Fig. 78, a system 7800 for delegated authentication code generation is shown. The system includes a letter of authorization (FOA) management circuit 7812, a request intake circuit 7814, a number lookup and mapping circuit 7816, an email RespOrg mapping circuit 7818, and/or an approval/rejection user interface 7820. In embodiments, a delegated code requestor 7822 may request permission from the LOA management circuit 7812 to upload a LOA. The LOA management circuit 7812 may then send a document ID and upload link to the delegated code requestor 7822. Upon receipt of the document ID and upload link, the delegated code requestor 7822 may proceed to upload an LOA to the LOA management circuit 7812. In embodiments, the request intake circuit 7814 may provide number lookup services via the number lookup and mapping circuit 7816. The request intake circuit 7814 may also provide email to RespOrgs and/or to the operator of a TFN registry via the email RespOrg mapping circuit 7818, which may include one or more mappings of RespOrgs to registered numbers and/or e-mail addresses. In embodiments, the uploaded LOA may correspond to TFNs for RespOrgs 7824, emails for local number administrators 7826, and/or local number code managers 7828. In embodiments, the approval/rejection user interface 7820 may provide for the delegated code requestor 7822 to request the status of TFNs 7824, emails 7826 and/or local numbers 7828 via a status request 7830.

[00667] Turning now to Fig. 79, an example of an LOA upload by a delegated code requestor is shown. In embodiments, a delegated code requestor 7912 may request to upload an LOA via a LOA management platform 7914. The LOA management platform 7914 may include a web application firewall (WAF) 7916, an API gateway 7918, a serverless compute service 7920, e.g., AWS Lambda, and a user management API 7822, e.g., Amazon Cognito. In response to the request to upload a LOA, the LOA management platform 7914 may transmit an upload link to the delegated code requestor 7912 which may direct the delegated code requestor 7912 to a location 7926, e.g., a bucket, for uploading the LOA. In embodiments, a bucket may be a location in memory where related LOAs can be stored.

[00668] Illustrated in Fig. 80 is an example of a LOA request being transmitted to a RespOrg or administrator. A delegated code requestor 8012 may send a LOA request to a WAF 8014 that passes it to an API gateway 8016 which may communicate with a user management API 8018. The API gateway 8016 may then send the request to a request circuit 8020 that verifies the request via a bucket 8022 and forwards the request to a database 8024 that may then stream data 8026 to one or more processing circuits 8028, 8030 and/or 8032 that generate an email notification that is sent via an email server 8034 to at least one corresponding RespOrg 8036, 8038 and/or an administrator 8040.

[00669] Shown in Fig. 81 is an example of a get status request executed by an embodiment of an LOA management platform 8112. A delegated code requestor 8114 may send a status request for a number to a WAF 8116 that passes the request to an API gateway 8118. The API gateway 8118 may communicate with a user management API 8120. The API gateway 8118 may send the request to a processing circuit 8122 that interacts with one or more databases 8124 and/or 8126 that return the status of the requested number to the dedicated code requestor 8114.

[00670] Turning to Fig. 82, an example of an approval/rejection of one or more numbers is shown.

A RespOrg 8210 may login to an approval/rejection user interface 8214 that may, in turn, communicate with a TFN registry 8216 to open a session and generate a security token. The approval/rejection user interface 8214 may then communicate with an API gateway 8216 through a WAF 8218. The API gateway 8216 may then provide access to an update status circuit 8220 that communicates with a LOA bucket 8222 and/or a database 8224 to determine a status of one or more numbers and/or to update the status of the one or more numbers.

[00671] Shown in Fig. 83 is an example of a request to generate and/or retrieve an authentication code. In embodiments, a RespOrg 8310 may initiate a session with a TFN registry 8312 that provides the RespOrg 8310 with a security token. The RespOrg 8310 may then communicate with an API gateway 8314 through a WAF 8316. The API gateway 8314 may provide access to a first process 8317 for generating an authentication code and/or a second process 8318 for retrieving an authentication code from a database 8320. The processes 8317 and/or 8318 may also communicate with a TFN authentication service 8322.

[00672] Referring now to Fig. 84, an example of verification of a number is shown. A verifying entity 8412 may communicate with an API gateway 8414 (of enterprise validator 8416) through a WAF 8418. The API gateway 8414 may provide access to a verify number circuit 8420 that communicates with a database 8422 to verify the number.

[00673] Fig. 85 depicts an example submission request for generation and/or regeneration of a number authentication code, e.g., a local number. A manager and/or administrator 8512 of a local number may communicate with an API gateway 8514 through a WAF 8516. The API gateway 8514 may be in communication with a user management API 8518 and provide access to a code generation circuit 8520 that generates an authentication code and pairs it to a number in a database 8522. In embodiments, the code generation circuit 8520 may be in communication with one or more circuits 8524 that provide services to and/or from third party entities, e.g., number administrators·

For example, the code generation circuit 8520 may use the one or more circuits 8524 to retrieve a number for pairing to the authentication code.

[00674] As shown in Fig. 86, embodiments of the current disclosure may provide for batching of DNO lists. For example, one or more users 8612 may generate a batch file 8614 for inserting/adding numbers for inclusion in a DNO registry. The batch file 8614 may be uploaded through a user interface 8616 to a system 8618 that coverts that batch file 8614 to a JavaScript Object Notation (JSON) file that is received by a batch API 8619. The batch API 8619 creates a batch header 8620 and a batch simple queue service (SQS) message 8622. A SQS lambda service 8624 then picks up the SQS message 8622 and splits it into partial batches for processing, wherein the processed partial messages are placed back on the same SQS queue. The partial messages may also be picked up by the SQS batch lambda service 8624 for processing. Local numbers may be validated through a third- party service and/or TFNs may be validated through a TFN registry 8626. Completed database entries may be written to a batch table 8628 and a number table 8630. Upon completion of the final partial batch, the batch header database entry is updated with the final counts and status.

[00675] Referring to Fig. 87, a method 87100 for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure, is provided. The method 87100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 87100 may include interpreting telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers 87112. The method 87100 may further include generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers 87114. The method 87100 may further include transmitting the list 87116. In embodiments, the telecommunication identifiers in the list may be local telephone numbers. In embodiments, the local telephone numbers may be for the United States, Canada, and/or any other country and/or telecommunication system. The method 87100 may further include indicating that the telecommunication identifiers in the list should not originate a telecommunication message 87118. Indicating that the telecommunication identifiers in the list should not originate a telecommunication message may include at least one of setting a data field associated with the list 87120; and/or generating a message apart from the list 87122, e.g., a separate data packet and/or other electronic communication structured to convey that the telecommunication identifiers included in the list should not be originating telecommunication messages. The telecommunication messages may be at least one of a text message, a voice call, a video call, an e-mail, or the like. Generating the list based at least in part on the telecommunications data may include removing the assigned telecommunication identifiers and/or the in-use telecommunication identifiers from the available telecommunication identifiers 87124. Generating the list based at least in part on the telecommunications data may further include including the disconnected telecommunication identifiers 87126. In embodiments, the list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers. The list may further include the disconnected telecommunication identifiers. [00676] Referring to Fig. 88, another method 88100 for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure, is provided. The method 88100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 88100 may include interpreting telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers 88112. The method 88100 may further include generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers 88114. The method 88100 may further include transmitting the list 88116. In embodiments, the telecommunication identifiers in the list may be toll-free numbers. The toll-free numbers may be for the United States, Canada, and/or any other country and/or telecommunication system. The method 88100 may further include indicating that the telecommunication identifiers in the list should not originate telecommunication messages 88118. Indicating that the telecommunication identifiers in the list should not originate telecommunication messages may include at least one of setting a data field associated with the list 88120; and/or generating a message apart from the list 88122. Generating the list based at least in part on the telecommunications data may include removing the assigned telecommunication identifiers and/or the reserved telecommunication identifiers from the available telecommunication identifiers 88124. Generating the list based at least in part on the telecommunications data may further include including the disconnected telecommunication identifiers 88126. In embodiments, the list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers. The list may further include the disconnected telecommunication identifiers.

[00677] Referring to Fig. 89, an apparatus 89100 for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure, in provided. The apparatus 89100 may include a telecommunications data processing circuit 89102, a list generating circuit 89104, and a list provisioning circuit 89106. The telecommunications data processing circuit 89102 may be structured to interpret telecommunications data 89108 including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and/or disconnected telecommunication identifiers. The list generating circuit 89104 may be structured to generate a list 89110 based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers 89112 that are a subset of the available telecommunication identifiers. The list provisioning circuit 89106 may be structured to transmit the list 89110. In embodiments, the list 89110 includes a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers. The list 89110 may further include the disconnected telecommunication identifiers.

[00678] Referring to Fig. 90, another apparatus 90100 for generating a list of telecommunication identifiers, in accordance with embodiments of the current disclosure, is provided. The apparatus 90100 may include a telecommunications data processing circuit 90102, a list generating circuit 90104, and a list provisioning circuit 90106. The telecommunications data processing circuit 90102 may be structured to interpret telecommunications data 90108 including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The list generating circuit 90104 may be structured to generate a list 90110 based at least in part on the telecommunications data. In embodiments, the list includes telecommunication identifiers 90112 that are a subset of the available telecommunication identifiers. The list provisioning circuit 90106 may be structured to transmit the list 90110. In embodiments, list 90110 includes a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers. The list 90110 may further include the disconnected telecommunication identifiers.

[00679] Referring to Fig. 91, a method 91100 for routing a telecommunication message, in accordance with embodiments of the current disclosure, is provided. The method 91100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 91100 may include interpreting a list generated based at least in part on telecommunications data 91112. The telecommunications data may include available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The list may also include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method 91100 may further include determining whether to route a telecommunications message based at least in part on the list 91114. In embodiments, telecommunication identifiers in the list may be local telephone numbers. In embodiments, the local telephone numbers may be for the United States, Canada, and/or any other country.

[00680] Referring to Fig. 92, another method 92100 for routing a telecommunication message, in accordance with embodiments of the current disclosure, is provided. The method 92100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 92100 may include interpreting a list generated based at least in part on telecommunications data 92112. The telecommunications data may include available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. In embodiments, the list may include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method 92100 may further include determining whether to route a telecommunications message based at least in part on the list 92114. In embodiments, telecommunication identifiers in the list may be toll-free numbers.

[00681] Referring to Fig. 93, a method 93100 for mitigating telecommunications fraud, in accordance with embodiments of the current disclosure is provided. The method 93100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 93100 may include identifying an entity that routed a telecommunications message that originated from a telecommunication identifier on a list 93112. The list may include a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between available telecommunication identifiers and in-use telecommunication identifiers. The method 93100 may further include penalizing the entity 93114. In embodiments, penalizing the entity includes at least one of: generating a message indicating that the entity should be fined 93116; charging the entity a fee 93118; and/or any other type of action structured to incentivize the entity to not route telecommunications messages originating from a telecommunication identifier on the list.

In embodiments, the telecommunication identifiers in the list may be local telephone numbers. In embodiments, the local telephone numbers may be for the United States, Canada, and/or any other country.

[00682] Referring to Fig. 94, another method 94100 for mitigating telecommunications fraud, in accordance with embodiments of the current disclosure, is provided. The method 94100 may be performed by any of the apparatuses and/or other computing devices described herein. The method 94100 may include identifying an entity that routed a telecommunications message that originated from a telecommunication identifier on a list 94112. In embodiments, the list may include a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and reserved telecommunication identifiers. The method 94100 may further include penalizing 94114 the entity. In embodiments, penalizing the entity may include at least one of: generating a message indicating that the entity should be fined 94116; charging the entity a fee 94118; and/or any other type of action structured to incentivize the entity to not route telecommunications messages originating from a telecommunication identifier on the list. In embodiments, the telecommunication identifiers in the list may be toll-free numbers. [00683] Embodiments of the current disclosure may provide for a system for validating a telephone service request. The system includes a phone number database and a controller. The phone number database includes a data record that pairs a managing entity to a phone number. The controller communicates with the phone number database and is operative to: receive an authentication code request corresponding to the managing entity and identifying the phone number; validate the phone number is registered to the managing entity via querying the phone number database; responsive to validating the phone number is registered to the managing entity, generate an authentication code corresponding to the phone number; and transmit the authentication code. In certain embodiments, the controller is further operative to: store the generated authentication code in the data record; receive a validation request corresponding to a service provider, the validation request including an authentication code; validate that the authentication code in the validation request matches the authentication code stored in the data record via querying the phone number database; and responsive to validating that the authentication code in the validation request matches the authentication code in the data record, transmit an authentication message. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM. In certain embodiments, the validation request identifies one or more services corresponding to the phone number; and the authentication message indicates the authentication code in the validation request provides access to the one or more services. In certain embodiments, the managing entity is a local number administrator· In certain embodiments, the managing entity is a Responsible Organization. In certain embodiments, the phone number database is a number registry. In certain embodiments, the number registry is a toll-free number registry.

[00684] Embodiments of the current disclosure may provide for a method for validating a telephone service request. The method includes receiving, from a managing entity, an authentication code request that identifies a phone number; and validating that the phone number is registered to the managing entity via querying a phone number database including a data record that pairs the managing entity to the phone number. The method further includes: responsive to validating that the phone number is registered to the managing entity, generating an authentication code corresponding to the phone number; and transmitting the authentication code to the managing entity. In certain embodiments, the method further includes: storing the generated authentication code in the data record; receiving, from a service provider, a validation request, that includes an authentication code; validating that the authentication code in the validation request matches the authentication code stored in the data record; and responsive to validating that the authentication code in the validation request matches the authentication code stored in the data record, transmitting an authentication message to the service provider. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM. In certain embodiments, the validation request identifies one or more services corresponding to the phone number; and the authentication message indicates the authentication code in the validation request provides access to the one or more services. In certain embodiments, the managing entity is a local number administrator. In certain embodiments, the managing entity is a Responsible Organization. In certain embodiments, the phone number database is a number registry. In certain embodiments, the number registry is a toll-free number registry.

[00685] Embodiments of the current disclosure may provide for a non-transitory computer-readable medium storing instructions. The stored instructions adapt at least one processor to: receive, from a managing entity, an authentication code request that identifies a phone number; and validate that the phone number is registered to the managing entity via querying a phone number database including a data record that pairs the managing entity to the phone number. The stored instructions further adapt the at least one processor to, responsive to validating that the phone number is registered to the managing entity, generate an authentication code corresponding to the phone number; and transmit the authentication code to the managing entity. In certain embodiments, the stored instructions further adapt the at least one processor to: store the generated authentication code in the data record; receive, from a service provider, a validation request, that includes an authentication code; validate that the authentication code in the validation request matches the authentication code stored in the data record; and responsive to validating that the authentication code in the validation request matches the authentication code stored in the data record, transmit an authentication message to the service provider. In certain embodiments, the authentication message indicates the authentication code in the validation request authorizes access to one or more services corresponding to the phone number. In certain embodiments, the one or more services include: a call request; SMS; RCS; and/or CNAM.

[00686] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller in communication with an enterprise validation server and operative to: transmit an authentication code request to the validation server, the authentication code request identifying a phone number; receive an authentication code from the enterprise validation server; and transmit the authentication code. In certain embodiments, the controller is further operative to: receive the authentication code request prior to transmitting the authentication code request to the validation server. [00687] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes transmitting an authentication code request to an enterprise validator, the authentication code request identifying a phone number. The method further includes receiving an authentication code from the enterprise validator; and transmitting the authentication code to an enterprise. In certain embodiments, the method further includes receiving the authentication code request from an enterprise prior to transmitting the authentication code request to the enterprise validator.

[00688] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller operative to: receive an authentication code corresponding to a phone number; and transmit a service request to a service provider server, the service request including the authentication code and identifying a service corresponding to the phone number. In certain embodiments, the controller is further operative to transmit, to a responsible organization server, an authentication code request identifying the phone number; and the authentication code is received from the responsible organization server. In certain embodiments, the service is: a call request; SMS; RCS; and/or CNAM.

[00689] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes: receiving, from a responsible organization, an authentication code corresponding to a phone number; and transmitting, to a service provider, a service request that includes the authentication code and identifies a service corresponding to the phone number. In certain embodiments, the method further includes transmitting, to a responsible organization, an authentication code request identifying the phone number. In certain embodiments, the service is: a call request; SMS; RCS; and/or CNAM.

[00690] Embodiments of the current disclosure may provide for another system for validating a telephone service request. The system includes a controller in communication with an enterprise validation server and operative to: receive a service request corresponding to an enterprise, the service request including an authentication code and identifying a service and a phone number; transmit a validation request to the enterprise validation server, the validation request including the authentication code and identifying the phone number; and receive an authentication message from the enterprise validation server. Upon receipt of the authentication message, the controller provides the service to the enterprise for the phone number. In certain embodiments, the validation request further identifies the service. In certain embodiments, the authentication message indicates the enterprise is authorized to access the service for the identified phone number.

[00691] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes receiving, from an enterprise, a service request that includes an authentication code and identifies a service corresponding to a phone number; transmitting, to an enterprise validator, a validation request that includes the authentication code and identifies the phone number; receiving an authentication message from the enterprise validator; and responsive to receiving the authentication message, providing the service to the enterprise for the phone number. In certain embodiments, the validation request further identifies the service. In certain embodiments, the authentication message indicates the enterprise is authorized to access the service for the identified phone number.

[00692] Embodiments of the current disclosure may provide for another method for validating a telephone service request. The method includes transmitting, by a responsible organization to an enterprise validator, an authentication code request that identifies a phone number; and upon receiving the authentication code request at the enterprise validator, validating, by the enterprise validator, that the phone number is registered to the responsible organization via querying a phone number database. The method further includes responsive to validating that the phone number is registered to the responsible organization, generating, by the enterprise validator, an authentication code corresponding to the phone number. The method further includes transmitting, by the enterprise validator, the authentication code to the responsible organization; storing, by the enterprise validator, the generated authentication code in the phone number database; and transmitting, by the responsible organization, the authentication code to an enterprise. The method further includes upon receiving the authentication code at the enterprise, transmitting, by the enterprise to a service provider, a service request including the authentication code and identifying a service corresponding to the phone number. The method further includes upon receiving the service request at the service provider, transmitting, by the service provider to the enterprise validator, a validation request including the authentication code and identifying the phone number. The method further includes upon receiving the validation request at the enterprise validator, validating, by the enterprise validator via querying the phone number database, that the authentication code in the validation request matches the authentication code stored in the phone number database. The method further includes responsive to validating that the authentication code in the validation request matches the authentication code stored in the phone number database, transmitting, by the enterprise validator to the service provider, and authentication message; and in response to receiving the authentication message at the service provider, providing, via the service provider, a service to the enterprise for the phone number.

[00693] A method according to one disclosed non-limiting embodiment of the present disclosure may include a web-based interface adapted to communicate with a toll-free telecommunications management platform and a toll-free network operator platform; at least one processor in communication with the toll-free telecommunications management platform, wherein the web-based interface is adapted to transmit a command to the at least one processor; a database associated with the toll-free telecommunications management platform, wherein the database contains call routing data that is associated with the toll-free network operator platform; and [00694] an activation mechanism within the web-based interface, the activation mechanism programmed to generate the command, wherein the command is to at least update the database by appending IP address data to the call routing data.

[00695] In embodiments, an activate request may be received from a user, through a web-based interface, wherein the request includes at least a customer record template reference and an indication of when to activate a toll-free telecommunications number associated with the request.

An add request may be received from the user, through the web-based interface, wherein the add request includes at least one IP address datum associated with the toll-free telecommunications number. A customer record template may be updated and a call routing table with the at least one IP address based at least in part on the received add request, wherein the call routing table is associated with the toll-free telecommunications number, and the update stored in a database that is associated with a toll-free telecommunications management. A call routing table may be configured to include multiple carriers. A call routing table may be configured to have at least one rule pertaining to the proximity of a caller to an entity associated with the toll-free number. A rule may be shared with a service provider and/or integrated within a call routing template. In embodiments, the web-based interface may be designed to operate on a mobile device, including but not limited to a smart phone. [00696] In embodiments, a toll-free call route trend may be identified among a plurality of toll-free calls taking place within a toll-free network operator platform; wherein the call route trend is identified at least in part by call routings among toll-free numbers sharing an attribute. The toll-free network operator platform may be notified of the trend, an entity identified using at least one toll- free number with the shared attribute from among the entities using the toll-free network operator platform. An add request may be received through a web-based interface, wherein the add request includes at least one IP address datum associated with the entity and at least one toll-free number sharing the attribute, and a call route template update created for use in directing calls to the at least one toll-free number sharing the attribute, wherein the call routing template update includes the at least one IP address datum. In embodiments, an entity may be a carrier, a call center, a service control point, or some other type of entity. An attribute may be an originating state, a geographic region, an area code, a telecommunications carrier, or some other type of attribute. In embodiments, calls may be directed based at least in part on a call routing preference associated with an entity. A call routing preference may be stored in a call routing template. Call routing preference may vary based at least in part on the attribute.

[00697] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving a one-click activate request from a user, wherein the request includes at least a customer record template reference and an indication of when to active a toll-free number associated with the request; searching a responsible organization record to determine the presence of a defined customer template record relating to the user request, wherein the responsible organization is associated with toll-free telecommunications; retrieving at least one customer template record, wherein the customer template record is a defined customer template record for the responsible organization; and activating the user request, wherein the activation includes at least one of activating or reserving the toll-free number.

[00698] A further embodiment of the present disclosure may include that the one-click activate request is received from a widget that is operable on a client device.

[00699] A further embodiment of the present disclosure may include that the at least one customer template record includes call path data derived at least in part from a predictive analytics engine. [00700] A further embodiment of the present disclosure may include that the activation of the user request creates a toll-free service provider identifier (TSPID) that is associated with the user.

[00701] A method according to one disclosed non-limiting embodiment of the present disclosure can include creating at least two toll-free call routing tables based on a congestion threshold criterion, wherein the first of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are below the congestion threshold, and the second of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are equal to or above the congestion threshold; providing the call routing tables to at least one service control point that is associated with the toll- free telecommunications carrier network; monitoring toll-free call volumes and durations occurring within a toll-free telecommunications carrier network; receiving at least one of a call count datum or call duration datum from the toll-free telecommunications carrier network wherein the call count datum or call duration datum indicates a change in call volumes over the toll-free telecommunications carrier network from below the congestion threshold to above the congestion threshold; and instructing the service control point to switch from using the first call routing table to the second call routing table.

[00702] A further embodiment of the present disclosure may include that the switch from the first call routing table to the second call routing table is based at least in part on the receipt of an abuse report associated with toll-free number within the toll-free telecommunications carrier network. [00703] A further embodiment of the present disclosure may include that the call volume is expressed as a percentage of the total call volume occurring over the network.

[00704] A further embodiment of the present disclosure may include that the call volume is specific to an entity.

[00705] A further embodiment of the present disclosure may include that the switch to the second call routing table is automated and occurs in real time.

[00706] A further embodiment of the present disclosure may include that decision nodes of the first and second call routing tables are loaded into the service control point.

[00707] A further embodiment of the present disclosure may include that the call volumes are used to create a call path score for a possible call route path that is available on the network.

[00708] A further embodiment of the present disclosure may include that the call path score is based at least in part on a call travel distance estimate.

[00709] A further embodiment of the present disclosure may include that the call path score is based at least in part on a call travel speed estimate.

[00710] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving data relating to toll-free number call activity from a toll-free telecommunications system, wherein the data includes at least one of call duration or call count data; receiving third party data relating to macroeconomic activity; modeling at least one of call duration or call count data with the third party data to derive a macroeconomic trend; receiving a request from a client device to present the macroeconomic trend; and presenting a representation of the macroeconomic trend to a user interface on the client device.

[00711] A further embodiment of the present disclosure may include that the presentation of the macroeconomic trend is presented to the user interface in conjunction with a sponsored content. [00712] A further embodiment of the present disclosure may include that the third party data is stock market data.

[00713] A further embodiment of the present disclosure may include that the third party data is Bloomberg TM data.

[00714] A further embodiment of the present disclosure may include that the third party data is government data.

[00715] A further embodiment of the present disclosure may include that the third party data is social media data.

[00716] A further embodiment of the present disclosure may include that there is a temporal delay between the time of the request and the time of the presentation of long enough duration that the client device enters a sleep mode as regards the interaction, and the client device is activated out of sleep mode upon the presentation.

[00717] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving a one-click activate request from a user, wherein the request includes at least a customer record template reference and an indication of when to active a toll-free number associated with the request; searching a responsible organization record to determine the presence of a defined customer template record relating to the user request, wherein the responsible organization is associated with toll-free telecommunications; retrieving at least one customer template record, wherein the customer template record is a defined customer template record for the responsible organization; and activating the user request, wherein the activation includes at least one of activating or reserving the toll-free number.

[00718] A user interface according to one disclosed non-limiting embodiment of the present disclosure can include a webpage; and a widget operable to reserve a toll free number embedded within the webpage.

[00719] A further embodiment of the present disclosure may include that the widget provides a login element.

[00720] A further embodiment of the present disclosure may include that the widget provides a search feature for the toll free number.

[00721] A further embodiment of the present disclosure may include that the widget provides a reservation feature for the toll free number.

[00722] A further embodiment of the present disclosure may include that the widget provides an activation feature for the toll free number.

[00723] A further embodiment of the present disclosure may include that the widget provides historical information related to actions previously performed by a user.

[00724] A further embodiment of the present disclosure may include that the widget provides one- click functionality.

[00725] A method to secure user interface according to one disclosed non- limiting embodiment of the present disclosure can include lazy loading a widget operable to reserve a toll free number embedded within a webpage.

[00726] A further embodiment of the present disclosure may include providing a login element upon loading of the widget.

[00727] A further embodiment of the present disclosure may include providing a search feature for the toll free number. [00728] A further embodiment of the present disclosure may include providing a reservation feature for the toll free number.

[00729] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving data relating to at least one of a dip rate or dip volume that is associated with a toll-free number; receiving social media data relating to usage of the toll-free number; analyzing the combined data and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the demand associated with the toll-free number; and distributing a communication to an entity regarding the current valuation of the toll-free number.

[00730] A further embodiment of the present disclosure may include that the data is data sniffer data.

[00731] A further embodiment of the present disclosure may include that the tag includes data related to a category of toll-free number.

[00732] A further embodiment of the present disclosure may include that the category relates to an industry segment.

[00733] A further embodiment of the present disclosure may include that the tag includes data relating to popularity as derived at least in part from the search history associated with the toll-free number.

[00734] A further embodiment of the present disclosure may include that the tag includes location information associated with the toll-free number.

[00735] A further embodiment of the present disclosure may include that the tag includes financial information associated with the toll-free number.

[00736] A method according to one disclosed non-limiting embodiment of the present disclosure can include analyzing data relating to a toll-free number and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the inferred economic activity associated with the toll-free number; inferring a rating of a second toll-free number based at least in part on the valuation metadata, wherein the toll-free number and the second toll-free number share an attribute; and storing the inferred rating of the second toll-free number.

[00737] A further embodiment of the present disclosure may include that the data is data sniffer data.

[00738] A further embodiment of the present disclosure may include that the inferred rating is presented to a user in a user interface upon the user submitting a toll-free number query. [00739] A further embodiment of the present disclosure may include that the inferred rating generates an alert to a user if it exceeds a given rating value.

[00740] A further embodiment of the present disclosure may include that the alert is sent to a user sharing the attribute.

[00741] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving data relating to at least one of a dip rate or dip volume that is associated with a toll-free number; receiving social media data relating to usage of the toll-free number; analyzing the combined data and social media data to create a valuation metadata tag that is associated with the toll-free number, wherein the valuation metadata is a quantitative summary of the demand associated with the toll-free number; and initiating a toll-free number reservation based on the current valuation of the toll-free number.

[00742] A further embodiment of the present disclosure may include that the data is data sniffer data.

[00743] A method according to one disclosed non-limiting embodiment of the present disclosure can include creating at least two toll-free call routing tables based on a congestion threshold criterion, wherein the first of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are below the congestion threshold, and the second of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are equal to or above the congestion threshold; providing the call routing tables to at least one service control point that is associated with the toll- free telecommunications carrier network; monitoring toll-free call volumes and durations occurring within a toll-free telecommunications carrier network; receiving at least one of a call count datum or call duration datum from the toll-free telecommunications carrier network wherein the call count datum or call duration datum indicates a change in call volumes over the toll-free telecommunications carrier network from below the congestion threshold to above the congestion threshold; and instructing the service control point to switch from using the first call routing table to the second call routing table.

[00744] A further embodiment of the present disclosure may include that the call volume is expressed as a percentage of the total call volume occurring over the network.

[00745] A further embodiment of the present disclosure may include that the call volume is an indication of a network failure to transmit calls.

[00746] A further embodiment of the present disclosure may include that the call volume is specific to an entity.

[00747] A further embodiment of the present disclosure may include that the entity is a carrier. [00748] A further embodiment of the present disclosure may include that the entity is a call center. [00749] A further embodiment of the present disclosure may include that the entity is a service control point.

[00750] A further embodiment of the present disclosure may include that the switch to the second call routing table is automated and occurs in real time.

[00751] A further embodiment of the present disclosure may include that decision nodes of the first and second call routing tables are loaded into the service control point.

[00752] A further embodiment of the present disclosure may include that the call volumes are used to create a call path score for a possible call route path that is available on the network.

[00753] A further embodiment of the present disclosure may include that the call path score is based at least in part on a call travel distance estimate.

[00754] A further embodiment of the present disclosure may include that the call path score is based at least in part on a call travel speed estimate.

[00755] A further embodiment of the present disclosure may include that the call path score is used in association with the congestion threshold criterion to determine the switch to the second call route table.

[00756] A method according to one disclosed non-limiting embodiment of the present disclosure can include associating a toll-free telecommunications network congestion threshold criterion with a first rule regarding the usage of a plurality of call routing tables, and a second rule regarding the usage of a plurality of telecommunications carriers, wherein the congestion threshold criterion indicates a level of toll-free call volumes occurring within the toll-free telecommunications network; and switching toll-free calls across the telecommunications carriers based at least on the congestion threshold criterion, wherein the switched calls are further routing according to at least one of the plurality of call routing tables.

[00757] A method according to one disclosed non-limiting embodiment of the present disclosure can include creating at least two toll-free call routing tables based on a congestion threshold criterion, wherein the first of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are below the congestion threshold, and the second of the two call routing tables is to be used when toll-free call volumes occurring within a toll-free telecommunications carrier network are equal to or above the congestion threshold; providing the call routing tables to at least one service control point that is associated with the toll- free telecommunications carrier network; monitoring toll-free call volumes and durations occurring within a toll-free telecommunications carrier network; receiving at least one of a call count datum or call duration datum from the toll-free telecommunications carrier network wherein the call count datum or call duration datum indicates a change in call volumes over the toll-free telecommunications carrier network from below the congestion threshold to above the congestion threshold; creating a second congestion threshold criterion based on the data received from the toll- free telecommunications network; and creating a third call routing table based on the second congestion threshold criterion.

[00758] A further embodiment of the present disclosure may include that the toll-free call traffic occurring within a toll-free telecommunications network is switched based at least in part on one of the first or second congestion threshold criterion.

[00759] A method of identifying and storing an identifier associated with a toll-free-communication entity, according to one disclosed non-limiting embodiment of the present disclosure can include locating an identifier within the header portion of an SMS text message routed over a toll-free telecommunications line, the identifier located based at least in part through latent semantic indexing; comparing the located identifier with metadata stored on a server, the metadata associated with a plurality of entities; selecting an entity from among the plurality of entities based at least in part on the comparison; and storing a code associated with the entity within a translation table associated with a toll-free telecommunications management platform.

[00760] A further embodiment of the present disclosure may include that the code is an FCC code.

[00761] A further embodiment of the present disclosure may include that the entity is engaged in multimedia content distribution.

[00762] A further embodiment of the present disclosure may include that the entity is an ad agency.

[00763] A further embodiment of the present disclosure may include that the translation table pertains to routing voice data.

[00764] A further embodiment of the present disclosure may include that the translation table pertains to routing multimedia data.

[00765] A method of creating and storing an identifier associated with a toll-free-communication entity, according to one disclosed non-limiting embodiment of the present disclosure can include locating data within the header portion of an SMS text message routed over a toll-free telecommunications line, the data located based at least in part through latent semantic indexing; creating an entity identifier based at least on the data; storing a code associated with the entity identifier and an entity within a translation table associated with a toll-free telecommunications management platform; and associating the entity and entity identifier with a call routing table. [00766] A further embodiment of the present disclosure may include that the call routing table is configured to include multiple carriers. [00767] A further embodiment of the present disclosure may include that the call routing table is configured to have at least on rule pertaining to the time of day at which a call occurs.

[00768] A further embodiment of the present disclosure may include that the call routing table is configured to have at least one rule pertaining to the proximity of a caller to the entity.

[00769] A method of identifying and storing an identifier associated with a toll-free-communication entity, according to one disclosed non-limiting embodiment of the present disclosure can include identifying a toll-free call route trend among a plurality of toll-free calls taking place within a toll- free telecommunications network; wherein the call route trend is identified at least in part by call routings among toll-free numbers sharing an attribute; creating a call route template based at least in part on the trend; identifying an entity using at least one toll-free number with the shared attribute; prepopulating a call route tree for the entity based on the call route template.

[00770] A method according to one disclosed non-limiting embodiment of the present disclosure can include storing a taxonomy of abuse events that may occur regarding the usage of a toll-free number; storing a rule regarding an action to take upon receipt of a reported abuse event, wherein the rule specifies a routing rule defining how a call that is associated with the abuse event is to be routed over a toll-free telecommunications system; receiving a report of abuse of a toll-free number; identifying at least one abuse event within the stored taxonomy and routing rule that is related to content of the abuse report; and automatically routing a call that is the subject of the abuse report according to the routing rule.

[00771] A further embodiment of the present disclosure may include that the report of abuse derives from a call center.

[00772] A further embodiment of the present disclosure may include that the report of abuse derives from a telecommunications carrier.

[00773] A further embodiment of the present disclosure may include that the report of abuse derives from a business entity.

[00774] A further embodiment of the present disclosure may include that the routing rule is integrated within a call routing template.

[00775] A further embodiment of the present disclosure may include that the call routing template is shared with an entity other than that generating the report of abuse.

[00776] A further embodiment of the present disclosure may include that the routing of the call is manual instead of automatic.

[00777] A further embodiment of the present disclosure may include that the report of abuse includes data relating to a responsible organization. [00778] A further embodiment of the present disclosure may include that the report of abuse includes data relating to a time of the abuse event.

[00779] A further embodiment of the present disclosure may include that the report of abuse includes data relating to an originating number.

[00780] A further embodiment of the present disclosure may include that the report of abuse includes data relating to a geographic location of an originating number.

[00781] A further embodiment of the present disclosure may include that the report of abuse includes data relating to a geographic location of a terminating number.

[00782] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving a report of abuse of a toll-free number; identifying an absence of an abuse event definition within a stored taxonomy that is related to the type of abuse reported; storing a new definition of the abuse event within the taxonomy; and creating a routing rule defining how a call that is associated with the abuse event is to be routed over a toll-free telecommunications system. [00783] A further embodiment of the present disclosure may include that the stored definition is further associated with third party industry data.

[00784] A method according to one disclosed non-limiting embodiment of the present disclosure can include storing a taxonomy of abuse events that may occur regarding the usage of a toll-free number; associating the abuse events in the taxonomy with a toll-free number rating action; receiving a report of abuse of a toll-free number; identifying at least one abuse event within the stored taxonomy and rating action that is related to content of the abuse report; automatically computing a rating for the toll-free number based on the rating action; and reporting the rating to an entity. [00785] A further embodiment of the present disclosure may include that the rating is associated with a call routing rule.

[00786] A further embodiment of the present disclosure may include that the call routing rule is shared with a service provider.

[00787] A mobile device, according to one disclosed non-limiting embodiment of the present disclosure may include a unique toll-free ID (TFID) present in the mobile device, the TFID operable to facilitate toll-free communication between the mobile device and a manufacturer.

[00788] A further embodiment of the present disclosure may include that the TFID is hard flashed in the mobile device and present at the time of manufacture of the mobile device.

[00789] A further embodiment of the present disclosure may include that the TFID is operable to identify a customer.

[00790] A further embodiment of the present disclosure may include that the TFID is operable to identify a toll free provider that is providing the toll free communication. [00791] A further embodiment of the present disclosure may include that the TFID is provided via a standard support app that is natively installed.

[00792] A further embodiment of the present disclosure may include that the TFID is agnostic of type of mobile device.

[00793] A further embodiment of the present disclosure may include that the TFID facilitates a consumer’ s ability to at least one of talk, message, view, and browse support related features associated with merchandise at a point of sale.

[00794] A further embodiment of the present disclosure may include that the TFID facilitates a registration process.

[00795] A further embodiment of the present disclosure may include that the TFID facilitates a warranty process.

[00796] A further embodiment of the present disclosure may include a TFID Mobile App resident on the mobile device, the TFID Mobile App operable with the TFID.

[00797] A further embodiment of the present disclosure may include that the TFID Mobile App facilitates reading of at least one of a QR code, Barcode, RFID, and a serial number via a camera of the mobile device.

[00798] A method of communication via a toll-free service according to one disclosed non-limiting embodiment of the present disclosure can include associating at least one mobile device to merchandise purchased from a manufacturer via a unique toll-free ID (TFID) present in the mobile device, the TFID operable to facilitate toll-free communication between the mobile device and the manufacturer.

[00799] A further embodiment of the present disclosure may include reading of at least one of a QR code, Barcode, RFID, and a serial number via a camera of the mobile device.

[00800] A further embodiment of the present disclosure may include associating at least one of the QR code, Barcode, RFID, and the serial number with the TFID via a TFID Mobile App.

[00801] A further embodiment of the present disclosure may include identifying a customer via the TFID.

[00802] A further embodiment of the present disclosure may include identifying a toll free provider that is providing the toll free service via the TFID.

[00803] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving data relating to toll-free number call activity from a toll-free telecommunications system, wherein the data includes at least one of call duration or call count data; receiving third party data relating to macroeconomic activity; modeling at least one of call duration or call count data with the third party data to derive a macroeconomic trend; receiving a request from a client device to present the macroeconomic trend; and presenting a representation of the macroeconomic trend to a user interface on the client device.

[00804] A further embodiment of the present disclosure may include that the toll-free telecommunications system is a toll-free service provider.

[00805] A further embodiment of the present disclosure may include that the toll-free telecommunications system is a service control point.

[00806] A further embodiment of the present disclosure may include that the toll-free telecommunications system is an interexchange carrier.

[00807] A further embodiment of the present disclosure may include that the third party data is stock market data.

[00808] A further embodiment of the present disclosure may include that the third party data is Bloomberg TM data.

[00809] A further embodiment of the present disclosure may include that the third party data is government data.

[00810] A further embodiment of the present disclosure may include that the third party data is social media data.

[00811] A further embodiment of the present disclosure may include that the third party data is credit card processing data.

[00812] A further embodiment of the present disclosure may include that there is a temporal delay between the time of the request and the time of the presentation of long enough duration that the client device enters a sleep mode as regards the interaction, and the client device is activated out of sleep mode upon the presentation.

[00813] A method according to one disclosed non-limiting embodiment of the present disclosure can include receiving data relating to toll-free number call activity from a toll-free telecommunications system, wherein the data includes at least one of call duration or call count data; receiving metadata about the toll-free numbers that are the subject of the call activity, wherein the metadata includes data pertaining to at least one of business type or location; modeling at least one of call duration or call count data with the metadata to derive a macroeconomic trend; receiving a request from a client device to present the macroeconomic trend; and presenting a representation of the macroeconomic trend to a user interface on the client device.

[00814] A further embodiment of the present disclosure may include that the business type is a governmental office. [00815] A further embodiment of the present disclosure may include that the governmental office is an unemployment office.

[00816] A method of distributing a macroeconomic data trend over a network to a remote client device, according to one disclosed non- limiting embodiment of the present disclosure can include providing a user interface dashboard to a user for installation on the remote client device; receiving third party social media data; modeling at least one of call duration or call count data with the third party social media data to derive a macroeconomic trend; receiving a request from the remote client device to present the macroeconomic data trend; generating an alert from the macroeconomic data trend that contains a stock name, stock price and a universal resource locator (URL), which specifies the location of the data source; transmitting the alert over a communication channel to the remote client device associated with the user based upon a destination address and transmission schedule that is associated with the remote client device, wherein the alert activates the user interface dashboard to cause the alert to display on the remote client device and to enable connection with the user interface dashboard when the remote client device is activated.

[00817] Embodiments of the current disclosure may provide for a method for generating a list of telecommunication identifiers. The method includes interpreting, via at least one processor, telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The method further includes generating the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The method further includes transmitting the list. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The telecommunication identifiers in the list may be local telephone numbers. The method may further include indicating that the telecommunication identifiers in the list should not originate a telecommunication message. Indicating that the telecommunication identifiers in the list should not originate a telecommunication message may include at least one of: setting a data field associated with the list; or generating a message apart from the list. The telecommunication message may be at least one of a text message, a voice call, a video call, an e-mail, or the like. Generating the list based at least in part on the telecommunications data may include removing the assigned telecommunication identifiers and the in-use telecommunication identifiers from the available telecommunication identifiers. Generating the list based at least in part on the telecommunications data may further include including the disconnected telecommunication identifiers. The list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers. The list may further include the disconnected telecommunication identifiers.

[00818] Embodiments of the current disclosure may provide for another method for generating a list of telecommunication identifiers. The method may include interpreting, via at least one processor, telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The method may further include generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include transmitting the list. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The telecommunication identifiers in the list may be toll-free numbers. The method may further include indicating that the telecommunication identifiers in the list should not originate telecommunication messages. Indicating that the telecommunication identifiers in the list should not originate telecommunication messages may include at least one of: setting a data field associated with the list; or generating a message apart from the list. Generating the list based at least in part on the telecommunications data may include removing the assigned telecommunication identifiers and the reserved telecommunication identifiers from the available telecommunication identifiers. Generating the list based at least in part on the telecommunications data may further include including the disconnected telecommunication identifiers. The list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers. The list may further include the disconnected telecommunication identifiers.

[00819] Embodiments of the current disclosure may provide for an apparatus for generating a list of telecommunication identifiers. The apparatus may include a telecommunications data processing circuit structured to interpret telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The apparatus may further include a list generating circuit structured to generate the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The apparatus may further include a list provisioning circuit structured to transmit the list. Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers. The list may further include the disconnected telecommunication identifiers.

[00820] Embodiments of the current disclosure may provide for another apparatus for generating a list of telecommunication identifiers. The apparatus may include a telecommunications data processing circuit structured to interpret telecommunications data including available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The apparatus may further include a list generating circuit structured to generate the list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers. The apparatus may further include a list provisioning circuit structured to transmit the list. Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The list may include a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers. The list may further include the disconnected telecommunication identifiers.

[00821] Embodiments of the current disclosure may provide for a method for routing a telecommunication message. The method may include interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein the telecommunications data includes available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers. The list may include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include determining whether to route the telecommunications message based at least in part on the list. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The telecommunication identifiers in the list may be local telephone numbers.

[00822] Embodiments of the current disclosure may provide for another method for routing a telecommunication message. The method may include interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein the telecommunications data includes available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers. The list may include telecommunication identifiers that are a subset of the available telecommunication identifiers. The method may further include determining whether to route a telecommunications message based at least in part on the list. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The telecommunication identifiers in the list may be toll-free numbers.

[00823] Embodiments of the current disclosure may provide for a method for mitigating telecommunications fraud. The method may include identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between available telecommunication identifiers and in-use telecommunication identifiers. The method may further include penalizing, via the at least one processor, the entity. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Penalizing the entity may include at least one of: generating, via the at least one processor, a message indicating that the entity should be fined; or charging, via the at least one processor, the entity a fee. The telecommunication identifiers in the list may be local telephone numbers.

[00824] Embodiments of the current disclosure may provide for another method for mitigating telecommunications fraud. The method includes identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and reserved telecommunication identifiers. The method further includes penalizing, via the at least one processor, the entity. Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Penalizing the entity may include at least one of: generating, via the at least one processor, a message indicating that the entity should be fined; or charging, via the at least one processor, the entity a fee. The telecommunication identifiers in the list may be toll-free numbers. In embodiments, the telecommunication identifiers in the list may be tagged as not authorized to originate telecommunications traffic from outside a geographic region. In embodiments, the geographic region is at least one of the United States or Canada.

[00825] The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. Further, the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor. References to a “processor,” “processing unit,”

“processing facility,” “microprocessor,” “co-processor” or the like are meant to also encompass more that one of such items being used together. The present invention may be implemented as a method on the machine, as a system or apparatus as part of or in relation to the machine, or as a computer program product embodied in a computer readable medium executing on one or more of the machines. The processor may be part of a server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform. A processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like. The processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon. In addition, the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application. By way of implementation, methods, program codes, program instructions and the like described herein may be implemented in one or more thread. The thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code. The processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere. The processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere. The storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.

[00826] A processor may include one or more cores that may enhance speed and performance of a multiprocessor. In embodiments, the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).

[00827] The methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware. The software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server and other variants such as secondary server, host server, distributed server and the like. The server may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like. The methods, programs, or codes as described herein and elsewhere may be executed by the server. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.

[00828] The server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.

[00829] The software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like. The client may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like. The methods, programs, or codes as described herein and elsewhere may be executed by the client. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.

[00830] The client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.

[00831] The methods and systems described herein may be deployed in part or in whole through network infrastructures. The network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art. The computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like. The processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.

[00832] The methods, program codes, and instructions described herein and elsewhere may be implemented on a cellular network having multiple cells. The cellular network may either be or include a frequency division multiple access (FDMA) network or a code division multiple access (CDMA) network. The cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like. The cell network may be one or more of GSM, GPRS, 3G, EVDO, mesh, or other network types.

[00833] The methods, programs codes, and instructions described herein and elsewhere may be implemented on or through mobile devices. The mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices. The computing devices associated with mobile devices may be enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices. The mobile devices may communicate with base stations interfaced with servers and configured to execute program codes. The mobile devices may communicate on a peer-to-peer network, mesh network, or other communications network. The program code may be stored on the storage medium associated with the server and executed by a computing device embedded within the server. The base station may include a computing device and a storage medium. The storage device may store program codes and instructions executed by the computing devices associated with the base station.

[00834] The computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g. USB sticks or keys), floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like. [00835] The methods and systems described herein may transform physical and/or or intangible items from one state to another. The methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.

[00836] The elements described and depicted herein, including in flow charts and block diagrams throughout the figures, imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure. Examples of such machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipment, servers, routers and the like. Furthermore, the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions. Thus, while the foregoing drawings and descriptions set forth functional aspects of the disclosed systems, no particular arrangement of software for implementing these functional aspects should be inferred from these descriptions unless explicitly stated or otherwise clear from the context. Similarly, it will be appreciated that the various steps identified and described above may be varied, and that the order of steps may be adapted to particular applications of the techniques disclosed herein. All such variations and modifications are intended to fall within the scope of this disclosure. As such, the depiction and/or description of an order for various steps should not be understood to require a particular order of execution for those steps, unless required by a particular application, or explicitly stated or otherwise clear from the context.

[00837] The methods and/or processes described above, and steps thereof, may be realized in hardware, software or any combination of hardware and software suitable for a particular application. The hardware may include a general-purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing device. The processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory. The processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine-readable medium.

[00838] The computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low- level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.

[00839] Thus, in one aspect, each method described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof. In another aspect, the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware. In another aspect, the means for performing the steps associated with the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.

[00840] While the invention has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the spirit and scope of the present invention is not to be limited by the foregoing examples but is to be understood in the broadest sense allowable by law.

[00841] All documents referenced herein are hereby incorporated by reference.

Claims

What is Claimed is:

1. A method comprising: interpreting, via at least one processor, telecommunications data comprising: available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers; generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers; and transmitting the list.

2. The method of claim 1, wherein the telecommunication identifiers in the list are local telephone numbers.

3. The method of claim 1 further comprising: indicating that the telecommunication identifiers in the list should not originate a telecommunication message.

4. The method of claim 3, wherein indicating that the telecommunication identifiers in the list should not originate a telecommunication message comprises at least one of: setting a data field associated with the list; or generating a message apart from the list.

5. The method of claim 4, wherein the telecommunication message is at least one of: a text message; a voice call; a video call; or an e-mail.

6. The method of claim 1, wherein generating a list based at least in part on the telecommunications data comprises: removing the assigned telecommunication identifiers and the in-use telecommunication identifiers from the available telecommunication identifiers.

7. The method of claim 6, wherein generating a list based at least in part on the telecommunications data further comprises: including the disconnected telecommunication identifiers.

8. The method of claim 1, wherein the list includes: a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers; and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers.

9. The method of claim 8, wherein the list further includes: the disconnected telecommunication identifiers.

10. A method comprising: interpreting, via at least one processor, telecommunications data comprising: available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers; generating a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers; and transmitting the list.

11. The method of claim 10, wherein the telecommunication identifiers in the list are toll-free numbers.

12. The method of claim 10 further comprising: indicating that the telecommunication identifiers in the list should not originate telecommunication messages.

13. The method of claim 12, wherein indicating that the telecommunication identifiers in the list should not originate telecommunication messages comprises at least one of: setting a data field associated with the list; or generating a message apart from the list.

14. The method of claim 12, wherein generating a list based at least in part on the telecommunications data comprises: removing the assigned telecommunication identifiers and the reserved telecommunication identifiers from the available telecommunication identifiers.

15. The method of claim 14, wherein generating a list based at least in part on the telecommunications data further comprises: including the disconnected telecommunication identifiers.

16. The method of claim 10, wherein the list includes: a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers.

17. The method of claim 16, wherein the list further includes: the disconnected telecommunication identifiers.

18. An apparatus comprising: a telecommunications data processing circuit structured to interpret telecommunications data comprising: available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers; a list generating circuit structured to generate a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers; and a list provisioning circuit structured to transmit the list.

19. The apparatus of claim 18, wherein the list includes: a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the in-use telecommunication identifiers.

20. The apparatus of claim 19, wherein the list further includes: the disconnected telecommunication identifiers.

21. An apparatus comprising: a telecommunications data processing circuit structured to interpret telecommunications data comprising: available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers; a list generating circuit structured to generate a list based at least in part on the telecommunications data, wherein the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers; and a list provisioning circuit structured to transmit the list.

22. The apparatus of claim 21, wherein the list includes: a first difference between the available telecommunication identifiers and the assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and the reserved telecommunication identifiers.

23. The apparatus of claim 22, wherein the list further includes: the disconnected telecommunication identifiers.

24. A method comprising: interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein: the telecommunications data comprises: available telecommunication identifiers, assigned telecommunication identifiers, in-use telecommunication identifiers, and disconnected telecommunication identifiers; and the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers; and determining whether to route a telecommunications message based at least in part on the list.

25. The method of claim 24, wherein the telecommunication identifiers in the list are local telephone numbers.

26. A method comprising: interpreting, via at least one processor, a list generated based at least in part on telecommunications data, wherein: the telecommunications data comprises: available telecommunication identifiers, assigned telecommunication identifiers, reserved telecommunication identifiers, and disconnected telecommunication identifiers; and the list includes telecommunication identifiers that are a subset of the available telecommunication identifiers, and determining whether to route a telecommunications message based at least in part on the list.

27. The method of claim 26, wherein the telecommunication identifiers in the list are toll-free numbers.

28. A method comprising: identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes: a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between available telecommunication identifiers and in-use telecommunication identifiers; and penalizing, via the at least one processor, the entity.

29. The method of claim 28, wherein penalizing the entity comprises at least one of: generating, via the at least one processor, a message indicating that the entity should be fined; or charging, via the at least one processor, the entity a fee.

30. The method of claim 28, wherein the telecommunication identifiers in the list are local telephone numbers.

31. A method comprising:

Identifying, via at least one processor, an entity that routed a telecommunications message that originated from a telecommunication identifier on a list, wherein the list includes: a first difference between available telecommunication identifiers and assigned telecommunication identifiers, and a second difference between the available telecommunication identifiers and reserved telecommunication identifiers; and penalizing, via the at least one processor, the entity.

32. The method of claim 31, wherein penalizing the entity comprises at least one of: generating, via the at least one processor, a message indicating that the entity should be fined; or charging, via the at least one processor, the entity a fee.

33. The method of claim 31, wherein the telecommunication identifiers in the list are toll-free numbers.

34. The method of claim 31, wherein the telecommunication identifiers in the list are tagged as not authorized to originate telecommunications traffic from outside a geographic region.

35. The method of claim 34, wherein the geographic region is at least one of the United States or Canada.