# US 8,543,474 B2 · Method, communication apparatus and system for handling a recharge service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,543,474 B2
- Document ID: US8543474B2
- Status: Granted
- Kind: B2
- Application number: 12/576,885
- Filed: 2009-10-09
- Published: 2010-04-15
- Granted: 2013-09-24
- Earliest claimed: 2008-10-09
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Bin Wang
- Inventors: Bin Wang
- Web page: https://patentgrep.com/patent/US8543474B2

## CPC

- G06Q 30/02: Marketing; Price estimation or determination; Fundraising
- G06Q 20/105: {involving programming of a portable memory device, e.g. IC cards, "electronic purses"}
- G06Q 20/349: {Rechargeable cards}
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 40/12: Accounting
- G07F 7/1008: {Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/47: {Fraud detection or prevention means}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/90: {using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]}
- H04M 17/00: Prepayment {of wireline communication systems, wireless communication systems or} telephone systems (using a coded card to authorise calls from a telephone set H04M1/675)
- H04M 17/02: Coin-freed or check-freed systems {, e.g. mobile- or card-operated phones, public telephones or booths}
- H04M 17/20: {with provision for recharging the prepaid account or card, or for credit establishment}
- H04M 17/204: {on-line recharging, e.g. cashless}
- H04Q 3/0029: {Provisions for intelligent networking}
- H04W 4/24: Accounting or billing
- G07F 19/20: {Automatic teller machines [ATMs]}
- H04M 2017/24: {with on-line recharging of an account or card, e.g. cashless}
- H04M 2215/0148: Fraud detection or prevention means
- H04M 2215/016: Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
- H04M 2215/0188: Network monitoring; statistics on usage on called/calling number
- H04M 2215/204: UMTS; GPRS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Methods and systems for handling a recharge service and communication apparatuses thereof are disclosed. The method includes receiving a recharge service request; checking whether an abnormal recharge log includes a recharge card ID and whether a recharging process has been successfully performed via a recharge card associated with the recharge card ID; requesting a voucher center to authenticate the recharge card associated with the recharge card ID so that the voucher center may recharge, after the recharge card passes the authentication, the user account via the recharge card if the recharge card ID carried in the recharge service request is not contained in the abnormal recharge log, or a recharging process has not been successfully performed via the recharge card associated with the recharge card ID carried in the recharge service request.

## Claims

### Claim 1

A method for handling a recharge service, comprising:
receiving, by a service control point (SCP), a recharge service request including a recharge card ID and a user account to be recharged;
sending, by the SCP, an authentication request to an online charging system (OCS) to query an abnormal recharge log stored by the OCS,
wherein the abnormal recharge log is logged by the OCS when receiving an instruction from the SCP, when the SCP fails to receive an acknowledgement indicating a successful recharge from the OCS within a predetermined time period, after the SCP sends a recharge request, or when the OCS fails to generate or send the acknowledgement indicating the successful recharge, and the abnormal recharge log includes (a) recharge result information indicating whether a recharging process has been successfully performed in the OCS and (b) an recharge ID corresponding to the recharge result information;
checking whether the abnormal recharge log includes the recharge card ID and whether the recharging process has been successfully performed in the OCS via a recharge card associated with the recharge card ID according to the abnormal recharge log; and
requesting, by the SCP, a voucher center to authenticate the recharge card associated with the recharge card ID so that the voucher center may recharge, after the recharge card passes the authentication, the user account via the recharge card if the recharge card ID carried in the recharge service request is not contained in the abnormal recharge log, or the recharging process has not been successfully performed via the recharge card associated with the recharge card ID carried in the recharge service request.

### Claim 2 (depends on 1)

The method of claim 1, wherein recharging the user account via the recharge card comprises:
generating, by the SCP, the recharge request and sending the recharge request to the OCS, requesting the OCS to recharge the user account via the recharge card;
generating, by the SCP, a recharge card setting request and sending the recharge card setting request to the voucher center after receiving the acknowledgement indicating the successful recharge returned by the online charging system, wherein the recharge card setting request includes the recharge card ID;
receiving, by the SCP, a recharge card setting response returned by the voucher center after the voucher center sets the recharge card;
sending, by the SCP, a recharge confirmation request to the online charging system; and
receiving, by the SCP, a recharge confirmation result returned by the online charging system, wherein the recharge confirmation result includes recharge time and recharge amount.

### Claim 3 (depends on 1)

The method of claim 1, wherein
the abnormal recharge log comprises the recharge card ID and recharge result information indicating that the recharging process has been successfully performed via the recharge card.

### Claim 4 (depends on 3)

The method of claim 3, wherein
requesting, by the SCP, the voucher center to authenticate the recharge card associated with the recharge card ID comprises:
sending, by the service control point, the authentication request to the voucher center, wherein the authentication request carries the recharge card ID carried in the recharge service request;
determining, by the voucher center, the validity of the recharge card associated with the recharge card ID carried in the authentication request, checking whether the recharge card associated with the recharge card ID carried in the authentication request is in an unavailable status; and
sending, by the voucher center, an authentication result message indicating that the recharge card has not passed the authentication to the service control point if the recharge card is in the unavailable status or an invalid status; sending, by the voucher center, an authentication result message indicating that the recharge card has passed the authentication to the service control point if the recharge card is in a valid status.

### Claim 5 (depends on 4)

The method of claim 4, wherein setting the status of the recharge card to an unavailable status if the voucher center fails to set the recharge card or the voucher center fails to receive the recharge card setting request for the recharge card within a predetermined time period after the voucher center sends the authentication result message indicating that the recharge card has passed the authentication to the service control point.

### Claim 6 (depends on 3)

The method of claim 3, wherein the abnormal recharge log further comprises a user account which is recharged via the recharge card associated with the recharge card ID;
the requesting the voucher center to authenticate the recharge card associated with the recharge card ID comprises:
sending, by the service control point, the authentication request to the voucher center, wherein the authentication request carries the user account and the recharge card ID carried in the recharge service request;
determining, by the voucher center, the validity of the recharge card associated with the recharge card ID carried in the authentication request;
checking whether a setting failure log comprises the recharge card ID carried in the authentication request when the recharge card is valid;
checking whether a user account carried in the authentication request is the same as a user account in the setting failure log associated with the recharge card ID carried in the authentication request, wherein the setting failure log comprises relationship between the recharge card ID of the recharge card where setting fails and a recharged user account;
sending, by the voucher center to the service control point, an authentication result message indicating that the recharge card has not passed the authentication if the user account carried in the authentication request is different from the user account in the setting failure log associated with the recharge card ID carried in the authentication request; and
sending, by the voucher center to the service control point, an authentication result message indicating that the recharge card has passed the authentication, if the setting failure log does not comprise the recharge card ID carried in the authentication request or if the user account carried in the authentication request is the same as the user account in the setting failure log associated with the recharge card ID carried in the authentication request.

### Claim 7 (depends on 6)

The method of claim 6, wherein recording, by the voucher center, in the setting failure log the relationship between the recharge card ID of the recharge card where the setting fails and the currently recharged user account, if the voucher center fails to set the recharge card or the voucher center fails to receive the recharge card setting request for the recharge card within the predetermined time period after the voucher center sends the authentication result message indicating that the recharge card has passed the authentication to the service control point.

### Claim 8

A communication apparatus, comprising:
an information interaction module and a first query module;
the information interaction module is configured to receive a recharge service request which includes a recharge card ID and a user account to be recharged; and the information interaction module is further configured to request a voucher center to authenticate the recharge card, according to a query result obtained by the first query module, if the recharge card ID carried in the recharge service request is not contained in an abnormal recharge log, or a recharging process has not been successfully performed via the recharge card associated with the recharge card ID, so that the voucher center may recharge the user account via the recharge card after the recharge card passes the authentication;
the first query module is configured to check whether the abnormal recharge log includes the recharge card ID and the recharging process has been successfully performed via the recharge card associated with the recharge card ID,
wherein the abnormal recharge log is logged by an online charging system (OCS) when receiving an instruction from the communication apparatus, when the communication apparatus fails to receive an acknowledgement indicating a successful recharge from the OCS within a predetermined time period after the communication apparatus sends a recharge request or when the OCS fails to generate or send the acknowledgement indicating the successful recharge, and the abnormal recharge log includes recharge result information indicating whether a recharging process has been successfully performed in the OCS and recharge ID corresponding to the recharge result information.

### Claim 9 (depends on 8)

The communication apparatus of claim 8, wherein the information interaction module comprises a receiving unit and a sending unit;
the receiving unit is configured to receive the recharge service request; and configured to receive an authentication result message returned from the voucher center, the acknowledgement indicating the successful recharge returned from the OCS, a recharge card setting response returned from the voucher center and a recharge confirmation result returned from the online charging system;
according to the query result obtained by the first query module, if the recharging process has not been successfully performed via the recharge card associated with the recharge card ID, the sending unit is configured to generate and send a recharge card authentication request to the voucher center, generate the recharge request for recharging the user account and send the recharge request to the OCS, generate and send a recharge card setting request to the voucher center and generate and send a recharge confirmation request to the OCS.

### Claim 10 (depends on 9)

The communication apparatus of claim 9, further comprising:
a first timer module, configured to count a predetermined time period after the sending module sends the recharge request to the online charging system;
a first notification module, configured to send a write-in notification to the online charging system, informing the online charging system to record in the abnormal recharge log the recharge card ID and the recharge result information indicating that the recharging process has been successfully performed via the recharge card, when the following conditions is met:
the receiving unit fails to receive the acknowledgement indicating the successful recharge returned from the OCS within the predetermined time period after the sending unit sends the recharge request to the OCS.

### Claim 11

An online charging system (OCS), comprising:
a first receiving module, configured to receive a recharge request for recharging a user account sent by a service control point, wherein the recharge request includes a recharge card ID and the user account to be recharged; and further configured to receive a recharge confirmation request sent by the service control point;
a recharge module, configured to recharge the user account via the recharge card and generate an acknowledgement indicating a successful recharge when the first receiving module receives the recharge request, and configured to complete the recharge and generate a recharge confirmation result when the first receiving module receives the recharge confirmation request, wherein the recharge confirmation result comprises recharge time and recharge amount;
a first sending module, configured to send the acknowledgement indicating the successful recharge to the service control point after the recharge module recharges the user account and configured to send the recharge confirmation result to the service control point; and
a write-in module, configured to record in an abnormal recharge log the recharge card ID and recharge result information indicating whether a recharging process has been successfully performed via the recharge card associated with the recharge card ID when one of the following conditions is met:
(1) the write-in module receives a write-in notification sent by the service control point when the service control point fails to receive the acknowledgement indicating the successful recharge from the OCS within a predetermined time period after the recharge request is sent;
(2) the recharge module fails to generate the acknowledgement indicating the successful recharge; and
(3) the first sending module fails to send the acknowledgement indicating the successful recharge.