WO2004008760A1 - コンテンツ受信器およびコンテンツ送信器 - Google Patents
コンテンツ受信器およびコンテンツ送信器 Download PDFInfo
- Publication number
- WO2004008760A1 WO2004008760A1 PCT/JP2003/009043 JP0309043W WO2004008760A1 WO 2004008760 A1 WO2004008760 A1 WO 2004008760A1 JP 0309043 W JP0309043 W JP 0309043W WO 2004008760 A1 WO2004008760 A1 WO 2004008760A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- packet
- information
- capsule
- extended
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
- H04N7/17345—Control of the passage of the selected programme
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
- H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
- H04L1/1678—Details of the supervisory signal the supervisory signal being transmitted together with control information where the control information is for timing, e.g. time stamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/23614—Multiplexing of additional data and video streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2389—Multiplex stream processing, e.g. multiplex stream encrypting
- H04N21/23895—Multiplex stream processing, e.g. multiplex stream encrypting involving multiplex stream encryption
-
- 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/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/637—Control signals issued by the client directed to the server or network components
- H04N21/6375—Control signals issued by the client directed to the server or network components for requesting retransmission, e.g. of data packets lost or corrupted during transmission from server
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/64322—IP
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/6437—Real-time Transport Protocol [RTP]
-
- 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/854—Content authoring
- H04N21/8547—Content authoring involving timestamps for synchronizing content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
- H04N7/17309—Transmission or handling of upstream communications
- H04N7/17318—Direct or substantially direct transmission and handling of requests
Definitions
- the present invention relates to a digital television broadcast receiver, a personal computer, a mobile phone, a mobile information terminal, and a mobile phone adapter.
- transmitters and receivers having functions such as streaming for transmitting and receiving video and audio contents via a communication network have become widespread in the market.
- FIG. 7 is a diagram showing a configuration of a conventional content transmitter.
- FIG. 10 is a diagram showing a transition of a packet configuration between a conventional content transmitter and a conventional content receiver.
- FIG. 11 is a diagram showing the structure of a conventional packet.
- the video encoder 51 shown in FIG. 7 encodes a video signal by a predetermined compression method and outputs the encoded video signal to a subsequent stage.
- Fig. 7 shows a configuration using the MPEG2 method.
- the output from the video encoder 51 is composed of an MPEG2 transport stream bucket (hereinafter abbreviated as MPEG2-TSP).
- the system clock generator 54 generates a 27 MHz clock.
- the system clock used when the video encoder 51 encodes the video signal is this 27 MHz clock.
- the audio encoder 52 encodes the audio signal using the same compression method as the video encoder 51, and outputs MPEG2-TSP to the subsequent stage.
- the data encoder 53 encodes data such as data broadcast and EPG data in the same compression format as the video encoder 51, and outputs MPEG2_TSP to the subsequent stage.
- the stream multiplexer 55 multiplexes the above-mentioned three MPEG2-TSPs on the time axis. Further, the stream multiplexer 55 generates a PCR signal for reproducing the system clock on the receiving side by periodically using a count value obtained by counting the system clock at a cycle of about 50 ms. And the stream multiplexer 55 After the signal is converted into 1 ⁇ £ 2_3, it is further multiplexed with the above multiplexed signal and output to the subsequent stage as an MPEG2 transport stream (hereinafter abbreviated as MPEG2-TS). . This output signal is shown as S11 in FIG.
- FIG. 10 is a diagram showing a transition of multiplexing of packets on a time axis.
- the horizontal axis in Fig. 10 is time. However, in FIG. 10, the steady delay in each process is ignored and not shown.
- 10 1, VIDEO 02, VIDEO 3, AUD I 01, AUD I 02, and DAT A 1 of 31 1 are packets multiplexed by the stream multiplexer 55.
- 31 1, 10 £ 1, VIDE ⁇ 2, and VIDE03 are available in MPEG2-TSP with video code.
- AUD I01 and AUD I02 of S11 are audio-encoded MPEG21-TSP.
- DATA 1 in S11 is a data encoded MPEG2-TSP. The description of the PCR signal is omitted because it is a well-known content in the MPEG2 system.
- the scrambler 56 encrypts the MPEG2-TS with a predetermined symbol and outputs it.
- the example shown here is an example of the MULT I 2 system.
- the RTP packetizer 58 encapsulates each MPEG2-TSP with one or more.
- the RTP packetizer 58 has a counter for counting the path clock that the transceiver 61 reproduces based on the reference time information provided from the communication network. The transceiver 61 will be described later.
- the RTP packetizer 58 adds a header including the time stamp as the counter value and information identifying that the encapsulated information is MPEG2-TSP to the output signal, Output to the subsequent stage.
- This output signal is shown as S12 in FIG. Also, 312 Ding? Is the header. This time stamp is used when the receiver uses the bus clock to correct the jitter when the packet arrives.
- UDP / IP packetizer 59 stores each RTP packet in an IP datagram for transmission to the IP communication network. Then, the UDP / IP packetizer 59 adds an IP packet header to each of the stored RTP packets and outputs the packet as an IP packet. This output signal is shown as S13 in FIG.
- the IP of S13 is a header in a communication protocol such as an IP header. IP Since the contents of the packet header are well known on the Internet, description thereof will be omitted.
- the Ethernet packetizer 60 stores the IP packet in the data area of the Ethernet, adds a header and a checksum to the Ethernet packet, and outputs the packet as an Ethernet packet. The Ethernet bucket header and the checksum are well known on the Internet, and will not be described.
- the transceiver 61 transmits the Ethernet packet to the Internet network. Then, the transceiver 61 receives the above-described reference time information and the like.
- FIG. 11 is a diagram showing a conventional packet configuration.
- 10 MPEG2-TSPs are encapsulated.
- an 8-byte header including MPEG2-TSP identification information and a time stamp used when the packet arrives is added.
- it is converted into an 182-byte RTP packet.
- an 8-byte UDP packet header is added to the RTP packet to form a 1900-byte UDP packet.
- a 24-byte IP bucket header is added to the UDP bucket to make a 1924-byte IP packet.
- a 14-byte Ethernet header and a 4-byte checksum are added to the IP packet to form a 1942-byte Ethernet bucket.
- the maximum transmission bucket unit, MTU is often limited. If the size of the packet data to be sent exceeds the MTU, the packet is often divided on the communication network. On the Internet, such a process is called a fragment.
- the MTU in the Ethernet communication network is 1500 bytes.
- the data size of the data area of the Ethernet bucket exceeds the MTU, fragmentation in the communication network cannot be prevented. Therefore, some packets may lose header information. For this reason, it is difficult for the receiving side to compensate for bucket loss jitter generated after fragmentation.
- FIG. 8 is a diagram showing a configuration of a conventional example of a content receiver.
- FIG. 9 is a flowchart showing the operation from reception of a packet to decoding.
- the receiver 71 receives an Ethernet bucket from a communication network such as the Internet, and outputs the packet to a subsequent stage. This Ethernet bucket is shown in FIG.
- the Ethernet packet processor 72 performs Ethernet protocol processing on the Ethernet packet addressed to the Ethernet packet processor 72, and outputs a UDP / IP packet to the subsequent stage. This process is shown in STEP 91 of FIG. This output signal is shown in S14 of FIG.
- S14 in FIG. 10 indicates that jitter and packet loss have occurred in the received UDP ZIP packet as a result of transmitting and receiving the received UDP / IP bucket via the Internet network.
- the bucket including V I DEOl and DATA1 has a larger delay than the steady delay.
- Packets including VIDEO03 and AUDI02 have a smaller delay than the regular delay.
- the jitter and packet loss of the Internet will be described with reference to FIG.
- packets are assigned different routes, packets cannot be transmitted during the valid time of the packet, packets are deleted at the gateway, and packets are retransmitted. And packet loss occurs.
- the limited delay on the paper is described in an easy-to-understand manner by intentionally expressing the stationary delay to zero. More specifically, the bucket including VIDEO1 and DATA1 has a longer delay than the steady delay, and is described as being slower than S13.
- the bucket containing VI DEO 3 and AUD I O 2 is marked earlier (as though it is moving ahead) than S 13 due to the delay being less than the steady delay.
- the bucket containing VIDEO2 and AUDIO1 has a packet loss.
- the UDPZIP packet processing section 73 shown in FIG. 8 performs UDP IP protocol processing on the UDP / IP packet and outputs an RTP packet. This process is shown in STEP 92 of FIG. The output signal is shown in S15 of FIG.
- Ethernet and UDP / IP protocol processing is performed on the Internet. Description is omitted because it is well known.
- each header includes information indicating the protocol processing method of the data body.
- the processing methods for various protocols are standardized, and the content receiver can be equipped with the processing methods in advance. Therefore, the content receiver can perform the protocol processing of the data body after removing the header by analyzing the information indicating the protocol in the header.
- the RTP bucket processor 79 acquires a header of each RTP packet from each RTP bucket shown in FIG. Further, the RTP packet processor 79 acquires information indicating the contents of the configuration data included in the header.
- the information indicating the contents of the data is information for identifying the format type of the stored data. Here, this information is information for identifying the above-mentioned MP EG2-TSP.
- the RTP bucket processor 79 has a counter that counts the bus clock reproduced by the receiver 71 using the reference time information. The RTP bucket processor 79 counts this bus clock, and if the counted value matches the time stamp in the header, removes the header and outputs MP EG2—TSP to the subsequent stage (STEP in FIG. 9). 93). Then, the RTP packet processor 79 checks whether or not the MPEG2-TSP is scrambled (STEP 94 in FIG. 9). The MPEG 2 — TSP header has information on whether or not the MPEG 2 — TSP is scrambled outside the scrambled range. Therefore, once the MPEG2-TSP is extracted, the information can be confirmed and descramble processing can be performed. It is possible for the receiving side and the transmitting side to decide which method to use in advance, or to confirm and recognize the table information to be received on the receiving side. .
- the descrambler 74 descrambles the MPEG2-TSP by a method corresponding to the scrambling method determined on the transmitting side and outputs the descrambled signal. This process is shown in STEP 9 of FIG. This output signal is shown in S17 of FIG.
- the TS decoder 77 converts 1 ⁇ 1? £ 02-c3? Into a form that the AV decoder 78 can perform AV decoding and outputs (step 97 in FIG. 9).
- AV decoder one 78 The data input to the AV decoder 78 is AV-decoded and output (STEP 98 in FIG. 9).
- STEP 93 of FIG. 9 when the counted value of the bus clock does not match the time stamp in the header 1, the TS decoder 1 77 verifies the difference (STEP 95 in FIG. 9). If the difference is within a range that can be compensated for by a buffer inside a playback controller (not shown), the TS decoder 77 waits for the extended TS packet on this buffer. If the difference exceeds the range that can be compensated by this buffer, the TS decoder 77 controls to discard the corresponding TS packet (STEP 96 in FIG. 9).
- the receiving side cannot compensate for the packet loss occurring in the communication network in real time, and when the packet loss occurs, it becomes a decoy error. It is generated by the count of the bus clock unrelated to the decoding. Also, the reference time information used to generate the bus clock is not sufficiently accurate with respect to the jitter accuracy required for decoding. In addition, this reference time information is affected by the jitter of the communication network. For these reasons, the accuracy of jitter compensation at the time of decoding on the receiving side may be insufficient, resulting in decoding errors.
- the present invention relates to a receiver for receiving and playing back a content formed by a stream composed of a compressed transport bucket from a transmitting side and receiving the content after receiving the content; Playback means for playing back the stored content. Further, if each transport bucket forming the content is an extended transport packet having playback time indication information generated using the system clock of the transport bucket, the playback means stores the transport packet. Each of the stacked extended transport buckets is reproduced at the time determined from the reproduction time instruction information.
- the present invention provides a transmitter for transmitting content formed by a stream composed of compressed transport packets, wherein the transmitting means for transmitting the content, and the receiving side is transmitted from the storage means using the system clock of the transport packet A reproduction time instruction information generating means for generating reproduction time instruction information for instructing a reproduction time.
- the transmitting means transmits an extended transport packet in which reproduction time indication information is added to each transport packet to be transmitted.
- FIG. 1 is a block diagram of a content transmitter according to Embodiment 1 of the present invention.
- FIG. 2 is a block diagram of a content receiver according to Embodiment 1 of the present invention.
- FIG. 3 is a diagram showing a first operation flowchart in the content receiver according to the first embodiment of the present invention.
- FIG. 4 is a diagram showing a second operation flowchart in the content receiver according to the first embodiment of the present invention.
- FIG. 5 is a diagram showing the transition of the bucket configuration according to the first embodiment of the present invention.
- FIG. 6 is a diagram showing an Ethernet packet configuration according to the first embodiment of the present invention.
- FIG. 7 is a block diagram of a conventional content transmitter
- Figure 8 shows a block diagram of a conventional content receiver.
- Fig. 9 is a flowchart showing the operation of the conventional content receiver.
- FIG 10 shows the transition of the conventional packet configuration
- FIG 11 shows the conventional packet configuration
- FIG. 12 is a block diagram of a content receiver according to Embodiment 2 of the present invention.
- FIG. 13 is a block diagram of the IE 13 9 4 interface of the content receiver according to the second embodiment of the present invention.
- FIG. 14 is a diagram showing a packet configuration transition according to the second embodiment of the present invention.
- FIG. 15 shows a first IEEE 1394 bucket configuration according to Embodiment 2 of the present invention.
- FIG. 16 shows a second IEEE 1394 packet configuration according to the second embodiment of the present invention.
- FIG. 1 is a diagram illustrating a configuration of a content transmitter according to the first embodiment.
- FIG. 5 is a diagram showing transition of the bucket configuration in the content transmitter and the content receiver according to the first embodiment.
- FIG. 6 is a diagram illustrating a configuration of a packet according to the first embodiment.
- a microcomputer 14 controls each part of the content transmitter.
- the video encoder 1 encodes the video signal by a predetermined compression method and outputs the video signal to a subsequent stage.
- the MPEG2 system is shown as an example, and the output signal output from the encoder 1 is composed of MPEG2-TSP.
- System clock generator 4 generates a 27 MHz clock.
- the system clock used when the video encoder 11 encodes a video signal is this 27 MHz clock.
- the audio encoder 1-2 encodes the audio signal using the same compression method as the video encoder 11 and outputs MPEG2-TSP to the subsequent stage.
- the data encoder 13 encodes data such as data broadcasts and EPG data using the same compression method as the video encoder 11, and outputs MPEG2-TSP to the subsequent stage.
- the stream multiplexer 4 multiplexes the above three types of MPEG2-TSP on the time axis. Further, the stream multiplexer 4 generates a PCR signal for reproducing the system clock on the receiving side by using a counter for counting the system clock.
- the PCR signal is generated at a period of about 50 ms. Then, the stream multiplexer 4 converts the PCR signal to MPEG2-TSP, further multiplexes the PCR signal into the multiplexed signal, and outputs the multiplexed signal as MPEG2-TS. This output signal is shown as S1 in FIG.
- FIG. 5 is a diagram showing the transition of bucket multiplexing on the time axis.
- the horizontal axis in Fig. 5 is time. However, in Fig. 5, the steady delay in each process is Ignored and not shown.
- VIDE 51, VIDEO2, VIDEO3, AUDI ⁇ 1, AUDIO2, and DATA1 of S5 are packets multiplexed by the stream multiplexer 5.
- 31 ⁇ 10 £ ⁇ 1, VI DEO 2 and VIDE ⁇ 3 are video encoded MP EG 2—TSP.
- AUD I ⁇ 1 and AUD I02 of S1 are audio encoded MPEG2-TSP.
- DATA1 of S1 is a data encoded MPEG2-TSP. Since the PCR signal is well known in the MPEG2 system, its description is omitted.
- the scrambler 6 encrypts the MPEG2-TS using a predetermined symbol system and outputs it.
- the example shown here is an example of the MULT I 2 system.
- the time stamp adder 7 has a counter that counts the system clock output from the system clock generator 4. Then, the time stamp adder 7 includes the count value in the header as a time stamp, adds this header to each MPEG 2—TS (in this example, scrambled), and adds it to the subsequent stage as an extended TS packet. Output.
- This output signal is shown as S2 in FIG.
- the TS in Fig. 5 indicates a header including a time stamp. The receiving side does not use this timestamp to determine the system clock.
- the receiving side ignores the packet generation timing on the transmitting side and stores the packet in the storage device. Then, the receiving side uses this time stamp to determine the timing of bucket generation at the transmitting side (to reproduce MPEG2-TS) when playing back the stored packets.
- the counter and the counter that generates the PCR signal are synchronized because they use the same system clock.
- the frequency of the system clock, the maximum speed of the extended TS packet to be transmitted, and the minimum size of the storage device 32 on the receiving side to be described later are determined in advance. . Then, the number of bits of this counter is set so that all the extended TS packets to be transmitted during the round of the count can be stored.
- the size of the storage device is sufficiently large. Since it is secured, there is no problem that the receiving side cannot secure the playback time.
- this counter when adding a time stamp, this counter is initialized at a predetermined timing according to the count value of the PCR signal, so that it is synchronized with the count value used to generate the PCR signal. I do.
- the counter is initialized after a predetermined offset time and then time stamped. This allows the receiving side to use the counter for system clock reproduction by the PCR as the counter for MPEG2-TS reproduction.
- the counter on the receiving side can be synchronized with this counter. In this case, it is desirable to match the number of bits of this counter with the number of bits of the counter for generating the PCR signal. By doing so, the carryover process on the receiving side can be simplified.
- the supercapsulator 8 encapsulates each extended TS packet by one or more. Also, a header including information for identifying that the encapsulated information is an extended TS packet, the packet length of the extended TS packet in the capsule, the number of extended TS packets, and the capsule counter value is included in the output signal. In addition, it is output to the subsequent stage as a super pusher.
- This super capsule is shown at S3 in FIG. Further, CH in FIG. 5 indicates a header. This capsule counter value is used to confirm the continuity of the super capsule on the receiving side. Then, every time the supercapsulator 8 outputs a supercapsule, the supercapsulator 8 counts up the capsule counter value.
- the present embodiment does not limit the number of extended TS packets.
- the information in the additional header in the supercapsule is intended to store the content of the encapsulated data and information for confirming the continuity at the receiving side, and is limited to the format described above. Not something.
- the capsule counter value may be included as the extended TS bucket count value and information on the number of extended TS buckets may be included.
- the bucket length and the number of extended TS buckets of the extended TS bucket may be the total data length encapsulated.
- the super encapsulation machine 8 The super capsule is output to the storage buffer 15 together with the output of the super capsule.
- the accumulation control to the accumulation buffer 15 is performed by the microcomputer 14 in a ring buffer system.
- the microcomputer 14 manages the area for storing the super capsule of the storage buffer 15 and the header information of each super capsule.
- the retransmission command detector 13 detects the retransmission command output by the receiver 12. Then, at the time of retransmission control of the supercap cell, the retransmission command detector 13 specifies the information (at least the power cell counter value in this example) for specifying the supercapsule included in the retransmission command and requiring retransmission, and instructs retransmission. Information to be output to the microcomputer 14.
- the microcomputer 14 reads out the super capsule corresponding to the capsule counter value from the storage buffer 15. Thereafter, the microcomputer 14 controls the output to the UDPZIP packetizer 9 to retransmit the super capsule.
- information indicating that the packet is a retransmission packet may be added to the header of the supercapsule and output.
- the counting range of the capsule counter value can cover at least twice the maximum delay time (the delay from the transmission of the supercapsule to the reception of the retransmission command) in the communication network for the transmission speed of the supercapsule Desirably the number of bits.
- the storage buffer size is at least enough to store the supercapsules in the counting range of the capsule count.
- the format of the retransmission command may be determined in advance with the receiving side. In this embodiment, the format of the retransmission command is not particularly limited.
- the UDPZIP packetizer 9 stores various super capsules in an IP datagram for transmission to an IP communication network, adds an IP bucket header, and outputs the packet as an IP packet.
- This output signal is shown as S4 in FIG.
- the IP of S4 indicates a header in a communication protocol such as an IP header. Since the IP packet header is well known on the Internet, its description is omitted. In this example, the IP bucket header is further stored in the UDP bucket, but this is not necessary. Further, another protocol, for example, an IP bucket header may be stored in a TCP bucket.
- the Ethernet packetizer 10 is input to the Ethernet packetizer 10.
- IP bucket is stored in the Ethernet data area.
- the Ethernet packetizer 10 adds an Ethernet packet header and a checksum to the IP packet and outputs the packet as an Ethernet packet.
- the Ethernet packet header and the checksum are well-known on the Internet and will not be described.
- the transmitter 11 transmits an Ethernet packet to the Internet network.
- various carriers operate communication networks in various formats, and the transmitter 11 and the receiver 12 correspond to these various formats. There are no particular restrictions on the form or specifications.
- FIG. 6 is a diagram showing an Ethernet packet configuration in the present embodiment.
- seven extended TS buckets each of which has a 4-byte header including a time stamp added to MPEG2—TSP, are encapsulated.
- an 8-byte header including the identification value for identifying the extended TS packet, the capsule counter value, the extended TS packet size, and the number of the extended TS packets is added, and a 1352-byte super capsule is added.
- an 8-byte UDP packet header is added to the super capsule to make a 1356-byte UDP packet.
- a header of a 24 byte IP packet is added to the UDP packet to make the IP packet of 130 bytes.
- a 14-byte Ethernet header and a 4-byte checksum are added to the IP packet to form a 1398-byte Ethernet packet.
- the maximum transmission bucket unit, MTU In a communication network, the maximum transmission bucket unit, MTU, is often limited. When the size of the packet data to be transmitted exceeds the MTU, the packet is often divided on the communication network. On the Internet, such a process is called a fragment. It is difficult for the receiver to compensate for packet loss and jitter that occur after fragmentation. This is due to the loss of header information. Therefore, in the present embodiment, the number of extended TS packets in the super capsule is set to seven. This is to prevent the data size of the data area of the Ethernet packet from exceeding the MTU 1500 bytes in the Ethernet communication network.
- the data size of MPEG 2—TSP is 18 8 bytes according to the specifications of the encoder. Is fixed. Therefore, the data size of the extended TS packet is 192 bytes.
- the maximum number of extended transport buckets that can be stored in the supercapsule while satisfying the MTU 1500 byte in the Ethernet communication network is a maximum of seven.
- the communication network is not limited to the Internet using Ethernet.
- a USB may be used, or a wireless communication network such as a mobile phone may be used.
- the MTU can correspond to a value corresponding to them.
- the compression method is not limited to MPEG2.
- M PEG 4 or another method may be used.
- a microcomputer 29 controls each part of the content receiver.
- the receiver 21 receives and outputs the Ethernet packet shown in FIG. 6 from a communication network such as the Internet network.
- a communication network such as the Internet network.
- various telecommunications carriers operate communication networks using various methods, and the receiver 21 and a transmitter 31 described later correspond to those methods.
- the communication network is not limited to the Internet using Ethernet, and may use a USB or a wireless communication network such as a mobile phone.
- the Ethernet packet processor 22 performs Ethernet protocol processing on the Ethernet packet corresponding to the Ethernet packet processor 22 and outputs a UD PZIP packet (this processing is shown in STEP 51 of FIG. 3. This output signal is shown as S5 in Fig. 5).
- S5 in Fig. 5 means that jitter and bucket loss have occurred as a result of the received UDP IP packet passing through the Internet network.
- VIDEO The packet containing 1 and DATA 1 has a larger delay than the regular delay. Packets containing VI DEO 3 and AUD I ⁇ 2 have a smaller delay than the regular delay. In addition, the packet including VI DE02 and AUD IO 1 becomes a bucket loss once and is retransmitted later.
- the jitter and packet loss in the case of the In-net network will be described with reference to FIG.
- all packets are transmitted with their steady delay, in which case no jitter or packet loss occurs.
- packets are assigned different routes, packets cannot be transmitted during the valid time of the packet, the packet is deleted by the gateway, and the bucket is retransmitted. Packet loss occurs.
- S5 the limited delay on the paper is clearly indicated by dare expressing the constant delay to zero. More specifically, the bucket including VIDEO 1 and DATA1 has a longer delay than the steady delay, and is described as being slower than S4.
- Packets containing VIDEO 3 and AUD I O 2 are marked earlier (as if they were ahead) than S 4 because they have a smaller delay than the regular delay. It also indicates that packets containing VIDEO 2 and AUD IO 1 have been lost once and are retransmitted later.
- the UDPZ IP packet processing unit 23 shown in FIG. 2 performs UD PZ IP protocol processing on the UDP / IP bucket and outputs a super capsule (this processing is shown in STEP 52 of FIG. 3. (See S6 in Figure 5).
- Ethernet and UDP / IP protocol processing are well known on the Internet, and thus description thereof is omitted. Also, the processing of Ethernet packets and UDP packets is not limited to the contents described here, but depends on the type of receiving bucket and the specifications of the communication network. Further, other communication protocol processing may be performed.
- each of these communication protocols information indicating the protocol processing method of the data body is included in each header.
- the processing methods for various protocols are standardized, and the content receiver can be equipped with the processing methods in advance. Therefore, the content receiver analyzes the information indicating the protocol in the header, After the header is deleted, protocol processing of the data body can be performed.
- the capsule processor 24 obtains the header of each supercapsule from each supercapsule shown in FIG. Further, the capsule processor 24 outputs information indicating the content of the configuration data included in the header to the microcomputer 29.
- the information indicating the content of the data is information for identifying the format type of the encapsulated data (in this example, information for identifying the extended TS packet described above).
- the information indicating the content of this data includes information indicating the bucket length and the number of extended TS buckets of the extended TS packet in the capsule.
- the information indicating the packet length of the extended TS packet and the number of extended TS buckets may be the total data length encapsulated.
- the microcomputer 29 interprets the information indicating the content of the given data and recognizes that the encapsulated data is an extended TS bucket (STEP 53 in FIG. 3).
- the microcomputer 29 recognizes the size of each extended TS packet and secures a storage area of the storage device 32.
- the microcomputer 29 also prepares the storage controller 28 for setting the storage bucket size and initial setting of the address when storing each extended TS packet (STEP 50 in FIG. 3). These preparations may be made when the first super capsule is input or when it is detected that the information indicating the data content has changed.
- the capsule processor 24 monitors the capsule force center contained in the header to check the continuity (Step 54 in FIG. 3).
- the capsule processor 24 detects a capsule count value in each supercapsule and checks a discontinuity point. If the capsule processor 24 detects a discontinuity point, it verifies the discontinuity based on the transition of the capsule counter (STEP 64 in Fig. 3).
- the capsule processor 24 detects that the capsule counter value detected after the discontinuity point exceeds the capsule counter value immediately before the discontinuity point. Delete the super capsule until the discontinuity is resolved (STEP 65 in Fig. 3). .
- the capsule processor 24 does not delete the super capsule corresponding to the discontinuity. And power The capsule processor 24 notifies the microcomputer 29 that the discontinuous point has been detected, and outputs the capsule counter value corresponding to the supercapsule that the capsule processor 24 could not receive to the microcomputer 29.
- the capsule processor 24 generates a dummy super capsule having a dummy header composed of a dummy extended TS packet. Then, the capsule processor 24 inserts this dummy supercapsule into the time space corresponding to the supercapsule that the capsule processor 24 could not receive and outputs it to the subsequent stage (STEP 66 in FIG. 3). This is to simplify the retransmission packet insertion process at a later stage.
- the microcomputer 29 receives the notification from the capsule processor 24 and outputs a retransmission command for instructing the super capsule to retransmit. At this time, the microcomputer 29 generates this retransmission command using the capsule counter value corresponding to the supercapsule that the capsule processor 24 could not receive (STEP 67 in FIG. 3). Sends a resend command to the sender via a communication network such as the Internet using Ethernet.
- the capsule processor 24 can detect the supercapsule. Therefore, the capsule processor 24 removes the discontinuity from the object of the above-described verification of the discontinuity, and outputs it as it is to the subsequent stage. (STEP 54 in FIG. 3).
- the microcomputer 29 does not have to control the retransmission command transmission immediately after receiving the discontinuity notification from the capsule processor 24.
- the microcomputer 29 instructs the capsule processor 24 to wait for reception of a super capsule that could not be detected, and controls the retransmission command transmission when the corresponding super capsule has not been received for a predetermined period of time. May be done. If reception is possible within a predetermined time after instructing reception standby, the capsule processor 24 adds information indicating a retransmission packet within a predetermined header and outputs it to the subsequent stage. This is because the packet is processed in the subsequent stage in the same manner as the retransmission packet.
- the waiting time is shorter than the rounding time of the capsule counter value and longer than the maximum delay time of packet arrival in the communication network.
- the capsule processor 24 separates and outputs the extended TS packet encapsulated under the control of the microcomputer 29.
- the header containing the MPEG2—TSP and the time stamp are included. Output separately.
- Microcomputer 29 checks whether MPEG2—TSP is scrambled (Step 55 in FIG. 3).
- the MPEG 2 — TSP header has information about whether or not it is scrambled outside the range to be scrambled. Therefore, the microcomputer 29 can take out the MPE G2-TSP once, confirm the information, and perform the descrambling process on the scrambled range.
- the receiving side and the transmitting side decide which method to use in advance, or the receiving side confirms and recognizes the table information to be received. is there.
- the descrambler 25 descrambles the MP EG2—TSP input to the descrambler 25 by a method corresponding to scrambling on the transmission side, and outputs it to the subsequent stage.
- the header including the time stamp is delayed by the processing time of the descrambler 25 in the time stamp buffer 26, synchronized with the MPEG-2—TSP in time, and then output to the subsequent stage (STEP in FIG. 3). 56).
- the microcomputer 29 also checks whether the packet is a retransmission packet (STEP 68 in Fig. 3).
- the retransmission bucket has information indicating the retransmission bucket in the header. Therefore, the microcomputer 29 checks the packet to see if it is a retransmission packet.
- information indicating that the packet is a retransmission bucket, and a header to which a capsulation counter value is further added are generated and output to the time stamp buffer 126 (FIG. 3, STEP 69).
- the extended TS reproducer 27 combines the MPEG2-TS and the header to reproduce and output the extended TS packet. This process is shown in STEP 57 of FIG. This output signal is shown in S7 of FIG.
- the storage controller 28 checks whether or not the extended TS packet is reacquired due to a delay or a source in the communication network based on the header information (STEP 58 in FIG. 3). If the packet is not a retransmission packet, control the microcomputer 29. The extended TS packets are sequentially written to the managed area on the storage device 32 (STEP 59 in FIG. 3). If the packet is a retransmission bucket, a dummy one extended TS packet and dummy super capsule are generated in STEP 66. Then, the re-acquired extended TS packet is overwritten in the corresponding dummy extended TS bucket already stored (STEP 60 in FIG. 3).
- the retransmitted extended TS packet contains the capsule counter value.
- the microcomputer 29 manages the capsule counter value and the address of the storage device 32. Based on these facts, this overwrite control compensates for continuity in the storage device 32 by storing the retransmitted extended TS packets in the original storage area (the area where dummy extended TS packets are temporarily stored and secured). (S8 in Fig. 5).
- the retransmitted extended TS packets of VIDEO2 and AUD I ⁇ 1 are stored in their original locations.
- the storage device 32 since the storage device 32 stores the arrival time and the transmission time on the transmission side without referring to the time, each extended TS packet can be efficiently stored.
- the storage device 32 may be any storage medium such as an HDD or a DVD, or may be a semiconductor memory. Further, if the retransmission control is simplified and the control is performed only for the jitter compensation, the capacity required for the storage device 32 is also reduced to a range where all the extended TS packets received during the time when the counter described later makes one round can be stored.
- the microcomputer 29 confirms that no extended TS packet is stored. For example, if this is a normal MPEG2-TSP, check whether it is scrambled in the same way (STEP 61 in Fig. 3). If it is scrambled, it is descrambled by the descrambler 25 (STEP 62 in FIG. 3). Then, the extended TS player 27 generates and adds a header including a time stamp to the extended TS packet, outputs the extended TS packet (STEP 63 in FIG. 3), and stores it in the storage device 32 similarly. In this case as well, the subsequent reproduction processing can be shared. However, in this case, jitter compensation and packet loss compensation are the same as in the conventional example.
- the reproduction controller 33 has a counter for counting the system clock.
- the playback controller 33 sets the count value of the counter to the PCR signal output from the TS decoder 34 so that the result becomes equal. Controls the frequency of the system clock. That is, the system clock can be reproduced using the existing MPEG transport system as it is. Therefore, at the time of playback, the specifications of the MPEG transport system can be easily satisfied using existing technology. Further, under the control of the microcomputer 29, the reproduction controller 33 sequentially reads out the extended TS packets stored in the storage device 32 in synchronization with this system clock (STEP 71 in FIG. 4).
- the playback control unit 33 removes the header including the time stamp at the timing when the individual time stamps and the count value of the above-mentioned counter have a predetermined offset value (STEP 72 in FIG. 4). . Then, the reproduction controller 33 outputs each MPEG2-TSP to the subsequent stage. This process is shown in STEP 73 of FIG. This output signal is shown in S9 in FIG.
- the MPEG2-TS on the transmitting side has been reproduced, and the jitter generated in the communication network has been compensated.
- the transmission side uses the PCR signal. Therefore, the reproduction controller 33 can compare the count value of this counter obtained from the PCR signal with the time stamp.
- the TS decoder 34 converts the MPEG2_TSP into a form that the AV decoder 35 can perform AV decoding and outputs.
- the AV decoder 35 performs AV decoding on the data input to the AV decoder 35 and outputs the data. If the time stamp does not match the system clock counter value in STEP 72, the reproduction controller 33 verifies the difference (STEP 75 in FIG. 4). If the difference is within a range in which jitter can be compensated for in a buffer (not shown) inside the reproduction controller 33, the extended TS packet is made to wait on the buffer. If the difference exceeds the range in which jitter can be compensated by the buffer inside the playback controller, control is performed to discard the corresponding extended TS packet (STEP 76 in Fig. 4).
- FIG. 6 shows an example in which the number of extended TS packets in a supercapsule receives seven Ethernet packets (1398 bytes).
- the data area has a 1356 byte UDP / IP bucket, The data area has a 1352 byte super capsule.
- the supercapsule encapsulates seven extended TS packets with a 4-byte header including a time stamp added to MPEG2-TSP.
- the super capsule has an 8-byte header including an identification value for identifying an extended TS packet, a capsule count value, an extended TS packet size, and the number of extended TS packets.
- the maximum transmission bucket unit, MTU is often limited. If the packet data size exceeds the MTU, the packet is often divided on the communication network.
- the number of extended TS packets in the super capsule is set to seven. This is to prevent the data size of the data area of the Ethernet packet from exceeding the MTU 1500 byte in the Ethernet communication network.
- the data size of MPEG2-TSP is fixed at 188 bytes according to the specifications of the encoder. Therefore, the data size of the extended TS packet is 192 bytes, and the maximum number of extended transport buckets that can be stored in a super capsule while satisfying the MTU 150 bytes in the Ethernet communication network is a maximum of seven.
- the time stamp for playback included in each extended TS packet is used to accurately compensate for jitter generated in the communication network with the accuracy of the system clock. Further, as described above, the compensation is performed efficiently and reliably by the joint control of the jitter compensation for controlling the decoding timing of the content transmitter and the content receiver and the packet loss compensation for the retransmission control.
- the communication network is not limited to the Internet using Ethernet.
- a USB or a wireless communication network such as a mobile phone may be used.
- the compression method is not limited to MPEG2.
- MP EG 4 or another method may be used.
- the playback controller 33 outputs MPEG2-TSP from the content receiver to the AV decoder connected to the bus.
- the reproduction controller 33 is connected to an external output interface such as an IEEE 1394 interface (not shown).
- MPEG2-TSP is stored in an isochronous bucket defined by the interface.
- the TS decoder 134 may be connected to an external output interface such as an IEEE1394 interface (not shown), and the output of the TS decoder 34 may be transmitted to an external AV decoder.
- the external output interface stores and outputs MP EG2-TSP in an isochronous bucket defined by the interface standard.
- FIG. 12 is a diagram illustrating a configuration of a content transmitter according to the second embodiment.
- FIG. 13 is a diagram showing the configuration of the IEEE 1394 interface according to the second embodiment.
- FIG. 14 is a diagram showing the transition of the bucket configuration in the content receiver according to the second embodiment.
- FIGS. 15 and 16 are diagrams showing the configuration of the packet transmitted by the IEEE 1394 interface according to the second embodiment.
- the configuration and operation up to the storage of the bucket received from the Internet network by the storage device 32 are the same as those of the first embodiment, and thus the description thereof is omitted.
- the read controller 36 reads the extended TS bucket stored in the storage device 32 in accordance with an instruction from the microcomputer 29 in synchronization with a clock of a predetermined frequency generated by the extended TS bucket read clock generator 37. In this case, a predetermined time interval is inserted between the extended TS buckets as shown by S10 in FIG. 14 and output (S10 in FIG. 14).
- the interval is set according to the clock frequency of the clock regenerator 37 so that the bit rate of the extended TS bucket after the insertion of the time interval is equal to or greater than the bit rate of the content transmitter when the extended TS packet is transmitted.
- the IE EE 1394 interface 38 conforms to the IEEE 1394 standard.
- the IEEE 1394 interface 38 outputs the extended TS packet input to the IEEE 1394 interface 38 in the asynchronous transfer mode (S11 in FIG. 14).
- S11 ISO is a header added by the IEEE 1394 interface.
- the transmission signal between the read controller 36 and the IEEE 1394 interface 38 is composed of a data signal, a clock signal, a packet state signal, and a data enable signal as in the case of MPEG2-TS.
- the extended TS bucket information is set in the IEEE 1394 interface 38 by the microcomputer. This will be explained.
- FIG. 13 is a diagram showing the configuration of the IEEE 1394 interface 38.
- the stream of the extended TS packet is input to the MPEG2 interface 41.
- the DTCP encryption circuit 42 encrypts the extended TS packet output from the MPEG2 interface 41 for the purpose of copyright protection in accordance with the DTCP (Digital Transcription Control Protocol) standard. And output.
- the header adding circuit 43 adds a header to the packet subjected to the DTCP encryption and outputs the packet. This header is a header necessary for isochronous transfer.
- Information specifying the format of the extended TS packet is input to the bucket format information adding circuit 44 from the microcomputer via the host interface 46. Then, the packet format information adding circuit 44 performs a process of writing, at a predetermined position in the header, information for identifying the data format of the bucket to be asynchronously transferred from the extended TS bucket.
- Information specifying the data size of the extended TS bucket is input from the microcomputer to the bucket data size adding circuit 45 via the host interface 46. Then, the packet data size information adding circuit 45 calculates and determines the data size of the isochronous packet based on the information. Alternatively, the packet data size information addition circuit 45 receives information on the size of the asynchronous packet for storing the extended TS bucket from the microcomputer via the host interface 46. Is done. Then, the packet data size information adding circuit 45 performs a process of writing information on the data size of the packet to be transmitted asynchronously to a predetermined position of the header.
- FIG. 15 is a diagram illustrating an example in which only an isochronous header is added to an extended TS packet. In this case, write only the packet data size in the data length area shown in Fig. 15. If the data size of the extended TS packet is 192 bytes, the data size is 576 bytes, which is 3 times 192, and 588 bytes, which is the sum of one asynchronous header and 12 bytes of data CRC. Write to the 15-day long field.
- FIG. 16 is a diagram illustrating an example in which the extended TS packet includes an isochronous header and a common header.
- the packet data size is written in the data length area of the isochronous header in FIG. 16 and information for identifying the extended TS packet is written in the format area of the common header. If the data size of the extended TS packet is 192 bytes, the number obtained by adding 4 and 192 in the Reserved area is tripled to 588 bytes, and the data size of the synchronous header, common header, and common header is 588 bytes.
- the Reserved area is an area for future expansion.
- the information for identifying the extended TS packet is the data that is determined in advance as the content transmitting side within the range excluding the currently operating data, if any.
- FIGS. 15 and 16 show examples of asynchronous packets in which three extended TS packets are stored, but the number of packets is not limited to three.
- the number of buckets can be four, two, or one.
- the data size of the extended TS packet is an example of 192 bytes, but is not particularly limited.
- the data size of the extended TS packet may be 196 bytes.
- An IE EE 1394 isochronous bucket transmission circuit 47 shown in FIG. 13 implements a data link layer and a physical layer protocol in accordance with the IE EE 1394 standard. It is composed of circuits.
- the IEEE 1394 isochronous packet transmission circuit 47 transmits the packet to which the header 1 added to the IEEE 1394 isochronous packet transmission circuit 47 is added. Send to the bus.
- a TS decoder 1 (not shown) and an AV decoder (not shown) are separately connected on the 1394 bus. The effects described can be achieved.
- the content receiver of the present invention it is possible to prevent a packet loss occurring in a communication network from being compensated on the receiving side and to prevent a packet loss from occurring when a packet loss occurs. It is useful for digital television broadcast receivers, personal computers, mobile phones, portable information terminals and mobile phone adapters.
- the data can be efficiently stored in the storage device on the receiving side ignoring the arrival time when storing the data. Also, at the time of reproduction, reproduction can be performed with the accuracy required by the decoder using a time stamp indicating the time to output to the decoder. This prevents decoding errors when the jitter compensation accuracy is insufficient for decoding, and is useful for digital television broadcast receivers, personal computers, mobile phones, personal digital assistants, and mobile phone adapters. It is.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Compression Or Coding Systems Of Tv Signals (AREA)
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03741425.7A EP1553774B1 (en) | 2002-07-16 | 2003-07-16 | Content receiving apparatus and content transmitting apparatus |
CN038164469A CN1669320B (zh) | 2002-07-16 | 2003-07-16 | 内容接收器 |
AU2003281136A AU2003281136A1 (en) | 2002-07-16 | 2003-07-16 | Content receiving apparatus and content transmitting apparatus |
JP2004521223A JP4042745B2 (ja) | 2002-07-16 | 2003-07-16 | コンテンツ受信器 |
US10/515,528 US7830881B2 (en) | 2002-07-16 | 2003-07-16 | Content receiver and content transmitter |
US12/899,074 US8503471B2 (en) | 2002-07-16 | 2010-10-06 | Content receiver and content transmitter |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002-206780 | 2002-07-16 | ||
JP2002206780 | 2002-07-16 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10515528 A-371-Of-International | 2003-07-16 | ||
US12/899,074 Continuation US8503471B2 (en) | 2002-07-16 | 2010-10-06 | Content receiver and content transmitter |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004008760A1 true WO2004008760A1 (ja) | 2004-01-22 |
Family
ID=30112803
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/009043 WO2004008760A1 (ja) | 2002-07-16 | 2003-07-16 | コンテンツ受信器およびコンテンツ送信器 |
Country Status (7)
Country | Link |
---|---|
US (2) | US7830881B2 (ja) |
EP (1) | EP1553774B1 (ja) |
JP (3) | JP4042745B2 (ja) |
KR (2) | KR100784874B1 (ja) |
CN (1) | CN1669320B (ja) |
AU (1) | AU2003281136A1 (ja) |
WO (1) | WO2004008760A1 (ja) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006014153A (ja) * | 2004-06-29 | 2006-01-12 | Nec Commun Syst Ltd | パケットエラー監視型mpegデコーダ、mpeg映像伝送システム及びmpeg映像伝送方法 |
JP2007266875A (ja) * | 2006-03-28 | 2007-10-11 | Toshiba Corp | 映像データの処理方法及び無線通信装置 |
JP2007329606A (ja) * | 2006-06-07 | 2007-12-20 | Hitachi Ltd | 中継装置 |
JP2008511214A (ja) * | 2004-08-20 | 2008-04-10 | ソニー エレクトロニクス インク | データストリーム通信装置及びデータストリーム通信方法 |
JP2009081658A (ja) * | 2007-09-26 | 2009-04-16 | Kyocera Corp | 署名検証方法および受信装置 |
JP2009081564A (ja) * | 2007-09-25 | 2009-04-16 | Kyocera Corp | 署名検証方法および受信装置 |
JP2009081560A (ja) * | 2007-09-25 | 2009-04-16 | Kyocera Corp | 署名検証方法、ストリーム生成方法、受信装置、およびストリーム送信装置 |
US7830881B2 (en) | 2002-07-16 | 2010-11-09 | Panasonic Corporation | Content receiver and content transmitter |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1430706A4 (en) * | 2001-06-11 | 2011-05-18 | Broadcom Corp | SYSTEM AND METHOD FOR MULTI-CHANNEL VIDEO AND AUDIO CODING ON A SINGLE CHIP |
KR100608715B1 (ko) * | 2003-09-27 | 2006-08-04 | 엘지전자 주식회사 | QoS보장형 멀티미디어 스트리밍 서비스 시스템 및 방법 |
JP2005204001A (ja) * | 2004-01-15 | 2005-07-28 | Hitachi Ltd | データ配信サーバ、ソフトウェア、及びシステム |
KR100631758B1 (ko) * | 2004-05-04 | 2006-10-09 | 삼성전자주식회사 | 멀티 스트리밍 포맷을 지원하는 네트워크 i/f 카드 및그 방법 |
US20060007943A1 (en) * | 2004-07-07 | 2006-01-12 | Fellman Ronald D | Method and system for providing site independent real-time multimedia transport over packet-switched networks |
JP4421537B2 (ja) | 2005-09-14 | 2010-02-24 | 株式会社東芝 | ストリーム生成装置 |
KR100739740B1 (ko) * | 2005-10-17 | 2007-07-13 | 삼성전자주식회사 | 방송 녹화 장치 및 방법 |
KR100800690B1 (ko) * | 2006-02-10 | 2008-02-01 | 삼성전자주식회사 | 디지털 방송 서비스 시스템에서 방송 데이터 전송 장치 및방법 |
FR2898453A1 (fr) * | 2006-03-13 | 2007-09-14 | Thomson Licensing Sas | Transmission d'un signal genlock sur un reseau ip |
US7672393B2 (en) * | 2006-08-02 | 2010-03-02 | Richtek Technology Corporation | Single-wire asynchronous serial interface |
US8363541B2 (en) * | 2006-12-22 | 2013-01-29 | Pratt & Whitney Canada Corp. | Serial digital communication protocol |
US8145775B2 (en) * | 2007-05-08 | 2012-03-27 | Canon Kabushiki Kaisha | Method to receive UDP response messages across multiple incoming UDP ports |
EP2028857A1 (en) * | 2007-08-21 | 2009-02-25 | Alcatel Lucent | Method and system for pausing and resuming a real-time data stream |
US8477793B2 (en) * | 2007-09-26 | 2013-07-02 | Sling Media, Inc. | Media streaming device with gateway functionality |
US7908404B1 (en) * | 2007-11-09 | 2011-03-15 | Qlogic, Corporation | Method and system for managing network and storage data |
US8824511B2 (en) * | 2008-03-27 | 2014-09-02 | Nec Corporation | Clock synchronization system, node, clock synchronization method, and program |
FR2939993B1 (fr) * | 2008-12-12 | 2010-12-17 | Canon Kk | Procede de transmission d'un flux de donnees multi-canal sur un tunnel multi-transport, produit programme d'ordinateur, moyen de stockage et tetes de tunnel correspondantes |
JP5549221B2 (ja) * | 2009-12-28 | 2014-07-16 | ソニー株式会社 | 再生装置、再生制御方法、およびプログラム |
US8514329B2 (en) | 2011-05-31 | 2013-08-20 | Motorola Mobility Llc | Jitter estimation for MPEG receivers |
JP2012257041A (ja) | 2011-06-08 | 2012-12-27 | Sony Corp | 通信装置、通信システム、通信方法及びプログラム |
US9451313B2 (en) | 2011-06-29 | 2016-09-20 | Harman International Industries, Incorporated | Network media adapter |
EP2798843A4 (en) * | 2011-12-28 | 2015-07-29 | Intel Corp | SYSTEMS AND METHOD FOR INTEGRATED METADATA INSERT IN A VIDEO CODING SYSTEM |
US20140369222A1 (en) * | 2012-01-26 | 2014-12-18 | Electronics And Telecommunications Research Institute | Method for estimating network jitter in apparatus for transmitting coded media data |
GB2499261B (en) * | 2012-02-10 | 2016-05-04 | British Broadcasting Corp | Method and apparatus for converting audio, video and control signals |
WO2013173683A1 (en) * | 2012-05-18 | 2013-11-21 | Motorola Mobility Llc | Synchronizing multiple transcoding devices utilizing simultaneity of receipt of multicast packets |
JP6505413B2 (ja) * | 2013-11-08 | 2019-04-24 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 送信方法、受信方法、送信装置、及び受信装置 |
JP6298305B2 (ja) * | 2014-01-23 | 2018-03-20 | 株式会社メディアリンクス | 放送信号ip伝送システムおよび放送信号ip伝送方法 |
CN110071785B (zh) * | 2014-06-24 | 2021-10-26 | 株式会社索思未来 | 接口方法 |
US9723610B2 (en) * | 2015-04-07 | 2017-08-01 | Qualcomm Incorporated | Multi-layer timing synchronization framework |
CN108600861A (zh) * | 2018-03-26 | 2018-09-28 | 南京地铁建设有限责任公司 | 基于城市轨道乘客信息系统的音视频数据包包长调整方法 |
US10848539B2 (en) | 2018-09-20 | 2020-11-24 | Cisco Technology, Inc. | Genlock mechanism for software pacing of media constant bit rate streams |
JP7210272B2 (ja) * | 2018-12-28 | 2023-01-23 | 株式会社東芝 | 放送システム、エンコーダ、多重化装置、多重化方法、系統切替装置、および同期制御装置 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10313350A (ja) * | 1997-05-13 | 1998-11-24 | Matsushita Electric Ind Co Ltd | 通信システム |
JPH1188856A (ja) * | 1997-09-05 | 1999-03-30 | Hitachi Ltd | 伝送プロトコル変換方式およびプロトコル変換装置を用いたcatvネットワーク接続方式 |
JP2000307637A (ja) * | 1999-04-16 | 2000-11-02 | Nec Corp | マルチメディア端末装置及び網間接続装置 |
JP2001016267A (ja) * | 1999-07-01 | 2001-01-19 | Sony Corp | 通信装置および方法、並びに媒体 |
JP2001320413A (ja) * | 2000-05-02 | 2001-11-16 | Sony Corp | データ送信装置及び方法 |
JP2002051321A (ja) * | 2000-08-04 | 2002-02-15 | Sony Corp | デジタルビデオ送信機、デジタルビデオ受信機及びデジタルビデオ送受信機 |
JP2002141917A (ja) * | 2000-08-22 | 2002-05-17 | Matsushita Electric Ind Co Ltd | 送信装置、ソースパケット生成装置、パケット形態決定方法、媒体及び情報集合体 |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS56160157A (en) * | 1980-04-22 | 1981-12-09 | Sony Corp | Bit clock reproducing circuit |
US20010013123A1 (en) * | 1991-11-25 | 2001-08-09 | Freeman Michael J. | Customized program creation by splicing server based video, audio, or graphical segments |
JPH07212245A (ja) | 1994-01-26 | 1995-08-11 | Sony Corp | データ転送回路 |
JP3371174B2 (ja) * | 1994-09-22 | 2003-01-27 | ソニー株式会社 | パケット受信装置 |
JP3617655B2 (ja) * | 1994-11-10 | 2005-02-09 | ソニー株式会社 | エンコードシステムおよびエンコード方法、デコードシステムおよびデコード方法、エンコードデータ記録装置およびエンコードデータ記録方法、エンコードデータ伝送装置およびエンコードデータ伝送方法、並びに記録媒体 |
US5901149A (en) * | 1994-11-09 | 1999-05-04 | Sony Corporation | Decode and encode system |
JP3440390B2 (ja) * | 1995-03-01 | 2003-08-25 | 日本電信電話株式会社 | 等時性保証型連続メディア伝送装置及び等時性保証型連続メディア伝送方法及び受信装置 |
US5920572A (en) * | 1995-06-30 | 1999-07-06 | Divicom Inc. | Transport stream decoder/demultiplexer for hierarchically organized audio-video streams |
US5822317A (en) * | 1995-09-04 | 1998-10-13 | Hitachi, Ltd. | Packet multiplexing transmission apparatus |
BR9711082A (pt) * | 1996-03-29 | 2000-01-11 | Lawrence Berkeley National Lab | Realce de rmn emri na presença de gases mopbres hiperpolarizados. |
JP3400681B2 (ja) * | 1997-07-16 | 2003-04-28 | 株式会社日立製作所 | データパケット再多重方法及び再多重装置 |
AR016812A1 (es) * | 1997-08-14 | 2001-08-01 | Samsung Electronics Co Ltd | Metodo para transmitir informacion de video comprimida, disposiciones de compresion y de grabacion de video y aparato de reproduccion de video |
EP0901261B1 (en) * | 1997-09-05 | 2013-01-09 | Hitachi, Ltd. | Transport protocol conversion method and protocol conversion equipment |
JP3017983B2 (ja) * | 1997-11-19 | 2000-03-13 | 株式会社ケンウッド | 同期捕捉回路 |
JP3642180B2 (ja) * | 1998-04-24 | 2005-04-27 | 三菱電機株式会社 | クロック再生装置 |
SG71835A1 (en) * | 1998-09-07 | 2000-04-18 | Victor Company Of Japan | A dejittering and clock recovery technique for real-time audio/visual network applications |
DE69938094T2 (de) * | 1998-11-30 | 2009-02-05 | Matsushita Electric Industries Co. Ltd., Kadoma | Paketwiederübertragungskontrolle mit Prioritätsinformationen |
JP2000173181A (ja) * | 1998-12-04 | 2000-06-23 | Sony Corp | データ記録装置及び出力装置、データ出力システム、データ記録方法及び出力方法、並びにデータ記録及び出力方法 |
US20060262813A1 (en) * | 1998-12-18 | 2006-11-23 | Digital Networks North America, Inc. | Multi-channel video pump |
US6493832B1 (en) * | 1999-03-17 | 2002-12-10 | Sony Corporation | Communication apparatus which handles a time stamp |
JP4081936B2 (ja) * | 1999-03-17 | 2008-04-30 | ソニー株式会社 | 通信装置、通信方法、および記録媒体 |
US6792615B1 (en) * | 1999-05-19 | 2004-09-14 | New Horizons Telecasting, Inc. | Encapsulated, streaming media automation and distribution system |
JP4271787B2 (ja) * | 1999-07-29 | 2009-06-03 | 日本電信電話株式会社 | 通信システム |
JP4193297B2 (ja) * | 1999-08-04 | 2008-12-10 | ソニー株式会社 | 通信装置および方法、通信システム、並びに記録媒体 |
JP4129664B2 (ja) * | 1999-10-05 | 2008-08-06 | ソニー株式会社 | データ処理装置およびデータ処理方法 |
JP3630406B2 (ja) * | 2000-07-17 | 2005-03-16 | 松下電器産業株式会社 | パケット処理装置、パケット処理方法及びその記憶媒体 |
AU2001296586A1 (en) * | 2000-10-05 | 2002-04-15 | Provisionpoint Communications, Llc | Group packet encapsulation and compression system and method |
KR20020032730A (ko) * | 2000-10-27 | 2002-05-04 | 구자홍 | 데이터 재전송 장치 및 그 방법 |
US7023924B1 (en) * | 2000-12-28 | 2006-04-04 | Emc Corporation | Method of pausing an MPEG coded video stream |
US20040114908A1 (en) * | 2001-03-29 | 2004-06-17 | Masanori Ito | Av data recording/reproducing apparatus and method for the same, and disc on which data is recorded by the av data recording/reproducing apparatus or method |
US6907081B2 (en) * | 2001-03-30 | 2005-06-14 | Emc Corporation | MPEG encoder control protocol for on-line encoding and MPEG data storage |
US20030198223A1 (en) * | 2002-04-23 | 2003-10-23 | General Instrument Corporation | Method and apparatus for identifying data streams as networks |
US7061942B2 (en) * | 2002-05-31 | 2006-06-13 | Skystream Networks Inc. | Apparatus for redundant multiplexing and remultiplexing of program streams and best effort data |
EP1553774B1 (en) | 2002-07-16 | 2019-03-13 | Panasonic Corporation | Content receiving apparatus and content transmitting apparatus |
US7349386B1 (en) * | 2003-02-18 | 2008-03-25 | Cisco Technology, Inc. | Method and apparatus for transporting MPEG streams on IP networks including removing null packets |
US7660516B2 (en) * | 2004-02-17 | 2010-02-09 | Panasonic Corporation | Recording medium, reproduction device, program, and reproduction method |
JP5994653B2 (ja) * | 2013-01-23 | 2016-09-21 | マツダ株式会社 | 火花点火式多気筒エンジンの始動装置 |
-
2003
- 2003-07-16 EP EP03741425.7A patent/EP1553774B1/en not_active Expired - Fee Related
- 2003-07-16 US US10/515,528 patent/US7830881B2/en not_active Expired - Fee Related
- 2003-07-16 WO PCT/JP2003/009043 patent/WO2004008760A1/ja active Application Filing
- 2003-07-16 AU AU2003281136A patent/AU2003281136A1/en not_active Abandoned
- 2003-07-16 JP JP2004521223A patent/JP4042745B2/ja not_active Expired - Lifetime
- 2003-07-16 CN CN038164469A patent/CN1669320B/zh not_active Expired - Fee Related
- 2003-07-16 KR KR1020067022351A patent/KR100784874B1/ko active IP Right Grant
- 2003-07-16 KR KR20057000783A patent/KR100709484B1/ko active IP Right Grant
-
2010
- 2010-06-14 JP JP2010134744A patent/JP4666110B2/ja not_active Expired - Lifetime
- 2010-06-14 JP JP2010134745A patent/JP5170166B2/ja not_active Expired - Fee Related
- 2010-10-06 US US12/899,074 patent/US8503471B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10313350A (ja) * | 1997-05-13 | 1998-11-24 | Matsushita Electric Ind Co Ltd | 通信システム |
JPH1188856A (ja) * | 1997-09-05 | 1999-03-30 | Hitachi Ltd | 伝送プロトコル変換方式およびプロトコル変換装置を用いたcatvネットワーク接続方式 |
JP2000307637A (ja) * | 1999-04-16 | 2000-11-02 | Nec Corp | マルチメディア端末装置及び網間接続装置 |
JP2001016267A (ja) * | 1999-07-01 | 2001-01-19 | Sony Corp | 通信装置および方法、並びに媒体 |
JP2001320413A (ja) * | 2000-05-02 | 2001-11-16 | Sony Corp | データ送信装置及び方法 |
JP2002051321A (ja) * | 2000-08-04 | 2002-02-15 | Sony Corp | デジタルビデオ送信機、デジタルビデオ受信機及びデジタルビデオ送受信機 |
JP2002141917A (ja) * | 2000-08-22 | 2002-05-17 | Matsushita Electric Ind Co Ltd | 送信装置、ソースパケット生成装置、パケット形態決定方法、媒体及び情報集合体 |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7830881B2 (en) | 2002-07-16 | 2010-11-09 | Panasonic Corporation | Content receiver and content transmitter |
US8503471B2 (en) | 2002-07-16 | 2013-08-06 | Panasonic Corporation | Content receiver and content transmitter |
JP2006014153A (ja) * | 2004-06-29 | 2006-01-12 | Nec Commun Syst Ltd | パケットエラー監視型mpegデコーダ、mpeg映像伝送システム及びmpeg映像伝送方法 |
JP4491290B2 (ja) * | 2004-06-29 | 2010-06-30 | 日本電気通信システム株式会社 | パケットエラー監視型mpegデコーダ、mpeg映像伝送システム及びmpeg映像伝送方法 |
JP2008511214A (ja) * | 2004-08-20 | 2008-04-10 | ソニー エレクトロニクス インク | データストリーム通信装置及びデータストリーム通信方法 |
JP4874250B2 (ja) * | 2004-08-20 | 2012-02-15 | ソニー エレクトロニクス インク | データストリーム通信装置及びデータストリーム通信方法 |
JP2007266875A (ja) * | 2006-03-28 | 2007-10-11 | Toshiba Corp | 映像データの処理方法及び無線通信装置 |
WO2007119458A1 (ja) * | 2006-03-28 | 2007-10-25 | Kabushiki Kaisha Toshiba | 映像データの処理方法及び無線通信装置 |
US8300709B2 (en) | 2006-03-28 | 2012-10-30 | Kabushiki Kaisha Toshiba | Method of processing video data and wireless communication apparatus |
JP2007329606A (ja) * | 2006-06-07 | 2007-12-20 | Hitachi Ltd | 中継装置 |
JP2009081560A (ja) * | 2007-09-25 | 2009-04-16 | Kyocera Corp | 署名検証方法、ストリーム生成方法、受信装置、およびストリーム送信装置 |
JP2009081564A (ja) * | 2007-09-25 | 2009-04-16 | Kyocera Corp | 署名検証方法および受信装置 |
JP2009081658A (ja) * | 2007-09-26 | 2009-04-16 | Kyocera Corp | 署名検証方法および受信装置 |
Also Published As
Publication number | Publication date |
---|---|
JP5170166B2 (ja) | 2013-03-27 |
JP4042745B2 (ja) | 2008-02-06 |
CN1669320B (zh) | 2011-03-23 |
KR100784874B1 (ko) | 2007-12-14 |
JP2010226766A (ja) | 2010-10-07 |
EP1553774A4 (en) | 2011-05-25 |
JPWO2004008760A1 (ja) | 2005-11-17 |
AU2003281136A1 (en) | 2004-02-02 |
US20110023078A1 (en) | 2011-01-27 |
CN1669320A (zh) | 2005-09-14 |
EP1553774A1 (en) | 2005-07-13 |
JP2010246146A (ja) | 2010-10-28 |
US7830881B2 (en) | 2010-11-09 |
KR20050025607A (ko) | 2005-03-14 |
KR100709484B1 (ko) | 2007-04-20 |
JP4666110B2 (ja) | 2011-04-06 |
EP1553774B1 (en) | 2019-03-13 |
KR20060132017A (ko) | 2006-12-20 |
US8503471B2 (en) | 2013-08-06 |
US20050237434A1 (en) | 2005-10-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4666110B2 (ja) | コンテンツ受信機 | |
RU2273111C2 (ru) | Способ преобразования пакетизированного потока информационных сигналов в поток информационных сигналов с временными отметками и наоборот | |
EP0874503B1 (en) | Data transmitting and/or receiving apparatus, methods and systems for preventint illegal use of data | |
EP0838926A2 (en) | Apparatus and method for transmitting and receiving isochronous data | |
US8966241B2 (en) | Apparatus and method for sending encrypted data to conditional access module over common interface, conditional access module and system thereof | |
US20040260823A1 (en) | Simultaneously transporting multiple MPEG-2 transport streams | |
EP1705842B1 (en) | Apparatus for receiving packet stream | |
JP4135763B2 (ja) | コンテンツ受信器 | |
JP4561822B2 (ja) | コンテンツ受信機 | |
KR100919216B1 (ko) | 데이터 송신 방법, 수신 방법 및 그 장치 | |
US6763037B1 (en) | Transmitting apparatus and method, receiving apparatus and method | |
JPH1173729A (ja) | 記録再生装置 | |
JP3547641B2 (ja) | 送信装置、受信装置及びプログラム記録媒体 | |
KR100636107B1 (ko) | 실시간 데이터 처리 장치 및 방법 | |
MXPA01000580A (en) | Method of converting a packetized stream of information signals into a stream of information signals with time stamps and vice versa | |
GB2490492A (en) | Encrypted data format conversion for a conditional access module (CAM) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2004521223 Country of ref document: JP |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ 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): 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 PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
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: 10515528 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038164469 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003741425 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057000783 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057000783 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2003741425 Country of ref document: EP |