Abstract:
System and method to enable and facilitate purchases through mobile communications on mobile devices, smartphones, feature phones, tablet computers, etc by allowing the user to interact with native interface and/or by eliminating the need of entering the MSISDN identifier by the user. MSISDN value is required to identify mobile subscriber and request a mobile billing transaction through carrier&#39;s infrastructure. A system comprises at least one data computing facility, which is connected to mobile carrier billing, short code and networking infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various mobile device types and platforms.

Description:
FIELD OF INVENTION 
       [0001]    The present invention relates to the field of mobile payments, more specifically to facilitating purchases of goods and services on mobile devices via cross-platform user interface and/or by automatic Mobile Network Code, Mobile Country Code and MSISDN detection. 
       BACKGROUND OF THE INVENTION 
       [0002]    It is known to perform purchases of goods or services using a mobile device. For example, a user may purchase a song while browsing a mobile website. Or pay for additional content inside mobile game or application. There are various methods and technologies, which allow a user to perform purchases on a mobile device, including but not limited to those provided by mobile operating system manufacturer, handset vendors, mobile carriers and banks. 
         [0003]    Every mobile platform and operating system has a distinctive user interface—a unique set of visual elements and guidelines often called native user interface. Applications that follow respective platform&#39;s user interface guidelines benefit from being easier and more convenient for the user. The same applies for purchasing methods. On the other hand sellers are interested in minimizing the number of variations in purchasing options and methods thus lowering operational costs. 
         [0004]    What is needed is a method and system, that benefits from utilizing native and universal user interface while not being tied to a single mobile platform or operating system, thus enabling a native interface for various platforms via a single integration for the seller. 
         [0005]    From the user perspective instead of a single purchase flow for all mobile devices, that includes multiple steps and a lot of user input, a native platform specific user experience and interface is used. As a result, the process of purchase on mobile device feels like an initial and built-in functionality of the handset provided by mobile operator. 
         [0006]    From another user perspective the time-consuming step of phone number (MSISDN) input is excluded from the purchase flow. The whole payment process is more smooth and effective without the risk of input errors. As a result, the purchase process is completed in fewer steps 
       BRIEF DESCRIPTION OF THE INVENTION 
       [0007]    The aim of present invention is to provide a solution for purchases on mobile devices using cross mobile platform native user interface technology and solution to facilitate purchases on mobile devices by automatic Mobile Network Code, Mobile Country Code and MSISDN detection for in-application payments without knowing the phone number of the user. 
         [0008]    The system and method according to present invention is used to enable and facilitate purchases through mobile communications on mobile devices including but not limited to smartphones, feature phones and tablet computers by allowing the purchaser to interact with native interface and/or by eliminating the need of entering the MSISDN identifier by the purchaser. 
         [0009]    A system comprises at least one data computing facility (DCF), which is connected to mobile carrier billing infrastructure, short code and networking infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various types of mobile devices and platforms. 
         [0010]    The advantage of the present invention from the user perspective is that instead of a single purchase flow for all mobile devices, that includes multiple steps and a lot of user input, a native platform specific user experience and interface is used or the time-consuming step of MSISDN input is excluded from the purchase flow. The whole payment process is more smooth and effective without the risk of input errors. As a result, the process of purchase on mobile device it feels like an initial and built-in functionality of the handset provided by mobile operator. 
         [0011]    The advantage of the present invention from the merchant perspective is that purchases can be enabled for several mobile device platforms using a single solution and a single integration, while still providing a native interface and purchase flow. This allows minimizing the number of variations in purchasing options and methods thus lowering operational costs. 
         [0012]    In a first embodiment a system and method for cross-platform purchases on mobile devices comprises at least one data computing facility, which is connected to mobile carrier billing infrastructure and at least one converter to communicate and interface with at least one of controllers for various types of mobile devices and platforms. Respective controller integrates with mobile device native input and output interface in order to obtain user&#39;s identification details (for example MCC, MNC, MSISDN), inform the user about upcoming transaction cost and associated merchant details (for example name, contacts and/or other information about service provider) and confirm the purchase through respective payment confirmation screen. Once confirmed, purchase confirmation and user&#39;s identification details are communicated by respective controller to respective converter, that forwards transaction details (for example the recipient, the sum of transaction, confirmation, etc) to mobile carrier billing infrastructure through data computing facility. Once transaction is confirmed by carrier&#39;s infrastructure, respective converter transmits purchase confirmation details to respective controller on user&#39;s device. Transaction confirmation is later communicated to user through platform&#39;s native interface. 
         [0013]    In a first embodiment a respective controller integrates with platform&#39;s native interface in order to obtain user&#39;s identification details, inform the user about upcoming transaction cost and associated merchant details and confirm the purchase through respective payment confirmation opt-in screen, provided by the platform&#39;s interface. When the purchase is once confirmed, the purchase confirmation and user&#39;s identification details are communicated by respective controller to respective converter that forwards transaction details to mobile carrier billing infrastructure through computing facility. 
         [0014]    When the transaction is confirmed by carrier&#39;s infrastructure, the respective converter transmits purchase confirmation details to respective controller on user&#39;s device. A transaction confirmation is later communicated to user through platform&#39;s native interface. 
         [0015]    In a second embodiments system and method for facilitating purchases on mobile devices by automatic Mobile Network Code, Mobile Country Code and Mobile Subscriber ISDN (MSISDN) detection comprises at least one data computing facility, which is connected to mobile carrier billing infrastructure, short code and networking infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various types of mobile devices and platforms. Respective controller communicates with respective operating system telephony component by using native system functionality and obtains Mobile Network Code (MNC) and Mobile Country Code (MCC) values. If the code values are among the ones currently supported by data computing facility&#39;s existing connection to mobile carrier billing infrastructure, a text message to respective short code consisting of encoded device and purchase identification details (for example the recipient, the sum of purchase, confirmation, etc) is initiated and sent by respective controller through operating system&#39;s native messaging component. Once the purchase identification details are received by the short code, the message is transported to data computing facility and decoded by respective converter. As a result, MNC, MCC and MSISDN values are obtained and can be used for initiating a transaction through carrier billing infrastructure. 
         [0016]    In a second embodiment the MSISDN value is required to identify mobile subscriber and request a mobile billing transaction through carrier&#39;s billing infrastructure. Respective controller communicates with respective operating system telephony component by using native system functionality and obtains Mobile Network Code (MNC) and Mobile Country Code (MCC) values. If code values are among the ones currently supported by data computing facility&#39;s existing mobile carrier billing connections, a text message to respective short code consisting of encoded device and purchase identification details is initiated and sent by respective controller through operating system&#39;s native messaging component. Once received by the short code, message is transported to data computing facility and decoded by respective converter. As a result, MNC, MCC and MSISDN values are obtained and can be used for initiating a transaction through carrier billing infrastructure. 
         [0017]    A further development of the present invention is combining and integrating first and second embodiments, system and method for facilitating purchases on mobile devices via a cross-platform native user interface and/or Mobile Network Code, Mobile Country Code and MSISDN detection. The system and method comprises a mobile device component connected to a network and a server component connected to the network and having a database component. Mobile device component is a further development of device controller, connected to device core platform. Server and database components are the further development of data computing facility and remote converters. 
         [0018]    Mobile device component comprises a device controller, configured to interface with operating system of the device and detect operating system&#39;s type and version; a purchase user interface controller, configured to interface with input and output components of mobile device including but not limited to display, keyboard, speaker, touchscreen. 
         [0019]    Server component comprises an interface converter connected with a plurality of native interface controllers. 
         [0020]    Database component is configured to store native user interface data including but not limited to visual elements, layouts, stylesheets and animations for different mobile operating systems. 
         [0021]    In response to initialization of purchase process by the user, purchase user interface controller connects with device controller and obtains operating system information including name and version. This information is later sent to interface converter on server component. Interface converter connects to respective native interface controller, which matches device&#39;s operating system. Native interface controller connects to database component and obtains respective user interface data, which is sent back to interface converter, where the data is converted to common format and sent back to purchase user interface controller for being displayed to the user. 
         [0022]    In an alternative embodiment the present invention includes a method of connecting with universal interface controller on server component in case device&#39;s operating system is not supported by any of the native user interface controllers. In such case a best suiting universal user interface data in terms of visual elements, size and layout is sent back to interface converter. 
         [0023]    In an alternative embodiment the present invention comprises a method of obtaining Mobile Country Code and Mobile Network Code values by the device controller in case such values are provided by operating system of the device. Mobile Country Code and Mobile Network Code values may be further used for identifying the user and facilitating the purchase process. 
         [0024]    In an alternative embodiment the present invention comprises a method of obtaining MSISDN value by the device controller in case such value is provided by operating system of the device. MSISDN value may be further used for identifying the user and facilitating the purchase process. 
         [0025]    Other features will be apparent from the accompanying drawings and from the detailed description, which follows. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0026]    The present invention is explained more precisely with references to figures added, where 
           [0027]      FIG. 1  depicts an illustrative system for cross-platform purchases on mobile devices according to the first embodiment; 
           [0028]      FIG. 2  depicts an illustrative system for facilitating purchases on mobile devices by automatic Mobile Network Code, Mobile Country Code and MSISDN detection according to the second embodiment; 
           [0029]      FIG. 3  depicts an illustrative system for facilitating purchases on mobile devices via cross-platform native user interface and/or Mobile Network Code, Mobile Country Code and MSISDN detection; 
           [0030]      FIG. 4  depicts an illustrative method for providing native or universal user interface for purchase on mobile device; 
           [0031]      FIG. 5  depicts an illustrative method for obtaining Mobile Country Code and Mobile Network Code values by the device controller for facilitating purchases on mobile devices; 
           [0032]      FIG. 6  depicts samples of native and universal user interface for purchase on different mobile platform and operating system. 
           [0033]      FIG. 7  depicts the third embodiment combining and integrating first and second embodiments. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0034]    For the purposes of promoting an understanding of the principles of the invention, reference will now be made to a number of illustrative embodiments illustrated in the drawings and specific language will be used to describe the same. The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. 
         [0035]    The process of completing a purchase on mobile device consists of several steps and requires user authorization through detecting user&#39;s country, mobile carrier and phone number. Part of this information is obtainable directly from mobile device, bypassing the need of requesting this information from user. Country information can be obtained from Mobile Country Code (MCC) and carrier information can be obtained from Mobile Network Code (MNC) values in accordance with E.212 numbering standard by International Telecommunication Union. 
         [0036]    Subscriber identification is performed using Mobile Subscriber Integrated Services Digital Network Number (MSISDN) value according to recommendation E.164 of ITU Telecommunication Standardization Sector. 
         [0037]    A system according to present invention comprises at least one data computing facility, which is connected to mobile carrier billing infrastructure, short code and networking infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various mobile device types and platforms. 
         [0038]    Each converter is configured to communicate with a respective controller using any of supported wireless communication protocols (for example UMTS, W-CDMA, HSPA, LTE, EDGE, GSM, GPRS, GSM Short Message protocol, IEEE 802.11. etc) Selection of communication interface is performed automatically by interrogating with device&#39;s platform core component. 
         [0039]    In a first embodiment each controller is designed to integrate with respective device&#39;s platform interface. In a second embodiment each controller is designed to interact with respective device&#39;s operating system native telephony and messaging component in order to determine MNC and MCC values based on device&#39;s operating system. 
         [0040]    In case respective controller is not able to integrate with platform&#39;s native interface, a universal HTML5 markup language based web interface is used for purchase confirmation. Operating system detection is performed by converter based on user agent property according to RFC 1945. Device and purchase identification details are transmitted using operating system&#39;s native messaging component through SMS-PP protocol as a Mobile Originated (MO) short message service transfer. Mobile subscriber identification is performed by using Mobile Subscriber Integrated Services Digital Network Number (MSISDN) value according to ITU-T specification E.164. MSISDN value is obtained from Mobile Originated short message service transfer by short code gateway. 
         [0041]      FIG. 1  shows a system to enable and simplify cross-platform purchases on mobile devices. In  FIG. 1 , a system consists of at least one data computing facility, which is connected to mobile carrier billing infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various mobile device types and platforms. 
         [0042]    In  FIG. 1  a method to facilitate purchases on mobile devices in a first embodiment via cross-platform native user interface comprises following steps (Interaction with user through native device user interface): 
         [0043]    1. Transaction initiated by user 
         [0044]    2. Transaction details requested from converter 
         [0045]    3. Transaction details sent to controller 
         [0046]    4. Transaction details displayed to user 
         [0047]    5. Transaction confirmation obtained from user 
         [0048]    6. Transaction confirmation forwarded to converter 
         [0049]    7. Confirmation transaction details forwarded to carrier 
         [0050]    8. Successful payment confirmed by carrier billing system 
         [0051]    9. Payment confirmation sent to controller 
         [0052]    10. Payment confirmation displayed to user 
         [0053]      FIG. 2  shows a system to facilitate purchases on mobile devices by automatic Mobile Network Code, Mobile Country Code and MSISDN detection. In  FIG. 2 , a system comprises at least one data computing facility (DCF), which is connected to mobile carrier billing, short code and networking infrastructure and a plurality of converters to communicate and interface with a plurality of controllers for various mobile device types and platforms. 
         [0054]    In  FIG. 2 . a method to facilitate cross-platform purchases on mobile devices in a second embodiment by MNC/MCC/MSISDN detection comprises following steps: 
         [0055]    1. Transaction initiated by user 
         [0056]    2. MNC and MCC values are sent to converter for coverage check 
         [0057]    3. MNC and MCC values are checked with DCF coverage database 
         [0058]    4. MNC and MCC support is confirmed by DCF to converter 
         [0059]    5. MNC and MCC confirmation forwarded to controller 
         [0060]    6. Encoded transaction details are sent via SMS text message to short code using messaging component 
         [0061]    7. MSISDN value and transaction details are obtained by short code from incoming SMS text message and sent to DCF 
         [0062]    8. Transaction details are decoded by DCF and sent to carrier billing system for making a MSISDN based transaction. 
         [0063]    9. Transaction billing status is confirmed by carrier billing to DCF 
         [0064]    Referring to  FIG. 3 , an illustrative system for facilitating purchase on mobile device  102  is depicted in third embodiment combining and integrating first and second embodiments. The system comprises mobile device component  101  and server component  105  connected to database component  111 . Mobile device component  101  and server component  105  are connected to a network. Mobile device component  101  comprises: a device controller  103 , configured to interface with operating system of the device, available API&#39;s and functions including but not limited to detecting device operating system, it&#39;s type and version; a purchase user interface controller  104 , configured to interface with input and output components of mobile device including but not limited to display, keyboard, speaker, touchscreen, buttons and indicating lights. Server component  105  comprises user interface converter  106 , at least one platform native interface controller, for example platform native interface controllers  107 ,  108 ,  109  and a universal user interface controller  110 . 
         [0065]    After the purchase is initiated by the user, respective process is created in purchase user interface controller  104  and device and operating system information is requested from device controller  103 . In response to receiving the request, device controller  103  communicates with mobile device core platform  102  and device controller  103  obtains: device information including name, manufacturer, model number, type, screen size; operating system including name, version, manufacturer. This obtained information is required for identifying the device and supporting appropriate user interface for purchase. Respective data is sent to purchase user interface controller  104 . 
         [0066]    Purchase user interface controller  104  sends device and operating system information via network to user interface converter  106  of server component  105 . After obtaining device and operating system information and comparing with the list of supported platforms and operating systems, user interface converter  106  connects to respective platform native interface controller  107 ,  108 ,  109 , that matches the platform of mobile device.  FIG. 3 . depicts 3 sample platform native interface controllers, which are purely illustrative and the amount and type of actual controllers varies in order to match all mobile platforms and operating systems. Platform native interface controller  107 ,  108 ,  109  connects to database component  111  and obtains respective native user interface data including but not limited to graphical and textual combination of elements, that is common for respective platform and operating system.  FIG. 6 . depicts samples of such elements for native and universal user interfaces. Native user interface data is sent to user interface converter  106  and converted to common format in order to be forwarded to purchase user interface controller  104  on mobile device. 
         [0067]    In case of the platform or operating system is not detected by device controller  103  or not supported by any of the existing native interface controllers  107 ,  108 ,  109  the user interface converter  106  shall request universal user interface data from universal user interface controller  110 . Respective universal user interface data and elements are obtained from database component  111  and sent back to user interface converter  106  in same way as with native user interface data. Methods and control procedures conducted within the process of requesting the user interface of  FIG. 3  are detailed in  FIG. 4 . 
         [0068]    The process is started  201  by purchase user interface controller  104 . If device controller  103  does not succeed in identification of device platform and operating system  202 , the universal user interface is requested  204  from user interface converter  106  and universal user interface controller  110 . If identification  202  is completed successfully, the decision of selecting an appropriate user interface is passed to user interface converter  106 , user interface converter  106  compares device platform and operating system with the list of supported native user interfaces  203 . In case of a positive match, respective native user interface is requested  205  from appropriate platform user interface controller  107 ,  108 ,  109 . In case a matching native user interface is not found, a universal user interface is requested  204  from universal interface controller  110 . Resulting user interface is forwarded to mobile device and is used for completing the purchase  206 . 
         [0069]    After obtaining the user interface data from user interface converter  106  by purchase user interface controller  104  of mobile device as depicted on  FIG. 3  and  FIG. 4 , it&#39;s is exposed to the user through visual display of the device  102 .  FIG. 6 . depicts illustrative samples for native and universal user interfaces. 
         [0070]    In order to further facilitate the process of purchase on mobile device for the user, purchase user interface controller  104  may obtain additional information from device controller  103 . 
         [0071]    The methods and procedures of obtaining additional information by purchase user interface controller  103  are depicted on  FIG. 5 . The process is started  301  after obtaining user interface data from  206  from user interface converter  106 . If MCC value can not be obtained  302  from device controller  103 , user is asked to select his country from a list  304 . On next step user is asked to provide his network operator  305  in case MNC value was not obtained  303 . Once both country and carrier information is obtained, it is compared with the list of supported countries and carriers  306 . In case user&#39;s country or carrier is not supported for completing the purchase, it is cancelled  308 . Otherwise user is able to continue with the process of completing the purchase  307 . 
         [0072]    In the illustrative embodiments  401 ,  402  and  403  of  FIG. 6  a sample of purchase user interface on mobile device are depicted. Native and universal user interfaces for mobile devices can vary by several components including but not limited to size, color and style of fonts, interface elements like buttons, checkboxes and input fields, descriptive texts, input methods like keyboards, touchscreens and buttons, their position, background, size, visual style and animation effects. All of the above form a native interface experience, unique for each platform and mobile device operating system. 
         [0073]    Referring to  FIG. 1 ,  FIG. 2  and  FIG. 3 ,  FIG. 7  depicts the third embodiment combining and integrating first and second embodiments of the present invention. Mobile device component  702  is a further development of device controller, connected to device core platform  701  and used for interfacing with mobile device input and output components. Server  704  and database components  705  are the further development of data computing facility and remote converters  703  with the purpose of maintaining and sending native user interface data to phone component. 
         [0074]    While the invention has been illustrated and described in detail in the foregoing drawings and description, the same is to be considered as illustrative and not restrictive in character, it being understood that only illustrative embodiments thereof have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected.