AU2016262133A1 - Method and system for remote data acquisition - Google Patents

Method and system for remote data acquisition Download PDF

Info

Publication number
AU2016262133A1
AU2016262133A1 AU2016262133A AU2016262133A AU2016262133A1 AU 2016262133 A1 AU2016262133 A1 AU 2016262133A1 AU 2016262133 A AU2016262133 A AU 2016262133A AU 2016262133 A AU2016262133 A AU 2016262133A AU 2016262133 A1 AU2016262133 A1 AU 2016262133A1
Authority
AU
Australia
Prior art keywords
content
data
initiating
server
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
AU2016262133A
Other versions
AU2016262133B2 (en
Inventor
Markie BRYANT
Jayson HORNIBROOK
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bomb'd Pty Ltd
Original Assignee
Bombd Pty Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AU2015901741A external-priority patent/AU2015901741A0/en
Application filed by Bombd Pty Ltd filed Critical Bombd Pty Ltd
Publication of AU2016262133A1 publication Critical patent/AU2016262133A1/en
Application granted granted Critical
Publication of AU2016262133B2 publication Critical patent/AU2016262133B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H04N21/2543—Billing, e.g. for subscription services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
    • H04N21/2743—Video hosting of uploaded data from client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

A method and system for configuring a content device to generate content data comprises receiving, at the content device, first configuration data from an initiating device via a network. The content device and initiating device may each be a mobile communications device. The first configuration data includes the first content request. The first configuration data can additionally include one or more parameters. The content device is configured to generate content data of a type associated with the first content request, generating the content data in accordance with the parameter(s), and sending the content data to the initiating device via the network. As an example, the content data may be visual data such as a photograph or a video.

Description

FIELD OF THE INVENTION [0001] The invention generally relates to the configuration of remote devices and the transfer of data between devices, in particular, where those devices include portable computing devices such as smartphones.
BACKGROUND TO THE INVENTION [0002] Since the development of mobile phones including cameras, and the ability to instantly communicate photos and videos (and other media) recorded by the mobile phone to other mobile phones, the concept of “social media” has developed remarkably. In particular, with the advent of so-called “smartphones” and similar devices, that is, mobile phones and other portable devices having significant computing resources and access to the Internet, people are now able to communicate through multimedia in near real time with little or no effort required by the users of such devices.
[0003] There are a number of services, typically in the form of applications or “apps”, which aim to facilitate communication of multimedia between users.
These existing services rely upon a “push out” model, where a first user instigates the communication of multimedia data to a second user by sending the second user multimedia data. There is no requirement for the second user to engage with the first user, even if the second user views the multimedia data.
[0004] These existing services have found utility not only in interpersonal communication, but as a technique for brand owners to engage with their customers and renowned entities to engage with their supporters. However, the engagement is difficult to measure and can be easy to ignore; that is, the total engagement with the customer or fan base is only a fraction of the total base.
WO 2016/179665
PCT/AU2016/050365
SUMMARY OF THE INVENTION [0005] According to a first aspect of the present invention, there is provided a method for configuring a content device to generate content data, comprising the steps of: receiving, at the content device, first configuration data from an initiating device via a network, wherein the first configuration data comprises at least a first content request and at least one parameter; configuring the content device to generate content data of a type associated with the first content request; generating the content data in accordance with the at least one parameter; and sending, via the network, the content data to the initiating device.
[0006] Advantageously, the method allows for a user of an initiating device to cause another device (the content device) to generate content data, based on parameters specified by the user of the initiating device, and then to subsequently communicate this content data to the initiating device, thereby allowing the user of the initiating device to view the content data in an appropriate format.
[0007] According to a second aspect of the present invention, there is provided a method for configuring a content device to generate content data, comprising the steps of: receiving, at the content device, first configuration data from a plurality of initiating devices via a network, wherein the first configuration data of each initiating device comprises at least a first content request; configuring the content device to generate content data of a type associated with the first content request; determining at least a first parameter, and generating the content data in accordance with the at least the first parameter; and sending, via the network, the content data to each of the initiating devices.
[0008] Preferably, the content data is of a type determined by the first content request.
[0009] Optionally, the step of generating the content data includes the step of obtaining from a camera of the content device visual data, wherein the visual data
WO 2016/179665
PCT/AU2016/050365 corresponds, at least in part, to the content data, preferably wherein the visual data is one of a photograph or a video. Optionally, the at least one parameter includes a time delay parameter, and wherein the visual data is acquired from the camera after a delay determined by the time delay parameter from an activation action received at the content device. Where the visual data is a video, the at least one parameter may include a recording length parameter, and the visual data is then acquired from the camera over a period of time determined by the recording length parameter.
[0010] Advantageously, this embodiment incentivises a user of the content device to take an immediate (or at least prompt) photograph or video representing their current activity.
[0011] In an embodiment, the method further comprises the steps of: the, or each, initiating device sending via the network first configuration data to the content device; the, or each, initiating device receiving, via the network, the content data; and at least one initiating device displaying the content data on a display of the initiating device. The initiating device may send first configuration data to the content device in response to a user input, the user input at least in part specifying at least one parameter. Preferably, the content data is displayed for a predetermined time and/or the content data is displayable for a predetermined time.
[0012] Optionally, the method includes the step of providing a server in communication, via the network, with the content device configured for maintaining a contact database, wherein the contact database comprises a plurality of identifiers including a first identifier associated with the content device, and wherein the, or each, first configuration data is received by the content device via the server and/or the content data is sent to the, or each, initiating device via the server.
WO 2016/179665
PCT/AU2016/050365 [0013] Preferably, according to this option, the method further comprises the steps of: the server receiving first configuration data from the, or each, initiating device via the network, the first configuration data further comprising a destination ID parameter; the server retrieving an identifier from the database corresponding to the destination ID parameter; the server determining a content device network location of the content device based on the retrieved identifier; and the server sending the first configuration data to the content device based at least in part on the content device network location.
[0014] In addition, the server may be further configured to maintain a record database, and the method then further comprises the steps of: the server recording a request event into the record database in response to the server sending first configuration data to the content device; and/or the server recording a response event into the record database in response to the server receiving the content data from the content device. In an implementation, the server is configured to record the content data received from the content device into the record database.
[0015] In an embodiment, the method further comprises the steps of: receiving, at one or more further content devices, the first configuration data from the initiating device via a network; configuring the, or each, further content device to generate content data of a type associated with, preferably determined by, the first content request; for the, or each, further content device, generating the content data in accordance with the at least one parameter; sending, via the network, the content data of the, or each, further content device to the initiating device.
[0016] The method may further comprise the steps of: providing at least two communication devices; selectively configuring one of the communication devices as an initiating device; and selectively configuring another one of the communication devices as the content device.
WO 2016/179665
PCT/AU2016/050365 [0017] Typically, the content device is a first mobile computing device, preferably a smartphone having wireless access to the network, and the, or each, initiating device is another mobile computing device, preferably a smartphone having wireless access to the network.
[0018] In another embodiment, the generation of the content data includes the step of selecting a pre-generated content item from a repository of content items.
[0019] Preferably, the method further comprises the step of facilitating payment to a user of the content device for the, or each, initiating device receiving content data.
[0020] According to a third aspect of the present invention, there is provided a server comprising a network interface and a first memory operatively associated with a processor, wherein the first memory is configured for storing a content database comprising a plurality of identifiers and wherein the server is configured for maintaining the content database, the server configured to: receive, at the network interface, first configuration data and a destination ID parameter from an initiating device, wherein the first configuration data comprises at least a first content request and at least one parameter; in response, retrieve an identifier from the contact database corresponding to the destination ID parameter; determine a content device network location associated with the retrieved identifier; send via the network interface the first configuration data to a content device based at least in part on the network location; receive, from the content device at the network interface, content data generated by the content device in response to the content device receiving the first configuration data, the content data being determined at least in part based on the at least one parameter; and send via the network interface the content data to the initiating device.
[0021] According to this aspect, the content data may be generated according to the first aspect.
WO 2016/179665
PCT/AU2016/050365 [0022] Optionally, the server is further configured to: maintain a record database; record a request event into the record database in response to the server sending first configuration data to the content device; and/or record a response event into the record database in response to the server receiving the content data from the content device.
[0023] According to a fourth aspect of the present invention, there is provided a communication system comprising an initiating device and a content device, the initiating device in network communication with the content device, wherein the content device is configured to undertake the following steps: receiving, at the content device, first configuration data from a initiating device via a network, wherein the first configuration data comprises at least a first content request and at least one parameter; configuring the content device to generate content data of a type associated with the first content request; generating the content data in accordance with the at least one parameter; and sending, via the network, the content data to the initiating device.
[0024] Preferably, the content data is of a type determined by the first content request.
[0025] The initiating device may be configured to undertake the following steps: sending via the network the configuration data to the content device; receiving, via the network, the content data; and displaying the content data on a display of the initiating device.
[0026] According to a fifth aspect of the present invention, there is provided a method for configuring a computing device, the method comprising the steps of: sending, preferably via a network, instructions configured to cause the computing device to implement the method of the first aspect.
[0027] According to a sixth aspect of the present invention, there is provided a method for acquiring content data from a content device, comprising the steps of:
WO 2016/179665
PCT/AU2016/050365 receiving an initiating request from each of a plurality of initiating devices via a network; determining that a threshold condition related to the received initiating request has been satisfied, and in response communicating first configuration data including a first content request to the content device; obtaining content data, the content data generated by the content device in accordance with the first configuration data; and communicating, via the network, the content data to at least one of the plurality of initiating devices.
[0028] Typically, the threshold condition corresponds to receiving initiating requests from a pre-determined minimum number of initiating devices, preferably wherein the pre-determined minimum number is selected by a user of the content device. The initiating requests may be received at a threshold module, the threshold module being configured for determining that the threshold condition has been satisfied. The threshold module preferably communicates the first configuration data to the content device. For example, the threshold module may generate the first configuration data.
[0029] Optionally, the method further comprises the steps of: receiving, at the content device, the first configuration data; configuring the content device to generate content data of a type associated with, preferably determined by, the first content request; and generating the content data in accordance with at least one parameter. Preferably, the at least one parameter is communicated to the content device as part of the first configuration data.
[0030] Preferably, the content data is communicated to each of the plurality of initiating devices. In an embodiment, the content device directly communicates the content data to the at least one initiating device. In an alternative embodiment, a distribution module obtains the content data from the content device, and wherein the distribution module communicates the content data to the at least one initiating device.
WO 2016/179665
PCT/AU2016/050365 [0031 ] Preferably, the method further comprises the step of facilitating payment to a user of the content device for the, or each, initiating device receiving content data.
[0032] According to a seventh aspect of the present invention, there is provided a server comprising a network interface and a first memory operatively associated with a processor, wherein the first memory is configured for storing a content database comprising a plurality of identifiers and wherein the server is configured for maintaining the content database, the server configured to: receive, at the network interface, an initiating request from each of a plurality of initiating devices; determine that a threshold condition has been satisfied, the threshold condition associated with a content device; and in response, communicate first configuration data comprising a first content request and one or more parameters to the content device.
[0033] Optionally, the server is further configured to: receive, from the content device, content data generated by the content device in accordance with the first configuration data; in response, communicate via the network the content data to at least one of the plurality of initiating devices.
[0034] The content data is preferably communicated to each of the plurality of initiating devices.
[0035] According to a eighth aspect of the present invention, there is provided a communication system comprising a plurality of initiating devices and a content device, the initiating devices and content device being in network communication with a threshold module, wherein the initiating devices are each configured to communicate to the threshold module an initiating request, wherein the threshold module is configured to determine, based on the received initiating communication data, that a pre-determined threshold condition has been met and in response communicate to the content device first configuration data comprising content request and one or more parameters, wherein the content device is
WO 2016/179665
PCT/AU2016/050365 configured to generate content data in response to receiving the first configuration data, the content data generated in accordance with the first configuration data, and wherein the content device is configured to communicate, optionally via a distribution module, the content data to at least one of the initiating devices.
[0036] Preferably, the content data is communicated to each of the plurality of initiating devices. The threshold module may be implemented within the content device. In this case, the threshold module may be implemented within a server in network communication with the content device and each of the plurality of initiating devices. The server is preferably the server of the sixth aspect.
BRIEF DESCRIPTION OF THE DRAWINGS [0037] Embodiments of the invention will now be described with reference to the accompanying drawings. It is to be appreciated that the embodiments are given by way of illustration only and the invention is not limited by this illustration. In the drawings:
[0038] Figure 1 shows an exemplary communication system for implementing embodiments of the invention;
[0039] Figure 2a shows a server maintaining a database comprising a plurality of identifiers according to an embodiment;
[0040] Figure 2a shows a server maintaining a database comprising a plurality of identifiers according to another embodiment;
[0041] Figure 2c shows identifiers associated with users;
[0042] Figure 3a shows the server implemented as a separate entity to a plurality of communication devices;
WO 2016/179665
PCT/AU2016/050365 [0043] Figure 3b shows communication devices each comprising a server;
[0044] Figure 4 shows a content device and an initiating device is network communication with one another, the content device comprising a camera;
[0045] Figure 5 shows a method for configuring a content device to acquire content data;
[0046] Figure 6 shows an initiating device sending configuration data to a plurality of content devices, and receiving content data from each content device;
[0047] Figure 7 shows the server maintaining a record database comprising records;
[0048] Figure 8 shows the server having a database comprising a plurality of content items;
[0049] Figure 9 shows a threshold module in network communication with a plurality of initiating devices and a content device; and [0050] Figure 10 shows a threshold module and a distribution module, each in network communication with a plurality of initiating devices and a content device.
DESCRIPTION OF PREFERRED EMBODIMENTS [0051] For the purpose of the disclosure herein, a general feature referred to in the figures is labelled with a number. Where it is necessary to distinguish specific instances of the general feature in a particular figure, the specific instances are labelled with the number of the general feature and a unique letter suffix. Reference can be made to the general feature by omitting the suffix and one or more specific instances by including the suffix.
WO 2016/179665
PCT/AU2016/050365 [0052] Referring first to Figure 1, there is shown an overview of one exemplary communication system 10. The communication system 10 includes a server 12 and one or more communication devices 14. Generally, the server 12 and communication devices 14 are in data communication with a network 16, which can include the Internet, proprietary mobile data networks, and/or one or more local intranets.
[0053] Figure 1 depicts the communication system 10 schematically; it is not intended to limit the technology or devices employed at the server 12 and the one or more communication devices 14. The one or more communication devices 14 in particular may be wired or wireless devices, and their connections to the network 16 may utilise various technologies and bandwidths. For example, applicable communication devices 14 include (without limitation): PC’s with wired (e.g. LAN, cable, ADSL, dial-up) or wireless (e.g. WLAN, cellular) connections; and wireless portable/handheld devices such as PDA’s or mobile/cellular telephones. The protocols and interfaces between the communication devices 14 and the server 12 may also vary according to available technologies, and include (again without limitation): wired TCP/IP (Internet) protocols; WiFi; Bluetooth; GPRS, WAP, 3G and/or 4G protocols (for handheld/cellular devices); and/or proprietary communications protocols. Typically, the one or more communication devices 14 are portable devices and employ wireless communication technologies, though it can be that the wireless communication technology is in combination with wired communication technologies.
[0054] The server 12 can be a single device or a plurality of interconnected devices, and includes at least one processor as well as at least one database, which would typically be stored on a secondary storage device of the server 12, such as one or more hard disk drives. Server 12 further includes at least one storage medium, typically being a suitable type of memory, such as random access memory, for containing program instructions and transient data related to the implementation of the invention as well as other necessary functions of the server 12. In particular, the memory contains a body of program instructions.
WO 2016/179665
PCT/AU2016/050365 [0055] Depending on the embodiment, the server 12 can provide multiple functions. It is understood that the functions described could in fact be implemented on separate servers 12 which are in data communication with one another. It is also understood that the functions could be implemented on a single server 12 configured to provide virtual environments for each function.
[0056] Similarly, the communication devices 14 include at least one processor and a secondary storage device (for example, a solid state storage device). The communication devices 14 also include suitable temporary storage, such as random access memory, for containing program instructions and transient data related to the implementation of the invention as well as other necessary functions of the communication device 14. In particular, the memory contains a body of program instructions.
[0057] The hardware shown in Figure 1 is merely one possible embodiment and any other suitable structure may be utilised. For the purpose of describing embodiments of the invention, unless stated otherwise, the one or more communication devices 14 are “smartphones”.
[0058] Referring to Figures 2a to 2c, the server 12 maintains a contact database 18 comprising one or more identifiers 19, each associated with a communication device 14. In an embodiment, as shown in Figure 2a, each identifier 19 is uniquely associated with a communication device 14. In another embodiment, as shown in Figure 2b, each identifier 19 is associated with one or more communication devices 14. Each identifier 19 can also be associated with a user 20. For example, a particular user 20a associated with a particular identifier 19a operates a particular communication device 14a also associated with the identifier 19a. The contact database 18 can optionally comprise further information associated with each identifier 19, for example, a username, user picture, and other metadata as required, etc.
WO 2016/179665
PCT/AU2016/050365 [0059] Each identifier 19 at least includes information configured for facilitating communication between different communication devices 14. Typically, this will be an IP address or some other unique network address for the, or each, communication device 14 associated with the identifier 19.
[0060] In an embodiment, as shown in Figure 3a, the server 12 is a separate entity to the communication devices 14, for example maintained by a server operator. The communication devices 14 communicate with the server 12 via the network 16 as shown in Figure 1. Typically, the server 12 will maintain a collection of identifiers 19, each associated with one or more communication devices 14, which is stored in the database of the server 12. This enables the server 12 to perform a lookup on the database in order to identify and retrieve a particular identifier associated with one or more particular communication devices 14 associated with a particular identifier 19. Each communication device 14 is typically enabled to send instructions to the server 12 in order to facilitate maintenance of the database. For example, if a network address of a communication device 14 changes, then the communication device 14 is configured to communicate an instruction to the server 12 to update the database with the new network address. In another example, if a user 20 configures a new communication device 14, it is configured to provide an instruction to the server 12 to add the communication device 14, and its associated network address, to the database and to associate the communication device 14 with the identifier 19 associated with the user 20. In yet another example, a user 20 dissociates a communication device 14 with the user 20, and the communication device 14 provides an instruction to the server to remove the association between itself and the identifier 19 associated with the user 20.
[0061] In another embodiment, as show in Figure 3b, there are effectively servers 12 maintained on each communication device 14. Each server 12 is configured for providing information that can be unique to a user 20 of the communication device 14. The server 12 is typically only accessible by the communication device 14 in which it is implemented. However, in a variation of
WO 2016/179665
PCT/AU2016/050365 the embodiment, copies of the server 12 are maintained on each communication device 14 associated with the same user 20. The copies can be maintained through regular, or on demand, network communication between the communication devices 14 associated with the user 20.
[0062] The embodiment of Figure 3a can be considered a ‘centralised system’, where a server 12 separate from the communication devices 14 maintains the database necessary for facilitating data communication between the different communication devices 14. In contrast, the embodiment of Figure 3b can be considered a ‘decentralised system’, where each communication device 14 is responsible for maintaining a database for facilitating communication between itself and other communication devices 14.
[0063] Referring to Figure 3, each communication device 14 is configurable as a content device 22 and/or an initiating device 24. The communication system 10 should include at least a first communication device 14a configured as a content device 22 and at least a second communication device 14b configured as an initiating device 24, the second communication device 14b constituting separate and distinct hardware to the first communication device 14a. Typically though, the communication system 10 comprises an open ended number of unique communication devices 14 which can be selectively configured, for example by a user, as a content device 22 or an initiating device 24 as required. Selectively configured means, in effect, that a communication device 14 can in one instance be configured as a content device 22 and in another instance as an initiating device 24, and this selection may at least in part be determined by the actions of a user 20.
[0064] For Figures 4 to 8, reference is made to “content devices 22” and “initiating devices 24” as opposed to the more general “communication devices 14”, though it is understood that the disclosure is to a communication device 14 configured as either the content device 22 or initiating device 24.
WO 2016/179665
PCT/AU2016/050365 [0065] Referring to Figure 4, each content device 22 is configured to produce content data. In the particular embodiment shown, the content data is visual data typically a still photograph or a video. This visual data is generated “on the fly” by the content device 22 through the operation of a digital camera 23 of the content device 22. Audio data can also be generated by the content device 22, in particular when the visual data comprises a video. In any event, metadata can also be generated by the content device 22 and associated with the visual data. Such metadata may include location data associated with the content device (e.g. local time, location information such as GPS coordinates, etc.). In another embodiment, audio data can also constitute the content data without providing visual data.
[0066] Still referring to Figure 4, the content device 22a is shown in network communication with an initiating device 24a.
[0067] Referring now to Figure 5, according to an embodiment the content device 22a receives via the network 16 configuration data from an initiating device 24 at step 100. The configuration data includes at least a content request specifying one or more parameters and providing an instruction to the content device 22 to generate content. The content device 22 is then configured for generating content data in accordance with the received one or more parameters, which dictate at least one aspect of the operation of the content device 22.
[0068] In an embodiment, the configuration data is communicated from the initiating device 24 to the server 12, which in turns communicates the configuration data to the content device 22.
[0069] In the embodiments described herein, the content data is only generated after an activation action is undertaken by a user 20 of the content device 22, at optional step 101. Typically, the activation action constitutes interacting with the content device 22, for example through a touch screen interface, and providing an input. In one implementation, the content device 22
WO 2016/179665
PCT/AU2016/050365 displays to the user a notification indicating that configuration data has been received, and the user “accepts” the notification. It is envisaged, however, that the activation action is not directly undertaken by the user 20, for example, may correspond simply to receipt of the content data.
[0070] The one or more parameters generally relate to the operation of the hardware of the content device 22 provided for generating the content data, and the content device 22 is configured according to the one or more parameters at step 102.
[0071 ] In the case of the generation of visual data in the form of a still photograph, the one or more parameters include a time delay parameter. The time delay parameter configures the content device 22 by providing an instruction to the content device 22 to capture a still photograph after a time delay from the occurrence of the activation action. It is envisaged that the time delay will be a number of seconds when the content device 22 is a mobile phone, for example selected from a number of whole seconds between 1 and 10. The time delay may include or exclude an initiation time of the hardware of the content device 22.
[0072] In the case of the generation of visual data in the form of a video, the one or more parameters include a time delay parameter and an optional recording length parameter. The time delay parameter acts in the same way as for the generation of a still photograph, providing a time delay between the activation action and the initiation of video recording by the content device 22. The recording length parameter configures the content device 22 by specifying the length of the video recording, and can be implemented as an optional parameter or a required parameter. Where the recording length parameter is an optional parameter and is not provided as part of the configuration data, it is envisaged that the user of the content device 22 can control the length of the video recording. Where the recording length parameter is provided, either as an optional or required parameter, the content device 22 will record for the corresponding length of time.
WO 2016/179665
PCT/AU2016/050365 [0073] In an embodiment, the configuration data received from an initiating device 24 includes content type parameter specifying a type of content data that the content device 22 is to generate. This may be particularly useful where the content devices 22 are capable of producing one or more types of content data. For example, the content type parameter can be selected from one of: still photograph, video, audio recording, etc. Selection of a particular type of content data is shown in Figure 5 as optional step 103.
[0074] In another embodiment, each content device 22 is configured only to produce one type of content data. In an embodiment, this is a still photograph. In this implementation, it is unnecessary for the configuration data to include a content type parameter.
[0075] The generated content data is then communicated via the network 16 from the content device 22 to the initiating device 24 at step 104. Typically, this communication will occur without further input from the user of the content device 22, and will occur shortly after the content data has been generated. In an embodiment, if the network 16 is temporarily non-accessible to the content device 22, the content data will be stored in a memory of the content device 22 until such time as the network 16 is once again accessible. In a variation of this embodiment, a time limit will be imposed after which the content data is removed from the memory of the content device 22 and no communication to the initiating device 24 is undertaken.
[0076] In an embodiment, the content data is communicated from the content device 22 to the server 12, which in turns communicates the content data to the initiating device 12.
[0077] The initiating device 24 is then configured, typically after receiving an input from a user 20 of the initiating device 24, to present the content data at step 105. For example, where the content data corresponds to a still photograph or a video, a screen of the initiating device 24 is utilised to display the still photograph
WO 2016/179665
PCT/AU2016/050365 of video. In another example, the content data contains audio which is played through speakers associated with the initiating device 24.
[0078] In a variation to the embodiment of Figure 5, the content device 22 receives configuration data from one or more, preferably a plurality, of initiating devices 24. The content device 22 can be configured to display an indicator of the number of initiating devices 24 from which configuration data has been obtained. The content device 22 then, for example due to an activation action corresponding to a user of the content device 22 providing an input, produces content data as previously described. The content data can be produced in accordance with one or more parameters received from one, some, or all of the initiating devices 24. Alternatively, in this variation, the content data is produced in accordance with predetermined parameters not communicated with the configuration data. The content data is then communicated to each of the initiating devices 24.
[0079] Another variation to the embodiment of Figure 5 is shown in Figures 9 and 10. In this embodiment, the content device 22 generates content data in response to a threshold module 30 providing configuration data to the content device 22. Referring to Figure 9, the threshold module 30 is shown in network communication with a plurality of initiating devices 24a-c and the content device 22.
[0080] The threshold module 30 is configured to receive initiating requests from the plurality of initiating devices 24. The threshold module 30 can be implemented, for example, as a software module operated within the content device 22 or the server 12. The threshold module 30 then communicates configuration data including a content request and optionally one or more parameters to the content device 22 once a preselected threshold condition is met. In this way, the threshold module 30 acts as an intermediary between the initiating devices 24 and the content device 22. Alternatively, the one or more parameters are preconfigured on the content device 22.
WO 2016/179665
PCT/AU2016/050365 [0081] In one implementation, the threshold condition corresponds to receiving initiating requests from a predetermined minimum number of initiating devices 24.
[0082] The threshold condition (such as the minimum number of initiating devices 24) can be set before receipt of configuration data. The threshold condition can be configured by a user associated with the content device 22, for example through an interface provided on the content device 22, or alternatively, a user can set the threshold condition through operation of a separate user terminal in communication (either directly or via the network 16) with the threshold module 30.
[0083] The threshold module 30 communicates configuration data to the content device 22 upon the threshold condition being met. In one example, the pre-selected threshold condition is for the threshold module 30 to receive initiating requests from 30,000 initiating devices 24. Once this threshold condition is met, the threshold module 30 undertakes action similar to the initiating device 24 of the embodiment of Figure 5; that is, the threshold module 30 communicates configuration data including a content request and one or more parameters to the content device 22.
[0084] The content device 22 then generates content data in accordance with the content request and the one or more parameters as previously described with reference to Figure 5.
[0085] In a variation to this embodiment, the content device 22 is provided with the one or more parameters separately to the configuration data communicated from the threshold module 30.
[0086] The content device 22 then causes the content data to be communicated to at least one and preferably all of the plurality of initiating devices 24. In one implementation, as shown in Figure 9, the one or more
WO 2016/179665
PCT/AU2016/050365 parameters includes information identifying each of the initiating devices 24 thereby enabling the content device 22 to directly communicate the content data to the plurality of initiating devices 24. In another implementation, as shown in Figure 10, the threshold module 30 is in communication with a distribution module 32, which can be implemented, for example, as a software module operated within the content device 22 or the server 12. The distribution module 32 receives from the threshold module 30 (optionally via the content device 22) information identifying each of the initiating devices 24, and the generated content data from the content device 22. It is then the distribution module 32 which communicates the content data to each of the initiating devices 24.
[0087] Referring to Figure 6, an embodiment is shown in which the initiating device 24 communicates the configuration data (shown by lines 200) to a plurality of content devices 22 (three content devices 22a, 22b, 22c are shown in the figure). According to this embodiment, each content device 22 generates its own content data as already described. Each content device 22 then communicates its generated content data to the initiating device 24 (shown by lines 201). It is understood that each content data is generally generated at different times, in particular where an activation action is required before the content data is generated. It is therefore the case that, generally, the initiating device 24 will receive each content data at different times.
[0088] According to a variation of this embodiment, the content data of each content device 22 is also communicated to the other content devices 22. This can be an optional occurrence, for example, each content device 22 requests an input from its associated user to allow the content data to be communicated to the other content devices 22. Despite this, generally, the content data is in any event communicated to the initiating device 24. The content data can be first communicated to the initiating device 24, which then communicates the content data to each of the other content devices 22. A variation has each content device 22 directly communicate its content data to the remaining content devices 22. In the later case, the configuration data originally sent to each content device 22
WO 2016/179665
PCT/AU2016/050365 includes ID data comprising identifiers of each content device 22 receiving the configuration data. This enables each content device 22 to identify each other content device 22 for sending content data.
[0089] In another variation of the implementation, each content device 22 communicates its content data to each of the other content devices 22 via the server 12. In effect, the server 12 acts as a distributor of content data between the content devices 22.
[0090] According to an embodiment, the event of an initiating device 24 receiving content data generated by a content device 22 results in a separate success event. The success event corresponds to an action taken in acknowledgement of the initiating device 24 successfully obtaining content data from a content device 22. In one implementation, the success event includes facilitating a payment by the user of the initiating device 24 to a payment server. The payment server receives the payment, and can then distribute the received payment according to pre-determined payment rules. For example, a first percentage of the received payment is paid to an operator of the communication system 10 and a second percentage (preferably the remainder of the payment) is paid to a user of the content device 22 which produced the content data received by the initiating device 24.
[0091] In another embodiment, the success event includes the manipulation of the content data received from the content device 22. By way of example, an organiser of an event or campaign, using the initiating device, can send a request for content data to a plurality of content devices. The user of each content device is preferably subscribed to a service of an organiser or is a consumer (or potential consumer) of a service provided by the organiser. The request for content data may be accompanied by one or more rules governing elements to be included in the content. For example, the rule can require the user to capture content showing the user using, displaying, or promoting a product/service of the organiser. Upon a content device receiving and triggering the request for content
WO 2016/179665
PCT/AU2016/050365 data from the initiating device, the user captures content data, which is transmitted to the initiating device. If content data satisfies the rule(s) set by the initiating device, the content data is manipulated, which is then used as part of the organiser’s event or campaign. The content data can for example be manipulated to the extent that content from the organiser is incorporated into the content data. The content from the organiser may for example be a trade mark, advertisement, or promotion of the organiser.
[0092] Referring to Figure 7, the server 12 maintains record database 26 suitable for recording instances in which content data has been communicated between particular content devices 22 and initiating devices 24. Where the server 12 is implemented as part of the communication devices 14, the record database 26 will typically only contain records 27 relating to communications involving the particular communication device 14 and/or one or more communication devices 14 associated with the same user 20 as the communication device 14 implementing the server 12. Where the server 12 is implemented separately to the communication devices 14, the record database 26 typically comprises records 27 relating to a plurality of communication devices 14.
[0093] The record database 26 can be configured to record different information in the form of records 27, depending on the implementation. In one implementation, the record database 26 simply comprises records identifying instances of successes and/or non-successes. In effect, each identifier 19 has associated with it, in the record database 26, a history of successful and/or nonsuccessful communications of content data from particular content devices 22 and initiating devices 24.
[0094] It is envisaged that the actual content data sent from a content device 22 to an initiating device 24 via a server 12 can be recorded into the record database 26. Preferably, the users of the initiating device 24 and content device 22 will provide, for example through interfaces of the initiating device 24 and
WO 2016/179665
PCT/AU2016/050365 content device 22, permission for the content data to be recorded into the record database 26.
[0095] Other records 27 include: time of communication of the configuration data; time of generation of content data; time of receipt and/or presentation of content data by the initiating device 24; etc.
[0096] The record database 26 of the server 12 can be accessed via an analytics client, which can be implemented in the same hardware as a communication device 14 or different hardware. In the later case, it is envisaged that a personal computer in data communication with the network 16 may be configured as an analytics client.
[0097] In an embodiment, the initiating device 24 (and in applicable embodiments, the content device(s) 22) is configured to limit the availability of the content data to a user 20 of the initiating device 24. Typically, this is implemented through removal of the content data immediately following the display of the content data on the initiating device 24. Furthermore, the initiating device 24 can be configured to limit the time content data is presented to the user 20. In the case of a still photograph, this may be a fixed number of seconds (for example, ten seconds). In the case of a video or audio recording, it can be the length of the recording.
[0098] In an embodiment, the configuration data includes initiating content data. The initiating content data is generated by the initiating device 24 in a similar manner to the content data generated by a content device 22. In this embodiment, in order to successfully instruct a content device 22 to generate content data, the initiating device 24 is required to first provide initiating content data to the content device 22. The initiating content data can be of the same type as the content data that will be generated, for example, a still photograph, a video, or an audio recording. In one implementation, the initiating content data is presented by the content device 22 to a user 20 of the content device 22 before
WO 2016/179665
PCT/AU2016/050365 the content device 22 generates the content data. In an alternative implementation, the initiating content data is only present by the content device 22 to the user of the content device 22 after the generation of the content data. In this later implementation, the presentation of the initiating content data can be a “reward” to the user of the content device 22 for undertaking the activation action. This later implementation thereby provides additional incentives in order to achieve a success.
[0099] With reference to Figure 8, the content data generated by the content device 22 can, in an embodiment, be selected from a repository 28 comprising a plurality of pre-generated content items 29 rather than generated “on-the-fly” in response to receipt of configuration data from an initiating device 24. In the example shown in Figure 8, the repository 28 constitutes a database maintained by the server 12. Typically, the content items 29 are created by a provider entity, for example a media company. The content items 29 can constitute a wide variety of different formats, typically those formats suitable for providing to a mobile phone, in particular a smartphone. The content items 29 can comprise instructions that, upon receipt, cause the initiating device 24 to undertake an action, for example, displaying a particular webpage. The content items 29 can also comprise media items such as still photographs, videos, audio recordings, etc.
[00100] In an implementation of this embodiment, the content data is selected by selecting a content item 29 from the repository of content items 28 using a purely random selection process, or a modified random selection process. A purely random selection process can correspond to selecting one of the content items at random and communicating this to the initiating device 24.
[00101] A modified random selection process utilises information of the user of the initiating device 24 and/or provided with the configuration data in order to determine a subset of the content items 29 of the repository for subsequent
WO 2016/179665
PCT/AU2016/050365 random selection and/or to alter the probability of different content items 29 being selected.
[00102] Further modifications and improvements may be made without departing from the scope of the present invention. For example, it is envisaged that each identifier 19 of the contact database 18 may be associated with one or more identifier groups. A user 20 of an initiating device 24 may select an identifier group, and this is communicated to the server 12. The server 12 then selects one (for example, at random), several, or all of the identifiers 19 associated with the identifier group, determines the content device 22 of each identifier 19, and sends the configuration data to each determined content device 22. According to this example, the user 20 is not required to specify particular recipients of the configuration data.
WO 2016/179665
PCT/AU2016/050365

Claims (35)

  1. THE CLAIMS DEFINING THE INVENTION ARE AS FOLLOWS:
    1. A method for configuring a content device to generate content data, comprising the steps of:
    receiving, at the content device, first configuration data from an initiating device via a network, wherein the first configuration data comprises at least a first content request and at least one parameter;
    configuring the content device to generate content data of a type associated with the first content request;
    generating the content data in accordance with the at least one parameter; and sending, via the network, the content data to the initiating device.
  2. 2. A method for configuring a content device to generate content data, comprising the steps of:
    receiving, at the content device, first configuration data from a plurality of initiating devices via a network, wherein the first configuration data of each initiating device comprises at least a first content request;
    configuring the content device to generate content data of a type associated with the first content request;
    determining at least a first parameter, and generating the content data in accordance with the at least the first parameter; and sending, via the network, the content data to each of the initiating devices.
  3. 3. The method of claim 1 or 2, wherein the content data is of a type determined by the first content request.
  4. 4. The method according to claim 1 or 2, wherein the step of generating the content data includes the steps of obtaining from a camera of the content device visual data, wherein the visual data corresponds, at least in part, to the
    WO 2016/179665
    PCT/AU2016/050365 content data, preferably wherein the visual data is one of a photograph or a video.
  5. 5. The method according to claim 4, wherein the at least one parameter includes a time delay parameter, and wherein the visual data is acquired from the camera after a delay determined by the time delay parameter from an activation action received at the content device.
  6. 6. The method according to claim 4, wherein the visual data is a video, and wherein the at least one parameter includes a recording length parameter, and wherein the visual data is acquired from the camera over a period of time determined by the recording length parameter.
  7. 7. The method according to claim 1 or 2, further comprising the steps of: the, or each, initiating device sending, via the network, first configuration data to the content device;
    the, or each, initiating device receiving, via the network, the content data; and at least one initiating device displaying the content data on a display of the initiating device.
  8. 8. The method according to claim 7, wherein the content data is displayed for a predetermined time and/or the content data is displayable for a predetermined time.
  9. 9. The method according to claim 1 or 2, including the step of providing a server in communication, via the network, with the content device configured for maintaining a contact database, wherein the contact database comprises a plurality of identifiers including a first identifier associated with the content device, and wherein the, or each, first configuration data is received by the content device via the server and/or the content data is sent to the, or each, initiating device via the server.
    WO 2016/179665
    PCT/AU2016/050365
  10. 10. The method according to claim 9, further comprising the steps of: the server receiving first configuration data from the, or each, initiating device via the network, the first configuration data further comprising a destination ID parameter;
    the server retrieving an identifier from the contact database corresponding to the destination ID parameter;
    the server determining a content device network location of the content device based on the retrieved identifier; and the server sending the first configuration data to the content device based at least in part on the content device network location.
  11. 11. The method according to claim 9, wherein the server is further configured to maintain a record database, further comprising the steps of:
    the server recording a request event into the record database in response to the server sending first configuration data to the content device; and/or the server recording a response event into the record database in response to the server receiving the content data from the content device.
  12. 12. The method according to claim 11, wherein the server is configured to record the content data received from the content device into the record database.
  13. 13. The method according to claim 1, further comprising the steps of: receiving, at one or more further content devices, the first configuration data from the initiating device via a network;
    configuring the, or each, further content device to generate content data of a type associated with the first content request;
    for the, or each, further content device, generating the content data in accordance with the at least one parameter;
    sending, via the network, the content data of the, or each, further content device to the initiating device.
    WO 2016/179665
    PCT/AU2016/050365
  14. 14. The method according to claim 1, wherein the generation of the content data includes the step of selecting a pre-generated content item from a repository of content items.
  15. 15. A server comprising a network interface and a first memory operatively associated with a processor, wherein the first memory is configured for storing a content database comprising a plurality of identifiers and wherein the server is configured for maintaining the content database, the server configured to:
    receive, at the network interface, first configuration data and a destination ID parameter from an initiating device, wherein the first configuration data comprises at least a first content request and at least one parameter;
    in response, retrieve an identifier from the contact database corresponding to the destination ID parameter;
    determine a content device network location associated with the retrieved identifier;
    send via the network interface the first configuration data to a content device based at least in part on the network location;
    receive, from the content device at the network interface, content data generated by the content device in response to the content device receiving the first configuration data, the content data being determined at least in part based on the at least one parameter; and send via the network interface the content data to the initiating device.
  16. 16. The server according to claim 15, wherein the content data is generated according to the method of claim 1.
  17. 17. The server according to claim 15, wherein the server is further configured to:
    maintain a record database;
    record a request event into the record database in response to the server sending first configuration data to the content device; and/or
    WO 2016/179665
    PCT/AU2016/050365 record a response event into the record database in response to the server receiving the content data from the content device.
  18. 18. A communication system comprising an initiating device and a content device, the initiating device in network communication with the content device, wherein the content device is configured to undertake the following steps:
    receiving, at the content device, first configuration data from an initiating device via a network, wherein the first configuration data comprises at least a first content request and at least one parameter;
    configuring the content device to generate content data of a type associated with the first content request;
    generating the content data in accordance with the at least one parameter; and sending, via the network, the content data to the initiating device.
  19. 19. The system according to claim 18, wherein the content data is of a type determined by the first content request.
  20. 20. The system according to claim 19, wherein the initiating device is configured to undertake the following steps:
    sending via the network the configuration data to the content device;
    receiving, via the network, the content data; and displaying the content data on a display of the initiating device.
  21. 21. A method for configuring a computing device, the method comprising the steps of: sending instructions configured to cause the computing device to implement the method of claim 1 or 2.
  22. 22. A method for acquiring content data from a content device, comprising the steps of:
    receiving an initiating request from each of a plurality of initiating devices
    WO 2016/179665
    PCT/AU2016/050365 via a network;
    determining that a threshold condition related to the received initiating requests has been satisfied, and in response communicating first configuration data including a first content request to the content device;
    obtaining content data, the content data generated by the content device in accordance with the first configuration data; and communicating, via the network, the content data to at least one of the plurality of initiating devices.
  23. 23. The method of claim 22, wherein the threshold condition corresponds to receiving initiating requests from a pre-determined minimum number of initiating devices, preferably wherein the pre-determined minimum number is selected by a user of the content device.
  24. 24. The method of claim 22, wherein the initiating requests are received at a threshold module, and wherein the threshold module is configured for determining that the threshold condition has been satisfied.
  25. 25. The method of claim 22, further comprising the steps of: receiving, at the content device, the first configuration data; configuring the content device to generate content data of a type associated with the first content request; and generating the content data in accordance with at least one parameter.
  26. 26. The method of claim 22, wherein a distribution module obtains the content data from the content device, and wherein the distribution module communicates the content data to the at least one initiating device.
  27. 27. A server comprising a network interface and a first memory operatively associated with a processor, wherein the first memory is configured for storing a content database comprising a plurality of identifiers and wherein the server is configured for maintaining the content database,
    WO 2016/179665
    PCT/AU2016/050365 the server configured to:
    receive, at the network interface, initiating requests from each of a plurality of initiating devices;
    determine that a threshold condition has been satisfied, the threshold condition associated with a content device; and in response, communicate first configuration data comprising a first content request and one or more parameters to the content device.
  28. 28. The server of claim 27, further configured to:
    receive, from the content device, content data generated by the content device in accordance with the first configuration data;
    in response, communicate via the network the content data to at least one of the plurality of initiating devices.
  29. 29. The server of claim 28, wherein the content data is communicated to each of the plurality of initiating devices.
  30. 30. A communication system comprising a plurality of initiating devices and a content device, the initiating devices and content device being in network communication with a threshold module, wherein the initiating devices are each configured to communicate to the threshold module an initiating request, wherein the threshold module is configured to determine, based on the received initiating communication data, that a pre-determined threshold condition has been met and in response communicate to the content device first configuration data comprising content request and one or more parameters, wherein the content device is configured to generate content data in response to receiving the first configuration data, the content data generated in accordance with the first configuration data, and wherein the content device is configured to communicate, optionally via a distribution module, the content data to at least one of the initiating devices.
    WO 2016/179665
    PCT/AU2016/050365
  31. 31. The system of claim 30, wherein the content data is communicated to each of the plurality of initiating devices.
  32. 32. The system of claim 30, wherein the threshold module is implemented within the content device.
  33. 33. The system of claim 30, wherein the threshold module is implemented within a server in network communication with the content device and each of the plurality of initiating devices.
  34. 34. The system of claim 33, wherein the server is the server of claim 27
  35. 35. The method of claim 1,2 or claim 18, further comprising the steps of:
    facilitating payment to a user of the content device for the, or each, initiating device receiving content data.
    WO 2016/179665
    PCT/AU2016/050365
    1/10
    Figure 1
    WO 2016/179665
    PCT/AU2016/050365
    2/10
    Figure 2b
    WO 2016/179665
    PCT/AU2016/050365
    3/10
    X # MK. Ϊ to,» ·» ««-:«« λ*»*»» ««-:««>e« j»*
    KB
    20d
    Figure 2c
    WO 2016/179665
    PCT/AU2016/050365
    4/10
    Figure 3a
    14c
    Figure 3b
    14d
    WO 2016/179665
    PCT/AU2016/050365
    5/10
    Figure 4
    23a
    WO 2016/179665
    PCT/AU2016/050365
    6/10
    Figure 5
    WO 2016/179665
    PCT/AU2016/050365
    7/10
    Figure 6
    WO 2016/179665
    PCT/AU2016/050365
    8/10
    Figure 8
    WO 2016/179665
    PCT/AU2016/050365
    9/10 v_/ \_/ \_/
    Figure 9
    WO 2016/179665
    PCT/AU2016/050365
    10/10
    Figure 10
AU2016262133A 2015-05-13 2016-05-13 Method and system for remote data acquisition Active AU2016262133B2 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
AU2015901741A AU2015901741A0 (en) 2015-05-13 Method and System for Remote Data Acquisition
AU2015901741 2015-05-13
AU2015903370A AU2015903370A0 (en) 2015-08-20 Method and System for Remote Data Acquisition
AU2015903370 2015-08-20
PCT/AU2016/050365 WO2016179665A1 (en) 2015-05-13 2016-05-13 Method and system for remote data acquisition

Publications (2)

Publication Number Publication Date
AU2016262133A1 true AU2016262133A1 (en) 2018-01-18
AU2016262133B2 AU2016262133B2 (en) 2020-07-23

Family

ID=57247620

Family Applications (1)

Application Number Title Priority Date Filing Date
AU2016262133A Active AU2016262133B2 (en) 2015-05-13 2016-05-13 Method and system for remote data acquisition

Country Status (2)

Country Link
AU (1) AU2016262133B2 (en)
WO (1) WO2016179665A1 (en)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7554570B2 (en) * 2005-06-21 2009-06-30 Alcatel-Lucent Usa Inc. Network support for remote mobile phone camera operation
US7779444B2 (en) * 2006-07-23 2010-08-17 William Glad System and method for video on request
US20130093904A1 (en) * 2011-02-11 2013-04-18 Cole & Ashcroft Lp Remote Shutter for a Camera or Other Imaging Device
US20130054750A1 (en) * 2011-08-23 2013-02-28 Vlognow, Inc. System and method for requesting media coverage of an event
US20140317202A1 (en) * 2013-04-19 2014-10-23 Tim Baldwin System and method for requesting and sending audio, video, still pictures, and text from a specified location
US20150124109A1 (en) * 2013-11-05 2015-05-07 Arben Kryeziu Apparatus and method for hosting a live camera at a given geographical location

Also Published As

Publication number Publication date
WO2016179665A1 (en) 2016-11-17
AU2016262133B2 (en) 2020-07-23

Similar Documents

Publication Publication Date Title
US10959040B2 (en) Venue and event recommendations for a user of a portable media player device
US9953356B2 (en) Image-based product marketing systems and methods
KR101526837B1 (en) Method, system, and apparatus for exchanging data between client devices
US8943164B2 (en) Apparatus and methods for retrieving/ downloading content on a communication device
CN104823169B (en) For the index configurations that can search for data in network
US9080891B2 (en) Methods, devices, and computer program products for exchanging interactive map information
US9078047B2 (en) Content reproduction device
WO2015124449A1 (en) An analytics server and method
KR20160132047A (en) Communication event history
US20150373016A1 (en) Sharing content using a dongle device
US10218769B2 (en) Monitoring digital images on mobile devices
JP2010160585A (en) Server apparatus, information processing method, information processing system
US9137295B2 (en) Determining audience engagement levels with presentations and providing content based on the engagement levels
AU2016262133B2 (en) Method and system for remote data acquisition
JP2020537385A (en) Systems and methods for providing video messaging services
JP6122235B1 (en) Image management server, image management method, recording medium, and program
CN114666643A (en) Information display method and device, electronic equipment and storage medium
US10462021B2 (en) System and method for providing object via which service is used
US20110314416A1 (en) Collected media content data
WO2017113061A1 (en) Information processing method and apparatus
JP6491308B2 (en) TERMINAL DEVICE CONTROL PROGRAM, TERMINAL DEVICE CONTROL METHOD, AND TERMINAL DEVICE
JP2015069533A (en) Data management device and data management method
JP2014154029A (en) Useful information presentation system and method for controlling useful information presentation system
WO2017181641A1 (en) Method and device for communication number processing, and storage medium
CN111343480B (en) Video processing method, device and storage medium

Legal Events

Date Code Title Description
MK25 Application lapsed reg. 22.2i(2) - failure to pay acceptance fee
NB Applications allowed - extensions of time section 223(2)

Free format text: THE TIME IN WHICH TO PAY THE ACCEPTANCE FEE HAS BEEN EXTENDED TO 23 NOV 2020

FGA Letters patent sealed or granted (standard patent)