A multi-tenant media communication platform system and methods. The platform system includes media communication micro-services and micro-service configuration for a plurality of entities configured for use of the platform system. Enrolling an entity in the platform system includes setting entity configuration for use of the platform system by the entity. A micro-service request is processed according to the entity configuration. The micro-service request is a request for use of at least one micro-service of the platform system on behalf of the entity. Use of each micro-service is accounted for on behalf of the entity. Billing information for the entity is generated based on the accounting for the use of each micro-service on behalf of the entity. Entity configuration includes micro-service configuration, and micro-service configuration specifies at least one of: an endpoint mapping to at least one application logic URI, an event callback URI, and an event application logic URI.

The disclosed system provides a facility for split billing for a single user on multiple billing systems. The disclosed system activates the user on each respective billing system using a unique pairing, such as an international mobile subscriber identity that identifies the user, and a mobile station international subscriber directory number that identifies a particular user device. As device data is routed through a telecommunication network via each access point name (APN), the network generates call detail records (CDRs), which include an indication of the APN used. The CDRs are routed to a mediations platform that uses the received APN information to route each CDR to the appropriate target billing system. For example, CDRs identifying a APN may be routed to a telematics billing system, which then generates a bill that is sent to a car dealership.

Example implementations relate to dynamically generating an aggregation routine. For example, a computing device may include a processor. The processor may receive a data record from a particular service source of a plurality of service sources in communication with the computing device. The data record may relate to usage of the particular service source. The processor may identify at least one field associated with the data record and convert the data record to a standardized record associated with metadata based on the at least one field. The standardized record may have a standardized record format. The processor may dynamically generate an aggregation routine based on the standardized record and the metadata associated with the standardized record. The aggregation routine may be used to calculate usage data associated with the usage of the particular service source.

Various methods for a 3GPP defined Charging and Collection Function are employed that may use a microservices approach. The microservice approach may decompose the function of the network elements into component level functions that may be deployed as separate functional elements.

A method for identifying communicators as wanted or unwanted based on messages from such communicators comprising receiving, by the data processing system, an inbound message from a communicator, comparing, by the data processing system, the inbound message to fingerprints stored in a database accessible to the data processing system, determining, by the data processing system, at least one match to the fingerprints, determining, by the data processing system, an identity of the communicator by determining whether and how likely the communicator is wanted or unwanted based on the at least one match to the fingerprints, and configuring, by the data processing system, handling of calls from the communicator based on the identity.

The present invention provides a data management apparatus for managing a plurality of data items output by a plurality of communication devices that output data. The data management apparatus includes a storage section configured to store device identification information of each of the plurality of communication devices in association with charge identification information including either contractor identification information of a contractor of a contract for using a relay apparatus that is configured to transfer the plurality of data items to the data management apparatus or acquirer identification information of a data acquirer who acquires the data from the data management apparatus, and a charge amount determination section configured to determine a charge amount for each item of the charge identification information on the basis of data communication traffic volumes corresponding to data output from the communication devices of one or more device identification information items stored in association with the charge identification information.

A method for monitoring and controlling session traffic usage, includes: receiving traffic usage increment information of a first session and a second session reported by a first PCF and a second PCF; accumulating a total traffic usage of the first session and the second session according to the received traffic usage increment information; determining whether a current total traffic usage reaches a threshold value of a total issued traffic usage; and sending the total traffic usage information of the first session and the second session to the first PCF and the second PCF in response to that the current total traffic usage reaches the threshold value of the total issued traffic usage and in response to that the current total traffic usage does not reach the threshold value of the total issued traffic usage, repeating above steps.

One or more computing devices, systems, and/or methods for performing entity actions based upon inputs received via email interfaces are provided. For example, an email received by an email account may be identified. The email may be associated with an entity action corresponding to a first entity. A selectable input corresponding to performing the entity action may be displayed via an email interface associated with the email account. A request to perform the entity action may be received via a selection of the selectable input. Responsive to receiving the request, an action interface corresponding to performing the entity action may be displayed within the email interface. One or more inputs associated with the entity action may be received via the action interface. Responsive to determining that the entity action is completed, a confirmation message, indicative of the entity action being completed, may be displayed using the email interface.

A system for tracking telephone calls made in response to advertising campaigns in electronic or other media is provided. The system permits an advertiser to associate specific and distinct telephone numbers with associated advertising campaigns. The system further modifies advertiser-provided information in response to the advertising campaign to which a potential customer responds, and includes the associated telephone number in the modified advertiser information. The system processes telephone calls made to the selected telephone numbers, and provides reports to advertisers of call data associated with the respective advertising campaigns.

A method and apparatus are described for supporting a two-stage device-to-device (D2D) discovery using a D2D interworking function (IWF). A D2D IWF component may be configured to perform mapping between an application running on an application server and a third generation partnership project (3GPP) network, and provide a set of application programming interfaces (APIs) to allow discovery to be provided as a service to D2D applications. An application identifier may be mapped to a 3GPP identifier. Further, a method and apparatus are described for performing client-server discovery. A first wireless transmit/receive unit (WTRU) may be configured for a listen-only operation, and a second WTRU may be configured to transmit beacons. The first and second WTRUs may perform a radio access network (RAN) discovery procedure at an access stratum (AS) layer. A method and apparatus for performing charging for D2D service using a D2D IWF are also described.