Patent Application
20120278214
Mobile service providers are moving away from access-based business models due to diminishing margins in traditional network based services. Instead, there now exist efforts to target the millions of subscribers on their network with rich content and multimedia services. Mobile content is any type of text or media content (news, weather forecasts, ring tones, wallpapers, games, applications, etc.) that can be viewed or used on a mobile phone. Since the service providers already have a billing relationship with these customers, it is easy to offer them content services that can be billed through an existing pay channel. Direct mobile billing is a desirable option for purchasing mobile content when compared to payment solutions that require the sharing of private information (e.g., credit card number, account number, authentication information with online payment instruments, etc.).
Generally, mobile service providers rely on content partners (CP) to provide content. There are two models typically used by operators for providing content to their customers, on-deck and off-deck. In the on-deck model, content may be provided by a CP, but sold under the branding of the service provider. In the off-deck model, content is sold directly by the CP to the service provider's customers. Traditionally, the on-deck model has been the preferred model for providers.
However, it has been noted that service providers that have opened up to the off-deck model have seen their content business growing many-fold due to the sheer volume, regional coverage and creativity of off-deck content partners; the on-deck model often cannot match these advantages. As such, in the off-deck model, services are provided directly by the CP to the subscriber and the corresponding charges are communicated to the service provider. Implicit in this mode of operation is the assumption that the service provider has complete trust on charging claims made by its content providers.
Understandably, such trust is difficult to establish with a large number of content partners and this lack of trust is a major hindrance in acceptance of the off-deck model by service providers. The concerns associated with this model in the current form are related to the following actions that a fraudulent CP may be able to perform unchecked, merely by way of example: charging a customer for a content he/she did not purchase or was tricked into purchasing; charging an amount more than the price displayed at the time of purchase; starting a subscription against the customer's wishes when the customer only made a one-time purchase request; renewing a subscription even though the subscriber has given instructions to stop the service; and providing a service which is inconsistent with a displayed specification.
This, in turn, leads to problems difficulties at the service provider end, including (by way of example): customer dissatisfaction, resulting in a blow to the provider's reputation and an attendant decline in revenue; increased help desk calls to handle resulting complaints, thus adding to the cost of supporting the content business; revenue leakage due to revenue share for unauthorized transactions going to the CP; and increased costs of partner revenue settlement and partner management, thereby limiting the capability to partner with a large number of content partners.
In summary, one aspect of the invention provides a method comprising: receiving, at a charging service provider, notice of a customer request for content of a third party content provider; generating an authorization code on behalf of the content provider and returning the authorization code to the customer via a channel other than a channel which links the customer with the third party content provider; accepting the authorization code from the third party content provider as received by the third party content provider from the customer; verifying the authorization code; and executing charging for the requested content.
Another aspect of the invention provides an apparatus comprising: at least one processor; and a 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: computer readable program code configured to receive notice of a customer request for content of a third party content provider; computer readable program code configured to generate an authorization code on behalf of the content provider and returning the authorization code to the customer via a channel other than a channel which links the customer with the third party content provider; computer readable program code configured to accept the authorization code from the third party content provider as received by the third party content provider from the customer; computer readable program code configured to verify the authorization code; and computer readable program code configured to execute charging for the requested content.
An additional aspect of the invention provides a computer program product comprising: a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising: computer readable program code configured to receive notice of a customer request for content of a third party content provider; computer readable program code configured to generate an authorization code on behalf of the content provider and returning the authorization code to the customer via a channel other than a channel which links the customer with the third party content provider; computer readable program code configured to accept the authorization code from the third party content provider as received by the third party content provider from the customer; computer readable program code configured to verify the authorization code; and computer readable program code configured to execute charging for the requested content.
It will be readily understood that the components of the embodiments of the invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations in addition to the described exemplary embodiments. Thus, the following more detailed description of the embodiments of the invention, as represented in the figures, is not intended to limit the scope of the embodiments of the invention, as claimed, but is merely representative of exemplary embodiments of the invention.
Reference throughout this specification to “one embodiment” or “an embodiment” (or the like) means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” or the like in various places throughout this specification are not necessarily all referring to the same embodiment.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in at least one embodiment. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the various embodiments of the invention can be practiced without at least one of the specific details, or with other methods, components, materials, et cetera. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The description now turns to the figures. The illustrated embodiments of the invention will be best understood by reference to the figures. The following description is intended only by way of example and simply illustrates certain selected exemplary embodiments of the invention as claimed herein.
It should be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, methods and computer program products according to various embodiments of the invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises at least one executable instruction for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Referring now to
In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents at least one of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by at least one data media interface. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, at least one application program, other program modules, and program data. Each of the operating system, at least one application program, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with at least one external device 14 such as a keyboard, a pointing device, a display 24, etc.; at least one device that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with at least one other computing device. Such communication can occur via I/O interfaces 22. Still yet, computer system/server 12 can communicate with at least one network such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
The disclosure now turns to
To facilitate easier reference, in advancing from
In accordance with at least one embodiment of the invention, there is broadly contemplated herein a method and framework for the authorization of charging requests made by a service provider's content partners for services that were provided to its customers.
Broadly contemplated herein, in accordance with at least one embodiment of the invention, is the use of a mobile channel to facilitate and simplify authentication and authorization so that no redirection to the service provider site is required. An authorization code is sent to a customer through an SMS (short message service) channel by way of authenticating a customer as well as obtaining authorization for a specific transaction. Authorization process flow is decoupled from ordering process flow so that users can authorize asynchronously, thus improving usability over conventional arrangements. A service provider is able to control delivery of third party content so that the user authorization can be obtained before charging and content delivery. The aforementioned decoupling and delivery control is transparent to the content provider, and multiple transactions can be associated with a single authorization request to achieve batch authorization of transactions, thus further improving usability.
In the context of at least one embodiment of the invention,
As illustrated in
Based on this, in accordance with at least one embodiment of the invention, the following use cases are considered by way of illustration: subscription purchases (web), content purchases (web/WAP), subscription purchases (SMS) and subscription deactivation (SMS). Of course, these merely represent examples of possible use cases in accordance with at least one embodiment of the invention and are intended to be illustrative and non-restrictive.
Essentially,
Next, in the conventional process illustrated in
In contrast, in a process according to at least one embodiment of the invention as shown in
Continuing with the process of
Thereafter, in the process of
The approach described hereinabove with respect to
Generally, it can be understood that purchasing a content item is similar to purchasing a subscription. However, in the former case (now to be addressed), content is usually delivered through a URL embedded in a WAP push message sent to the customer. Thus, in accordance with the conventional arrangement shown in
Turning now to an approach in accordance with at least one embodiment of the invention, as shown in
Thus, in accordance with at least one embodiment of the invention, inasmuch as WAP is recognized as a preferred channel for browsing and purchasing individual third party content items, the problem of switching to messaging application for retrieving the authorization code could be avoided if the authorization step could be moved out of the ordering process and executed separately at a later point of time.
Accordingly, in accordance with at least one embodiment of the invention,
The details of message replacement are shown in
Notably, the approach of
As such, in accordance with at least one embodiment of the invention as contemplated broadly in accordance with
Essentially, the approach of
Conventionally, a typical workflow for ordering off-deck content through SMS involves the customer sending a text message with a key word (to a specified short code) to request a content item or to avail a subscription offer, while a messaging proxy at the service provider routes the request to the content partner responsible for the service. The CP makes a charging request corresponding to the content purchase. The service provider then charges the customer and returns “success” to the CP, while thereupon the CP makes the content available and sends a WAP push/SMS, with a link to the content, to the customer. Then the customer may click on the message/URL to access the content.
In accordance with at least one variant embodiment of the invention, the approach described and illustrated hereinabove with respect to
In accordance with at least one other variant embodiment in accordance with the invention, it is possible to include the authorization information as part of the aforementioned step of sending a text message with a key word (to a specified short code) to request a content item or to avail a subscription offer. This has the effect of further reducing the number of exchanges. Thus, by way of an illustrative and non-restrictive example, if the normal message for requesting a wall paper from a service provider is:
then, the authorization information can be included as illustrated in the two messages below:
wherein Rs=rupees (currency of India).
Accordingly, the service provider can then easily handle a message containing authorization as follows. First, the request is parsed for authorization parameters and key word. The service provider registers the request (for a given short code, key word) against the customer. The request (along with key word) is then routed to the CP. Thence, the charging request from the CP is compared with the registered request and permitted only if the charged amount is within limits authorized by the customer.
There is further broadly contemplated, in accordance with at least one variant embodiment of the invention, an arrangement for pre-authorization. Essentially, in the approaches contemplated hereinabove in connection with
In accordance with at least one embodiment of the invention, if the service is ordered through a web or WAP channel, the identity of the content partner (or at least its web address) is known to the customer. A service provider could provide its customers a feature on a self-care portal to pre-approve charging for at least one CP. For each request, the user could select a CP (e.g. based on web address) from a list of CP's displayed on the page and specify pre-authorization information such as maximum amount, determinative time period, etc. The customer can also be afforded the equivalent facility of getting such pre-authorization preferences registered through interactive voice response (IVR) or by directly speaking with a customer care representative.
In accordance with at least one embodiment of the invention, if the service is being ordered through an SMS channel, the customer in all probability will be unaware of the CP providing the service. In such a case, pre-authorization can be linked to the short code which is used for ordering the service. In the SMS approaches discussed hereinabove with respect to
Support for pre-authorization options as described above can be easily implemented at the provider by storing these preferences for users and keeping track of a remaining pre-authorized amount for a CP in a given time period. If a charging request from a CP is for an amount greater than remaining authorization amount for that CP, then either the charge request can be failed as unauthorized, or a post purchase authorization flow (e.g., as contemplated hereinabove with respect to
As shown in
It should be noted that aspects of the invention may be embodied as a system, method or computer program product. Accordingly, aspects of the invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the invention may take the form of a computer program product embodied in at least one computer readable medium having computer readable program code embodied thereon.
Any combination of at least one computer readable medium may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having at least one wire, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire line, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the invention may be written in any combination of at least one programming language, including an object oriented programming language such as Java®, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer (device), partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
This disclosure has been presented for purposes of illustration and description but is not intended to be exhaustive or limiting. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments were chosen and described in order to explain principles and practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Although illustrative embodiments of the invention have been described herein with reference to the accompanying drawings, it is to be understood that the embodiments of the invention are not limited to those precise embodiments, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the disclosure.
