WO2017139836A1

WO2017139836A1 - Auction systems and methods

Info

Publication number: WO2017139836A1
Application number: PCT/AU2017/050124
Authority: WO
Inventors: Qi Chen; Aimee PAGRAM
Original assignee: Rea Group Ltd
Priority date: 2016-02-15
Filing date: 2017-02-15
Publication date: 2017-08-24

Abstract

A method for conducting of an auction that caters to both on-site physical bidding and online bidding. An auction server communicates with computing devices registered for the auction and a content file server across a network. The auction server application is receiving a request from one of the plurality of computing device and determining a request type of the request. The method further comprising responsive to determining that the request is a request to accept a proposed bid and that the proposed bid is acceptable, determining an updated current increment value based on a comparison of the proposed bid and a current bid for the auction, storing the updated current increment value as the current increment value; storing the acceptable proposed bid as the current bid, and transmitting the updated current increment value and current bid to the content file server for broadcasting to some of the computing devices.

Description

"Auction systems and methods"

Technical Field

[1] Described embodiments relate to auction systems and methods. Some embodiments relate to auction systems and computer-implemented methods for facilitating the conducting or hosting of auctions that allow or cater to both on-site bidders and online bidders.

Background

[2] With a traditional style auction, bidders, or their representatives, partaking in an auction are physically present at the same location as the auctioneer. More recently, online auction systems have been made available, which allow bids to be received online from bidders located remotely from the auction system and which are run automatically, independent of an auctioneer in the traditional sense.

[3] There is a desire to address or ameliorate one or more shortcomings or disadvantages associated with existing auction systems and methods or to at least provide a useful alternative thereto.

[4] Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention as it existed before the priority date of each claim of this application.

[5] Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

Summary

[6] Some embodiments relate to a computer implemented method for facilitating the conducting an auction that caters to both on-site physical bidding and online bidding, the method implemented by an auction server in communication with a plurality of computing devices registered for the auction and a content file server across a communications network, the auction server comprising one or more processors and memory comprising an auction application, which when executed by the one or more processors, is configured to perform the method, the method comprising: receiving a request from one of the plurality of computing devices; determining a request type of the request; responsive to determining that the request is a request to accept a proposed bid and that the proposed bid is acceptable: determining an updated current increment value based on a comparison of the proposed bid and a current bid for the auction; storing the updated current increment value as the current increment value; storing the acceptable proposed bid as the current bid; and transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices. For example, determining that the request to accept the proposed bid is acceptable may comprise determining a source of the request.

[7] In some embodiments, determining that the request to accept the proposed bid is acceptable comprises determining a source of the request; responsive to determining that the source of the request is an auctioneer application running on one of the plurality of computing devices, determining that the proposed bid is preapproved; and responsive to determining that the source of the request is a bidding application running on one of the plurality of computing devices, transmitting a request for approval to the auctioneer application and receiving approval of the proposed bid from the auctioneer application.

[8] In some embodiments, determining that the request to accept the proposed bid is acceptable comprises: determining a source of the request; responsive to determining that the source of the request is an auctioneer application running on one of the plurality of computing devices, determining that the proposed bid is preapproved; and responsive to determining that the source of the request is a bidding application running on one of the plurality of computing devices, determining that the proposed bid complies with the current increment level.

[9] In some embodiments, the method further comprises: responsive to determining that the request is a request to accept an auctioneer suggested bid, storing the suggested bid as the current bid; responsive to determining that the increment value should be updated based on a comparison of the auctioneer suggested bid and the current bid, determining an updated increment value and storing the updated increment value as the current increment value; and transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices.

[10] In some embodiments, determining that the increment value should be updated comprises determining a difference between the auctioneer suggested bid and the current bid and responsive to the difference being less than a threshold value, determining that the updated increment value is substantially equal to the threshold value. For example, the threshold value may comprise the current increment value.

[11] Some embodiments relate to a computer implemented method for facilitating the conducting of an auction that caters to both on-site physical bidding and online bidding, the method implemented by an auction server in communication with a plurality of computing devices registered for the auction and a content file server across a communications network, the auction server comprising one or more processors and memory comprising an auction application, which when executed by the one or more processors, is configured to perform the method, the method comprising: receiving a request from one of the plurality of computing devices; determining a request type of the request; responsive to determining that the request is a request to accept an auctioneer suggested bid, storing the suggested bid as the current bid; responsive to determining that the increment value should be updated based on a comparison of the auctioneer suggested bid and the current bid, determining an updated increment value and storing the updated increment value as the current increment value; transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices.

[12] In some embodiments, determining that the request to accept the proposed bid is acceptable comprises: responsive to determining that the request is a request to accept a proposed bid and that the proposed bid is acceptable: determining an updated current increment value based on a comparison of the proposed bid and a current bid for the auction; storing the updated current increment value as the current increment value; storing the acceptable proposed bid as the current bid; and transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices.

[13] In some embodiments, the method comprises: responsive to determining that the request is a request to set/change the current bid, the suggested bid and/or the increment level, determining a source of the request; and responsive to determining that the source of the request is an auctioneer application running on one of the plurality of computing devices, determining an updated current bid, suggested bid and/or increment value from the request, storing the updated current bid, suggested bid and/or increment value as the current bid, current suggested bid and/or current increment value, respectively, and transmitting the updated current bid, current suggested bid and/or current increment value to the content file server for broadcasting to at least some of the computing devices.

[14] In some embodiments, the method comprises: responsive to determining that the request is a request to initiate an auction, transmitting a create session request to the content file server and responsive to receiving acknowledgement of the creation of the session from the content file server, transmitting a notification to at least some computing devices to indicate that the auction session has been established.

[15] Some embodiments relate to a computer implemented method for engaging in an auction that caters to both on-site physical bidding and online bidding, the method implemented by a computing device in communication with an auction sever across a communications network, the computing device comprising one or more processors and memory comprising a bidding application, which when executed by the one or more processors, is configured to perform the method, the method comprising: receiving a request to enable an auto-bidding function from a user via a user interface of the computing device, the request comprising a budget price; storing the budget price as a maximum bid value; responsive to receiving an indication of an auctioneer suggested bid, determining whether the auctioneer suggested bid is greater than the maximum bid value; responsive to the auctioneer suggested bid not being greater than the budget price, transmitting a request to accept the auctioneer suggested bid to the auction server; and responsive to the auctioneer suggested bid being greater than the budget price, issuing an alert to the user via the user interface. For example, the alert may comprise a request for an updated maximum bid value.

[16] Some embodiments relate to an auction system for facilitating the conducting of an auction that caters to both on-site physical bidding and online bidding in the same auction, the auction system comprising: an auction server in communication with a plurality of computing devices across a communications network, the auction server comprising one or more processors and having access to memory storing executable program code comprising or defining an auction application, which when executed by the one or more processors, is configured to perform any of the described methods.

[17] In some embodiments, the auction system further comprises a content file server in communication with the auction server across the communications network, the content file server comprising one or more processors and having access to memory storing executable program code comprising or defining a database auction application, which, when executed by the one or more processors, is configured to: transmit data including at least one of current bid, current suggested bid and/or current increment values to at least some of the computing devices registered for the auction.

[18] In some embodiments, the content file server is further configured to: receive streamed auction audio and/or video content from the auctioneer application running on one of the plurality of computing devices; and responsive to receiving a subscription request to subscribe to the auction session from one or more of the others of the plurality of computing devices, streaming the auction audio and/or video content to the subscribed computing devices.

[19] In some embodiments, the auction system comprises at least one computing device in communication with the auction server across the communications network, the computing device comprising one or more processors and having access to memory storing executable program code comprising or defining a bidding application, which, when executed by the one or more processors, is configured to perform any of the described methods,

[20] Some embodiments relate to computer program product comprising a computer readable medium encoded with computer executable instructions, which when executed in a computer system, is effective to cause the computer system to carry out any of the described methods, For example, the computer readable medium may be a non-transitory computer readable medium.

Brief Description of Drawings

[21] Figure 1 is an example of a communications system comprising an auction system, according to some embodiments; [22] Figure 2 is a block diagram of program memory of an auction server of the auction system of Figure 1, according to some embodiments;

[23] Figure 3 is a block diagram of memory of a mobile computing device of the auction system of Figure 1, according to some embodiments;

[24] Figure 4 is a block diagram of program memory of a content file server of the auction system of Figure 1, according to some embodiments;

[25] Figure 5 is a schematic representation of data flow between the auction server, user interfaces of two or more mobile computing devices and the content file server of the auction system of Figure 1, according to some embodiments;

[26] Figure 6 is a data flow diagram of a method of processing an auction initiation request received from an auctioneer or assistant application deployed on a mobile computing device of the auction system of Figure 1, according to some embodiments, the method implemented by the auction system of Figure 1 ;

[27] Figure 7 is a data flow diagram of a method of processing a request for setting an increment value received from an auctioneer or assistant application deployed on a mobile computing device of the auction system of Figure 1, according to some embodiments, the method implemented by the auction system of Figure 1;

[28] Figure 8 is a data flow diagram of a method of processing a request to accept a suggested bid received from a bidder application deployed on a mobile computing device of the auction system of Figure 1 according to some embodiments, the method implemented by the auction system of Figure 1 ;

[29] Figure 9 is a data flow diagram of a method of processing a request to accept a proposed bid received from a bidder application deployed on a mobile computing device of the auction system of Figure 1 according to some embodiments, the method implemented by the auction system of Figure 1 ;

[30] Figure 10 is a process flow diagram of a computer-implemented method of facilitating the hosting of an auction catering to both on-site physical bidders and online bidders, according to some embodiments, the method implemented by the auction server of the auction system of Figure 1 ;

[31] Figure 11 is an example screen shot of a display of an graphical representation of an auction progression displayed on a user interface of an auctioneer and/or assistant computing device of the communications system of Figure 1;

[32] Figure 12 is an example screen shot of a display showing information pertaining to an auction in progress displayed on a user interface of an auctioneer and/or assistant computing device of the communications system of Figure 1;

[33] Figure 13A, is an example screen shot of a display of information pertaining to an auction in progress as displayed on a user interface of an online bidder or viewer's computing device;

[34] Figure 13B is an example screen shot of a display showing an input screen to allow a bidder to engage with an auction in progress to propose a bid as displayed on a user interface of an online bidder's computing device;

[35] Figure 13C is an example screen shot of a display showing an input screen to allow an auctioneer and/or assistant to place a bid on behalf of an on-site bidder as displayed on a user interface of an auctioneer and/or assistant computing device;

[36] Figure 14 is a process flow diagram of a computer-implemented method of engaging in an auction that caters to both on-site physical bidders and online bidders, according to some embodiments, the method implemented by a bidder application deployed on a mobile computing device of the auction system of Figure 1 ;

[37] Figures 15A is an example screen shot of a display showing an input screen to allow a user to view and select from a list of items providing information pertaining to upcoming or past auctions;

[38] Figure 15B an example screen shot of a display showing an item of the list of items shown in Figure 15A; [39] Figure 15C is an example screen shot of a display showing an input screen to allow an auctioneer and/or assistant to place a bid on behalf of an on-site bidder as displayed on a user interface of an auctioneer and/or assistant computing device;

[40]

[41] Figure 16 is an example screen shot of display showing an input space to allow a user to input a suggested bid for display on a user interface of a bidder or viewer' s computing device; andFigure 17 is an example of an auction report.

Description of Embodiments

[42] Described embodiments relate to auction systems and methods. Some embodiments relate to auction systems and methods for facilitating the hosting or conducting of auctions that allow or cater to both on-site physical bidders and online bidders participating in the same auction. Such auction systems and methods enable auctioneers to host traditional outdoor or indoor auctions at any location where people can gather together and accept physical bids from bidders present at the auction and online bids from remote bidders through use of the auction system. In general, physical bids are bids that are not made online but are made by bidders located in the vicinity of the auctioneer by signalling to the auctioneer or their assistant.

[43] One advance in computer technology provided by the described auction system resides in the particular computerisation that enables the auction system to distinguish between requests relating to physical bids, for example, received on behalf of onsite bidders, and requests relating to online bids, for example, received from onsite or offsite online bidders, to allow for appropriate processing of the requests to thereby cater for both types of bidders. This technical solution provides a significant improvement over known auction systems which are not equipped to cater to both on-site physical bidders and online bidders participating in the same auction. Further, this improvement in the functioning of the described auction system is independent of the auction data being processed.

[44] For real estate auctions, for example, it is common for multiple real estate agents to be present, one of those being designated as the auctioneer and at least one other being designated as an auctioneer's assistant. In some embodiments, the described auction systems and methods allows agents or auctioneers or their assistants to control the pace of the auction by setting and controlling minimum increments of bids before and during the auction and to finish auctions at will.

[45] The described auction systems and methods may provide live audio and/or video streaming of the auctioneer conducting the auction at the physical location of the premises to the computing devices associated with some or all participants of the auction, including viewers and bidders. Auction audio and/or video playback may be available for streaming to computing devices.

[46] The described auction systems and methods provide real-time data

reporting/visualisation of the bids of the auction as the auction progresses. For example, in some embodiments, a real-time updated price chart based on the progress of the auction and/or bid history may be displayed on a display of the auctioneer or the auctioneer assistant' s computing device and broadcast to all bidders' or registered parties' computing devices. For example, the price chart may be benchmarked against historical and advertised prices.

[47] Referring now to Figure 1, there is illustrated a communications system 100 comprising an auction system 102. The auction system 102 comprises an auction server 104 in communication with a plurality of mobile computing devices 106 across a communications network 108, such as a local area network, a wireless data network, an intranet or the Internet or a combination of a number of such networks.

[48] The auction system 102 further comprises a content file server or database server 110 for storage and retrieval of data. In some embodiments, the content file server 110 may be coupled to and accessible by the auction server 104 and/or the computing devices 106, for example, directly or via a private communications network. In some embodiments, the content file server 110 may be coupled to and accessible by the auction server 104 and/or the computing devices 106, over the communications network 108. The content file server 110 may be configured to store data pertinent to operations of the auction server 104 and the provision of service to the computing devices 106. For example, the content file server 110 may store data pertaining to an auction being conducted by an auctioneer employing the auction system 102. [49] In some embodiments, the auction server 104 may comprise the content file server 110. In some embodiments, the auction server 104 and/or the content file server 110 may each comprise a single server or multiple servers or server systems. In some embodiments, the computing devices 106, may comprise a mobile or hand-held computing device such as a smartphone or tablet, a laptop, or PC, and may, in some embodiments, comprise multiple computer devices. In some embodiments, the content file server 110 may comprise a socket server.

[50] As shown in Figure 1, the auction server 104 comprises a processor 112 (which may include multiple processing components or multiple virtual or physical servers operating together), program memory 114, data memory 116 and a network interface 118. The processor 112 may include components such as digital signal processing units (DSPUs), central processing units (CPUs), arithmetic logic units (ALUs) and registers for storing data. Program memory 114 and/or data memory 116 may comprise a combination of volatile and non-volatile computer readable storage. For example, program memory 114 may include read-only memory (ROM) such as erasable ROM (EROM) and electrically erasable programmable ROM (EEPROM or flash ROM), or random access memory (RAM) such as static RAM (SRAM), dynamic RAM (DRAM) or non-volatile RAM (NVRAM or flash). Program memory 114 has sufficient capacity to store program code executable by the processor 112 in order to perform appropriate processing functions as described herein, including providing an auction platform for facilitating an auction. Data memory 116 may be configured to store data pertinent to operations of the auction server 104 and provision of service to the computing devices 106, and/or to store information pertaining to the auction platform, an auction being conducted and/or previously conducted auctions. The network interface 118 may comprise suitable hardware and software interfaces to facilitate wireless communication with computing devices 106 and server 104, for example, over a network, such as communications network 110. In some embodiments, the network interface 118 may comprise suitable hardware and software interfaces to facilitate wired communication between the auction server 104, computing devices 106 and content file server 110.

[51] The computing device(s) 106 comprises at least one processor 120, one or more forms of memory 122, a user interface 124 and a network interface 126. Memory 122 may comprise volatile (e.g. RAM) and n-volatile (e.g. hard disk drive, solid state drive, flash memory and/or optical disc) storage. For example, memory 122 may store or be configured to store a number of software applications or applets executable by at least one processor 120 to perform various device-related functions discussed herein. The user interface 124 may comprise at least one output device, such as a display and/or speaker, for providing an output for the computing device 106 and at least one input device, such as a touch-screen, a keyboard, mouse, microphone, video camera, stylus, push button, switch or other peripheral device that can be used for providing user input to the computing device 106. The network interface 126 may comprise suitable hardware and software interfaces to facilitate wireless communication with the auction server 104, other computing devices 106 and/or content file server 110, for example, over a network, such as communications network 110. For example, the network interface 126 may comprise a USB port, Ethernet port, a wireless adapter or a Bluetooth module. In some embodiments, the network interface 126 may comprise suitable hardware and software interfaces to facilitate wired communication between the computer device 106, the auction server 104, and/or content file server 110.

[52] Similar to auction server 104, the content file server 110 comprises a processor 128 (which may include multiple processing components or multiple virtual or physical servers operating together), program memory 130, data memory 132 and a network interface 134. The processor 128 may include components such as digital signal processing units (DSPUs), central processing units (CPUs), arithmetic logic units (ALUs) and registers for storing data. Program memory 130 and/or data memory 132 may comprise a combination of volatile and non-volatile computer readable storage. For example, program memory 130 may include read-only memory (ROM) such as erasable ROM (EROM) and electrically erasable programmable ROM

(EEPROM or flash ROM), or random access memory (RAM) such as static RAM (SRAM), dynamic RAM (DRAM) or non-volatile RAM (NVRAM or flash). Program memory 130 has sufficient capacity to store program code executable by the processor 128 in order to perform appropriate processing functions as described herein. Data memory 132 may be configured to store data pertinent to operations of the content file server 110 and provision of service to the auction server 104 and the computing devices 106, and/or to store information pertaining to the auction platform, an auction being conducted and/or previously conducted auctions. The network interface 134 may comprise suitable hardware and software interfaces to facilitate wireless communication with computing devices 106 and auction server 104, for example, over a network, such as communications network 110. In some embodiments, the network interface 134 may comprise suitable hardware and software interfaces to facilitate wired communication between the content file server 110 and the auction server 104 and computing devices 106. [53] Referring now to Figure 2, there is illustrated a block diagram of program memory 114 of the auction server 104. Program memory 114 comprises program code including an operating system 200, and an auction application 202, supported by suitable application framework 204, such as Symfony (for PHP). The auction application 202 comprises program code, such as executable code modules, which includes a data handling module 208, a bidding module 208, an increment module 210 and a streaming module 212. The executable code modules of the auction application 202, when aggregated and executed by the processor 112, perform programmed functions as described herein and cause the auction server 104 to provide the auction platform to the computing device(s) 106 to facilitate the conducting and management of an auction, catering to both on-site bidders and online bidders as will be discussed in more detail with reference to Figures 5 to 14.

[54] The data handling module 206, when executed by the processor 112, is configured to receive requests or messages from authorised parties at the computing device(s)106, for example, such as bidders, the auctioneer, the auctioneer's assistant and/or the vendor, and to determine how the requests are to be processed. For example, the data handling module 206 may be configured to determine a source and/or type of the received request and to pass the request to at least one of the bidding module 208, the increment module 210 and/or the streaming module 212 based on the type of the request received. In some embodiments, the data handling module 206 may be configured to determine the source of the request, for example, to determine whether the request has been received from an auctioneer application, an assistant application or a bidder application. For example, the request may include an source indicator indicating the source or application type source from which the request was received. The data handling module 206 may be configured to associate the received request with a particular computing device 106 from which it was received and/or a user associated with the computing device 106 from which it was received. In some embodiments, the data handling module 206 may be configured to determine the type of the request, for example, to determine whether the request comprises a request to start an auction, to store a value for the current bid and/or the current increment value, to record an auctioneer suggested bid, to accept an auctioneer suggested bid, to change an increment level, and/or to propose a bid, for example of a value greater than that of the current auctioneer suggested bid or the current bid plus the current increment value, or of a value less than the auctioneer suggested bid or that dictated by the current increment value. The functionality of the data handling module 206 is described in more detail below with reference to Figures 5 to 14. [55] The bidding module 208, when executed by the processor 112, is configured to process requests received from the data handling module 206, such as requests for storing a value for the initial current bid, recording an auctioneer suggested bid, accepting auctioneer suggested bids and/or proposing bids from parties at the computing device(s)106. The requests may be associated with physical bids received from the auctioneer or assistant' s computing device 106 on behalf of bidders physically present at and partaking in the auction or the requests may be associated with online bids received from a bidder's computing device 106.

[56] The bidding module 208, when executed by the processor 112, is configured to determine how to process the requests based on the type of request received and/or a source from which the request was received. For example, the bidding module 208 may store or update information in the data memory 116 and/or may interact with the increment module 208, the database bid history module 404 and/or the user interface 124 of one or more of the computing devices associated with the auctioneer, auctioneer' s assistant and/or bidder when processing requests as described in more detail below with reference to Figures 5 to 14.

[57] The increment module 210, when executed by the processor 112, is configured to process data received from the data handling module 206, such as requests to set initial increment values and/or change increment values from parties at the computing device(s)106, such as the assistant or the auctioneer. In some embodiments, the current increment value may dictate a lower threshold increment value. The increment module 210, when executed by the processor 112, is also configured to process data received from the bidding module 208 to determine any change in the increment value that may arise from a received auctioneer suggested bid received on behalf of an on-site bidder or an online bidder and/or an accepted proposed bid from a bidder. For example, in some embodiments, the increment module 210 may determine any such change in the increment value by comparing the suggested bid or proposed bid with the bid previously recorded as most recent or current bid, to determine whether difference between the two bids is less than or greater than the current increment value.

[58] The increment module 208, when executed by the processor 112 may store or update the initial increment value and/or a changed increment value as the current increment value in the data memory 116 and/or may interact with the database increment module 406 (Figure 4) of the content file server 110 to cause the database increment module 406 store or update the initial increment value and/or a changed increment value as the current increment value in the data memory 132. The increment module 208 may interact with the data memory 116, the data handling module 206, the bidding module 208 and/or the database increment module 406 when processing requests as described in more detail below with reference to Figures 5 to 14.

[59] The streaming module 212, when executed by the processor 112, is configured to receive requests to initiate sessions from a requesting party (for example, an auctioneer or auctioneer's assistant) at the computing device(s)106, instruct a database streaming module 406 (Figure 4) of the content file server 110 to establish a session, receive notification of whether the session was successfully established from the content file streaming module 406 (Figure 4) and notify the requesting party at the computing device(s)106, and notify all interested parties that the auction session has been established. For example, interested parties may include bidders and in some cases, viewers, who may have registered for the auction.

[60] Program memory 114 may also comprise web server functions 214 (e.g. using a hypertext transfer protocol daemon (HTTP)), data processing functions and data storage and retrieval functions (e.g. using structured query language (SQL) support, such as object- relational database 216) in conjunction with content file server 110. Program memory 114 may also comprise scripting language support 218, such as Microsoft™ ASP, ASP.NET, Java/J2EE or PHP.

[61] When supported by and combined with the application framework 204, and the other server- side functions described previously, the auction application 202 provides an auction platform for facilitating an auction for catering to both on-site bidders and online bidders. In some embodiments, the auction platform may encompass activities that can be viewed as being performed or executed at the computing devices 106. However, it is to be emphasised that the activities performed or executed at the computing devices 106 are reliant on program code (including applets, where appropriate) served by auction server 104 to the computing devices 106 and executed by a browser application 304. The functionality of the auction platform is therefore driven by code executed and served by the auction server 104.

[62] Referring to Figure 3, memory 122 of the computing devices 106 includes an operating system 300 and a number of software applications or applets executable by at least one processor 120 to perform various device-related functions. At least one such software application includes a browser application 304 for enabling a user to navigate to sites accessible over the communications network 108 to receive content therefrom. In some examples, the browser application 304 can be used to communicate with auction server 104 to request content therefrom, in the form of one or more web pages provided as program code to the browser application 304 and executable by the processor 120. According to some embodiments, the auction server 104 is configured to serve code to the computing devices 106 to provide an auction platform generated by browser application 304 and viewable on a display of the user interface 124. Thus, the auction server 104 can be considered to act as an auction system or to act as a host for such a system.

[63] In some embodiments, the browser application 304 may be supplemented by a special purpose add-on or may be substituted by special purpose user software (i.e. an "app" for a smart-phone or tablet device) in order to perform the functions described herein or to facilitate such functions. For example, for a computing device 106, a special purpose application 306 may be downloaded from the auction server 104 or a separate dedicated download server (not shown) and installed on the computing device 106. When such a special purpose application 306 is executing on the mobile user computing devices 306, it may facilitate appropriate formatting, interaction, display and input to enable the user interface functionality described herein. In this way, the special purpose application 306 cooperates with the auction server 104 to provide access to and interaction with the auction platform realised by the auction application 202 implemented by the auction server 104.

[64] For example, the special purpose application 306 may comprise an auctioneer application, an assistant application, a bidder application or a viewer application, wherein each of the special purpose application 306 is configured to allow a user to perform specialist functions as will be described in more detail below with reference to Figures 5 to 14. In some embodiments, the auctioneer application and the assistant application may be different modes of the same application which allow or provide some differing functions or permissions. For example, an auctioneer/assistant application may comprises an auctioneer mode which may be a passive mode of the auctioneer/assistant application and may be configured to display information pertinent to the auction on the user interface 124 to assist the auctioneer in conducting the auction whereas the assistant mode may be an active mode of the of the auctioneer/assistant application and may be configured to display pertinent to the auction and to allow a user (e.g. the assistant or auctioneer) to input information and requests into the auction system 102, such as requests for initiating an auction, setting or changing initial values for the default or current bid and/or increment, accepting a suggested bid on behalf of an on-site bidder. In some embodiments, the bidder application may be an active application, configured to display pertinent to the auction and to allow a user (e.g. the online bidder) to input information and requests into the auction system 102, such as requests for accepting a suggested bid or for proposing a bid. In some embodiments, the viewer application may be a passive application, configured to display information pertinent to the auction on the user interface 124 to inform the viewer of the progress of the auction. The auctioneer application, assistant application, bidder application and/or viewer application may all be associated with different permission levels dictating the accessibility to the auction system 102 and range of information accessible to the user of the computing device running the special purpose application 306.

[65] For simplicity of illustration, the auction server 104 is generally described as serving code or one or more applets to the computing devices 106 to perform some of the described user interface functions. However, it should be understood that this includes the auction server 104 transmitting code and/or data to (and receiving code and/or data from) the special purpose application 306 executing on the computing device 106 to enable that special purpose application 306 to provide the necessary or appropriate displays and interactive features (e.g. display of information fields, user selectable options, conference panels etc.) described herein. Other user software applications may execute on the computing device(s) 106 using the operating system 302.

[66] Referring now to Figure 4, there is illustrated a block diagram of program 130 of the content file server 110. Program memory 130 comprises program code including an operating system 400, and a database auction application 402. The database auction application 402 comprises program code, such as executable code modules, which includes a database bid history module 404, a database increment module 406 and a database streaming module 408. The executable code modules of the database auction application 402, when aggregated and executed by the processor 128, perform programmed functions as described herein and cause the file content server 110 to provide content to the auction server 104 and/or the computing device(s) 106 on demand to facilitate the conducting and management of an auction, catering to both on-site physical bidders and online bidders as will be discussed in more detail with reference to Figures 5 to 14. [67] The database bid history module 404, when executed by the processor 128, is configured to receive an accepted suggested bid and/or an accepted proposed bid from the bidding module 208 and store it as the most recent or current bid for the auction and to broadcast the most recent or current bid for the auction to at least some of the participants of the auction.

[68] The database increment module 406, when executed by the processor 128, is configured to receive a set or determined increment value from the increment module 208 and to store it as the most recent or current increment value for the auction and to broadcast the most recent or current increment value for the auction to at least some of the participants of the auction.

[69] The database streaming module 408, when executed by the processor 128, is configured to receive session initiation requests from the streaming module 212, to establish the session, to receive upstream audio and/or video content from computing device(s) 106, to receive requests to subscribe to a session from computing device(s) 106 and to stream audio and/or video downstream to subscribed computing device(s) 106. In this way, the content file server 110 may function as a web-socket server, as discussed below with reference to Figure 6.

[70] Referring now to Figure 5 and the message flow diagrams of Figures 6 to 12, the auction system and method for facilitating the conducting of an auction that caters to both on- site physical bidders and online bidders will be described.

[71] Figure 6 is a message flow diagram of a method 600 of initiating an auction according to some embodiment, the method implemented by the auction system 102. For example, the initiation of the auction involves establishing a session to allow audio and/or video associated with the auctioneer conducting the auction to be streamed to computing devices 106 associated with parties registered or subscribed to partake or witness the auction. For example, the auctioneer may be equipped with a microphone headset and/or a video camera to allow the audio and/or video content to be streamed from the auctioneer or the auctioneer' s assistant' s computing device 106 to the content file server 110.

[72] In response to an input via user interface 124 of the computing device 106, the auctioneer or assistant application 306, when executed by the processor 120 of the mobile computing device 106, is configured to transmit a request to initiate a session to the auction server 104, at 602.

[73] In response to receiving the request to initiate a session from the auctioneer or assistant application 306, the streaming module 212 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to transmit an instruction to create a session to the database streaming module 408 or an audio/video archive storage of the content file server 110, at 604. The streaming module 212 of the auction application 202, when executed by the processor 112 of the auction server 104, is also configured to transmit an indication that the session was started successfully to the auctioneer or assistant application 306, at 606.

[74] In response to receiving an indication that the session was started successfully, the auctioneer or assistant application 306, when executed by the processor 120 of the mobile computing device 106, is configured to stream auction audio and/or video from the auctioneer or assistant's computing device 106 upstream to the database streaming module 408 of the content file server 110, at 608.

[75] The streaming module 212 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to notify all bidders or viewers that registered for the auction once the session has been established, at 610. In some embodiments, the auction will be advertised in advance and interested parties may register as viewers and/or bidders. For example, a party that registers as a viewer for the first time will be provided with an option of downloading a special purpose application 306 or viewer' s application to allow the necessary or appropriate displays and interactive features (e.g. display of information fields, user selectable options, conference panels etc.) to be provided on the mobile computing device 106 to allow the viewer to participate in the auction as a viewer. Similarly, a party that registers as a bidder for the first time will be provided with an option of downloading a special purpose application 306 or bidder's application to allow the necessary or appropriate displays and interactive features (e.g. display of information fields, user selectable options, conference panels etc.) to be provided on the computing device 106 to allow the viewer to participate in the auction as a bidder.

[76] In response to receiving the notification from the auction server 104, the special purpose application 306 (such as the bidder application or viewer application) and/or browser application 304 of the computing device 106, when executed by the processor 120, is configured to issue a subscription request to subscribe to or participate in the session to the database streaming module 408 of the content file server 110, at 612. In response to receiving the subscription request from the computing device 106, the database streaming module of the content file server 110 is configured to stream the auction audio and/or video received from the auctioneer's computing device 106 to the subscribed computing devices 106, at 614.

[77] In some embodiments, the auction system 102 may comprise a default bid value which is set as the current bid value at the initiation of an auction. In some embodiments, the current bid value for an auction may be set by an auctioneer and/or auctioneer's assistant or any authorised party. For example, the current bid value may be received by the bidding module 108 of the auction server 104 from an auctioneer/assistant application 306 deployed on a mobile computing device 106 of the auction system 102 and the bidding module 108 may store the received value as the current bid value in data memory 116 and/or transmit the value to the database bid history module 404 to be recorded as the current bid value in data memory 132 of the content file server 110. The content file server 110 may be configured to broadcast the current bid value to the bidders at bidders' computing devices 106 registered for the auction, and in some embodiments, all viewers at viewers' computing devices 106 registered for the auction. The bid history database of content file server 110 may also broadcast the current bid value to the assistant's mobile computing device 106 and/or the auctioneer's mobile computing device 106.

[78] In some embodiments, a bid suggested by an auctioneer when conducting the auction, i.e., an auctioneer suggested bid, may be input to the auction system 102. For example, the auctioneer suggested bid may be received by the bidding module 108 from an

auctioneer/ assistant application 306 and the bidding module 108 may store the received value as the current suggested bid value in data memory 116 and/or transmit the value to the database bid history module 404 to be recorded as the current suggested bid value in data memory 132 of the content file server 110. In some embodiments, the content file server 110 may be configured to broadcast the current suggested bid value to the at least some of the computing devices 106 registered for the auction, for example, for display on the user interface 124.

[79] In some embodiments, the auction system 102 may comprise a default increment value which is set as the current increment value at the initiation of an auction. In some embodiments, the current increment value for an auction may be set by an auctioneer and/or auctioneer' s assistant or any authorised party in a manner similar to that of changing the increment value as described below with reference to Figure 7.

[80] Figure 7 is a message flow diagram of a method 700 of processing a request to set an increment value for the auction, according to some embodiment, the method implemented by the auction system 102. In some embodiments, the increment value for an auction may be set by the auctioneer or assistant using computing device 106. For example, the auctioneer or assistant may decide to increase or to decrease the increment value for the auction.

[81] In response to the auctioneer's or assistant's input via user interface 124 of the mobile computing device 106, the auctioneer or assistant application 306 and/or browser application 304, when executed by the processor 120 of the mobile computing device 106, is configured to transmit a request to set an increment value for the auction to the auction server 104, 702. The request may comprise an indication of an increment value, for example, AU$5,000.

[82] In response to receiving the request from the auctioneer or assistant' s computing device 106, the data handling module 206, when executed by the processor 112 of the auction server 104, determines the type of request and in some embodiments, the source of the request, to determine how to process the request, at 704. In response to determining that the request is a request to set an increment value for the auction, and in some embodiments, that the request was transmitted by an authorised party, i.e., the auctioneer and/or assistant application 306, the data handling module 206 transmits the request to the increment module 210, at 706.

[83] In response to receiving the request to set the increment value from the data handling module 206, the increment module 208 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to transmit the increment value to the database increment module 406 of the content file server 110, at 708. In some embodiments, the increment module 210 may store the changed increment value as the current increment value in data memory 116.

[84] In response to receiving the increment value from the increment module 208, the database increment module 406 of content file server 110 is configured to store the increment value as the current increment value, for example in data memory 134 of the content file server 110, at 710 and to broadcast the current increment value to the computing devices 106 registered for the auction, for example, those associated with the bidders, viewers, the auctioneer and/or the assistant, at 712. The increment database of content file server 110 may also be configured to broadcast the current increment value to the mobile computing device 106 from which the request was received, at 714.

[85] Figure 8 is a message flow diagram of a method 800 of processing a request to accept an auctioneer suggested bid received from an auctioneer/assistant application 306 or a bidder application 306 deployed on a mobile computing device 106 of the auction system 102, according to some embodiments, the method implemented by the auction system 102. For example, the request to accept an auctioneer suggested bid may be transmitted to the auction server 104 on behalf of a bidder physically present at the auction who has placed a physical bid during the auction or on behalf of an online bidder.

[86] In some embodiments, when a physical bid is made at the auction site, the auctioneer or auctioneer's assistant will input the bid into the auction system 102. In response to the auctioneer's or assistant's input via user interface 124 of the auctioneer or assistant's mobile computing device 106, the auctioneer or assistant application 306 and/or browser application 304, when executed by the processor 120 of the mobile computing device 106, is configured to transmit a request to accept the suggested bid, for example, AU$510,000, to the data handling module 206 of the auction server 104, at 802.

[87] In some embodiments, in response to receiving the request to accept the suggested bid from the assistant or auctioneer application, the data handling module 206 determines how the request should be processed, at 804. For example, the data handling module 206, when executed by the processor 112 of the auction server 104, determines the type of request received and in some embodiments, the source of the request received, to determine how to process the request. In response to determining that the request is a request to accept the suggested bid from an authorised party, for example, the auctioneer and/or assistant application 306, or an authorised bidder's bidder application 306, the data handling module 206 transmits the request to the bidding module 208, at 806. In some embodiments, the data handling module 206 may be configured to associate the received request with a particular computing device 106 from which it was received and/or a user associated with the computing device 106 from which it was received so that the request to accept the suggested bid is associated with a particular bidder. [88] In some embodiments, in response to receiving the request to accept the suggested bid from the data handling module 206, the bidding module 208 approves the request to accept the suggested bid, at 808. For example, the suggested bid, having been suggested by the auctioneer conducting the auction is considered to have been pre-approved and accordingly, a request by a bidder to accept the auctioneer suggested bid (i.e., place a bid for the auctioneer suggested bid value) is deemed to be acceptable.

[89] In some embodiments, the bidding module 208, when executed by the processor 112 of the auction server 104, may be configured to transmit a notification to the auctioneer and/or assistant's mobile computing device 106 and/or bidder's mobile computing device 106 indicating whether or not the request has been received and approved, at 810. For example, if the bidding module 208 determines that the suggested bid is acceptable, the notification will indicate that the request has been approved. If the bidding module 208 determines that the suggested bid is not acceptable, the notification will indicate that the request has been rejected.

[90] If the bidding module 208 determines that the suggested bid is acceptable, the bidding module 208, when executed by the processor 112 of the auction server 104, transmits the accepted suggested bid to the database bid history module 404 of the content file server 110, at 812. In some embodiments, the bidding module 208 may store the accepted suggested bid as the current bid in data memory 116. For example, the current bid will now be recorded as $510,000.

[91] In response to receiving the accepted suggested bid, the database bid history module 406 of content file server 110 is configured to store the accepted suggested bid as the current bid, for example, in data memory 132, at 814, and to broadcast the current bid to the computing devices 106 registered for the auction, for example, those associated with the bidders, viewers, the auctioneer and/or the assistant, at 816. In some embodiments, the database bid history module 404 of content file server 110 may be configured to broadcast the current bid to the mobile computing device 106 from which the request to accept the suggested bid was received, at 818.

[92] In some embodiments, the bidding module 208 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to pass the accepted suggested bid to the increment module 210 of the auction application 202, at 820, to allow the increment module 210 to determine whether the current increment value should be updated as a result of the accepted suggested bid, at 822. For example, and the increment module 210, when executed by the processor 112 of the auction server 104, is configured to determine the difference between the new current bid (i.e., the accepted suggested bid) and the previous current bid and to compare the difference with the current increment value. If the difference is equal to or greater than the current increment value, the increment module 210 may determine that the current increment value does not need to be updated. If the difference is greater than the current increment value, the increment module 210 may determine that the current increment value should be increased to the value of difference. If the difference is less than the current increment value, the increment module 210 may determine that the current increment value should be decreased to the value of difference. In other embodiments, the acceptance of a suggested bid does not cause any change in the current increment value.

[93] For example, if the previous current bid was $500,000, and the current increment value was $10,000, the difference between the previous current bid and the accepted suggested bid (or new current bid) is equal to the current increment value, and the increment module 210 may determine that the current increment value does not need to be updated. If for example, the previous current bid was $500,000, and the current increment value is $20,000, the difference between the previous current bid and the accepted suggested bid (or new current bid) is greater than the current increment value, and the increment module 210 may determine that the current increment value does need to be updated to reflect the current increment value as $20,000. If, for example, the previous current bid is $500,000, and the current increment value is $5,000, the difference between the previous current bid and the accepted suggested bid (or new current bid) is less than the current increment value, and the increment module 210 may determine that the current increment value does not need to be updated or may determine that the current increment value does need to be updated to reflect the current increment value as $10,000.

[94] If the increment module 210 determines that the current increment value should be changed, the increment module 210, when executed by the processor 112 of the auction server 104, is configured to transmit the determined current increment value (i.e., the difference between the accepted suggested bid and the previous current bid) to the database increment module 406 of the content file server 110, at 824. In some embodiments, the increment module 210 stores the difference as the current increment value, for example, in data memory 116. [95] In response to receiving the determined increment value, the database increment module 406 of the content file server 110 is configured to store the determined increment value as the current increment value, for example, in data memory 132, at 826, and to broadcast the current increment value to the computing devices 106 registered for the auction, for example, those associated with the bidders, viewers, the auctioneer and/or the assistant, at 828. In some embodiments, the database increment module 406 of the content file server 110 may be configured to broadcast the current increment value to the mobile computing device 106 from which the request to accept the suggested bid was received, at 830.

[96] Figure 9 is a data flow diagram of a method 900 of processing a bidder proposed bid received from a bidder application deployed on a mobile computing device of the auction system according to some embodiments, the method implemented by the auction system of Figure 1.

[97] In some instances an online bidder may suggest a bid that is less than or greater than the current proposed bid. For example, if the most recent or current bid is $500,000 and the minimum increment value is $10,000, when a bidder proposes a bid at $505,000, or at $515,000 the bid may be accepted subject to auctioneer approval.

[98] As shown in Figure 9, in response to the bidder' s input via user interface 124 of the bidder's mobile computing device 106, the bidder application 306 and/or browser application 304, when executed by the processor 120 of the mobile computing device 106, is configured to transmit a bidder request for a proposed bid to the data handling module 206 of the auctions server 102, at 902.

[99] In some embodiments, in response to receiving the request to accept the proposed bid from the bidder application, the data handling module 206 determines how the request should be processed, at 904. For example, the data handling module 206, when executed by the processor 112 of the auction server 104, determines the type of request received and in some embodiments, the source of the request received, to determine how to process the request. In response to determining that the request is a request to accept a proposed bid from an authorised party, for example, an authorised bidder's bidder application 306, the data handling module 206 passes the request to the increment module 210, at 906. In some embodiments, the data handling module 206 may be configured to associate the received request with a particular computing device 106 from which it was received and/or a user associated with the computing device 106 from which it was received so that the proposed bid is associated with a particular bidder.

[100] In response to receiving the bidder proposed bid from the data handling module 206, the increment module 210 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to determine whether the proposed bid should be accepted, at 908. For example, the increment module 210 may be configured to compare the proposed bid with the current bid to determine the difference between the proposed bid with the current bid and to compare the difference with the current increment value to determine whether the proposed bid complies with the current increment value. If the difference is equal to or greater than the current increment value, the increment module 210 may determine that the proposed bid complies with the current increment value and that the proposed bid is acceptable. If the increment module 210 determines that the difference is less than the current increment value, the increment module 210 may determine that the proposed bid does not comply with the current increment value.

[101] In some embodiments, if the increment module 210 determines that the suggested bid does not comply with the current increment value, the increment module 210 is configured to transmit an approval request comprising the bidder proposed bid to the auctioneer and/or assistant's computing device 106, at 910. In response to receiving the approval request from the auction server 104, the auctioneer application 306 and/or browser application 304, when executed by the processor 120 is configured to determine whether to approve the request and accept the bidder proposed bid, at 912. For example, in some embodiments, the auctioneer application 306 and/or browser application 304 is configured to display the bidder proposed bid on the user interface 124 of the auctioneer and/or assistant's computing device 106 and to receive a user input from the auctioneer and/or assistant via the user interface 124, for example, via a user-selectable option, to indicate whether or not the bidder proposed bid is deemed acceptable by the auctioneer. In some embodiments, if auctioneer/assistant application 306 and/or browser application 304, determines that the bidder's proposed bid is acceptable or unacceptable, the auctioneer/assistant application 306, when executed by the processor 120, transmits an approval or rejection notification to the auction server 104, at 914, and the increment module 210 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to transmit a notification that the bidder's proposed bid has been accepted or rejected to the bidder's mobile computing device 106, at 916. [102] In some embodiments, in response to receiving an approval notification from the auctioneer and/or assistant, the increment module 210 may be configured to record the determined difference between the proposed bid and the current bid as the current increment value, for example, in data memory 116.

[103] The increment module 210 is configured to transmit the new current increment value to the database increment module 406, at 918. In response to receiving the new current increment value, the database increment module 404, when executed by the processor 128, stores the new current increment value as the current increment value, for example, in data memory 134, at 920, and broadcasts the new current increment value to the computing devices 106 registered for the auction, for example, those associated with the bidders, viewers, at 922, to the assistant and/or auctioneer's mobile computing device 106, at 924, and the mobile computing device 106 from which the request to accept the proposed bid was received, at 926.

[104] If the bidder's proposed bid is accepted, the increment module 210 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to notify the bidding module 208 of the accepted proposed bid, at 928. The bidding module 208, when executed by the processor 112, is configured to transmit the accepted proposed bid to the database bid history module 406 to cause the database bid history module 406, at 930.

[105] In response to receiving the accepted proposed bid, the database bid history module 406, when executed by the processor 128, is configured to store the accepted proposed bid as the current bid, for example, in data memory 134, at 932, and to transmit or broadcast the current bid to the computing devices 106 registered for the auction, for example, those associated with the bidders, viewers, at 934, to the assistant and/or auctioneer's mobile computing device 106, at 936, and the mobile computing device 106 from which the request to accept the proposed bid was received, at 938.

[106] Referring now to Figure 10, there is illustrated a process flow diagram of a computer- implemented method for facilitating the conducting of an auction catering to both on-site physical bidders and online bidders, according to some embodiments, the method implemented by the auction server 104 of the auction system 102 of Figure 1.

[107] The data handling module 206 receives a request to initiate an auction from a computing device 106, at 1002. In some embodiments, before initiating the auction session, the data handling module 206 may determine whether the request is a valid request, for example, by identifying a source of the request, as may be indicated by an source identifier in a data message or packet comprising the request and determining whether the source identifier corresponds with a list of authorised source identified, as may be stored in data memory 116.

[108] The data handling module 206 initiates the auction, at 1004. In some embodiments, the data handling module 206 passes the request to initiate the auction session to the streaming module 210 of the auction application 202. As described above with reference to Figure 6, in response to receiving the request to initiate the auction session from the data handling module 206, the streaming module 212 of the auction application 202, when executed by the processor 112 of the auction server 104, is configured to transmit an instruction to create a session to the database streaming module 408 or an audio/video archive storage of the content file server 110, and to notify all bidders or viewers that registered for the auction once the auction session has been established. In some embodiment, the streaming module 210 notifies the data handling module 206 that the auction session has been established.

[109] Once the auction session has been established, the data handling module 206 awaits receipt of requests pertinent to the auction, at 1006.

[110] When a request is received, the data handling module 206 determines the type of the request, at 1008. For example, the data handling module 206 may be configured to determine the request type by identifying a request type identifier provided in a data message or packet comprising the request and comparing the request type identifier a list of request type identifiers, as may be stored in data memory 116, to determine how to process the request.

[I l l] If the data handling module 206 determines that the request type is a request is a request to terminate the auction, at 1010, the data handling module 206 terminates the auction, at 1012, and may for example, notify all registered parties.

[112] If the data handling module 206 determines that the request type is a request to set/change the current bid and/ the suggested bid, at 1014, the data handling module 206 passes the request to the bidding module 208 for processing, at 1016. For example, and as previously described, in response to receiving a request to set/change the current bid, the bidding module 108 may be configured to store the received value as the current bid in data memory 116 and/or to transmit the received value to the database bid history module 404 to be recorded as the current bid in data memory 132 of the content file server 110. Similarly, in response to receiving a request to set/change the suggested bid, the bidding module 108 may be configured to store the received value as the current suggested bid in data memory 116 and/or to transmit the received value to the database bid history module 404 to be recorded as the current suggested bid in data memory 132 of the content file server 110. The content file server 110 may be configured to transmit or broadcast the updated current bid or current suggested bid to registered parties.

[113] If the data handling module 206 determines that the request type is a request to set/change the current increment value, at 1018, the data handling module 206 passes the request to the increment module 210 for processing, at 1020. For example, and as previously described with reference to Figure 7, in response to receiving a request to set/change an increment value for the auction, the increment module 208 may be configured to store the received value as the current increment value in data memory 116 and/or to transmit the received value to the database increment module 406 to be recorded as the current increment value in data memory 132 of the content file server 110. The content file server 110 may be configured to transmit or broadcast the updated current increment value to registered parties.

[114] If the data handling module 206 determines that the request type is a request to accept the current suggested bid, at 1022, the data handling module 206 passes the request to the bidding module 208 for processing, at 1024. For example, and as previously described with reference to Figure 8, in response to receiving a request to accept the current suggested bid, the bidding module 208 may be configured to approve the request, notify the auctioneer and/or assistant's mobile computing device 106 and/or bidder's mobile computing device 106 that the request has been received and approved, store the accepted suggested bid as the current bid in data memory 116, and/or transmit the accepted suggested bid to the database bid history module 404 of the content file server 110 to be stored as the current bid in data memory 134. The content file server 110 may be configured to transmit or broadcast the updated current bid to registered parties. The bidding module 208 may also be configured to pass the accepted suggested bid to the increment module 210 (or to notify the increment module 210 that the current bid was updated as a result of the suggested bid being accepted). The increment module 210 may be configured to determine whether the current increment value should be updated as a result of the accepted suggested bid, and if so, to update the current increment value to be the difference between the previous current bid and the accepted suggested bid (the current bid), and to transmit the determined current increment value (i.e., the difference between the accepted suggested bid and the previous current bid) to the database increment module 406 of the content file server 110 for storing as the current increment value in data memory 134. The content file server 110 may be configured to transmit or broadcast the updated current increment value to registered parties.

[115] If the data handling module 206 determines that the request type is a request to accept a proposed bid, at 1026 , the data handling module 206 passes the request to the increment module 210 for processing, at 1028. For example, and as previously described with reference to Figure 9, in response to receiving a request to accept a bidder proposed bid, the increment module 210 may be configured to determine whether the proposed bid should be accepted, for example, by determining whether the proposed bid complies with the current increment level and/or seeking approval of the proposed bid from the auctioneer/assistant. In some embodiments, if the proposed bid is approved, the increment module 210 may be configured to determine a difference between the accepted proposed bid and the current bid and to store the difference as the current increment value, for example, in data memory 116. The increment module 210 may also be configured to transmit the new current increment value to the database increment module 406 for storing the new value as the current increment value, for example, in data memory 134. The content file server 110 may be configured to transmit or broadcast the updated current increment value to registered parties. The increment module 210 may also be configured to notify the bidding module 208 of the accepted proposed bid, and the bidding module 208 may be configured to transmit the accepted proposed bid to the database bid history module 406 to cause the database bid history module 406 to store the accepted proposed bid as the current bid. The bidding module 208 or the increment module 210 may be configured to store the accepted proposed bid as the current bid, for example, in data memory 116. The content file server 110 may be configured to transmit or broadcast the updated current bid to registered parties.

[116] If the data handling module 206 is unable to determine the request type, the data handling module 206 identifies the request as an unrecognised or unauthorised request, at 1030. In some embodiments, the data handling module 206 may transmit a notification to the assistant and/or auctioneer application to inform the assistant and/or auctioneer that an unidentified and unprocessed request was received. If the data handling module 206 identifies the request as an unrecognised or unauthorised request, the method reverts to 1006, and the data handling module 206 awaits recept of further requests.

[117] Referring to Figure 11, there is shown an example screen shot of a display 1100 on the user interface 124 of an auctioneer and/or assistant's computing device 106. The display 1100 shows a graph depicting the progress of an auction. The auctioneer/assistant application 306 and/or browser application 304 of the auctioneer's computing device is configured to update the display 1100 as information relating to the auction is received from the auction server 104 and/or content file server 110. As shown, the graph is a plot of the value of the bids made against time, and each bid made is associated with an identifier. For example, the identifier may indicate whether the bid was made by the vendor, for example, by the assistant or by a bidder, and in some embodiments, the identifier may identify the actual bidder's name. In some embodiments, historical data, advertised data and/or predicted data may used as benchmarks.

[118] Referring to Figure 12, there is shown an example screen shot of a display 1200 on the user interface 124 of an auctioneer and/or assistant's computing device 106. The display 1200 shows information pertaining to an auction in progress and in particular, the value of the current bid and the current increment value, a graphical representation of the values of the current bids over the duration of the auction session, and an identifier, such as an icon, representing one or more of the bidders registered for the auction. As shown, each identifier may show a value of the most recent bid made by the bidder associated with the identifier.

[119] Figure 13 A, is an example screen shot of a display 1300A of information pertaining to an auction in progress as displayed on a user interface 124 of an online bidder or viewer's computing device 106. As shown, the display 1300A shows information pertaining to an auction in progress such as an identification of the article or property under auction, messages transmitted to online bidders which may correspond with an audio stream recording of the auctioneer conducting the auction, and a data feed of bids accepted as the auction progresses.

[120] Figure 13B is an example screen shot of a display 1300B showing an input screen to allow a bidder to engage with an auction in progress to propose a bid as displayed on a user interface 124 of an online bidder's computing device 106. The display 1300B shows information pertaining to an auction in progress and in particular, a data feed of bids which were accepted by the auction system 102, and whether those bids were made by bidders physically present at the auction site or online bidders, the value of the current bid and the current increment value. The display further shows a user selectable option to allow a user to make a bid at the suggested bid value.

[121] Figure 13C is an example screen shot of a display 1300C showing an input screen to allow a an auctioneer and/or assistant to place a bid on behalf of an on-site bidder as displayed on a user interface 124 of an auctioneer and/or assistant computing device 106. As shown, the display 1300C identifies the current bid and a minimum increment value allowable, and provides a message tab, an increment tab and a custom tab to allow the user to interact with the auction server 104. The increment tab provides a number of user-selectable increment options and a place bid user selectable option to allow a user to place a bid at a value of the current bid plus the value of the selected increment option. The custom option may allow a user to manually input a value of a proposed bid and the message tab may allow a user to send a message to the assistant, auctioneer and/or other bidders or viewers of the auction.

[122] Referring now to Figure 14, there is shown a process flow diagram of a computer implemented method 1400 for engaging in an auction that allows or caters to both on-site physical bidding and online bidding. The method is implemented by the bidder application 306 deployed on a mobile computing device 106 of the auction system 102. In particular, the processor 120 of the computing device 106 is configured to execute the browser application 304 and the bidder application 306 to perform the method of Figure 14.

[123] The browser application 304 and/or the bidder application 306 is configured to provide the user with an option to select an auto-bidding function for an auction being hosted by the auction server 104, at 1402. For example, the browser application 304 may be configured to display a user-selectable option on the user interface 124. The user may also be required to input a budget price via the user interface 124, for example, by inputting a particular budget price, or selecting one of a number of pre-defined budget prices.

[124] In response to receiving a request to enable an auto-bidding function from the user via the user interface 124 of the computing device 106, at 1404, the bidder application 306 is configured to determine the budget price from the request and to store the budget price as maximum bid value, at 1406 for example, in data memory 122. [125] In response to receiving an indication of an auctioneer suggested bid at 1408, for example from the auction server 104, the bidder application 306 is configured to determine whether the auctioneer suggested bid is greater than the maximum bid value, at 1410. In response to determining that the auctioneer suggested bid is not greater than the maximum bid value, the bidder application 306 is configured to transmit a request to accept the auctioneer suggested bid to the auction server, at 1412 and the method returns to 1408.

[126] In response to determining that the auctioneer suggested bid is greater than the maximum bid value, the bidder application 306 is configured to issue an alert to the user via the user interface 124, at 1414. For example, the alert may comprise a request for an updated maximum bid value. In some embodiments, the user may increase the maximum bid value by inputting a budget price of a greater value than that of the maximum bid value stored. The bidder application 306 may be configured to determine whether an updated budget price is received, at 1416, and if so, the method may revert to 1406 where the new budget price may be stored as the maximum bid value. If an updated budget price is not received at 1416, the bidder application 306 may be configured to exit the auction, at 1418,

[127] The auto-bidding function allows a user to "set and forget", allowing the bidding application to bid in an auction hosted by the auction server 104 on behalf of the user.

[128] Figure 15A, is an example screen shot of a display 1500A of information pertaining to upcoming auctions as displayed on a user interface 124 of an online bidder or viewer' s computing device 106. As shown, the display 1500A shows a list of user selectable items, each displaying information pertaining to an upcoming auction such as an identification of the article or property under auction, including an address, a date and time for the auction and an image of the property. The display 1500A also provides a user selectable option or tab to view information pertaining to past auctions. For example, such information may be collected and stored prior to, during and/or after the auction takes place and includes, for example, an identification of the article or property under auction, including an address, a date and time for the auction, an image of the article or property, the reserve amount, the actual price at which it was sold, a number of bidders etc.

[129] Figure 15B is an example screen shot of a display 1500B of one of the user selected items of Figure 15 A. The display 1500B shows an expanded view of the information relating to the item of Figure 15A and includes additional information, including a listed price or price range. The display 1500B provides a user selectable option to allow the user to activate a share mode to share the item, for example, via a text message, email, and/or on a social media network. The display 1500B further provides a user selectable option to allow the user to activate a private mode, which disables the share mode. The display 1500B further provides a user selectable option to allow the user to view the bidders registered for the auction, and a user selectable option to allow the user to view a report associated with the auction. In some embodiments, the report is only available when the auction is finished and/or marked as sold. An example of the report is shown in Figure 17. As shown, the report may display the auction details, a graph depicting the progress of the auction and a record or table of the bids made during the auction.

[130] Figure 15C is an example screen shot of a display 1500C showing an input screen to allow an auctioneer and/or assistant to place a bid on behalf of an on-site bidder as displayed on a user interface 124 of an auctioneer and/or assistant computing device 106. As shown, the display 1500C identifies the current bid and a minimum increment value allowable, and provides a message tab, an amount tab and an increment tab to allow the user to interact with the auction server 104. As shown, the amount tab provides a number of user-selectable increment number options to allow a user to enter a specific bid. The amount tab also provides a user selectable increment option to allow a user to place a bid at a value of the current bid plus the value of the selected increment option. The message tab may allow a user to send a message to the assistant, auctioneer and/or other bidders or viewers of the auction.

[131] Figure 16 shows an example screen shot of display 1600 showing an input space 1602 to allow a user to input a suggested bid for display on a user interface of a bidder or viewer's computing device. The input space 1602 or drawing screen may be used by a user, such as a bidder or viewer to show others in their vicinity a suggested next bid. In some embodiments, the input space 1602 and suggested bid may be only displayed locally on the user interface of the bidder or viewer's computing device. It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the above-described embodiments, without departing from the broad general scope of the present disclosure. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

1. A computer implemented method for facilitating the conducting of an auction that caters to both on-site physical bidding and online bidding, the method implemented by an auction server in communication with a plurality of computing devices registered for the auction and a content file server across a communications network, the auction server comprising one or more processors and memory comprising an auction application, which when executed by the one or more processors, is configured to perform the method, the method comprising:

receiving a request from one of the plurality of computing device;

determining a request type of the request;

responsive to determining that the request is a request to accept a proposed bid and that the proposed bid is acceptable:

determining an updated current increment value based on a comparison of the proposed bid and a current bid for the auction;

storing the updated current increment value as the current increment value; storing the acceptable proposed bid as the current bid; and

transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices.

2. The method of claim 1, wherein determining that the request to accept the proposed bid is acceptable comprises determining a source of the request.

3. The method of claim 1, wherein determining that the request to accept the proposed bid is acceptable comprises:

determining a source of the request;

responsive to determining that the source of the request is an auctioneer application running on one of the plurality of computing devices, determining that the proposed bid is preapproved; and

responsive to determining that the source of the request is a bidding application running on one of the plurality of computing devices, transmitting a request for approval to the auctioneer application and receiving approval of the proposed bid from the auctioneer application.

4. The method of claim 1, wherein determining that the request to accept the proposed bid is acceptable comprises:

determining a source of the request;

responsive to determining that the source of the request is a bidding application running on one of the plurality of computing devices, determining that the proposed bid complies with the current increment level.

5. The method of any one of the preceding claims, wherein, responsive to determining that the request is a request to accept an auctioneer suggested bid,

storing the suggested bid as the current bid;

responsive to determining that the increment value should be updated based on a comparison of the auctioneer suggested bid and the current bid, determining an updated increment value and storing the updated increment value as the current increment value; transmitting the updated current increment value and current bid to the content file server for broadcasting to at least some of the computing devices.

6. The method of claim 5, wherein determining that the increment value should be updated comprises determining a difference between the auctioneer suggested bid and the current bid and responsive to the difference being less than a threshold value, determining that the updated increment value is substantially equal to the threshold value.

7. The method of claim 6, wherein the threshold value comprises the current increment value.

8. A computer implemented method for facilitating the conducting an auction that caters to both on-site physical bidding and online bidding, the method implemented by an auction server in communication with a plurality of computing devices registered for the auction and a content file server across a communications network, the auction server comprising one or more processors and memory comprising an auction application, which when executed by the one or more processors, is configured to perform the method, the method comprising:

receiving a request from one of the plurality of computing device; determining a request type of the request;

responsive to determining that the request is a request to accept an auctioneer suggested bid,

storing the suggested bid as the current bid;

9. The method of claim 8, wherein determining that the request to accept the proposed bid is acceptable comprises:

storing the updated current increment value as the current increment value;

storing the acceptable proposed bid as the current bid; and

10. The method of any one of the preceding claims, wherein:

responsive to determining that the request is a request to set/change the current bid, the suggested bid and/or the increment level, determining a source of the request; and

responsive to determining that the source of the request is an auctioneer application running on one of the plurality of computing devices, determining an updated current bid, suggested bid and/or increment value from the request, storing the updated current bid, suggested bid and/or increment value as the current bid, current suggested bid and/or current increment value, respectively, and transmitting the updated current bid, current suggested bid and/or current increment value to the content file server for broadcasting to at least some of the computing devices.

11. The method of any one of the preceding claims, wherein responsive to determining that the request is a request to initiate an auction, transmitting a create session request to the content file server and responsive to receiving acknowledgement of the creation of the session from the content file server, transmitting a notification to at least some computing devices to indicate that the auction session has been established.

12. A computer implemented method for engaging in an auction that caters to both on- site physical bidding and online bidding, the method implemented by a computing device in communication with an auction sever across a communications network, the computing device comprising one or more processors and memory comprising a bidding application, which when executed by the one or more processors, is configured to perform the method, the method comprising:

receiving a request to enable an auto-bidding function from a user via a user interface of the computing device, the request comprising a budget price;

storing the budget price as a maximum bid value;

responsive to receiving an indication of an auctioneer suggested bid, determining whether the auctioneer suggested bid is greater than the maximum bid value;

responsive to the auctioneer suggested bid not being greater than the budget price, transmitting a request to accept the auctioneer suggested bid to the auction server; and

responsive to the auctioneer suggested bid being greater than the budget price, issuing an alert to the user via the user interface.

13. The method of claim 12, wherein the alert comprises a request for an updated maximum bid value.

14. An auction system for facilitating the conducting of an auction that caters to both on- site physical bidding and online bidding in the same auction, the auction system comprising: an auction server in communication with a plurality of computing devices across a communications network, the auction server comprising one or more processors and memory comprising an auction application, which when executed by the one or more processors, is configured to perform the method of any one of claims 1 to 10,

15. The auction system of claim 14, further comprising a content file server in communication with the auction server across the communications network, the content file server comprising one or more processors and memory comprising a database auction application, which, when executed by the one or more processors, is configured to: transmit data including at least one of current bid, current suggested bid and/or current increment values to at least some of the computing devices registered for the auction.

16. The auction system of claim 15, wherein the content file server is further configured to:

receive streamed auction audio and/or video content from the auctioneer application running on one of the plurality of computing devices; and

responsive to receiving a subscription request to subscribe to the auction session from one or more of the others of the plurality of computing devices, streaming the auction audio and/or video content to the subscribed computing devices.

17. The auction system of any one of claims 14 to 16, further comprising at least one computing device in communication with the auction server across the communications network, the computing device comprising one or more processors and memory comprising a bidding application, which, when executed by the one or more processors, is configured to perform the method of claim 12 or claim 13.

18. A computer program product comprising a computer readable medium encoded with computer executable instructions, which when executed in a computer system, is effective to cause the computer system to carry out the method of any one of claims 1 to 13.

19. The computer readable medium of claim 18, wherein the computer readable medium is a non-transitory computer readable medium.