WO2008151383A1 - Transfert de contenu - Google Patents

Transfert de contenu Download PDF

Info

Publication number
WO2008151383A1
WO2008151383A1 PCT/AU2008/000855 AU2008000855W WO2008151383A1 WO 2008151383 A1 WO2008151383 A1 WO 2008151383A1 AU 2008000855 W AU2008000855 W AU 2008000855W WO 2008151383 A1 WO2008151383 A1 WO 2008151383A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
processing system
data
request
transfer
Prior art date
Application number
PCT/AU2008/000855
Other languages
English (en)
Inventor
Christopher Paul Adkins
Tim Murray-Leslie
Alexander Charles Macpherson
Bradley Ronald Down
Original Assignee
Beam Me 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 AU2007903235A external-priority patent/AU2007903235A0/en
Application filed by Beam Me Pty Ltd filed Critical Beam Me Pty Ltd
Publication of WO2008151383A1 publication Critical patent/WO2008151383A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party

Definitions

  • the present invention generally relates to transferring content to a content receiving device.
  • the contact details may simply be memorised, written down on a piece of paper, or typed into a processing system for future retrieval.
  • this process is disadvantageous for a number of reasons. Firstly, by having to memorise or reduplicate the content of the contact details can cause errors being made. Furthermore, in this age of near-instant access to information, the recordal of information is a relatively time-consuming task.
  • the method includes, in a server processing system: receiving, from a user processing system, a request for content; obtaining the content requested; and transferring message data indicative of the content to the content receiving device.
  • the method includes, in the server processing system: receiving, from the user processing system, request data, wherein the request data is received in response to the user processing system processing first data received from an intermediary processing system; determining, based at least partially upon the request data, if the content can be transferred to the content receiving device; and in the event of a positive determination: transferring second data indicative of a content transfer interface to the user processing system for display; receiving, from the user processing system and upon user interaction with the content transfer interface, content request data indicative of the request for the content; and transferring ⁇ message data indicative of the content to the content receiving device.
  • the method in another form, in the event of a negative determination, includes, in the server processing system, restricting the content being transferred to the content receiving device.
  • the request data is indicative of a content identity indicative of a unique identity of the content requested, wherein the server processing system queries a data store associated with the server processing system using the content identity to determine if the content is transferable to the content receiving device.
  • the method includes, in the server processing system: receiving input data from a content provider; generating, using the input data, the first data; storing, in a data store associated with the server processing system and using the input data, authorisation data used for determining, with the request data, if the content is transferable; and transferring the first data to the intermediary processing system.
  • the authorisation data is indicative of at least one of identification data indicative of an identity of the intermediary processing system which is authorised to transfer the first data to the user processing system, and financial data indicative of a payment arrangement for funding the transfer of the content
  • the method includes, in the server processing system, using the request data in association with at least one of the identification data and the financial data to determine if the content is transferable to the content receiving device.
  • the request data is indicative of an intermediary processing system identity
  • the server processing system queries the data store using the intermediary processing system identity to determine if the content is transferable to the content receiving device.
  • the intermediary processing system is a webserver hosting a portal, wherein the intermediary processing system identity is a Uniform Resource Locator (URL) of the portal.
  • URL Uniform Resource Locator
  • obtaining the content includes one of: retrieving the content which is stored in a data store associated with the server processing system; and processing the request data, wherein the request data is at least partially indicative of the content.
  • At least a portion of the request data is encrypted, wherein the method includes the server processing system decrypting the request data.
  • the request data is indicative of an encrypted string indicative of the content to be transferred to the content receiving device.
  • the method includes, in the server processing system: generating a decryption key using intermediary processing system identity and the content identity indicated by the request data; and decrypting the encrypted string using the decryption key to obtain the content for transfer to the content receiving device.
  • a portion of the message data is indicative of advertising content.
  • the server processing system receives advertiser data from an advertiser, wherein the advertiser data indicates at least a partial subsidy for the transfer of the content to the content receiving device.
  • the method includes, in the server processing system: recording data indicative of a frequency of requests for transfer of the content; and transferring data to a content provider indicative of the frequency of requests for transfer of the content.
  • the content receiving device is a mobile telecommunications device.
  • the mobile telecommunications device is a mobile telephone.
  • a server processing system for transferring content to a content receiving device, wherein the server processing system is configured to: receive, from a user processing system, a request for content; obtain the content requested; and transfer message data indicative of the content to the content receiving device.
  • the server processing system is configured to: receive, from the user processing system, request data, wherein the request data is received in response to the user processing system processing first data received from an intermediary processing system; determine, based at least partially upon the request data, if the content can be transferred to the content receiving device; and in the event of a positive determination: transfer second data indicative of a content transfer interface to the user processing system for display; receive, from the user processing system and upon user interaction with the content transfer interface, content request data indicative of the request for the content; and transfer message data indicative of the content to the content receiving device.
  • the server processing system in the event of a negative determination, is configured to restrict the content being transferred to the content receiving device.
  • the request data is indicative of a content identity indicative of a unique identity of the content requested, wherein the server processing system queries a data store associated with the server processing system using the content identity to determine if the content is transferable to the content receiving device.
  • the server processing system is configured to: receive input data from a content provider; generate, using the input data, the first data; store, in a data store associated with the server processing system and using the input data, authorisation data used for determining, with the request data, if the content is transferable; and transfer the first data to the intermediary processing system.
  • the authorisation data is indicative of at least one of identification data indicative of an identity of the intermediary processing system which is authorised to transfer the first data to the user processing system, and financial data indicative of a payment arrangement for funding the transfer of the content, wherein the server processing system is configured to use the request data in association with at least one of the identification data and the financial data to determine if the content is transferable to the content receiving device.
  • the request data is indicative of an intermediary processing system identity
  • the server processing system queries the data store using the intermediary processing system identity to determine if the content is transferable to the content receiving device.
  • the intermediary processing system is a webserver hosting a portal, wherein the intermediary processing system identity is a Uniform Resource Locator (URL) of the portal.
  • URL Uniform Resource Locator
  • the server processing system is configured to obtain the content by: retrieving the content which is stored in a data store associated with the server processing system; and processing the request data, wherein the request data is at least partially indicative of the content.
  • the request data is encrypted, wherein the server processing system is configured to decrypt the request data.
  • the request data is indicative of an encrypted string indicative of the content to be transferred to the content receiving device.
  • the server processing system is configured to: generate a decryption key using intermediary processing system identity and the content identity indicated by the request data; and decrypt the encrypted string using the decryption key to obtain the content for transfer to the content receiving device.
  • a portion of the message data is indicative of advertising content.
  • the server processing system receives advertiser data from an advertiser, wherein the advertiser data indicates at least a partial subsidy for the transfer of the content to the content receiving device.
  • the server processing system is configured to: record data indicative of a frequency of requests for transfer of the content; and transfer data to a content provider indicative of the frequency of requests for transfer of the content.
  • the content receiving device is a mobile telecommunications device.
  • the mobile telecommunications device is a mobile telephone.
  • a computer program product including a computer readable medium having a computer program recorded therein or thereon, the computer program enabling transfer of content to a content receiving device, wherein the computer program product configures a server processing system to: receive, from a user processing system, a request for content; obtain the content requested; and transfer message data indicative of the content to the content receiving device.
  • a method of requesting content to be transferred to a content receiving device includes, in a user processing system: receiving interface data indicative of a content request interface; displaying, using the interface data, the content request interface; and transferring, to a server processing system, content request data indicative of a user requesting content by interacting with the content request interface, wherein the transfer of the content request data causes the requested content to be transferred to the content receiving device.
  • the method includes, in the user processing system: receiving the first data from an intermediary processing system; processing the first data to generate request data; transferring, to a server processing system, the request data, wherein the server processing system determines, based at least partially upon the request data, if the content can be transferred to the content receiving device; in the event of a positive determination by the server processing system, receiving, from the server processing system, second data indicative of the interface data; and displaying, using the second data, the content request interface.
  • the processing the first data includes, in the user processing system, interpreting the first data.
  • the first data is computer interpretable code, wherein interpreting the first data includes, in the user processing system, interpreting the computer interpretable code in a computer interpretable code application executed by the user processing system.
  • the computer interpretable code application is one of: an Internet browser; and an email application.
  • the method includes: receiving embedded data in addition to the first data from the intermediary processing system; and processing the embedded data, wherein one or more database queries are transferred to one of: the intermediary processing system; a processing system associated with a provider of the content; and another processing system in data communication with the user processing system.
  • the embedded data is embedded within one of: the first data; and computer interpretable code received from the intermediary processing system, wherein the computer interpretable code includes the first data.
  • a user processing system configured to request content to be transferred to a content receiving device, wherein the user processing system is configured to: receive interface data indicative of a content request interface; display, using the interface data, the content request interface; and transfer, to a server processing system, content request data indicative of a user requesting content by interacting with the content request interface, wherein the transfer of the content request data causes the requested content to be transferred to the content receiving device.
  • the user processing system is configured to: receive the first data from an intermediary processing system; process the first data to generate request data; transfer, to a server processing system, the request data, wherein the server processing system determines, based at least partially upon the request data, if the content can be transferred to the content receiving device; in the event of a positive determination by the server processing system, receive, from the server processing system, second data indicative of the interface data; and display, using the second data, the content request interface.
  • the user processing system processes the first data by interpreting the first data.
  • the first data is computer interpretable code, wherein the user processing system interprets the computer interpretable code in a computer interpretable code application executed by the user processing system.
  • the computer interpretable code application is one of: an Internet browser; and an email application.
  • the user processing system receives embedded data in addition to the first data from the intermediary processing system; and processes the embedded data, wherein one or more database queries are transferred to one of: the intermediary processing system; a processing system associated with a provider of the content; and another processing system in data communication with the user processing system.
  • the embedded data is embedded within one of: - l i ⁇
  • the first data includes computer interpretable code received from the intermediary processing system, wherein the computer interpretable code includes the first data.
  • computer program product including a computer readable medium having a computer program recorded therein or thereon, the computer program enabling a request for content to be transferred to a content receiving device, wherein the computer program product configures a user processing system to: receive interface data indicative of a content request interface; display, using the interface data, the content request interface; and transfer, to a server processing system, content request data indicative of a user requesting content by interacting with the content request interface, wherein the transfer of the content request data causes the requested content to be transferred to the content receiving device.
  • a method of requesting content to be transferred to a content receiving device includes: in a user processing system: receiving interface data representing a content request interface; displaying, using the interface data, the content request interface; and transferring, to the server processing system, content request data indicative of a user requesting content by interacting with the content request interface; and. in a server processing system: receiving, from the user processing system, the content request data; and transferring message data indicative of the requested content to the content receiving device.
  • a system of requesting content to be transferred to a content receiving device wherein the system includes a server processing system in data communication with a user processing system, wherein: the user processing system is configured to: receive interface data representing a content request interface; display, using the interface data, the content request interface; and transfer, to the server processing system, content request data indicative of a user requesting content by interacting with the content request interface; and the server processing system is configured to: receive, from the user processing system, the content request data; transfer message data indicative of the requested content to the content receiving device.
  • Figure IA illustrates a functional block diagram of an example processing system that can be utilised to embody or give effect to a particular embodiment
  • Figure IB illustrates an example system for transferring content to a content receiving device
  • Figure 1C illustrates another example system for transferring content to a content receiving device
  • Figure 2A illustrates an example system configured to transfer content to a mobile telecommunications device
  • Figure 2B illustrates a more detailed example of a system configured to transfer content to a mobile telecommunications device
  • Figure 3 illustrates flow chart representing an example method of enabling transfer of content
  • Figure 4 illustrates a flow chart representing an example method of transferring content to a mobile telecommunications device
  • Figure 5 illustrates an example web page including a content request button
  • Figure 6A illustrates the web page of Figure 5 in a state after the content request button has been selected by a user at the client processing system
  • Figure 6B illustrates the web page of Figure 5 in a state after the content request button has been selected by a user at the client processing system, wherein the web page includes a preview of content to be transferred;
  • Figure 7 A illustrates a modular block diagram illustrating an example of the server processing system
  • Figure 7B illustrates a modular block diagram illustrating an example of the content transfer management module
  • Figure 8 illustrates a flow chart representing an example of a method of enabling the transfer of content to a mobile telecommunications device
  • Figure 9 illustrates an example of a content transfer management interface including a plurality of content transfers
  • Figure 10 illustrates an example of the content transfer management interface when a new content transfer is to be created
  • Figure 11 illustrates an example of enabling data which is generated and transferred to the content provider processing system upon creation of a new content transfer
  • Figure 12 illustrates an example of the content transfer management interface when an existing content transfer is to be edited
  • Figure 13 illustrates an example of an advertising interface
  • Figure 14 illustrates an example of a graphical display of a performance of an advertisement
  • Figure 15 illustrates a further example of a content transfer management interface
  • Figure 16 illustrates a further flow chart representing an example method of enabling transfer of content
  • Figure 17 illustrates an example of first data
  • Figure 18 illustrates an example of first data where the content and parameters are encrypted
  • Figure 19 illustrates a content request interface including advertising content
  • Figure 20 illustrates a further example of a content transfer management interface including an example of first data which can be copied to the content provider web server.
  • the processing system 100 generally includes at least one processor 102, or processing unit or plurality of processors, memory 104, at least one input device 106 and at least one output device 108, coupled together via a bus or group of buses 110.
  • input device 106 and output device 108 could be the same device.
  • An interface 1 12 can also be provided for coupling the processing system 100 to one or more peripheral devices, for example interface 112 could be a PCI card or PC card.
  • At least one storage device 114 which houses at least one database 116 can also be provided.
  • the memory 104 can be any form of memory device, for example, volatile or non-volatile memory, solid state storage devices, magnetic devices, etc.
  • the processor 102 could include more than one distinct processing device, for example to handle different functions within the processing system 100.
  • Input device 106 receives input data 118 and can include, for example, a keyboard, a pointer device such as a pen-like device or a mouse, audio receiving device for voice controlled activation such as a microphone, data receiver or antenna such as a modem or wireless data adaptor, data acquisition card, etc.
  • Input data 118 could come from different sources, for example keyboard instructions in conjunction with data received via a network.
  • Output device 108 produces or generates output data 120 and can include, for example, a display device or monitor in which case output data 120 is visual, a printer in which case output data 120 is printed, a port for example a USB port, a peripheral component adaptor, a data transmitter or antenna such as a modem or wireless network adaptor, etc.
  • Output data 120 could be distinct and derived from different output devices, for example a visual display on a monitor in conjunction with data transmitted to a network.
  • a user could view data output, or an interpretation of the data output, on, for example, a monitor or using a printer.
  • the storage device 114 can be any form of data or information storage means, for example, volatile or non-volatile memory, solid state storage devices, magnetic devices, etc.
  • the processing system 100 is adapted to allow data or information to be stored in and/or retrieved from, via wired or wireless communication means, the at least one database 116.
  • the interface 112 may allow wired and/or wireless communication between the processing unit 102 and peripheral components that may serve a specialised purpose.
  • the processor 102 receives instructions as input data 118 via input device 106 and can display processed results or other output to a user by utilising output device 108. More than one input device 106 and/or output device 108 can be provided. It should be appreciated that the processing system 100 may be any form of terminal, server, specialised hardware, or the like.
  • the processing system 100 may be a part of a networked communications system.
  • Processing system 100 could connect to network, for example the Internet or a WAN.
  • Input data 118 and output data 120 could be communicated to other devices via the network.
  • the transfer of information and/or data over the network can be achieved using wired communications means or wireless communications means.
  • a server can facilitate the transfer of data between the network and one or more databases.
  • a server and one or more databases provide an example of an information source.
  • the server may transfer, to the processing system 100, data indicative of a computer program which when executed in the processing system 100 performs the method described herein.
  • FIG. IB there is shown an example of a system 150 to transfer content to a content receiving device.
  • the system includes a server processing system 220 in data communication with a user processing system 210.
  • the server processing system 220 receives from the user processing system 210 a request 215 for content.
  • the server processing system 220 obtains the content requested.
  • the server processing system 220 then transfers message data 235 indicative of the content to the content receiving device 240.
  • the system 180 includes the user processing system 210 in data communication with the server processing system 220 and an intermediary processing system 205.
  • the server processing system 220 receives, from the user processing system 210, request data 190, wherein the request data is received upon the user processing system processing first data 202 received from the intermediary processing system 205.
  • the server processing system 220 determines, based at least partially upon the request data 190, if the content can be transferred to the content receiving device 240. In the event of a positive determination the server processing system 220 transfers second data 214 indicative of a content transfer interface to the user processing system 210 for display. Then the server processing system receives, from the user processing system210 and upon user interaction with the content transfer interface, content request data 215 indicative of a request for the content.
  • the server processing system 220 transfers message data 235 indicative of the content to the content receiving device 240.
  • the system 200 includes the user processing system 210 which is operated by, or associated with, a user 211; the intermediary processing system 205 which in one particular, but non-limiting, form is a webserver which hosts a portal 208 in the form of a webpage provided by, or associated with, a content provider 206; a content server processing system 220; a message transfer gateway 230; and a mobile telecommunications device 240 operated by, or associated with, the user 211.
  • the intermediary processing system 205 which in one particular, but non-limiting, form is a webserver which hosts a portal 208 in the form of a webpage provided by, or associated with, a content provider 206; a content server processing system 220; a message transfer gateway 230; and a mobile telecommunications device 240 operated by, or associated with, the user 211.
  • the message transfer gateway 230 can be provided as a Short Message Service gateway, wherein the following examples will be described in relation to the ' implementation.
  • a Short Message Service (herein referred to as an SMS) is a means of sending short messages to and from mobile telecommunication devices such as mobile telephones. This service generally allows messages to be sent up to one hundred and sixty characters.
  • SMS can also be used herein to refer to text messages which are sent using this service.
  • the user processing system 210, the web server processing system 205, the content server processing system 220 and the SMS gateway 230 are in data communication via a network such as the Internet.
  • the SMS gateway 230 is in data communication with the mobile telecommunications device 240 via a network such as the Internet and a mobile telephone network.
  • a user 211 using the user processing system 210 requests 207 a webpage 208 associated with the content provider 206 to be displayed using a browser on the user's processing system 210.
  • Other means of displaying the content provider's webpage 208 may be used.
  • the content provider's web server 205 transfers data indicative of the webpage 208 to the user processing system 210 to be displayed to the user 211.
  • the webpage 208 can display a content request interface 501, as shown in Figures 5 and 6.
  • the user 211 then interacts with the content request interface 501 using the user processing system 210 to cause content request data 215 to be transferred to the content server processing system 220.
  • the content server processing system 220 then obtains the corresponding content 250, and generates message data 225 indicative of the obtained content 250 and a mobile telecommunications device number associated with the mobile telecommunications device 240 which is transferred to the SMS gateway 230.
  • the SMS gateway 230 uses the SMS request data 225 to transfer message data, in one form, an SMS 235 indicative of the content 250, to the mobile telecommunications device 240 associated with the mobile telecommunication device number.
  • This system 200, and below described method 300, 400 advantageously enable relatively quick retrieval and accurate recordal of content 250. Furthermore, due to the rapid adoption of mobile telephones in society, the user 211 has an electronic record of the content which is easy to retrieve and display.
  • FIG. 2B there is shown a more detailed example of a system 299 to enable transfer of content 250 to a mobile telecommunications device 240.
  • the content provider 206 uses a content provider processing system 204 to interact with a content transfer management system controlled by the content server processing system 220. More detailed description of the operation of system 299 will be described below in relation to an example method illustrated in Figure 8.
  • the method 300 includes receiving input data 201, indicative of the content 250 from the content provider processing system 204.
  • the method 300 includes generating, using the input data, first data 202 to enable a request 215 for content 250 to be transferred to the mobile telecommunications device 240.
  • the first data 202 is computer interpretable code which can be included in source code of a web page to enable a request 215 to be selected by the user 211.
  • the method 300 includes, transferring the first data 202 to the content provider processing system 204.
  • the method 400 includes the content server processing system 220 receiving, from the user processing system 210, a request 215 for content 250 to be transferred to a user's mobile telecommunications device 240.
  • the method 400 includes the content server processing system 220 obtaining the requested content 250.
  • the method 400 includes the content server processing system 220 transferring an SMS 235 indicative of the requested content 250 to the user's mobile telecommunications device 240.
  • the content provider webpage 208 includes a content request interface 501 which the user 211 can interact with using the input device of the user processing system 210 to request content 250 to be transferred to the mobile telecommunications device 240 associated with the user 211.
  • the content request interface 501 can include an interactive element in the form of a content request button 510, 520 including a visual indicia which indicates that content can be requested and transferred to the user's mobile telecommunications device 240.
  • the user processing system 210 may dynamically display a second content request interface 502 which requests the user to provide the mobile telecommunications device number associated with the mobile telecommunications device 240 in an input field 525, as shown in Figure 6A.
  • the second content request interface 502 may also display a preview of a representation of the content 540 which can be transferred to the mobile telecommunications device 240, as displayed in Figure 6B.
  • the user 211 can interact with one or more interactive elements 530 to confirm the request 215 for content 250.
  • content request data 215 is transferred to the content server processing system 220 requesting the appropriate content 250 to be transferred to the user's mobile telecommunications device 240.
  • the content server processing system 220 can include a content transfer management module 710, a content request module 720 and a storage module 730.
  • the content transfer management module 710 is configured to provide a management interface 900, generally via a series of web pages, allowing one or more content providers 206 to manage one or more content transfers 910 respectively.
  • the content transfer management interface 900 is generally provided as one or more web pages which are transferred from the content server processing system 220 to a content provider processing system 204, allowing the content provider 206 to manage the one or more content transfers 910, as will be discussed in more detail below.
  • the content request module 720 is configured to receive the one or more content requests 215 from the one or more user processing systems 210, and to obtain and transfer the requested content 250 to the specified mobile telecommunications device 240.
  • the storage module 730 generally stores data associated with the one or more content transfers 910 for the one or more content providers 206.
  • the storage module 730 may generally be provided in the form of a database.
  • the storage module may store the content associated with each content transfer.
  • the content request module 720 interacts with the storage module to retrieve the content from the storage module 730. However, as will be discussed, this is optional as the content may be stored in the first data.
  • the content transfer management module 710 includes a registration and login module 740, a creation module 750, an editing module 760, a pause module 770, and a deletion module 780, wherein each module can be used to manage one or more content transfers 910 for a content provider 206.
  • Each module can be implemented using software.
  • the registration and login module 740 is configured to allow content providers 206 the functionality to create a content provider account, using the registration and login module 740, such that content transfers 910 can be created and managed by the content provider 206.
  • the content provider 206 registers with the content server processing system 220 via a web page provided via the Internet.
  • the content provider 206 nominates a username and password which is recorded by the content server processing system 220 and in response an email is sent by the content server processing system 220 to the content provider 206 which includes an embedded URL which the content provider 206 can select to enable the content provider account.
  • other means of registering the content provider can additionally or alternatively be implemented.
  • the content provider 206 can log into the content transfer management system via a login web page, wherein the registration and login module 740 is configured to authenticate the content provider, wherein upon successful authentication of the content provider's username and password, the content provider 206 is displayed a content transfer management interface 900, as shown in Figure 9.
  • the creation module 750 is configured to allow the content provider 206 to generate a new content transfer 910, wherein the user specifies 201 the content to be transferred to a specified mobile telecommunications device. Furthermore, the creation module 750 generates first data 202 to enable a content request interface to be displayed within the content provider's webpage 208. The creation module 750 will be described in more detail in relation to Figure 10 and 11.
  • the editing module 760 is configured to retrieve existing data associated with an existing content transfer 910 and to update particular data associated with the respective content transfer 910.
  • the editing module 760 will be explained in more detail below in relation to Figure 12.
  • the pause module 770 is configured to receive input from the content provider 206 indicating that one or more of the content transfers 910 are to be paused.
  • the selection of pausing one or more content transfers 910 disables data being transferred from the content server processing system 220 to the SMS gateway 230 for the relevant paused content transfers 910.
  • second data 214 may be transferred to the user processing system 210 including a disabled interface such that the user 211 cannot interact with the content request interface 501.
  • data such as a webpage, indicating that content transfer 910 has been paused may be transferred back to the user processing system 210 to indicate to the user 211 that the content request 215 cannot currently be performed.
  • the deletion module 780 is configured to delete the record associated with each selected content transfer 910.
  • the deletion module 780 interacts with the database containing the relevant record for the one or more selected content transfers 910 such that the record is deleted from the storage module 730.
  • the deletion module 850 can be configured to confirm with the relevant content provider 206 that the relevant records associated with the one or more selected content transfers 910 have been deleted.
  • FIG 805 there is shown a more detailed flowchart representing a method 800 of enabling transfer of content.
  • the method 800 includes the content provider 206 registering with the content transfer system.
  • the content provider 206 generally visits a registration web page hosted by the content server processing system 220, or associated processing system, to register.
  • the registration and login module 740 records a username and password, which is generally encrypted, in the storage module 730.
  • the content provider 206 logs into the content transfer management system. Generally, this is performed using a login webpage which is hosted by the content server processing system 220, or associated processing system. The content provider 206 uses the username and password to log into the content transfer management system. Upon successful authentication of the content provider 206 by the registration and login module
  • the content server processing system 220 transfers data indicative of the content transfer management interface 900 to the content provider processing system 204.
  • the content provider 206 requests generation of a new content transfer 910.
  • data indicative of the generation request is transferred to the content server processing system, wherein in response the content server processing system 220 transfers data indicative of a new content transfer window 1000 for display at the content provider processing system 204.
  • the content provider 206 generates the new content transfer 910.
  • the content provider 206 defines properties associated with the new content transfer 910.
  • the content provider 206 defines the content 250 which is to be transferred to the mobile telecommunications device 240, as will be discussed in more detail in relation to Figure 10.
  • the content provider 206 defines a network address, specifically a uniform resource locator (URL), which the content request interface 501 is to be displayed for the content transfer 910.
  • URL uniform resource locator
  • the content server processing system 220 stores, in the storage module 730 which is generally a content transfer table of a database, a record regarding the new content transfer 910 and a unique content transfer identity which identifies the new content transfer 910 from other content transfers 910. Furthermore, the content server processing system 220 stores an association between the newly created content transfer 910 and the respective content provider 206.
  • the content server processing system 220 generates first data 202.
  • the first data 202 is indicative of the content transfer identity uniquely identifying the content requested.
  • the first data 202 when interpreted by a user processing system browser, causes a content provider processing system identity to be transferred to the content server processing system.
  • the content provider processing system identity is a network address of the webpage 208, such as a URL, which the first data 202 is included therein to be transferred to the content server processing system 220.
  • the first data 202 attempts to overcome problems associated with an authorised content provider 206 copying the first data onto a different webpage 208 which the content transfer is not registered for, or other similar problems.
  • the content server processing system 220 transfers the first data 202 to the content provider processing system 204.
  • the content provider 206 copies the first data 202 to the corresponding webpage 208 hosted at the content provider web server 205 which the respective content transfer 910 is registered for.
  • the source code of the webpage 208 includes the first data 202.
  • the user 211 at the user processing system 210 requests 207 the display of the content provider webpage 208 including the first data 202.
  • the user 211 uses a webpage browser to request display of the webpage 208.
  • the content provider web server 205 transfers data indicative of the webpage 208 to the user processing system 210.
  • the web browser interprets the first data 202 included in the webpage 208.
  • the web browser transfers request data 213 requesting the second data to the content server processing system 220.
  • the request data 213 is indicative of the network address of the webpage 208 displayed, and the content transfer identity which is indicated by the first data 202.
  • the network address is known as the HTTP referrer indicating the URL of the webpage 208 which included the first data 202.
  • the content server processing system 220 uses the request data 213 to determine if the request for content can be performed. This can include determining if the request for content is authorised or valid. In particular, the content server processing system 220 uses the content transfer identity to retrieve, from the storage module 730, the record for the relevant content transfer 910. If no content transfer 910 exists corresponding to the content transfer identity indicated in the request, the request 213 is invalid, and subsequently data is transferred to the user processing system 210 disabling the content request interface 501.
  • the content server processing system 220 determines whether the content request is authorised by determining if the HTTP referrer corresponds to the network address which the content transfer 910 is registered. If the HTTP referrer does not correspond, then this may indicate that the first data 202 is located at the wrong web page 208 or may have been stolen/copied from the registered webpage 208. Therefore, again the content request interface 501 is disabled or second data 214 is not forwarded to the user processing system.
  • the content server processing system 220 determines whether there is a valid content provider account and correspondingly that the content provider 206 has associated credit to complete the content transfer 910. In the event that the there is not a valid content provider account and/or credit associated with the content transfer 910, again the content request interface 501 is disabled as above.
  • the method includes the content server processing system 220 generating and transferring second data 214 to the user processing system 210.
  • the content server processing system 220 retrieves data enabling the display of the content request interface 501.
  • the second data 214 may be indicative of the content transfer identity and the content request interface 501 such as the content request button/icon 510, 520.
  • the method includes the web browser interpreting the second data 214 and displaying the webpage 208 including the content request interface 501, as shown in Figure 5.
  • the user 211 interacts with the content request interface 501, generally by selecting the content request button 510, 520 using an input device of the user processing system 210.
  • the web browser dynamically displays a second portion of the content request interface 502 which overlaps the first content request interface 501 requesting input of the user's mobile telephone number, as shown in Figures 6 A and 6B.
  • the user 211 generally inputs the user's mobile telephone number using the keyboard of the user processing system 210 and selects the send button 530 as shown in Figures 6A and 6B.
  • the user processing system 210 transfers content request data 215 to the content server processing system 220.
  • the content request data 215 is indicative of the unique content transfer identity, the network address of the webpage and the mobile telephone number input by the user.
  • step 885 the content server processing system 220 determines, using the content request data 215, if the content request can be performed. Generally, this is similar to step 860 wherein one or more of the above-mentioned comparisons can be performed for precaution. For instance, during the time that step 865 and 885 are performed, the relevant content provider 206 may have had a number of content transfers 910 being performed, thus reducing the associated credit available for the content provider 206 to service content transfers. Thus, step 885 is performed to ensure that the content transfer 910 can be performed, and in the event that the content transfer 910 can be performed, the method continues to step 890.
  • the method includes the content server processing system 220 retrieving the relevant content 250 for the content transfer 910.
  • the method includes the content server processing system 220 generating an SMS request 225 using the retrieved content 250.
  • the SMS request 225 is generally indicative of the retrieved content 250 and the mobile telephone number. However, other properties associated with the content transfer can also be included in the SMS request 225 which are to be transferred to the mobile telecommunications device 240 via an SMS 235.
  • the method includes the content server processing system 220 transferring the SMS request 225 to the SMS gateway 230.
  • the SMS gateway 230 transfers the SMS 235 to the specified mobile telecommunications device 240 using the SMS request 225. Subsequently, the mobile telecommunications device 240 receives the requested content 250 via SMS 235.
  • FIG. 9 there is shown an example of the content transfer management interface 900 displaying current content transfers 910 which are associated with the content provider 206. Furthermore, for each content transfer 910 there is displayed an associated network address which the content request button 510, 520 is located, the date which the content transfer 910 was created, a time when the last content transfer 910 was requested, and the number of content transfers 910 that have been requested.
  • the content transfer management interface 900 includes a plurality of buttons including a button 920 enabling the content provider to create a new content transfer using the creation module 750, a button 930 to edit an existing content transfer using the editing module 760, a button 940 to pause an existing content transfer using the pause module 770, and a button 950 to delete an existing content transfer using the deletion module 780.
  • the content transfer management interface 900 displays, using the creation module 750, a window 1000 including a number of input fields 1010, 1020, 1030, 1035, 1040, 1050 requesting information regarding the new content transfer, as shown in Figure 10.
  • the new content transfer window 1000 includes a name field 1010 which the content transfer 910 can be identified by, a content provider field 1020 which allows the content provider 206 to identify themselves to the user 211, a message field 1030 which allows the content provider to input and/or format the content 250 which is to be transferred upon request, a webpage address field 1035 which allows the content provider 206 to indicate the network location which the content request interface 501 is to be located, and a tag field 1040 which allows the content provider 206 to classify and group similar content transfers 910 together. Additionally, the new content transfer window 1000 further includes a radio button region 1050 which allows the content provider 206 to select an appropriate content request interface 501 such as a content request button/icon to be displayed on the content provider website 208.
  • a radio button region 1050 which allows the content provider 206 to select an appropriate content request interface 501 such as a content request button/icon to be displayed on the content provider website 208.
  • a save button 1060 can be selected by the content provider 206.
  • the input data 201 is transferred from the content provider processing system to the content server processing system 220, wherein the creation module 750 stores a record regarding the newly created content transfer 910 in the storage module 730.
  • the creation module 750 then generates first data 202, as shown in Figure 11, which is transferred to the content provider processing system 205 to enable the content transfer interface 910 to be requested upon a user browser interpretation of the first data 1100.
  • the first data 1100 is provided in the form of source code 1100, in one form HTML and javascript, which the content provider 206 can copy and include in the source code for the relevant web page 208 stored on the content provider web server 205.
  • a request 213 is transferred to the content server processing system 220 requesting the content request interface 501.
  • the content request interface 501 is transferred to the user processing system 210 for display, thus enabling the user to request content.
  • a clipboard button 1120 is provided which the user 211 can select to copy the first data 202.
  • Figure 11 also shows a preview content region 1110 which displays to the user 211 the format of the content 250 when received via SMS 235.
  • a record is retrieved, using the editing module 760.
  • the editing window 1200 is transferred to the content provider's processing system 204 including input fields populated with the retrieved data for the indicated content transfer 910.
  • the content provider 206 can then modify the populated input fields and save the edited data for the respective content transfer by transferring the edited data back to the content server processing system 220 for storage by the editing module 760 in the database.
  • Optional embodiments of the present invention may also be said to broadly consist in the parts, elements and features referred to or indicated herein, individually or collectively, in any or all combinations of two or more of the parts, elements or features, and wherein specific integers are mentioned herein which have known equivalents in the art to which the invention relates, such known equivalents are deemed to be incorporated herein as if individually set forth.
  • the content server processing system 220 can include the SMS gateway 230.
  • the SMS gateway 230 is a separate processing system which is in data communication with the content server processing system 220 via a network, such as the Internet.
  • the content provider web server 205 and the content provider processing system 204 can be the same processing system or two separate processing systems.
  • the user 211 at the user processing system 210 registers to use the content transfer system with the content server processing system 220. This may include the user 211 visiting a registration website hosted by the content server processing system 220, wherein the user 211 provides the mobile telephone number.
  • the content server processing system 220 records the mobile telephone number and a user processing system identifier uniquely associated with the user processing system 210.
  • the user processing system 210 stores data indicative of the unique user processing system identifier.
  • the user 211 selects the content retrieval button 510, 520 using a single click of the mouse. Due to the content server processing system 220 having data indicative of the user's mobile phone number due to the user 211 performing a registration process, the input box 525 and send button 530 are no longer required to be displayed using the user processing system 210. In response to the user 211 selecting the content request button 510, 520, the user processing system 210 generates the content request 215 indicative of the user processing system identifier.
  • the user processing system identifier is used by the content server processing system 220 to retrieve the mobile phone number, allowing the content 250 to be transferred to the mobile telephone 240 without requiring the user 211 to input their mobile telephone number.
  • This feature significantly simplifies the process for the user to retrieve content 250. Furthermore, this feature also overcomes problems associated with the user 211 inputting the incorrect mobile phone number. The user 211 may use the registration web page to alter the mobile phone number.
  • the content provider 206 may be charged for the content transfer 910.
  • the content provider 206 may purchase credit in order for content transfers 910 to be enabled using the content server processing system 220, such that each time content 250 is transferred via an SMS 235 for a particular website 208, the content server processing system 220 decrements the number of remaining content transfers available.
  • the content provider 206 is debited for each content transfer 910 which is performed.
  • the content provider 206 may be requested to provide financial account details, such as a credit card number, or enable a direct debit function, such that when one or more content requests 910 are performed, the content provider is debited for the content transfer 910.
  • the user 211 requesting the content 250, or the user associated with mobile telecommunications device 240 is charged for the content transfer 910.
  • the user may be charged upon the transfer of the content 250.
  • the user 211 may also purchase credit in order for content transfer 910 to be enabled.
  • the user 211 may be assigned identification information, such as a username and password which the user 211 is required to input to request content 250 to be transferred.
  • the content server processing system 220 authenticates the username and password prior to transferring content 250 to the mobile telecommunications device 240.
  • an advertiser may fund the content transfer 910, wherein each content transfer 910 includes data indicative of an advertisement.
  • the content server processing system 220 modifies the message containing the requested content 250 such that the content 250 further includes an advertisement, wherein the associated advertiser funds the content transfer 910.
  • the content server processing system 220 includes records which associate one or more content providers 206 with one or more relevant advertisements, such that when content 250 is requested, a relevant advertisement is selected using the associated record and the advertisement is concatenated to the content 250 which is to be transferred to the user's mobile telecommunications device 240.
  • an advertiser is able to log into an advertiser website hosted by the content server processing system, wherein the advertiser is able to setup one or more advertisements 1310 to at least partially fund one or more content transfers.
  • an advertisement record is stored in an advertiser table of the database 730 at the content server processing system.
  • Each advertisement record stored is indicative of advertising content 1314, an advertisement identity 1312 to uniquely identify the advertisement, the content transfer identity of the particular content transfer which the advertising content is to be appended thereto, optionally an advertising campaign identity 1320 to uniquely identify an advertising campaign which the advertisement is part thereof, and an advertiser identity to uniquely identify the advertiser associated with the advertisement.
  • the advertising identity is used by the content server processing system when attempting to execute a content transfer, wherein the advertising content 1314 is included in the content which is transferred to the user.
  • an advertising interface 1300 which is displayed to the advertiser upon correctly logging into the advertising webpage.
  • the advertiser may have multiple advertising campaigns 1320, wherein each advertising campaign can group multiple advertisements 1310 together.
  • Each advertisement for a particular advertising campaign is associated with the same advertising campaign identity 1322.
  • Each advertisement is associated with a unique advertisement identity, uniquely identifying the advertisement from other advertisements of the respective advertising campaign.
  • the advertising interface 1300 displays additional information.
  • information displayed by the advertising interface 1300 can include at least a portion of the advertisement content 1314 for each advertisement 1310, a date and time when each advertisement was created 1316, the number of instances advertising content for each advertisement had been transferred 1319, and the most recent instance that advertising content has been transferred 1318.
  • a graphical display 1400 can be provided to the advertiser indicating the performance of a particular advertisement associated with a particular content transfer.
  • the graphical display 1400 may be a frequency diagram indicating, for particular points or periods of time, the number of instances a content transfer interface has been displayed to a user 1410, and a number of instances that a content transfer has been executed 1415.
  • This graphical display allows an advertiser to assess whether the content transfer associated with the advertisement has been successful. Additional information 1420 may be displayed regarding a plurality of content transfers having the highest frequency of executions. The advertiser is further able to edit the amount of funding provided toward each content transfer.
  • an advertiser can interact with the advertising interface 1300 to enable one or more advertisements or advertising campaigns to be automatically targeted toward particular content requesting users. Therefore, in some instances, the advertiser does not necessarily have to indicate specific content transfers which are to be at least partially funded, but rather the advertiser indicates particular requirements for which a content request can be at least partially funded, and thus the content server dynamically selects a content transfer to be at least partially funded by the respective advertiser
  • an advertiser can define and store, at the content server, one or more advertising matching rules which are executed to determine content transfers or a group of content transfers, generally associated together via a tag and herein referred to as a "content transfer campaign", that are to be at least partially funded.
  • Example of rules can be based upon the geographic location of the user receiving the content, the domain or URL which the content request interface is being displayed upon, or keywords.
  • the content server receives content request data associated with a particular content transfer, the content request can be analysed by the content server to determine these requirements, and thus if the requirements are successfully satisfied, advertising content from the advertiser is appended to the content transfer to at least partially fund the content transfer.
  • the server can perform generative grammar linguistics in order to identify the most related advertisement available for a specifically requested content transfer. Additionally, the amount of funding which an advertiser is willing to pay per appended advertisement may also be taken into account when dynamically selecting the advertisement to be appended to a content transfer.
  • an advertiser may be willing to pay more funding than it costs to execute the content transfer. For example, it may costs 20 cents to execute a content transfer. However, an advertiser may be willing to pay 30 cents for each content transfer. Therefore, in this instance, the content provider may receive an income from the advertising funds attributed to particular content transfers.
  • a further example of a content transfer management interface 1500 is shown which is displayable to the content provider.
  • some of the content transfers may be associated with an advertisement 1510 to help fund the content transfer.
  • Similar information is displayed to the content provider to that of the advertiser, wherein the information displayed in the content transfer management interface can include an advertiser campaign identity 1520 for a respective content transfer, the number of advertisements associated with the advertising campaign, the date and time that the advertisement was created, when the last content transfer occurred, and how many content transfers have been performed.
  • a content provider may have the ability to allow an advertiser to append an advertisement to all content transfers, to at least some content transfers for which have a content transfer interface displayed on a particular domain, or for selected content transfers which the content provider selects. If multiple advertisements are associated with the same content transfer, then an advertisement is selected by the content server processing system at random or sequentially.
  • the content provider may indicate that any advertiser can append advertisement to the content transfers being executed.
  • the content provider may define and store, at the content server, one or more rules to define specific advertisements which are considered acceptable to be appended to the content transfer.
  • the content provider can use the content transfer management interface to peruse the number of advertisements being sent and can also peruse each specific advertisements that have been sent in the past.
  • a content provider may be able to indicate via the content transfer management interface that the one or more particular transfers are available for advertising.
  • the content server processing system may host a webpage which displays an auction of one or more content transfer which are available to be sponsored by an advertiser.
  • a potential advertiser is able to peruse each content transfer which is displayed on the auction webpage, wherein information about the respective content transfer can be reviewed by the potential advertiser.
  • Information which the potential advertiser can review can include the URL of the webpage which the content transfer interface is to be displayed upon, the content which is being transferred, the number of instances which the content transfer has been performed over a period of time, and/or the graphical display discussed above.
  • the potential advertiser is interested in placing a bid to sponsor the content transfer, the potential advertiser can submit a bid, wherein a bid value, a bidder identity uniquely identifying the bidder, and an auction identity uniquely identifying the auction of the respective content transfer, is recorded by the content server processing system. Similar to typical auction systems, once the respective auction expires, the highest bidding advertiser is awarded the right to. append an advertising content to the respective content transfer.
  • the content server processing system reviews the respective content transfer record in the content transfer table to determine if advertising content needs to be appended to the content transfer. If so, the content transfer record can include the advertisement identity which can be used to query the advertiser table to retrieve the respective advertising content which is then included, typically appended, to the content to be transferred to the user. The advertiser may then be debited at least partially for funding the content transfer.
  • the advertising content may be text, but other forms of media are also possible such as images, audio, animation, a file, or the like.
  • the content provider 206 may transfer, to the content server processing system 220, source code data indicative of the source code for the content provider web page 208.
  • the content provider may also indicate a desired location or region which the content request button 510, 520 is to be located on the web page.
  • the content server processing system 220 modifies the source code with the first data 202 according to the indicated desired location or region such that upon viewing the website using the modified source code, the content request button 510, 520 is located in the desired position or region.
  • the modified source code can be previewed by the content provider 206 prior to being transferred back to the content provider processing system 204.
  • the content provider 206 may transfer a plurality of files indicative of source code for a plurality of web pages 208, wherein the content server processing system 220 performs a batch enablement of the web pages 208.
  • the content provider 206 may specify that the first data 202 is to be provided at a particular region or location on each webpage 208. This feature produces a consistent layout of the content request interface 501 on each of the content provider's web pages 208.
  • the content transfer management interface 900 may also include a search button 960 and input search field 970 which allows a content provider 206 to perform a search of multiple content transfers 910.
  • the input field 970 provides a pull-down menu providing a number of tags which have been used to classify content transfers 910.
  • the plurality of content transfers 910 is searched by the content server processing system 220 to determine one or more content transfers 910 which satisfy the search criteria of the specified tag.
  • the server processing system 220 can include a use monitoring module which is configured to monitor the amount of content transfers 910 being requested by one or more users 211.
  • the use monitoring module may be configured to record the number of content transfers 910 requested for a particular mobile telecommunications device 240 associated with a particular mobile telecommunications device number.
  • the use monitoring module uses the stored records to determine whether the specified mobile telecommunications device requesting the content 250 has equalled or exceeded the threshold for a period of time. In this instance, the content transfer would not be performed.
  • the IP address of the user processing system may additionally or alternatively be recorded for each received content request.
  • the use monitoring module can use the IP address to determine how many instances in a particular period of time a content transfer has been requested, and then if this equals or exceeds a threshold, the content transfer is not performed. As described above, the use monitoring module can be used to reduced misuse of requesting content transfers.
  • the use monitoring module can be configured to record the number of successfully completed requests 215 for at least some of the content transfers 910.
  • the use monitoring module is configured to record, in the storage module 730, the frequency of successfully completed requests for each content transfer 910.
  • the content provider 206 can use the content transfer management interface 900 to request an indication of the frequency which content 250 has been requested and transferred for a particular content transfer 910.
  • first data 202 being transferred, from the content server processing system, including first data 202 and second data 214
  • first data 202 when interpreted, displays the content request interface 501.
  • the user's browser interface interprets the first enabling 202 due to attempting to display the webpage 208, the content request interface 501 is displayed without requiring requesting second data 214 from the content server processing system 220.
  • the content server processing system 220 uses the HTTP referrer, or the like, to determine the location of the web page 208, and if the determined web page 208 is not registered for the corresponding content transfer 910, the content transfer 910 is not performed. In this manner, although the content request interface 501 could be displayed on another webpage by another content provider 206 copying the source code, the method and system would still have security measures.
  • the method 1600 includes the content provider requesting generation of a new content transfer.
  • the method includes the content provider inputting the content to be transferred and one or more parameters which are used to control the display of the content transfer interface and/or the execution of the content transfer.
  • the one or more parameters can include one or more tags to be associated with the content transfer, a sender identifier indicating whom is sending content transfer, a label to be displayed upon the content transfer interface, and one or more various visual options, such as the icon to be displayed, to vary the display of the content transfer interface.
  • the method includes the content server generating first data indicative of the message, the one or more parameters of the content transfer, and content transfer identity, and a URL for receiving the request for the content transfer.
  • first data 1790 can be provided as a piece of javascript code which includes a URL 1791 which is formatted to submit the content transfer identity 1792 using the GET html method, upon interpretation, to the content server.
  • the first data 1790 includes the content to be transferred and various other parameters 1793.
  • a window 2000 of the content transfer management interface can be used by the user to transfer instructions to the content server to generate the first data 1790 and to receive the first data via the window 2000 of the content transfer management interface.
  • the server is configured, upon receiving the input from the content provider, to encrypt a portion of the received input, wherein the first data includes an encrypted portion 1893 as shown in Figure 18.
  • the content and the various parameters can be encrypted, wherein the first data includes an encrypted string 1893 which represents the content and the various parameters 1793 of the content transfer.
  • Steps 1620 to 1635 of method 1600 are performed similarly to steps 835 to 850 of method 800.
  • the method includes the user processing system transferring request data to the content server, wherein the encrypted content and other parameters are transferred to the server for decrypting.
  • the method includes the server using the URL which the first data is located and/or the beam identity to determine if the request is valid. For example, if the first data is copied by an unauthorised entity to another web server, a security check can be performed by the content server to ensure that an unauthorised content transfer is not executed. If the request is valid, the method proceeds to step 1650.
  • the method includes the content server using the content transfer identity appended to the URL included in the first data to determine the content provider identity.
  • the content server checks to determine if the content transfer can be performed. This may include determining if the content transfer has funds or sponsorship to pay for the content transfer if required, and/or determining if the content provider has paused the transfer of this particular content transfer. In the event that the content transfer can be performed, the method continues to step 1660, otherwise no content transfer interface is displayed by'the user processing system.
  • the method includes the content server generating a decryption key using the content transfer identity and the content provider identity.
  • the method includes decrypting the encrypted string to obtain unencrypted content and one or more parameters.
  • the method includes the server generating second data indicative of the decrypted message, the decrypted parameters, and optionally advertising content.
  • the server uses the content transfer identity and/or the content provider identity to query the database to determine if the respective content transfer is being at least partially funded by an advertiser. In the event that the content transfer is being at least partially funded by an advertiser, the method can include retrieving the advertising content.
  • the advertising content may include textual content and/or graphical content as well as other digital forms of content which can be displayed using a processing system.
  • the advertising content may be advertising such as graphical content 1910 shown in Figure 19 which is displayed upon the content request interface.
  • the advertising content may include an advertisement which is transferred with the content transfer to the content receiving device.
  • the server appends the advertisement to the message to be transferred to the content receiving device, wherein the second data is indicative of the modified message.
  • the second data may also be indicative of an advertising identity uniquely identifying the advertisement and the advertiser.
  • the content server transfers the second data to the user processing system.
  • the content request interface 502 is displayed as shown in Figure 19, wherein the advertising content 1910 is displayed.
  • data is transferred from the user processing system to the content server indicating that the advertising content 1910 has been displayed at a user processing system.
  • the content server records the display of the specific advertisement 1910 such that the advertiser can be informed, via the graphical display 100, of the number of instances an advertisement has been displayed, thereby enabling analysis of the performance of an advertisement.
  • the data transferred back to the content server may be indicative of the advertising identity, thereby uniquely identifying the advertisement.
  • the data may be also indicative of other data such as demographical information (i.e. the country which the user processing).
  • Steps 1680 to 1710 of method 1600 are performed substantially similarly to steps 875 to 897.
  • the content is not retrieved from the content server but rather the content is transferred from the user processing system and received by the content server.
  • encryption of the content and parameters is not essential, as shown by the first data indicated in Figure 17, and thus the content provider can alter the content to be transferred to the user by simply modifying the first data stored at the content provider's web server.
  • the content request data transferred to the content server may additionally be indicative of advertising identity.
  • the first data received by the content provider can be modified by the content provider such that additional interpretable data can be processed by the user processing system.
  • executable or interpretable computer statements can be embedded in the first data which is included in the webpage. This feature allows the content provider to customise the presentation or functionality of the content transfer.
  • the content provider may require one or more database queries to be executed at a content provider database in response to the user processing system receiving the first data.
  • the content provider can embed further computer instructions associated with the first data to cause this function to occur.
  • the first data is transferred to the user processing system generally in the form of source code of a website
  • a part of the source code causes the request data to be sent to the content server processing system
  • another part of the source code referred to as embedded data
  • the additional embedded computer instructions can be in the form of executable computer instructions, an interpretable script, such as Javascript, HTML, or the like.
  • the method includes the content server debiting at least one of the user receiving the SMS, the content provider, and/or one or more advertisers for the executed content transfer.
  • the content request data may be indicative of the advertising identity such as to perform a query on the database to determine how much the advertiser is to be debited.
  • an email can be received by a user including a signature having a content request interface 501 which a recipient can interact with in order for the contact details of the sender of the email to be transferred to the recipient's mobile telecommunications device 240 via an SMS 235.
  • an email application such as Microsoft Outlook, can be used to view the content transfer interface and to select the transfer of the content to the content receiving device.
  • the above examples have illustrated textual content being transferred to the user's mobile telecommunications device 240, it will be appreciated that other forms of data may also be transferred.
  • the above examples have illustrated transferring the content 250 via an SMS 235, other forms of transferring the content 250 may also be implemented such as using EMS (Enhanced Messaging Service), MMS (Multimedia Message Service), email, instant message service, WAP push, premium SMS, i-mode and the like.
  • EMS Enhanced Messaging Service
  • MMS Multimedia Message Service
  • email instant message service
  • WAP push premium SMS
  • i-mode premium SMS
  • the first data and/or the second data may be an interpreted script or executable code. Therefore, this could encompass HTML, Javascript, Coldfusion as well as other scripting and executable code forms.
  • the first data may be in the form of ActionScript code which when interpreted by an Internet browser, an email application, or any other computer application capable of displaying multimedia data, the content transfer interface may be displayed using Adobe Flash.
  • the content transfer interface may be embedded within a graphical element such as a Flash banner.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé, un système, un système de traitement de serveur, un système de traitement d'utilisateur et un produit programme d'ordinateur servant à transférer un contenu dans un dispositif récepteur de contenu. Dans le système de traitement de serveur de contenu, le procédé consiste à recevoir une requête de contenu provenant du système de traitement d'utilisateur ; obtenir le contenu demandé ; transférer des données de message indicatives du contenu demandé au dispositif récepteur de contenu.
PCT/AU2008/000855 2007-06-15 2008-06-13 Transfert de contenu WO2008151383A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US93483207P 2007-06-15 2007-06-15
US60/934,832 2007-06-15
AU2007903235 2007-06-15
AU2007903235A AU2007903235A0 (en) 2007-06-15 Content transfer
US731107P 2007-12-11 2007-12-11
US61/007,311 2007-12-11
AU2007906722 2007-12-11
AU2007906722A AU2007906722A0 (en) 2007-12-11 Content transfer

Publications (1)

Publication Number Publication Date
WO2008151383A1 true WO2008151383A1 (fr) 2008-12-18

Family

ID=40129145

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2008/000855 WO2008151383A1 (fr) 2007-06-15 2008-06-13 Transfert de contenu

Country Status (1)

Country Link
WO (1) WO2008151383A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004030326A2 (fr) * 2002-09-30 2004-04-08 Sony Ericsson Mobile Communications Ab Interrogation et acheminement d'informations de numeros composes depuis un mobile

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004030326A2 (fr) * 2002-09-30 2004-04-08 Sony Ericsson Mobile Communications Ab Interrogation et acheminement d'informations de numeros composes depuis un mobile

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"SMS WebInfo Melbourne Australia", Retrieved from the Internet <URL:http://www.web.archive.org/web/20061028032133/http://www.smswebinfo.com.au> *
HOWSTUFFWORKS: "How Internet Infrastructure Works", Retrieved from the Internet <URL:http://www.web.archive.org/web/20010606174747/http://www.howstuffworks.com/internet-infrastructure.htm> *

Similar Documents

Publication Publication Date Title
CA2803786C (fr) Gestion de confidentialite de publicite
US10679250B2 (en) System and method for sharing content on third-party mobile applications
US20120130801A1 (en) System and method for mobile advertising
TWI478081B (zh) 對使用者的視覺化電子郵件收件箱傳送廣告起始之電子郵件以提供對內容之存取之方法及系統
US20100218128A1 (en) Offer And Incentive Widget-Based System
US20130204957A1 (en) Method, System, and Graphic User Interface for Enabling a Customer to Access a Media File
KR20080099306A (ko) 모바일 장치들을 통해 광고들을 제공하기 위한 시스템
WO2007070404A2 (fr) Modules de documents conteneurs personnalises utilisant des preferences
WO2007070402A2 (fr) Collecte de donnees pour serveur mandataire pour incorporation de module dans un document conteneur
US20080162537A1 (en) Method and system for utilizing profiles
US9978072B2 (en) Computerized system and method for creating a modified version of a digital slide show by creating and inserting a digital content item into the digital slide show
KR20080104398A (ko) 클라이언트 단말기에 사용자의 소비 성향에 따른 정보를제공하는 시스템 및 방법
WO2002097652A1 (fr) Systeme et procede de flux de donnees permissif et de transfert d&#39;application
WO2010045424A2 (fr) Publicité sur un dispositif mobile
US7970889B2 (en) Intelligent subscription builder
US7739199B2 (en) Verification of a testimonial
CN111177597B (zh) 扫码收取电子发票的方法、电子设备及存储介质
US9654431B1 (en) Automated email account verification
US20100077215A1 (en) Method for transmitting information with a semantic acknowledgement of receipt
KR20190098810A (ko) 인터랙티브 메시지 서비스 방법 및 이를 수행하는 서버 장치
WO2008090553A2 (fr) Système et procédé d&#39;envoi de contenu numérique vers un dispositif mobile
WO2008151383A1 (fr) Transfert de contenu
CA2610714C (fr) Pistage de clics approfondi
CN112639780A (zh) 突出强调内容中经标记的交互式组件
US20150112794A1 (en) System And Process For Cloud Based Conversion Tracking

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08756935

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08756935

Country of ref document: EP

Kind code of ref document: A1