EP1139258A1 - Système et méthodes associées pour suivre et controler la distribution de contenu - Google Patents

Système et méthodes associées pour suivre et controler la distribution de contenu Download PDF

Info

Publication number
EP1139258A1
EP1139258A1 EP01302430A EP01302430A EP1139258A1 EP 1139258 A1 EP1139258 A1 EP 1139258A1 EP 01302430 A EP01302430 A EP 01302430A EP 01302430 A EP01302430 A EP 01302430A EP 1139258 A1 EP1139258 A1 EP 1139258A1
Authority
EP
European Patent Office
Prior art keywords
content
document
user
publication
content objects
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.)
Withdrawn
Application number
EP01302430A
Other languages
German (de)
English (en)
Inventor
Donald X Ii Smith
Aloke Gupta
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.)
HP Inc
Original Assignee
Hewlett Packard Co
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
Application filed by Hewlett Packard Co filed Critical Hewlett Packard Co
Publication of EP1139258A1 publication Critical patent/EP1139258A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • a document delivery system comprising one or more virtual sensors, to monitor the distribution of content objects, and a virtual editor to receive content objects from one or more content providers, distribute select content to one or more requesting users, and account to the content providers based, at least in part, on information received from the virtual sensors.
  • the virtual editor when the virtual editor receives content objects (articles, pictures, advertisements, audio content, video content, etc.) from content providers, the content objects are categorized and placed in a virtual wrapper. Subsequently, the virtual editor constructs custom publications using the received, wrapped, content objects for requesting users.
  • the virtual sensors track distribution of the wrapped content objects through the distribution system to the user, ensuring that content objects sent were actually received, and providing the virtual editor with this information. Moreover, the virtual sensors are able to determine how the user interacted with the wrapped content objects, providing this information to the virtual editor as well.
  • virtual editor generates accurate royalty payments to certain content providers (e.g., authors, artists, etc.), while generating accurate bills for other content providers (e.g., advertisers).
  • Fig. 1 illustrates a block diagram of an innovative document delivery system, according to one embodiment of the invention.
  • Document delivery system 10 contains document server 100.
  • document server 100 is operatively coupled via network 200 to a variety of personal computers, printing devices, and other electronic devices, collectively referred to devices 300.
  • document server 100 contains an innovative edit module 120, transmission module 150 and knowledge module 170 to dynamically generate personalized publications from otherwise disparate content objects for requesting users/subscribers.
  • Edit module 120 receives content object input from one or more content providers 50, and/or one or more advertising providers 80 to generate personalized documents based, at least in part, on a number of key criteria including, for example, user interests, seasonality, content provider and advertising provider distribution criteria, and the like.
  • content providers 50 are intended to include all providers of publication content non-inclusive of advertising, while advertising providers 80 provide advertising material. From a financial business model, these two sources of publication material differ significantly (i.e., content providers 50 are paid a royalty from the operator of the document server, while advertisers 80 pay to advertise in the generated publications). From the standpoint of the end-user, however, they both provide content to the publication. Consequently, when used without a reference numeral the general term "content providers" is intended to include both content providers 50 and advertising providers 80. If a distinction is intended, the appropriate reference numeral will be specifically denoted to further specify the source of content.
  • Distribution module 400 is operatively coupled to document server 100 and, as will be discussed, optionally distributes product and/or product subsidies to users based, at least in part, on the source and quantity of content provided to the users.
  • document server 100 is a minicomputer/server, such as an HP 9000 server sold by the Hewlett-Packard Company, although those skilled in the art will appreciate that document server 100 could be any type of other computing or electronic device(s) that performs the functions described herein and still fall within the spirit and scope of the invention.
  • Network 200 is preferably the Internet, although an Intranet, local area network, or other type of public or private network, either wired (e.g., telephone, cable TV, etc.) or wireless (e.g., satellite, radio, cell phone, etc.), could also or additionally be used.
  • Devices 300 are shown in Fig. 1 as being capable of being configured in a wide variety of ways.
  • personal computer 310 is shown connected to printing device 320, which prints document 10320 for user 20320.
  • personal computer 310 is operatively coupled to network 200.
  • printing device 330 which prints document 10330 for user 20330, is operatively coupled to network 200 without an intervening personal computer or other electronic device.
  • Printing device 350 which prints document 10350 for user 20350, is shown connected to electronic device 340, which could be a set top box, television set, palmtop personal digital assistant (PDA) or other type of electronic device that is operatively coupled to network 200.
  • PDA personal digital assistant
  • printing device 370 which prints document 10370 for user 20370, is connected to electronic device 360, which is operatively connected to network 200.
  • the printing devices shown in Fig. 1 could be printers, such as the HP DeskJet 890 printer, HP LaserJet V printer, or other models of printers manufactured by HP or others; so-called “mopiers” or other multi-function printing devices that can print, fax, scan, and/or copy, or any other device capable of transferring information to a printable media such as plain paper, specialty paper, transparencies, or other media capable of tangibly receiving such information and which can be easily carried about by the user.
  • Fig. 13 illustrates a block diagram of edit module 120 incorporating the teachings of the present invention.
  • edit module 120 comprises one or more controllers) 502, an innovative publishing agent 504, an innovative virtual editor 506, memory space 508 and one or more input/output (I/O) interface(s) 510, each coupled as depicted.
  • edit module 120 may well contain one or more application(s) 512 executable by controller(s) 502. It will be appreciated that although depicted as separate and distinct functional entities, one or more functional blocks 502-510 may well be combined into common functional entities.
  • edit module 120 and its constituent elements 502-510 may well be embodied as a series of executable instructions which, when executed by a host processor, implement the features and functions of edit module 120 to be discussed below.
  • Fig. 13 is merely illustrative of the scope and spirit of the claimed invention.
  • controller(s) 502 selectively invoke one or more of the virtual editor 506 to generate a custom document for a requesting and/or subscribing user, or publishing agent 504 to complete the layout and optimize the delivery schedule of such custom documents.
  • Controller(s) 502 may initiate construction and/or delivery of a custom document in response to user interaction with a user interface (e.g., a web page), or to accommodate a user-selected delivery schedule.
  • controller 502 communicates with external applications (e.g., web page) or other elements (e.g., a user profile) via input/output (I/O) interface(s) 510.
  • external applications e.g., web page
  • other elements e.g., a user profile
  • controller 502 provides a user with a user interface with which to request/build a custom document using one or more of applications 512.
  • controller(s) 502 are intended to represent any of a broad range of control devices known in the art including, but not limited to, a programmable logic array (PLA), microprocessor, special purpose controller, application specific integrated circuit (ASIC), and the like.
  • controller(s) 502 are embodied as a series of executable instructions which, when executed, implement the control logic described herein.
  • Memory device 508 and I/O interface(s) 510 are each intended to represent such devices commonly known in the art.
  • I/O interface(s) 510 are intended to include one or more of any of a number of communication interfaces known in the art including, but not limited to, a direct connect communication interface (e.g., a serial interface, a parallel interface, a Universal Serial Bus (USB), an Advanced Graphic Port (AGP), etc.), a local area network interface (e.g., an Ethernet interface, a Token Ring interface, etc.), or a wide area network interface.
  • edit module 120 may communicate with any of a number of external and remote devices using an appropriate one of a plurality of wired and/or wireless I/O interfaces 510.
  • analysis/wrapper agent 522 encapsulates the content object in a wrapper with a unique identifier. It will be appreciated, based on the description to follow, that the encapsulating wrapper enables virtual sensors (not shown) in the document distribution system to accurately track distribution, receipt and disposition of content objects. According to one embodiment, virtual sensors are embedded within printing modules 380 to track distribution, receipt and disposition of encapsulated content objects.
  • the contract administrator 524 is a database driven component that manages all of the contractual obligations of the users (subscribers, content providers, etc.) of the document delivery system.
  • contract administrator 524 maintains royalty calculation and display agreements for select content providers (e.g., artists), the advertising rates for other content providers (e.g., advertisers), subscription information for select users, and the like.
  • contract administrator 524 accesses one or more content provider databases to identify content object distribution, to compute royalty payments, advertising bills and subscription bills for distribution to appropriate users via the transaction agent 526. In this regard, contract administrator 524 ensures that contractual obligations of the document delivery system are adhered to.
  • Transaction agent 526 is the primary interface between the document delivery system and a public/private e-commerce financial system (e.g., the CheckFreeTM financial network offered by CheckFree Corporation). As introduced above, the transaction agent 526 is responsible for executing payments and account credit/debit transactions with user accounts based, at least in part, on the distribution of content objects in accordance with the terms and conditions maintained in contract administrator 524. It should be noted that although depicted as an element of edit module 120, those skilled in the art will appreciate that content manager 518 may well be deployed as an separate and independent functional entity without deviating from the spirit and scope of the present invention.
  • the construction agent 520 of virtual editor 506 extracts content objects to generate a custom document according to one or more key contributors.
  • the key contributors include one or more of a requesting/subscribing user's interests, demographics, seasonality, document server requirements, and content provider usage criteria, and the like.
  • construction agent 520 extracts content objects which are likely to be of interest to a particular user and generates a personalized publication for that user.
  • the construction agent 520 utilizes information received via overt and covert processes of document delivery system 10 to log a user's interaction and disposition of received material, as well as soliciting feedback from the user, to improve the user's satisfaction with subsequent personalized publications.
  • construction agent 520 Information gathered as a result of these overt/covert processes are used by construction agent 520 to update a user profile associated with the user, which is accessed when generating a personalized publication.
  • construction agent 520 performs functions commonly associated with a physical editor of, say, a magazine: publication content decisions, layout and format decisions, advertising and the like, yet it factors in other key information such as personal preferences to generate personalized publications for up to millions of individuals.
  • schedule manager 514 completes the publication layout (e.g., with last minute content objects, or updates to such objects), and schedules delivery of the personalized publication.
  • schedule manager 514 utilizes information from a number of available sources to schedule delivery of the publication. More particularly, schedule manager 514 utilizes information from the user's personal profile, a complexity measure from layout manager 516, and an indication from printing devices associated with the user confirming that an adequate amount and type of media is available for printing the publication. Based, at least in part, on such information, schedule manager 514 works to establish an optimum publication schedule for one or more personalized publications.
  • document delivery server 100 By dynamically acquiring and maintaining accurate information on the distribution, receipt and user disposition of publications at the content object level, document delivery server 100 is able to provide a personalized publication to the user accurately targeting the user's interests, while at the same time providing an accurate accounting to content providers for royalty and/or licensing fee purposes.
  • document delivery system 10 represents a revolutionary advance in the publishing industry, i.e., the ability to provide individually targeted publications on a scale heretofore available only to mass-media enterprises.
  • virtual sensor(s) 35000 are incorporated into printing module 380 throughout document delivery system 10.
  • sensors 35000 are additionally/alternatively deployed in one or more of devices 300 such as, for example, one or more computing devices, one or more printing devices, and/or one or more network infrastructure devices (not shown). It will be appreciated that the amount of information collected is at least loosely dependent upon the number of virtual sensors 35000 deployed throughout document delivery system 10.
  • virtual sensor 35000 comprising a monitoring agent 35002 and a reporting agent 35004, communicatively coupled as depicted.
  • monitoring agent 35002 receives network traffic and analyzes the traffic for distribution of content objects which are traceable back to a particular edit module (e.g., 120) and/or document delivery server (e.g., 100).
  • a particular edit module e.g., 120
  • document delivery server e.g., 100
  • monitoring agent 35002 analyzes the received network traffic for content objects wrapped in trace wrappers (to be described more fully below).
  • the trace wrapper information uniquely identifies the content object and, optionally, the edit module or document delivery server responsible for the distribution of the content object.
  • content provider information database 620 is used by document delivery system to maintain a history of content object distribution, receipt and disposition.
  • contract administrator 524 utilizes information maintained in content provider information database 620 to periodically calculate royalty payments, advertising bills, and subscription bills.
  • Example user profile information and content provider information data structures are illustrated with reference to Figs. 16A and 16B.
  • Fig. 16A graphically illustrates an example user profile data structure 602, suitable for use by the innovative document delivery system.
  • user profile information data structure 602 includes a user_name field 604, a user_id field 606. a contact information field 608, an interest information field 610, a subscription information field 612, a disposition information field 614, and a feedback information field 616.
  • some of the information maintained in user profile data structure 602 is overtly obtained, e.g., by asking the user for such information during a registration period.
  • the user profile data structure 602 is a continuously evolving, continuously improving, set of information reflecting the current interests of the users of the document delivery system.
  • Fig. 16B illustrates an example data structure comprising content provider information, according to one embodiment of the present invention.
  • content provider information data structure 620 includes a content provider name field 622, a content provider ID field 624, a wrapper ID field 626 for each of the content objects provided by the content provider, a rate schedule field 628, a monthly usage field 630 and feedback information field 630.
  • data structures of greater or less complexity may well be utilized to maintain user profile information and/or content provider information without deviating from the spirit and scope of the present invention.
  • FIGs. 2-4 flowcharts detailing the operation of transmission module 150 and a first mode of operation of printing module 380 are presented, according to one embodiment of the invention.
  • the flow diagram shown in the left column is executed by transmission module 150 of document server 100
  • the flow diagram in the right column is executed by printing module 380.
  • the flow diagram for transmission module 150 starts in block 1000
  • the flow diagram for printing module 380 starts in block 2000. Since there is a great deal of interaction between these two flow diagrams, as represented by dashed lines connecting the two columns, the operation of the two flow diagrams will be described simultaneously.
  • block 1100 receives the user profile data sent by block 2100.
  • Block 1200 stores the user profile data, preferably in knowledge module 170. Alternately, the user profile data could be stored in device 300 or in some other local or remote location.
  • Fig. 7 shows one example of printing schedule 390, of the type that might be used in an enhanced version of HP's Instant Delivery program.
  • the title of delivery, delivery schedule, next delivery data and time, and the last deliver status are shown.
  • the user can select what time a document should be printed, whether it should be printed on a specific day of the week or month, weekdays, or weekends, and whether the printing schedule should expire after a specific period of time or continue indefinitely.
  • printing module 380 monitors printing schedule 390 to see if a document should be requested from document server 100 or from another source.
  • block 2200 determines that a document should be requested from document server 100 or from another source
  • block 2200 is answered affirmatively, and block 2300 automatically requests the document without user intervention from server 100 or from another source, as will be described in greater detail below.
  • printing module 380 is located on device 300
  • block 2200 operates in a "pull" mode - where the document is "pulled" from document server 100 or another source to device 300.
  • the user does not press "any" print buttons or otherwise be directly involved in the printing process; in fact, the user may not even be present in the same room, city, state, or country as device 300 during the printing operation.
  • the printing operation automatically occurs in an unattended state - regardless of whether the user is present or not.
  • print schedule 390 is stored in a device-independent manner, such as on document server 100, a travelling user could "log in” to document server 100 and have his or her customized document sent to a device 300 that is convenient to the user's current location.
  • block 2600 checks to see whether the document printed successfully. If not, block 2800 performs error handling, such as attempting to print the document again, notifying the user that the printing device is out of paper or has some other error condition, or simply deciding not to print the document. When the document prints successfully, block 2900 informs document server 100 that the document printed successfully. Block 1600 waits for an indication from printing module 380 that the document did print successfully. When such an indication is received, block 1700 updates the user profile with this information.
  • error handling such as attempting to print the document again, notifying the user that the printing device is out of paper or has some other error condition, or simply deciding not to print the document.
  • block 2900 informs document server 100 that the document printed successfully.
  • Block 1600 waits for an indication from printing module 380 that the document did print successfully. When such an indication is received, block 1700 updates the user profile with this information.
  • Block 1800 examines the user profile preferably stored in knowledge module 170 to determine whether a product subsidy should be provide to the user. For example, if the information in the user profile indicates that this user has printed off his 1000 th document, such as a "preferred" document that contains advertising from advertising providers 80 or is otherwise under the control of edit module 120, providing a product subsidy to the user may be warranted.
  • a "product subsidy" could be a print consumable or other product.
  • a “print consumable” is an inkjet cartridge for an inkjet printer, ink for such an inkjet cartridge, a toner cartridge for a laser printer, toner for such a toner cartridge, or any other product or substance that is depleted when a document gets printed, including printer ribbons, etc.
  • the "ink” referred to above would typically be of a permanent variety, but erasable ink, such as that sold by the Eink Company, could also be used.
  • the product subsidy referred to herein is preferably funded at least in part by advertising revenue received from advertising providers 80 (Fig. 1), but an embodiment has been contemplated where the product subsidy is funded at least in part from the distribution revenue received from content providers 50 (Fig. 1).
  • information (such as statistical information) about what was printed by whom is preferably provided to content providers 50 and/or advertising providers 80 - preferably as a document that is automatically sent to one or more printing devices according to the teachings of this invention.
  • printable media such as plain paper, specialty paper, transparencies, and the like
  • devices 300 such as printing devices, electronic devices, and personal computers.
  • other products such as a subscription price to a document, or even a product not directly related to the document delivery system shown herein, such as soap or dog food, are subsidized.
  • block 1900 requests that distribution module 400 provides such a subsidy to the user.
  • distribution module 400 simply mails a product such as a print consumable or other product such as the type described above to a user at the address specified in the user profile.
  • distribution module 400 mails or electronically generates a coupon that the user can use to receive a free or discounted product of the type described above. Regardless of whether block 1800 is answered affirmatively or negatively, flow of control then returns back to block 1300 (Fig. 2) to see if another document has been requested from the printing module 380.
  • Block 4300 checks to see whether this updated version of printing module 380 should be requested to be downloaded. While a user would typically be asked whether such a download should be requested or not, and would typically perform this download at a convenient time, such a step could also be performed automatically without user intervention. If such a download is requested, block 4400 is answered affirmatively, and block 3500 downloads the updated printing module, which is then installed in block 4500. Regardless of how blocks 4200 and 4300 are answered, flow of control moves to block 4600, which checks to see if a disconnected state should be entered. If block 2300 (Fig.
  • the title of document 11000 specifies a network address, such as an Internet uniform resource locator (URL) that contains the network location of a document to be printed.
  • URL Internet uniform resource locator
  • edit module 120 of document server 100 merely goes out to the Internet at the URL indicated (which would be shown in Fig. 1 as one of the content providers 50), and captures the indicated document, which is then transmitted to a printing device via transmission module 150 and printing module 380, as has been discussed.
  • device 300 could go directly out to the URL itself without assistance from document server 100; in this case, block 2300 (Fig. 2) requests document 11000 from another source - directly from the content provider 50 (at the indicated URL) via network 200.
  • document 12000 is not a document that originates with a content provider 50 via the Internet, but instead is stored directly on device 300, such as a printing device, personal computer, or other electronic device.
  • device 300 such as a printing device, personal computer, or other electronic device.
  • An example of such a document could be a daily calendar from a program such as Microsoft Outlook, which the user has requested be printed automatically to his printer, without any user intervention, at 7:00 a.m. every weekday morning.
  • printing module 380 does not need to request the document from document server 100, since it can access the documents without going through network 200.
  • block 2300 of Fig. 2 requests the document from another source - device 300.
  • block 2900 would still preferably indicate that the document was printed, and while block 1700 would still preferably update the user profile in knowledge module 170, printing such a document would preferably not generate any type of credit towards a product subsidy, since such a document would not be considered a "preferred" document, e.g., not a document under the control of edit module 120.
  • Document 13000 is referred to as a "personalized document”.
  • a "personalized document” is a document that is assembled by edit module 120 of document server 100 from a variety of content providers 50 and advertising providers 80, based on information contained in the user profile stored in knowledge module 170.
  • document 13000 is a "personalized document”.
  • Our user has requested that document 13000 - his personalized newspaper - be printed at 6:00 a.m. every day.
  • Edit module 120 examines the user's interests as specified in the user profile stored in knowledge module 170 to assemble the document from selected content providers 50 in which the user has indicated an interest.
  • Edit module 120 also inserts advertising from selected advertising providers 80 - again based on the user profile stored in knowledge module 170.
  • Fig. 8 shows how the print schedule 390 of Fig. 7 can be edited by the user.
  • the user can use the publisher's recommended schedule, use a default schedule the user has set, or use a custom schedule for delivery. If a custom schedule is selected, the user can select a daily, weekly, or monthly delivery, or select a delivery once every specified number of days, or specify every weekday.
  • the time of day can also be specified: once at a designated time, multiple times during the day, or multiple times separated by a specified period of time. While not shown here, the user could also edit print schedule 390 to request that a document be sent upon creation, or upon the occurrence of an external event.
  • Figs. 9A-9B show document 11000 printed by the printing device according to one embodiment of the invention. Note that this document came from one content provider 50 via network 200 (either through document server 100 or directly), and contains no advertising. While document 11000 is preferably formatted by content provider 50 such that the information contained in the document is optimized to be printed, such formatting is not necessary.
  • Fig. 10 shows document 12000 printed by the printing device according to one embodiment of the invention. Note that this document is a user's daily calendar which came directly from device 300 and not from document server 100 via network 200.
  • Figs. 11A-D show document 1300 printed by the printing device according to one embodiment of the invention.
  • this document is a user's personalized newspaper which contains information in which the user has indicated a specific interest in, as stored in the user profile in knowledge module 170.
  • this document contains advertising that edit module 120 determined the user would also be interested in, again based on the information contained in the user profile stored in knowledge module 170.
  • the user may receive a product subsidy of a print consumable or other product(s).
  • Fig. 12 shows document 14000 printed by the printing device according to one embodiment of the present invention.
  • document 14000 is the HP Instant Delivery Times - a document located on document server 100. While this document does not contain advertising per se, it is still considered to be a "preferred document", since it is under the control of edit module 120.
  • Document 14000 informs users of Instant Delivery of new releases or new information about the Instant Delivery Program.
  • Figs. 17-21 provide additional operational information regarding select aspects of the present invention.
  • a flow chart illustrating an example method for generating a personalized document begins with block 1010, wherein editor module receives content objects from content providers 50 and /or advertising providers 80, and selectively invokes an instance of content manager 518.
  • content manager 518 classifies, wraps and stores each of the received content objects, block 1015. More specifically, as introduced above, content manager 518 invokes an instance of analysis/wrapper agent 522 to analyze and encapsulate the received content object in a trace wrapper having a unique identifier.
  • analysis agent 522 identifies meta data within the received content object to classify the content object.
  • content manager 518 updates the content provider information data structure 620 associated with the provider of the content object to denote the wrapper identifier for the received content object.
  • edit module 120 identifies whether an indication for construction of a personalized document has been received. As introduced above, such an indication may be generated by a requesting user via a user interface (e.g., a web page), or in response to an indication received from, for example, print schedule 390. In either case, if an indication is received, edit module 120 invokes an instance of the innovative virtual editor 506 to generate a personalized publication for delivery to the identified user. In this regard, virtual editor 506 invokes an instance of construction agent 520, which obtains information from a user profile associated with the identified user to determine user interests, block 1410.
  • construction agent 520 obtains information from the user profile 602 to determine the medium of choice (e.g., send the publication electronically via email, send via fax, send to a local printer of the user, etc.), interests, preferences and/or a history of received information.
  • medium of choice e.g., send the publication electronically via email, send via fax, send to a local printer of the user, etc.
  • construction agent 520 determines whether the publication request is unique to an individual user, or whether the information has already been retrieved for another user. If content objects identified for publication have already been retrieved to satisfy another user request, construction agent 520 access local memory 508 to quickly retrieve the identified content objects, block 1425. Otherwise, in block 1430, construction agent 520 extracts the appropriate ones of the categorized content objects with which to generate a personalized publication.
  • construction agent 520 generates an initial layout of the personalized document using the extracted information.
  • construction agent 520 identifies additional content objects based, at least in part, on the already extracted content objects and other key contributor criteria (e.g., seasonality, locality, etc.) introduced above.
  • construction agent 520 may also leave room in the layout for inclusion of content by a local content provider (e.g., an ISP), through which the personalized publication will be transmitted en route to the identified user.
  • a local content provider e.g., an ISP
  • the construction agent 520 further optimizes document layout, updating the content provider information database 620 with an indication of which content objects have been utilized in construction of the personalized document.
  • the personalized document created by construction agent 520 of virtual editor 506 is then sent to publishing agent 504, block 1445.
  • layout manager 516 of publishing agent finalizes the layout and content (except for last minute, time sensitive content objects), while scheduling manager 514 optimally schedules delivery of the publication to include such last minute, time sensitive content objects.
  • Publishing agent 504 then issues the personalized document for delivery to the user via transmission module 150 and a printing module 380 associated with the user.
  • printing module 380 includes a virtual sensor (not shown) which detects and identifies trace wrappers for content objects comprising received personalized publications, providing document server 100 with confirmation of receipt of the content objects.
  • the method begins with block 2695, wherein printing module 380 informs the publication server that the publication was successfully printed.
  • printing module 380 informs the publication server that the publication was successfully printed.
  • the document server 100 is informed that the publication was successfully printed.
  • content manager 518 updates the usage fields of the content objects comprising the received personalized document, for accurate accounting to content providers 50 and advertising providers 80.
  • printing module 380 covertly monitors user interaction with the received publication.
  • printing module 380 weighs user satisfaction based, at least in part, on observed user interaction with the received publication and any received feedback from the user.
  • printing module 380 notes any further distribution of the content objects comprising the personalized publication, whether any edits/annotations were made to the publication, etc. and provides such information to edit module 120 to update user profile and content provider information data structures 602 and 620, respectively.
  • System 10 subsequently tracks the re-distribution, receipt and user disposition of the content objects to the new recipients as described above for the original recipient.
  • publishing agent 504 invokes an instance of layout manager 516 and an internal clock (not shown) is engaged to monitor compilation time.
  • more complex measures are developed and maintained such as, for example, compilation time at a particular time of day, day of the week, etc. By maintaining this measure of compilation time, however complex or rudimentary, enables publishing agent 504 to improve publication and delivery scheduling.
  • layout manager 516 determines whether the publication contains any time sensitive material. If so, a further determination is made of whether the delivery schedule must include time to obtain information (content objects) immediately prior to delivery of the publication, block 1451. If the publication does not contain time sensitive information (1449), or the delivery schedule does not require obtaining information immediately prior to delivery (1451), layout manager 516 receives the content objects from the virtual editor 506 to finalize the layout of the publication, block 1453. In block 1455, layout manager analyzes the content objects in light of the key contributor information and generates a final layout of the document.
  • layout manager 516 receives the content objects from the virtual editor and performs a partial final layout of the publication, leaving layout completion to the schedule manager 514 once the last minute content objects have been retrieved, block 1454.
  • layout manager 516 disengages the internal clock, calculates the compilation time and updates a measure of compilation time.
  • layout manager 516 generates a measure of publication complexity and maintains a measure of estimated compilation time for varying degrees of publication complexity. The estimated compilation time may then be used to optimally schedule publication layout jobs based, at least in part, on the complexity of the jobs.
  • Fig. 20 provides a flow chart of an example method for optimally scheduling publication, according to one aspect of the present invention.
  • the process begins with block 1465, wherein schedule manager 514 receives a publication from layout manager 516 and performs an initial load balancing calculation.
  • layout manager 516 provides schedule manager 514 with an estimate of compilation time, from which schedule manager 514 schedules publication to optimally utilizes the resources of publishing agent 504.
  • the estimate of compilation time may be a quantitative value (e.g., the compilation time of layout manager 516 to layout the publication), or a qualitative value (e.g., an indication that the publication is of low, medium or high complexity).
  • Schedule manager 516 then identifies an optimal publication start time based on, for example, the relative complexity of the received publication versus other scheduled publications. According to one embodiment, schedule manager 514 maintains a queue of publication jobs denoting the start time and estimated processing time for each publication.
  • schedule manager 514 determines whether it is time to complete publication and delivery of a queued publication. If so, schedule manager 514 engages an internal clock to monitor compilation time, block 1471. As above, the measure of compilation time is useful for making future estimates of schedule manager 514 processing time for jobs of similar complexity, thereby iteratively developing a more accurate schedule manager 514.
  • schedule manager 514 retrieves any last minute, time sensitive information for inclusion in the publication, and finalizes the layout of the publication including such content.
  • schedule manager 514 continuously monitors whether the publisher agent 504 is on schedule to complete the publication within the allocated time. This is particularly important during, for example, publication of multiple quantities of a document. In such an instance, schedule manager continuously determines whether publication of all the documents is likely to occur. Assuming that publisher is currently on schedule, schedule manager 514 further determines in block 1477 whether publication is complete.
  • schedule manager 514 disengages the internal clock measuring compilation time and records this information for use in future publication estimation and scheduling, block 1479.
  • schedule manager 514 generates the document for delivery to printing module 380, and sends the document to transmission module 150 for delivery to the printing modules 380, block 1495.
  • schedule manager 514 determines that the publisher is not likely to complete the publication according to schedule, schedule manager 514 defaults on the publication in block 1483, so that it can maintain its publication schedule by moving on to the next publication job. In such an implementation, schedule manager 514 notifies system management to adjust the heuristic data and report the failed publications, block 1485. In block 1487, a default publication is generated and provided to printing module(s) 380, block 1481. In an alternate implementation, rather than defaulting the current publication (1483), schedule manager 514 re-optimizes the publication schedule, shifting publication jobs in the queue as necessary to ensure publication of the current document.
  • trace wrappers and virtual sensor(s) 35000 facilitate the covert monitoring of content object distribution and disposition from up to many points throughout document delivery system 10, document delivery server 100 with valuable feedback on which objects are of interest to particular users, the amount of distribution of content objects (e.g., for accounting purposes), and the like.
  • trace wrappers are non-invasive markers, i.e., they do not alter the content of the content objects.
  • a personalized publication 6000 comprised of content objects embedded in trace wrappers 6002(A)...(N) is provided with reference to Fig. 22.
  • content object 6004 is encapsulated within a trace wrapper 6002(A) with a "tag", or "marker" 6006 which is stored in content provider information data structure to uniquely identify the content object.
  • the method of Fig. 21 begins with block 5002, wherein the content manager 518 of virtual editor 506 receives an report from one or more virtual sensor(s) that content objects have been sent through, or received by, identified users. In response, appropriate content manager 518 updates appropriate user profile(s) (block 5004) and content provider information data structures (block 5006) to reflect the distribution, receipt and/or disposition of content objects.
  • contract administrator 524 of content manager 518 periodically initiates financial transactions with content providers 50, advertising providers 80 and subscribing users.
  • contract administrator 524 initiates royalty payments for the distribution and receipt of content objects provided by select content providers, in accordance with contractual obligations established between the document delivery system and such content providers.
  • contract administrator identifies the usage of content objects associated with the content providers 50 to determine an accurate royalty payment, and instructs transaction agent 526 to complete the financial transaction, preferably via one of a number of electronic financial service networks.
  • transaction agent 526 initiates a payment to the financial service network account associated with the content providers 50 in the amount identified by contract administrator 524.
  • transaction agent 526 may initiate printing of checks payable to the content providers 50 in a denomination indicated by contract administrator 524, wherein such printed checks are then mailed to the content providers 50.
  • the degree of accuracy with which content distribution and disposition is monitored within document delivery system 10 facilitates "micro-transactions", i.e., electronic transactions which occur automatically with each system operation in which a financial obligation is created (as defined in contract administration information).
  • a financial account associated with a content provider 50 is credited with a royalty payment each time a content object associated with the content provider 50 is (re)distributed, This may amount to hundreds, thousands or millions of micro-transactions per day, per content provider.
  • Transaction agent 526 may initiate financial transactions as accrued lump sums transacted on a periodic basis, or based on reaching a monetary threshold (e.g., payments are made in $10 increments).
  • financial transaction agent 526 may alternatively debit accounts of advertising providers 80, or subscribing users on a micro-transaction, periodic or other lump-sum basis in much the same fashion as described above.
  • contract administrator 524 periodically calculates advertising usage for advertising providers 80, instructing transaction agent 526 to bill the identified advertising providers 80 based on advertising usage, placement, associations, and the like.
  • transaction agent 526 preferably carries this billing out via an electronic financial network, but may alternatively (or in addition) initiate the printing and mailing of physical bills to the advertising providers 80.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
EP01302430A 2000-03-30 2001-03-15 Système et méthodes associées pour suivre et controler la distribution de contenu Withdrawn EP1139258A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US53930300A 2000-03-30 2000-03-30
US539303 2000-03-30

Publications (1)

Publication Number Publication Date
EP1139258A1 true EP1139258A1 (fr) 2001-10-04

Family

ID=24150658

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01302430A Withdrawn EP1139258A1 (fr) 2000-03-30 2001-03-15 Système et méthodes associées pour suivre et controler la distribution de contenu

Country Status (3)

Country Link
EP (1) EP1139258A1 (fr)
JP (1) JP2001312668A (fr)
IL (1) IL140724A0 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2452133C2 (ru) * 2007-04-26 2012-05-27 Телефонактиеболагет Лм Эрикссон (Пабл) Способ и устройство для обработки исторической информации по мобильной станции в системе беспроводной связи

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7577706B2 (en) * 2003-11-24 2009-08-18 Xerox Corporation Integrating a document management system with a workflow system and method
JP7424801B2 (ja) * 2019-11-12 2024-01-30 株式会社Ｔｂｓテレビ テキストデータを用いた映像編集出力制御装置、テキストデータを用いた映像編集出力方法、及びプログラム

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5710884A (en) * 1995-03-29 1998-01-20 Intel Corporation System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use
US5761662A (en) * 1994-12-20 1998-06-02 Sun Microsystems, Inc. Personalized information retrieval using user-defined profile

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05233698A (ja) * 1992-02-21 1993-09-10 Nippon Telegr & Teleph Corp <Ntt> 表現方法指定型記事編集方法
US5740549A (en) * 1995-06-12 1998-04-14 Pointcast, Inc. Information and advertising distribution system and method
JPH0973487A (ja) * 1995-09-01 1997-03-18 Fujitsu Ltd コンテンツ売上金分配システム及び分配方法
JP2000076339A (ja) * 1998-09-01 2000-03-14 Toppan Printing Co Ltd コンテンツ運用方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5761662A (en) * 1994-12-20 1998-06-02 Sun Microsystems, Inc. Personalized information retrieval using user-defined profile
US5710884A (en) * 1995-03-29 1998-01-20 Intel Corporation System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
No Search *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2452133C2 (ru) * 2007-04-26 2012-05-27 Телефонактиеболагет Лм Эрикссон (Пабл) Способ и устройство для обработки исторической информации по мобильной станции в системе беспроводной связи
US8345632B2 (en) 2007-04-26 2013-01-01 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for processing mobile station history information in a wireless communication system

Also Published As

Publication number Publication date
IL140724A0 (en) 2002-02-10
JP2001312668A (ja) 2001-11-09

Similar Documents

Publication Publication Date Title
US6826534B1 (en) Agent and method for dynamically scheduling publication in an automated document delivery system
US6981214B1 (en) Virtual editor and related methods for dynamically generating personalized publications
EP1108240B1 (fr) Agent et procede d&#39;ordonnancement dynamique de publications dans un systeme de remise de documents automatise
EP1217566A1 (fr) Système de livraison de documents comprenant des fonctions intégrées de renvoi
WO2001095140A2 (fr) Systeme et procedes associes permettant de selectionner de maniere dynamique le contenu d&#39;une publication
US7025346B1 (en) System and related methods for automatically determining the media count in a printing device media tray
EP1108324B1 (fr) Systeme et procedes apparentes permettant de determiner automatiquement un type de support dans un plateau de support d&#39;impression d&#39;un dispositif d&#39;impression
EP1139258A1 (fr) Système et méthodes associées pour suivre et controler la distribution de contenu
MXPA01001482A (en) A multi-sourced extensible publishing and editorial system and related methods

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FR GB SE

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17P Request for examination filed

Effective date: 20020311

AKX Designation fees paid

Free format text: DE FR GB SE

17Q First examination report despatched

Effective date: 20041201

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050412