WO2020008384A1 - Provision et recouvrement d'avances sur une utilisation de réseau - Google Patents

Provision et recouvrement d'avances sur une utilisation de réseau Download PDF

Info

Publication number
WO2020008384A1
WO2020008384A1 PCT/IB2019/055673 IB2019055673W WO2020008384A1 WO 2020008384 A1 WO2020008384 A1 WO 2020008384A1 IB 2019055673 W IB2019055673 W IB 2019055673W WO 2020008384 A1 WO2020008384 A1 WO 2020008384A1
Authority
WO
WIPO (PCT)
Prior art keywords
amount
control flag
balance control
state
main account
Prior art date
Application number
PCT/IB2019/055673
Other languages
English (en)
Inventor
Bassim Said HAIDAR
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 MX2020010529A priority Critical patent/MX2020010529A/es
Publication of WO2020008384A1 publication Critical patent/WO2020008384A1/fr

Links

Classifications

    • 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/83—Notification aspects
    • 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/853—Calculate maximum communication time or volume
    • 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/88—Provision for limiting connection, or expenditure
    • H04M15/881—Provision for limiting connection, or expenditure for continuing the call beyond the limit using allow grace
    • 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
    • H04M15/882—Provision for limiting connection, or expenditure for continuing the call beyond the limit using an alternative, e.g. alternative account
    • 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
    • H04M15/883—Provision for limiting connection, or expenditure linked escalation limits, i.e. establish, first or second limit
    • 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
    • H04M15/885—Provision for limiting connection, or expenditure limit per application
    • 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
    • H04M15/886—Provision for limiting connection, or expenditure limit per terminal
    • 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
    • H04M15/888—Provision for limiting connection, or expenditure severing connection after predetermined time or 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
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H04M17/20—Prepayment of wireline communication systems, wireless communication systems or telephone systems with provision for recharging the prepaid account or card, or for credit establishment
    • 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

Definitions

  • This invention relates to systems and methods for the provision and recovery of network usage advances, such as airtime or mobile bundle advances to prepaid mobile subscribers.
  • A“prepaid mobile subscriber”, or simply“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 recorded against an account associated with the subscriber.
  • the prepaid services require the balance of the subscriber’s account to be positive for the subscriber to be able to conduct telephonic transactions.
  • the positive balance of a prepaid subscriber’s account is typically colloquially referred to as“airtime” against which transactions are recorded.
  • Airtime and mobile bundle advance systems are known in the art. Such systems enable airtime or mobile bundles to be advanced to prepaid mobile subscribers in advance of payment, i.e. on credit. Such systems enable subscribers who have depleted airtime and/or mobile bundle balances to continue to transact on a mobile telephone network, for example by making phone calls, exchanging data messages, sending SMS messages or the like.
  • an airtime advance system may for example deduct a monetary value associated with the airtime advance from an airtime account (termed a“main account” herein) against which the subscriber’s use of the mobile telephone network is normally charged. The amount of airtime advanced is then recorded in a separate account (termed a“dedicated account” herein) against which further use of the mobile telephone network may be charged.
  • a“main account” herein
  • the deduction of the monetary value associated with the airtime advance may cause the balance of the main account to go negative.
  • MNOs mobile network operators
  • Such configuration may be to prevent revenue leaks which could potentially be detrimental to the business of the MNO. It may also be that the relevant MNOs are not inclined or allowed to permit changes to such configurations in order to protect their revenue streams.
  • a computer-implemented method comprising: receiving a network usage advance request, the network usage advance request including a subscriber identifier and a first amount associated with a network usage advance, wherein a network usage advance enables network usage in advance of received payment; switching a balance control flag associated with the subscriber identifier from a first state to a second state, wherein the balance control flag is queried by a charging system of a mobile telephone network when recording transactions against a main account associated with the subscriber identifier, the transactions being associated with usage of the mobile telephone network by a subscriber associated with the subscriber identifier, and wherein transactions relating to a deduction from the main account after which a balance of the main account would be negative are prohibited when the balance control flag is in the first state and permitted when the balance control flag is in the second state; while the balance control flag is in the second state, deducting a second amount associated with the first amount from the main account associated with the subscriber identifier, wherein subsequent provisioning of a third
  • a further feature provides for the method to include provisioning the first amount to a dedicated account associated with the subscriber identifier, wherein further transactions associated with usage of the mobile telephone network by the subscriber are recorded against the dedicated account.
  • Further features provide for the method to include switching the balance control flag from the second state to the first state; and for switching the balance control flag from the second state to the first state to be immediately in response to the deducting or provisioning operations.
  • Still further features provide for switching the balance control flag to be associated with permissions, and for the method to include satisfying permissions prior to switching the balance control flag.
  • the method may be conducted at a service provider platform which interfaces with an intelligent network (IN) of the mobile telephone network to switch the balance control flag and adjust the main account and dedicated account balances.
  • the method may be conducted at a network node of an intelligent network (IN) of the mobile telephone network.
  • Yet further features provide for the method to include: receiving a top-up notification including a subscriber identifier and a third amount, wherein the third amount is a top-up amount by which the balance of the main account associated with the subscriber is to be increased; and, provisioning the third amount to the main account to effect partial or complete recovery of the second amount; for complete recovery of the second amount to be effected if the third amount is greater than or equal to the second amount; for partial recovery of the second amount to be effected if the third amount is less than the second amount; and for partial or complete recovery of the second amount to be effected immediately in response to provisioning the third amount to the main account.
  • Further features provide for the method to include, if upon receiving the network usage advance request the balance of the main account is positive, transferring a fourth amount corresponding to the positive balance of the main account to the dedicated account; and for transferring the fourth amount to the dedicated account to be prior to deducting the second amount from the main account.
  • Still further features provide for the network usage advance request to be received from a mobile handset associated with the subscriber identifier, and for the network usage advance request to be received via one of: a short messaging service (SMS) message, an unstructured supplementary service data (USSD) message or an interactive voice response (IVR) message.
  • SMS short messaging service
  • USSD unstructured supplementary service data
  • IVR interactive voice response
  • Yet further features provide for the network usage advance request to relate to a request for an amount of airtime in advance, for the first amount to be the amount of airtime to be advanced and for the second amount is a monetary value associated with the amount of airtime and optionally to include a fee.
  • the network usage advance request to relate to a request for a particular category of mobile telephone network utilisation, for the first amount to be a usage limit in respect of the particular category of mobile telephone network utilisation, and for the second amount to be a monetary value associated with the usage limit and optionally to include a fee; for the particular category of mobile telephone network utilisation to be one of: an SMS bundle advance request; a data bundle advance request; and, a voice minutes bundle advance request, and for the usage limit to be one of: a number of SMS messages which may be transmitted from a mobile handset associated with the subscriber identifier; a number of bytes which may be exchanged between the mobile handset and a data communication network; and, a duration of telephone calls that may be initiated from the mobile handset.
  • balance control flag to be implemented as a service class associated with the subscriber identifier, and for the method to include provisioning a new service class associated with the second state.
  • a system comprising: a processor and a memory configured to provide computer program instructions to the processor to execute functions of components; a network usage advance request receiving component for receiving a network usage advance request, the network usage advance request including a subscriber identifier and a first amount associated with a network usage advance, wherein a network usage advance enables network usage in advance of received payment; a balance control flag switching component for switching a balance control flag associated with the subscriber identifier from a first state to a second state, wherein the balance control flag is queried by a charging system of a mobile telephone network when recording transactions against a main account associated with the subscriber identifier, the transactions being associated with usage of the mobile telephone network by a subscriber associated with the subscriber identifier, and wherein transactions relating to a deduction from the main account after which a balance of the main account would be negative are prohibited when the balance control flag is in the first state and permitted when the balance control flag is in the second state; and, a main account deducting
  • a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: receiving a network usage advance request, the network usage advance request including a subscriber identifier and a first amount associated with a network usage advance, wherein a network usage advance enables network usage in advance of received payment; switching a balance control flag associated with the subscriber identifier from a first state to a second state, wherein the balance control flag is queried by a charging system of a mobile telephone network when recording transactions against a main account associated with the subscriber identifier, the transactions being associated with usage of the mobile telephone network by a subscriber associated with the subscriber identifier, and wherein transactions relating to a deduction from the main account after which a balance of the main account would be negative are prohibited when the balance control flag is in the first state and permitted when the balance control flag is in the second state; and, while the balance control flag is in the second state, deducting a second amount associated with the first amount from the main
  • Figure 1 is a schematic diagram which illustrates an exemplary system for the provision and recovery of network usage advances
  • Figure 2 illustrates an exemplary data structure which may be maintained by a charging system of an MNO
  • FIG. 3 is a swim-lane flow diagram which illustrates an exemplary method for provision and recovery of network usage advances in which respective swim- lanes delineate steps, operations or procedures performed by respective entities or devices;
  • Figure 4 is a block diagram which illustrates exemplary components which may be provided by a system for the provision and recovery of network usage advances.
  • Figure 5 illustrates an example of a computing device in which various aspects of the disclosure may be implemented.
  • 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 subscriber in advance of received payment.
  • aspects of the present disclosure are directed towards the provisioning of network usage advances in such a way that outstanding loan amounts associated with the network usage advances can be recovered immediately upon top-up or other injection of funds initiated by or on behalf of the relevant subscriber.
  • This may be achieved by provisioning, in association with a subscriber identifier (e.g. an MSISDN), a dedicated loan account (termed herein a“dedicated account”) which receives the network usage advance.
  • a balance control flag may be provisioned in association with the subscriber identifier.
  • the balance control flag may be configured to be queried by a charging system maintained by the MNO when recording transactions (which are associated with usage of the mobile telephone network) against a main account associated with the subscriber.
  • the balance control flag may be configured to be toggled between first and second states, where: transactions relating to a deduction from the main account which would leave the main account with a negative balance are prohibited when the balance control flag is in the first state and permitted when the balance control flag is in the second state.
  • the balance control flag may be an on/off field, Boolean data type or other variable in a data structure (e.g. in the IN/charging system of the MNO or in a profile associated with the subscriber) which can be switched between first and second states.
  • the balance control flag may be configured to be queried by other components or nodes of the IN/charging system (e.g. pursuant to performing a deducting operation against a corresponding main account).
  • the balance control flag may be provided by a new service class which is provisioned to allow adjustment of the main account with a negative value.
  • the balance control flag may be set temporarily, in order to adjust the main account, after which it may be reverted to its previous state.
  • balance control flag may overcome challenges introduced because of the particular configuration of the charging system required by some MNOs, namely configuration to prevent or prohibit the balance of a subscriber’s main account from being negative so as to prevent revenue leaks.
  • FIG. 1 is a schematic diagram which illustrates an exemplary system (100) for the provision and recovery of network usage advances.
  • the system (100) may include a service provider platform (102) and an MNO platform (104).
  • the service provider platform may be provided by a third party service provider which provides network usage advance services to the MNO and its prepaid subscribers.
  • the functionality of the service provider platform may be built-in or integrated with the MNO platform (without the need for a third party service provider).
  • the system may further include mobile handsets (106) associated with prepaid mobile subscribers who typically purchase airtime and mobile bundle advances to make use of a mobile telephone network (1 10) provided by the MNO.
  • the service provider platform (102) may be provided by any suitable computing device.
  • the service provider platform (102) may be configured to interface with the MNO platform (104).
  • the service provider platform may be configured to interface with an intelligent network (IN) and/or charging system of the MNO platform via an appropriate IN integration component. Interfacing with the IN and/or charging system may enable the service provider platform to access and update selected data records stored therein.
  • the service provider platform (102) may be in communication with the mobile handsets (106) via the mobile telephone network (1 10) via which data and/or messages may be transmitted to and received from the respective mobile handsets.
  • the service provider platform may for example be configured to receive network usage advance requests from the mobile handsets and to transmit notifications relating to network usage advance requests to the mobile handsets.
  • the MNO platform (104) and mobile telephone network (1 10) may collectively provide the infrastructure by way of which mobile handsets can communicate with each other and the broader public switched telephone network (PSTN) and the Internet.
  • PSTN public switched telephone network
  • the mobile telephone network may for example include one or more base station subsystems while the MNO platform may provide back-end systems such as a USSD/GPRS gateway and associated components (VLR, HLR, etc.).
  • the MNO platform (104) may include an IN (1 14) and a charging system (1 16).
  • the IN (1 14) 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 (1 14) 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 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 may be supported by the Signalling System #7 (SS7) protocol between network switching centres and other network nodes owned by network operators.
  • SS7 Signalling System #7
  • the charging system (1 16) may be responsible for collecting data on service usage and to generate reports thereon for billing, either on demand or automatically.
  • the charging system (1 16) may be implemented as a node within the IN (1 14).
  • the charging system (1 16) may be implemented as a high-throughput database that maintains multiple accounts of each subscriber.
  • the purpose, type and usage of the accounts may be defined by the MNO.
  • each subscriber may be associated with a main account, a dedicated account and a service class. Airtime top-ups may be provisioned to the main account and usage of the mobile telephone network (1 10) may be charged against the main account.
  • Airtime advances may be provisioned to the dedicated account and, once provisioned, further use of the mobile telephone network may be charged against the dedicated account (until the balance thereof has been depleted).
  • the charging system may maintain a data structure in which each row is associated with a subscriber (identified by way of a subscriber identifier, such as an MSISDN) and columns are associated with accounts.
  • An exemplary data structure (200) which may be maintained by the charging system (1 16) is illustrated in Figure 2.
  • the accounts described herein may be implemented fields of a database, which may be a high- throughput database configured for manipulation and/or accessing of multiple fields per second.
  • 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 service class may be one of the fields stored in a subscriber profile linked to the subscriber identifier. Other fields stored in the subscriber profile may include: an activation date, an expiration date, a first call flag and the like.
  • the service class may be used by the operator to group the subscribers and assign tariffs, services, etc.
  • the service class associated with each subscriber may be configured to operate as a balance control flag which can be toggled between first and second states.
  • the service class, and hence balance control flag may be queried by the charging system (1 16) when recording transactions against the main account associated with the subscriber.
  • a new service class may be provisioned in which transactions causing the balance of the main account to decrease below zero may be permitted.
  • the service class may be toggled between first and second states, where transactions relating to a deduction from the main account after which the balance of the main account would be negative are prohibited in the first state and permitted in the second state.
  • the rules of the charging system may be temporarily changed during provisioning of a network usage advance.
  • the charging system (1 16) may include a front-end API (1 16A) by way of which the service provider platform (102) may interface with the charging system (1 16).
  • the system (100) described above may implement a method for provision and recovery of network usage advances.
  • An exemplary method for provision and recovery of network usage advances is illustrated in the swim-lane flow diagram of Figure 3 in which respective swim-lanes delineate steps, operations or procedures performed by respective entities or devices.
  • certain steps, operations or procedures are performed by the service provider platform (102) which interfaces with the IN (1 14) of the MNO platform (104) via an IN interface.
  • the functionality of the service provider platform may be incorporated in the IN, such that the described steps, operations or procedures are performed by one or more nodes of the IN.
  • the method may commence with the MNO platform provisioning or otherwise instantiating the dedicated account (206) associated with the subscriber identifier.
  • a dedicated account (206) for airtime and for each category of mobile telephone network utilisation e.g. SMS, data, voice
  • the method may also include provisioning or otherwise instantiating a balance control flag associated with the subscriber identifier. These provisioning operations may include adding fields or columns to a data structure (200) maintained by the charging system (1 16) of the MNO.
  • the balance control flag may be implemented or embodied as a service class associated with the subscriber identifier, and provisioning the balance control flag may include provisioning a new service class associated with the second state. Provisioning the balance control flag may further include configuring the charging system and/or IN to query the balance control flag when performing any deducting operations on the main account (or simply for any deducting operations on the main account which has or will have (after deduction) a negative balance).
  • the service provider platform (102) may receive (302) a network usage advance request.
  • the network usage advance request may include or be associated with a subscriber identifier (e.g. an MSISDN, IMSI or the like) and a first amount associated with the network usage advance requested.
  • the network usage advance request may be received from a mobile handset (106) of a prepaid subscriber.
  • the network usage advance request may be received via one of: a SMS message, a USSD message or an IVR message.
  • the request may be initiated by the subscriber sending a predefined message to an SMS short code (e.g. sending “ADVANCE ZAR 10” to the number 12345), dialling a USSD short code and selecting an amount, being the first amount, offered as an advance or the like.
  • the network usage advance request may be received from the MNO platform or may be generated internally by the service provider platform as a part of an automated network advance service that is for example trigged should the balance of a main account associated with the subscriber identifier drop below a predetermined threshold, should the subscriber attempt a transaction for which he or she has insufficient balance, or the like.
  • steps or operations may precede the receiving of the network usage advance request, such as a determination and/or selection of the first amount, evaluating subscriber eligibility (e.g. credit scoring) and the like.
  • the network usage advance request may relate to a request for an amount of airtime in advance, in which case the first amount may be the amount of airtime to be advanced (e.g. ZAR 10). Otherwise, the network usage advance request may relate to a request for a particular category of mobile telephone network utilisation, for example one of: an SMS bundle advance request; a data bundle advance request; and, a voice minutes bundle advance request.
  • the first amount may be a usage limit in respect of the particular category of mobile telephone network utilisation, for example being one of: a number of SMS messages which may be transmitted from the subscriber’s mobile handset; a number of bytes which may be exchanged between the mobile handset and a data communication network; and, a duration of telephone calls that may be initiated from the mobile handset.
  • the service provider platform (102) may transfer (303) the quantity of the positive balance of the main account (204) to the dedicated account (206). This may be performed prior to deducting the second amount from the main account (204) or at any other suitable stage and may be effected by the service provider platform instructing the charging system (1 16) to perform the transfer via a front-end API (1 16A) of the charging system, which is exposed to the service provider platform.
  • the main account may have a balance of ZAR0.2 which may be transferred to the dedicated account.
  • the service provider platform (102) may switch (304) a balance control flag associated with the subscriber identifier from a first state, in which transactions causing a balance of the main account (204) to decrease (or remain) below zero are prohibited, to a second state, in which transactions causing the balance of the main account (204) to decrease (or remain) below zero are permitted.
  • the balance control flag may be associated with permissions (e.g. a permissions list) which provide rules for switching or changing the balance control flag.
  • the service provider platform (102) may satisfy these permissions prior to switching the balance control flag, for example by authenticating itself with the MNO platform (104) or the like.
  • the balance control flag may be provided by a service class (210) which is maintained in the data structure (200) in association with the subscriber identifier (202).
  • the first state may for example be represented by a value of 200 while the second state may be represented by a value of 300. These values are indicated as examples only, and other values (e.g. 1 and 0, A and B, etc.) may be used.
  • Toggling from one state to the next me include overwriting the existing state (e.g. 200) with the new state (e.g. 300). As mentioned, this overwriting may be subject to satisfying the permissions (e.g. it may be that only the service provider platform has permission to write to the service class).
  • the service provider platform (102) switching (304) the balance control flag from the first state to the second state may include the service provider platform (102) instructing the charging system (1 16) to switch the service class (e.g. from‘200’ to‘300’) via the front-end API (1 16A) of the charging system (1 16).
  • the service provider platform (102) may deduct (306) a second amount, which is associated with the first amount, from the main account (204) associated with the subscriber identifier (202). Deducting (306) the second amount may have the effect of reducing the balance of the main account (204) (e.g. equivalent to a debit operation to record a sum owed). Deducting (306) the second amount from the main account may have the effect of recording an amount outstanding (i.e. the subscriber identifier is associated with an outstanding amount which needs to be repaid). As will be explained further below, subsequent provisioning of a third amount to the main account responsive to a top-up notification or instruction may effect partial or complete recovery of the second amount (or the outstanding amount). This recovery may thus be an immediate and automatic recovery that occurs upon a top-up event.
  • Deducting (306) the second amount may include the service provider platform (102) instructing the charging system (1 16) to deduct the second amount via the front-end API (1 16A) of the charging system (1 16).
  • Deducting the second amount (306) may include the charging system (1 16) querying (308) one or both of the balance of the main account (204) and the balance control flag to ascertain whether or not the transaction is permissible. This may entail establishing the effect which the intended deduction would have on the main account (204), and if that effect would be to leave the main account with a negative balance (even if it already has a negative balance), then the transaction, when the balance control flag is in the first state, must be declined or prohibited. It should be appreciated that transactions which provision amounts to the main account and which, despite the provisioning, would leave the main account with a negative balance may be allowed in all circumstances (e.g. irrelevant of the state to which the balance control flag is set).
  • the second amount may be a monetary value associated with the amount of airtime and may optionally include a fee.
  • the monetary value of the amount of airtime and the amount of airtime may be the same (e.g. ZAR 10). If a fee is included, the second amount may then be ZAR 1 1 (corresponding to a 10% fee).
  • the second amount may a monetary value associated with the usage limit and may optionally include a fee. For example, an SMS bundle for sending 20 SMS messages may be associated with a monetary value of R20. If a fee is included, the second amount may then be R22 (corresponding to a 10% fee).
  • the service provider platform (102) may provision (310) the first amount (e.g. ZAR10) to the dedicated account (206) associated with the subscriber identifier. Provisioning (310) the first amount to the dedicated account may have the effect of increasing the balance of the dedicated account by the first amount (e.g. may be equivalent to a credit operation).
  • the first amount e.g. ZAR10
  • Provisioning (310) the first amount to the dedicated account may have the effect of increasing the balance of the dedicated account by the first amount (e.g. may be equivalent to a credit operation).
  • Further transactions associated with usage of the mobile telephone network (1 10) by the subscriber may be recorded against the dedicated account (206). Recording transactions against the dedicated account (206) may have the effect of reducing the balance of the dedicated account (e.g. may be equivalent to debit operations).
  • the dedicated account (206) may be associated with that particular category of network utilisation and only further usage of that category of network utilisation will be dedicated from the dedicated account.
  • the service provider provisioning (310) the first amount to the dedicated account (206) may include the service provider platform instructing the charging system (1 16) to provision the first amount to the dedicated account via the front-end API (1 16A) of the charging system (1 16).
  • the service provider platform (102) may switch (312) the balance control flag from the second state to the first state.
  • the balance control flag is reverted to the state in which deductions from the main account which would have the effect of leaving the main account (204) with a negative balance are prohibited.
  • the balance control flag from the second state to the first state may be performed immediately in response to either the deducting (306) or provisioning (310) operations described above. It should be appreciated that the operations of deducting the second amount and provisioning the first amount (and any associated operations) may be performed in quick succession and may take only a few milliseconds, or less. It is therefore anticipated that the balance control flag may be left in the second state for a very short period of time, thus minimising the possible exposure of the MNO to revenue leaks.
  • the service provider platform (102) switching the balance control flag may include the service provider platform instructing the charging system to switch the service class (e.g. from‘300’ to ‘200’) via the front-end API (1 16A) of the charging system (1 16).
  • the service provide platform (102) may transmit a notification to the prepaid subscriber (e.g. an SMS message to the mobile handset (106) of the subscriber) to confirm provisioning of the network usage advance. While the dedicated account (206) has a positive balance, the subscriber may continue to transact on the mobile telephone network (1 10), with such transactions being recorded against the dedicated account. In the case of the advance of a particular category of mobile telephone network utilisation, only that category of network utilisation may be permitted and while the corresponding dedicated account (206) has a positive balance.
  • a notification to the prepaid subscriber e.g. an SMS message to the mobile handset (106) of the subscriber
  • a top-up or other injection of funds may be initiated by or on behalf of the relevant subscriber. This may be effected by way of an airtime recharge of any type (e.g. scratch card, electronic recharge, etc.) or by other methods (e.g. person-to-person (p2p) monetary transfers among subscribers or the like).
  • an airtime recharge of any type (e.g. scratch card, electronic recharge, etc.) or by other methods (e.g. person-to-person (p2p) monetary transfers among subscribers or the like).
  • the MNO platform (104) may receive (314) a top-up notification or instruction including the subscriber identifier and a third amount, being a top-up amount by which the balance of the main account (204) associated with the subscriber is to be increased.
  • the notification or instruction may be generated by the MNO platform (104) in response to receiving a recharge voucher from the mobile handset (106) of the subscriber or may be in the form of a notification relating to an electronic recharge, p2p monetary transfer or the like.
  • the charging system (1 16) may provision (316) the third amount (e.g. a top-up amount of ZAR12) to the main account (204). Provisioning of the third amount may be responsive to receiving the notification or instruction. Provisioning of the third amount to the main account (204) may have the effect of increasing the balance of the main account by the third amount (e.g. equivalent to a credit operation), thereby effecting partial or complete recovery of the second amount, as the case may be. Complete recovery of the second amount may be effected if the third amount is greater than or equal to the second amount while partial recovery of the second amount may be effected if the third amount is less than the second amount. Partial or complete recovery of the second amount may thus be effected immediately in response to provisioning the third amount to the main account (204). In some cases, this recovery may be effected without knowledge or intervention of the service provider platform. In a sense, recovery of the second amount may be effected immediately upon recharge by or on behalf of the subscriber.
  • the third amount e.g. a top-
  • the IN (1 14) may then perform call detail record (CDR) operations or adjustments.
  • CDRs may be used to capture usage information summaries for the subscribers and may facilitate the determination of a subscriber’s eligibility for mobile telephone network usage advances based on the usage accumulated, the last time the subscriber used the mobile telephone network, active period of the subscriber and the like.
  • the adjusted CDRs may be shared with the service provider platform (102) which may in turn updates its ledgers and accounts.
  • the service provider platform (102) may then send a notification to the prepaid subscriber updating the subscriber on the status of the network usage advance (e.g. partially or completely recovered).
  • the following two tables illustrate exemplary operations for provisioning and recovery of a network usage advance according to aspects of the present disclosure.
  • the first table illustrates partial recovery while the second table illustrates full recovery.
  • Example 1 Full recovery of the loan
  • Example 2 Partial recovery followed by a full recovery of a loan
  • FIG. 4 is a block diagram which illustrates exemplary components which may be provided by a system for the provision and recovery of network usage advances.
  • the system may include a service provider platform (102).
  • the service provider platform may be provided by an independent service provider providing network usage advance services or functionality to an MNO.
  • the functionality of the service provider platform may be built into and or otherwise provided by an MNO platform, without the need for the services of an independent service provider.
  • 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.
  • the service provider platform (102) may include a network usage advance request receiving component (406) arranged to receive a network usage advance request.
  • the network usage advance request may include a subscriber identifier and a first amount associated with the network usage advance.
  • the request may be received from a mobile handset of a subscriber or may be auto-generated by the service provider platform or MNO platform in response to certain predefine conditions being met (e.g. insufficient or low balance triggers).
  • the service provider platform (102) may include a balance control flag switching component (408) arranged to switch a balance control flag associated with the subscriber identifier from a first state to a second state.
  • the balance control flag may be queried by the charging system when recording transactions against a main account associated with the subscriber. Transactions relating to a deduction from the main account after which the balance of the main account would be negative are prohibited when the balance control flag is in the first state and permitted when the balance control flag is in the second state.
  • the balance control flag may be implemented as a service class in a charging system (e.g. as a column in a data structure of the charging system).
  • the service provider platform (102) may include a main account deducting component (410) which may be arranged to deduct a second amount associated with the first amount from the main account associated with the subscriber identifier while the balance control flag is in the second state.
  • the service provider platform (102) may include a dedicated account provisioning component (412) arranged to provision the first amount to a dedicated account associated with the subscriber identifier. Further transactions associated with usage of the mobile telephone network by the subscriber may be recorded against the dedicated account while it has a positive balance. In the case of the dedicated account being associated with a particular category of utilisation of the mobile telephone network, only deductions in respect of that category of utilisation may be recorded against the dedicated account.
  • a new charging account (termed a dedicated account) which receives a loan amount associated with a network usage advance.
  • a new service class may be provisioned to enable adjustment of a main account with a negative value.
  • the service class may be set temporarily in order to adjust the main account, after which it will be reverted to its previous state.
  • the main account may be configured so that no other service is able to adjust it when it contains a negative balance.
  • a subscriber requests a loan from the service provider platform of X amount.
  • the service provider platform queries the IN for balances and an IN profile.
  • the main account has a balance of Y amount. Any outstanding main account balance (Y) may be transferred to a loan account or any other charging account.
  • the service provider platform runs eligibility checks to decide whether the subscriber can obtain the loan.
  • the service provider platform performs the following requests to the IN to advance the loan: changes the service class to allow main account to be set to a negative value; sets the main account to the negative value -(X+Z), where X is the loan amount and Z is fees; changes the service class back to default value; the loan amount X with the main account balance Y, i.e. (X+Y), is credited to the dedicated account.
  • the service provider platform sends an SMS notification to the subscriber for the provision of the loan.
  • a subscriber either makes a recharge of any type (scratch card, electronic recharge etc.) or the main balance is increased by other methods (e.g. p2p monetary transfers among subscribers).
  • the amount W is added to the main account. If recharge amount W is larger than the negative balance of the main account the addition will render the main account positive and the loan fully repaid. If recharge amount W is less than the negative balance of the main account the addition will leave the main account in negative balance and the loan will be partially repaid.
  • the IN generates adjustment CDRs and transmits these to the service provider platform.
  • the service provider platform receives the adjustments CDRs and updates its ledger accounts.
  • the service provider platform sends an SMS notification to the subscriber for the provision of the loan.
  • aspects of the present disclosure describe a negative balance method in which the main account of the subscriber is adjusted to a negative value when the loan is advanced.
  • the main account By setting the main account to a negative value, the account cannot not be used for any other service charges and upon recharge the loan is automatically recovered. So, the process or recovery starts at the advance.
  • the subscriber recharges, the amount is added to the main account. If the recharge amount is large enough to render the main account positive, the loan will be fully repaid.
  • airtime advance may include any on-credit provisioning of airtime made in favour of a prepaid mobile subscriber account so as to increase a balance of the account associated with the subscriber (the main account) and allow the subscriber to transact on the mobile telephone network.
  • An“airtime advance” may be a loan of an amount of airtime made to the subscriber by an MNO or other service provider and which the subscriber is obliged pay back at a later stage (in some cases along with a fee).
  • the term“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 to a prepaid subscriber.
  • “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.
  • FIG. 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
  • 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. in a distributed, cluster or cloud-based computing configuration) and appropriate software units may be arranged to manage and/or process data on behalf of remote devices.
  • 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
  • BIOS basic input/output system
  • System software may be stored in the system memory (515) including operating system software.
  • the memory components may also include secondary memory (520).
  • the secondary memory (520) may include a fixed disk (521 ), such as a hard disk drive, and, optionally, one or more storage interfaces (522) for interfacing with storage components (523), 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.
  • 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
  • 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. using Wi-FiTM), satellite-phone network, Satellite Internet Network, etc.) and may include an associated wireless transfer element, such as an antenna and associated circuitry.
  • 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 computer-readable medium, or may be provided via a signal or other transient 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 controller such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like
  • One or more displays (545) (which may be touch-sensitive displays) may be coupled to or integrally formed with the computing device (500) via a display (545) or video adapter (540).
  • a software unit is implemented with a computer program product comprising a non-transient 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.
  • 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.
  • RAM random access memory
  • ROM read-only memory
  • magnetic medium such as a hard-drive
  • optical medium such as a CD-ROM.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Telephonic Communication Services (AREA)
  • Meter Arrangements (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système et un procédé de provision et de recouvrement des avances sur une utilisation de réseau. Dans un procédé, une demande d'avance sur une utilisation de réseau, qui comprend un identifiant d'abonné et un premier montant associé à l'avance, est reçue. Un indicateur de contrôle de solde associé à l'identifiant d'abonné est basculé d'un premier état à un second état. Les transactions relatives à une déduction sur un compte principal associé à l'identifiant d'abonné laissant le compte principal sur un solde négatif sont interdites lorsque l'indicateur de contrôle de solde est dans le premier état et sont autorisées lorsque l'indicateur de contrôle de solde est dans le second état. Pendant que l'indicateur est dans le second état, un second montant associé au premier montant est déduit du compte principal. Le provisionnement ultérieur d'un troisième montant sur le compte principal en réponse à une notification ou une instruction de rechargement permet un recouvrement partiel ou complet du second montant.
PCT/IB2019/055673 2018-07-04 2019-07-03 Provision et recouvrement d'avances sur une utilisation de réseau WO2020008384A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
MX2020010529A MX2020010529A (es) 2018-07-04 2019-07-03 Abono y recuperacion de anticipos para uso de red.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ZA2018/04476 2018-07-04
ZA201804476 2018-07-04

Publications (1)

Publication Number Publication Date
WO2020008384A1 true WO2020008384A1 (fr) 2020-01-09

Family

ID=69060152

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/055673 WO2020008384A1 (fr) 2018-07-04 2019-07-03 Provision et recouvrement d'avances sur une utilisation de réseau

Country Status (2)

Country Link
MX (1) MX2020010529A (fr)
WO (1) WO2020008384A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022008988A1 (fr) * 2020-07-07 2022-01-13 Channel Technologies Fze Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
WO2022038455A1 (fr) * 2020-08-17 2022-02-24 Channel Technologies Fze Système et procédé de fourniture de produit d'utilisation de réseau
CN116436969A (zh) * 2023-06-15 2023-07-14 北京世冠金洋科技发展有限公司 一种人工智能引擎代理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020021665A1 (en) * 2000-05-05 2002-02-21 Nomadix, Inc. Network usage monitoring device and associated method
US20070111706A1 (en) * 2003-12-31 2007-05-17 Megasoft, Ltd. Real-time interconnect billing system and method of use
US20130196623A1 (en) * 2012-01-27 2013-08-01 Openet Telecom Ltd. System and Method For Enabling Interactions Between a Policy Decision Point and a Charging System
US20130326076A1 (en) * 2012-05-29 2013-12-05 Alcatel-Lucent Canada Inc. Per flow and per session metering limit application
KR20150132803A (ko) * 2014-05-15 2015-11-26 삼성전자주식회사 단말장치, 클라우드 장치, 단말장치의 구동방법, 데이터 협업처리 방법 및 컴퓨터 판독가능 기록매체

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020021665A1 (en) * 2000-05-05 2002-02-21 Nomadix, Inc. Network usage monitoring device and associated method
US20070111706A1 (en) * 2003-12-31 2007-05-17 Megasoft, Ltd. Real-time interconnect billing system and method of use
US20130196623A1 (en) * 2012-01-27 2013-08-01 Openet Telecom Ltd. System and Method For Enabling Interactions Between a Policy Decision Point and a Charging System
US20130326076A1 (en) * 2012-05-29 2013-12-05 Alcatel-Lucent Canada Inc. Per flow and per session metering limit application
KR20150132803A (ko) * 2014-05-15 2015-11-26 삼성전자주식회사 단말장치, 클라우드 장치, 단말장치의 구동방법, 데이터 협업처리 방법 및 컴퓨터 판독가능 기록매체

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022008988A1 (fr) * 2020-07-07 2022-01-13 Channel Technologies Fze Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
WO2022038455A1 (fr) * 2020-08-17 2022-02-24 Channel Technologies Fze Système et procédé de fourniture de produit d'utilisation de réseau
CN116436969A (zh) * 2023-06-15 2023-07-14 北京世冠金洋科技发展有限公司 一种人工智能引擎代理方法及装置
CN116436969B (zh) * 2023-06-15 2023-09-26 北京世冠金洋科技发展有限公司 一种人工智能引擎代理方法及装置

Also Published As

Publication number Publication date
MX2020010529A (es) 2020-11-06

Similar Documents

Publication Publication Date Title
US8799092B2 (en) Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts
RU2417536C2 (ru) Система и устройство для реализации дополнительной услуги извещения о начислении платы
US10560818B2 (en) Device and method for controlling charging in a mobile communication system
WO2020008384A1 (fr) Provision et recouvrement d'avances sur une utilisation de réseau
WO2016165337A1 (fr) Procédé et dispositif pour réaliser une facturation
US11349996B2 (en) Offline charging of communications services
WO2019229655A1 (fr) Fourniture d'avances d'utilisation de réseau basée sur une limite de crédit
WO2019229652A1 (fr) Système et procédé de fourniture et de recouvrement d'une avance d'utilisation de réseau
EP3104550B1 (fr) Système de télécommunication cellulaire numérique mobile avec fonctionnalité de correction de tarification avancée
WO2022038455A1 (fr) Système et procédé de fourniture de produit d'utilisation de réseau
OA18745A (en) Provision and recovery of network usage advances
OA18893A (en) System and method for provision and recovery of a network usage advance.
JP2016208131A (ja) 提携サービス提供方法
WO2022008967A1 (fr) Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile
WO2022200881A1 (fr) Gestion intégrée de comptes multiplateformes
OA20072A (en) Electronic voucher distribution account management.
WO2022008988A1 (fr) Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
OA21014A (en) Integrated cross-platform account management.
OA19726A (en) Provision of different network usage advance services to different categories of subscribers
WO2021240253A1 (fr) Provisionnement, en fonction de la classification de type, d'avances d'utilisation du réseau dans un réseau mobile
CN103813289B (zh) 实时在线计费方法和实时在线计费处理系统
OA21158A (en) System and method for network usage product provisioning.
CN112533035B (zh) 广告推送方法及系统
OA19720A (en) Network usage product provisioning via a mobile wallet platform
OA18625A (en) Systems and methods for mobile subscriber provisioning

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: 19830942

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16.04.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19830942

Country of ref document: EP

Kind code of ref document: A1