WO2005052805A1 - Data structure, event reporting system and method for event reporting - Google Patents

Data structure, event reporting system and method for event reporting Download PDF

Info

Publication number
WO2005052805A1
WO2005052805A1 PCT/KR2004/000872 KR2004000872W WO2005052805A1 WO 2005052805 A1 WO2005052805 A1 WO 2005052805A1 KR 2004000872 W KR2004000872 W KR 2004000872W WO 2005052805 A1 WO2005052805 A1 WO 2005052805A1
Authority
WO
WIPO (PCT)
Prior art keywords
xsd
event report
data
event
time
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.)
Ceased
Application number
PCT/KR2004/000872
Other languages
English (en)
French (fr)
Inventor
Young-Joo Song
Jin-Woo Hong
Nam-Mee Mun
Kyung-Hee Ji
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.)
Electronics and Telecommunications Research Institute
Original Assignee
Electronics and Telecommunications Research Institute
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 Electronics and Telecommunications Research Institute filed Critical Electronics and Telecommunications Research Institute
Priority to JP2006541012A priority Critical patent/JP4795247B2/ja
Priority to US10/580,290 priority patent/US8271573B2/en
Publication of WO2005052805A1 publication Critical patent/WO2005052805A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/443—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41407—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop

Definitions

  • the present invention relates to data structure, system and method for reporting an Event occurred due to a digital item (DI); and more particularly, the present invention relates to data structures of Event Report Request (ER-R) data and Event Report (ER) data, an Event Reporting system for managing and processing the Event based on the ER-R data and the ER data, a method for reporting the Event, and a computer readable medium storing instructions for implementing the same method.
  • DI digital item
  • Moving picture expert group proposed 'Event Reporting' due to a new standard working item of MPEG-21, a digital item.
  • the digital item means a structured digital object with a standard representation, identification and metadata.
  • the Event Reporting means a process of Event monitoring, which requests a report on a certain Event occurred during the digital item is used in user terminal, and reports occurrence of the Event.
  • the user includes all of a provider, an authorizer, a distributor and a consumer of the digital item.
  • MPEG-21 includes seven core elements, i.e., Digital Item Declaration (DID) , Digital Item Identification and Description (DII&D) , Content Handling and Usage, Intellectual Property Management and Protection (IPMP), Terminal & Network, Content Representation and Event Reporting.
  • An object of the Event Reporting is to provide a standardized interface for measuring and reporting the Event occurred when using the digital item of MPEG-21 in direct or indirect.
  • the Event Reporting is applied to usage report, e.g., Performance and Copies of the digital item, and technical report, e.g., Bandwidth Usage/Availability, Network Congestion, Load Balancing, and a financial report, e.g., Proof of Purchase, License Purchase and Delivery.
  • the Event Reporting increases understanding user's action, provides generation, delivery and consumption of the digital item, and enables the user to manage circulation of the copyrighted material by reporting the Event related to royalties and finances.
  • the Event Reporting is classified into Event Report Requests and Event Reports.
  • the Event Report Request means a process in which an Event Report Request data, which is preferred to be generated as metadata, requesting a report for a certain Event occurred in accordance to use of a digital item is generated and transmitted.
  • the Event Report means a process in which that an Event Report data, which is preferred to be generated as metadata, containing report data is generated and transmitted, when an Event specified in the Event Report Request data occurs.
  • the Event Reporting system should include an apparatus which generates Event Report Request data in response to a request of a user and transmits the same, and an apparatus which receives, analyzes and stores the Event Report Request data, monitors the Event, generates Event Report data corresponding to the Event, and transmits the same.
  • the Event Reporting system needs to have standardized data structures of the Event Report Request data and the Event Report data.
  • there is no apparatus for reporting the Event occurred from usage of the digital item data structures of Event Report Request data and the Event Report data are not standardized. Therefore, there is a problem that the Event Reporting can not be applied.
  • an object of the present invention to provide data structures of an Event Report Request data and an Event Report data for reporting an Event occurred due to a digital item (DI) . It is, therefore, another object of the present invention to provide an Event Reporting system for processing the Event based on the Event Report Request data and the Event Report data, a method for reporting the Event, and a computer readable medium storing instructions for implementing the same method.
  • DI digital item
  • an Event Report Request data for requesting to deliver an Event Report data, wherein the Event Report data reports an Event occurred in accordance with use of a digital item, the Event Report Request data comprising Delivery Time information describing time for transmitting the Event Report data, wherein the Delivery Time information includes: a specific time; an elapsed time; and a periodic time.
  • an Event Report data for reporting an Event occurred in accordance with use of a digital item wherein the Event Report data provides information specified in an Event Report Request data, the Event Report data comprising: ER Descriptor describing contents and formats of the Event Report data; and Source Descriptor describing information on a source generating the Event Report data.
  • an Event Reporting system for processing an Event Report data in order to report an Event occurred in accordance with use of a digital item, the Event Report system comprising: Event Report Request processing means for generating and delivering an Event Report Request data requesting to report an Event in response to user's request; and Event Report processing means for generating and delivering an Event Report data reporting the Event specified in the Event Report Request data .
  • an apparatus for requesting to report an Event and processing an Event Report Request data in order to report an Event occurred in accordance with use of a digital item comprising: Event Report Request generation means for generating the Event Report Request data; Event Report Request transmission means for transmitting the Event Report Request data; Event Report Request receiving means for receiving an Event Report Request data; Event Report Request analysis means for the Event Report Request data received in the Event Report Request receiving means; and Event occurrence monitoring means for monitoring whether or not an Event occurs.
  • an apparatus for processing an Event Report data in order to report an Event occurred in accordance with use of a digital item comprising: Event Report generation means for generating the Event Report data; Event Report transmission means for transmitting the Event Report data; Event Report receiving means for receiving an Event Report data; and Event Report Request analysis means for the Event Report data received in the Event Report receiving means.
  • a method for requesting to report an Event and processing an Event Report Request data in order to report an Event occurred in accordance with use of a digital item comprising steps of: a) generating and delivering the Event Report Request data; and b) receiving an Event Report Request data from an outside, analyzing the Event Report Request data received from the outside and monitoring whether or not an Event specified in the Event Report Request data received from the outside occurs.
  • a method for requesting to report an Event and processing an Event Report Request data in order to report an Event occurred in accordance with use of a digital item comprising steps of: a) generating and delivering the Event Report Request data; and b) receiving an Event Report Request data from an outside, analyzing the Event Report Request data received from the outside and monitoring whether or not an Event specified in the Event Report Request data received from the outside occurs.
  • a computer readable recording media storing instructions for executing a method for requesting to report an Event and processing an Event Report Request data in order to report an Event occurred in accordance with use of a digital item, the method comprising steps of: a) generating and delivering the Event Report Request data; and b) receiving an Event Report Request data from an outside, analyzing the Event Report Request data received from the outside and monitoring whether or not an Event specified in the Event Report Request data received from the outside occurs.
  • Fig. 1 is a block diagram showing an Event Reporting system in accordance with the present invention
  • Fig. 2 is a diagram showing data structure of Event Report Request data. in accordance with an embodiment of the present invention
  • Fig. 3 is a diagram showing contents of delivery time information of Event Report Request data in accordance with an embodiment of the present invention
  • Fig. 4 is a diagram showing data structure of Event Report Request data in accordance with another embodiment of the present invention
  • Fig. 5 is a diagram showing data structure of Event Report data in accordance with another embodiment of the present invention
  • Fig. 6 is a diagram showing Event Report Request data including other Event Report Request data and Event Report data including other Event Report data and another Event Report
  • FIG. 7 is a detailed block diagram showing a main processing unit of an Event Reporting system in accordance with the present invention
  • Fig. 8 is a detailed block diagram showing an Event Report Request processing unit of an Event Reporting system in accordance with the present invention
  • Fig. 9 is a detailed block diagram showing an Event Report processing unit of an Event Reporting system in accordance with the present invention
  • Fig. 10 is a flow chart showing an Event Report Requesting process
  • Fig. 11 is a flow chart showing an Event Reporting process
  • Fig. 12 is a flow chart showing an Event Report processing process
  • Fig. 13 is a flow chart showing an Event Report data analyzing process.
  • Fig. 1 is a block diagram showing an Event Reporting system in accordance with the present invention.
  • a main processing unit 101 which processes Event Reporting in an Event Reporting system 100, communicates with a user 10 in direct through an input/output interface 30, through a file stored on a storing unit 20 or through a remote access 40.
  • the Event Reporting system transmits and receives to/from other user in outside, Event Report data (ER) or Event Report Request data (ER-R) through a network 50.
  • Event Report Request (ER-R) is information describing what to report, to whom to report, a form of report, when and how to report, when an Event is generated with respect to a digital item. Further description on it will be provided later.
  • the Event Report (ER) data describes information on the Event requested by the ER-R data, a user requesting the Event Reporting, and a recipient receiving the ER data, which will be described in detail.
  • the Event Reporting system 100 can be installed on all of systems generating, transmitting and consuming a digital item, for example, a computer including a laptop computer, a notebook computer, a desktop computer, a workstation and a mainframe, and a mobile terminal including a personal digital assistant (PDA) and a mobile station.
  • the user 10 accesses the Event Reporting system 100 and requests to generate the Event Report Request (ER-R) data through a direct input process based on an application program. Also, the user 10 requests the Event Reporting system 100 to generate the ER-R data by storing contents on the storing unit 20 in advance.
  • ER-R Event Report Request
  • the storing unit 20 can be located in inside or outside of the Event Reporting system 100, and includes all kinds of computer readable recording medium, e.g., a CD-ROM, a random access memory (RAM) , a read only memory (ROM) , a floppy disk, a hard disk and a magneto-optical disk.
  • the user 10 accesses the Event Reporting system 100 in remote and requests the Event Reporting system 100 to generate the ER-R data.
  • the Event Reporting system 100 receives a request to generate the ER-R data from the user 10, generates the ER-R data and transmits the ER-R data to the user through a network 50.
  • the network 50 includes wired/wireless local area networks (LAN), e.g., Ethernet, a fiber distributed data interface (FDDI) network, a token ring network and an asynchronous transfer mode (ATM) network, and a wide area network, e.g., a public switched telephone network (PSTN), a packet switched data network (PSDN) and an integrated services digital network (ISDN).
  • LAN local area networks
  • FDDI fiber distributed data interface
  • ATM asynchronous transfer mode
  • PSTN public switched telephone network
  • PSDN packet switched data network
  • ISDN integrated services digital network
  • the Event Reporting system 100 receives the ER data and the ER-R data through the network 50, analyzes them, generates another ER data or another ER-R data and transmits them to an outside, extracts information from the ER data and the ER-R data, stores the extracted information or transmits the extracted information to user application program in direct.
  • Event Report Request (ER-R) data includes a "Condition Descriptor” field, an "Event Report Request (ERR) Descriptor” field, an “Event Report (ER) Descriptor” field, a “Delivery Descriptor” field and "To Whom” field.
  • the ER-R data includes a "Condition Descriptor” describing conditions for the delivery of the ER data, i.e., occurrence of an Event, an "ERR Descriptor” describing identification and characteristics of the ER-R data itself, an “ER Descriptor” describing contents and formats of the ER data corresponding to the Event condition, a “Delivery Descriptor” describing generation and transmission schemes of the ER data, and "To Whom" field describing recipients of the ER data.
  • a "Condition Descriptor” describing conditions for the delivery of the ER data, i.e., occurrence of an Event
  • an “ERR Descriptor” describing identification and characteristics of the ER-R data itself
  • an “ER Descriptor” describing contents and formats of the ER data corresponding to the Event condition
  • a “Delivery Descriptor” describing generation and transmission schemes of the ER data
  • “To Whom” field describing recipients of the ER data.
  • the "Condition Descriptor” includes "Time” field describing the Event occurrence time, "DI Related Operation” field describing user operation condition in accordance with the use of the digital item, "Peer Related Operation” field describing condition in accordance with the operations occurred in the peer.
  • the peer means a device or application that compliantly processes the digital item without modification.
  • the "Time” describes a specific time, an elapsed time or a periodic time, on which the Event occurs.
  • the "DI Related Operation” may use terms of right data dictionary (RDD) defined in MPEG-21, e.g., DI play, stop, modify, install, uninstall, print, adapt, delete, execute and move.
  • RDD right data dictionary
  • the "Peer Related Operation” may use terms of the Peer Environment of a Digital Item Adaptation (DIA) defined in the MPEG-21, e.g., network congestion and peer capability.
  • the "ERR Descriptor” includes an "ID” field describing identification (ID) of the ER-R data, a “Description” field of the ER-R data describing attributes of the ER-R data, and an "Access Right” field describing an access right of the ER-R data.
  • the "Description” information includes a "Time Stamp” field describing a time on which the ER-R data is generated, a "Life Time” field describing a life time of the ER-R data, a “History” field describing a history of creation or modification of the ER-R data and a "Priority Level” field describing the priority level to the ER-R data, wherein the priority level is used by peers to handle ER-R data.
  • the "ID” may have the same format as digital item identification (DII) defined in the MPEG-21, and the "Life Time” may be described as a time to live (TTL) .
  • the "ER Descriptor” includes an "ER Data Descriptor” field describing a report data list and format of the Event Report (ER) data, wherein the report data list is a list of information to be included in the ER data, and an "ERR” field describing another Event Report Request message data requesting an operation, e.g., an acknowledgement or forwarding of the ER-R data.
  • the "ER Data Descriptor” includes an "ER ID” field describing identification of an ER data and a "Report Data” field describing list of information which the Event Report data reports .
  • the "ER ID” may have the same format as the DII defined in the MPEG-21.
  • the "Report Data” includes a "Peer Data” field describing information on the peer and a "User Data” field describing information on the user.
  • the “Delivery Descriptor” includes a "Format” field describing a format of data used for generating the ER data, an "Encryption” field describing an encryption method for encrypting the ER data, an "Access right” field describing access right to the ER data, an "Authentication” field describing an authentication method for authenticating the ER data, a "Delivery time” field describing time to delivery the ER data, a “Protocol” field describing a network protocol for delivering the ER data and a “Compression” field describing a compression method for compressing the Event Report data.
  • the "Delivery Time” includes a specific time, an elapsed time and a periodic time on which the Event Report data is delivered.
  • Fig. 3 is a diagram showing contents of delivery time information of Event Report Request data in accordance with an embodiment of the present invention.
  • the "Delivery Time” may request to deliver the Event Report data on a time tl (see 1001), before a time t2 (see 1005) and between tl and t2 (see 1007) .
  • the "Delivery Time” may request to deliver the Event Report data after a time el based on Event occurrence (see 1009), before a time e2 (see 1011) and between el and e2 (time subtracted from e2 by el) (see 1013) .
  • the "Delivery Time” may request to deliver the Event Report data at every time corresponding to a transmission period pi (see 1015) .
  • syntax of Delivery Time information is defined as Table 1.
  • Tables 3 to 5 show an example of Delivery Time information defined by XML syntax.
  • [Table 3] ⁇ deliveryTime> ⁇ specificTime> ⁇ beforeOn>2004-03-31T00:00:00 ⁇ /deforeOn> ⁇ /specificTime> ⁇ /deliveryTime>
  • XML syntax of Delivery Time information is applied to Event occurrence time information of Condition Descriptor.
  • the "To Whom” includes a "Peer IDs” field, which is identification information of the peers receiving the Event
  • the "To Whom” may be multiple recipients, and the recipients may be classified as mandatory recipients and optional recipients.
  • XML syntax of "To Whom” information is defined as a following table 6.
  • Table 8 shows an example of "Recipient" defined by XML syntax in the table 7.
  • FIG. 4 is a diagram showing data structure of Event Report Request data in accordance with another embodiment of the present invention. As shown, the data structure of Event Report Request data in accordance with a second embodiment includes a "Condition Descriptor" field, an "ERR Descriptor” field, an "ER Descriptor” field and a "Delivery Descriptor” field.
  • Fig. 5 is a diagram showing data structure of Event Report data in accordance with an embodiment of the present invention.
  • the Event Report (ER) data includes an "ER Descriptor” field describing contents and formats of the ER data, a “Source Descriptor” field describing information on a source generating the Event Report message, an "ER Report data” field describing reportable information corresponding to items requested by the ER-R data, and an "Additional Action Descriptor” field describing additional actions related to generation, transmission and reception of the ER data corresponding to the ER-R data.
  • the "ER Descriptor” includes identification (ID) of the ER data and description information of the ER data.
  • the ER descriptor further includes an "ER Status” field describing status of the ER data, which is an optional element .
  • the description information includes a "Format” field describing a format of Event Report information data, an "Encryption” field describing an encryption algorithm for encrypting the ER data, an "Access Right” field describing an access right of the ER data, an "Authentication” field describing an authentication method for authenticating the ER data, a "Compression” field describing a compression method for compressing the ER data, a "History” field describing a history of creation or modification of the ER data, a "Priority Level” field describing the priority level to the ER data, wherein the priority level is used by the recipient to handle ER data, and a "Time Stamp” field describing a timing information on which the ER data is generated.
  • the "Source Descriptor” includes an "ER Peer ID” field describing identification (ID) of the peer who generates the ER data at the first, and an "Original ERR” field describing information on the ER-R data requesting to generate the ER data.
  • the "ERR” field may describe the ER-R data requesting to generate the ER data as an embedded whole ERR message data or a reference other ERR data.
  • the "ER Report Data” may allow the reportable information to be linked to the ER data as an embedded data or a reference data.
  • the "Additional Action Descriptor” includes an "ERR” field describing another Event Report Request data requesting an operation, e.g., an acknowledgement, forwarding or merging of the ER data, and an "ER” field describing another Event Report data to be linked to the ER data . Accordingly, the “Additional Action Descriptor” allows the ER data to include another ER-R data or another ER data, and process recursive Event Report or Event Report Request .
  • the "ERR” may describe the ER-R data requesting an acknowledgement or forwarding or merging of the ER data as an embedded data or a reference data.
  • the "ER Report Data” may allow another Event Report data related to the ER data, as an embedded data or a reference data. Fig.
  • Event Report Request data including other Event Report Request data and Event Report data including other Event Report data and another Event Report Request data in accordance with an embodiment of the present invention.
  • the ER data may include one or more other Event Report data or Event Report Request data an embedded data or a reference data.
  • an Event Report Request (ER-R) data ER-R A may include other ER-R data ER-R B, ER-R C as a reference data or an embedded data based on the "ERR" of the "ER Descriptor" .
  • ER data ER A corresponding to the ER-R data ER-R A may include another ER-R data ER-R D as well as ER data ER B, ER C corresponding to ER-R data ER-R B, ER-R C based on the "Additional Action Descriptor". Accordingly, using the Event Reporting system and the Event Report data in accordance with the present invention, recursive Event Reporting and Event Report Request can be implemented.
  • Fig. 7 is a detailed block diagram showing a main processing unit 101 of an Event Reporting system in accordance with the present invention. As shown, the main processing unit 101 includes an Event Report Request (ER-R) processing unit 201 and an Event Report (ER) processing unit 203.
  • the Event Report Request processing unit 201 receives from a user a request to report an Event, generates an Event report (ER-R)
  • the Event Report Request processing unit 201 analyzes the ER-R data received from an outside, monitors whether or not the Event specified in the ER-R data occurs, and requests the Event Report processing unit 203 to generate an Event Report (ER) data when the Event specified in the ER-R data occurs.
  • the Event Report processing unit 203 generates an Event Report (ER) data when the Event specified in the ER-R data occurs.
  • the Event Report processing unit 203 generates an Event Report (ER) data when the Event specified in the ER-R data occurs.
  • the Event Report processing unit 203 analyzes an ER data received from the outside, extracts contents of the ER data and transmits the contents of the ER data to the user. It is apparent to one skilled in the art that the Event Report Request processing unit 201 and the Event Report processing unit 203 may be independently implemented and operated in different devices (peer) . Fig.
  • the Event Report Request processing unit 201 includes an Event Report Request generation unit 301, an Event Report Request transmission unit 303, an Event Report Request receiving unit 305, an Event Report Request analysis unit 307, an Event occurrence monitoring unit 309 and an Event Report Request information managing unit 311.
  • the Event Report Request generation unit 301 generates the ER-R data in accordance with the request of the user.
  • the Event Report Request transmission unit 303 transmits the ER-R data generated in the Event Report Request generation unit 301 to the recipient.
  • the Event Report Request transmission unit 303 is made by a protocol stack for a network resource and attaches a protocol header to the ER-R data generated in the Event Report Request generation unit 301 and transmits the ER-R data.
  • the ER-R data and the ER data may be transmitted through on a commonly used protocol, e.g., a transmission control protocol (TCP) , a user datagram protocol (UDP) , a hyper-text transfer protocol (HTTP), a simple object access protocol (SOAP) , or through a new protocol developed for the Event Reporting.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • HTTP hyper-text transfer protocol
  • SOAP simple object access protocol
  • the Event Report Request receiving unit 305 is a network module which receives the ER-R data from an outside and analyzes a network header of the ER-R data.
  • the Event Report Request receiving unit 305 transmits the ER-R data to the Event Report Request analysis unit 307, and if not, the Event Report Request receiving unit 305 transmits the ER-R data to a network route for the recipient of the ER-R data.
  • the Event Report Request analysis unit 307 analyzes the ER-R data received from the outside, transmits to the Event occurrence monitoring unit 309 information on whether an Event Report is requested when a certain Event occurs with respect to a certain digital item, and transmits to the Event Report Request information managing unit 311 the information on what information to report, to whom to report, a format of the report, when to report and how to report .
  • the Event occurrence monitoring unit 309 monitors whether or not it occurs the Event for the digital item specified in the ER-R data. For example, the ER-R data requesting to report an Event when the digital item is played, the Event occurrence monitoring unit 309 monitors whether or not the digital item specified in the ER-R data is played, and when starting to play the digital item, informs occurrence of the Event to the Event Report Request information managing unit 311 to generate an ER data.
  • the Event Report Request information managing unit 311 is a database storing the information received from the Event Report Request analysis unit 307.
  • Fig. 9 is a detailed block diagram showing an Event Report processing unit of an Event Reporting system in accordance with the present invention.
  • the Event Report processing unit includes an Event Report generation unit 401, an Event Report transmission unit 403, an Event Report receiving unit 405 and an Event Report analysis unit 407.
  • the Event Report generation unit 401 generates Event
  • the Event Report transmission unit 403 transmits the Event Report (ER) data in response to request to generate the ER data from the Event request information managing unit 313.
  • the Event Report transmission unit 403 transmits the
  • the Event Report transmission unit 403 is made by a protocol stack for a network resource and is a network module which attaches a protocol header to the ER data generated in the Event Report generation unit 401 and transmits the ER data through an actual network resource.
  • the Event Report receiving unit 405 is a network module which receives the ER data from an outside and analyzes a network header of the ER data. If the ER data is transmitted to itself, the Event Report receiving unit 405 transmits the ER data to the Event Report analysis unit 407, and if not, the Event Report receiving unit 405 transmits the ER data to a network route for the recipient of the ER data.
  • the Event Report analysis unit 407 analyzes the ER data received from the outside, extracts information on what Event occurs for what digital item from the ER data, and transmits the information to the user. If the ER data includes Event Report Request (ER-R) data, the Event Report analysis unit 407 transmits the ER-R data to the Event
  • Fig. 10 is a flow chart showing an Event Report
  • the Event Report Request processing unit 201 generates ER-R data or receives ER-R data from an outside at step S600.
  • the Event Report Request processing unit 201 analyzes the ER-R data at step S601 and checks the recipient of the ER-R data at step S602. If the recipient is not itself, at step S603, the ER- R data is transmitted to a network route for the recipient of the ER-R data. If the recipient is itself, the Event Report Request processing unit 201 analyzes contents of the ER-R data at step S605, and determines whether the ER-R data includes another ER-R data at step S606.
  • ER-R data includes another ER-R data
  • the process continues to the step S601, to process another ER-R data.
  • the Event Report Request processing unit 201 stores the ER- R data at step S607, and monitors whether it occurs an Event corresponding to the ER-R data at step S609.
  • Fig. 11 is a flow chart showing an Event Report process . If a reportable Event occurs, a generation of an Event Report (ER) data is requested and the ER data is generated at step S701. A "Delivery Time" specified in the ER-R data is checked at step S703 and the ER data is delivered to the user on the delivery time at step S705.
  • Fig. 13 is a flow chart showing an Event Report data analyzing process. First, a header of the ER data is analyzed at step S901, and the recipient of the ER data is checked at step S902. If the recipient is not itself, at step S903, the ER data is transmitted to a network route for the recipient of the ER data.
  • ER data is analyzed at step S905, extracts information from the ER data and transmits the information to the user at step S909.
  • the present invention can be implemented and stored in a computer readable recording medium, e.g., CD-ROM, a random access memory (RAM) , a read only memory (ROM) , a floppy disk, a hard disk, and a magneto-optical disk. While the present invention has been described with respect to certain preferred embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the scope of the invention as defined in the following claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer And Data Communications (AREA)
  • Storage Device Security (AREA)
  • Information Transfer Between Computers (AREA)
PCT/KR2004/000872 2003-11-26 2004-04-14 Data structure, event reporting system and method for event reporting Ceased WO2005052805A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2006541012A JP4795247B2 (ja) 2003-11-26 2004-04-14 デジタルアイテムの使用に応じるイベント報告のためのデータ構造、並びにこれを利用したイベント報告システム及びその方法
US10/580,290 US8271573B2 (en) 2003-11-26 2004-04-14 Data structure, event reporting system and method for event reporting

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2003-0084742 2003-11-26
KR20030084742 2003-11-26

Publications (1)

Publication Number Publication Date
WO2005052805A1 true WO2005052805A1 (en) 2005-06-09

Family

ID=34632022

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2004/000872 Ceased WO2005052805A1 (en) 2003-11-26 2004-04-14 Data structure, event reporting system and method for event reporting

Country Status (3)

Country Link
US (1) US8271573B2 (cg-RX-API-DMAC7.html)
JP (1) JP4795247B2 (cg-RX-API-DMAC7.html)
WO (1) WO2005052805A1 (cg-RX-API-DMAC7.html)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10235410B2 (en) 2015-02-11 2019-03-19 Electronics And Telecommunications Research Institute Query input apparatus and method

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020095429A1 (en) * 2001-01-12 2002-07-18 Lg Electronics Inc. Method of generating digital item for an electronic commerce activities
US20030018798A1 (en) * 2001-07-20 2003-01-23 Lg Electronics Inc. Multimedia contents description model

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07235966A (ja) 1994-02-25 1995-09-05 Nippon Telegr & Teleph Corp <Ntt> Osiネットワーク管理システム及び方法
CN100365535C (zh) 1995-02-13 2008-01-30 英特特拉斯特技术公司 用于安全交易管理和电子权利保护的系统和方法
US6151624A (en) 1998-02-03 2000-11-21 Realnames Corporation Navigating network resources based on metadata
US6326675B1 (en) 1999-03-18 2001-12-04 Philips Semiconductor, Inc. Semiconductor device with transparent link area for silicide applications and fabrication thereof
US6785016B1 (en) 1999-05-25 2004-08-31 Silverbrook Research Pty Ltd. Portable interactive printer
JP2001175606A (ja) 1999-12-20 2001-06-29 Sony Corp データ処理装置、データ処理機器およびその方法
JP2002373261A (ja) 2001-06-18 2002-12-26 Hitachi Ltd 情報配信システム
US20030177283A1 (en) 2002-03-18 2003-09-18 Hamilton Thomas E. Application program interface

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020095429A1 (en) * 2001-01-12 2002-07-18 Lg Electronics Inc. Method of generating digital item for an electronic commerce activities
US20030018798A1 (en) * 2001-07-20 2003-01-23 Lg Electronics Inc. Multimedia contents description model

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ISO/IEC JTC1/SC29/WG11 N6279("Requirement for Event Reporting), *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10235410B2 (en) 2015-02-11 2019-03-19 Electronics And Telecommunications Research Institute Query input apparatus and method

Also Published As

Publication number Publication date
US8271573B2 (en) 2012-09-18
US20070282884A1 (en) 2007-12-06
JP2007513411A (ja) 2007-05-24
JP4795247B2 (ja) 2011-10-19

Similar Documents

Publication Publication Date Title
US6832250B1 (en) Usage-based billing and management system and method for printers and other assets
JP2009059160A (ja) サーバ装置、ネットワークシステム、コンテンツ発見通知方法、及びコンピュータ・プログラム
CN100553251C (zh) 用于安全并且自适应地传送多媒体内容的方法和设备
US20050114487A1 (en) Notification framework and method of distributing notification
US20080034393A1 (en) Distribution of content and advertisement
US7716290B2 (en) Send by reference in a customizable, tag-based protocol
US20080072264A1 (en) Distribution of content on a network
US20110270855A1 (en) State operating system
US20040015578A1 (en) Web services runtime architecture
US20060106748A1 (en) System and method for orchestrating composite web services in constrained data flow environments
EP1130845A2 (en) Publish/subscribe system
EP1454493A2 (en) Method of rights management for streaming media
US20070250545A1 (en) Computer implemented method for transforming an event notification within a database notification infrastructure
CN101304392B (zh) 一种用于媒体资产管理的并行应用服务网关、系统及方法
CN100508601C (zh) 用于数字项的ipmp方案描述的处理方法
CN106411996B (zh) 内容中心网络中的内容协商
CN101156407B (zh) 通过通信网络提供内容的方法
US8352931B2 (en) Data push service method and system using data pull model
Gurel et al. Need for low latency: Media over QUIC
JP6466382B2 (ja) 鍵を送付するための方法および装置
US8271573B2 (en) Data structure, event reporting system and method for event reporting
KR101090763B1 (ko) 디지털 아이템 사용에 따른 이벤트 리포팅을 위한 데이터구조와 이를 이용한 이벤트 보고 시스템 및 그 방법
JP2003319360A (ja) 映像配信システム、及び同システムにおける映像コンテンツのアクセス方法、認証アクセスサーバ、ウェブサーバ、並びにサーバプログラム
JP2005070884A (ja) 課金ポリシー生成装置、メタデータ配信サーバ、有料情報配信サーバ、有料情報配信システム、課金ポリシー生成方法、及び、有料情報課金方法
CN101359992A (zh) 内容类别请求方法、确定方法、交互方法及装置

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2006541012

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase
WWE Wipo information: entry into national phase

Ref document number: 10580290

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 10580290

Country of ref document: US