GB2526862A - Betting system - Google Patents

Abstract

A betting system links affiliates 5, 6 such as betting organisations and users 7, 8, 9 via user interfaces on a users device and a data server, such that the user can view odds and/or place bets with the affiliates without direct interaction with the affiliate. The user interface may be a mobile app and may include information provided by tipsters, selection of a tipster allowing automatic bet placement. Data from a plurality of affiliates and/or an official data source 4 may be normalised for presentation to the user. The user may have an account with the affiliate and bets may be accepted or rejected based on available funds in a users account. The user may be able to sign up to multiple affiliates using the single platform. The system may comprise a data store 1 connected to data processing means 2 held at a central server or distributed over a plurality of services. Users may register as tipsters. Tipsters may have profiles and associated risk categories and may earn commission. The system may maintain audit trails and provide advertising. Users may enter virtual or real money versions of the application, the virtual application allowing restricted viewing of betting information.

Description

Betting System This invention relates to a betting system.

In particular, it relates to a computer/mobile device based betting system for enabling a user to place bets with a number of providers, aided by as much information as possible.

The betting industry worldwide is very large indeed and there are many different ways to bet and organisations involved. In addition to users who wish to place bets, there are also many international organisations that will take big bets and will set their own odds for various events (such as the odds for horse races). There also many tipsters' who study form, etc and can provide comments and suggestions for any particular event.

Computer or mobile based betting platforms are common. Most of these are provided by a single organisation such that a user can only place bets through this organisation, or are associated with a single tipster for example. It is difficult for a user to be able to thoroughly review a market or at least part of a market in order to determine the different offers being made by different betting organisations and a selection of advices from tipsters and who then choose, using one single platform, where to place a bet. Note in this specification that the various betting organisations (in the UK typical ones for these are Paddy Power, Ladbrokes and so) are termed "affiliates".

The present invention arose in an attempt to provide an improved betting system and platform for computer and mobile use allowing users to view odds from a plurality of affiliates and to trade with any selected one or more of these affiliates, from the system itself, ie without having to separately accept specific affiliation websites or platforms.

According to the present invention in a first aspect there is provided a betting system comprising a data server, means for linking to a plurality of affiliates and one or more user interfaces provided on user's devices, whereby a user can interact, via a user interface, with the data server and thereby interact with one or more of the affiliates to view odds and/or place bets, using the data server, with said one or more affiliates.

Thus a user can place bets directly with affiliates via the system, without having to specifically visit an affiliate's website, or otherwise interact directly with the affiliate.

The user interfaces are preferably interfaces on mobile devices such as mobile phones or tablets and may comprise an app'.

Preferably, a user can also sign up to multiple affiliates through said app without having to specifically visit an affiliate's website, or contact them direct.

The system may also comprise links to services provided by one or more tipsters and be adapted such that a user can view information provided by one or more tipsters, or provided by one or more affiliates.

Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings, in which: Figure 1 shows an overview of a betting system; Figure 2 shows schematically a system architecture; and Figures 3 to 7 are flowcharts, in which: Figure 3 shows how a user may gain use of the system initially; Figure 4 shows a registration process; Figure 5 shows how a user can place a bet by following a tipster or their own selection; Figure 6 shows how tips might be published; and Figure 7 shows integration points.

As shown in Figure 1, on a general level, a betting system/platform comprises a data store 1, connected to a data processing means 2 which may be provided at a central server, or distributed over a plurality of services, for example.

Connections are made to and from this from one or more official sources over official source data APIs (Application Program Interface) 3 and these may be the official data sources of events such as horse racing events, football matches, and so on. Links are also provided via respective APIs to at least affiliate 5, 6. In this example, two affiliate links are shown. These may be betting organisations for example.

Links are also provided to interfaces which may be provided on a user device. For example, a web interface 7 may comprise a website or specific application accessible on a user's computer, a website link or more preferably an app will be provided on a user's mobile and/or tablet 8 and an open API 9 may also be provided which enables other devices and systems to be able to interface with it.

The central data store/processing system 1, 2 may receive external reference data which may comprise various news feeds, details of affiliate deals, market analysis reports and other data which can be useful to the system supplier and/or the end users.

Provider side services can also interface with the data store/processing system. These may comprise a CRM management module 12 which may handle, for example, accounts data, information and processing, communications such as email, SMS and so on with users and others, advertising, including the transmission of adverts, whether targeted or general, to users, etc. A system management module 13 may handle commissions, audits, various reporting and regulatory tasks and client management, including details of clients addresses, contact details and so on.

In general terms, the platform may have or include at least some of the following attributes: * A simple and easy to use interface * Multiple affiliates * Display a consolidated view of odds from many affiliates * Place bets with any affiliate through the Juno platform * View account information (md. balances) from the affiliates * Handle special deals and offers from affiliates * Choose and offer bets with the best odds available from any affiliate * Include a concept of tipsters' o A tipster will have a certain risk category o A tipster can be followed and their bets tracked o A "follower" can have bets placed automatically depending on how they have configured their account, and once a tipster has published their tips * Be completely secure * Offer a wide range of interfaces including website, mobile and tablet * Administration and back office functionality o Market creation and management o Client relationship management and support o Commission payments, reports and audit trails o Tipster management o Advertisements, news and market analysis could be presented to the user o Additional sports and betting markets introduced o Geographic markets and multilingual offerings provided o Multi bet and complex wager offerings added o Tipster profiles o Interaction with social media (eg FacebookTM, Twitter1M, etc) The basic platform (data store 1, data processing means 2) is adapted to display a range of bets from a plurality of different sports in preferred embodiments. For horse racing the official source data may come from "The Jockey Club" in the UK and/or other licensed information provider. This communicates through a gateway G4 with the platforms via a licensed API. The source of official data 4 provides a basic driver for a market displayed to a user over a web interface 7, mobile/tablet API and so on. The data must therefore be normalised and entered into permanent storage at the store 1.

The affiliate data 5 and 6 is also transmitted through respective gateways G5 and G6. Each affiliate may provide live prices and data concerning each published market.

Since in general each affiliate will produce its data in its own unique way then the data must be normalised within the data processing apparatus before being stored, consolidated and published to the web interface/mobile/table app.

The APIs may be by XML feeds for example for at least part of the data but other parts of the data, such as, for example, trading interfaces or account access with a particular affiliate, may require more detail/additional APIs.

Other features of the general scheme are as follows: Pricing Multiple affiliate pricing updated in real-time and made available to the user interfaces 7 to 9.

Affiliate pricing needs to be matched to the markets and consolidated where appropriate.

Markets should be closed at the appropriate times, ie the start of the horse race or the kick-off of a football match.

Market results updated when received and reported to the user.

User Access Users will need to be able to open and manage accounts, link to affiliates and configure their preferences.

Users should be able to link to Tipsters and manage their risk profiles and betting strategies.

Tipsters Users can upgrade themselves to tipsters or register simply as a tipster.

Tipsters may be linked to multiple followers.

Results from bets need to be recorded against the tipster's and possibly user's history.

Algorithms are created that can analyse a tipster's performance and allocate them a score and a risk category (high or low risk).

The user interfaces 7 to 9 should display leader boards with tipster's organised by risk and sorted by success scores.

Orders & Strategies It is possible for a user to create a betting strategy linked to one or more tipster.

Whenever a tipster places a bet then the associated user's strategies need to be exercised.

Since there will be a time delay between the tipsters bet and the followers bets, it may not be possible for all the followers to get the same odds.

Trading A user can place standard bets directly with the affiliates via the system, without having to specifically visit the affiliate's website.

A user can either select the affiliate to use manually, or it may be possible for the user interfaces 7 to 9 to offer better odds or special deals available.

It may be necessary to automatically create an affiliate account for the user.

Depending on the affiliates it may be possible for a user to cancel a bet before the event occurs.

The results of individual bets should be available in the user's trade history.

Audit Trails The system maintains audit trails for every transaction and action that occurs.

These actions include administration changes, strategies, user bets, affiliate updates and user updates.

Administration An administration system is provided, using the system management tools 13. The main functions of this are, for example: Commission profile configuration Manual commission payments Affiliate commission payment checks Problem locating and audit trails Reporting Tasks Regulatory reporting and tasks Amending clients or tipsters Management of markets and bets available Client Relationship Management The system is able to send email or SMS updates to confirm user changes

Client statements and history should be available

Client trading history reports to locate active and dormant users Advertising, offers and incentives Platforms To offer the most flexibility the user interface may be available on different platforms, eg Website 7 Mobile -OS, Android or Windows mobile 8 Tablet-iOS, Android of Windows mobile 8 Figure 2 shows one example of a typical system architecture. The public side 20 includes a web interface 7, mobile tablet interface 8 and so on, in addition to the affiliate sources 5 and 6 and administrator 13. The user interfaces] and 8 interface with respective client data servers 21, 22. The affiliate or data sources interface through respective gateways 23 and 24. The administrator administers via an administration website 25.

The basic data base may be based on Microsoft SQL for example. The database interfaces with a local area network 26 which includes a pricing and market making module 27, a bet handler 28, a bet processing module 29 and a data nornialisation, storage and distribution module 30. As described above, data from official sources and also from affiliates may be received in different formats and using different methodology and it would be necessary to normalise this, such that they can all be compared and used together and this is achieved in the module 30. The modules 27 to 30 communicate with an in-memory data storage module 31 and also with a tipster and strategy handling module 32. The in-memory data storage module 31 is connected to, or forms part of. a main memory or data store 33.

The various modules are created using proprietary code for example and may run as services on a Window platform. They may include remote monitoring features. Each module (otherwise known as an engine) is most preferably designed to handle a specific task, such as communication with an affiliate or various trading or managing strategies.

This enables development and maintenance tasks to be undertaken in parallel.

The web interface 7 will be via a website. The mobile/tablet interfaces may be by a website or more preferably may be via a mobile app.

Embodiments of the invention enable a user to place a bet quickly with an affiliate based on a tipster's knowledge, either manually or through an auto-copyfunction. In a little more detail, it provides the following functions: The user interface, for mobile use 8, comprises a Smartphone (Android, iPhone or similar) application for the purpose of sharing betting information and tips, with the ability to then place bets via an affiliate.

The application / platform is aimed at facilitating users to engage and network with other users for the provision and receipt of betting tips and advice.

The purpose of the platform isto offerthe userthe abilityto participate in a non monetary betting gaming experience, or, additionally, to both easily and quickly place monetary bets through a partner third party commercially and legally established affiliate[s] accessed directly from the application.

The application/platform will not offer any gambling opportunities in its own rights and will have no monetary handling capabilities.

The application may offer two distinct participation levels consisting of virtual and real money versions. There is little operational difference between the two applications.

The perceivable cosmetic differences between virtual and real money are in visual presentation and the depth and scope of data available on the virtual version.

The real money version provides a portal through to the live betting service of one or more affiliates, without the need to leave the application.

All real money users have the ability to be followed as a tipster. Once they have also met specific criteria they will then be eligible to receive a commission based on the revenue generated by users following their selections.

Upon meeting the criteria the user will be entitled to receive a commission based on how much net revenue is placed on the live gambling facilities of the partner site(s) by ordinary users connected to their network. This will be monitored as the portal that the bets are placed through will be connected to and record which tipster has generated what traffic/value meaning that ordinary users may follow a number oftipster's but any commissions payable are restricted only to the tipster(s) that generates the revenue traffic. Note that there is no necessity for a user to accept this change in status.

The exception will be professional tipsters with proofed history or who offer a service which is paid by a monthly fee, who will be automatically deemed to have met the criteria. In the case of paid for services a deduction will be made each month from the monthly subscriptions to cover costs of the application.

All users have the ability to enter the virtual version of the application. This will provide them with: * The ability to follow tipsters either by viewing a league table or by searching for a specific user.

* View bets or tips by others and receive user configurable updates (via SMS, email etc) * Place notional non monetary value bets on the application by following a tipster(s).

Values of betting notional money will be reset after a defined period (eg: monthly).

* Virtual users will be able to see live' data from current betting byTipster's but without specific data (for example the location of the race and the current advised odds but not the time of the race or the name of the horse).

All users can use the real money version of the application. This will provide them with: * The ability to follow tipsters either by viewing a league table or by searching for a specific user.

* View bets or tips bytipsters and receive user configurable updates (via SMS, email, etc).

* Follow tips by a tipster and be notified when tips are posted by that user placing immediate bets via a portal connected to third party site.

* Automatically "copy" the tipsters bets, the application will then place the relevant bets with an affiliate(s) if monies are available without manual intervention and advise the user of the bets placed via SMS or email.

* Follow more than one tipster and select a certain percentage of a user defined amount to be split between those tipsters, for example £10 total stake, split 50% on subscriber A, 25% on tipster B and 25% on tipster C. * View a league showing results viewable in a number of different formats (eg biggest win, win %, etc).

* Make own selections and place bets without following another user.

Figure 3 shows how a user may gain access to a mobile app for the system. Via a website 30 the user may gain access to the system website 8 or he may access this directly. He may also link to the app via iTunesTM, the Google Play StoreTM, or other app stores on Android or other platforms 31. Since betting activities are often age restricted in certain countries, the user may be required to prove his age 32. the receives details of the app including screenshots, etc 33 from where they can then download the app 34.

Figure 4 is a flowchart explaining a registration process in order to participate in the system. This is split into two different types as described above, virtual and real money.

Once the application has been installed on the phone 35, the user opens the app 36 to a splash page 37. This leads to a landing page (tutorial) 38 which explains the system. The next page 39 allows a user to select either virtual or real play. For virtual play 14, the user is passed to a tipster page 41 and can then register on the app 42, by inserting his details such as email, a user name, password, security word and so on. Once all the required details have been added, an email message 43 is sent from the system to the email address the user has given. This is then verified 44. In the virtual system, this can lead to an amount of virtual money (say £1,000) being added to the user's account. For real money play, the user is directed again to a tipster page 40 and encouraged to register on the app 41. He then has to enter his email, user name, password, security word, etc details 42 and then an email verification 43 is again sent to the user's email account. This is then verified by the user 44. For the real money system, after email verification the user is then prompted whether he is already registered with a sponsor/affiliate (or with more than one of these) 45. If he is already linked to one of these, ie already has an account with them, then he is prompted to enter account details such as password, etc for that particular affiliate 46. If the user has no current links with any affiliates, then the app will redirect the user to the affiliate's site 47 where he may register. This takes place within the app, so the user does not need to specifically visit the affiliates website.

Thus, the user is provided with means for signing up/registering with an affiliate through the app.

Once registered with affiliates and having been logged into these, then the affiliate account details can be saved in the application to enable automatic login afterwards, if required.

Figure 5 is a flowchart explaining how a user can place a bet by following a particular tipster, or place bets based on their own selections. Initially, the user logs onto the system and decides to look at tipster details. They will be provided with a list of tipsters from which they choose their desired tipster and are directed to that tipster page 50. From here, they are given two options, either to follow the tipster's recommendations or to place bets themselves (known as DIV -Do It Yourself) 51. If the user wishes to follow the tipster, they will be presented with a screen 52 which provides them with filtering options to filter to the desired sport of their choice. This may have further filters to select, including the choice of whether the event is free, paid or both and within certain time frames, for example. The information may be updated 53 based on the particular filter used. If the user is happy with this he can choose to select the tipster 54. He then receives the tipster's page including information on recent form 55. Various parts of this 56, 57 and 58 enable the user to see how well the tipster has performed in their relevant sport and screenshots may be provided showing this and thus giving the user information such as the tipster's success rates. The user may be able to view the tipster's latest selections ("tips of the day") 56 or to follow/u nfollow the tipster. He is able to auto-copy the tipster 58, ie to automatically choose the tipsters selected tip (eg place bet on Horse A in Race X).

After the user has selected a particular race, the user is selected with a particular list of horses together with the tipster's tips and can select one of these or select the tipster's auto bet 59. If the user chooses to follow the tipster's suggestion, then the user may receive a confirmation 60 that the bet will been placed. From here, the system retrieves account information from the used affiliate, balances available, odd, etc and displays whatever information a user's default setting have been set to. That is, the user can choose what information is displayed to him at this stage, as he may be interested in all information or simply the fact that the bet has been made. When an auto-copy bet 58 is made, the system uses a default affiliate. This may have been selected by the user in a configuration step. However, if when the bet request is passed to the affiliate, the balance in that user's account, or their credit, at that affiliate is insufficient, then the application may be arranged to look at other accounts the user has and to fulfil it based upon the best selected odds and the highest balance available, or on other criteria.

If the user decides not to follow a tipster but instead to use the DIV approach, then they are presented with a sport select screen 61 from where they can select the relevant sport. Relevant data is then retrieved from the database 1, 2 at step 62. The user then selects a particular bet and places this 63. This then again goes to a bet confirmation screen 60 where the system tries to place the bet and this will be allowed if the user has sufficient credit/funds available in the affiliate account.

Figure 6 is a flowchart showing how a tipster can publish tips. As described, a tipster is a user that has been upgraded or specifically registers as a tipster. Thus, the tipster logs on to the system 70. They then select the DIV option on the tipster page 71.

The tipster then selects a particular sport 72 and the system then retrieves the various fixtures within this sport and the odds within each fixture 73 from the affiliates, via the affiliate database 5. The tipster can then select ones of these, according to his experience and skill and choose to publish them 74. These tips, together with the current prices offered by the affiliate are then stored on the system servers in the system database 33.

If a user has chose to auto-follow a tipster then notifications of these will be sent automatically to that user together with any auto-updated information 76. If a tipster recommends making a bet, then the auto-copy bets may also be sent 77 and the user can then decide whether to accept the bets 78. The user may decide to place all bets selections used by the tipster or only the best bets selected by the tipster. Once the bets have been placed via the affiliate, then a bet confirmation will be sent back from the affiliate database and all bets placed will be logged on the user's history in the database 79. Any betting winnings will then be calculated and stored against the user's details.

Figure 7 shows integration points between the application (on the left-hand side of the figure), the system server Sand an affiliate server (eg 5). That is, points where the user interface (app, etc) must interface, communicate with these parts. These show for example that the splash and home pages are clearly shown on the app and there is no integration with external databases necessary for these. For login and registration interfaces with both the system server Sand the affiliate serverS are necessary. For the tipster table and tipster information following screens, integration with only the servers is required, and so on as shown in the figure.