Methods and arrangements for third party charging authorization for mobile service providers

US10068236B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10068236-B2
Application numberUS-201113095251-A
CountryUS
Kind codeB2
Filing dateApr 27, 2011
Priority dateApr 27, 2011
Publication dateSep 4, 2018
Grant dateSep 4, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Methods and arrangements for handling web-based purchase requests. A customer request for content of a third party content provider is received at a charging service provider. An authorization code on behalf of the content provider is generated and returned to the customer via a channel other than a channel which links the customer with the third party content provider. The authorization code is accepted from the third party content provider as received by the third party content provider from the customer, the authorization code is verified, and charging for the requested content is executed.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: utilizing at least one processor to execute computer code configured to perform the following steps at a charging service provider: receiving, at the charging service provider, notice of a customer request for content of a third party content provider; generating, at the charging service provider, an authorization code on behalf of the content provider and returning (i) the authorization code, (ii) an identification of the content to be purchased, and (iii) an amount to be charged to the customer via a channel independent of the third party content provider; accepting, at the charging service provider, the authorization code from the third party content provider once the third party content provider receives the authorization code from the customer; verifying, at the charging service provider, the authorization code provided by the third party content provider against the authorization code generated by the charging service provider; executing at the charging service provider and responsive to determining that the authorization code provided by the third party content provider matches the authorization code generated by the service provider, charging for the requested content; and availing the requested content to the customer via: receiving a communication originating from the third party content provider, the communication comprising a link which avails customer access to the requested content; and blocking customer access to the requested content until said verifying of the authorization code, via controlling access to a URL of the third party content provider, the URL comprising the link which avails customer access to the requested content; wherein the requested content comprises content availed to the customer via a message containing the URL, the message comprising the communication originating from the third party content provider and the URL comprising the link which avails customer access to the requested content; said blocking comprising: holding the message at the charging service provider; and releasing the message to the customer subsequent to: said generating and returning of the authorization code; and said verification of the authorization code. 2. The method according to claim 1 , wherein: said receiving comprises receiving notice of a customer purchase action at the third party content provider; said returning comprises returning the authorization code along with charge information; said accepting comprising accepting the authorization code from the third party content provider as received by the third party content provider from the customer over a channel which links the customer with the third party content provider; said verifying comprises validating the authorization code at the charging service provider; and said method further comprises confirming the charging to the third party content provider and prompting the third party content provider to avail purchased content to the customer. 3. The method according to claim 1 , wherein the content comprises at least one taken from the group consisting of: a subscription purchase; content purchase. 4. The method according to claim 1 , wherein: the charging service provider comprises a mobile phone service operator, with the content provider comprising a provider of mobile phone compatible content. 5. The method according to claim 4 , wherein said executing comprises charging against a mobile phone account of the customer. 6. The method according to claim 1 , wherein: said accepting comprises accepting customer provision of the authorization code as issued by the third party content provider and comprises no redirection to a website of the charging service provider for achieving authorization; and said verifying is transparent to the third party content provider. 7. The method according to claim 1 , wherein said receiving and said verifying are performed asynchronously. 8. The method according to claim 1 , wherein said blocking comprises intercepting the message transmitted by the third content provider to the customer, wherein the message contains the URL. 9. The method according to claim 1 , wherein the predetermined authorization condition comprises: the authorization code being generated and returned to the customer; and customer provision of the authorization code being accepted. 10. The method according to claim 1 , further comprising: at least twice performing said receiving notice of a customer request for content of at least one third party content provider; at least twice performing said blocking of customer access to the requested content; and solely once performing said accepting customer provision of the authorization code. 11. The method according to claim 10 , wherein: the requested content comprises content availed to the customer via at least two messages containing URL's, the messages comprising the communication originating from the third party content provider and the URL's comprising the link which avails access to the requested content; said blocking comprises holding the messages, and then releasing the messages to the customer upon a predetermined authorization condition being satisfied. 12. The method according to claim 11 , wherein the predetermined authorization condition comprises: an authorization code corresponding to each request for content being generated and returned to the customer; and customer provision of a final single authorization code being accepted. 13. The method according to claim 1 , wherein: said returning of the authorization code comprises sending a text message to the customer; said channel independent of the third party content provider comprising a medium for sending a text message to the customer. 14. The method according to claim 1 , wherein the notice of customer request comprises an SMS message. 15. The method according to claim 1 , wherein, by way of preauthorization, said generating, accepting and verifying are performed prior to said receiving. 16. The method according to claim 15 , wherein said accepting comprises receiving from a customer preauthorization information specifying the third party content provider. 17. The method according to claim 15 , wherein said accepting comprises receiving from a customer preauthorization information appended to a code for ordering, wherein the code does not specify the third party content provider. 18. An apparatus comprising: at least one processor; and a non-transitory computer readable storage medium having computer readable program code embodied therewith and executable by the at least one processor, the computer readable program code comprising: at a charging service provider, computer readable code configured to: receive, at the charging service provider, notice of a customer request for content of a third party content provider; generate, at the charging service provider, an authorization code on behalf of the content provider and returning (i) the authorization code (ii) an identification of the content to be; purchased, and fin) an amount to be charged to the customer via a channel independent of the third party content provider accept, at the charging service provider, the authorization code from the third party content provider once the third party content provider has received the authorization code from the customer; verify, at the charging service provider, the authorization code provided by the third party content provider against the authorization code generated by the chargi

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10068236B2 cover?
Methods and arrangements for handling web-based purchase requests. A customer request for content of a third party content provider is received at a charging service provider. An authorization code on behalf of the content provider is generated and returned to the customer via a channel other than a channel which links the customer with the third party content provider. The authorization code i…
Who is the assignee on this patent?
Kumar Apurva, Rana Aamer Iqbal, IBM
What technology area does this patent fall under?
Primary CPC classification G06Q30/00. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 04 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).