WO2021107990A1

WO2021107990A1 - Methods and systems for distributing messaging content using telecommunication networks

Info

Publication number: WO2021107990A1
Application number: PCT/US2020/041111
Authority: WO
Inventors: Soren SCHAFFT; Tor SOEVIK
Original assignee: Campaign Registry Inc
Current assignee: Campaign Registry Inc
Priority date: 2019-11-27
Filing date: 2020-07-08
Publication date: 2021-06-03
Anticipated expiration: 2022-05-27

Abstract

Methods and systems are described for distributing messaging content using telecommunication networks. More specifically, the methods and system described herein provide for a messaging architecture, gateway, and/or management tool that use a messaging container that includes a specific data structure and is populated with data using a centralized registry. The use of this structure allows for additional features and functionality of messages along the communication network without obstructing, or being obstructed by, the new communication protocols and ad hoc modifications that have been created by different entities throughout the telecommunication networks.

Description

METHODS AND SYSTEMS FOR DISTRIBUTING MESSAGING CONTENT USING TELECOMMUNICATION NETWORKS

CROSS-REFERENCE TO RELATED APPLICATION

[001] This application claims priority to U.S. Patent App. No. 62/941,379, filed November 27, 2019, which is hereby incorporated by reference in its entirety.

FIELD OF THE TNVENTTON

[002] The invention relates to distributing messaging content using telecommunication networks.

BACKGROUND

[003] Modem telecommunications networks, which exchange information using electromagnetic systems, were developed with an emphasis on person-to-person telephone communications and often, a physical location as well (e.g. “the Smith’s family landline phone”). As such, much of the underlying infrastructure, standards, and industry protocols are developed with features and limitations geared towards person-to-person telephone communications. As the availability of devices that exchange information using electromagnetic systems and the amount of information that is exchanged has exponentially increased, the conventional telecommunication networks face ever increasing structural and functional limitations. Technology companies discovered that these phone numbers could be used for completely different types of applications and services not restricted to a physical location (e.g. sending a PIN message to verify the identity of a bank account owner).

[004] In some cases, to meet the increasing needs of the industry, new communication protocols and ad hoc modifications have been created by different entities throughout the telecommunication networks. These new protocols such as 10DLC (“10-Digit Long Code Messaging”) and SMS short codes provide a means for sending messages via telecommunication networks. Due to the limitations of these systems, new standards (e.g., “A2P 10DLC”) have begun to be adopted by some entities along the chain of the telecommunication networks. However, these new standards and routing infrastructure continue to have fundamental problems with respect to identifying sender and content metadata and integrating this information with routing infrastructure. Not only are sender and content details not collected effectively, but a lack of standardized definitions and metadata structure create confusion and errors as a particular service provider may take one, two or more different roles within the process of enabling a particular messaging service. Further, these roles can change from one messaging service to another. In order to ensure correctly identifying the sender and content, the service providers need to be allocated against the different roles in provider for each service. As different entities along the chain add ad hoc modifications to the telecommunication networks (e.g., to provide individual benefits or functionality), and/or different entities perform multiple roles along the chain, generating standardize messaging protocols becomes more difficult.

SUMMARY

[005] Methods and systems are described herein for distributing messaging content using telecommunication networks. More specifically, the methods and system described herein provide for a messaging architecture, gateway, and/or management tool that overcomes the problems described above by identifying the originators and/or senders of a particular message, their role in the ecosystem, and a type of message sent. To enable these features, the methods and systems create a specific data structure, which is shared with the entities in the messaging ecosystem either in the form of a novel messaging container or through online lookups against a centralized registry. The use of this structure allows for additional features and functionality of messages along the communication network without obstructing, or being obstructed by, the new communication protocols and ad hoc modifications that have been created by different entities throughout the telecommunication networks.

[006] Moreover, these methods and systems of identifying sender and content metadata is applicable for all forms of communication distribution networks (e.g., 10DLC, SMS short codes, MMS, RCS or variants of OTT messaging such as global messaging app providers). For example, conventional messages are transmitted using a decentralized structure that may be based on general industry standards such as 10DLC and SMS short codes. However, these standards have numerous disadvantages. For example, short codes create an impersonal user experience because receiving a text from a 5 or 6-digit number (as opposed to one with the same area code as the user) feels impersonal. In another example, short code keywords limit the number of possible responses as such shared short codes are not conversational because they limit the number of keyword responses customers can use. Additionally, if another entity has already claimed a keyword, the keyword is no longer usable. 10DLC also has disadvantages. For example, 10DLC may have limited through- put (e.g., 1 message per second). The use of the methods and systems described herein enables entities to use new standards such as application-to-person digital long code (“ A2P DLC”), which provides for conversational responses, allows for the use of local areas codes, allows for 5-15 messages per second when using an A2P DLC, allows for higher throughput than peer-to-peer, and/or allows for fast provisioning/assignment, and/or selection of numbers. Additionally, the methods and systems allow for the use in fallback messaging campaigns. For example, if an RCS messaging is not available for a campaign, the system may use an SMS message.

[007] The methods and systems also provide for unique advantages irrespective of the industry standard used. For example, through the unique message architecture any entity along the chain of the communications network may (e.g., acting as message gateway) verify the originator of the message, validate that the message should be sent to an end-user (or passed along in the chain of the communications network), and/or independently apply qualifications to the message (e.g., message may be managed based on throughput, surcharges may be applied, etc.). This is in stark contrast to conventional systems where a given entity on the chain may not know what entity originated the message and/or for what purpose.

[008] Additionally or alternatively, the methods and systems may allow these entities to determine what should be done with the message (e.g., determine a use of the message, identify target end-users, and/or apply vertical integration). For example, the entities may use the unique message architecture to provide streamlined provision management, enhanced network control, granular control layers, and/or provide billing and micro-controls via a message gateway. In conventional systems, there is no standard practice for filtering across different entities along the communications network chain. Due to this, filtering is limited to a simple static list of prohibited terms

[009] Finally, the methods and systems may also provide for unconventional controls and management tools for end-users such that end-users may provide user consent, provide feedback, and/or enter message preferences. End-users may thus interact with and establish controls that are passed along to message originators without ever directly contacting or having knowledge of the message originators. This is particularly notable as due to the numerous entities that provide the telecommunications network and/or assist in transmission of a message from a third-party entity (e.g., a known brand) to the end-user, a message may not be directly sent to the end-user from the third-party entity. Because of this, the third-party entity and/or the end-user may not necessarily know what entities were involved in facilitating the transmission of the message and/or how to contact each other. For example, the third-party entity may have used a messaging service provider (e.g., a social media and/or messaging platform) that directed the message to a direct connect aggregator, which then transmitted the message to a mobile network operator. In such a scenario, only the mobile network operator may have access to the contact information of the end-user. [010] In some aspects, systems and methods for distributing messages, via telecommunications networks, featuring data structures that allow third-party entities along the telecommunications network to determine source information, telecommunication network infrastructure relationships, and metadata for the messages are described. For example, the system may receive, at a campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user. The system may receive, at the campaign registry, first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message. The system may generate, at the campaign registry, a campaign identification for the messaging campaign based on the first and second records. The system may store, at the campaign registry, the campaign identification. The system may generate metadata, at the campaign registry, for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

[Oil] In some aspects, systems and methods for providing a gateway for telecommunications networks are described. For example, the system may receive, by an entity providing the telecommunications network, a message being transmitted from a third-party entity to an end-user according to a messaging campaign, wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user. The system may retrieve, from the message, a campaign identification for the messaging campaign, wherein the campaign identification is based on first and second records, stored in a campaign registry, corresponding to the messaging campaign, and wherein the first record identifies the third-party entity and the second record identifies a use case for the message. The system may retrieve a transmission rule for transmissions to the end-user; and determining a qualification level for the message based on the transmission rule. The system may determine, based on the qualification level, an amount of information about the third-party entity required to be accessible at the campaign registry to transmit the message. The system may determine whether the amount of information is accessible at the campaign registry. In response to determining that the amount of information is accessible at the campaign registry, the system may qualify the message for transmission by the entity.

[012] In some aspects, systems and methods filtering messages distributed via telecommunications networks are described. For example, the system may receive, at a campaign registry portal, a user input setting an end-user rule for messaging campaigns directed to an end- user; storing, at a campaign registry, the end-user rule. The system may receive, at the campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the message is labeled as being transmitted from the third-party entity when received by the end-user. The system may compare the end-user rule to information about the message. The system may determine that transmitting the message complies with the end-user rule based on the comparison. The system may generate metadata, at the campaign registry, for the message for transmission via a telecommunications network to the end-user, wherein a campaign identification, provided by the campaign registry, is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

[013] Various other aspects, features, and advantages of the invention will be apparent through the detailed description of the invention and the drawings attached hereto. It is also to be understood that both the foregoing general description and the following detailed description are examples and not restrictive of the scope of the invention. As used in the specification and in the claims, the singular forms of “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. In addition, as used in the specification and the claims, the term “or” means “and/or” unless the context clearly dictates otherwise. Additionally, as used in the specification “a portion,” refers to a part of, or the entirety of (i.e., the entire portion), a given item (e.g., data) unless the context clearly dictates otherwise. BRIEF DESCRIPTION OF THE DRAWINGS

[014] FIG. 1 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments.

[015] FIG. 2 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments.

[016] FIG. 3 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments.

[017] FIG. 4 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments.

[018] FIG. 5 shows an illustrative system diagram, in accordance with one or more embodiments. [019] FIGS. 6A-B show an illustrative system diagram, in accordance with one or more embodiments.

[020] FIG. 7 shows an illustrative system diagram, in accordance with one or more embodiments.

[021] FIG. 8 shows an illustrative system diagram, in accordance with one or more embodiments.

[022] FIG. 9 shows an illustrative system diagram, in accordance with one or more embodiments.

[023] FIG. 10 shows an illustrative system diagram, in accordance with one or more embodiments.

[024] FIG. 11 shows an illustrative system diagram, in accordance with one or more embodiments.

[025] FIG. 12 shows an illustrative diagram of message qualification levels, in accordance with one or more embodiments.

[026] FIG. 13 shows an illustrative message data structure, in accordance with one or more embodiments.

[027] FIG. 14 shows a flowchart of the steps involved in distributing messages via telecommunications networks, in accordance with one or more embodiments.

[028] FIG. 15 shows a flowchart of the steps involved in providing a gateway for a telecommunications networks, in accordance with one or more embodiments.

[029] FIG. 16 shows a flowchart of the steps involved in filtering messages distributed via telecommunications networks, in accordance with one or more embodiments. RETATT,ER DESCRIPTION OF THE DRAWINGS

[030] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It will be appreciated, however, by those having skill in the art, that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other cases, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.

[031] As described herein methods and systems are recited for a centralized registry for messaging campaigns, which identifies a specific campaign through the use of a campaign identification. This campaign identification is associated with the routing infrastructure such that as messages are routed, entities along the infrastructure may determine that the messages are registered messages by means of the campaign identification and/or identify attributes related to the messages, campaign, etc., which are used to support carrier specific processes such as determining whether the campaign is approved for a particular carrier, filtering levels, micro billing levels, message throttle rate, etc. Attributes may be made available to specific industry routing entities based upon their support of carrier desired routing processes. Additionally, the campaign registry may also provide a user interface to confirm user consent and/or messaging preferences as well as along entities to create and modify attributes of messaging campaigns. [032] In some embodiments, one or more computing devices are programmed to perform (e.g., via control circuitry) the functions described herein. The computing devices may include one or more electronic storages (e.g., databases or other electric storages), one or more physical processors programmed with one or more computer program instructions, and/or other components. The computing devices may include communication lines or ports to enable the exchange of information with a network or other computing platforms via wired or wireless techniques (e.g., Ethernet, fiber optics, coaxial cable, WiFi, Bluetooth, near field communication, or other technologies). The computing devices may include a plurality of hardware, software, and/or firmware components operating together. For example, the computing devices may be implemented by a cloud of computing platforms operating together as the computing devices. [033] The electronic storages described herein may include non-transitory storage media that electronically stores information. The electronic storage media of the electronic storages may include one or both of (i) system storage that is provided integrally (e.g., substantially nonremovable) with servers or client devices or (ii) removable storage that is removably connectable to the servers or client devices via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). The electronic storages may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storages may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). The electronic storage may store software algorithms, information determined by the processors, information obtained from servers, information obtained from client devices, or other information that enables the functionality as described herein.

[034] The processors may be programmed to provide information processing capabilities in the computing devices. As such, the processors may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. In some embodiments, the processors may include a plurality of processing units. These processing units may be physically located within the same device, or the processors may represent processing functionality of a plurality of devices operating in coordination. The processors may be programmed to execute computer program instructions to perform functions described herein of one or more subsystems. The processors may be programmed to execute computer program instructions by software; hardware; firmware; some combination of software, hardware, or firmware; and/or other mechanisms for configuring processing capabilities on the processors.

[035] FIG. 1 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments. For example, FIGS. 1-4 may represent user interfaces provided by a campaign registry system. It should be noted that while FIGS. 1-4 may represent user interfaces used to create messaging campaigns, these embodiments may also be applied to offer end-user features (e.g., as described in relation to FIG. 16 below). For example, the system may provide FIGS. 1-4 through a campaign registry portal. Entities may access the portal in order to review information about a messaging campaign. For example, third-party entities and/or campaign service providers may access the campaign portal to view information on their messaging campaigns, whereas end-users may access the campaign portal to edit information about themselves and set end-user rules. For example, the end-user may set rules related to “who” and/or “what” messages and/or messaging campaigns may be transmitted to the end-user. Additionally, the end-user may select and/or provide user consent, enter timing and data windows and/or deadlines for receiving messages and/or messaging campaigns, provide feedback on messages and/or messaging campaign, respond to messages, edit preferences, and/or block messages and/or messaging campaigns. It should also be noted that other entities may provide user interfaces such as user interface 100 and these other entities may pull data from a campaign registry to populate the interface.

[036] FIG. 1 includes user interface 100. In some embodiments, user interface 100 may represent a messaging campaign dashboard through which entities may monitor and track messaging campaigns. As referred to herein, a message may include any form of electronic communication and/or communication facilitated through electronic means. For example, a message may include an SMS message, RCS message, voice message, video message, and/or another communication format. For example, the message may include any communication that refers to how an entity describes itself, its services, its products, its positions, and/or the value it provides. The message may also refer to a different entity, product, service, or other idea. The message may be transmitted through text messages, social media posts, press releases, telephone calls, emails, and/or any other form of communication.

[037] The messages may be organized and/or transmitted as part of a messaging campaign, and the messaging campaign may be managed through user interface 100. For example, the messaging campaign may be comprised by a series of messages that are sent to a group of people or entities in furtherance of a goal. The messaging campaign may comprise a campaign name, goal, start and end dates, and creating messaging content. For example, through user interface 100 a campaign service provider may register (e.g., in a campaign registry) a messaging campaign. The campaign service provider may register the messaging campaign by declaring “who” (e.g., a third-party entity) is sending the messages and “what” messaging is being sent (“e.g., a use case and targeted industry). In response to registering the campaign, a direct connect aggregator (or other entity) may activate the campaign by providing contact information for end-users and/or linking a campaign identification to the messages. For example, the campaign registry, which is shared with the entities in the messaging ecosystem either in the form of a messaging container for the message or through online lookups against the campaign registry. For example, the message may include a container that includes campaign registry information or a campaign identifier, which may be used by an entity to lookup campaign registry information in the campaign registry. In some embodiments, the campaign registry may further include fallback campaigns (e.g., as described in FIG. 6B).

[038] For example, in response to selection of icon 102, the system may present user interface 100. User interface 100 may include additional icons, graphics, and/or analytics related to the campaign. Additionally, new campaigns may be started (e.g., via selecting icon 112). A user accessing user interface 100 (e.g., a campaign service provider) may additionally track top-use cases (e.g., via chart 110) as well as select additional options (e.g., option 104, option 106, and option 108). For example, additional options (e.g., option 104) may allow a user to access additional information on end-users and/or entities involved in transmitting and/or facilitating a message and/or messaging campaign. Rules associated with a messaging campaign, message, and/or end-user as well as graphic and/or statistical analyses of the messaging campaign, message, and/or end-user (e.g., user views, user interactions, success rates, and/or other data that tracks conversions from messages, targeted audiences for future messages, and remarket opportunities to end-users engaged in a specific action).

[039] FIG. 2 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments. For example, the system may generate user interface 200 in response to a user selection of option 106 (FIG. 1). In user interface 200, the system may generate for display registered brands and information about the brands such as a country of registration and/or a level of vetting. For example, as shown in user interface 200, a “trust level” may be assigned to a brand. This level may correspond to an external vetting or other metric used to verify, validate, and/or qualify a message and/or campaign.

[040] FIG. 3 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments. For example, the system may generate user interface 300 in response to a user selection of a brand from user interface 200 (FIG. 2). In response to the selection of a brand, the system may generate additional information about the brand and/or the messaging campaign related to the brand.

[041] FIG. 4 shows an illustrative user interface for a messaging campaign registry system, in accordance with one or more embodiments. For example, the system may generate user interface 400 in response to a user selection of option 108 (FIG. 1). Through user interface 400, a user may view one or more events tied to one or more branding campaigns.

[042] FIGS. 5-11 show illustrative system diagrams. For example, FIGS. 5-11 show various alternative embodiments, which may be used, either alone or in combination to distribute messages. In some embodiments, depending on the type of distribution (e.g., SMS or RCS), the system may use a specific data structure. For example, the data structure may include a campaign registry or a messaging container that includes a campaign registry or a campaign identifier for the message. The campaign registry, which may be located on a remote server, may be accessible by the entities in the messaging ecosystem. Alternatively or additionally, the message may include a container that includes campaign registry information or a campaign identifier, which may be used by an entity to lookup campaign registry information in the campaign registry.

[043] For example, FIG. 5 shows an illustrative system diagram, in accordance with one or more embodiments. For example, FIG. 5 shows system 500, which represents an exemplary messaging campaign (e.g., an SMS or 10DLC campaign). For example, system 500 includes campaign registry 502, which receives information 504 (e.g., a user case of a messaging campaign) and information 506 (e.g., a vertical industry of the messaging campaign). Campaign registry 502 also includes information from various entities related to “who” is transmitting a message and/or instituting a messaging campaign.

[044] For example, system 500 includes various entities. As referred to herein, an entity may include a person, company, organization, group of people, and/or categorization of people, places, or things that may distinguish one entity from another. For example, entities as referred to herein may refer to the entities that provide a telecommunications network and/or facilitate communications along a telecommunications network. For example, an entity may include a third- party entity (e.g., associated with a known brand) that wishes to send messages to another entity (e.g., an end-user). The end-user may comprise a person, account (e.g., a social media account, email account, etc.), organization, etc. For example, the end-user may comprise a person to which the third-party entity wishes to transmit a message.

[045] Other examples of entities may include campaign services providers (e.g., campaign service provider 510). For example, the campaign service provider may comprise an entity with a messaging platform that creates and manages campaigns for the third-party entities. In some embodiments, the campaign service provider may comprise a messaging platform (e.g., a cloud communications platform as a service (“CPaaS”) that allows software developers to programmatically make and receive phone calls, send and receive text messages, and perform other communication functions using its web service APIs. As shown in FIG. 5, campaign service provider 510, third-party entity 508, and direct connect aggregator 512 may transmit information to campaign registry 502. This information may then be stored in campaign registry 502.

[046] Entities may also include additional entities that the message encounters from its source to a receiver. For example, the message may be transmitted from the campaign service provider through one or more telecommunication hops and/or to entities that provide the hops. In some embodiments, the entities may comprise any additional connection between a campaign service provider and a direct connect aggregator. Other entities may provide services such as settlement and exchange, post-call validation, and message rating services (e.g., as used in the validation, verification, and/or qualification of messages and messaging campaigns).

[047] Other examples of entities may include direct connect aggregators (e.g., direct connect aggregator 512). Direct connect aggregators may connect campaign service providers to mobile network operators. In some embodiments, direct connect aggregators may also perform the role of a campaign service provider. Direct connect aggregators may aggregate numerous messaging campaigns to one or more additional entities. For example, a direct connect aggregator may have existing commercial and technical integrations with multiple other entities (e.g., mobile network operators) in single or multiple markets and may significantly simplify the work of a campaign service provider wanting to procure mobile services access. Through the direct connect aggregator, the campaign service provider may obtain a short code, provision mobile services and start delivering services nationally across all mobile networks within hours if not minutes (without the weeks and even months that negotiations with individual mobile network operators currently may take).

[048] For example, campaign service provider 510 may register (e.g., in campaign registry 502) a messaging campaign. Campaign service provider 510 may register the messaging campaign by declaring “who” (e.g., third-party entity 508) is sending the messages and “what” messaging is being sent (e.g., information 504 and information 506). In response to registering the campaign, direct connect aggregator 512 may activate the campaign by providing contact information for end-users (e.g., end-user 518) and/or linking a campaign identification to the messages. For example, after the campaign is created in the campaign registry, the message senders (e.g., direct connect aggregator 512) associate their sending numbers (e.g., a 10DLC number) with the campaign identification of the message. The system may maintain the association at the campaign registry and make the associations accessible to entities in the messaging ecosystem including gateways, which may then look up the sending permissions for the given campaign and its associated numbers. The campaign attributes can be encrypted and/or obfuscated when shared in public or semi-public databases, to ensure that only authorized users (e.g., gateway 514, mobile network operator 516, etc.) have access to the information (e.g., as described below in FIG. 1 and in database 906 (FIG. 9)).

[049] The messages may then be processed through gateway 514. A gateway may comprise a portion of a mobile network operator and/or be a separate entity from the mobile network operator. The gateway may connect the direct connect aggregator to the mobile network operator. For example, a gateway may comprise a piece of networking hardware (or an entity in control of the hardware) used in telecommunications for telecommunications networks that allows data to flow from one discrete network to another. The gateway may communicate using more than one protocol to connect multiple networks and can operate at any of the seven layers of the open systems interconnection model. As described herein, a gateway may also provide function directly tied to a campaign registry (e.g., as described in FIG. 15 below).

[050] Gateway 514 may then send (or allow to pass) the message to mobile network operator 516 (e.g., as further described in FIG. 9 below). A mobile network operator may comprise a wireless service provider, wireless carrier, cellular company, or mobile network carrier, is a provider of wireless communications services that owns or controls some or all of the elements necessary to sell and deliver services to an end-user including radio spectrum allocation, wireless network infrastructure, back haul infrastructure, billing, customer care, provisioning computer systems and marketing and repair organizations. It should be noted that while embodiments are described in relation to “mobile” network operators, the same embodiments may apply to network operators in general.

[051] Mobile network operator 516 may then transmit the message to end-user 518 (or to a user device associated with end-user 518). For example, the user device may include any type of mobile terminal, fixed terminal, or other device. Each of these devices may receive content and data via input/output (hereinafter “I/O”) paths and may also include processors and/or control circuitry to send and receive commands, requests, and other suitable data using the EO paths. The control circuitry may be comprised of any suitable processing circuitry. Each of these devices may also include a user input interface and/or display for use in receiving and displaying data (e.g., user interface 100 (FIG. 1) and/or messages). By way of example, user devices may include a desktop computer, a server, a mobile phone, table computer, or other device capable of displaying electronic communications. Through the user of a user input interface and/or display a message recipient may see information about a sender and content of a given message, and may also be able to set preferences for which senders and message types to receive.

[052] FIG. 6A shows an illustrative system diagram, in accordance with one or more embodiments. In some embodiments, system 600 may be used for RCS and bot-based distribution. While similar to the SMS distribution of FIG. 5 above, system 600 includes additional information related to rights to use logos/trademarks.

[053] For example, system 600 may include a bot-based campaign registry (e.g., campaign registry 602). The bot may be an autonomous program on a network (especially the Internet) that interacts with computer systems, entities, or end-users. In such embodiments, third-party entity 610 may transmit permissions related to the use of logos and trademarks (e.g., information 604), which is stored in campaign registry 602. Furthermore, in system 600, a campaign service provider may comprise a bot-based service provider 612. Additionally, system 600 may include Messaging as a Platform (“Maap”) 606.

[054] In some embodiments, third party entities may submit bot information for verification by a campaign registry, which checks the identity of senders (e.g., “Who” information), and the rights to use the bot assets, and information about the message (e.g., “What” information). In this way, the campaign registry supports both campaign and bot registration.

[055] System 600 may allow third-party entities to message end-users with a wide range of services such as chatbots, plugins, artificial intelligence, and other industrial applications. This effectively extends the person-to-person messaging ecosystem to include Application-to-Person (A2P) and enterprise messaging to create a new communications category of Business to People (B2P). Furthermore, end-users may have direct access to brands and services where they can engage with chatbots or other virtual assistants to answer questions, investigate options, coordinate plans, make reservations or any number of other service scenarios.

[056] In FIG. 6B, system 650 further includes RCS bot 652. For example, system 650 may provide authenticated SMS fallback to RCS bots by associating one or more approved 10DLC SMS campaigns with RCS bot 652 (e.g., at permissions database 654). System 650 may allow RCS bot 652 to fall back to SMS messaging for use in sending messages of a messaging campaign by using a number associated with an approved SMS campaign when RCS bot 652 cannot deliver a message as RCS. For example, in response to receiving a notification that RCS bot 652 cannot deliver a message as RCS (e.g., based on an error or return notification received from one or more entities), RCS bot 652 send an SMS message using approved SMS campaign.

[057] For example, system 650 may associate both bots (e.g., RCS bot 652) and individual campaigns (e.g., in a campaign registry) with the same brand (e.g., brand 656) or campaign service provider (e.g., campaign service provider 658) as well as respective fallback SMS campaigns. [058] FIG. 7 shows an illustrative system diagram, in accordance with one or more embodiments. In particular, system 700 illustrates a campaign registry process. In such cases, information 702 (e.g., corresponding to the “who” of the messaging campaign) and information 704 (e.g., corresponding to the “what” of the messaging campaign) may be stored in campaign registry 706 (which is pictured as separate from messaging campaign 708 in FIG. 7). For example, information 702 may be implemented in campaign 708 through the use of transmission rules and qualification levels (e.g., as described below in FIG. 12). Furthermore, information 704 may be used to grant permissions (e.g., as related to transmission rules and end-user rules).FIG. 8 shows an illustrative system diagram, in accordance with one or more embodiments. For example, system 800 indicates the application of mobile network operator rules. For example, rules engine 802 may apply carrier specific rules (e.g., mobile network operator rules) to registered campaigns, with output as needed by each carrier, in the form of campaign classifications, permissions, tags, etc., for use in their respective systems. Through this mechanism, the campaign registry and rules engine 802 may apply the carrier specific rules in a manner that is not available in conventional systems. It should be noted that rules engine 802 may be housed in, and controlled by, one or more entities in system 800. For example, rules engine 802 may be implemented in a campaign registry such as campaign registry 804. In some embodiments, rules engine 802 may be implemented in an intelligent gateway (e.g., as described in FIG. 15).

[059] FIG. 9 shows an illustrative system diagram, in accordance with one or more embodiments. For example, as shown in system 900, a campaign registry may use a specific mechanism whereby messaging campaign attributes (e.g., as stored in the campaign registry), as well as output from rules engine 902 is shared through database 906 (e.g., a NetNumber override services registry database). For example, transmission rules 904 may indicate what information is permissible and/or what information should be obfuscated. The resulting messaging and or information may then be subject to filtering at gateway 908, which may verify compliance of messages and messaging campaigns against mobile operator network rules.

[060] For example, after the messaging campaign is created in a campaign registry, the message senders (e.g., brand 910, campaign service provider 912, direct connect aggregator 914, etc.) associate their sending numbers (e.g., a 10DLC number found in numbers database (e.g., database 906) with the campaign identification. The system may maintain the association at the campaign registry or by third parties and made available to the messaging ecosystem including gateways, which can then look up the sending permissions for the given campaign and its associated numbers. The campaign attributes can be encrypted and/or obfuscated when shared in public or semi-public databases, to ensure that only authorized users (e.g., gateway 908, mobile network operator 916, etc.) have access to the information database 906. In some embodiments, the campaign registry may further include fallback campaigns (e.g., as described in FIG. 6B).

[061] FIG. 10 shows an illustrative system diagram, in accordance with one or more embodiments. System 1000 may indicate a feedback loop to a campaign registry. For example, a campaign registry may incorporate feedback (compliance, sentiment, etc.) received from mobile network operators, gateways, and spam filters. This information may be used to update vetting scores and/or campaign permissions. For example, if a message is blocked due to mobile network operator rules, the campaign registry may update a vetting score associated with the campaign and/or modify attributes of the messaging campaign and/or message to comply.

[062] For example, system 1000 may include a feedback loop comprising scoring component 1004 and reapplication component 1002. For example, messages transmitted through system 1000 (e.g., as described above in FIGS. 5-9) may receive a vetting score that is transmitted back to different entities throughout the system (e.g., third-party entity 508 (FIG. 5), campaign registry 502 (FIG. 5), campaign service provider 510 (FIG. 5), and direct connect aggregator 512 (FIG. 5)) via component 1004. Furthermore, messages that were blocked, modified, and/or delayed may be sent back to the campaign registry (e.g., campaign registry 502 (FIG. 5)) via component 1002. [063] For example, the entities and gateways that check messaging traffic for compliance against permissions (granted by the mobile network operator, as produced by a rules engine, and shared through the override services registry database), provide feedback to the campaign registry, which in turn can maintain a vetting score for each of the entities throughout the system (e.g., third-party entity 508 (FIG. 5), campaign registry 502 (FIG. 5), campaign service provider 510 (FIG. 5), and direct connect aggregator 512 (FIG. 5)) and for each campaign. This vetting score can then be used in the rules engine to update the messaging campaign permissions in a cyclical manner. [064] FIG. 11 shows an illustrative system diagram, in accordance with one or more embodiments. For example, system 1100 illustrates an intelligent gateway (e.g., as described in FIG. 15 below). For example, gateway 1102 may comprise a network gateway and spam/message filter that may filter messages based on mobile network operator permissions and information received from the campaign registry.

[065] For example, in conventional systems, carrier traffic management functions (and/or the gateways and/or spam filters that perform these functions) typically rely upon message content and/or message metadata to enforce carrier traffic policies, to implement differentiated pricing, etc. However, gateway 1102 may combine the gateway and messaging filtering functions as well as implement them with improved precision by accessing information on a given message and/or messaging campaign (e.g., third-party entity, vetting score, qualification level, transmission rules, and/or end-user rules) through the campaign registry.

[066] FIG. 12 shows an illustrative diagram of qualification levels, in accordance with one or more embodiments. For example, as further described in FIG. 15 below, the system may determine a qualification level for a brand, message, and/or messaging campaign. For example, the system may filter out brands, messages, and/or messaging campaign that do not meet a predetermined qualification level and/or apply rules to the messages and/or messaging campaigns.

[067] As shown in FIG. 12, diagram 1200 indicates an example qualification levels. For example, the campaign registry may provide information about a message and/or messaging campaign (e.g., “who” and “what” information), which describes a third-party entity attributed to the messages and/or a use case of the message. Entities along the telecommunications network may then qualify the message and/or messaging campaign against a set of rules provided by the entity (e.g., a mobile network operators). The system may access numerous types and amounts of data, and the rules may detail the type, level, and amount of qualification is required for different types of campaigns. For example, a political campaign may require verification that the campaign is associated with a candidate running for office or with a registered political organization. Alternatively, a charity campaign may require verification of legal status as a charity (501(c)(3)). Other campaigns require details around the companies involved with the campaign and their history (Telephone Consumer Protection Act violations, etc.).

[068] For example, as shown in diagram 1200, an initial qualification level (e.g., qualification level 1) may require a name, email, and/or phone number for a third-party entity. The system may also verify this information based on comparing this information to other publicly available information. In some embodiments, the initial qualification level may be associated with messages and/or messaging campaigns sent by individual users.

[069] As shown in diagram 1200, a second qualification level (e.g., qualification level 2) may require a name, email, phone number, and/or address for a third-party entity. The system may also verify this information based on comparing this information to other publicly available information. In some embodiments, the second qualification level may be associated with messages and/or messaging campaigns sent by small companies. To verify and/or vet this information, the system may rely on a verified address, which is more reliable that an email or name.

[070] As shown in diagram 1200, a third qualification level (e.g., qualification level 3) may require second qualification level data as well as a company identity for a third-party entity. The system may also verify this information based on comparing this information to other publicly available information. In some embodiments, the third qualification level may be associated with messages and/or messaging campaigns sent by medium-sized companies. To verify and/or vet this information, the system may rely on the verification of the company data (e.g., employment identification numbers and/or other company information issued by a governmental source). [071] As shown in diagram 1200, a fourth qualification level (e.g., qualification level 4) may require third qualification level data as well as external vetting (e.g., vetting via third party provider which may provide a vetting score of reliability and/or according to published rules). The system may also verify this information based on comparing this information to other publicly available information. In some embodiments, the fourth qualification level may be associated with messages and/or messaging campaigns sent by publicly listed companies, government organizations, etc. To verify and/or vet this information, the system may rely on the verification of the company data (e.g., employment identification numbers and/or other company information issued by a governmental source), stock symbols, and/or a vetting score. For example, both internal and external verification, cyber checks, and/or validation processes may be used to set qualification levels that are fed into the system (e.g., a rules engine of the system). For vetting scores, these scores may be based on historical data about the third-party entity that includes compliance information, end-user complaints, etc.

[072] In some embodiments, information in diagram 1200 (e.g., a required qualification level of a message) may be found in a message container for a message. For example, a messaging container may comprise a campaign registry or a data structure (e.g., data structure 1300 (FIG. 13)) that includes a campaign registry or a campaign identifier for the message. The campaign registry, which may be located on a remote server, may be accessible by the entities in the messaging ecosystem. Alternatively or additionally, the message may include a container that includes campaign registry information or a campaign identifier, which may be used by an entity to lookup campaign registry information in the campaign registry.

[073] FIG. 13 shows an illustrative message data structure, in accordance with one or more embodiments. Data structure 1300 may show record information that is included with a message and/or associated with a messaging campaign in a campaign registry. For example, data structure 1300 includes various tag components that may be attached to a message, stored in a campaign registry record, and/or otherwise associated with a messaging campaign. For example, data structure 1300 may include an external identification number used for settlement and exchange, post-call validation, and message rating services (e.g., a “External ID”). The component may also include information that relates the message to a given campaign service provider and/or a direct connect aggregator. For example, data structure 1300 may comprise information used to identify a messaging campaign and/or include information about a messaging campaign with the message. The campaign registry, which may be located on a remote server, may be accessible by entities in the messaging ecosystem using information in data structure 1300. Data structure 1300 may comprise a container that includes campaign registry information or a campaign identifier, which may be used by an entity to lookup campaign registry information in the campaign registry.

[074] Data structure 1300 may also include a message class, which may be assigned based on a user case, industry, trust level, and/or other criteria. Data structure 1300 may also include a source entity ID (e.g., an identification for a third-party entity). In some embodiments, this information may be obfuscated. Additionally, data structure 1300 may include a campaign identification that identifies the campaign at the campaign registry. [075] FIG. 14 shows a flowchart of the steps involved in distributing messages via telecommunications networks, featuring data structures that allow third-party entities along the telecommunications network to determine source information (e.g., “who” sent a message), telecommunication network infrastructure relationships (a role of an entity along the telecommunications network), and metadata (e.g., “what” is the message for) for the messages, in accordance with one or more embodiments. For example, process 1400 may be performed by one or more devices as described in FIGS. 1-13. For example, user interface 100 (FIG. 1) may be used to initiate process 1400. Process 1400 may then be executed by one or more devices as shown in system 500 (FIG. 5). In some embodiments, one or more steps of process 1400 may be combined with one or more steps in process 1500 (FIG. 5) and process 1600 (FIG. 16).

[076] At step 1402, process 1400 receives a request to generate a messaging campaign from a third-party entity. For example, the system may receive (e.g., at a campaign registry) a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user. For example, the third- party entity may be an entity associated with a brand known to an end-user. The third-party entity may wish to directly message the end-user using SMS or RCS messaging. That is, while the third-party entity may need other entities (e.g., a messaging platform, a direct connect aggregator, a mobile network operator, etc.) that provide the telecommunications network to facilitate the transmission, the third-party entity may wish for the message delivered to the end- user to appear as if it was received directly from the third-party entity.

[077] At step 1404, process 1400 receives first and second records corresponding to the messaging campaign. For example, the system may receive (e.g., at the campaign registry) first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message. For example, the first record may include campaign registry “who” information (e.g., information about the third-party entity and/or campaign service providers such as an entity with a messaging platform that creates and manages campaigns for their customers (e.g., the third party entity)). The second record may include campaign registry “what” information (e.g., information that indicates a user case and/or industry related to the message). For example in some embodiments, the first record may include an airline brand and a mobile marketing service provider and the second record may include an operational use case (e.g., alerts, reminders, notifications, etc.) and list the travel industry as the relevant industry).

[078] For example, entities (e.g., campaign service providers) may register campaigns by declaring “who” are the service providers of the campaign and “what” type of communication (use case / vertical) is to be provided. Upon registration (e.g., in the campaign registry), the system assigns the campaign a campaign identification (e.g., a serial number, account number, and/or another alphanumeric identifier). Entities (e.g., the direct connect aggregator or the mobile network operator) may then activate campaigns by associating the campaign identification with information about the entity (e.g., a registration number for the direct connect aggregator or the mobile network operator) and the contact information (e.g., routing information, phone numbers, IP addresses, social media account information, etc. for end-users) to be used by the campaign. For example, after the campaign is created in the campaign registry, the message senders may associate their sending numbers (e.g., a 10DLC number) with the campaign identification. The system may maintain the association at the campaign registry and make the associations available to entities in the messaging ecosystem including gateways (e.g., as described in FIG. 15 below), which may then look up the sending permissions for the given campaign and its associated numbers. The campaign attributes may be encrypted and/or obfuscated when shared in public or semi-public databases, to ensure that only authorized users have access to the information.

[079] At step 1406, process 1400 generates a campaign identification for the messaging campaign based on the first and second records. For example, the system may generate (e.g., at the campaign registry) a campaign identification for the messaging campaign based on the first and second records. For example, the campaign identification may be an alphanumeric code or serial number associated with the campaign in the campaign registry.

[080] At step 1408, process 1400 stores the campaign identification. For example, the system may store (e.g., at the campaign registry) the campaign identification. For example, the messaging industry has not conventionally used uniform definitions and that, coupled with the fact that a single entity may play multiple roles within a given campaign, creates confusion and stifles industry innovation. By storing the campaign identification in a campaign registry, the system creates a uniform definition and/or source of information (e.g., “who” and “what” information) about a given campaign. The system may also simultaneously share the campaign identification with third-parties through a NetNumber OSR database (e.g., database 906 (FIG.

9))·

[081] In some embodiments, the system may receive a data element from a direct connect aggregator or a mobile network operator and activate the messaging campaign at the campaign registry in response to receiving the data element from the direct connect aggregator or the mobile network operator. For example, the system may activate a campaign (or campaign identification stored at a campaign registry) by coupling it with the data elements of the direct connect aggregator or a mobile network operator (e.g., routing information, phone numbers, IP addresses, social media account information, etc. for end-users). For example, after a campaign is created in the campaign registry, the message senders (e.g., direct connect aggregator 512 (FIG. 5)) associate their sending numbers (e.g., a 10DLC number) with the campaign identification. The system may maintain the association at the campaign registry or by third parties and made available to the messaging ecosystem including gateways, which may then look up the sending permissions for a given messaging campaign and its associated numbers. The campaign attributes can be encrypted and/or obfuscated when shared in public or semi-public databases, to ensure that only authorized users (e.g., gateway 514, mobile network operator 516, etc.) have access to the information.

[082] At step 1410, process 1400 generates metadata for the message for transmission via a telecommunications network to the end-user. For example, the system may generate (e.g., at the campaign registry) the metadata for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end- user. For example, the system may create metadata which ties each sent message to Senderlds, UseCase, etc. The message provider (e.g., a brand, aggregator, etc.) may further generate (e.g., by adding additional content) the message and transmit the messages.

[083] In some embodiments, the message may include a data structure (e.g., data structure 1300 (FIG. 13)) that may include a campaign registry or information used to lookup a messaging campaign in a campaign registry. For example, the data structure may be included in a messaging container that includes a campaign registry or a campaign identifier for the messaging campaign. [084] It is contemplated that the steps or descriptions of FIG. 14 may be used with any other embodiment of this disclosure. In addition, the steps and descriptions described in relation to FIG. 14 may be done in alternative orders or in parallel to further the purposes of this disclosure. For example, each of these steps may be performed in any order or in parallel or substantially simultaneously to reduce lag or increase the speed of the system or method. Furthermore, it should be noted that in some embodiments, one or more steps of process 1400 may be combined with one or more steps in process 1500 (FIG. 5) and process 1600 (FIG. 16).

[085] FIG. 15 shows a flowchart of the steps involved in providing a gateway for telecommunications networks, in accordance with one or more embodiments. For example, process 1500 may be performed by one or more devices as described in FIGS. 1-13. For example, user interface 100 (FIG. 1) may be used to initiate process 1500. Process 1500 may then be executed by one or more devices as shown in system 500 (FIG. 5).

[086] At step 1502, process 1500 receives a message being transmitted from a third-party entity to an end-user according to a messaging campaign. For example, the system may receive, by an entity providing the telecommunications network, a message being transmitted from a third-party entity to an end-user according to a messaging campaign, wherein the message is labeled as being transmitted from the third-party entity when received by the end-user. For example, the third- party entity may be an entity associated with a brand known to an end-user. The third-party entity may wish to directly message the end-user using SMS or RCS messaging. Furthermore, the third- party entity may need other entities (e.g., a messaging platform, a direct connect aggregator, a mobile network operator, etc.) that provide the telecommunications network to facilitate the transmission by providing contact information or other data elements (e.g., routing information, phone numbers, IP addresses, social media account information, etc. for end-users).

[087] At step 1504, process 1500 retrieves, from the message, a campaign identification for the messaging campaign. For example, the system may retrieve from the message, a campaign identification for the messaging campaign, wherein the campaign identification is based on first and second records, stored in a campaign registry, corresponding to the messaging campaign, and wherein the first record identifies the third-party entity and the second record identifies a use case for the message. For example, the campaign identification may correspond to a unique campaign record stored at a campaign registry. The campaign registry may store additional information on the “who” and “what” information (as described above) for the message and/or messaging campaign associated with the message. Additionally, or alternatively, the campaign registry may verify, validate, and/or qualify campaigns and upload campaign identification and related attributes into existing routing infrastructure. For example, the message may include a messaging container comprising a data structure (e.g., data structure 1300 (FIG. 13)) used to identify a messaging campaign, provide campaign registry information, and/or include information about a messaging campaign with the message.

[088] At step 1506, process 1500 retrieves a transmission rule for transmissions to the end-user. For example, the system may retrieve a transmission rule (e.g., from a rule set of an entity) for transmissions to the end-user. For example, the system may validate information about the message and/or information about a messaging campaign (e.g., the first record) and corresponding to the third-party entity. In some embodiments, the system may collect information and validate that information prior to processing it through a rules engine (e.g., located at the campaign registry and/or other location along the network) which may determine a distribution network (and/or distribution rules) for the message. For example, the system may access a public industry database and retrieve routing details from the database. The system may also validate that sensitive information (e.g., confidential and/or other information prohibited by a transmission rule) is not contained in the message. If so, the system may block the message and/or obfuscate the sensitive information.

[089] The transmission rule may also indicate a distribution path and/or distribution list for the message and/or messaging campaign as well as rules specific to that path and/or list. For example, a messaging platform may allow user rules and/or guidelines specific to the messaging platform. A mobile network operator may provide rules for traffic on its network. Entities may also apply ecosystem rules and/or tools to support service enhancements and/or special use management (e.g., large volume service management) related to messages. The transmission rule may also include an end user rules (e.g., created using end-user tools as described in FIG. 16).

[090] In some embodiments, the evaluation of the transmission rule may be performed by a rules engine. The rules engine may collect relevant data and/or performing vetting on the data, performing identification and cybersecurity checks, create campaign classes, upload messages into a routing infrastructure, access APIs and/or portals form transmission along the communications network. [091] The rules engine may allow for individual entities to decide how to use campaign registry data to support the management process. For example, the campaign registry data may include message classes that allow an entity to filter the messages and/or monitor throughout, apply surcharges, monitor rules, performing data vetting, and/or maintain best practices. The rules engine may also indicate what data sets are available and/or provide access to them (e.g., via APIs or dynamic IP addresses). For example, the rules engine may provide data such as qualification levels and/or additional data fields associated with a message and/or message campaign (e.g., as described in FIGS. 12-13). The additional data may allow entities to manage traffic and campaign provisioning based on the third party-entity or qualification level, the campaign identification and/or information about the campaign accessible via the campaign registry, externally created vetting results (e.g., based on verifying information about the messaging campaign), other fields defmed/required by an entity (e.g., brand name, contact information, industry, etc.). The additional data may also allow an entity to track and/or generate reports and overviews of a messaging campaign, message traffic, end-user results, etc.

[092] At step 1508, process 1500 determines a qualification level for a brand, message, and/or messaging campaign. For example, the system may determine a qualification level for a brand based on the transmission rule. In some embodiments, the system may compare qualification levels as described in FIG. 12 above. For example, the system may filter out brands, messages and/or messaging campaign that do not meet a predetermined qualification level. For example, using the information in the campaign registry, entities may apply rules to the messages and/or messaging campaigns.

[093] At step 1510, process 1500 determines an amount of information about the third-party entity required to be accessible at the campaign registry to transmit the message. For example, the system may determine, based on the qualification level, an amount of information about the third- party entity required to be accessible at the campaign registry to transmit the message. For example, a branding campaign requires verification that the campaign is associated with the brand. Alternatively, a company campaign requires verification of legal status as a register company. [094] At step 1512, process 1500 determines whether the amount of information is accessible at the campaign registry. For example, the system may determine whether or not the amount of information required to meet the qualification level (e.g., whether the amount of information and the resulting brand qualification level meets the requirements for the brand to send the message) is accessible at the campaign registry. For example, whether or not an address listed in the campaign registry as required by a qualification level (and/or whether or not the address is verified).

[095] At step 1514, process 1500 qualifies the message for transmission by the entity in response to determining that the amount of information is accessible at the campaign registry. For example, the system may qualify the message for transmission by the entity in response to determining that the amount of information is accessible at the campaign registry. For example, in response to determining that a messaging campaign requires an external vetting score of a predetermined amount, the system may determine whether or not the external vetting score (e.g., “trust level”) is above the predetermined amount. In some embodiments, determining that the amount of information is accessible at the campaign registry may comprise determining that the message sender and message type corresponds to a registered messaging campaign. For example, at step 1512, the gateway may look up the campaign identification for the given message in the campaign registry. If the campaign identification is found, the content (e.g., the “What” information) may be compared to the declared content type for the campaign, and captured by the campaign registry in structure 500 (FIG. 5)).

[096] It is contemplated that the steps or descriptions of FIG. 15 may be used with any other embodiment of this disclosure. In addition, the steps and descriptions described in relation to FIG. 15 may be done in alternative orders or in parallel to further the purposes of this disclosure. For example, each of these steps may be performed in any order or in parallel or substantially simultaneously to reduce lag or increase the speed of the system or method. Furthermore, it should be noted that in some embodiments, one or more steps of process 1500 may be combined with one or more steps in process 1400 (FIG. 4) and process 1600 (FIG. 16).

[097] FIG. 16 shows a flowchart of the steps involved in filtering messages distributed via telecommunications networks, in accordance with one or more embodiments. For example, process 1600 may be performed by one or more devices as described in FIGS. 1-13. For example, user interface 100 (FIG. 1) may be used to initiate process 1600. Process 1600 may then be executed by one or more devices as shown in system 500 (FIG. 5). In some embodiments, a user interface (e.g., user interface 100 (FIG. 1)) that is accessible to an end-user may be used to facilitate process 1600. [098] At step 1602, process 1600 receives a user input setting an end-user rule for messaging campaigns directed to an end-user. For example, the system may receive, at a campaign registry portal, a user input setting of an end-user rule for messaging campaigns directed to an end-user. For example, the system may receive the end-user setting via a user interface (e.g., user interface 100 (FIG. 1)) that is accessible by an end-user.

[099] At step 1604, process 1600 stores the end-user rule. For example, the system may store, at a campaign registry, the end-user rule. For example, the end-user may set rules related to “who” and/or “what” messages and/or messaging campaigns may be transmitted to the end-user. Additionally, the end-user may select and/or provide user consent, enter timing and data windows and/or deadlines for receiving messages and/or messaging campaigns, provide feedback on messages and/or messaging campaigns, respond to messages, edit preferences, and/or block messages and/or messaging campaigns.

[0100] For example, as the messaging industry has not traditionally used uniform definitions and that coupled with the fact that a single company can play multiple roles within a given service, an end-user may not be able to determine who sent a message, how to respond to the message, and/or how to provide feedback on the message. This functionality may be provided by the system.

[0101] At step 1606, process 1600 receives a request to generate a messaging campaign from a third-party entity. For example, the system may receive, at the campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user. For example, while the message may have been transmitted along a telecommunications network provided by numerous entities, and contact information of the end-user may not have been known by the third-party, the message may still appear as if it was transmitted to the end-user directly by the third-party. [0102] At step 1608, process 1600 compares the end-user rule to information about the message or messaging campaign. For example, the system may compare the end-user rule to information about the message (e.g., a message class, a source entity identification, and a campaign identification) or messaging campaign (e.g., a brand or other provider of the campaign). For example, the system may compare the qualification level of the message to that as set by the end- user. [0103] At step 1610, process 1600 determines that transmitting the message (or that the campaign) complies with the end-user rule based on the comparison. For example, the system may determine that transmitting the message or that the campaign complies with the end-user rule based on the comparison (e.g., the system may compare a message class, a source entity identification, or a campaign identification to an end-user rule indicating message classes, sources, or campaigns that may transmit messages to the user). In contrast, if the system determines that transmitting the message does not comply with the end-user rule based on the comparison, the system may block the message.

[0104] At step 1612, process 1600 causes the message to be transmitted via a telecommunications network to the end-user. For example, the system may cause the message to be transmitted via a telecommunications network to the end-user, wherein a campaign identification, provided by the campaign registry, is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user. For example, the messages may be sent (by an entity), and subsequently a gateway may verify that the message is compliant and may be delivered via the campaign registry. For example, the message may include a messaging container comprising a data structure (e.g., data structure 1300 (FIG. 13)) used to identify a messaging campaign, provide campaign registry information, and/or include information about a messaging campaign with the message.

[0105] It is contemplated that the steps or descriptions of FIG. 16 may be used with any other embodiment of this disclosure. In addition, the steps and descriptions described in relation to FIG. 16 may be done in alternative orders or in parallel to further the purposes of this disclosure. For example, each of these steps may be performed in any order or in parallel or substantially simultaneously to reduce lag or increase the speed of the system or method. Furthermore, it should be noted that in some embodiments, one or more steps of process 1600 may be combined with one or more steps in process 1400 (FIG. 4) and process 1500 (FIG. 15).

[0106] The above-described embodiments of the present disclosure are presented for purposes of illustration and not of limitation, and the present disclosure is limited only by the claims which follow. Furthermore, it should be noted that the features and limitations described in any one embodiment may be applied to any other embodiment herein, and flowcharts or examples relating to one embodiment may be combined with any other embodiment in a suitable manner, done in different orders, or done in parallel. In addition, the systems and methods described herein may be performed in real time. It should also be noted that the systems and/or methods described above may be applied to, or used in accordance with, other systems and/or methods.

[0107] The present techniques will be better understood with reference to the following enumerated embodiments:

1. A method for distributing messages via telecommunications networks, the method comprising: receiving, at a campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; receiving, at the campaign registry, first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message; generating, at the campaign registry, a campaign identification for the messaging campaign based on the first and second records; storing, at the campaign registry, the campaign identification; and generating metadata, at the campaign registry, for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

2. A method for providing a gateway for a telecommunications network, the method comprising: receiving, by an entity providing the telecommunications network, a message being transmitted from a third-party entity to an end-user according to a messaging campaign, wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; retrieving, from the message, a campaign identification for the messaging campaign, wherein the campaign identification is based on first and second records, stored in a campaign registry, corresponding to the messaging campaign, and wherein the first record identifies the third-party entity and the second record identifies a use case for the message; retrieving a transmission rule for transmissions to the end-user; and determining a qualification level for the message based on the transmission rule; determining, based on the qualification level, an amount of information about the third-party entity required to be accessible at the campaign registry to transmit the message; determining whether the amount of information is accessible at the campaign registry; in response to determining that the amount of information is accessible at the campaign registry, qualifying the message for transmission by the entity.

3. A method for filtering messages distributed via telecommunications networks, the method comprising: receiving, at a campaign registry portal, a user input setting an end-user rule for messaging campaigns directed to an end-user; storing, at a campaign registry, the end-user rule; receiving, at the campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end- user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; comparing the end-user rule to information about the message; determining that transmitting the message complies with the end-user rule based on the comparison; and causing, at the campaign registry, the message to be transmitted via a telecommunications network to the end-user, wherein a campaign identification, provided by the campaign registry, is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

4. The method of any one of the preceding embodiments, wherein the first record further identifies a messaging platform corresponding to the message, and wherein the second record further identifies an industry corresponding to the message.

5. The method of any one of the preceding embodiments, wherein the entity providing the telecommunications network comprises a direct connect aggregator or a mobile network operator.

6. The method of any one of the preceding embodiments, further comprising: receiving a data element from a direct connect aggregator or a mobile network operator; and in response to receiving the data element from the direct connect aggregator or the mobile network operator, activating the messaging campaign at the campaign registry.

7. The method of any one of the preceding embodiments, wherein the data element comprises a telephone number of the end-user.

8. The method of any one of the preceding embodiments, further comprising: receiving a transmission rule from the mobile network operator, wherein the transmission rule is based on the data element; and determining a qualification level for the message or campaign based on the transmission rule; determining, based on the qualification level, an amount of information about the third-party entity required to be accessible at the campaign registry to transmit the message; determining whether the amount of information is accessible at the campaign registry; in response to determining that the amount of information is accessible at the campaign registry, qualifying the message.

9. The method of any one of the preceding embodiments, further comprising validating the first record and corresponding to the third-party entity.

10. The method of any one of the preceding embodiments, further comprising: determining an end-user rule based on the data element, wherein the end-user rule was received via an input of the end-user through a campaign registry portal; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.

11. The method of any one of the preceding embodiments, further comprising: receiving, at a campaign registry portal, a user input setting an end-user rule for messaging campaigns directed to an end-user; storing, at the campaign registry, the end-user rule; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.

12. The method of any one of the preceding embodiments, wherein the message includes a message class, a source entity identification, and a campaign identification.

13. The method of any one of the preceding embodiments, wherein a campaign identification is included in a message container of the message or an online database.

14. A tangible, non-transitory, machine-readable medium storing instructions that, when executed by a data processing apparatus, cause the data processing apparatus to perform operations comprising those of any of embodiments 1-13.

15. A system comprising: one or more processors; and memory storing instructions that, when executed by the processors, cause the processors to effectuate operations comprising those of any of embodiments 1-13.

16. A system comprising means for performing any of embodiments 1-13.

Claims

WHAT IS CLAIMED IS:

1. A system for distributing messages, via telecommunications networks, featuring data structures that allow third-party entities along the telecommunications network to determine source information, telecommunication network infrastructure relationships, and metadata for the messages, the system comprising: cloud-based memory configured to a campaign registry; and cloud-based control circuitry configured to: receive a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end-user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; receive first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message; generate a campaign identification for the messaging campaign based on the first and second records; store the campaign identification; generate metadata for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end- user; receive a data element from a direct connect aggregator or a mobile network operator; activate the messaging campaign at the campaign registry in response to receiving the data element from the direct connect aggregator or the mobile network operator; and cloud-based I/O circuitry configured to: transmit the message via the telecommunications network to the end-user in response to activating the messaging campaign.

2. A method for distributing messages, via telecommunications networks, featuring data structures that allow third-party entities along the telecommunications network to determine source information, telecommunication network infrastructure relationships, and metadata for the messages, the method comprising: receiving, at a campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end- user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; receiving, at the campaign registry, first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message; generating, at the campaign registry, a campaign identification for the messaging campaign based on the first and second records; storing, at the campaign registry, the campaign identification; and generating, at the campaign registry, metadata for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

3. The method of claim 2, wherein the first record further identifies a messaging platform corresponding to the message, and wherein the second record further identifies an industry corresponding to the message.

4. The method of claim 2, wherein the entity providing the telecommunications network comprises a direct connect aggregator or a mobile network operator.

5. The method of claim 2, further comprising: receiving a data element from a direct connect aggregator or a mobile network operator; and in response to receiving the data element from the direct connect aggregator or the mobile network operator, activating the messaging campaign at the campaign registry.

6. The method of claim 2, wherein the data element comprises a telephone number of the end-user.

7. The method of claim 5, further comprising: receiving a transmission rule from the mobile network operator, wherein the transmission rule is based on the data element; determining a qualification level for the message based on the transmission rule; determining, based on the qualification level, an amount of information about the third- party entity required to be accessible at the campaign registry to transmit the message; determining whether the amount of information is accessible at the campaign registry; in response to determining that the amount of information is accessible at the campaign registry, qualifying the message.

8. The method of claim 2, further comprising validating the first record and corresponding to the third-party entity.

9. The method of claim 5, further comprising: determining an end-user rule based on the data element, wherein the end-user rule was received via an input of the end-user through a campaign registry portal; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.

10. The method of claim 2, further comprising: receiving, at a campaign registry portal, a user input setting an end-user rule for messaging campaigns directed to an end-user; storing, at the campaign registry, the end-user rule; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.

11. The method of claim 2, wherein the message includes a message class, a source entity identification, and a campaign identification.

12. A non-transitory computer-readable medium for distributing messages, via telecommunications networks, featuring data structures that allow third-party entities along the telecommunications network to determine source information, telecommunication network infrastructure relationships, and metadata for the messages comprising instructions that, when executed by one or more processors, cause operations comprising: receiving, at a campaign registry, a request to generate a messaging campaign from a third-party entity, wherein the messaging campaign comprises transmitting a message to an end- user, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user; receiving, at the campaign registry, first and second records corresponding to the messaging campaign, wherein the first record identifies the third-party entity and the second record identifies a use case for the message; generating, at the campaign registry, a campaign identification for the messaging campaign based on the first and second records; storing, at the campaign registry, the campaign identification; and generating, at the campaign registry, metadata for the message for transmission via a telecommunications network to the end-user, wherein the campaign identification is attached to the message in a format accessible to an entity providing the telecommunications network, and wherein the messaged is labeled as being transmitted from the third-party entity when received by the end-user.

13. The non-transitory computer-readable medium of claim 12, wherein the first record further identifies a messaging platform corresponding to the message, and wherein the second record further identifies an industry corresponding to the message.

14. The non-transitory computer-readable medium of claim 12, wherein the entity providing the telecommunications network comprises a direct connect aggregator or a mobile network operator.

15. The non-transitory computer-readable medium of claim 12, wherein the instructions further cause operations comprising: receiving a data element from a direct connect aggregator or a mobile network operator; and in response to receiving the data element from the direct connect aggregator or the mobile network operator, activating the messaging campaign at the campaign registry.

16. The non-transitory computer-readable medium of claim 15, wherein the data element comprises a telephone number of the end-user.

17. The non-transitory computer-readable medium of claim 15, wherein the instructions further cause operations comprising: receiving a transmission rule from the mobile network operator, wherein the transmission rule is based on the data element; determining a qualification level for the message based on the transmission rule; determining, based on the qualification level, an amount of information about the third- party entity required to be accessible at the campaign registry to transmit the message; determining whether the amount of information is accessible at the campaign registry; and in response to determining that the amount of information is accessible at the campaign registry, qualifying the message.

18. The non-transitory computer-readable medium of claim 12, wherein the instructions further cause operations comprising: validating the first record and corresponding to the third- party entity.

19. The non-transitory computer-readable medium of claim 15, wherein the instructions further cause operations comprising: determining an end-user rule based on the data element, wherein the end-user rule was received via an input of the end-user through a campaign registry portal; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.

20. The non-transitory computer-readable medium of claim 12, wherein the instructions further cause operations comprising: receiving, at a campaign registry portal, a user input setting an end-user rule for messaging campaigns directed to an end-user; storing, at the campaign registry, the end-user rule; comparing the end-user rule to information about the message; and determining that transmitting the message complies with the end-user rule based on the comparison.