WO2022038455A1 - Système et procédé de fourniture de produit d'utilisation de réseau - Google Patents

Système et procédé de fourniture de produit d'utilisation de réseau Download PDF

Info

Publication number
WO2022038455A1
WO2022038455A1 PCT/IB2021/057246 IB2021057246W WO2022038455A1 WO 2022038455 A1 WO2022038455 A1 WO 2022038455A1 IB 2021057246 W IB2021057246 W IB 2021057246W WO 2022038455 A1 WO2022038455 A1 WO 2022038455A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscriber
network usage
mobile subscriber
prepaid mobile
data
Prior art date
Application number
PCT/IB2021/057246
Other languages
English (en)
Inventor
Antonios CHATZISTAMATIOU
Stelios LELIS
Original Assignee
Channel Technologies Fze
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Channel Technologies Fze filed Critical Channel Technologies Fze
Priority to MX2023000817A priority Critical patent/MX2023000817A/es
Publication of WO2022038455A1 publication Critical patent/WO2022038455A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/852—Low balance or limit reached
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/88—Provision for limiting connection, or expenditure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/90—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H04M17/02—Coin-freed or check-freed systems, e.g. mobile- or card-operated phones, public telephones or booths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • a “prepaid mobile subscriber” may be any user of a prepaid mobile communication service hosted on a mobile telephone network.
  • the prepaid mobile subscriber may have a communication device with which the prepaid mobile subscriber may be able to conduct telephonic transactions such as making phone calls, sending short messaging service (SMS) messages, using mobile data and the like.
  • SMS short messaging service
  • the conducting of transactions over a mobile telephone network incurs charges for the subscriber. These charges may be debited against an account (which may be an airtime account) associated with the subscriber. Typically, on prepaid accounts, the prepaid services require the balance of the subscriber’s airtime account to be positive for the subscriber to be able to conduct telephonic transactions.
  • the positive balance of a prepaid subscriber’s airtime account is typically colloquially referred to as “airtime”.
  • subscribers may choose to purchase mobile bundles such as SMS, data or voice minute bundles using their airtime or through other mechanisms. Each mobile bundle is associated with a particular category of mobile telephone network utilisation, such as sending SMSs, sending and receiving data packets or making telephone calls.
  • Mobile bundles are typically associated with a usage limit, such as 30 SMSs, 500 MB of data or 100 voice minutes, which may be recorded against a bundle account associated with the respective category of utilisation.
  • a usage limit such as 30 SMSs, 500 MB of data or 100 voice minutes.
  • Utilisation of the mobile telephone network in a particular category may be recorded against (or deducted from) the relevant mobile bundle usage limit stored in the relevant bundle account, as opposed to being deducted from the subscriber’s airtime account.
  • a mobile bundle’s usage limit has been reached, further utilisation of the mobile telephone network within that category might be deducted from the subscriber’s positive airtime account approaches or reaches zero, the subscriber may be barred from conducting further telephonic transactions.
  • an airtime top-up may be performed by, for example, purchasing vouchers or tokens which can be input or redeemed for an amount of airtime.
  • Mobile bundles may be subsequently purchased using the airtime or may be purchased using special tokens.
  • a subscriber is unable to purchase vouchers or tokens to top-up the balance of the subscriber’s account or to purchase further mobile bundles after depletion.
  • “out of bundle” utilisation of the mobile telephone network in a particular category may be automatically applied and/or may incur much higher costs than “in bundle” utilisation. This may lead to unsuspecting subscribers having their airtime depleted rapidly as they continue to utilise the mobile telephone network in categories for which associated mobile bundles have been depleted. This may leave subscribers without means to conduct further telephonic transactions until they are able to purchase airtime vouchers or tokens. There is accordingly scope for improvement.
  • the preceding discussion of the background to the invention is intended only to facilitate an understanding of the present invention.
  • a computer-implemented method comprising: retrieving data points associated with a prepaid mobile subscriber including a subscriber profile having been output by a data processing system retrieving and processing features relating to the prepaid mobile subscriber from one or more data stores, wherein one of the data stores includes a category of transactional records associated with the prepaid mobile subscriber; determining subscriber eligibility for a network usage product based on the data points; and, interacting with an intelligent network of a mobile telephone network to provision the network usage product to an account associated with the prepaid mobile subscriber.
  • the method may include determining a value associated with the network usage product for which the prepaid mobile subscriber is eligible, including retrieving or determining a total credit limit value based on the data points, and including storing the credit limit value in a field of a subscriber record configured for querying before provisioning the network usage product.
  • the method may include storing the subscriber eligibility in a field of a subscriber record configured for querying before provisioning the network usage product.
  • the method may include: receiving a payload from a software application executing on a communication device associated with the prepaid mobile subscriber, wherein the payload includes data elements obtained from the communication device; and, extracting the data elements from the payload and storing them in a subscriber record, wherein retrieving data points associated with the prepaid mobile subscriber includes retrieving the extracted data elements from the subscriber record.
  • Retrieving data points associated with the prepaid mobile subscriber may include retrieving a net present value associated with a communication device associated with the prepaid mobile subscriber, including retrieving the net present value from a table maintained by a mobile network operator.
  • the subscriber profile may change over time in response to changes in transactional records associated with the prepaid mobile subscriber, and wherein the method includes retrieving an updated subscriber profile and determining one or both of an updated subscriber eligibility and an updated total credit limit value based on the updated subscriber profile.
  • the provision of the network usage product to the account associated with the prepaid mobile subscriber may be associated with a predefined condition, wherein the method includes: monitoring one or both of the account and subscriber record for fulfilment of the predefined condition; and, if non-compliance with the predefined condition is detected, transmitting a lock instruction to an EMM module executing on a communication device associated with the prepaid mobile subscriber and configured to lock or disable predefined functionality on the communication device.
  • the method may include transmitting a network usage product offer message to a communication device associated with the prepaid mobile subscriber, wherein the network usage product offer message includes a list of pre-approved amounts based on a value of the network usage product for which the prepaid mobile subscriber is eligible, and wherein transmitting the network usage subscriber based on one or more of: the subscriber eligibility and the subscriber profile, wherein generating dynamic USSD menus includes personalizing one or both of USSD pages and tree structures based on information unique to the prepaid mobile subscriber.
  • the network usage product may be a network usage advance, such as an airtime advance or bundle advance which is provisioned to the account associated with the prepaid mobile subscriber in advance of received payment from the prepaid mobile subscriber.
  • a system including a memory for storing computer-readable program code and a processor for executing the computer- readable program code, the system comprising: a data point retrieving component for retrieving data points associated with a prepaid mobile subscriber including a subscriber profile having been output by a data processing system retrieving and processing features relating to the prepaid mobile subscriber from one or more data stores, wherein one of the data stores includes a category of transactional records associated with the prepaid mobile subscriber; a subscriber eligibility component for determining subscriber eligibility for a network usage product based on the data points; and, an IN-integration component for interacting with an intelligent network of a mobile telephone network to provision the network usage product to an account associated with the prepaid mobile subscriber.
  • a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: retrieving data points associated with a prepaid mobile subscriber including a subscriber profile having been output by a data processing system retrieving and processing features relating to the prepaid mobile subscriber from one or more data stores, wherein one of the data stores includes a category of transactional records associated with the prepaid mobile subscriber; determining subscriber eligibility for a network usage product based on the data points; and, interacting with an intelligent network of a mobile telephone network to provision the network usage product to an account associated with the prepaid mobile subscriber.
  • Figure 1 is a schematic diagram which illustrates an exemplary system for network usage product provisioning according to aspects of the present disclosure
  • Figure 2 is a flow diagram which illustrates an exemplary method for network usage product provisioning according to aspects of the present disclosure
  • Figure 3A is a flow diagram which illustrates an exemplary method for network usage product provisioning including updating subscriber eligibility and/or credit limit values based on a changing subscriber profile
  • Figure 3B is a flow diagram which illustrates an exemplary method according to aspects of the present disclosure
  • Figure 4 is a block diagram which illustrates exemplary components which may be provided by a system for network usage product provisioning according to aspects of the present disclosure
  • Figure 5 illustrates an example of a computing device in which various aspects of the disclosure may be implemented.
  • aspects of the present disclosure provide an airtime and mobile bundle (collectively “network usage”) advance service platform (ASP).
  • the ASP provides a value-added service, termed “network usage advance service” to eligible prepaid subscribers of a mobile telephone network.
  • a network usage advance may be a provision of services before payment has been received or in advance of payment in a prepaid model.
  • a network usage advance may for example enable mobile telephone network usage by an associated prepaid mobile subscriber in advance of received payment from that prepaid mobile subscriber.
  • the ASP may thus be configured to provision an amount of airtime (termed “an amount of airtime advance”) and/or mobile bundles to a prepaid mobile subscriber in advance of received payment (i.e.
  • embodiments of the present disclosure may allow a prepaid mobile subscriber (hereafter “subscriber”) having insufficient airtime to make and complete an urgent telephone call or otherwise use the mobile Transactions that may be performed or conducted on a mobile telephone network may be categorised according to the manner in which the mobile telephone network is utilised. Different categories of utilisation may include SMS messaging, data utilisation (e.g. internet browsing, etc.), making and receiving voice calls, unstructured supplementary service data (USSD) sessions and the like.
  • SMS messaging SMS messaging
  • data utilisation e.g. internet browsing, etc.
  • USSD unstructured supplementary service data
  • airtime advance may include any credit transaction made against an account associated with a subscriber by a mobile network operator (MNO) or other appropriate service provider on behalf of the subscriber so as to increase a balance of an account (typically an airtime account dedicated to receiving the airtime advance) associated with the subscriber.
  • An “airtime advance” may be a loan of an amount of airtime made to the subscriber by an MNO and which the subscriber is obliged to pay back at a later stage.
  • mobile bundle advance may include the on-credit (i.e. ahead of payment) provisioning of a usage limit in respect of one or more categories of mobile telephone network utilisation.
  • mobile bundle advance may include the on-credit provisioning of a usage limit in respect of one or more categories of mobile telephone network utilisation for pre- paid (as opposed to post-paid or contract) subscribers.
  • Exemplary categories of utilisation may include sending SMS messages, transmitting and receiving data messages and making voice calls.
  • the usage limit associated with each category of utilisation may for example be a number of SMS messages, an amount of data (e.g. in bytes) and a number of minutes for which voice calls may be made.
  • Airtime advance and mobile bundle advances may be collectively referred to as network usage advances.
  • FIG. 1 is a schematic diagram which illustrates an exemplary system (100) for network usage product provisioning according to aspects of the present disclosure.
  • Network usage products include network usage advances, such as airtime and bundle advances.
  • the system (100) may include a service provider platform (102) and an MNO platform (104).
  • the MNO platform (104) may be provided by a mobile network operator (MNO).
  • the service provider platform (102) may be provided by a third-party service provider which provides network usage advance services to the MNO and its prepaid subscribers. In other implementations, the service provider platform (102) may be built-in to or integrated with the MNO platform (104) (without the need for a third-party service provider).
  • the system (100) may further include a communication device (106) associated with an entity, such as a mobile handset associated with a prepaid mobile subscriber, who typically purchases airtime and mobile bundles to make use of a mobile telephone network (110) provided by the MNO. Although only one communication device (106) is illustrated, it should be appreciated that in a practical implementation there may be a plurality of each of these.
  • the MNO platform (104) and mobile telephone network (110) may collectively provide the infrastructure by way of which communication devices (106) can communicate with each other and the broader public switched telephone network (PSTN) and the Internet.
  • the mobile telephone network (110) may for example include one or more base station subsystems while the MNO platform (104) may provide back-end systems such as a USSD/GPRS gateway, SMSC and associated components (VLR, HLR, etc.).
  • the MNO platform (104) may include a prepaid gateway (113), an intelligent network (IN) (114) and a charging system (116).
  • the prepaid gateway (113) may be configured, amongst other things, to detect requested usage of the mobile telephone network by a subscriber associated with a subscriber identifier, to capture information associated with the requested usage, such as the subscriber identifier, to transmit the captured information to the charging system (116), to receive permitted usage information from the charging system (116), to permit and monitor usage of the network (110) in accordance with the permitted usage information and to report actual usage information to the charging system (116).
  • the IN (114) may be implemented according to any suitable network architecture (e.g. that specified in the ITU-T Q.1200 series recommendations, or the like).
  • the IN (114) may allow the MNO to provide various value-added services, such as network usage advance services, in addition to the standard telecom services such as PSTN, GSM, etc.
  • the IN (114) may include one or more network nodes on the service layer, distinct from the switching layer of the core network, as opposed to solutions based on intelligence in the core switches or equipment.
  • the IN (114) may be supported by the Signalling System #7 (SS7) protocol between network switching centres and other network nodes owned by network operators. for collecting data on service usage and to generate reports thereon for billing, either on demand or automatically.
  • the charging system (116) may be an online charging system (OCS).
  • the charging system (116) may be configured to authenticate and authorize network usage requests associated with subscriber identifiers received from the prepaid gateway (113), determine and transmit permitted usage information (such as a maximum call duration, etc.) to the prepaid gateway (113) and to receive and charge the subscriber in accordance with actual usage information from the prepaid gateway (113).
  • the charging system (116) may be implemented as or have access to a high-throughput database that maintains multiple accounts for each subscriber. The purpose, type and usage of the accounts may be defined by the MNO, in some cases upon request by the service provider.
  • Each subscriber may be associated with one or more of: a main account, a dedicated account, a premium dedicated account, a loan tracking account (also referred to as a principal tracking account) and a fee tracking account.
  • a main account a dedicated account
  • a premium dedicated account a loan tracking account
  • a fee tracking account a loan tracking account
  • Different implementations may require the provision of different accounts.
  • These accounts may be airtime accounts in that their value is denominated in airtime (which is typically equivalent to a value of currency, such as ZAR, USD, NGN, etc.).
  • Each subscriber may further be associated with one or more data bundle, SMS bundle and voice minute bundle accounts which accounts may have their values denominated in bytes, a number of SMS messages and a number of minutes and seconds, respectively.
  • Airtime top-ups may be provisioned to the main account and usage of the mobile telephone network (110) (such as making phone calls, sending SMS messages, transmitting and receiving data packets) by the subscriber may typically be charged against the main account.
  • Network usage advances (such as airtime advances) may be provisioned to one of: the main account, the dedicated account or, in some implementations, the premium dedicated account depending on a network usage advance service class (referred to herein as a service class) with which the subscriber is associated. Once the network usage advance has been provisioned, further use of the mobile telephone network may be charged against the account to which the network usage advance was provisioned until the balance thereof has been depleted.
  • Data bundles purchased by the subscriber may be provisioned to a main data bundle account after which the transmission and reception of data packets by the subscriber’s communication device (106) via the mobile network (110) may be recorded (or deducted from) the main data bundle account.
  • Data bundle advances may be provisioned either to the main data bundle account or, in some implementations, to a dedicated data bundle account. Once provisioned, further transmission/reception of data packets may be recorded against the main data bundle account or the dedicated data bundle account, as the case may be, until the balance thereof has bundle accounts.
  • the tracking accounts may be used to keep track of amounts owed by subscribers in respect of network usage advances that the subscribers have requested and received.
  • a non-zero balance of any one of the tracking accounts may indicate an outstanding network usage advance.
  • the value or amount of balance may indicate the amount in respect of the network usage advance owed by the subscriber.
  • a single tracking account may be provided for tracking outstanding amounts of all types of network usage advances provided to the subscriber.
  • the accounts described herein may be implemented as fields of a high-throughput database. The fields may be associated with a subscriber identifier and can be updated or modified in real-time in response to network usage or top-up events. Different fields of the database may represent different accounts associated with a particular subscriber.
  • the charging system (116) may include or be embodied by a data structure, such as a table maintained by relational database management system (RDBMS), having rows which are associated with subscribers (identified by way of a subscriber identifier, such as an MSISDN or other suitable identifier) and columns which are associated with account identifiers which identify and correspond to different types of accounts, such as each of the respective accounts described in the foregoing.
  • RDBMS relational database management system
  • the charging system (116) may have access to and/or maintain a rating tariff table (117) in which different types of accounts are associated with different tariffs.
  • the rating tariff table (117) may associate a subset of the above accounts (i.e.
  • the charging system (116) and/or IN (114) may therefore be configured to apply different tariffs to different accounts. For example, as mentioned above, usage of the mobile telephone network (110) by the subscriber may be charged against any one of the subscriber’s: main account, dedicated account, or premium dedicated account. However, the tariff applied to or charged for such usage may differ based on the account that is being charged.
  • the charging system (116) and/or IN (114) may be configured to apply first tariff data in respect of usage recorded against a main account or the dedicated account.
  • the IN (114) and/or charging system (116) therefore maintains different accounts for the same subscriber which are configured for provision of different classes or types of network usage advance service (e.g. by virtue of the different tariffs).
  • the MNO platform (104) may include a front-end API (126) by way of which the service provider platform (102) may interface with components or nodes of the MNO platform (104), such as the charging system (116).
  • the front-end API (126) may interface with or provide access to an IN- integration component for aspects of the interface.
  • the MNO platform (104) may include a communication gateway (144) which may for example include the GPRS/USSD gateway which facilitates the exchange of USSD messages between subscribers and various applications.
  • the communication gateway (144) and/or GPRS/USSD gateway may expose an API (e.g. one or more of SMPP, ParlayX, a proprietary HTTP-based API or the like).
  • the service provider platform (102) may be provided by any suitable computing device or devices.
  • the service provider platform (102) may be configured to interface with the MNO platform (104).
  • the service provider platform (102) may be configured to interface with the intelligent network (IN) (114) and/or charging system (116) of the MNO platform (104) via an appropriate IN integration component (114A).
  • the service provider platform (102) may include a subscriber channel (121) for interfacing with the mobile telephone network (110) and in turn the communication devices (106).
  • the service provider platform (102) may transmit and receive data and/or messages to and from the respective communication devices (106) via the subscriber channel (121) and the mobile telephone network (110).
  • the service provider platform (102) may for example be configured to receive network usage advance requests from the communication devices (106) and to transmit notifications relating to network usage advances to the communication devices (106).
  • the subscriber channel (121) may for example include an SMSC integration component (121A) and a USSD integration component (121B), which may provide a USSD gateway adapter which may be configured to interface with (e.g. consume) one or more APIs provided by the communication gateway (144) of the mobile operator platform (104).
  • the subscriber channel menus unique to the subscriber based on, for example, the subscriber eligibility, the subscriber profile (described in greater detail below) and the like.
  • the menu-tree dialog module (121C) may be configured to manage the lifecycle of a USSD, SMS, IVR, etc.
  • the USSD gateway adapter of the USSD integration component (121B) may be configured to connect with a communication gateway (144) of the mobile operator platform (104) to send and receive USSD messages.
  • the USSD gateway adapter may for example be configured to: translate different APIs to a common internal representation for USSD messages and vice versa; route incoming USSD messages (e.g.
  • USSD sessions may be menu-based, allowing subscribers to browse through different options associated with network usage advances.
  • the service provider platform (102) may for example be configured to request the subscriber to input his or her preferred language.
  • the service provider platform (102) may further be configured to generate dynamic USSD menus which are uniquely associated with the subscriber (e.g. which display amounts, usage limits and values which are based on the subscriber profile and/or eligibility).
  • the service provider platform (102) may be configured for communication of subscriber requested amounts of network usage advance by way of USSD short codes; i.e. subscribers may request an airtime advance by using a predefined short code (e.g. *123#) together with the network usage advance amount requested (e.g. USD10) by using the USSD short code *123*10#.
  • the subscriber channel (121) and its associated components and modules may be configured to provide functionality which allows subscribers to: check their network usage advance balance (which could be different from the main airtime account balance); check the transaction history; check their status: e.g.
  • each subscriber record (124) associated with each subscriber is stored.
  • Each subscriber record (124) may include and be associated with a subscriber identifier, such as an MSISDN or a derivative thereof.
  • each subscriber record (124) includes data points associated with the subscriber including, for example, one or more sets of credit data, such as an outstanding network usage advance status, a network usage advance eligibility, a total credit limit and a service class assignment (i.e. an indication of a service class to which the subscriber has been assigned), which may make up or be included in the subscriber profile.
  • the total credit limit may be a total credit limit value denominated in a value of airtime or local currency.
  • the credit limit value represents a value of a network usage advance for which a subscriber associated with the subscriber identifier is eligible in advance of payment.
  • Each subscriber record (124) may additionally store identifiers of accounts which are associated with the subscriber.
  • the subscriber record may for example include account identifiers for each of: the main account, dedicated account, premium dedicated account, loan tracking account and fee tracking account.
  • Each subscriber record may additionally store an association or linking of each of the account identifiers to one or more service classes. For example, the premium dedicated account may be associated with a first service class while the dedicated account and fee tracking account may be associated with a second service class.
  • Each subscriber record (124) may additionally store data elements received from a communication device associated with the relevant subscriber, such as a device identifier, software application identifier and the like. Each subscriber record may further store other information unique to the subscriber, such as a subscriber's name, national identity number, menu browsing pattern built up over time, spoken language, preferences and the like.
  • the service provider platform (102) may have access to a service class assignment data structure (128) in which each service class is linked to corresponding service class data (such as account identifiers and/or tariff data) and associated rules for provisioning in accordance with the service class (e.g. which accounts to adjust, how to adjust them, which tariffs to apply, etc.).
  • the service provider platform (102) may include or have access to a data processing system (130) configured for large-scale processing of data records.
  • the data processing system (130) may include a data receiving component (132) for receiving raw data records including a first type of data records having static values (e.g. customer demographic records such as Know Your Customer (KYC) records) and a second type of data records relating to transactional records with timestamps of events (e.g. Call Detail Records (CDR)).
  • the raw data records relate to telecommunications and the entities are subscribers.
  • the first type of data records are subscriber data records with static values of subscriber attributes and the second type of data records are call detail records of events.
  • the data processing system (130) may include a transforming component for transforming data records to standardized formats.
  • the data processing system (130) may include a filtering component (136) for filtering relevant data records.
  • the filtering component applies filtering rules to extract relevant records from transactional records including one or more of the group of: records relating to events including: calls; messages; monetary events; data usage events; lifecycle events; advance usage events; loan events; mobile wallet events and the like.
  • the data processing system (130) may include a data store persisting component (138) for persisting the transformed data records into two different data stores, including a first data store (140) for static data relating to subscribers for retrieval based on static values including a unique identifier of a subscriber, and a second data store (142) for transactional data (including transactional records) for retrieval based on timestamps of events.
  • the first data store (140) may be configured for efficient retrieval based on static values (such as unique identifier). For example, the first data store (140) may be configured to store information using the unique identifier of the subscriber as a key so as to enable efficient retrieval of the subscriber’s static data.
  • the second data store (142) is partitioned for time periods and/or by type of event.
  • the second data store (142) may be configured for efficient retrieval based on timestamps of events.
  • the second data store (142) may be configured to store information using the timestamp of the transactional records as a key. Storing information with only the timestamp as the key may enable efficient retrieval of transactional data for a batch of entities, or all subscribers.
  • the second data store (142) may be configured to store information using the timestamp of the transactional records and the unique identifier of the subscriber as a key (e.g. a compound key). This may enable efficient retrieval of transactional data per entity. In either of the two examples above, the retrieval of transactional data per entity, or entities, at different points in time and as new transactional data are continuously added, and the subsequent creation of features based on this transactional data, may be very efficient.
  • the data processing system (130) may include a unique identifier component (145) for generating a unique identifier for each subscriber as a combination of a Mobile Station International Subscriber Directory Number (MSISDN) and a Subscriber Identity Module (SIM) activation date.
  • MSISDN Mobile Station International Subscriber Directory Number
  • SIM Subscriber Identity Module
  • the data processing system (130) may include a subscriber profile component (150) for retrieving features relating to a subscriber from the data stores for processing to provide an output relating to the subscriber.
  • An output relating to the subscriber may include a subscriber profile.
  • An output relating to the subscriber may include a list with subscriber identifiers and credit data such as one or more of credit scores, credit limits, outstanding network usage advances, subscriber eligibility and optional additional information.
  • the output may be an extraction of potential borrowers’ profiles, development of credit scoring models, and methods of credit scoring subscribers and assigning credit limits.
  • the subscriber profile may be a collection of aggregate and static values derived from the subscriber data processed by the data ingestion components described above. These values may be called features and describe the subscriber’s behaviour given a reference time point.
  • the subscriber profile may be in the format required for credit risk analysis and limit assignment.
  • the features may be aggregates of transactional events (recharges, advances, etc.), categorical and cardinal features based on KYC, and several combinations of these.
  • the features may describe several dimensions of subscriber behaviour on different time frames. Dimensions of user behaviour may include recency, loyalty, frequency, aggregates of amounts and durations. The dimensions may also include minimum, maximum, counts, means, standard deviations, medians, quartiles and trends of counts, amounts, duration, ratios and average amounts and activity. Time frames, at which dimensions may be expressed before the reference point may be, for example, recent weeks, fortnights, months, quarters, semesters and/or years. In addition, several features may describe the dimensions across the full duration of a service/product usage by the subscriber. A subscriber profile is unique to the associated subscriber and may indicate the credit risk associated with the subscriber.
  • the subscriber profile component (150) may include feature generation with dimensions of behaviour of the subscriber at a given reference point in time, including: a feature retrieving component for retrieving features from different tables; a feature joining component for joining the features; and a feature transforming component for transforming the features to the reference point in time.
  • the subscriber profile component (150) may have and may be configured to access and replace the subscriber profiles of individual subscriber records with updated subscriber profiles as may be required.
  • the subscriber profile may be an indication of credit worthiness or an indication of the risk associated with the subscriber.
  • the data processing system (130) may be configured to receive and process raw data records continuously to update the data stores and tables for continually processing by the subscriber profile component for outputting updated subscriber profiles.
  • the subscriber communication device (106) may be any suitable computing device with a communication functionality, such as a mobile phone or mobile handset.
  • the communication device (106) may be associated with a device identifier which uniquely identifies the communication device (106), such as an IMEI or the like.
  • the communication device (106) includes an enterprise mobility module (EMM) module (119) configured for remote control, and particularly remote locking or disabling, of the communication device by an authorised enterprise, such as the service provider.
  • EMM enterprise mobility module
  • the various gateways of the mobile operator platform (104) interface with corresponding components of the service provider platform (102) so as to provide a level of integration between the two.
  • the service provider platform (102) may transmit notifications to and receive requests from the subscriber via the mobile operator platform (104) and its associated infrastructure. Furthermore, the service provider platform (102) may interact with the mobile operator platform (104), for example, to access and/or update or manipulate account information of an account associated with the subscriber.
  • the system (100) described above may implement a method for network usage product provisioning.
  • An exemplary method for network usage product provisioning is illustrated in the flow diagram of Figure 2. The method may be conducted by the service provider platform (102) or one or more computing devices thereof.
  • the network usage product is a network usage advance.
  • the method may include receiving (202) a network usage advance trigger.
  • aspects of the present disclosure anticipate various network usage advance triggers, including, for example receiving a request for the network usage advance from a communication device (106) of the subscriber; receiving an attempted transaction notification from a mobile network operator (e.g. generated by the prepaid gateway and/or charging system) indicating that a balance of an account associated a phone call or send a message); the method automatically determining that the balance of an account associated with the subscriber has reduced to a predetermined low level, and the like.
  • Requests for a network usage advance may be received via SMS message, USSD message, interactive voice response (IVR) message, application data message and the like.
  • a request for the network usage advance received from the subscriber communication device (106) may include a subscriber requested amount.
  • the request may be received via a USSD session which may have been initiated using a USSD short code including the subscriber requested amount, for example *123*20#, where ‘20’ is the amount of airtime advance being requested.
  • the subscriber may be offered a network usage advance should the balance of an account associated with the subscriber reduce to a predetermined low level.
  • Exemplary accounts which may be monitored include an airtime account (e.g. main airtime account) and one or more bundle accounts (e.g. SMS bundle account, data bundle account, voice minute bundle account, etc.).
  • the method includes retrieving (203) data points associated with a subscriber.
  • the retrieved data points include one or more of: a subscriber profile; a subscriber eligibility; a credit limit value; other relevant credit data; a net present value (NPV) of a subscriber communication device (106); and, data points received from the subscriber communication device (106).
  • the subscriber profile may be output by a data processing system (130) retrieving and processing features relating to the subscriber from one or more data stores (140, 142), including for example a table (148) which includes a category of transactional records.
  • the data stores (140, 142) may be configured for efficient retrieval, as described above.
  • the data points may be retrieved from a subscriber record (124) which is uniquely associated with the subscriber.
  • Retrieving the data points may include querying a subscriber database (122) using a subscriber identifier to identify a subscriber record from where the data points are to be retrieved.
  • the method may include determining (204) whether the subscriber is eligible for a network usage advance. This may include determining subscriber eligibility for the network usage advance based on the data points. Subscriber eligibility may be a binary field, for example, ‘yes’ or ‘no’ (or ‘eligible’ and ‘ineligible’), which indicates whether or not the subscriber is eligible for the network usage advance. Determining subscriber eligibility may include querying the value of a subscriber eligibility field in a subscriber record (124) associated with the subscriber. In some cases, e.g.
  • the field may be blank, and determining subscriber eligibility may include using other data points, such as the subscriber profile, to calculate or otherwise some cases, this may for example include inputting the subscriber profile into an eligibility determining algorithm. In other cases, this may for example include inputting the subscriber profile into a credit scoring algorithm which outputs a credit score based on the subscriber profile, and basing eligibility on the resulting credit score. Eligibility may be contingent on values of other data points too, for example, communication device NPV, subscriber age, the presence of outstanding network usage advances or the like.
  • Determining subscriber eligibility using the data points may include inputting the data points into an eligibility algorithm that outputs an eligibility based on the inputs and storing or updating the subscriber eligibility in a field of a subscriber record configured for querying before provisioning the network usage product.
  • Determining (204) whether the subscriber is eligible for a network usage advance may include requiring the subscriber to be part of an eligible subscriber base.
  • the method may include determining (206) a value associated with the network usage advance for which the subscriber is eligible. In the case of an airtime advance, the value associated with the network usage advance may be an amount of airtime to be advanced, which may be denominated in a local currency.
  • This may include processing the data points including the subscriber profile to determine the credit limit value. In other cases, this may include determining the credit limit value based on a credit score. In some embodiments, the credit limit value may be based on an NPV associated with the subscriber communication device (106). The value associated with the network usage advance for which the subscriber is eligible may be based on the credit limit value. In some implementations, the method may include transmitting (208) a network usage advance offer message to a communication device (106) of the subscriber. In the case of a low balance trigger, the message may for example read “Your balance is low! Get an airtime advance of ⁇ AMOUNT ⁇ and pay back on your next recharge.
  • the network usage advance offer message may include a list of pre-approved amounts based on the value of the network usage advance for which the subscriber is eligible.
  • the list of pre-approved amounts may be based on the subscriber profile and may include a maximum amount based on the value associated with the network usage advance for which the subscriber is determined to be eligible and one or more lesser amounts. For example, in the case of an airtime advance, the maximum amount and the value associated with the network usage advance for which the subscriber is determined to be eligible may be the same (e.g. USD20 of airtime).
  • the maximum amount may be a usage limit (e.g.50 GB) having a value which is equal to the value of network usage advance for which the subscriber is determined to be eligible (e.g. USD20).
  • the network usage advance offer message may be transmitted to the subscriber in an SMS message, USSD message, IVR message, application notification message or the like.
  • the list of pre-approved amounts may be presented to the subscriber for selection and acceptance of one of the amounts or rejection of all of the amounts.
  • Transmitting the network usage advance offer message may include generating (209) dynamic menus unique to the subscriber based on, for example, the subscriber eligibility, the subscriber profile and the like. This may include personalizing pages (and tree structure) based on information unique to the subscriber (e.g.
  • the method may include receiving (210) an indication of a subscriber preferred amount from the communication device (106) of the subscriber.
  • the subscriber preferred amount may have been selected by the subscriber from the list of pre-approved amounts.
  • the indication of the subscriber preferred amount may be received via an SMS message or application notification message or via a USSD or IVR session or the like.
  • the method includes interacting (211) with an intelligent network (114) of a mobile telephone network (110) to provision the network usage advance to an account associated with the subscriber.
  • This may include, if the subscriber is eligible for the network usage advance, crediting (212) an account associated with the subscriber with a credit amount.
  • the credit amount may be subscriber preferred amount is received, the credit amount may be the subscriber preferred amount.
  • crediting (212) an account associated with the subscriber with a credit amount may include crediting an airtime account with the amount of airtime.
  • the subscriber may be associated with a main airtime account and a dedicated airtime account and crediting an account associated with the subscriber with a credit amount may include crediting the dedicated airtime account with the credit amount (being the amount of airtime).
  • the subscriber may be associated with a service class and crediting the account may include crediting an account associated with the relevant service class (for example based on a service class assignment data structure).
  • crediting (212) an account associated with the subscriber with a credit amount may include crediting a bundle account associated with the particular category of mobile telephone network utilisation with a usage limit in respect of the particular category of mobile telephone network utilisation.
  • the usage limit may be: a number of SMS messages which may be transmitted from a communication device (106) associated with the subscriber; a number of bytes of data which may be exchanged between the communication device (106) and a data communication network (110); or, a total duration of telephone calls that may be initiated from the communication device (106).
  • Crediting (212) the account associated with the subscriber with the credit amount may enable continued use of the mobile telephone network (110) by the subscriber in advance of received payment.
  • the continued use may be confined to the particular category of mobile telephone network utilisation with which the bundle is associated. For example, if the network usage advance relates to a data bundle, it may be that only the exchange of data messages will be permitted.
  • an airtime advance may permit continued usage of the mobile telephone network (110) in accordance with any category (e.g. making calls, sending SMS messages, exchanging data messages and the like).
  • Crediting (212) the account associated with the subscriber with the credit amount may include recording an outstanding loan value against an account associated with the subscriber and/or against the subscriber record (124).
  • the subscriber may be associated with a main airtime account and a dedicated airtime account and the outstanding loan value may be recorded against the main airtime account by debiting the main airtime account (or deducting from the main airtime account) with the outstanding loan value.
  • the outstanding loan value may include the value associated with the network usage advance, as well as a fee. facilitate tracking and recovery of outstanding loans associated with the subscriber.
  • Subsequent airtime top-ups or recharges may be recorded against the main airtime account to increase the balance thereof and hence to recover the outstanding loan value (partially or completely).
  • the subscriber is associated with a loan tracking account and/or fee tracking account and the outstanding loan value may be recorded against one or both of these accounts.
  • Subsequent airtime top-ups or recharges may be recorded against the tracking account(s) to decrease the balance(s) thereof and hence to recover the outstanding loan value (partially or completely).
  • the network usage advance provisioned to the account associated with the subscriber may be associated with a predefined condition, and the method may include monitoring (214) the account and/or subscriber record for fulfilment of the predefined condition.
  • the predefined condition may for example include that the value associated with the network usage advance is repaid within a predefined time period, or that instalments are made on or before particular points in time or the like. If (215) the predefined condition is not met, or if non- compliance with the predefined condition is detected, the method may include transmitting (216) a lock instruction to an EMM module (119) executing on the subscriber communication device (106), which upon receipt locks or disables predefined functionality on the communication device.
  • the system (100) described in the foregoing may implement a method for network usage product provisioning including updating subscriber eligibility and/or credit limit values for a particular subscriber based on the changing subscriber profile.
  • a network usage product in the example embodiment of Figure 3A is a network usage advance.
  • the method may include a data processing system continually receiving and processing (302) raw data records including a first type having static values and a second type relating to transactional records with timestamps of events. The data records may be filtered and transformed to standardized formats.
  • the transformed data records may be persisted or stored into a first data store for static data relating to subscribers for retrieval based on static values, and a second data store for transactional data (including transactional records) for retrieval based on timestamps.
  • Different categories of transactional records may be grouped according to the unique identifiers of subscribers. The categories are persisted to different tables including maintaining a table of stable size for efficient access of a category of transactional records that is most frequently accessed.
  • the persisted data may be used for retrieving features relating to a subscriber from The method may include retrieving and processing (304) persisted data using appropriate key values to output a subscriber profile relating to the subscriber.
  • the method may include storing the subscriber profile in one or more fields of a subscriber record configured for querying before provisioning a network usage product.
  • the method may include determining (308) an eligible subscriber base, including determining subscriber eligibility for each of a plurality of subscribers. Determining the eligible subscriber base may include using dynamic mechanisms and may be performed periodically or upon the occurrence of certain predefined events.
  • the dynamic mechanisms may include using one or more of events, top-ups, airtime advance requests and airtime advance payments, an outstanding loan status, a credit limit value (e.g. being below a predetermined threshold), the subscriber profile and the like to constantly re-evaluate the subscriber’s eligibility. This information may be contained in a subscriber profile.
  • Updating the eligible subscriber base may include removing from the eligible subscriber base subscribers who have not performed any top-up activity for a configurable number of days or who otherwise no longer meet the eligibility requirements.
  • Determining the subscriber eligibility may include storing the subscriber eligibility in a field of a subscriber record configured for querying before provisioning a network usage product.
  • the method may include determining (310) the credit limit data including a total credit limit value associated with the subscriber based on the subscriber profile and/or recent subscriber transactions. The credit limit value may change based on a changing subscriber profile or based on outstanding network usage advances that are still to be repaid.
  • Determining the credit limit value may include deducting the value of a network usage advance provisioned to the account associated with the subscriber to reflect a lower credit limit value. Updating the credit limit value may include adding the value of a repaid network usage advance to reflect an increased credit limit value, up to a maximum credit limit value. Determining the credit limit value may include retrieving and using a net present value of a communication device (106) associated with the subscriber to determine the credit limit value. For example, the credit limit value may be required to be less than the net present value associated with the communication device. Determining the credit limit value may include storing the credit limit value (or updated credit limit value) in a field of a subscriber record (124) configured for querying before provisioning a network usage product.
  • the subscriber profile may change over time in response to changes in transactional records associated with the subscriber.
  • the method may repeat (311) such that changes in subscriber behaviour result in an appropriately updated profile, eligibility and credit limit value. Repeating the method may include retrieving an updated subscriber profile and determining one or both of an subscriber profile. At some stage, the subscriber may repay the outstanding loan value by performing an airtime recharge or top up. The method may include using any recharge amount associated with the airtime recharge or top-up to recover the outstanding loan value recorded against an account associated with the subscriber. If the recharge amount is less than the outstanding loan value, then multiple recharges may be required to recover the full outstanding loan value.
  • FIG. 3B is a flow diagram which illustrates an example method according to aspects of the present disclosure.
  • the method may include receiving (305) a payload from a software application executing on a communication device associated with the subscriber.
  • the payload includes data elements obtained from the communication device, such as a device identifier, a software application identifier, a third-party account identifier (e.g. social media handle, login, etc.).
  • the method may include extracting the data elements from the payload and storing (306) them in a subscriber record (124) associated with the subscriber profile.
  • the method may include retrieving (307) the net present value associated with the subscriber communication device from a table maintained by a mobile network operator using the data elements, for example the device identifier.
  • the net present value may for example be retrieved for use in determining a total credit limit associated with the subscriber.
  • the method may include activating and linking (309) an EMM module (119) on subscriber communication devices for each subscriber in the eligible subscriber base to corresponding subscriber records (124). Linking the EMM module (119) may include storing a software application identifier associated with a software application including or having access to the EMM module in the subscriber record (124).
  • the EMM module (119) may be provided by a software application or an operating system of the subscriber communication device (106) and is configured for remote locking of the subscriber communication device upon instruction by the service provider platform (102).
  • subscribers with low airtime balance while activating or purchasing any bundle or during renewal may have their bundle activated or renewed automatically even if the subscriber has insufficient airtime.
  • the subscriber may repay the loan associated with such a ‘bundle completion’ upon a next recharge. For example, if a subscriber tries to activate a bundle but does not have sufficient airtime, the subscriber may be prompted to accept a network usage advance offer for the subscription or activation to be completed.
  • the subscriber’s relevant bundle account will be credited with the right usage limit and another account associated with the subscriber (e.g. the main airtime account) may be debited with an outstanding loan value associated with the network usage advance. It may however be that the subscriber does not have sufficient airtime for bundle renewal on the day of renewal, in which case the subscriber may be offered a network usage advance for the renewal to be completed. If the subscriber accepts, the network usage advance will be provided, e.g. by crediting a bundle account with the associated usage limit and debiting another account associated with the subscriber (e.g. a tracking account) with an outstanding loan value associated with the network usage advance.
  • Various components may be provided for implementing the method described above with reference to Figures 2 and 3.
  • FIG. 4 is a block diagram which illustrates exemplary components which may be provided by a system for network usage product provisioning according to aspects of the present disclosure.
  • the system includes a service provider platform (102) which may be provided by one or more computing devices.
  • the service provider platform (102) may include a processor (402) for executing the functions of components described below, which may be provided by hardware or by software units executing on the service provider platform (102).
  • the software units may be stored in a memory component (404) and instructions may be provided to the processor (402) to carry out the functionality of the described components.
  • software units arranged to manage and/or process data on behalf of the service provider platform (102) may be provided remotely.
  • the service provider platform (102) may include a data point retrieving component (406) configured to retrieve data points associated with a subscriber.
  • the data point retrieving component (406) may retrieve the data points from a subscriber record (124).
  • the data points include a subscriber profile having been output, for example, by a data processing system (130) retrieving and processing features relating to the subscriber from one or more data stores, wherein one of the data stores includes a category of transactional records which may be associated with the subscriber.
  • the retrieved data points may optionally include one or more of data elements received in a payload from a subscriber communication device (106) and a net present value of the subscriber communication device (106).
  • the service provider platform (102) may include a subscriber eligibility component (408) arranged to determine subscriber eligibility for a network usage product based on the data points.
  • the service provider platform (102) may include an IN-integration component (114A) arranged to interact with an intelligent network (114) of a mobile telephone network (110) to provision the network usage product to an account associated with the subscriber.
  • the service provider platform (102) may include an updating component (410) configured to update one or both of subscriber eligibility and credit limit values based on a changing subscriber profile, for example as described above with reference to Figures 3A and 3B.
  • Figure 5 illustrates an example of a computing device (500) in which various aspects of the disclosure may be implemented.
  • the computing device (500) may be embodied as any form of data processing device including a personal computing device (e.g. laptop or desktop computer), a server computer (which may be self-contained, physically distributed over a number of locations), a client computer, or a communication device, such as a mobile phone (e.g. cellular telephone), satellite phone, tablet computer, personal digital assistant or the like.
  • a mobile phone e.g. cellular telephone
  • satellite phone e.g. cellular telephone
  • tablet computer e.g. cellular telephone
  • personal digital assistant e.g. cellular telephone
  • Different embodiments of the computing device may dictate the inclusion or exclusion of various components or subsystems described below.
  • the computing device (500) may be suitable for storing and executing computer program code.
  • the various participants and elements in the previously described system diagrams may use any suitable number of subsystems or components of the computing device (500) to facilitate the functions described herein.
  • the computing device (500) may include subsystems or components interconnected via a communication infrastructure (505) (for example, a communications bus, a network, etc.).
  • the computing device (500) may include one or more processors (510) and at least one memory component in the form of computer-readable media.
  • the one or more processors (510) may include one or more of: CPUs, graphical processing units (GPUs), microprocessors, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs) and the like.
  • a number of processors may be provided and may be arranged to carry out calculations simultaneously.
  • various subsystems or components of the computing device (500) may be distributed over a number of physical locations (e.g.
  • the memory components may include system memory (515), which may include read only memory (ROM) and random access memory (RAM).
  • ROM read only memory
  • RAM random access memory
  • a basic input/output system (BIOS) may be stored in ROM.
  • System software may be stored in the system memory (515) including operating system software.
  • the memory components may also include secondary memory (520).
  • storage components such as removable storage components (e.g. magnetic tape, optical disk, flash memory drive, external hard drive, removable memory chip, etc.), network attached storage components (e.g. NAS drives), remote storage components (e.g. cloud-based storage) or the like.
  • the computing device (500) may include an external communications interface (530) for operation of the computing device (500) in a networked environment enabling transfer of data between multiple computing devices (500) and/or the Internet.
  • Data transferred via the external communications interface (530) may be in the form of signals, which may be electronic, electromagnetic, optical, radio, or other types of signal.
  • the external communications interface (530) may enable communication of data between the computing device (500) and other computing devices including servers and external storage facilities. Web services may be accessible by and/or from the computing device (500) via the communications interface (530).
  • the external communications interface (530) may be configured for connection to wireless communication channels (e.g., a cellular telephone network, wireless local area network (e.g.
  • the external communications interface (530) may include a subscriber identity module (SIM) in the form of an integrated circuit that stores an international mobile subscriber identity and the related key used to identify and authenticate a subscriber using the computing device (500).
  • SIM subscriber identity module
  • One or more subscriber identity modules may be removable from or embedded in the computing device (500).
  • the computer-readable media in the form of the various memory components may provide storage of computer-executable instructions, data structures, program modules, software units and other data.
  • a computer program product may be provided by a computer-readable medium having stored computer-readable program code executable by the central processor (510).
  • a computer program product may be provided by a non-transient or non-transitory computer- readable medium, or may be provided via a signal or other transient or transitory means via the communications interface (530). Interconnection via the communication infrastructure (505) allows the one or more processors (510) to communicate with each subsystem or component and to control the execution of instructions from the memory components, as well as the exchange of information between subsystems or components.
  • Peripherals such as printers, scanners, cameras, or the like
  • input/output (I/O) devices such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like
  • I/O devices such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like
  • the computing device 500
  • a display or video adapter 540
  • a software unit is implemented with a computer program product comprising a non-transient or non-transitory computer-readable medium containing computer program code, which can be executed by a processor for performing any or all of the steps, operations, or processes described.
  • Software units or functions described in this application may be implemented as computer program code using any suitable computer language such as, for example, JavaTM, C++, or PerlTM using, for example, conventional or object- oriented techniques.
  • the computer program code may be stored as a series of instructions, or commands on a non-transitory computer-readable medium, such as a random access memory (RAM), a read-only memory (ROM), a magnetic medium such as a hard-drive, or an optical medium such as a CD-ROM.
  • Any such computer-readable medium may also reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
  • Flowchart illustrations and block diagrams of methods, systems, and computer program products according to embodiments are used herein. Each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may provide functions which may be implemented by computer readable program instructions. In some alternative implementations, the functions identified by the blocks may take place in a different order to that shown in the flowchart illustrations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Meter Arrangements (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Un système et un procédé de fourniture de produit d'utilisation de réseau sont divulgués. Le procédé comprend la récupération de points de données associés à un abonné mobile prépayé comprenant un profil d'abonné ayant été délivré par un système de traitement de données récupérant et traitant des caractéristiques se rapportant à l'abonné mobile prépayé à partir d'un ou de plusieurs magasins de données. L'un des magasins de données comprend une catégorie d'enregistrements transactionnels associés à l'abonné mobile prépayé. Le procédé comprend la détermination de l'éligibilité d'un abonné pour un produit d'utilisation de réseau sur la base des points de données. Le procédé comprend, si l'abonné mobile prépayé est éligible pour le produit d'utilisation de réseau, l'interaction avec un réseau intelligent d'un réseau de téléphonie mobile afin de fournir le produit d'utilisation de réseau à un compte associé à l'abonné mobile prépayé.
PCT/IB2021/057246 2020-08-17 2021-08-06 Système et procédé de fourniture de produit d'utilisation de réseau WO2022038455A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
MX2023000817A MX2023000817A (es) 2020-08-17 2021-08-06 Sistema y metodo para aprovisionamiento de productos de uso de red.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ZA202005064 2020-08-17
ZA2020/05064 2020-08-17

Publications (1)

Publication Number Publication Date
WO2022038455A1 true WO2022038455A1 (fr) 2022-02-24

Family

ID=80350464

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/057246 WO2022038455A1 (fr) 2020-08-17 2021-08-06 Système et procédé de fourniture de produit d'utilisation de réseau

Country Status (2)

Country Link
MX (1) MX2023000817A (fr)
WO (1) WO2022038455A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584978A (zh) * 2022-04-12 2022-06-03 中国联合网络通信集团有限公司 增值业务鉴权方法、装置、设备及可读介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050018824A1 (en) * 2001-09-18 2005-01-27 Richardson John H. Method for correcting call detail record files
US7123626B1 (en) * 1999-09-08 2006-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Facilitating data transmission
US20060256948A1 (en) * 2001-09-26 2006-11-16 Sbc Properties, L.P. Method and apparatus for enhanced call routing in a telecommunication system
US20170302551A1 (en) * 2015-07-06 2017-10-19 Airwatch Llc Application network usage management
WO2019229655A1 (fr) * 2018-05-30 2019-12-05 Channel Technologies Fze Fourniture d'avances d'utilisation de réseau basée sur une limite de crédit
WO2020008384A1 (fr) * 2018-07-04 2020-01-09 Channel Technologies Fze Provision et recouvrement d'avances sur une utilisation de réseau

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7123626B1 (en) * 1999-09-08 2006-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Facilitating data transmission
US20050018824A1 (en) * 2001-09-18 2005-01-27 Richardson John H. Method for correcting call detail record files
US20060256948A1 (en) * 2001-09-26 2006-11-16 Sbc Properties, L.P. Method and apparatus for enhanced call routing in a telecommunication system
US20170302551A1 (en) * 2015-07-06 2017-10-19 Airwatch Llc Application network usage management
WO2019229655A1 (fr) * 2018-05-30 2019-12-05 Channel Technologies Fze Fourniture d'avances d'utilisation de réseau basée sur une limite de crédit
WO2020008384A1 (fr) * 2018-07-04 2020-01-09 Channel Technologies Fze Provision et recouvrement d'avances sur une utilisation de réseau

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584978A (zh) * 2022-04-12 2022-06-03 中国联合网络通信集团有限公司 增值业务鉴权方法、装置、设备及可读介质
CN114584978B (zh) * 2022-04-12 2023-09-12 中国联合网络通信集团有限公司 增值业务鉴权方法、装置、设备及可读介质

Also Published As

Publication number Publication date
MX2023000817A (es) 2023-02-27

Similar Documents

Publication Publication Date Title
US9220025B2 (en) Core services platform for wireless voice, data and messaging network services
KR101160377B1 (ko) 가입자에 대한 통합식 선불 과금 및 후불 과금 제공 통신 네트워크, 방법 및 통신 네트워크의 과금 선택 시스템
US8799092B2 (en) Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts
CA2840314C (fr) Plate-forme de services d'infrastructure pour des services de reseau de voix, de donnees et de messagerie sans fil
EP2413581A1 (fr) Procédé implémenté par ordinateur, système et produit de programme informatique pour classement de télécommunication
US9161248B2 (en) Core services platform for wireless voice, data and messaging network services
WO2020008384A1 (fr) Provision et recouvrement d'avances sur une utilisation de réseau
WO2022038455A1 (fr) Système et procédé de fourniture de produit d'utilisation de réseau
BR102019015628A2 (pt) Provisão de uso de rede antecipado para um assinante de celular pré-pago
OA21158A (en) System and method for network usage product provisioning.
WO2007147220A2 (fr) Procédé et système de traitement de crédits permettant l'utilisation de ces derniers par les abonnés d'un réseau de télécommunications
CN104396224A (zh) 使用外部控制账户选择的电信计费
WO2019229652A1 (fr) Système et procédé de fourniture et de recouvrement d'une avance d'utilisation de réseau
WO2022008988A1 (fr) Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
WO2021240253A1 (fr) Provisionnement, en fonction de la classification de type, d'avances d'utilisation du réseau dans un réseau mobile
OA19726A (en) Provision of different network usage advance services to different categories of subscribers
WO2022008967A1 (fr) Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile
OA21014A (en) Integrated cross-platform account management.
OA20072A (en) Electronic voucher distribution account management.
OA19720A (en) Network usage product provisioning via a mobile wallet platform
WO2022200881A1 (fr) Gestion intégrée de comptes multiplateformes
OA18745A (en) Provision and recovery of network usage advances
OA18893A (en) System and method for provision and recovery of a network usage advance.
CN114240445A (zh) 一种业务处理方法、装置、电子设备及计算机可读介质
UA99917C2 (uk) Спосіб і система обробки кредитів для використання їх абонентами комунікаційної мережі

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21857843

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21857843

Country of ref document: EP

Kind code of ref document: A1